Hi.

I'm sure I had all this working in the past, but not now....... Not helped by issues with my main PC preventing reliable access to it.?? That is fully disconnected, cold and dead for now.

Fldigi 4.2.06 with Flrig 2.0.05 on LMDE 6 running on an 8 core intel based machine, a Dell XPS laptop with 8G RAM, using external USB connected sound device, and serial port DTR to key the radio, a TS870s.

Using Fldigi/Flrig for "normal" working is fine, but attempting to create a macro to send a CWID and "ONLY" a CWID, and I'm failing...

I'm sure this has cropped up before in the list, but attempting to create a macro to send a CWID and "ONLY" a CWID, regardless of the prevailing mode that was being used I can't make work, after some 40 minutes faffing about, so hear I am.

This is the contents behind a freshly assigned "CW ID" Macro button...

<TXRSID:off>
<PUSH>
<MODEM:CW>
<TX>
<CWID>
<RX>
<POP>
<TXRSID:on>

It fails miserably...

Firstly it doe not always put the rig into TX!? Sometimes it will for a few attempts, then it'll not bother, but sends audio each and every time.? (Debugging this with the rig on low power into a load, while using the default audio device for the TX audio, so hopefully no QRM being sent.)

It always sends a RSID (TXID button here is enabled by default, and is not seen to be disabled while the macro runs.)? Then a burst of Olivia 8/250 (the mode that is present before invoking the macro) then does the CWID, and goes back to recieve.

The indicated mode does not change in the lower left display of Fldigi either.

Each individual macro function works exactly as advertised, but not it seems when combined into one file.? In this case.

What have I missed this time??? I.e.? How to force a macro to execute sequentially, as it is shown in the editor.

I just want it to key the radio, send an unadulterated CWID without any TXID or burst of whatever other digimode was being used, then go back to RX restoring the mode that was in use before the macro was invoked.

As earlier.? "Normal" Fldigi usage is fine.?? As are the usual macros for calling answering sending info, logging and closing QSO's etc.

Confused again and getting fed up with it.

73.

Dave G0WBX.