Dave et al,

?? I’m running node-red on a Raspberry Pi. I have a Flex6600M, PGXL and TGXL. Everything works well except: If I power down the Pi and then power it on again, it throws an error for the TCP node in the TGXL flow. The only way it will fix itself is if I power down the TGXL and power it on again. Occasionally the TGXL utility on Windows will also exhibit this behaviour, but not consistently like power cycling the Pi. I’m wondering if node-red needs to ping the TGXL to initiate some output from it. Any clues guys?

73, Les VE3NNT

Hi Les,

?

It is actually working as designed. I will explain.

?

The Node Red server as I have designed the VITA49 and Flex Radio flows is designed to be running 24x7 and be running before a SmartSDR client connects (SSDR for Win, Maestro, SSDR for IOS, or MAC). If you reboot the Pi, then disconnect your client to the radio and reconnect, it will work.

?

Now, why did I do this? We found if you send TCP commands to the radio while it is transmitting will cause “popping” in the TX audio. You can hear it on SSB, see it in waterfall on FT8 and mangled CW character(s). The FlexRadio flow only sends the subscribe TCP commands when the client first connects. I used to send them every 5 seconds and wondered why I had the popping on FT8. Took a while to figure it out.

?

I could probably look at client connected global variable and wait 10 seconds. If Client Connected does not equal 1 I could have it send the sub commands again. Let me see if that would be feasible.

?

73

Dave wo2x

?

?

I’ve re-read your message Les. I am testing this now. I do not think it is a FlexRadio flow issue.

?

Standby ?

?

Dave wo2x

?

?