I believe that something like what you want to do COULD be done with Fldigi
using external scripts that are excecuted based upon commands from within
Fldigi. You would have to create a macro, say you call it "CW", and have
it set the mode in fldigi and then run the appropriate script that could
pass the information out to the K3.
Keep in mind, however, that under normal conditions, Fldigi does not do
true CW or true RTTY. It is audio-injected CW and AFSK.
"Real radio bounces off the sky"
On Tue, Sep 30, 2014 at 7:24 PM, David Cole email@example.com [linuxham] <
> Hello Steve,
> THANK YOU for the information... To answer your question regarding why
> a macro for mode changes:
> I have a K3, it has a "special" sub mode for RTTY. Basically it set
> the rig up in LSB, flat audio, allows a special filter to be used for
> RTTY, etc. Under MixW I fire off a set of hex commands to the radio to
> preset several things like this, and to trigger the RTTY sub mode. When
> I leave RTTY, I return the rig back to a standard resting state. I also
> preset a number of things as I change modes... For instance, if I move
> to CW, via MixW, the radio is changed, the bandwidth is set, the zero
> beat is set, the monitor level is set, and the IF passband is moved to
> accommodate the new zero beat frequency... Same for SSB, many things
> get set when I change modes... As you can tell, I like my macros! :)
> Your information helps me in looking for how to make this happen... I
> really want to leave Windows, but MixW is the single program holding me
> hostage to Windows... I may run a virtual box within Linux and them
> MixW if I can't find a way to do what it does with another package.
> As an aside, I would like to get onto a supported package anyway, and
> FLDigi is supported. My problem with MixW is the author is MIA and has
> been for 3 or more years... I expect no more real updates to MixW,
> while FLDigi continues on as a supported, and updated program, with an
> active user community, so I am really looking for a way to make the
> switch anyway... Once on FLDigi, Linux is only a very short step away.
> All of my other machines are running Debian, and the single windows box
> I have is running XP. I have opted off the windows rat wheel... My
> path for Windows is at an end with XP... I will run a <shudder> Mac
> before I return to Windows. But Linux is here, and a wonderful
> environment to use...
> Thanks and 73's,
> For equipment, and software setups and reviews see:
> for MixW support see;
> for Dopplergram information see:
> for MM-SSTV see:
> On Tue, 2014-09-30 at 11:19 -0500, Steve K0STK firstname.lastname@example.org [linuxham]
> > "David Cole email@example.com [linuxham]" said:
> > >I assume most of you are using FLDigi for your linux boxes... Is there
> > >a way from a spot list, to get FLDigi to change the radio's frequency,
> > >fire off a macro,
> > Fldigi does not have a way of retrieving a spot list from an external
> > source (e.g. dxcluster). But it does have an xml-rpc interface which can
> > be used by an external program (e.g. a DX spot browser) to set the RF
> > carrier frequency and run a macro. This feature is documented at
> > http://www.w1hkj.com/FldigiHelp-3.22/xmlrpc-control.html and a sample
> > perl xml-rpc client is shipped with the fldigi source code.
> > There are two ways that fldigi can select a digital mode QSO
> > from within the modem passband (on "on the waterfall"): a Signal Browser
> > (accessible from the "View" menu) and RSID.
> > The Signal Browser is works for some of the digital modes. Clicking on a
> > QSO line sets the waterfall cursor (i.e. tunes the modem) on that
> > frequency.
> > RSID (automatic mode detection and tuning) uses a special sequence of
> > tones transmitted at the beginning of each transmission to identify
> > and tune in the signals received. For this feature to work, not only
> > do you need to enable the feature in the receiver, but in addition the
> > stations you are wishing to tune in need to have this feature enabled on
> > transmission. Other programs also offer this RSID feature as an option.
> > >and enter all data from QRZ into the log by just double clicking the
> > >spot?
> > Not exactly.
> > Fldigi's interface has a "QRZ" button which can be used to populate the
> > logging interface with information on a Call. To use this feature you
> > either select the call sign by double clicking on it in the Receive pane
> > or by typing in in the "Call" box.
> > The "QRZ" button can be configured to look up call information from:
> > - a QRZ cdrom
> > - qrz.com
> > - hamcall.net
> > - hamqth.com
> > - callbook.info
> > >I am looking to replace MixW, and it has so many little cool things that
> > >I want to be sure FLDigi has most of them... I need a macro that gets
> > >fired off if I change modes... Can FLDigi do this?
> > Not that I'm aware of. What do you need this macro to do?
> > >Not looking to start a argument about which is better here, just getting
> > >my ducks lined up before I start down the path of dumping Windows, and
> > >MixW. The only reason I have kept Windows is MixW...
> > Has anyone tried running MixW in Wine? That might be a solution.