Flrig query

I am a fan of flrig, but have one issue, and it’s possible its just me having a derpy moment.

When it starts, the power and audio in and out are not where I want them. 

I’ve read the manual, and searched around the menus, but haven’t found a way to save my configuration. 

Is there a way?

-73 Mike N3LI -

Posted by: Michael Coslo <mjcn3li@...>


Re: Almost 100% Linux but some issues with QSSTV 8.2.11 and latest Fldigi PTT ?

Thanks Stew haven't heard of that one.

Cliff VK2NP

Posted by: vk2ccj-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org


Re: Setting up Rig Control on Yaesu FT 897D with Late 2013 MacBookPro and USB Signalink.

> Re: Setting up Rig Control on Yaesu FT 897D with Late 2013
>     MacBookPro and USB Signalink.  
>     Posted by: "Marty Hartwell" mhartwe@... martyhartwell
>     Date: Mon Jun 15, 2015 6:33 am ((PDT))
> Hi Bob
> I went to Dave's web site and also did not see a xml file for the
> 897D. I would try the 857D file to see it may be what other 897D users
> have been using. I have seen reference to others using Fldigi with the
> FT897D on this list before, so that may be how they are doing it. I
> have the 817 and have heard that it has a slightly different command
> set so I wouldn't try that file.
> Marty kd8bj

Does the Signalink do Rig Control?

I thought it's just an over priced soundcard with a crude VOX based PTT (That 
most rigs probably do better themselves anyway) with added EMC issues, "Pin 1" 
problems etc.   (RF getting in, from many reports I've seen, but others seem OK 
with it.)

Looking at:-

There is no mention of rig control, other than TX/RX by PTT.

So, you'll need a seperate USB<>Serial device for Rig "Control".

Anyway, download the XML file (right click, save as etc.) for the rig that is 
closest to what you have.    It's just a text file, so there is nothing stopping you 
from editing it to tweak it to work better with the radio you have.

Your rig's user manual should detail how to hook it up for CAT control, and have 
a list of what commands etc it uses, plus there is a section in the Fldigi wiki 
describing the RigCAT XML "language" in some detail.

Find that at:-

Use your favorite plain text editor, or Geany (does context highlighting, making 
things much easier to follow) to edit such files.

You can "test" the various commands with a simple terminal emulator program 
too, always good to do, as many radios features and foibles are often not as fully 
documented as you might expect, plus some combination of commands work 
better as a group when sent in one sequence than another.

See also:-
And the section regarding RigCAT control.

The "Grin Factor" when you make it work is well worth the effort, then you can 
send Dave (HKJ) a copy to add to the list of available rig_xml files.   Plus, you'll 
have learnt a valuable skill to help others with, as well as yourself in the future.

As someone else said, Flrig supports the 897D anyway (I don't have such a 
radio, so can't comment as to how well that works) and works well with Fldigi.    
Not sure about Hamlib, but the deatails as to how to use each of those methods 
can be found in the last of the above links.

I can't currently locate a list of suported rigs in Hamlib.   (www.hamlib.org is 
broken, it bounces to a non existent wiki on Sourceforge.)

If you have it installed, you can query it, but don't ask me exactly how.
(Poor documentation sadly, I think a command line command:-
'rigctl -1'   Might do that, but be prepared to capture all that scroll's up the 
screen, from vague memory, there is lots of it!)


Dave G0WBX.
(Still slowly working on the KX3 'driver' in Flrig.
 Never enough of the right sort of contiguious time available.)

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


How to submit a bug report

How do we submit bug reports? There appears to be one with flmsg.


Posted by: "thorpejeffrey@..." <thorpejeffrey@...>


Setting up Rig Control on Yaesu FT 897D with Late 2013 MacBook Pro and USB Signalink.

Hi Gentlepeople;

I am new to FLDigi and setting up rig control has been frustrating.

I have a Macbook Pro, the Yaesu FT897D and Signaling USB connected together.  Using Yaesu CT-62 FTDI Cable.  Currently using a 2.0 USB hub.  Will not be using the hub at Field day.  Previously have used MacLogger DX and Cocoamodem.  Radio has worked fine with Cocoamodem using the Yaesu USB CT-62 FTDI Cab.

In FLdigi config I see Hardware PTT, RigCat and Hamlib not sure where to go here.

Tried RigCat and looked at the site http://www.w1hkj.com/xlms for the FT897D and I didn’t see it listed.  So I am “sorta” back to ground zero.

Signalink, audio and waterfall are working fine.

A little history if I may.  I am a casual user and contester with a small station.

I really enjoy PSK 31 and was excited to see FLdigi demonstrated by a friend as one program does it all, which is what I am looking for. Hope to play at Field Day next week.





Posted by: b.merrill90 <at> yahoo.com


Almost 100% Linux but some issues with QSSTV 8.2.11 and latest Fldigi PTT ?

HI all,

I am a on/off Linux user over many years, giving it another go.

Running the Latest Linux Mint on an external drive on a MacMini at the moment.

The rig I am running is a Icom  IC-9100 over the USB connection only

I added several PPA's to the sources list and now have the latest Fldigi , WSJT-x

Managed to compile from source with info from the QSSTV site QSSTV 8.2.11 

Tried compiling the earlier version 8.1.17 but came up with docx errors ?

Brought in WSJT-x 1.60 wh ich included WSPR and JT modes using the additional repository

I don't seem to have any issues with the WSJT-x .

QSSTV is mostly working but when I go to Transmit certain modes PD and Robot I just get a Grey screen and the transmitted image is likewise. Martin and Scottie modes seem ok. Probably a compiling error on my part.

Fldigi is working mostly but sometimes I get strange sounding audio but can get it back to normal when i logout and back in again.

