Robert:
Your response reminded me that I have an "ancient" flamp.prefs file as I haven't needed to reconfigure it for a long time. I deleted it and "forced" a new one.? I see there is at least one new field. Regardless, the replacement didn't affect anything. Here is the information requested... The "screenshot" is what gets Tx'ed. I have tested any number of individual block relays, singles and multiples (with both spaces and commas as delimiters) with no difference. Typical modem is MFSK-32, but I have tried others in testing without any change. I should add that the Windows machines (running an older version of fldigi) is only used for SDR reception and not connected to a radio.? I "tested" them (after updating flamp to v2.2.12) in order to see if it was a Linux issue. This evening, I recompiled flamp on one of the three Linux boxes (all are connected to a radio) and still get the "aborted" relay. I seem to recall that previously the "blocks" field used to persist until AFTER the relay was complete before it was cleared (per the configuration setting).? For v2.2.12, it is cleared BEFORE the Tx even starts. Thanks for your help. de KI4DKS FLAMP.prefs
FLAMP.prefs
8F4F_HH-AZ-RR-240430-2000Z-TXID_BAD.k2s
8F4F_HH-AZ-RR-240430-2000Z-TXID_BAD.k2s
![]()
Screenshot 2024-05-08 225912.png
|