Re: sending to serial port from a script?

Thanks Andy.

I "discovered" the "sleep n" function myself yesterday evening, and now have that all working nicely. Thanks anyway.

(The script syntax in reality is not exactly as I originally quoted either. I can post the exact version later if anyone wants, I'm on a mobile not at the PC just now.)

Hint:  Use double quotes, and hex values!

echo -en "some command string\x0d" > /dev/ttyUSB0

Re Bash's recent trouble.
Bash is patched now anyway, but it doesn't matter if you script with it or not, it exists in the system and is needed by other features and functions, so if there is any problem remaining, it is still vulnerable regardless of what I use as the script interpreter.

But point taken.  Let the updates in!


Dave G0WBX.

Posted by: Dave Baxter <g8kbvdave-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>


PWR slider , flrig 1.3.17 + K3/100

PWR control only slides between values of 0 and 12, as if it no longer sees the rig as a K3/100.

If i turn power up above 12 using the knob on rig the numeric display in flrig displays the value ok, but the slider is 'pegged' for any values above 12watts.

I tried deleteing k3.prefs and starting over.

Also compared
my last backup of the .prefs file from before the update to 1.3.17, and everything referencing anything like "pwr" matches, I think.

Any other K3/100 owners have this happening?



Posted by: o11oo1oo-/E1597aS9LQAvxtiuMwx3w@public.gmane.org


sending to serial port from a script?


Working with Lubuntu 12.04

So I can "pre-set" something (a KISS capable TNC on a serial port) in a shell 
script used to start another program, before that program starts.

After some googling, I found a page at:- 
(and other sites with similar info)

Cross referencing what is said there and the other sites with the contens of 'man 
stty', would these work reliably in bash scripts?

# kisson.sh  To enter KISS mode.
# 9600bd, 8bits, one stop bit, no parity
stty -F /dev/ttyUSB102 speed 9600 cs8 -cstopb -parity
echo -en '\x13' > /dev/ttyUSB102
echo -en 'KISS ON\x13' > /dev/ttyUSB102
echo -en 'RESTART\x13' > /dev/ttyUSB102

(ttyUSB102, is udev'd to point to whatever the OS assigned to the actual 
hardware device as it found it.   Works well.)


# kissoff.sh  To exit KISS mode.
# 9600bd, 8bits, one stop bit, no parity
stty -F /dev/ttyUSB102 speed 9600 cs8 -cstopb -parity
#             0xc0, 0xff, 0xc0
echo -en '\x192\x255\x192' > /dev/ttyUSB102

I've not had the chance to try this, yet (my sacrificial 'nix box just committed 
suicide, hard disk or RAM issues I think.  It was not exactly the newest PC on the 
floor.  Memtest86 shows OK, running Spinrite now, no obvious issues yet.)

What I've not been able to figure out yet, is how to put a short wait (delay) after 
each of the echo commands to the port.   (Needed I find, to allow the TNC to 
chew on things and sort its knickers out after being told to do something!)

I do know that sending it in one hit 'KISSON\rRESTART\r' (\r == cr byte) sends 
it into abject raptures, needing a power off/on cycle to get it out of the mess.

This procedure (psudo code)...

  Send a single \r, (empty line)

  Wait/give time for the tnc to send its default 'cmd:' prompt

  Send KISS ON\r

  Wait/give time for the tnc to send its default 'cmd:' prompt

  Send RESTART\r

Works 100% of the time.   I've proven that with Procom+ under DOS! and even 
a GWBASIC program!   But that's all on DOS, and I'm wanting to do this under 

I see crN listed in stty's help text, but no clue where to use that function (a delay 
of N 'somethings' after a cr byte, nor are the units of the delay specified.)

Any (sensible) suggestions?  :)

I've got another hour or two, before I may get the old 'nix box back.   Else even 
longer before I get to sit in front of another with a real port, not a VM.   Or 
reload the OS on the old box again.


Dave G0WBX.

Posted by: "Dave B" <g8kbvdave@...>


FLrig 1.3.17 Issues

I'm running a Kenwood TS-570 on a RT-Systems Serial-USB cable, it does this on 2 different computers. It worked fine on all previous version on both Windows and Linux. Then version 1.3.17 came out, now it don't work properly. It keeps setting the sliders to 0 no matter what you set the polling for. I have tried every setting there is and nothing fixes the issue. I can't believe I'm the only one having this problem. I've tried E-mailing the author of the software but it comes right back as undeliverable! does anyone know how to contact him?

Posted by: steve.frodo.5632-/1bC63wxbnBWk0Htik3J/w@public.gmane.org


x86 optimizations

