Interlock is preventing transmission amp:tgxl

Hi Greg,

Sorry you're having this problem. This is a well known, long standing and very irritating issue that seems to occur at the worst possible times. Flex has said they are aware of it, I think they said they've been able to reproduce it, and are working on it. One might hope there will be a fix in the vastly overdue v3.9 but I'm not aware they've ever stated that.

For what it's worth, various folks report success with different methods of clearing the interlock when it occurs. It seems as though something that works one time won't the next. I've tried changing TX antenna selection to something else and back, restarting the PGXL utility, restarting SSDR and/or the radio itself and restarting the PGXL. In one extreme case I simply restarted everything.

Others may suggest different/ better solutions but those are the ones I'm aware of. Yes, total PITA.

GL Russ KR6W

I have found the easiest remedy for this issue is to go to the PGXL software settings menu, then the FlexRadio tab and just select Save without reentering any radio data. During this process Windows may say that the program has stopped working, so close and restart it and then save the data.

I have found that this fixes both the Interlock issue and the missing amp power display in SmartSDR.

Bill

I have the 6600M, PGXL, TGXL and stacked AG's and running FRStack. I normally do not power these completely off. I am finding that Mike's finding of toggling between standby and operate works but as soon I change bands using FRStack the interlock problem returns. It seems the band change brings back the interlock issue. It is not intermittent . In my instance, I found that only after power cycling the AG's, did the interlock issue disappear and can change bands without the interlock issue. I tried restarting all the software one piece of equipment at a time, after a power cycle on that piece of equipment. Hope this helps tracking down the cause. It would be nice to have this resolved. I have the transmit delay set to 40. While this delay setting may fix other interlock issues, the one I am referencing simply did not clear until the AG's were powered cycled. Anyone else experiencing this?

Randy, KH6XX

I have seen the interlock issue recently while attempting to integrate an AG switch with a 2x8 switch controller with custom SW to mimic an AG switch in **** mode. The 4O3A team has published the AG API that I used as a reference for my implementation. Whenever I set the AG to use stacking and ports 7/8 for routing to the **** switch I get the interlock warning pop-up with AMP:TG. I also monitor the Flex API communication and see an error message 'M31000003 Interlock is preventing transmission' and a status message 'S0|interlock tx_client_handle=0x00000000 state=NOT_READY reason= source=TUNE tx_allowed=0 amplifier='.

This sequence of messages appears to indicate the TG(source=TUNE) is returning a 'NOT_READY' state. This occurs even if the TG is in bypass. I have also seen a 'NO PTT' error pop up on the TG. If I click on the TG TUNE button, it often causes the Flex to reset and SSDR crashes because it loses connection to the radio. Otherwise it pops up a LOW POWER warning.

This typically only happens on Slice 0/ANT1(Port A in my SO2R configuration). Slice 1/ANT2(Port B) will work most of the time. But, sometimes both Port A and Port B will generate the interlock error.

I should also mention that the interlock error occurs with the PGXL turned on or turned off.

Typically, the only way to recover completely is to factory reset the TG and the AG. Sometimes the radio needs to be power cycled.

I have also found that after disabling stacking and importing a previously exported non-stacking configuration, only the first 6 antennas will be listed in the Antennas tab. As if it still thinks it is in stacking mode. The AG seems to maintain some residual state that isn't cleared by an import of a previous configuration.

It would be useful if there was some documentation on the expected sequence of events and TCP messages sent between all the devices in a 'Dream Station' configuration during the PTT process when initiated from the Flex and from the TUNE button on the TG.

The bottom line for me is that there are still some issues with the TG and AG communications during a transmit initiation and likely some internal configuration data getting corrupted. When I have a little more time, I'll put a network sniffer on the TG to look at the communications in/out.

My SW/FW configuration for devices is the following:
Flex 8600: v3.9.19
TG: v1.2.17
PG: v3.8.9
AG: v4.1.16

Eric - NR4O

I have this problem quite regularly, and randomly, since introducing the 8600M to my shack last week. It rarely occurred with my 6600M. I use the AG, PGXL and TGXL. I've tried all of the above suggestions and the only thing that works for me is to power cycle the radio. Annoying at best. It doesn't matter whether my amp is in standby or operate, what band I'm on, which digital mode I'm using. I submitted a ticket, no resolution seems forthcoming. I am running all of the latest firmware for each of the devices.