开云体育

Welcome to all the new users! The purpose of this group is to share and collaborate ideas and flows for Node Red. There are flows from users in the file section which you can use, edit, and adapt to

The following files have been updated in the Files area of the [email protected] group. * /WSJT QSO Listener.json ( /g/nodered-hamradio/files/WSJT QSO Listener.json ) *By:*

Note on variable packet length. The QSO grid is always just right of your station grid, so you must enter your grid as shown to set the parse starting position. Alan

Andrew. Add the “string” node to you pallet. Alan

Hi Alan, Thanks for pulling this together.? I had been hacking away at something similar to no avail - I couldn't manage the variable length message. That said, I'm wondering if I've misunderstood

I have uploaded my flow for listening to the WSJT-X UDP Server. This broadcast contains a variable-length packet of QSO data. *Note to the "Parsing Wizard of the Stormy North East", Dave, my parsing

The following files have been uploaded to the Files area of the [email protected] group. * /WSJT QSO Listener.json ( /g/nodered-hamradio/files/WSJT QSO Listener.json ) *By:*

Yes it does. I use it in my rotor control flow. <PST><QRA>CM87SO</QRA></PST> Gary K6HN

Just an idea. PSTRotator has the ability to turn the antenna by entering the grid square. I wonder if the USP server in PSTRotator allows control via grid square? I’d test but still out of power

Here are more details on the WSJT-X Listener / Decoder; In the WSJT "Reporting" settings, set up your IP and Port numbers as follows: Note: I use the multicast IP address for my subnet so all of my

The following files have been uploaded to the Files area of the [email protected] group. * /WSHJT Log Listener.json ( /g/nodered-hamradio/files/WSHJT Log Listener.json )

The following files have been uploaded to the Files area of the [email protected] group. * /Flex Info Nodes.json ( /g/nodered-hamradio/files/Flex Info Nodes.json ) *By:* Alan

Thanks, Tormod. This is exactly what I did and it works great! Alan WA9WUD [email protected]> wrote:

Santiago and others, re VITA49 Broadcast Data on Pi FRS I do not see the VITA49 UDP broadcasts from Flex Server Port 4992 available on Pi FRS. I do not see that as an issue because the Flex Server

Just use mox. It goes on for both regular tx and tune when I checked yesterday. -- Tormod

I will check but I do not know if you can send a REST command to FRStack to interrogate the radio. I am without power here (2nd day after the storm). Once I get power back I can check unless someone

Dave, good morning. FRStacks flows are still running fine on my Pi3, so I postponed buying the Pi4 a few weeks. I already disabled Flexradio flow and looking to dissable VITA49, but I have not found

There is no INFO method today for SPE apis but I can add one. As far as CPU usage, To reduce overhead use the?Node RED?Disable feature to stop the portions of the FRStack flows you are not using.

Hi, Is there a way to request all SPE reports in one command or do I need to run them all separately? Thanks to Mark for all the work on FRStack and now the ability to integrate it all. I have both

The version of Node Red included with Rasbian is an older version. The script referenced in the WiKi will install the latest version. Dave wo2x Sent from my waxed string and tin cans.