Welcome to the FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
Need the latest SmartSDR or 4O3A Genius Product Software?
SmartSDR v4.1.3 | SmartSDR v4.1.3 Release Notes
SmartSDR v3.10.15 | SmartSDR v3.10.15 Release Notes
The latest 4O3A Genius Product Software and Firmware
If you are having a problem, please refer to the product documentation or check the Help Center for known solutions.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.

Interlock is preventing transmission amp:tgxl

AB7R
AB7R Member ✭✭
in Tuner Genius XL

I did a search on this and did not find any solutions. I have the tgxl and AG setup with the new 8600. When I click on SSDR TUNE I get the subject error notification.

Something is causing SSDR to not generate RF but I cannot find anything about interlock.

Please help….so close yet so far.

SSDR 3.8.23.35640

AG 4.1.1.6

TGXL 1.2.11

PGXL 3.8.9

TX delay in radio settings is 40.

Greg-AB7R

Tagged:

Answers

  • Russ Ravella
    Russ Ravella Member ✭✭✭

    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

  • W2PP
    W2PP Member ✭✭✭

    currently it’s only affecting slice A. The B slice transmits. The PGXL is in standby

  • AB7R
    AB7R Member ✭✭

    Thanks. I just tried slice B and got the same errors. So I have this $5K amp and $2K tuner that are door stops until someone fixes the software. Uggghhhh!!!!

  • Erik Carling EI4KF
    Erik Carling EI4KF Member ✭✭✭✭

    Try a factory reset. If you have profiles by all means export them first. But after the reset try without importing them.

    Also, always be sure to de-select the "Preferences" check-box when exporting or importing Profiles in order to prevent possibly exporting/importing corrupted band-persistence settings.

    The above is Ken Wells' answer on the Forum that solved the interlock issue for someone.

    Then there is always a Help Desk Ticket.

  • AB7R
    AB7R Member ✭✭

    Thanks Erik. I will try that later today. I did also submit it ticket yesterday.

    73!

    Greg

  • Mike-VA3MW
    Mike-VA3MW Administrator, FlexRadio Employee, Community Manager, Super Elmer, Moderator admin

    Next time you see this, try changing the status of the TGXL from Standby to Bypass and see if that clears it.

    Powering down the PGXL and TGXL can also clear it, but you might have to wait about 2 minutes. I have seen that about once/month and I did this morning. I turned off the TGXL and PGXL and it cleared after a short period of time.

    I hope that helps.

  • Bill AB7AA
    Bill AB7AA Member ✭✭✭

    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

  • AB7R
    AB7R Member ✭✭

    Thanks Bill. I did that and it fixed crazy SWR readings but not the amp info going to SSDR or FRStack.

  • KH6XX
    KH6XX Member ✭✭

    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

  • AB7R
    AB7R Member ✭✭

    Thanks Randy. Since the recent FW update to 3.9.18 AND the TGXL update these interlock issues have been almost completely gone.

  • NR4O
    NR4O Member ✭✭

    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

  • Mike-VA3MW
    Mike-VA3MW Administrator, FlexRadio Employee, Community Manager, Super Elmer, Moderator admin

    Please open a support ticket for this. Engineering is aware of part of this problem.

  • Phillip Hare
    Phillip Hare Member ✭✭

    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.

  • Geds42
    Geds42 Member ✭✭

    I ran into a similar issue yesterday during the CQ WW contest. While on 15 meters and not trying to transmit, the Interlock warning was popping up and down. I moved down the band and when I hit the Tune option on the TGXL menu SmartSDR crashed and the 8600 rebooted. When it came back up, there was no interlock warning, so I tried Tune again on the TGXL and got the same results. I powered down the 8600, waited a few minutes, unplugged the DC power, waited, and then brought the 8600 back up. I tried using Tune on 10, 20, and 40 meters with no issue. Went to 15 meters, hit Tune and SmartSDR crashed and the 8600 rebooted.

    Next, I tried powering off the TGXL, PGXL, powered down the 8600, disconnected DC power, and performed a restart on my PC. I then brought everything back up and the issue cleared.

    Everything is working today just fine.

  • Phillip Hare
    Phillip Hare Member ✭✭

    I assume DAX is set properly, and is activated?

  • NR4O
    NR4O Member ✭✭

    I'll be interested to hear if you file a ticket with Flex what response you get. BTW…What versions of firmware are you running on each of the devices?

    I'll tell you I was told to file a trouble ticket with 4O3A because Flex support thinks it's a problem with 4O3A firmware. I've gotten no response from 4O3A to my trouble ticket. Disappointed in with responses to say the least.

    At a minimum it would be nice to be able to command a reboot of the TGXL and PGXL from the apps. It would at least make it more convenient to recover from the issue.

    However, we're going to see any more bug fixes to the 3.x.x software stream if that's where the problem is. Any fixes will be in the SmartSDR Basic v4 release according to the version 3.10.15 release notes. Which is fine if that gets released sooner rather than later since there is at least one bug introduced in 3.10.10 with an API that CW and RTTY skimmers use that are not completely fixed in the 3.10.15 release that followed shortly after.

    Eric - NR4O

  • Erik Carling EI4KF
    Erik Carling EI4KF Member ✭✭✭✭
    edited October 2025

    Interlock for me (happens every time): 60mtr on 8400M, PGXL is STBY (not permissible in EI on 60m), TGXL is STBY (resonant antenna). Change to 40mtr on 8400M, PGXL still in STBY as is TGXL (resonant antenna). Interlock prevents transmission message. PGXL to OPERATE, still interlock error. Bring TGXL to OPERATE and back to STBY. No interlock now.

    With TGXL removed from line-up or in the line-up but powered off, I do not get the interlock error when changing these bands.

    I haven't deliberately tested any other band change combination but in my normal operating, and I use most bands daily, I have not had the same error as I get 60m>40m.

    When I first had the TGXL, although it prompted for a firmware update, I tested it without making that update and I did not have the interlock error. The issue started after I installed 1.2.17 and I wish I knew what FW version the TGXL came with as I would change back to it if possible but I did not make a note.

  • Mike-VA3MW
    Mike-VA3MW Administrator, FlexRadio Employee, Community Manager, Super Elmer, Moderator admin

    For CQWW this weekend, we had the odd TG interlock. Since we don't need the TG for station operation, other than as a watt meter, we put the TG in StandBy and for the next 44 hours we did not have a single interlock issue.

    I hope that helps.

  • Paul Christy
    Paul Christy Member ✭✭

    Same.

    TGXL 1.2.17 is nothin but trouble. Back to 1.2.11. Doing that I was able to run in RTTY RU. However, every half hour or so it interlocked and I had to power TGXL down and up to continue to limp along.

    But now another problem revealed itself. When I tune to a frequency, it tunes fine, but when leave it on the frequency and transmit 10 minutes later, it loses it's tuning completely and I have to retune. Then I downgraded all the way down to 1.1.20 and it seems to have gone away.

    Sounds like Erik has a similar issue.

    Gemini seems pretty certain this is the I2C issue and even gave me unit serial numbers for this known issue. Could this be it? I can't find anything about this in The Community. So is it hallucinating?

  • K1UO Larry
    K1UO Larry Member ✭✭✭

    I find that when I get the interlock and no transmit it is because the TGXL is in STANDBY. changing the TGXL to operate or bypass ALWAYS cleared the problem.

  • Phillip Hare
    Phillip Hare Member ✭✭

    I have tried each of the above stated remedies with mixed results, but the error would later rear its annoying head. However, when I downgraded the TGXL firmware to 1.2.12, (several months ago) per Tim Ellisons suggestion, all of my interlock issues went away. Current versions are: 8600M 4.1.3, PGXL 3.8.9, TGXL 1.2.12, and AG 4.1.8.

  • Paul Christy
    Paul Christy Member ✭✭

    I never put my TGXL in STANDBY. Maybe it goes there by itself? Hoping toggling STANDBY, though, will work because it's way better than powering it all the way down and back up. Still no problems using 1.1.20. So far radio silence on the I2C issue. They said I'll have to talk to the TGXL expert and possibly schedule a Paid FlexAdvantage appointment. Problem with 1.1.20 is that the ATU button on the Maestro doesn't work.

  • David Decoons, wo2x
    David Decoons, wo2x Member, Super Elmer Moderator

    Only 1.2.17 or 1.2.12 have integration with SmartSDR or Maestro.

    The integration adds more IP traffic between the radio and Tuner Genius (meter data, status, control). This extra traffic is not present on the older versions of Tuner Genius firmware. 8000 series with v4 and TG 1.2.17 seems to not have the disconnect issues.

  • Paul Christy
    Paul Christy Member ✭✭

    Roger. I have 6700 and nothing beyond 1.1.20 works on TGXL. Is this planned obsolescence or will there be a fix for me? Are you saying they expect me to get a new radio to make my Maestro work properly? The rumor I have heard is that it is the I2C system in the TGXL that's the problem. Not the radio.

  • NR4O
    NR4O Member ✭✭

    Dave, your statement about the 8000 series not having the disconnect issue is NOT correct.

    I reported on this thread back in September that I was and still having the interlock issue intermittently with my 8600, TGXL, AG, PGXL. It happens way less often when you uncheck the Enable AG integration in the TGXL.

    The first post on this thread dates back to May of 2025. It's taking an awfully long time to get this issue figured out.

    Paul, I'm curious where you've seen the rumor about the I2C system in the TGXL being implicated? In my attempts to troubleshoot the issue, capturing network traces, it appears the TGXL responds to a PTT request with an interlock response. But, there is no information about why it responds that way.

    Eric - NR4O

  • Paul Christy
    Paul Christy Member ✭✭

    This has also been plaguing my contest station for months. Helpdesk sent me an unpublished 1.2.12 but it didn't work. Google Gemini came up with the I2C thing. I think it came partly from a groups.io group? It could be hallucinating. But it's pretty specific about serial numbers and symptoms. My serial number, 2142, and symptoms match. And the 1.1.20 fix worked:

    The "I2C bus intermittent communications" problem is a known hardware-timing issue that affects earlier production runs of the Tuner Genius XL (TGXL). This issue is often masked on older firmware (v1.1.20) but causes significant instability, "No Band Data" errors, or tuning failures on newer versions (v1.2.11 and v1.2.17).

    Serial Number Range & Identification

    • Affected Units: Generally, units manufactured between 2021 (the initial release) and early 2025 are the primary candidates for this modification.
    • The "Rule of Thumb" Diagnosis: FlexRadio support treats the firmware behavior as the definitive test. If your TGXL is rock-solid on v1.1.20 but experiences crashes or communication loss on v1.2.x, your unit almost certainly requires the I2C ECO (Engineering Change Order).
    • Newer Units: Units manufactured from mid-2025 onward (roughly week 20 of 2025, or serial numbers starting with 2025 and higher) typically have this hardware modification pre-installed from the factory.

    Verifying the "I2C Issue" Range

    Keep an eye out for the first four digits. If your serial number begins with 1221 through 4824, it falls within the production window where the I2C bus stability modification (ECO) is most commonly applied.

Leave a Comment

Rich Text Editor. To edit a paragraph's style, hit tab to get to the paragraph menu. From there you will be able to pick one style. Nothing defaults to paragraph. An inline formatting menu will show up when you select text. Hit tab to get into that menu. Some elements, such as rich link embeds, images, loading indicators, and error messages may get inserted into the editor. You may navigate to these using the arrow keys inside of the editor and delete them with the delete or backspace key.

Comment As ...

Categories