开云体育

Hi All, For anyone getting started with Node Red, first check out the WiKi to get your Pi loaded with an OS and Node Red. Next, check out these videos that Andy, VA3CW found on YouTube. The videos will help you to start using Node Red. https://www.youtube.com/results?search_query=opto22+node+red In the files section in this group there are plenty of flows to get you started. If you use a Flex 6000 series radio you can load my VITA49 and FlexRadio flows. I am modifying the FlexRadio flow shortly to automatically detect the model number of your radio and set the meter subscriptions accordingly. Please look for a read.me file in each file folder which describes any node dependencies and any other info required for those flows. A note to people who have uploaded flows - Create a folder with your callsign then upload your flows to that folder. Create a read.me file with Notepad or other text editor listing any extra nodes that you have installed for your flows. This will help new users to get up and running. I can assist in moving previously uploaded flows from the main file folder to your callsign folder. If there is anything else you can think of to help please let me know. 73 Dave wo2x

Thought I'd share some my experiences with setting up the ser2net service on my raspberry pi to act like a USB/serial to network media converter. I installed the ser2net service with one command : sudo apt-get install ser2net The config file is located at /etc/ser2net.yaml. I removed almost all of the default config and started from scratch. If you do this, save the original with sudo cp /etc/ser2net.yaml /etc/ser2net.yaml_old. %YAML 1.1 --- # This is a ser2net configuration file, tailored to be rather # simple. # # Find detailed documentation in ser2net.yaml(5) # A fully featured configuration file is in # /usr/share/doc/ser2net/examples/ser2net.yaml.gz # # If you find your configuration more useful than this very simple # one, please submit it as a bugreport define: &banner \r\nser2net port \p device \d [\B] (Debian GNU/Linux)\r\n\r\n admin: accepter: tcp,8000 connection: &nr8001 accepter: tcp,8001 enable: on connector: serialdev, /dev/ttyACM0, 38400n81,local connection: &nr8002 accepter: tcp,8002 enable: on connector: serialdev, /dev/ttyACM1, 38400n81,local Let's break down one of the serial to network configs connection: &nr8001 - this is the name of the connection. I used nr for Node Red and the port number accepter: tcp,8001 - this is what protocol to listen on the network side and what port number to use to make a connection to the connector. In the example, it's listening on tcp port 8001. enable: on - this is to enable connections connector - this is the other side of the connection - serialdev - specifying a serial device - /dev/ttyAMC1 - this is the path to the device (I would substitute the full path here, check Dave WO2X's video on how to find the full ID path) - 38400n81 - this is the speed, baud rate, polarity and stop bits - local - specifying the device is local The man page for ser2net calls out all the different connection types (there is a lot). There is bug in the bullseye distribution Raspberry Pi config and sometimes the ser2net starts up before the networking starts up, so we need to add the following lines in the /lib/systemd/system/ser2net.service file Add these two lines in the [Unit] stanza After=network-online.target Wants=network-online.target pi@elayerrack:/lib/systemd/system $ more ser2net.service [Unit] Description=Serial port to network proxy Documentation=man:ser2net(8) After=network-online.target Wants=network-online.target [Service] EnvironmentFile=-/etc/default/ser2net ExecStart=/usr/sbin/ser2net -n -c $CONFFILE -P /run/ser2net.pid Type=exec Restart=on-failure [Install] WantedBy=multi-user.target pi@elayerrack:/lib/systemd/system $ After your done editing all the files, restart the service with sudo systemctl restart ser2net.service or sudo service ser2net restart. Issuing the command netstat -l will show you all the ports your Pi is listening on. Look for the TCP ports specified in your ser2net.yaml config file. You should see something like the below (but more output). Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp6 0 0 [::]:8002 [::]:* LISTEN tcp6 0 0 [::]:8001 [::]:* LISTEN tcp6 0 0 [::]:8000 [::]:* LISTEN Active UNIX domain sockets (only servers) Now you can replace the serial nodes with TCP nodes. For example. There is a downside. It's a 1:1 communication path to network to serial device, or at least my experience is every device I've tried. Unless that's an advanced setting within the connection config in the yaml file, once a device is communicating through the ser2net service via TCP, no other devices can communicate to that serial device. Troubleshooting : if you telnet into port 8000 (the admin port) you can monitor the TCP or serial side. Be aware anything you type will be echoed out to the screen. Typing help at the command prompt will get you a list of commands. 73 Kyle AA0Z

