Hi All
I wanted to share the devices at Sequent Microsystems.? They can give you an RPI with 8 SPDT relays rated at 10A for 120V, which is really good.
?
And, yes, you can control these with NodeRed.? Very slick.
You can never have too many dry contact relays.??
Mike va3mw
?
|
Hi All
We had a bunch of new users join yesterday thanks in part to the QSO Today Ham Radio Expo.? I think it was over 20 new members.
Welcome, everyone.
We are here to help out and even if you can just barely work with a Raspberry Pi, we have fellow Ham friends who can help guide the way.? No NOT feel intimidated?to ask even the simplest?question.??
We want to make you successful in your amateur radio node red project.
As well, we have a DMR BM TalkGroup that some have been frequenting on 30299 if you need a conversation.??
73 and welcome all,?
Mike va3mw
|
Welcome to the Node Red Ham Radio group
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 your needs. If you write a new flow please share so other users can benefit. The WiKi section has a How To on loading the OS, .Net, Node Red, and? FRStack on a Raspberry Pi. Once you have the Pi loaded you are ready to load additional nodes and flows. The readme.txt in my file folder has info on loading new nodes needed for my flows? /g/nodered-hamradio/files/wo2x%20flows/ReadMe.txtHave fun and ask questions if you need help! 73 Dave wo2x
|
The following files have been updated in
the Files area of the [email protected] group.
By: Alan Blind
Description:
Updated to add global variables to interface with the "WSJT Dashboard" flow. WSJT-X has a UDP Server that sends out a UDP broadcast containing data on the currently selected QSO and a stream of WSJT-X decoded messages. I built a Node-Red flow to receive the WSJT-X QSO UDP broadcasts and provide three outputs: 1- List of stations calling CQ, 2- Selected QSO - Call Sign, and 3 - Selected QSO - Grid Square. The UDP data string is of variable length, so the user must enter their six-digit Home Station Grid Square (i.e. mine is "EN61SW"), where indicated, to get a proper parse of the data. I used the standard WSJT-X port numbers, but if you are not using the same, you need to add your port number to the UDP listener node.
The following files have been uploaded to
the Files area of the [email protected] group.
By: Alan Blind
Description:
WSJT-X Dashboard. Displays data from "WSJT QSO Listener" and "WSJT Log Listener" Flows using Global Variables.
|
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.?
toggle quoted message
Show quoted text
On Aug 7, 2020, at 10:00 AM, Andrew Mitchell <AMITCHELL@...> wrote:
?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 your instructions or if I might be missing a module...  Perhaps you can point me in the right direction? Tks es 73 Andy VA3CW
|
Andrew. ?Add the ¡°string¡± node to you pallet.?
toggle quoted message
Show quoted text
On Aug 7, 2020, at 10:00 AM, Andrew Mitchell <AMITCHELL@...> wrote:
?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 your instructions or if I might be missing a module...  Perhaps you can point me in the right direction? Tks es 73 Andy VA3CW
|
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 your instructions or if I might be missing a module...  Perhaps you can point me in the right direction? Tks es 73 Andy VA3CW
|
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 technique is "ugly" so you should be able to make improvements when your power returns.
?My flow has three outputs:
1- List of stations calling CQ, with their Call Sign and Grid Square 2- Selected QSO call sign 3- Selected?QSO grid square
Use the WSJT UDP listener port:
The following files have been uploaded to
the Files area of the [email protected] group.
By: Alan Blind
Description:
WSJT-X has a UDP Server that sends out a UDP broadcast containing data on the currently selected QSO and a stream of decoded messages. I built a Node-Red flow to receive the WSJT-X QSO UDP broadcasts and provide three outputs: 1- List of stations calling CQ, 2- Selected QSO - Call Sign, and 3 - Selected QSO - Grid Square. The UDP data string is of variable length, so the user must enter their six-digit Grid Square (i.e. "EN61SW"), where indicated, to get a proper parse of the data. I used the standard WSJT-X port numbers, but if you are not using the same, you need to add your port number to the UDP listener node.
|
The following files have been uploaded to
the Files area of the [email protected] group.
By: Alan Blind
Description:
WSJT-X has a UDP Server that sends out a UDP broadcast containing data on the currently selected QSO and a stream of decoded messages. I built a Node-Red flow to receive the WSJT-X QSO UDP broadcasts and provide three outputs: 1- List of stations calling CQ, 2- Selected QSO - Call Sign, and 3 - Selected QSO - Grid Square. The UDP data string is of variable length, so the user must enter their six-digit Grid Square (i.e. "EN61SW"), where indicated, to get a proper parse of the data. I used the standard WSJT-X port numbers, but if you are not using the same, you need to add your port number to the UDP listener node.
|
Re: File /WSJT Log Listener.json updated
Yes it does. I use it in my rotor control flow.? <PST><QRA>CM87SO</QRA></PST> Gary K6HN
|
Re: File /WSJT Log Listener.json updated
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.
Dave wo2x Sent from my waxed string and tin cans.?
toggle quoted message
Show quoted text
On Aug 6, 2020, at 6:01 PM, [email protected] Notification <[email protected]> wrote:
?
The following files have been updated in
the Files area of the [email protected] group.
By: Alan Blind
Description:
WSJT-X uses a UDP broadcast to send log data to your Logbook. I built a Node-Red, WSJT Logbook UDP listener, and decoder. I used the WSJT default UDP port, but you may have changed it for your Logbook; if so, change the UDP Listener Port on the Node-Red UDP listener port. All variables are stored in memory as global variables, so your last WJST-X QSO will be retained in Node-Red memory and you can easily access any of the variables in any other Node-Red flow.
Change your notification settings
|
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 logbooks and now Node-Red will see the broadcast.? Use a multicast IP for your Subnet Mask, or the IP of your Raspberry Pi with Node-Red if you do not broadcast to a logbook.
The flow will store the WSJT-X variables in Global Variables, so your last QSO will be held memory.? You can access global variables using the "change" node, the same as I do on the lower half of the flow.
Here I use the Get Node to retrieve?the WSJT-X variables. ? Copy and paste any of these change nodes on any of your flows to access any of the?variables.? You must inject a timestamp?to update the variable:
Alan WA9WUD
The following files have been uploaded to
the Files area of the [email protected] group.
By: Alan Blind
Description:
WSJT-X uses a UDP broadcast to send log data to your Logbook. I built a Node-Red, WSJT Logbook UDP listener, and decoder. I used the WSJT default UDP port, but you may have changed it for your Logbook; if so, change the UDP Listener Port on the Node-Red UDP listener port. All variables are stored in memory as global variables, so your last WJST-X QSO will be retained in Node-Red memory and you can easily access any of the variables in any other Node-Red flow.
|
The following files have been uploaded to
the Files area of the [email protected] group.
By: Alan Blind
Description:
WSJT-X uses a UDP broadcast to send log data to your Logbook. I built a Node-Red, WSJT Logbook UDP listener, and decoder. I used the WSJT default UDP port, but you may have changed it for your Logbook; if so, change the UDP Listener Port on the Node-Red UDP listener port. All variables are stored in memory as global variables, so your last WJST-X QSO will be retained in Node-Red memory and you can easily access any of the variables in any other Node-Red flow.
|
The following files have been uploaded to
the Files area of the [email protected] group.
By: Alan Blind
Description:
Add these nodes to your Pi FRS "Meter" flow, if you want: 1- Station Name, 2- Station Call Sign, and 3- Flex Server IP address.
|
Re: FRStack Web APIs for RPi with FRStack Node Red Flows
Thanks, Tormod. ? This is exactly?what I did and it works great!
Alan WA9WUD
Just use mox. It goes on for both regular tx and tune when I checked yesterday.? ? Mark
I am looking at Pi FRStack for something that gives me the TX "state" of the Flex Server.? I found Tune and MOX status, but I need to combine them into one "state". ?
The Flex Server has a variable called "state" and returns "transmitting" or "ready".? I am using that now, but want to move this over to FRStack.
I looked at the FRStack "Radio Info" return, but could not find anything like this.
Can you help me find a similar data point in Pi FRStack Radio Info?
Alan WA9WUD
|
Re: FRStack Web APIs for RPi with FRStack Node Red Flows
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 will continue?to broadcast these packets, regardless.....and thus do not add any "overhead" to the system.? Node-Red is simply "listening" for the broadcast.?
I continue to use my Node-Red VITA49 UDP Broadcast "listener".
Pi FRS does have some Flex Server data available on the "Meter" flow.? Data is from the perspective of the "Active Client".? Data I found includes:
- Station - Call Sign - Flex Server IP Address
I will upload the additional nodes you need to add to your FRS "Meter" flow to see these parameters.? Just import the additional?nodes and put them on the Meter flow.?
Alan
On Fri, Jul 31, 2020 at 08:23 PM, David De Coons wo2x wrote:
I am following in Alan¡¯s steps to use FRStack for all the radio info and incorporate it into the other flows. The VITA49 and FlexRadio flows are fine if you are not going to use FRStack.
?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 in FRstack, where to get radio IP and radio Model, which I want to show in dashboard (client and radio name I got it covered).
hints?
Santiago
--
______________
73 de Santiago
HI8SMX - KB8SMX
web:?
YouTube: HI8SMX?
Twitter: @hi8smx
Instagram: hi8smx
|
Re: FRStack Web APIs for RPi with FRStack Node Red Flows
Just use mox. It goes on for both regular tx and tune when I checked yesterday.?
toggle quoted message
Show quoted text
31. jul. 2020 kl.?04:21 skrev Alan Blind <a.alan.blind@...>:
? Mark
I am looking at Pi FRStack for something that gives me the TX "state" of the Flex Server.? I found Tune and MOX status, but I need to combine them into one "state". ?
The Flex Server has a variable called "state" and returns "transmitting" or "ready".? I am using that now, but want to move this over to FRStack.
I looked at the FRStack "Radio Info" return, but could not find anything like this.
Can you help me find a similar data point in Pi FRStack Radio Info?
Alan WA9WUD
|
Re: FRStack Web APIs for RPi with FRStack Node Red Flows
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 else comes up with an answer first.
73
toggle quoted message
Show quoted text
On Aug 6, 2020, at 10:24 AM, Santiago Mejia via groups.io <hi8smx@...> wrote:
?On Fri, Jul 31, 2020 at 08:23 PM, David De Coons wo2x wrote:
I am following in Alan¡¯s steps to use FRStack for all the radio info and incorporate it into the other flows. The VITA49 and FlexRadio flows are fine if you are not going to use FRStack.
?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 in FRstack, where to get radio IP and radio Model, which I want to show in dashboard (client and radio name I got it covered). hints? Santiago -- ______________ 73 de Santiago HI8SMX - KB8SMX web:? YouTube: HI8SMX? Twitter: @hi8smx Instagram: hi8smx
|
Re: FRStack Web APIs for RPi with FRStack Node Red Flows
On Fri, Jul 31, 2020 at 08:23 PM, David De Coons wo2x wrote:
I am following in Alan¡¯s steps to use FRStack for all the radio info and incorporate it into the other flows. The VITA49 and FlexRadio flows are fine if you are not going to use FRStack.
?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 in FRstack, where to get radio IP and radio Model, which I want to show in dashboard (client and radio name I got it covered). hints? Santiago -- ______________ 73 de Santiago HI8SMX - KB8SMX web:? YouTube: HI8SMX? Twitter: @hi8smx Instagram: hi8smx
|
Re: FRStack Web APIs for RPi with FRStack Node Red Flows
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.?
Mark
|
Dave wo2x
Santiago Mejia