Re: Node Red article in QST September issue
Dave, a couple of thoughts:
1) QEX seems like a good publication for a more technical article on ham radio applications of Node-RED.
2) Have you asked the ARRL whether they'd be interested in publishing a book?
From: "David De Coons wo2x" <RocketNJ@...> To: "nodered-hamradio" < [email protected]> Sent: Friday, July 30, 2021 9:30:01 AM Subject: [nodered-hamradio] Node Red article in QST September issue
Hi All, ? Myself and Mike Walker wrote an article for QST magazine on Node Red. It will be published in the upcoming September issue. I didn¡¯t want to let the cat out of the bag until I was sure it would be published. ? Some of you may find it interesting but it is really an overview of Node Red being used in the ham radio world. It was not very technical but an overview to get more people interested. ?The ARRL has expressed interest in possibly putting a page up on their site dedicated to Node Red. ? I am also working on a project with the ARRL staff to leverage Node Red in their W1HQ station and possibly expand to the W1AW stations as well. The W1HQ station currently consist of a Flex 6600m and Power Genius XL amp at station 1, An Icom 9100 (soon to be replaced with a 9700 and an amp to be determined at station 2. Station 3 is left for any radios they want to bring in and use to test or during contests. They are using The Green Heron Everywhere server software and wireless base stations with a HamPlus 4x12 antenna switch and Green Heron RT21 controller. Jeff from Green Heron was very gracious when I spoke to him about interfacing Node Red to his GHE server. The ARRL gave me their RT21 controller to take home so I could write a flow to talk to it with Tormod¡¯s clickable azimuth map (Tormod, that is wonderful work you did!). unfortunately I have to give it back so I ordered one and received it yesterday. Already installed in my station. ? I¡¯ll be doing another trip to Newington in a couple of weeks as the W1HQ station was in the very early stages of being rebuilt. I will get pictures at that time as they should have more equipment installed then. ? 73 Dave wo2x ? ? ?
|
Node Red article in QST September issue
Hi All, ? Myself and Mike Walker wrote an article for QST magazine on Node Red. It will be published in the upcoming September issue. I didn¡¯t want to let the cat out of the bag until I was sure it would be published. ? Some of you may find it interesting but it is really an overview of Node Red being used in the ham radio world. It was not very technical but an overview to get more people interested. ?The ARRL has expressed interest in possibly putting a page up on their site dedicated to Node Red. ? I am also working on a project with the ARRL staff to leverage Node Red in their W1HQ station and possibly expand to the W1AW stations as well. The W1HQ station currently consist of a Flex 6600m and Power Genius XL amp at station 1, An Icom 9100 (soon to be replaced with a 9700 and an amp to be determined at station 2. Station 3 is left for any radios they want to bring in and use to test or during contests. They are using The Green Heron Everywhere server software and wireless base stations with a HamPlus 4x12 antenna switch and Green Heron RT21 controller. Jeff from Green Heron was very gracious when I spoke to him about interfacing Node Red to his GHE server. The ARRL gave me their RT21 controller to take home so I could write a flow to talk to it with Tormod¡¯s clickable azimuth map (Tormod, that is wonderful work you did!). unfortunately I have to give it back so I ordered one and received it yesterday. Already installed in my station. ? I¡¯ll be doing another trip to Newington in a couple of weeks as the W1HQ station was in the very early stages of being rebuilt. I will get pictures at that time as they should have more equipment installed then. ? 73 Dave wo2x ? ? ?
|
Follow the WiKi for either 32 bit or 64 bit OS. Both work on my Pi4 with 4 GB ram.?
Dave wo2x Sent from my waxed string and tin cans.?
toggle quoted message
Show quoted text
On Jul 30, 2021, at 11:34 AM, Santiago Mejia via groups.io <hi8smx@...> wrote:
?Goooooood morning all. Yes, I know, I?ve been missing in action for the past several months but I am back now. I have a Pi4 that I bought some time ago and that I hadn?t use and now whaetver OS I use it doesn?t boot up. Some people are saying that I am using an imagine for Pi3 and that should I use an image made for Pi4.
Anyone, maybe Alan or Dave has a Pi4 image with the OS, Node Red, etc...that could share?
73, Santiago
--
______________
73 de Santiago
GLAARG VE 2791E
HI8O (former HI8SMX) & KB8SM
web:?
YouTube: hamworldonline
Twitter: @hamworldonline
Instagram: hamworldonline
|
Goooooood morning all. Yes, I know, I?ve been missing in action for the past several months but I am back now. I have a Pi4 that I bought some time ago and that I hadn?t use and now whaetver OS I use it doesn?t boot up. Some people are saying that I am using an imagine for Pi3 and that should I use an image made for Pi4.
Anyone, maybe Alan or Dave has a Pi4 image with the OS, Node Red, etc...that could share?
73, Santiago
--
______________
73 de Santiago
GLAARG VE 2791E
HI8O (former HI8SMX) & KB8SM
web:?
YouTube: hamworldonline
Twitter: @hamworldonline
Instagram: hamworldonline
|
Mark that looks like the default settings.? ?In an attempt to stop the logs I set it to:
{
? "Logging": {
? ? "LogLevel": {
? ? ? "Default": "Error",
? ? ? "Microsoft": "Error",
? ? ? "Microsoft.Hosting.Lifetime": "Error",
? ? ? "Flex.Smoothlake": "None",
? ? ? "FRStackWebApi.Controllers": "None"
? ? ? }
? ? },
I just went back and changed it back to:
{
? "Logging": {
? ? "LogLevel": {
? ? ? "Default": "Warning",
? ? ? "Microsoft": "Warning",
? ? ? "Microsoft.Hosting.Lifetime": "Information",
? ? ? "Flex.Smoothlake": "Warning",
? ? ? "FRStackWebApi.Controllers": "Warning"
? ? ? }
? ? },
Now restarting FRStackWebApi see the following :
Jul 30 10:28:21 raspberrypi dotnet: Discovered 10.0.0.238 FLEX-6600: 0720-1007-6600-5639 (FM19bg 0x215ADFCE) fpc_mac:
Jul 30 10:28:21 raspberrypi dotnet: Radio: FindEqualizerByEQSelect(RX) returned null
Jul 30 10:28:21 raspberrypi dotnet: Radio: FindEqualizerByEQSelect(RX) returned null
Jul 30 10:28:22 raspberrypi dotnet: VitaSocket: Newly created on port 4991
Jul 30 10:28:22 raspberrypi dotnet: Profile List Problem!
Jul 30 10:28:22 raspberrypi dotnet: Radio: FindEqualizerByEQSelect(TX) returned null
Jul 30 10:28:22 raspberrypi dotnet: Radio: FindEqualizerByEQSelect(TX) returned null
Jul 30 10:28:22 raspberrypi dotnet: Radio Meter CODEC Signal strength of CODEC output - NO Data Ready handler
Jul 30 10:28:22 raspberrypi dotnet: Radio Meter SC_MIC Signal strength of MIC output - NO Data Ready handler
Jul 30 10:28:22 raspberrypi dotnet: Radio Meter SC_FILT_1 Signal strength after Filter 1 - NO Data Ready handler
Jul 30 10:28:22 raspberrypi dotnet: Radio Meter ALC Signal strength of signals after SW ALC (SSB Peak) - NO Data Ready handler
Jul 30 10:28:22 raspberrypi dotnet: Radio Meter PRE_WAVE_AGC Signal strength before Waveform AGC - NO Data Ready handler
Jul 30 10:28:22 raspberrypi dotnet: Radio Meter PRE_WAVE Signal strength before Waveform Shim - NO Data Ready handler
Jul 30 10:28:22 raspberrypi dotnet: Radio Meter SC_FILT_2 Signal strength after Filter 2 - NO Data Ready handler
Jul 30 10:28:22 raspberrypi dotnet: Radio Meter B4RAMP Signal strength of signals before the ramp - NO Data Ready handler
Jul 30 10:28:22 raspberrypi dotnet: Radio Meter AFRAMP Signal strength of signals after the ramp - NO Data Ready handler
Jul 30 10:28:22 raspberrypi dotnet: Radio Meter POST_P Signal strength after all processing is done but before attenuation for power control - NO Data Ready handler
Jul 30 10:28:22 raspberrypi dotnet: Radio Meter GAIN Signal strength after Gain - NO Data Ready handler
Jul 30 10:28:22 raspberrypi dotnet: Radio Meter +13.8B Main radio input voltage at CPU (continuous) - NO Data Ready handler
Jul 30 10:28:22 raspberrypi dotnet: Radio Meter MAINFAN Main radio fan RPM - NO Data Ready handler
Jul 30 10:28:22 raspberrypi dotnet: Profile List Problem!
?
-- Mick, W8BE
|
Look at your settings json file logging levels. ? ? ? "Default": "Warning", ? ? ? "Microsoft": "Warning", ? ? ? "Microsoft.Hosting.Lifetime": "Information", ? ? ? "Flex.Smoothlake": "Warning", ? ? ? "FRStackWebApi.Controllers": "Warning"
toggle quoted message
Show quoted text
On Jul 30, 2021, at 6:34 AM, Mick - W8BE <w8bea2b2c2@...> wrote: ?Dave, I upgraded to dotnet 5.0.8 this morning.? ?Same results.? ?So I did a quick test.? ?I don't think the issue has anything to do with Node-RED.? ?I stopped the Node-Red process and then restarted the FRStackWebApi.? ?Now with no Node-Red running and my radio on here is what I see in the log:
pi@raspberrypi:/usr/local/frstack $ sudo systemctl restart FRStackWebApi
pi@raspberrypi:/usr/local/frstack $ journalctl --unit FRStackWebApi --follow
-- Logs begin at Thu 2021-07-29 16:24:31 EDT. --
Jul 30 06:29:34 raspberrypi dotnet[19756]: Radio Meter LEVEL Signal strength of signals in the filter passband - NO Data Ready handler
Jul 30 06:29:34 raspberrypi dotnet[19756]: Radio Meter AGC+ Signal strength after AGC - NO Data Ready handler
Jul 30 06:29:34 raspberrypi dotnet[19756]: Radio Meter AM Signal strength after AM - NO Data Ready handler
Jul 30 06:29:34 raspberrypi dotnet[19756]: Waterfall::StatusUpdate: Key not parsed (band_zoom=0)
Jul 30 06:29:34 raspberrypi dotnet[19756]: Waterfall::StatusUpdate: Key not parsed (segment_zoom=0)
Jul 30 06:29:34 raspberrypi dotnet[19756]: Waterfall::StatusUpdate: Key not parsed (daxiq_channel=0)
Jul 30 06:29:34 raspberrypi dotnet[19756]: Slice::StatusUpdate: Key not parsed (sample_rate=24000)
Jul 30 06:29:34 raspberrypi dotnet[19756]: RXRemoteAudioStream::StatusUpdate: Invalid key/value pair ()
Jul 30 06:29:34 raspberrypi dotnet[19756]: RXRemoteAudioStream::StatusUpdate: Key not parsed (ip=10.0.0.55)
Jul 30 06:29:34 raspberrypi dotnet[19756]: ParseInterlockStatus: Error - Invalid reason (OUT_OF_PA_RANGE)
I wanted to post this test as Mark will eventually see it and advise.? Upgrading to dotnet 5.0.8 was a worthwhile endeavor.? It gave me the idea to test the FRStackWebApi with no conflicting processes.??
Regards
|
Dave, I upgraded to dotnet 5.0.8 this morning.? ?Same results.? ?So I did a quick test.? ?I don't think the issue has anything to do with Node-RED.? ?I stopped the Node-Red process and then restarted the FRStackWebApi.? ?Now with no Node-Red running and my radio on here is what I see in the log:
pi@raspberrypi:/usr/local/frstack $ sudo systemctl restart FRStackWebApi
pi@raspberrypi:/usr/local/frstack $ journalctl --unit FRStackWebApi --follow
-- Logs begin at Thu 2021-07-29 16:24:31 EDT. --
Jul 30 06:29:34 raspberrypi dotnet[19756]: Radio Meter LEVEL Signal strength of signals in the filter passband - NO Data Ready handler
Jul 30 06:29:34 raspberrypi dotnet[19756]: Radio Meter AGC+ Signal strength after AGC - NO Data Ready handler
Jul 30 06:29:34 raspberrypi dotnet[19756]: Radio Meter AM Signal strength after AM - NO Data Ready handler
Jul 30 06:29:34 raspberrypi dotnet[19756]: Waterfall::StatusUpdate: Key not parsed (band_zoom=0)
Jul 30 06:29:34 raspberrypi dotnet[19756]: Waterfall::StatusUpdate: Key not parsed (segment_zoom=0)
Jul 30 06:29:34 raspberrypi dotnet[19756]: Waterfall::StatusUpdate: Key not parsed (daxiq_channel=0)
Jul 30 06:29:34 raspberrypi dotnet[19756]: Slice::StatusUpdate: Key not parsed (sample_rate=24000)
Jul 30 06:29:34 raspberrypi dotnet[19756]: RXRemoteAudioStream::StatusUpdate: Invalid key/value pair ()
Jul 30 06:29:34 raspberrypi dotnet[19756]: RXRemoteAudioStream::StatusUpdate: Key not parsed (ip=10.0.0.55)
Jul 30 06:29:34 raspberrypi dotnet[19756]: ParseInterlockStatus: Error - Invalid reason (OUT_OF_PA_RANGE)
I wanted to post this test as Mark will eventually see it and advise.? Upgrading to dotnet 5.0.8 was a worthwhile endeavor.? It gave me the idea to test the FRStackWebApi with no conflicting processes.??
Regards
|
Alan I posted the flows under W8BE flows... If you see anything that can be made more efficient / cleaner please advise.?? Regards
|
Mick
I would be interested in looking at your "in the header" flow.? Could you post it to the files?
OK, another "clean-up"?trick.
Are you using Node-Red Projects?? If so, using the multiple select key combination, "option-click" for my Mac, on the Node-Red editor, select the tabs you absolutely?use for your "production" dashboard. ?"Export" these tabs to the clipboard.? Open a new project, import the essential tabs to the new project from the clipboard.? You will now have a "clean" set of ?"essential" flows.
If you do not use Node-Red Projects, export two versions of your flows.? Essential?tabs and everything flows, to?json files. ??
Go to the hidden ".Node-Red" directory, "/home/pi/.node-red". ? Delete or rename the "/home/pi/.node-red/flows_raspberrypi.json" file.? This will wipe your editor "clean".
Restart Node-Red.? Open up the Node-Red editor.? It should be empty.? Import your "essential" copy of flows.
You now have a "clean" Node-Red, and you are not running non-essential flows.? Now, focus on correcting each source of error messages.
Alan
|
Alan,?
Thanks for the info.? I went through and found no nodes that needed updated, no invalid, or unused nodes.? ?At this point I think Mark may have to weigh in.? ?No rush on that.? ?Regarding the toolbar I did learn that getting the solar data to work on all tabs and refresh required a client / server approach to ui_template.? ?The original ui_template that has the clock is the client side which i modifed for the solar data but I could not get all tabs to show the data and on refresh the data did not load.? ?I found out on the Node-RED forum about the server code to re post the variable so the client can fetch it.? My flow now looks like this:
Toolbar Flow - You only need one template for the client but you need to have the server update templates on at least one flow per dashboard tab.? I just linked back to the function that parses the data.? ?Seems to work well...?
Regards
|
Mick
Another Node-Red "clean up" task is to go to the list of "configuration nodes" on the hamburger pull down.? Select the "unused" tab.? Select each unused configuration and hit "delete" on the keyboard.
oh....also, on the Dashboard tool, look for empty groups and tabs.? Choose "edit" and then delete.
Regarding the time in header flow.? I am not the original code writer.? I found the "time in header" flow on the forum and knew that others in our group were looking for the same.? I was in error to not credit the source.
Alan. WA9WUD
|
Thanks Dave / Alan.? I will give the debug node a shot.? I have had debug on alot in the last few days and don't see any those errors.? They are being written to /var/log files. Alan i was looking at your clock code and I must say your write very clean code.? I was impressed.? I changed the way had my code to use <p> instead of <span>.? I was able to eliminate alot of extra code with that.? I added solar data to the toolbar.??  ? Regards
|
Mick
I cannot help with your specific log alarms.
I start by going to the Pallet?tool and finding any nodes that need to be updated.? I update each.
Re-Boot.
Then, I open a debug node on each Node-Red tab, looking for error messages.? Then, I click on the message to find the offending Node.
Then, I try to fix whatever is upsetting the node.
Repeat for each Node-Red editor tab.
Alan. WA9WUD
|
The WiKi was updated to show how to load .Net 5.0.8. Don¡¯t know if that will help.
My Green Heron RT21 just arrived and will be wiring that up. When done I wanted to build a new Pi4 using 32 bit OS. Right now using 64 bit with Node Red 1.3.5
73
toggle quoted message
Show quoted text
On Jul 29, 2021, at 5:05 PM, Mick - W8BE <w8bea2b2c2@...> wrote:
?I recently upgraded to Node-RED 2.03 and? dotnet 5.0.5.? ?I noticed I am getting error msgs like below:
Jul 29 16:55:44 raspberrypi dotnet: Radio Meter AM Signal strength after AM - NO Data Ready handler
Jul 29 16:55:44 raspberrypi dotnet: Waterfall::StatusUpdate: Key not parsed (band_zoom=0)
Jul 29 16:55:44 raspberrypi dotnet: Waterfall::StatusUpdate: Key not parsed (segment_zoom=0)
Jul 29 16:55:44 raspberrypi dotnet: Waterfall::StatusUpdate: Key not parsed (daxiq_channel=0)
Jul 29 16:55:44 raspberrypi dotnet: Slice::StatusUpdate: Key not parsed (sample_rate=24000)
Jul 29 16:55:44 raspberrypi dotnet: RXRemoteAudioStream::StatusUpdate: Invalid key/value pair ()
Jul 29 16:55:44 raspberrypi dotnet: RXRemoteAudioStream::StatusUpdate: Key not parsed (ip=10.0.0.55)
Jul 29 16:55:44 raspberrypi dotnet: ParseInterlockStatus: Error - Invalid reason (OUT_OF_PA_RANGE)
Jul 29 16:56:10 raspberrypi dotnet: ParseInterlockStatus: Error - Invalid reason (OUT_OF_PA_RANGE)
I loaded up a new pi with dotnet 5.0.3 and the latest Node-Red / FRStack and still see the errors.? I then loaded Mark's json to test and? see if something in my flow could be the issue but I see the same errors using the Mark's json.? ?I see the same errors using his flows as well.? ?I am curious if anyone has notice this.? ?I have not lost any functionality, I just don't like to see errors eating up cpu ticks to post a message to /var/log.? ?
Regards,
Mick
?
|
I recently upgraded to Node-RED 2.03 and? dotnet 5.0.5.? ?I noticed I am getting error msgs like below:
Jul 29 16:55:44 raspberrypi dotnet: Radio Meter AM Signal strength after AM - NO Data Ready handler
Jul 29 16:55:44 raspberrypi dotnet: Waterfall::StatusUpdate: Key not parsed (band_zoom=0)
Jul 29 16:55:44 raspberrypi dotnet: Waterfall::StatusUpdate: Key not parsed (segment_zoom=0)
Jul 29 16:55:44 raspberrypi dotnet: Waterfall::StatusUpdate: Key not parsed (daxiq_channel=0)
Jul 29 16:55:44 raspberrypi dotnet: Slice::StatusUpdate: Key not parsed (sample_rate=24000)
Jul 29 16:55:44 raspberrypi dotnet: RXRemoteAudioStream::StatusUpdate: Invalid key/value pair ()
Jul 29 16:55:44 raspberrypi dotnet: RXRemoteAudioStream::StatusUpdate: Key not parsed (ip=10.0.0.55)
Jul 29 16:55:44 raspberrypi dotnet: ParseInterlockStatus: Error - Invalid reason (OUT_OF_PA_RANGE)
Jul 29 16:56:10 raspberrypi dotnet: ParseInterlockStatus: Error - Invalid reason (OUT_OF_PA_RANGE)
I loaded up a new pi with dotnet 5.0.3 and the latest Node-Red / FRStack and still see the errors.? I then loaded Mark's json to test and? see if something in my flow could be the issue but I see the same errors using the Mark's json.? ? ?I am curious if anyone has notice this.? ?I have not lost any functionality, I just don't like to see errors eating up cpu ticks to post a message to /var/log.? ?
Regards,
Mick
?
|
Re: File /wo2x flows/Kenwood CAT to relay example.json uploaded
#file-notice
Read the comment node for info on replacing the inject and TCP Request nodes with a USB request node for your usb to serial adapter (Kenwood radio CAT needs to connect to the Pi.) If you need to share Kenwood CAT with other programs then you can take the Kenwood CAT payload and send back to a PC.
Think of Node Red as a flow chart. Input data, pass it to next node, do something with dat, pass it along, do something, etc.
Do Google searches for example Node Red flows, especially for Home Automation. They will give you an idea on how Node Red works. It is very easy once you start playing around. There are plenty of flows in the file section which will give ideas on how to accomplish a number of things.
73
Dave wo2x
toggle quoted message
Show quoted text
On Jul 29, 2021, at 2:52 PM, Dave / NR1DX <manuals@...> wrote:
?David
thanks ...... I'll send another thankyou once I figure out how to load this into my node-red library and what it all means ... 8^)
I finally found a good beginners tutorial <Workshops.opto22.com> which helped me a lot. Though I usually dislike U-Boob videos this kid's Midwest accent was flat enough and his voice had enough bass for my 160M static damaged ears to understand
Thanks again as this sounds exactly what I was going to try and do
Cheers
Dave
On 7/29/2021 11:41 AM, [email protected] Notification wrote:
The following files have been uploaded to the Files area of the [email protected] group.
* /wo2x flows/Kenwood CAT to relay example.json
</g/nodered-hamradio/files/wo2x flows/Kenwood CAT
to relay example.json>
*By:* David De Coons wo2x <RocketNJ@...>
*Description:*
Read the Comment node for information. An example of how to take Kenwood CAT and give a numerical output for each band that can be used to drive relays (GPIO, external relay module, etc)
--
Dave Manuals@... www.ArtekManuals.com
--
This email has been checked for viruses by Avast antivirus software.
|
Re: File /wo2x flows/Kenwood CAT to relay example.json uploaded
#file-notice
David
thanks ...... I'll send another thankyou once I figure out how to load this into my node-red library and what it all means? ... 8^)
I finally found a good beginners tutorial <Workshops.opto22.com> which helped me a lot.? Though I usually dislike U-Boob videos this kid's Midwest accent was flat enough and his voice had enough bass for my 160M static damaged ears to understand
Thanks again as this sounds exactly what I was going to try and do
Cheers
Dave
toggle quoted message
Show quoted text
On 7/29/2021 11:41 AM, [email protected] Notification wrote:
The following files have been uploaded to the Files area of the [email protected] group.
* /wo2x flows/Kenwood CAT to relay example.json
</g/nodered-hamradio/files/wo2x flows/Kenwood CAT
to relay example.json>
*By:* David De Coons wo2x <RocketNJ@...>
*Description:*
Read the Comment node for information. An example of how to take Kenwood CAT and give a numerical output for each band that can be used to drive relays (GPIO, external relay module, etc)
-- Dave Manuals@... www.ArtekManuals.com
--
This email has been checked for viruses by Avast antivirus software.
|
I just looked at all the tools on Github...Looks like it's SmartSDR for linux...Have you run flexclient and all the other tools on a linux device?? I am thinking this can't run on a pi effectively.??
Regards
Mick
|
The following files have been uploaded to
the Files area of the [email protected] group.
By: Alan Blind, WA9WUD <a.alan.blind@...>
Description:
DAX / CAT Flow with MQTT. You can only have one instance of the Node-Red, "exec", and it must be installed on the same device running nDAX & nCAT. This flow allows you to install the flow on a second, or more, devices, to control the "exec" Node from multiple devices. Remember, on the "Remote" devices, disable or remove the Node-Red "exec" Nodes.
The following files have been uploaded to
the Files area of the [email protected] group.
By: Alan Blind, WA9WUD <a.alan.blind@...>
Description:
nCAT and nDAX Install Steps. The steps are also included on the Node-Red flow, "Settings".
|
File //Node-Red DAX and CAT/nDAX nCAT.json updated
#file-notice
The following files have been updated in
the Files area of the [email protected] group.
By: Alan Blind, WA9WUD <a.alan.blind@...>
Description:
Cleaned up Flow and moved to a new file location.
Node-Red Flow DAX and CAT on Linux Machine with Dashboard Controls. Uses KC2G nDAX and nCAT. Install instructions are included on the Flow, "Settings" section.
|
Dave wo2x
Santiago Mejia