I am pleased to release a major upgrade to my Solar weather flow -- Solar 2.0. On the surface, it doesn't look all that different than the 1.x flow, but under the hood it has been completely rewritten from the ground up. There are numerous enhancements, but the star of the show is that you no longer have to average the data from nearby ionosondes to get an estimate of MUF and foF2 for your QTH. Instead, I am now doing a direct lookup of MUF and foF2 for your QTH based on the sophisticated interpolation that Andrew Rodland, KC2G, is doing on his excellent web site https://prop.kc2g.com/about/. I reached out to Roland a couple of months back and he graciously agreed to make an API available that will take your latitude and longitude (or Maidenhead grid) and return an estimate of MUF and foF2 for that location. This is much more robust because it does not rely on nearby ionosondes being active to do the estimate and Roland's interpolation routine is more sophisticated that what I was doing. This API works anywhere on the planet and does not require you to maintain a list of ionosondes. Thanks to Roland for this excellent resource. Keep in mind that the MUF you will see is directly overhead at your location, not necessarily the MUF along a path between you and a distance station. Since we no longer need to display the status of nearby ionosonde's, I repurposed that space for displaying recent X-ray flux data in the form of peak solar flare intensity over the past 24 hours (left number) and 2 hours (right number). In the screenshot shown, the maximum flare in the past 2 hours was a C5.4 classification. This was also the largest flare in the past 24 hours, so the two numbers are the same in this example. The solar flare classifications and the color scheme I am using throughout the flow can be found here: https://www.swpc.noaa.gov/noaa-scales-explanation I have updated all of the readings (other than MUF and foF2) so that they now pull data from NOAA instead of 3rd-party sources. All of the displays have been modified such that the color scheme and thresholds match NOAA standards (as best as I could determine). The space weather conditions R, S, and G (as defined in the link above) have also been rewritten, particularly what is displayed for the "Predicted" values. This one has always been tough, since the NOAA does not predict precise values for R and S, instead giving a range of probabilities. This is difficult to display in the space allotted. In the new flow, I do a better job of representing this information. The display for predicted R can be R0, R1/2, R2/3, or R3/5. For example, if R1/2 is displayed that means the most likely peak R value in the next 24 hours will be R1 or R2. NOAA provides less granularity for the S prediction so the two possible values are S0 or S1/+, the latter meaning that the most probably S value in the next 24 hours will be S1 or above. For both R and S predicted values, the display is further color coded to represent the expected intensity. The headings for all of the fields (except for the gauges) are clickable and will take you to a web site with more information about that measurement. As always, check out the README node for information about how to use the flow. In particular, you have to set up some environment variables with your latitude and longitude, otherwise you will be getting the MUF and foF2 for my location instead of yours. If you don't want the header "Solar Conditions", just delete the Solar Title node. This flow was developed and tested with Node-RED 4.0.2, but it should work fine with 3.x. 73, Scott AK5SD

Hi, Does anyone have a copy of the ToolbarSolarWxLightningUtcClock.json flow created by Mick, W8BE? It's not available in the files section anymore... Original link: /g/nodered-hamradio/files/w8be/ToolbarSolarWxLightningUtcClock%20.json Thanks Craig, M1FDS

I am currently using as modified ( I added some things) version of Wo2x flows to control my station. I am modifying my antenna system which will have a StepIR Big IR Vertical and a Urban Beam. I expect to have the Vertical up in a week. Overall I will have 3 antennas with overlapping frequency coverage. I have a 8600, TGXL, PGXL, and a 8x2 AG. My understanding is the StepIR tracks frequency from the 8600 which means they track regardless of what Antenna I selected in the AG. Is that correct? If that is the case I want to add the SteppIR flows so that they only track the frequency when selected by the AG. Thanks, Tim wa5yom

I wanted to make sure I understand how this will work before I commit to trying it as I just got my NR all swapped over to a new Pi. I admit it would be nice to have one less program running on my PC. If I chose to run FR Stack on my RaspberryPi instead of on my shack PC then can I still VNC into the Pi and adjust settings in FRStack with a graphical interface? Reason I ask is the default FRStack settings for PGXL limit drive power to 50w and it needs to be changed. I'm assuming this would still allow me to run my StreamDeck Rest commands because they'd be sending those to the Pi instead of the shack PC yes? Anyone who is running FRStack on a Pi I'd love to hear your experiences. I have no particular issues with it running on my PC, but I love the idea of having one less program running in the background on the PC.

