Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Nodered-Hamradio
- Messages
Search
Re: node-red forwarding UDP 4992 packets
Make sure both your Go script and the UDP node in NodeRed have the SO_REUSEPORT option selected/enabled for the UDP server. Otherwise only one UDP server will get the incoming datagrams.
In NodeRed, it¡¯s a checkbox on the udp in node. I think it¡¯s on by default. Here¡¯s an example for go (since v1.11) ¡ª? Stephen [edit] MQTT is a great alternative option and a really nice way to manage messages and control. |
Re: node-red forwarding UDP 4992 packets
Tommy I have two ideas. On the UDP out node (re-broadcast), try a unicast IP, "224.0.0.1". If that?doesn't work, I suspect your router or windows firewall?is blocking the broadcast.? I cannot help too much there, but: Try installing Node-Red on the Client Windows PC, and use the loopback IP, "127.0.0.1" or "localhost" as your UDP out IP address.? This way, the packet does not have to go through a router or windows firewall. Here are the instructions for installing Node-Red on windows: Alan. WA9WUD |
Re: node-red forwarding UDP 4992 packets
Also, I tried broadcasting on the receiver side using both 192.168.86.255 and 255.255.255.255 as the IP address, but that makes node red puke.? The udp node errors out when I do that.? And apologies for the repeat mesg.? I tried to delete one of my flows and reupload a corrected one and ended up deleting the entire msg on groups.io. Oops.
Tommy |
Re: node-red forwarding UDP 4992 packets
It took me a half hour or so of watching videos and reading about what MQTT is, but once that registered this was easy to set up.? Except I can't get the windows client to see the discovery packets.? I installed Mosquitto, put the sender flow at the radio, the receiver on the client network side and using the flexradio-discovery node I can discover the radio on the pi at the client side just fine.? I changed udp out node to point to 192.168.86.17 (the windows PC with the client) instead of localhost hoping to see the radio pop up in available radios in the client, but no joy.? I captured traffic on the client PC and can see those UDP 4992 packets making it to the PC.? They look fine enough (I think), but the client isn't picking them up.? Am I missing something?? It seems like what I thought would be hard (the MQTT stuff) was super easy and now the last easy bit has me stumped.? Alan, your instructions were incredibly helpful, especially the bit about the mosquitto broker.? I just imported your example flow and used those pieces, changing IPs where necessary.
I attached my receiver and sender flows and a packet trace if those are of any help.? Any ideas what I'm doing wrong?? You'd think that if it works with the flexradio-discovery node that it would work just fine with the client.? I must be munging something somewhere. |
Re: Panadapter!
#node-red-contrib-flexradio
toggle quoted message
Show quoted text
On Jan 1, 2022, at 3:44 PM, Stephen Houser, N1SH <stephenhouser@...> wrote:
-- Nick W7NIK? |
Re: node-red forwarding UDP 4992 packets
I can put Node Red on the other side of the VPN without a problem.? I'll probably find another use for it here, for that matter.? I'll watch some of those videos and see if I can wrap my head around it.? I now have about 2 days of Node Red under my belt, but maybe I can handle this with your flows and explanations.? Thank you!
|
Re: Panadapter!
#node-red-contrib-flexradio
Meant to include an updated video. Been playing with the "look" of the panadapter with SVG/D3js. I'm better at code than I am visuals :-)
|
Re: Panadapter!
#node-red-contrib-flexradio
For the really brave, this version (v1.1.0-beta.1) is on NPM in "prerelease" state along with an example flow. The example flow requires the dashboard nodes as well. The example is under "Import > Examples".
To install, from a command line or terminal in your NodeRed spot (where the node_modules is located): ? ? `npm install node-red-contrib-flexradio@prerelease` If you don't know what that does or where to do it, you are probably better off waiting for the general release. NOTE: I have not updated the documentation and there's a bunch of loose ends. I had to make a few changes to the larger code so there might be subtle differences from the v1.0 version. Also, not sure how well it will handle multiple panadapters yet. This is early days for this feature. Oh, daxAudio is in there as well. Just no good way to get it to the dashboard. Stephen, N1SH |
Re: Panadapter!
#node-red-contrib-flexradio
WOW, Very impressive.? This can actually be a game changer for all those who wanted a Linux SSDR client.? Can't wait for more.? Thanks so much.
|
Re: node-red forwarding UDP 4992 packets
Tommy
You asked on FaceBook, "?Does this mean you need node red running in both location" Yes, you?must have Node-Red on both ends. ?The MQTT Broker, is the common key connecting the two?separate networks together. "I do not understand MQTT?" Here is a link to a number of videos on MQTT and Node-Red Alan |
Re: node-red forwarding UDP 4992 packets
Tommy
Easy to do in Node-Red, using UDP in/out nodes and MQTT Broker as the TCP engine to cross networks. I use Mosquito MQTT as the broker, installed on the same Raspberry Pi running Node-Red. ?You can put the MQTT broker anywhere, on either end of the sender/receiver link......just adjust the IP address to point the MQTT nodes to the broker's device IP. ?MQTT will move the discovery packet, between devices (networks) via TCP. ?Use your favorite VPN to connect to the MQTT broker, from each end. ?I use Tailscale. My demonstration flow is attached. ?Since the UDP Sender and UDP receiver are on the same flow, I changed the port number on the Receiver to rebroadcast the Flex Discovery packet on port 5992. ?Change the port to 4992, on the receiver re-broadcast after you put this portion on the other network. I used Stephen's Flex Discovery node, as a proxy to show the Flex UDP packet is successfully moved between the transmitter to the other network receiver/re-broadcast. Flow is attached and screen shot below. Alan ? WA9WUD |
Projects and GitHub Issues
With a few projects I'm working on, it's probably time for me to setup a GitHub repository so I can post code and get some feedback and development help from others in a more structured way....but I'm having trouble setting my account up.
I've setup my SSH keys (I think I have them setup correctly).? I went through the github instructions on how to setup my public key and upload that to github.? After doing that, I was able to see my remote project on GitHub with the correct description.? Before that was not working correctly.? ?I don't have anything on my Github page repository, and would like to push my current project to the repository but I'm getting the error below. This is the error I get. I'm not really sure why it's looking for ___default_GitHub?????? Thoughts? Kyle AA0Z |
Re: LDG 1000 pro II
As promised the attachment is my LDG flow.? See the comments in the flow for details on setup.? The flow uses the node-red-node-serialport v0.15.0 to communicate with the tuner via USB serial adapter.? It should be added to your node palette before loading the flow.? I also attached the _MeterProtocol.pdf that is the reference I used to create the flow.?
Cable interface document: 73 and Happy New Year, Eric - NR4O |
node-red forwarding UDP 4992 packets
My Flex 6400 lives on the other side of an L3 site-to-site VPN.? I use a small script written in go to forward the UDP discovery packets from the radio to the other side of the VPN where I live. Since that app listens on 4992, node-red won't find any radios while it's running since node-red and the go script are running on the same raspberry pi.? I can either use that script or use node-red, but not both (at least as I have been able to determine).? If I stop the script my very basic flows work just fine. When I was setting this up someone mentioned using node-red to forward those discovery packets over the network, but I can't find any reference to how one would do that.? Can anyone point me in the right direction for accomplishing this??
Thanks, Tommy WZ4M |
Re: Restarting my Pi.
If node-Red is running and If your relays are using a usb FTDI serial port?
Unplug the USB cable and wait a minute and plug it back in the Pi should rediscover the com port if the COM port is changed you will have to go back in and select the correct COM port in the FLOW Oh make sure the relays have DC power? Sent from Gmail on my IPad
-- YMMV 73 Bret WX7Y |
Re: Restarting my Pi.
toggle quoted message
Show quoted text
On Jan 1, 2022, at 12:22 PM, Edward Dowdy <ka9ees@...> wrote:
|
to navigate to use esc to dismiss