"Interlock" Issues with FT8 on 60M


w2eck
 

 

I used to use a program called Slicemaster to start and make all the settings in WSJTX to work with my Flex6600. After a question I posted here regarding Grid Tracker ,Dave suggested I try using all the tools in DXLAB that can do all GT & Slicemaster does and more. So I have been just DLXLAB for a few weeks now and it’s great. But a new issue has arisen regarding DXCommander and FT8.

In FT8- 60 Meters, when my Flex6600 goes to Tx, I get the msg "Interlock is preventing transmission". If I try transmitting in the SSB or CW 60M channels, all works fine, I don't get any Interlock msg. Also I don’t get the Interlock msg in any other FT8 bands than 60M.

I posted the issue in the Flex community and received suggestions about adjusting Tx band width and Hi and Lo cut filters, checking center freq etc, which I checked with no fix to the problem.

So I closed DXCdr and used Slicemaster again to start WSJTX. It sets the Rig to Ham Radio Deluxe / PTT CAT Mode Data / Split None, and with these settings the radio transmits on 60M – no Interlock msg.

So I am guessing that I must have amiss in DXCmdr somewhere. Any suggestions?

 

73 Paul w2eck


Dave AA6YQ
 

+ AA6YQ comments below

I used to use a program called Slicemaster to start and make all the settings in WSJTX to work with my Flex6600. After a question I posted here regarding Grid Tracker ,Dave suggested I try using all the tools in DXLAB that can do all GT & Slicemaster does and more. So I have been just DLXLAB for a few weeks now and it’s great. But a new issue has arisen regarding DXCommander and FT8.

In FT8- 60 Meters, when my Flex6600 goes to Tx, I get the msg "Interlock is preventing transmission". If I try transmitting in the SSB or CW 60M channels, all works fine, I don't get any Interlock msg. Also I don’t get the Interlock msg in any other FT8 bands than 60M.

I posted the issue in the Flex community and received suggestions about adjusting Tx band width and Hi and Lo cut filters, checking center freq etc, which I checked with no fix to the problem.

So I closed DXCdr and used Slicemaster again to start WSJTX. It sets the Rig to Ham Radio Deluxe / PTT CAT Mode Data / Split None, and with these settings the radio transmits on 60M – no Interlock msg.

So I am guessing that I must have amiss in DXCmdr somewhere. Any suggestions?

+ I suggest that you ask FlexRadio Technical support to tell you exactly what causes SmartSDR to report "Interlock is preventing transmission" on one band only (60m). Given that information, we can take the appropriate diagnostic steps.

     73,

          Dave, AA6YQ


dl8le
 

No problem here with DXLab, WSJT-X (and JTDX), Flex6600 (with Smart SDR, not the physical interface) and JT-Alert on all bands. But I know that I cannot do any spotting on 60m in Spotcollector, i.e. frequency is not allowed, so might be that this behaviour in connection with Gridtracker may cause the problem. Just an idea, which may be wrong, however.
73

Juergen, DL8LE


Brian D
 

May be due to the "split" setting in WSJTX moving the base TX frequency so
that the audio bandwidth could produce tones out of the band segment.


"dl8le" <dl8le@...> wrote:

No problem here with DXLab, WSJT-X (and JTDX), Flex6600 (with Smart SDR,
not the physical interface) and JT-Alert on all bands. But I know that I
cannot do any spotting on 60m in Spotcollector, i.e. frequency is not
allowed, so might be that this behaviour in connection with Gridtracker
may cause the problem. Just an idea, which may be wrong, however. 73

Juergen, DL8LE






--
Brian D
G3VGZ G8AOE G3T
IO94im


Dave AA6YQ
 

+ AA6YQ comments below

No problem here with DXLab, WSJT-X (and JTDX), Flex6600 (with Smart SDR, not the physical interface) and JT-Alert on all bands. But I know that I cannot do any spotting on 60m in Spotcollector, i.e. frequency is not allowed, so might be that this behaviour in connection with Gridtracker may cause the problem. Just an idea, which may be wrong, however.

+ The BandModes.txt file distribute with SpotCollector updates does not contain entries for 60m, but you can add them to your own custom bandmode.txt file, which will enable you to submit spots on 60m. See

https://www.dxlabsuite.com/spotcollector/Help/ConfigurationGeneral.htm#Sub-band%20Definition%20panel

73,

Dave, AA6YQ


ab4sf@...
 

In my limited experience on 60 with my Flex 6600, I agree with Brian D.  I think the issue is that Rig and Fake WSJT-X can shift the transmitter VFO outside of what the radio thinks are the allowable 60-meter band "channels" limits that are set into the Flex F/W while WSJT-X keeps the transmitter audio frequencies in the center area of the transmitter's audio passband (for best response).  I have found that if I set WSJT-X to None and then keep my transmit audio frequency near the center of WSJT-X audio range myself,  the radio is happy and I can make QSO's on 60m. Perhaps there is a more elegant solution but this has worked for me.

Wray AB4SF


Dave / NR1DX
 

How do you handle F/H in this manner?

On 12/11/2022 10:04 AM, ab4sf@... wrote:
In my limited experience on 60 with my Flex 6600, I agree with Brian D.  I think the issue is that Rig and Fake WSJT-X can shift the transmitter VFO outside of what the radio thinks are the allowable 60-meter band "channels" limits that are set into the Flex F/W while WSJT-X keeps the transmitter audio frequencies in the center area of the transmitter's audio passband (for best response).  I have found that if I set WSJT-X to None and then keep my transmit audio frequency near the center of WSJT-X audio range myself,  the radio is happy and I can make QSO's on 60m. Perhaps there is a more elegant solution but this has worked for me.

Wray AB4SF


Joe Subich, W4TV
 

On 2022-12-11 10:12 AM, Dave / NR1DX wrote:
How do you handle F/H in this manner?
WSJTX F/H *does not require* that you change frequencies. A "fox"
will still acknowledge a report that is received above 1000 Hz.
The frequency move is only an attempt to assure that the hound sends
his report on a frequency that is (relatively) QRM free.

In any case, if one has WSJTX SPLIT=NONE and tunes so the Fox is
below 1000 Hz (typically 300 - 500 Hz) and sets a transmit frequency
above 1000 Hz, WSJTX will change the *transmit audio frequency* as
required to send the "hound" report (even if it is below 1500 Hz).

73,

... Joe, W4TV

On 2022-12-11 10:12 AM, Dave / NR1DX wrote:
How do you handle F/H in this manner?
On 12/11/2022 10:04 AM, ab4sf@... wrote:
In my limited experience on 60 with my Flex 6600, I agree with Brian D.  I think the issue is that Rig and Fake WSJT-X can shift the transmitter VFO outside of what the radio thinks are the allowable 60-meter band "channels" limits that are set into the Flex F/W while WSJT-X keeps the transmitter audio frequencies in the center area of the transmitter's audio passband (for best response).  I have found that if I set WSJT-X to None and then keep my transmit audio frequency near the center of WSJT-X audio range /myself/,  the radio is happy and I can make QSO's on 60m. Perhaps there is a more elegant solution but this has worked for me.

Wray AB4SF


dl8le
 

I have set WSJT-X to Fake and - as mentioned before, there are no problems in using the Flex 6600 on 60m for FT8. The reason why either Split or Fake should be used is still valid in my opinion and should be followed by the users.

@ Dave: Thank you for the information to change the bandmode.txt, now it works.

73

Juergen, DL8LE


w2eck
 

I am not experiencing the interlock issue anymore. I did change the WSJTX setting to fake it, not certain that was the problem. 

73 Paul w2eck