When building fldigi, the configure script gives several options for "x86 optimizations":

    --enable-optimizations  use x86 optimizations (none|sse|sse2|sse3|native)

What is "native" and is it likely to add much performance? Is it preferred to sse3?


Bob W6CP

Posted by: Bob Snyder <bob.snyder-j9pdmedNgrk@public.gmane.org>


CTY-2411 Country Files - 21 October 2014

The Country (CTY) Files were updated on 21 October 2014:


For installation instructions, start at:


Hover your mouse over the word Contest in the menu, then select the
software you are using.

To install the file, follow the link to your software at the top of the page.

If you are interested in a bigger CTY.DAT for everyday logging, you can get
it here:


Note that the release notes (and Version Entity) for this larger file are
different than what is shown below.  There is a separate link to them.

Here are the release notes:

    21 October 2014 (CTY-2411)
    VER20141021, Version entity is American Samoa, KH8

    Added/changed Callsigns/prefixes:

	* 3V8CB/J is Tunisia, 3V
	* 9M4SWK is East Malaysia, 9M6
	* EA9PD/7 is Spain, EA
	* TO2A is French Guiana, FY
	* GB0AS and GB2AS are both Northern Ireland, GI
	* GB2JSA is Jersey, GJ
	* GB0BSS and GB4PAS are both Scotland, GM
	* GB4ADU and GB4XT are both Wales, GW
	* IQ2MI/J, IQ3FL/J and IQ6VP/J are all Italy, I
	* KH8Z is Mariana Islands, KH0
	* KD3FZ, KE4ZXQ, KI6WOJ, KQ6CD, W8JVF and WA6UVF are all Hawaii, KH6
	* KH0WF is American Samoa, KH8
	  and N0IVJ are all Alaska, KL
	* PA3AFG/J, PA6JAM/J, PE2MC/J, PH9GFB/J, PI4BG/J and PI9TP/J are all Netherlands, PA
	* SZ2TSL/J is Greece, SV
	* TA1AO/4 is Asiatic Turkey, TA
	* RQ0C/4, RT9T/3 and UE95WS are all European Russia, UA
	* YT1S/J is Serbia, YU

    Retired Callsigns/prefixes:

	* 9M57MS and 9M57MW in East Malaysia, 9M6
	* GB2NZ, GB2RWW and GM4WSB/P in Scotland, GM
	* GB0BRE, GB2BEF and GB2WW in Wales, GW
	* 8N1AQ/JD1 in Minami Torishima, JD/m
	* KA8EBL and KB7MEU in Hawaii, KH6
	* N0LHN and WA7USX in Alaska, KL
	* LU5DQ/D, LU6EVD/D and LW3DG/D in Argentina, LU
	* TA1AYR/6 in Asiatic Turkey, TA
	* R85QMR and UA0QGM/3 in European Russia, UA
	* RA0BA/8 in Asiatic Russia, UA9

73 - Jim AD1C


Jim Reisert AD1C, <jjreisert at alum.mit.edu>, http://www.ad1c.us

Posted by: Jim Reisert AD1C <jjreisert@...>


fldigi 3.22.01 release

fldigi 3.22.01 has been release and posted to http://www.w1hkj.com

with the following changes from version 3.22.00

Version 3.22.01 * Maintenance release

   RX single click
     * restored Name / QTH clickable (1)

   Macro Buttons
     * Increase width of alternate macro button(s)
     * Add 2 row scheme, one above, one below text panel

   Thumb drive
     * update documentation on thumb drive installation

   Power Squelch
     * Correct initial state of power squelch

   Documentation update
     * Added missing documentation on use of Smeter / Power-meter
       display on main dialog.
     * Added new xmlrpc TxID commands

   TxID control via xmlrpc
     * Added xmlrpc commands
       - Main.get_txid
       - Main.set_txid
       - Main.toggle_txid

   Analysis modem
     * Fix seg fault in rx_process

   XMLRPC Character measurement issues with 8PSK modems
     * Update xmlprc Main_get_char_timing() routine. Problem still 
persist in
       other areas of FLDIGI ie Macro CPS, other xmlrpc commands.

   Gray-mapped 8PSK and soft-decision (2)
     * Upgraded 8psk to Gray mapped constellation
     * Implemented Soft-Decision decoder based on Gray constellation
     * Even when the received phase is distorted by +- 1 phase-position:
        - One of the bits is still known with 100% certianty.
        - Only up to 1 bit can be in error.
     * Increased gain for noisy/weak/HF channels

   View/Hide Smeter (3)
     * Add view/hide Smeter / Power meter
       - configuration saved in progdefaults, requires
         "save config" to keep setting between executions.
     * Reduce minimum width of main dialog to 750 pixels

   CW matched filter
     * Fix to inoperative matched filter

   flarq update
     * flarq changes to bring up to date with the 3.21 maintenance
     * version 4.3.5

