Standard Flow Outputs from Flex/FR Stack
Just a thought I had driving to work today, it would be nice (and easy) to have somewhere in the Flex flow or a dedicated flow (like the Flex meters flow were all the meters are kept) were all the parameters that potentially need to get pushed over to another flow in one place.? Does that make sense?
This way if a Flex radio flow changes, those outputs (PTT, frequency, mode, slice, antenna selected, etc) are all in one location, constant and are named.? Sometimes I find myself trying to find where I grabbed the PTT on/off because there are 3 different locations where you could get it.??
Just a thought here...
Kyle
AA0Z
|
Perfect. Thanks Alan. I am very familiar with the whole UDP interface as I had to program it from scratch to add it to TR4W (another contest logger). I send the same UDP messages from TR4W that N1MM sends.
Glad to hear some are already using it. Will start with these flows.
Thanks to you both (Dave and Alan).
73,
toggle quoted message
Show quoted text
Tom
N1MM has a lot of data available?from UDP broadcasts.? Several of us have used portions to drive various functions.? Node-Red handles this well.
Here is a flow to illustrate parsing N1MM UDP data from the "radio info" broadcast.? You will need to configure the UDP Port in N1MM and the flow to agree, for "radio info".
Alan
[{"id":"723d811b.88a7d","type":"tab","label":"Flow 1","disabled":false,"info":""},{"id":"4c4abb17.5a29cc","type":"debug","z":"723d811b.88a7d","name":"","active":false,"tosidebar":true,"console":false,"tostatus":false,"complete":"payload.RadioInfo.FocusRadioNr[0]","targetType":"msg","statusVal":"","statusType":"auto","x":600,"y":180,"wires":[]},{"id":"b9ef1965.2222c8","type":"udp in","z":"723d811b.88a7d","name":"","iface":"","port":"12075","ipv":"udp4","multicast":"false","group":"","datatype":"utf8","x":160,"y":260,"wires":[["8a5b4a27.e60da8"]]},{"id":"8a5b4a27.e60da8","type":"xml","z":"723d811b.88a7d","name":"","property":"payload","attr":"","chr":"","x":350,"y":260,"wires":[["4c4abb17.5a29cc","26c3afcd.56c5b","b32c1126.85901","9308404a.02014"]]},{"id":"26c3afcd.56c5b","type":"debug","z":"723d811b.88a7d","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"payload.RadioInfo.ActiveRadioNr[0]","targetType":"msg","statusVal":"","statusType":"auto","x":640,"y":280,"wires":[]},{"id":"b32c1126.85901","type":"debug","z":"723d811b.88a7d","name":"","active":false,"tosidebar":true,"console":false,"tostatus":false,"complete":"payload.RadioInfo.IsTransmitting[0]","targetType":"msg","statusVal":"","statusType":"auto","x":620,"y":400,"wires":[]},{"id":"9308404a.02014","type":"debug","z":"723d811b.88a7d","name":"","active":false,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","statusVal":"","statusType":"auto","x":420,"y":80,"wires":[]},{"id":"f126c3d2.5c6aa","type":"comment","z":"723d811b.88a7d","name":"Active Slice","info":"","x":620,"y":140,"wires":[]}]
I am curious if anyone had some flows that will parse the radio and rotor data from the UDP broadcasts that N1MM (and TR4W among others) sends out?
I was going to start not his project since I figure this would be useful to provide another way to drive the various flows on has in a shack. At a minimum, it would be cool to integrate a show of contest score, etc into the dashboard.
I saw Larry K8UT on the presentation the other night so this is also inquiring if anyone else if working on this project.
Tom Schaefer, NY4I
Blog:?
Madeira Beach, FL (Grid: EL87ot)
|
Tom
N1MM has a lot of data available?from UDP broadcasts.? Several of us have used portions to drive various functions.? Node-Red handles this well.
Here is a flow to illustrate parsing N1MM UDP data from the "radio info" broadcast.? You will need to configure the UDP Port in N1MM and the flow to agree, for "radio info".
Alan
[{"id":"723d811b.88a7d","type":"tab","label":"Flow 1","disabled":false,"info":""},{"id":"4c4abb17.5a29cc","type":"debug","z":"723d811b.88a7d","name":"","active":false,"tosidebar":true,"console":false,"tostatus":false,"complete":"payload.RadioInfo.FocusRadioNr[0]","targetType":"msg","statusVal":"","statusType":"auto","x":600,"y":180,"wires":[]},{"id":"b9ef1965.2222c8","type":"udp in","z":"723d811b.88a7d","name":"","iface":"","port":"12075","ipv":"udp4","multicast":"false","group":"","datatype":"utf8","x":160,"y":260,"wires":[["8a5b4a27.e60da8"]]},{"id":"8a5b4a27.e60da8","type":"xml","z":"723d811b.88a7d","name":"","property":"payload","attr":"","chr":"","x":350,"y":260,"wires":[["4c4abb17.5a29cc","26c3afcd.56c5b","b32c1126.85901","9308404a.02014"]]},{"id":"26c3afcd.56c5b","type":"debug","z":"723d811b.88a7d","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"payload.RadioInfo.ActiveRadioNr[0]","targetType":"msg","statusVal":"","statusType":"auto","x":640,"y":280,"wires":[]},{"id":"b32c1126.85901","type":"debug","z":"723d811b.88a7d","name":"","active":false,"tosidebar":true,"console":false,"tostatus":false,"complete":"payload.RadioInfo.IsTransmitting[0]","targetType":"msg","statusVal":"","statusType":"auto","x":620,"y":400,"wires":[]},{"id":"9308404a.02014","type":"debug","z":"723d811b.88a7d","name":"","active":false,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","statusVal":"","statusType":"auto","x":420,"y":80,"wires":[]},{"id":"f126c3d2.5c6aa","type":"comment","z":"723d811b.88a7d","name":"Active Slice","info":"","x":620,"y":140,"wires":[]}]
I am curious if anyone had some flows that will parse the radio and rotor data from the UDP broadcasts that N1MM (and TR4W among others) sends out?
I was going to start not his project since I figure this would be useful to provide another way to drive the various flows on has in a shack. At a minimum, it would be cool to integrate a show of contest score, etc into the dashboard.
I saw Larry K8UT on the presentation the other night so this is also inquiring if anyone else if working on this project.
Tom Schaefer, NY4I
Blog:
Madeira Beach, FL (Grid: EL87ot)
|
I¡¯ve done some N1MM+ radio broadcast parsing to show SO2R focus and TX status. I also did some other N1MM+ parsing.
Dave wo2x
Sent from my waxed string and tin cans.
toggle quoted message
Show quoted text
On Feb 3, 2021, at 11:52 AM, Tom Schaefer NY4I <thomasmschaefer@...> wrote:
?I am curious if anyone had some flows that will parse the radio and rotor data from the UDP broadcasts that N1MM (and TR4W among others) sends out?
I was going to start not his project since I figure this would be useful to provide another way to drive the various flows on has in a shack. At a minimum, it would be cool to integrate a show of contest score, etc into the dashboard.
I saw Larry K8UT on the presentation the other night so this is also inquiring if anyone else if working on this project.
Tom Schaefer, NY4I
Blog: www.ny4i.com
Madeira Beach, FL (Grid: EL87ot)
|
I am curious if anyone had some flows that will parse the radio and rotor data from the UDP broadcasts that N1MM (and TR4W among others) sends out?
I was going to start not his project since I figure this would be useful to provide another way to drive the various flows on has in a shack. At a minimum, it would be cool to integrate a show of contest score, etc into the dashboard.
I saw Larry K8UT on the presentation the other night so this is also inquiring if anyone else if working on this project.
Tom Schaefer, NY4I
Blog: www.ny4i.com
Madeira Beach, FL (Grid: EL87ot)
|
Re: General Questions about Node Red
Andre
Welcome to the forum.
I can comment on Green Heron RT21 controllers.
Yes, we have already built flows to interface directly with the RT21.? In my case, I built a Node-Red flow to get the AZ and EL data from SatPC32 and send that to the RT21.? Similarly, most logbook programs have a UDP or API interface to get the rotor info into Node-Red.? Then it's a simple change to my flow to command the RT21 with the same data.
An important consideration is what platform do you prefer to run Node-Red?? This is important in setting up the COM ports with the RT21s.? Since you have multiple rotors, might I suggest you run Node-Red on a Raspberry Pi and use COM to IP converters for each RT21.? I use the MOXA N5200.? I have direct experience with this configuration and found it is very stable.
Another approach is to command PST Rotor using Node-Red.? Many prefer this method.? However, this does not solve your need to use multiple inputs to command your multiple RT21s.
Which logging program do you use.? We already have Node-Red connectors for N1MM.
I think most of the devices you are using GH Anywhere, can be done with Node-Red and consolidated on a single Dashboard, including adding interlocks and other functions?between various devices.
I can help you get started with the rotor control if you like.? Then expand from there.
Alan. WA9WUD
I stumbled across a YouTube video by VA3MW and what I saw got my interest. I am building two fairly large stations and both have the same problems. Lots of different applications with different GUI's making it rather complicated. After watching the video it seems that Node Red will be able to bring all this together in one GUI. I really like what I see and before I dig too deep into this, I thought I would ask a few questions here:
- Both stations uses Green Heron's GH Everywhere wireless solution which controls a bunch of antenna switches, stack matches and other controllers remotely. It is a wonderful product but lots of different windows, buttons etc that needs to be centered on screens.? Will I be able to tie this into Node Red? If so, is anybody on this group using GH Everywhere??
- Both stations has three Green Heron RT21's and will be interfaced to a Logbook via PST Rotor. For PST to be able to run multiple rotors, one has to open multiple instances of the program to achieve this as per the author of the software. I wonder if someone out there has more that one RT21 interface through Node Red?
- Multiple radio interfacing: Both stations uses Icom and Flex so I was wondering how this would work.
As you can see, I am a rookie to NodeRed and willing to learn but I do not want to pursue this path if I cannot interface to the GH Everywhere stuff so any pointers will be greatly appreciated.
Best 73
Andre
NJ0F
|
General Questions about Node Red
I stumbled across a YouTube video by VA3MW and what I saw got my interest. I am building two fairly large stations and both have the same problems. Lots of different applications with different GUI's making it rather complicated. After watching the video it seems that Node Red will be able to bring all this together in one GUI. I really like what I see and before I dig too deep into this, I thought I would ask a few questions here:
- Both stations uses Green Heron's GH Everywhere wireless solution which controls a bunch of antenna switches, stack matches and other controllers remotely. It is a wonderful product but lots of different windows, buttons etc that needs to be centered on screens.? Will I be able to tie this into Node Red? If so, is anybody on this group using GH Everywhere??
- Both stations has three Green Heron RT21's and will be interfaced to a Logbook via PST Rotor. For PST to be able to run multiple rotors, one has to open multiple instances of the program to achieve this as per the author of the software. I wonder if someone out there has more that one RT21 interface through Node Red?
- Multiple radio interfacing: Both stations uses Icom and Flex so I was wondering how this would work.
As you can see, I am a rookie to NodeRed and willing to learn but I do not want to pursue this path if I cannot interface to the GH Everywhere stuff so any pointers will be greatly appreciated. Best 73 Andre NJ0F
|
Re: Sharing your Station flows
Mike w8be?
Those are really nice!? I love the layout.
Mike va3mw
Dwayne
Nice job.? I especially like how you selected the indexed parts of the UDP broadcasts.
Using the same UDP broadcasts from MacDoppler, I built a flow to have MacDoppler drive my rotors and provide uplink and downlink info to CAT drive the Flex.? It worked well with my Maestro using MacDoppler to CAT tune the Flex. ? However, I could not use the Flex to CAT tune MacDopler and I did not like the tiny little frequency knobs on MacDoppler, so I went back to SatPC32.
Using my Maestro and SatPC32, I have built a full suite of Node-Red flows to integrate?their operations, including rotor control.
Alan. WA9WUD
On Wed, Feb 3, 2021 at 1:32 AM Dwayne Sinclair AB6A via <Dwayne_sinclair= [email protected]> wrote: [Edited Message Follows]
My files are here:?/g/nodered-hamradio/files/MacDoppler%20to%20Goto%20Telescope%20Mount%20Rotator
1. Created a simple Flow to redirect unique UDP ports in SliceMaster WSJT-X to a standard port for MacLogger DX.
2. Working on a flow to monitor transmit VFO frequency of my radio and if it changes by more than 25KHz, drop my Amp into Standby.
3. Replacing DDUtil with Node-Red. Forward active VFO Frequency to Plaster. DDUtil is not reliable.
4. Working on rewriting my Telescope Rotator program from Python to Node-Red. Currently have the UDP Flow parsed from MacDoppler so now writing the logic for sending commands to telescope mount.
You are going to see different code for the same thing. You are likely going to use pieces of code and mix and match as needed. As an example, I have no use for the W02X Shack Control, but I do have a use for the small piece of code that provide the TX VFO.?
-D
|
Re: Sharing your Station flows
Dwayne
Nice job.? I especially like how you selected the indexed parts of the UDP broadcasts.
Using the same UDP broadcasts from MacDoppler, I built a flow to have MacDoppler drive my rotors and provide uplink and downlink info to CAT drive the Flex.? It worked well with my Maestro using MacDoppler to CAT tune the Flex. ? However, I could not use the Flex to CAT tune MacDopler and I did not like the tiny little frequency knobs on MacDoppler, so I went back to SatPC32.
Using my Maestro and SatPC32, I have built a full suite of Node-Red flows to integrate?their operations, including rotor control.
Alan. WA9WUD
On Wed, Feb 3, 2021 at 1:32 AM Dwayne Sinclair AB6A via <Dwayne_sinclair= [email protected]> wrote: [Edited Message Follows]
My files are here:?/g/nodered-hamradio/files/MacDoppler%20to%20Goto%20Telescope%20Mount%20Rotator
1. Created a simple Flow to redirect unique UDP ports in SliceMaster WSJT-X to a standard port for MacLogger DX.
2. Working on a flow to monitor transmit VFO frequency of my radio and if it changes by more than 25KHz, drop my Amp into Standby.
3. Replacing DDUtil with Node-Red. Forward active VFO Frequency to Plaster. DDUtil is not reliable.
4. Working on rewriting my Telescope Rotator program from Python to Node-Red. Currently have the UDP Flow parsed from MacDoppler so now writing the logic for sending commands to telescope mount.
You are going to see different code for the same thing. You are likely going to use pieces of code and mix and match as needed. As an example, I have no use for the W02X Shack Control, but I do have a use for the small piece of code that provide the TX VFO.?
-D
|
Re: File /KD4Z Flows/KPA1500_K3_K4.json uploaded
#file-notice
Hi Warren.
I will check the mode command as you pointed out. Thanks.
The TCP connection is left open so that if you manually press the on button on the RF deck the flow is connected to the amp.
I have three communications connections to the back of the KPA1500:
KXUSB cable from amp to USB port on Flex. This allows amp to follow frequency of TX slice and amp changes bands and tunes antenna tuner before any RF applied.
USB A to B cable from amp to PC for KPA1500;utility and remote programs.
Ethernet cable to gig-E switch at operating position for Node Red.
To check the WOL, double click the WOL node and make sure your amp MAC address is listed. Also check the amp menu settings. Net Wake on LAN must be enabled. I believe this is shown when tech mode is enabled. I will add these notes to the comment node on the KPA 1500 flow.
Feel free to reach out if you have any other suggestions to make the flow better. I am adding a one button antenna tune function to the 1500 flow.
73
Dave wo2x
toggle quoted message
Show quoted text
On Feb 3, 2021, at 9:33 AM, Warren Merkel <hullspeed21@...> wrote:
?Hey Dave,
I was getting the looping with your original Flow and no other applications running. The K3 isn't actually polling the KPA, as they have direct, event driven 2-way communication on the Auxbus. However that in-family integration is getting upset. If you created this with a Flex as the exciter, you might not have noticed this loop.
However, I assume you didn't have a K3 to test this with as the 1 second beeping of the K3 made it sound like you were in the ER! My change is a classic "loop breaker" and you might want to incorporate it in your primary Flow as the extra mode status command is unnecessarily being sent after each polling request. It really made the amp unhappy when you clicked Operate mode on.
What I'd like to know is why is the tcp connector is not disconnecting after each session --as it is configured to do so. Could this be a Raspian issue? If I have the KPA1500 Remote app running (and connected), the Flow is blocked. If I close the Remote app, and restart the Flow, then the Flow begins to work again.
BTW, the WOL section doesn't work in my setup. It's enabled in the Amp, but is ignored.
Warren, KD4Z
On 2/3/2021 9:19 AM, David De Coons wo2x wrote:
Hi Warren,
I can see the loop happening as you have two sources (maybe 3 with remote program) commanding the amp at the same time. Makes sense to have the K3 perform the Auto polling.
I went with 1 second polling and am going to add peak/hold to the KPA1500 meters as I use Node Red remote from my phone and iPad and want to capture peak output.
73
Dave wo2x
On Feb 3, 2021, at 8:59 AM, [email protected] Notification <[email protected]> wrote: ?
The following files have been uploaded to the Files area of the [email protected] group.
* /KD4Z Flows/KPA1500_K3_K4.json
</g/nodered-hamradio/files/KD4Z
Flows/KPA1500_K3_K4.json>
*By:* Warren Merkel
*Description:*
Modified flow from WO2X for Elecraft KPA1500 Amplifier. Fixes Status Mode polling loop issue when used with K3 or K4. The K3 / K4 detects Operating Mode status changes when connected to the KPA500/1500 Auxbus. The original flow causes the radio to beep at a one second rate as it was forcing the operating status over and over, after polling for the same. Also, when the Operating Mode was set to enabled, the KPA1500 was being forced to reconfigure once a second and was creating relay havoc. This flow breaks the loop when status polled for, but not when manually changed. Polling interval was altered from 1 second to 2 seconds, as not not hammer the KPA1500 for updates so frequently to be a good neighbor to other applications polling the amp such as the KPA1500 Remote app.
_._,_._,_
------------------------------------------------------------------------
|
Re: File /KD4Z Flows/KPA1500_K3_K4.json uploaded
#file-notice
Hey Dave,
I was getting the looping with your original Flow and no other applications running. The K3 isn't actually polling the KPA, as they have direct, event driven 2-way communication on the Auxbus. However that in-family integration is getting upset. If you created this with a Flex as the exciter, you might not have noticed this loop.
However, I assume you didn't have a K3 to test this with as the 1 second beeping of the K3 made it sound like you were in the ER! My change is a classic "loop breaker" and you might want to incorporate it in your primary Flow as the extra mode status command is unnecessarily being sent after each polling request. It really made the amp unhappy when you clicked Operate mode on.
What I'd like to know is why is the tcp connector is not disconnecting after each session --as it is configured to do so. Could this be a Raspian issue? If I have the KPA1500 Remote app running (and connected), the Flow is blocked. If I close the Remote app, and restart the Flow, then the Flow begins to work again.
BTW, the WOL section doesn't work in my setup. It's enabled in the Amp, but is ignored.
Warren, KD4Z
toggle quoted message
Show quoted text
On 2/3/2021 9:19 AM, David De Coons wo2x wrote: Hi Warren,
I can see the loop happening as you have two sources (maybe 3 with remote program) commanding the amp at the same time. Makes sense to have the K3 perform the Auto polling.
I went with 1 second polling and am going to add peak/hold to the KPA1500 meters as I use Node Red remote from my phone and iPad and want to capture peak output.
73
Dave wo2x
On Feb 3, 2021, at 8:59 AM, [email protected] Notification <[email protected]> wrote:
?
The following files have been uploaded to the Files area of the [email protected] group.
* /KD4Z Flows/KPA1500_K3_K4.json
</g/nodered-hamradio/files/KD4Z
Flows/KPA1500_K3_K4.json>
*By:* Warren Merkel
*Description:*
Modified flow from WO2X for Elecraft KPA1500 Amplifier. Fixes Status Mode polling loop issue when used with K3 or K4. The K3 / K4 detects Operating Mode status changes when connected to the KPA500/1500 Auxbus. The original flow causes the radio to beep at a one second rate as it was forcing the operating status over and over, after polling for the same. Also, when the Operating Mode was set to enabled, the KPA1500 was being forced to reconfigure once a second and was creating relay havoc. This flow breaks the loop when status polled for, but not when manually changed. Polling interval was altered from 1 second to 2 seconds, as not not hammer the KPA1500 for updates so frequently to be a good neighbor to other applications polling the amp such as the KPA1500 Remote app.
_._,_._,_
------------------------------------------------------------------------
|
Re: File /KD4Z Flows/KPA1500_K3_K4.json uploaded
#file-notice
Hi Warren,
I can see the loop happening as you have two sources (maybe 3 with remote program) commanding the amp at the same time. Makes sense to have the K3 perform the Auto polling.
I went with 1 second polling and am going to add peak/hold to the KPA1500 meters as I use Node Red remote from my phone and iPad and want to capture peak output.
73 Dave wo2x
toggle quoted message
Show quoted text
On Feb 3, 2021, at 8:59 AM, [email protected] Notification <[email protected]> wrote:
?
The following files have been uploaded to
the Files area of the [email protected] group.
By: Warren Merkel
Description:
Modified flow from WO2X for Elecraft KPA1500 Amplifier. Fixes Status Mode polling loop issue when used with K3 or K4. The K3 / K4 detects Operating Mode status changes when connected to the KPA500/1500 Auxbus. The original flow causes the radio to beep at a one second rate as it was forcing the operating status over and over, after polling for the same. Also, when the Operating Mode was set to enabled, the KPA1500 was being forced to reconfigure once a second and was creating relay havoc. This flow breaks the loop when status polled for, but not when manually changed. Polling interval was altered from 1 second to 2 seconds, as not not hammer the KPA1500 for updates so frequently to be a good neighbor to other applications polling the amp such as the KPA1500 Remote app.
|
The following files have been uploaded to
the Files area of the [email protected] group.
By: Warren Merkel
Description:
Modified flow from WO2X for Elecraft KPA1500 Amplifier. Fixes Status Mode polling loop issue when used with K3 or K4. The K3 / K4 detects Operating Mode status changes when connected to the KPA500/1500 Auxbus. The original flow causes the radio to beep at a one second rate as it was forcing the operating status over and over, after polling for the same. Also, when the Operating Mode was set to enabled, the KPA1500 was being forced to reconfigure once a second and was creating relay havoc. This flow breaks the loop when status polled for, but not when manually changed. Polling interval was altered from 1 second to 2 seconds, as not not hammer the KPA1500 for updates so frequently to be a good neighbor to other applications polling the amp such as the KPA1500 Remote app.
|
I think putting the required nodes in a read me file is the best way to go.? You can get a list of the dependent nodes from the package.json file in the .node-red directory.? ?
|
Re: Sharing your Station flows
My files are here:? /g/nodered-hamradio/files/MacDoppler%20to%20Goto%20Telescope%20Mount%20Rotator1. Created a simple Flow to redirect unique UDP ports in SliceMaster WSJT-X to a standard port for MacLogger DX. 2. Working on a flow to monitor transmit VFO frequency of my radio and if it changes by more than 25KHz, drop my Amp into Standby. 3. Replacing DDUtil with Node-Red. Forward active VFO Frequency to Plaster. DDUtil is not reliable. 4. Working on rewriting my Telescope Rotator program from Python to Node-Red. Currently have the UDP Flow parsed from MacDoppler so now writing the logic for sending commands to telescope mount. You are going to see different code for the same thing. You are likely going to use pieces of code and mix and match as needed. As an example, I have no use for the W02X Shack Control, but I do have a use for the small piece of code that provide the TX VFO.? -D
|
Another idea is to put a comment Node at top of the flow and list full names of all needed nodes as well as instructions for setting up flow (IP addresses, other flow dependencies, etc)
I will update my flows with this info tomorrow.?
Also you can create a folder in the files area with your call sign. You can add a read.me file with necessary info.?
Dave wo2x Sent from my waxed string and tin cans.?
toggle quoted message
Show quoted text
On Feb 2, 2021, at 10:11 PM, Dwayne Sinclair AB6A via groups.io <Dwayne_sinclair@...> wrote:
? Missing nodes are a pain. I do recommend adding a comment at the top fo the flow detailing node dependencies.
That being said, it might not be obvious to new users, but the Manage Pallet ?option in the top right is a really important option and provide you a guide search for modes.
-D
|
Missing nodes are a pain. I do recommend adding a comment at the top fo the flow detailing node dependencies.
That being said, it might not be obvious to new users, but the Manage Pallet ?option in the top right is a really important option and provide you a guide search for modes.
-D
|
One idea for this ongoing problem of missing nodes:? if people would start sharing flows as a node red project, the list of dependencies would be built in.
An existing flow can be imported to a project in the node red editor. Then, it handles all that, like missing nodes.
node-red-contrib-simple-gate
node-red-contrib-msg-resend?
|
node-red-contrib-simple-gate
node-red-contrib-msg-resend?
|
Al, there is a node that is "unknown" here......"Gate" . Do you have the full name for it?
Also in the KPA500 flow, it is unknown, as well as one called "msg-resend".
Charlie KB8CR
|
Kyle AA0Z
Tom Schaefer - NY4I
Dave wo2x
Neal AB6G