开云体育

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

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

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

Mike w8be Those are really nice! I love the layout. Mike va3mw wrote:

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

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

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

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

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

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.

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

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

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

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

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

Wondering if you would like to share your flows?? I just got NodeRed going yesterday and playing with wo2x's starter flows. I do like your Station flows. 73, Mike Kovacich - VE3CKO -

The following files have been uploaded to the Files area of the [email protected] group. * /K0VM Flows/KAT500 flow.json ( /g/nodered-hamradio/files/K0VM Flows/KAT500

The following files have been uploaded to the Files area of the [email protected] group. * /K0VM Flows/KPA500 flow.json ( /g/nodered-hamradio/files/K0VM Flows/KPA500

Dave Regarding StreamDeck buttons. ?I made a StreamDeck "Do All" button for my satellite station like you are thinking for your amp. When I select a satellite on SatPC32 the satellite name shows up