Long time lurker, almost first time poster :-)
It is great to see the energy and enthusiasm on this list.
When I started my code 3 years ago, I designed almost all features to live on their own PI. That¡¯s why you see a lot of data being pushed through the MQTT server. In the early days there were massive problems with the serial port library and sometimes the data for different serial ports got mixed up. Hence the separation. One PI one Serial port.
Going through the MQTT server for all the core data also has the benefit that I can whip up another debug UI client for experimentation without having to mess with my ¡°production¡± code. Easy data sharing of the current values.?
This is my current ¡°main¡± screen and it has not really changed a lot over the last 3 years.
I am using the following controls/modules:
-?Rotator (Green Heron) -?Amplifier Expert 2K FA and 1.3K FA -?Power Meter driven by AMP -?W2 Wattmeter -?SteppIR DB18E? -?SteppIR Maintenance functions (Home, Cal, Track) -?Digital Loggers Power Panel -?Ping (I have 4 PI, Flex, DL Switch and a remote on relay board)
This is what I am currently playing with with (The color scheme on my development environment is red to let me know which server I am on):
David¡¯s Antennas Genius looks interesting. Maybe I can borrow some code from him for this MultiFlex control :-)
Other controls I am interested in is the LP100.
73, Andreas, N6NU
|
Solved. HF Auto ini file wasn?t saved correctly thus it was missing some items. now its working nice.
Dave, take a look at an alternate DLI flow I created with 3D buttons which looks nice and works fine.
Santiago
______________
73 de Santiago
HI8SMX - KB8SMX
web:?
YouTube: HI8SMX?
Twitter: @hi8smx
Instagram: hi8smx
|
Re: FlexRadio V3 flow, volts/PA temp do not work
Dave
If I am not mistaken, based on what Mark explained, in Multiplex, the first client gets port 4991.? When the ?Flex Server (at IP address x.y.z.80) sees the second client, the server assigns it a port, most likely 4993, but not always.
Now at the Raspberry?Pi/Node-Red, when the user wants to know what?is going on in?Client #1, Node-Red asks "x.y.z.80:4991" (your current flow does this).??
If the user wants to know what is going on in Client #2 (if there is a second client?bonded to the Flex Server), Node-Red asks "x.y.z.80:new_second_port".? The IP address of the Flex Server remains the same as configured in the Node-Red TCP Client, only the port number changes.
If you can pull out the port number for client #2 from subscribed data, you can use that to change the port number in the below, TCP "Client" node. ? Client #1 will always be 4992?
??
?I tested the node by injecting "msg.payload = 4992" and it works nicely.
Alan WA9WUD
On Tue, Jul 21, 2020 at 10:17 AM David De Coons wo2x < RocketNJ@...> wrote: Hi Mark
The issue when you do a sub meter all to a 6700 and a 6600 the 6700 has internal FC bolts as meter 20 while the 6600 has it as meter 21.? I do not have a 6400 or 6600 to dig into to find out what ¡°extra¡± meter they put between meter 16 and 20.?
As far as ports, since I am only using a single client I do |client udpport 4991?
I could probably write a routine to have the second client use UDP 4995.? Those commands would be sent out two different TCP request nodes since each radio has a unique IP address.?
73 Dave wo2x Sent from my waxed string and tin cans.? ? Mark
A great lesson on the workings of multiplex API.
So....the port must be changed based on which client is "bound".? OK.
FYI, the normal Node-Red TCP nodes do not allow for changing the port number, outside of the manual configuration page. ??
So..... I found these TCP nodes that have provisions to input a msg.payload (or whatever) ?to make changes to the ?TCP configuration.? I gave the TCP Client a test run, by injecting msg.payload = 4992 and it works very well.? Other parameters?can be changed too.
Here is the Client Node: ? and the Server Node:?
Not sure what happens next, but it is fun playing.
Alan WA9WUD The port number used is a factor of the ports in use at the time of client initialization.
The FlexAPI attempts to create a exclusive UDP Socket at Port 4991, if that fails it will try the next and so on until Port 6010.
Once successfully bound it will inform the Radio with the following command "client udpport 4993"
Note that port 4992 is the discovery port so it will not be used.
This is why you will see the traffic on different ports depending on how many clients you are running
On Windows run the following to see UDP ports in use:?netstat -a -p UDP
So when I run FRStack and SmartSDR I see 4991, 4993 in use and 4992 in use 2 times.
I hope this helps.
Mark
W3II
|
I just checked it here by putting a debug node in the HFAuto flow right before the UDP send node for HFAuto port 12070. I am seeing the XML documented formatted message with correct frequency.
Try making sure both the Flex Radio and HFAuto flows are enabled and W1TR¡¯s software is configured to receive on port 12070.
73
toggle quoted message
Show quoted text
On Jul 21, 2020, at 9:59 AM, Santiago Mejia via groups.io <hi8smx@...> wrote:
?Dave, good morning. Quick question, did you update the HF Auto software? I did this morning and the node red flow is not working with HF Auto. Programs opens but make no connection to UDP and keep getting a pop up window with the info received from Node Red. I just disabled it from the flow and working with FRStack for the moment, while I troubleshoot this.
73
Santiago
______________
73 de Santiago
HI8SMX - KB8SMX
web:?
YouTube: HI8SMX?
Twitter: @hi8smx
Instagram: hi8smx
|
Re: FlexRadio V3 flow, volts/PA temp do not work
Hi Mark
The issue when you do a sub meter all to a 6700 and a 6600 the 6700 has internal FC bolts as meter 20 while the 6600 has it as meter 21. ?I do not have a 6400 or 6600 to dig into to find out what ¡°extra¡± meter they put between meter 16 and 20.?
As far as ports, since I am only using a single client I do |client udpport 4991?
I could probably write a routine to have the second client use UDP 4995. ?Those commands would be sent out two different TCP request nodes since each radio has a unique IP address.?
73 Dave wo2x Sent from my waxed string and tin cans.?
toggle quoted message
Show quoted text
On Jul 21, 2020, at 10:03 AM, Alan Blind <a.alan.blind@...> wrote:
? Mark
A great lesson on the workings of multiplex API.
So....the port must be changed based on which client is "bound".? OK.
FYI, the normal Node-Red TCP nodes do not allow for changing the port number, outside of the manual configuration page. ??
So..... I found these TCP nodes that have provisions to input a msg.payload (or whatever) ?to make changes to the ?TCP configuration.? I gave the TCP Client a test run, by injecting msg.payload = 4992 and it works very well.? Other parameters?can be changed too.
Here is the Client Node: ? and the Server Node:?
Not sure what happens next, but it is fun playing.
Alan WA9WUD The port number used is a factor of the ports in use at the time of client initialization.
The FlexAPI attempts to create a exclusive UDP Socket at Port 4991, if that fails it will try the next and so on until Port 6010.
Once successfully bound it will inform the Radio with the following command "client udpport 4993"
Note that port 4992 is the discovery port so it will not be used.
This is why you will see the traffic on different ports depending on how many clients you are running
On Windows run the following to see UDP ports in use:?netstat -a -p UDP
So when I run FRStack and SmartSDR I see 4991, 4993 in use and 4992 in use 2 times.
I hope this helps.
Mark
W3II
|
I will check this a little later.?
Dave Sent from my waxed string and tin cans.?
toggle quoted message
Show quoted text
On Jul 21, 2020, at 9:59 AM, Santiago Mejia via groups.io <hi8smx@...> wrote:
?Dave, good morning. Quick question, did you update the HF Auto software? I did this morning and the node red flow is not working with HF Auto. Programs opens but make no connection to UDP and keep getting a pop up window with the info received from Node Red. I just disabled it from the flow and working with FRStack for the moment, while I troubleshoot this.
73
Santiago
______________
73 de Santiago
HI8SMX - KB8SMX
web:?
YouTube: HI8SMX?
Twitter: @hi8smx
Instagram: hi8smx
|
Re: FlexRadio V3 flow, volts/PA temp do not work
Mark
A great lesson on the workings of multiplex API.
So....the port must be changed based on which client is "bound".? OK.
FYI, the normal Node-Red TCP nodes do not allow for changing the port number, outside of the manual configuration page. ??
So..... I found these TCP nodes that have provisions to input a msg.payload (or whatever) ?to make changes to the ?TCP configuration.? I gave the TCP Client a test run, by injecting msg.payload = 4992 and it works very well.? Other parameters?can be changed too.
Here is the Client Node: ? and the Server Node:?
Not sure what happens next, but it is fun playing.
Alan WA9WUD
The port number used is a factor of the ports in use at the time of client initialization.
The FlexAPI attempts to create a exclusive UDP Socket at Port 4991, if that fails it will try the next and so on until Port 6010.
Once successfully bound it will inform the Radio with the following command "client udpport 4993"
Note that port 4992 is the discovery port so it will not be used.
This is why you will see the traffic on different ports depending on how many clients you are running
On Windows run the following to see UDP ports in use:?netstat -a -p UDP
So when I run FRStack and SmartSDR I see 4991, 4993 in use and 4992 in use 2 times.
I hope this helps.
Mark
W3II
|
Dave, good morning. Quick question, did you update the HF Auto software? I did this morning and the node red flow is not working with HF Auto. Programs opens but make no connection to UDP and keep getting a pop up window with the info received from Node Red. I just disabled it from the flow and working with FRStack for the moment, while I troubleshoot this.
73
Santiago
______________
73 de Santiago
HI8SMX - KB8SMX
web:?
YouTube: HI8SMX?
Twitter: @hi8smx
Instagram: hi8smx
|
Re: FlexRadio V3 flow, volts/PA temp do not work
The port number used is a factor of the ports in use at the time of client initialization.
The FlexAPI attempts to create a exclusive UDP Socket at Port 4991, if that fails it will try the next and so on until Port 6010.
Once successfully bound it will inform the Radio with the following command "client udpport 4993"
Note that port 4992 is the discovery port so it will not be used.
This is why you will see the traffic on different ports depending on how many clients you are running
On Windows run the following to see UDP ports in use:?netstat -a -p UDP
So when I run FRStack and SmartSDR I see 4991, 4993 in use and 4992 in use 2 times.
I hope this helps.
Mark
W3II
|
Re: FlexRadio V3 flow, volts/PA temp do not work
You have a 6400 or 6600? Change sub meter 20 to sub meter 21.
For whatever reason Flex added an extra meter on the 6400 and 6600 series radios.
73
toggle quoted message
Show quoted text
On Jul 21, 2020, at 12:46 AM, Neal Pollack <nealix@...> wrote:
? Hi:
Today I downloaded from the files section Flex Radio V3 flow.? I changed the IP address of the TCP IN node to my radio.
While the following do seem to work;
TX VFO (at least to 4 digits after the decimal point)
RF Power setting
Tune Power Setting
Mode
Flex TX state
The two meters for Internal voltage and PA Temp do not.? From the flow, they are depending on UDP packets on the network at port 4991.
I used wireshark network analyzer, and there are plenty of packets from the radio on port 4992 for the other GUI information display,? but there are no packets at udp port 4991 at all.
Any ideas how to fix this?? Does the Flex 6600 transmit the packets on udp port 4991, or is this input expected from some other 3rd party program?
OR, do I need to first "do something" to register meters with the Flex 6600 so that it starts sending meter data on port 4991?
Cheers,
Neal? N6YFM
|
Just heard you ta
lking about this group on Ham Radio Workbench. Had to join, as I hope to dedicate a raspberry pi to Node Red and MQTT for remote monitoring of radio and other shack equipment.
Regards,
Ian, G4ZJH?
|
Re: Flex Info before calling support
I am not saying who or what caused me to draft the original email.??
Not to worry, it was all in good fun and thought I would pass on the message.??
Mike va3mw
On Mon, Jul 20, 2020 at 11:35 PM Neal Pollack < nealix@...> wrote: Hey Alan:
Don't worry about being a "poster child"? (A.K.A. Being Human).
The ONLY thing I hate more than perfect people, are people who THINK they are perfect :-)
The rest of us....? ?we tend to prove we are human by numerous recurring mistakes.
I know that I make PLENTY :-).? I love learning, and if you are not making mistakes, you really are not learning.
Cheers,
Neal
|
Re: FlexRadio V3 flow, volts/PA temp do not work
Neal
Dave, WO2X, says the Flex Meters, are work in progress, as he is trying?new parsing techniques on the VITA49 packet to improve its?reliability. ?
Alan
|
Count me in if you need a beta tester.
Cheers,
Neal, N6YFM
|
FlexRadio V3 flow, volts/PA temp do not work
Hi:
Today I downloaded from the files section Flex Radio V3 flow.? I changed the IP address of the TCP IN node to my radio.
While the following do seem to work;
TX VFO (at least to 4 digits after the decimal point)
RF Power setting
Tune Power Setting
Mode
Flex TX state
The two meters for Internal voltage and PA Temp do not.? From the flow, they are depending on UDP packets on the network at port 4991.
I used wireshark network analyzer, and there are plenty of packets from the radio on port 4992 for the other GUI information display,? but there are no packets at udp port 4991 at all.
Any ideas how to fix this?? Does the Flex 6600 transmit the packets on udp port 4991, or is this input expected from some other 3rd party program?
OR, do I need to first "do something" to register meters with the Flex 6600 so that it starts sending meter data on port 4991?
Cheers,
Neal? N6YFM
|
Re: Flex Info before calling support
Hey Alan:
Don't worry about being a "poster child"? (A.K.A. Being Human).
The ONLY thing I hate more than perfect people, are people who THINK they are perfect :-)
The rest of us....? ?we tend to prove we are human by numerous recurring mistakes.
I know that I make PLENTY :-).? I love learning, and if you are not making mistakes, you really are not learning.
Cheers,
Neal
|
DLI Webswitch alternate flow
Dear all, I was working on an alternate flow for my DLI webswitch and came up with this flow. I know probably there is an easier way of doing it, but at least I got it working. Feel free to try it and tinker with it. The file is posted in my folder on this group under the name DLI alternate (and in my github).  73, Santiago ______________ 73 de Santiago HI8SMX web:? YouTube: HI8SMX? Twitter: @hi8smx Instagram: hi8smx
|
Re: Flex Info before calling support
Hi Alan,
Thanks for sharing.? Our club is in the midst or integrating a FlexRadio 6600 into our station for remote operation.? Like you, we're going to use a RPi to control relay, including remote on/off.
I chose to use FTDI USB relays vs GPIO relays, but only because of the convenience of using a USB cable to a centrally located relay board/box.? The trade-off is that things are rather serial? - using crelay - but it works flawlessly.??
So, now I'm pondering, is USB likely to be more resilient to "short duration" drops in the GPIO?
Tks es 73,
Andy
VA3CW
|
Re: Flex Info before calling support
I am probably the guilty party/poster child for Mikes's phone call from Tim.
My Flex 6600 has experienced what I call, "uncommanded" ?short duration shutdown, and reboots.? I use the Flex remote on/off with a relay controlled?from Node-Rd.
I submitted a ticket.
When Tim asked for the Flex Front Button colors, during the experience, it dawned on me that the probable cause was a short duration operation from Node-Red causing the remote relay to cycle.?
I have added some nodes to the Raspberry GPIO pins, for the relay, to send the time of any on/off events at the pins to a flow.set (so it is retained in memory) to catch the next uncommanded shutdown. Of course, there have been zero instances since I installed the relay monitor.
There could be one other ?(6700) candidate for Tim's wrath today....but we may never know. ?(humor)
Alan WA9WUD
|
Flex Info before calling support
Hi All
(having just got off the phone?with Tim)
If your radio is doing weird things, before you open a support case, please make sure that NodeRed or some other?external software is not causing the problem.
This can be the following programs (but not limited to)
- FRStack
- SliceMaster
- NodeRed
- HRD
- Logbooks with CAT control
- VOX and loud dogs
- etc..
Thanks for help!? :)
Mike va3mw
|
Santiago Mejia
Dave wo2x
Ian Tickle
Neal AB6G