(1) Default is to use the SHIFT-mouse-left-click for selection of word.  
     can be changed to allow a SINGLE left click to select word.  
Previous versions
     allowed a DOUBLE left click.  This was changed to provide better 
touch screen
(2) 8PSK modem types in this release are NOT compatible with release 3.22.00
(3) Default is to hide Smeter.  Change with menu item:
       View / 'View/Hide Smeter'
     Save configuration to retain setting between execution sessions.

As of this distribution I will no longer be publishing linux binary 
files.  There are simply too many shared library dependencies to account 
for.  The self help group for fldigi and the other programs has written 
an excellent set of instructions for building the applications on a 
number of different Linux, OS X, and Windows platforms.  Please refer to 
the fldigi wiki, https://fedorahosted.org/fldigi/wiki

Report any problems to one of the three yahoo groups:


or directly to me.

The on-line help has been updated and a new pdf help file published on 
the http://www.w1hkj.com web site.

73, Dave, W1HKJ

Posted by: w1hkj <w1hkj@...>


FLDIGI on Thumb Drive Test

Today I concluded my test of operating FLDIGI on a thumb drive, which 
was accomplished by placing FLDIGI and other associated FL programs in 
an "FL_APPS" directory, as outlined in the FLDIGI documentation.

I ran FLDIGI and FLAMP successfully from my D: thumb drive for several 
months. No problems. All related directories and preference files were 
created there too.

Concluding that it worked just fine and deciding to free up that USN 
port, today I created an FL_APPS directory at:


- And copied all of the files and directories from my thumb drive to there.

Once I had done that, all that remained was to update the FLDIGI 
configuration to autoload FLAMP from it's new location, and update FLAMP 
to autoload it's tx files from the new location. - I also updated the 
desktop batch file to load from the new location.

First time I tried it out, it worked perfectly. - And now I've freed up 
a USB port and a thumb drive for other uses.

Running FLDIGI from a thumb drive was an unqualified success. All SGARN 
multicast were operated from that thumb drive for months with zero issues.

73 DE Charles, N5PVL

Posted by: Charles Brabham <n5pvl@...>


Fldigi 3.22

Got the new version today, nice, I can defiantly see the frequency now. One issue I noticed right off the bat is the view channels does not stay, If you close the program, then reopen the program, I have to click and view channels again and set size. other than that ok, although I have not researched the new S meter yet, so far its there but that is it. thanks Tom K8WDX

Posted by: k8wdx-/E1597aS9LQAvxtiuMwx3w@public.gmane.org


Fldigi 3.22 on Mint 17

I have Fldigi 3.22 installed on a dual boot laptop; Mint 13 and Mint 17, connected to an FT-857D.

While all works correctly on the Mint 13, using either rigCat or Hamlib on Mint 17, the CAT functions

fail to operate. Even with Hamlib as the selected option, the status Log gives the following (partial)

   I: init_modem: mode: 1, freq: 0
I: Open: Port Audio open mode = Read, device type = paALSA
I: src_data_reset: rbsize = 16384
I: do_readfile: Reading 247 bytes from logbook.adif
I: do_readfile: Read 1 records in 0.00 seconds
I: kiss_init: UDP Init - OK
I: kiss_loop: Kiss loop started.
I: ReadFromHostSocket: Kiss RX loop started.
I: rigCAT_close: Waiting for rigCAT_ thread
I: rigCAT_loop: Exit rigCAT loop
I: ~KmlSrvImpl: Cancelling writer thread
I: ~KmlSrvImpl: Cancelling subthread
I: ~KmlSrvImpl: Thread stopped. Message:Canceled thread
I: ReadFromHostSocket: Kiss RX loop exit.
I: kiss_close: Kiss loop terminated.
I: close: Stopping XML-RPC server

The PTT and waterfall info work properly. The Hamlib settings were copied from the working version (Mint 13)

but I continue to get "hamlib_init: IO error".

Any suggestions as to what files to examine/compare or setting to change. Since the USB to CAT interface cable works with Mint 13, I believe it's in the software.

Perhaps a query to the Mint 17 developers; but I thought I'd start here .

Thanks for any help/suggestions.




Posted by: wpfing62-/E1597aS9LQAvxtiuMwx3w@public.gmane.org


fldigi 3.22.00 issue

for me the squelch doesn't work.

Posted by: jhhaynes-ihVZJaRskl1bRRN4PJnoQQ@public.gmane.org