Also have no PTT control in Fldigi unless I run Flrig at the same time. Freq CAT control works fine either way.

I have be en able to get the PTT to work in Fldigi using my US-Navigator Interface but much prefer the single USB cable .

One further thing is there a way to lock down what ports a device uses when plugged in as sometimes they vary i.e.: /dev/ttyUSB0 becomes 1 etc.

Have a similar problem when running programs on OS X.

All in all pretty happy with my results this time round in Linux.

I have MMSSTV running perfectly under wine also.

Any suggestion on a good Log Keeping Program for Linux ? I use Rumlog on my Mac.



Posted by: vk2ccj-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org


Re: Interview with W1HKJ

> 3. Interview with W1HKJ
>     Posted by: "HFRadioPro" hfradiopro@... hfradiopro
>     Date: Sun Jun 14, 2015 7:24 am ((PDT))
> It was nice to catch Eric's (4Z1UG) interview with David on the QSO
> Today podcast.  If you want to check it out, it can be found at
> http://goo.gl/CvLNmV (iTunes), http://goo.gl/uhf1XZ (Stitcher), or on
> the web at http://goo.gl/o7F5o3.


Will listen to that later.

For those who wont (wisely cautious) click on obscured links in emails

Go to:-  www.qsotoday.com, then scroll down to Episode 044.

You can also "right click" the "Listen to Podcast" button and save the .mp3 as a 
file to listen offline, or copy to a portable device etc.

(some 50 minutes duration, and good quality audio too.)

There is also other good stuff to listen to on that site.


Dave G0WBX.

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


email problems

I do NOT want to receive emails from you .. I have been trying to UNSUBSCRIBE but emails are returned, 

Please unsubscribe me and confirm.

Brian a 

Posted by: briana990-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org


XMLRPC modem.set_by_nam() method not working properly in 3.22.10 ( or .08)

Hi All,

The following is on Debian 8 with Mate Desktop on dual core Linux box 
with 4gb RAM.

The XMLRPC method mode.set_by_name is not working properly in FLdigi. IE;

Lets say the modem is set to 'RTTY' and I send the XMLRPC command 
modem.set_by_name('CW').  If this is the first time I've issued the 
modem.set_by_name() method, it works, but takes maybe 5 seconds to 
complete. I then issue the command modem.set_by_name('RTTY') to set it 
back and it hangs for a long time and then completes but does not set 
the modem back to RTTY.

The return value the first time I send the command is correct, setting 
to 'CW' changes it slowly to 'RTTY'. After that, setting it back to 'CW' 
hangs for a long time then returns, but the return value is 'CW' still.

All the other methods seem to work OK.

Here is a session of me trying using the python shell . The return 
values are on the next line under the method invocation.

 >>> import xmlrpclib

 >>> s = xmlrpclib.ServerProxy("http://localhost:7362")

 >>> s.log.set_rst_out("559")   ***THIS WORKS IMMEDIATELY****

 >>> s.modem.set_by_name('CW')  ***THIS WORKS BUT SLOWLY***
'RTTY'                                                ***CORRECT RETURN 

 >>> s.modem.set_by_name('RTTY')   ***THIS HANGS THEN RETURNS WITHOUT 
'RTTY'                                                 ***WRONG... 
should be 'CW' (Probably because it didn't set)

setting to 'CW'***

 >>> s.modem.set_by_name('RTTY')   ***THIS WORKS SLOWLY***
'CW'                                                    ***CORRECT 
RETURN (old modem name) ***

 >>> s.modem.set_by_name('CW')   ***DOES NOT SET MODEM TO 'CW' and 
returns 'CW'

73 de Jim, W2XO

Posted by: Jim Durham <jimdur@...>


Interview with W1HKJ

It was nice to catch Eric's (4Z1UG) interview with David on the QSO Today podcast.  If you want to check it out, it can be found at http://goo.gl/CvLNmV (iTunes), http://goo.gl/uhf1XZ (Stitcher), or on the web at http://goo.gl/o7F5o3.

Dave Wright

“Real radio bounces off the sky"

Posted by: HFRadioPro <hfradiopro-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>



Others I have mentioned this before but I have been thinking about this more recently:


You sent up your flmsg in the socket settings to send to a fl-traffic ARQ address and Port instead of fldigi.

When you compose a flmsg message and press the auto-send button, it sends it to fl-traffic instead of fldigi.

Also fl-traffic monitors incoming received messages.

Fl-traffic lists the messages for outbound in inbound separately.

From fl-traffic, you can send the outbound or forward the inbound to send as well to any instance of fldigi you have set up by ip/port.

You can have multiple instances of fldigi set up by IP and/or port so one per radio/band HF/VHF/UHF/ etc.

fl-traffic allows you to check off if the message has been forwarded and a field for notes and to enter who you passed it to, etc.

fl-traffic has a running log of historical tasks you completed, receiving of files, sending of files, etc.

I know this might add too much for the normal user to handle.
But imagine a large scale event with multiple messages that need to be passed to multiple frequencies / nets.

Now imagine multiple flmsg message takers / fillers or even the served agency themselves filling out the messages in flmsg.

They then press autosend and it goes into the fl-traffic queue.

A ham is running the fl-traffic "switchboard" and is the only one that actually initiates the sending of the message as he/she is the only licensed amateur radio operator.

Imagine if there was a two way interface to flmsg also so that same "switchboard" operator could direct an incoming message to the appropriate operators computer.

This could make things flow a lot easier and reduce manpower needed to translate forms as the served agency is filling out flmsg forms natively and receiving them the same way.

Now for someone to implement this in actual code - the hard part.

I am no C programmer, I can program in different dialects of BASIC and have no time with my current work commitments.

Is anyone up to the challenge?

Larry Levesque

Posted by: Larry Levesque <ka1vgm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>