I have been working on a flow to adjust the AGC Threshold setting automatically. I followed Tim's paper on the topic: https://www.flexradio.com/videos/flex-6000-receiver-tuning-how-the-agc-t-works/ Here is a link to a You-Tub of the latest version of the flow in action: https://www.youtube.com/watch?v=vQ5BYy0nlM8 We have a group of "testers" giving suggestions on how to fix bug reports. I will upload the flow in a few days. Alan. WA9WUD

Hi I do not own a flexradio but I am helping VA2UR with his remote contest station. We want to capture the current transmit band , before starting transmission if possible. I am able to capture the transmit frequency when he transmits by subscribing to "sub tx all" and I get messages like this one: {"freq":14.20884,"lo":200,"hi":2900,"tx_filter_changes_allowed":1,"artopic":"transmit","ardate":"2025-03-29 14:47:29"} Ignore the last 2 fields (artopic and ardate, I added those. This tells me in real time the transmit frequency but we would like to know the selected band before tx happens to automatically adjust filters, etc I do not own or operate the flexradio myself so I am doing this a bit blindfolded. Thanks Patrick VA2ARZ

Thought I'd give some input on this. I just upgraded my Pi4 16GB to a Pi5 16GB. This is a dedicated Pi running only NR off of a 64GB card. I have 24 separate flows going on in my dashboard so I'd say I'm a fairly decent judge of performance. Previously I was cycling between 15-45% CPU usage on the Pi4. Now I'm between 5-15% with the same flows. Performance difference is very evident. Reboots are 5x faster. I did do a fresh install on the Pi5 of NR and just imported my flows. Took a little bit to get all my nodes back, but overall the process wasn't too bad. So if you're a fairly intensive NR user I can genuinely say that even if you're not pegging the CPU usage on the Pi4 you will notice a nice performance increase going to the Pi5

I have two different relay boards with ethernet ports. One I have working fine using the modbus-flex-getter and the modbus-flex-write. The manual is good enough that I even understand how it works. The other however seems to connect OK but always says "timed out" in Node-red when I try and send to or read from it. The relay device however does show as connected in the device relay web-server. I'll start with what I think is a simple question at my level of understanding. If I want to turn all relays on (12 of them on the board). The rather poor manual says I need to send 01 06 00 00 07 00 8B FA. If I do this using NetAssist to the required IP and port, it works. What I need to know is what to fill in in the function node preceding the modbus-flex-write node. So I understand that the string above is as follows; msg.payload = { 'value' :xxxx, (I don't know what should be entered in here in decimal to represent the 07 00 hex pairs above.... I know it needs to be a decimal number) 'fc' : 6, (function codes which should be 06 as the 2nd hex pair) 'unitid' : 1, (first byte of the hex string above being the unit ID, which I've checked is set to 1 on the board) 'address' : 0, ( I am guessing this should be 0 to reference the register 00 00 being the 3rd and 4th hex pairs above) 'quantity' : 2 (is this the number of data bytes? and if so what do I enter for the hex string above?) }; return msg; I am ignoring the 8B FA as that is just the crc and is not needed as far as I understand it in MODBUS TCP Or, am I understanding the hex string content incorrectly? I've attached the MODBUS programming manual to aid somebody in helping how I should address this relay board. The other relay board that works is made by Dingtian and they provided worked Node-Red examples. Those examples do not work with the board I'm having trouble with. All the hex strings in the manual work OK if I connect to it as a MODBUS client with NetAssist, so in that sense I can send and receive data from the board. Just for clarity everything is on the same private subnet. The MODBUS relay board is set up as TCP Server on a private IP of 192.168.0.42 port 10502. I have two node red instances, one on a Synology server at 192.168.0.21 and a Pi on 192.168.0.132. Both just say "node timeout" when sending anything from the MODBUS Node-Red flex-Writer or trying to trying to read status with the flex-getter. However, the bytes received count on the webserver of the Relay board increases each time I try and read or write. The bytes sent however always remains at zero so the board is seeing the incoming data but not acting on it or sending anything back to Node-Red. Any help would be appreciated. Sorry, the snipping tool seems to change the colours a bit but basically, it is an inject node followed by a flex-write node followed by the modbus response node. The latter never shows anything which is no surprise given that the board is not sending any return data. 73 G8PFR Mike