The flow I gave you should show actual beam heading in green. Target heading in red.
Dave wo2x
Sent from my waxed string and tin cans.
toggle quoted message
Show quoted text
On Aug 13, 2021, at 11:26 PM, AH0U <bruce@...> wrote:
?The thing I miss with the version I have is that the rotor selection cursor does not show the heading it is on¡. HRD for example shows the heading wherever the pointer is on the map
Non praeses meus
Those who would give up essential liberty, to purchase a little temporary safety,
deserve neither liberty nor safety. Benjamin Franklin (1706-1790
On Aug 13, 2021, at 20:13, David De Coons wo2x <RocketNJ@...> wrote:
?I decided to move the Green Heron RT21 direct to the Pi. Got everything with that working fine.
Added connectors for N1MM+ and N3FJP AC Log. Enter a call in either log program¡¯s entry window and hit tab. Azimuth is sent to the rotor flow to track automatically. I added a gate with a button that toggles between Tracking (green) and Manual (red).
Hopefully tomorrow I will add a log entry window to Node Ted that will send the call to both logging programs for lookup and logging from Node Red. Useful when portable remote.
My thought is I will be running only one or the other log program at a time.
Any input to tweak it is welcome.
I can assist with interfacing to other programs.
Alan has also done similar with Mac Logger DX & N1MM+. My flow is a little more streamlined with goal of remote control and logging from iPhone.
Once I get the logging input done I will post the flow.
73
Dave wo2x
Sent from my waxed string and tin cans.
|
The thing I miss with the version I have is that the rotor selection cursor does not show the heading it is on¡. HRD for example shows the heading wherever the pointer is on the map
Non praeses meus
Those who would give up essential liberty, to purchase a little temporary safety,
deserve neither liberty nor safety. Benjamin Franklin (1706-1790
toggle quoted message
Show quoted text
On Aug 13, 2021, at 20:13, David De Coons wo2x <RocketNJ@...> wrote:
?I decided to move the Green Heron RT21 direct to the Pi. Got everything with that working fine.
Added connectors for N1MM+ and N3FJP AC Log. Enter a call in either log program¡¯s entry window and hit tab. Azimuth is sent to the rotor flow to track automatically. I added a gate with a button that toggles between Tracking (green) and Manual (red).
Hopefully tomorrow I will add a log entry window to Node Ted that will send the call to both logging programs for lookup and logging from Node Red. Useful when portable remote.
My thought is I will be running only one or the other log program at a time.
Any input to tweak it is welcome.
I can assist with interfacing to other programs.
Alan has also done similar with Mac Logger DX & N1MM+. My flow is a little more streamlined with goal of remote control and logging from iPhone.
Once I get the logging input done I will post the flow.
73
Dave wo2x
Sent from my waxed string and tin cans.
|
Re: Kenwood CAT to relay example.json Serial Port Success
Tnx gonna be a couple of days
Tomorrow is lower antennas and pick up the yard day in prep for tropical storm Fred and then I have to package the R-PI and relay board, right now everything is spread out on top of the work station with wires every where like a frog in a high school biology class if you get my drift.
dit dit
Dave
NR1DX
toggle quoted message
Show quoted text
On 8/13/2021 11:14 PM, David De Coons wo2x wrote: Take a look at my Tuner Genius flow in the wo2x folder. I used the ui template on that flow.
Dave wo2x
Sent from my waxed string and tin cans.
On Aug 13, 2021, at 11:09 PM, Dave / NR1DX <manuals@...> wrote:
?And those are in the files area on the group.io page? Or out on the web somewhere?
Dave
NR1DX
On 8/13/2021 11:02 PM, David De Coons wo2x wrote:
I use UI template nodes for buttons. Much nicer.
Dave wo2x
Sent from my waxed string and tin cans.
On Aug 13, 2021, at 10:57 PM, Dave / NR1DX <manuals@...> wrote: ?In the final analysis The key to getting the serial data out of the serial input node was in getting the Input parameters setup correctly.
In my case (YMMV) in the port setup under INPUT parameters
1) "Wait for a start character of <F>, then" . All (recent) Kenwood serial frequency strings start with FA (for VFO A) or FB (VFO B).
2) "Split input <On the character><;>
Once the two changes were made the flow began reading serial data from the radio and putting out the appropriate relay numbers like a champ.
After many fails today I added the GPIO interfaces and by this evening I was setting relays based on the radio frequency
The whole point of this project was to build a home brew automatic antenna switch that selected the correct antenna based on the radio frequency the switch itself was finished several days ago and was running with a "soldering iron programmable" rotary switch box. As of tonight we were activating relays via the Raspberry-PI with node red massaging the radio serial data. A fancy set of desk top computer buttons will eventually cap the whole project off.. Thanks for everyone's help.. especially Dave and Alan
To steal the line from that Garth Brooks classic " I could have done without the pain, but I would have had to miss the dance"
I'm sure I will be back when I start trying to make computer desk top buttons
Dave
NR1DX
On 8/12/2021 1:13 PM, Alan Blind, WA9WUD wrote:
Dave
I have a little experience with using the Kenwood protocol. So just a guess here.
Switch to using the Node-Red Serial Request Node. Set it up as you did the receive Node. In fact, your cable should now be stored as a configuration and show up in the serial request node's pull down com selector.
Put an "inject" Node on the Input of the Serial Request Node. On the inject node, set it to inject a string, "FA;". Inject and watch the output of the Serial Request Node.
"FA;" tells the radio to send the VFO frequency, and it should reply with the frequency.
Alan
On Thu, Aug 12, 2021 at 1:00 PM Dave / NR1DX <manuals@... <mailto:manuals@...>> wrote:
Dave & Alan
OK Dave's cleanup and reinstall routine was 98% accurate and I was
able
to fill in the holes. I now have the all the other USB COM ports
cleaned
out and the FTDI port listed and connected... That is the good news
...the bad news is still no data coming out of the SERAIL-IN node. I
bypassed all the other stuff and routed the output of the SERIAL-IN
directly MSG_payload to see what if anything we were
getting...nothing.
My thinking is correct (verify) that if the SERIAL NODE is now
"connected", and my serial dongle RXD node is blinking when I change
FREQ we should see some kind of string coming out of that node (
ASCII I
suspect)
I will continue to plug away at this but if I don't solve it today
tomorrow at your convenience is fine
Dave
NR1DX
On 8/12/2021 12:08 PM, David De Coons wo2x wrote:
> To delete all the old references to serial ports in the serial
node, double click the serial node. Click the pencil to edit.
Upper left of that window select delete.
>
> Use pull down to select next serial device. Use pencil to edit.
Delete. Repeat for any remaining serial cables.
>
> Then it will prompt to create new. When you were in the
/dev/serial folder, highlight the serial cable in the serial by ID
folder. Right click and select copy path.
>
> Back in Node Red when you open the serial node and create new.
Paste the path you copied for the usb to serial adapter. Set baud
rate. Set timeout to something like 500 ms. It defaults to 10000
ms. This is important!
>
> Sorry if I am not 100% accurate with description. Doing it from
memory while out having lunch.
>
> Again let me know and I can help tomorrow.
>
> Dave wo2x
>
> Sent from my waxed string and tin cans.
>
>> On Aug 12, 2021, at 11:44 AM, Alan Blind, WA9WUD
<a.alan.blind@... <mailto:a.alan.blind@...>> wrote:
>>
>
>
>
>
-- Dave Manuals@... www.ArtekManuals.com
<>
-- This email has been checked for viruses by Avast antivirus software.
<>
--
Dave Manuals@... www.ArtekManuals.com
--
Dave Manuals@... www.ArtekManuals.com
--
Dave Manuals@... www.ArtekManuals.com
|
So you have Green Heron Everyware Server running on Pi ?
Ron WV4P?
On Fri, Aug 13, 2021, 10:13 PM David De Coons wo2x < RocketNJ@...> wrote: I decided to move the Green Heron RT21 direct to the Pi. Got everything with that working fine.
Added connectors for N1MM+ and N3FJP AC Log. Enter a call in either log program¡¯s entry window and hit tab. Azimuth is sent to the rotor flow to track automatically. I added a gate with a button that toggles between Tracking (green) and Manual (red).
Hopefully tomorrow I will add a log entry window to Node Ted that will send the call to both logging programs for lookup and logging from Node Red. Useful when portable remote.
My thought is I will be running only one or the other log program at a time.
Any input to tweak it is welcome.
I can assist with interfacing to other programs.
Alan has also done similar with Mac Logger DX & N1MM+. My flow is a little more streamlined with goal of remote control and logging from iPhone.
Once I get the logging input done I will post the flow.
73
Dave wo2x
Sent from my waxed string and tin cans.
|
Re: Kenwood CAT to relay example.json Serial Port Success
Take a look at my Tuner Genius flow in the wo2x folder. I used the ui template on that flow.
Dave wo2x
Sent from my waxed string and tin cans.
toggle quoted message
Show quoted text
On Aug 13, 2021, at 11:09 PM, Dave / NR1DX <manuals@...> wrote:
?And those are in the files area on the group.io page? Or out on the web somewhere?
Dave
NR1DX
On 8/13/2021 11:02 PM, David De Coons wo2x wrote:
I use UI template nodes for buttons. Much nicer.
Dave wo2x
Sent from my waxed string and tin cans.
On Aug 13, 2021, at 10:57 PM, Dave / NR1DX <manuals@...> wrote: ?In the final analysis The key to getting the serial data out of the serial input node was in getting the Input parameters setup correctly.
In my case (YMMV) in the port setup under INPUT parameters
1) "Wait for a start character of <F>, then" . All (recent) Kenwood serial frequency strings start with FA (for VFO A) or FB (VFO B).
2) "Split input <On the character><;>
Once the two changes were made the flow began reading serial data from the radio and putting out the appropriate relay numbers like a champ.
After many fails today I added the GPIO interfaces and by this evening I was setting relays based on the radio frequency
The whole point of this project was to build a home brew automatic antenna switch that selected the correct antenna based on the radio frequency the switch itself was finished several days ago and was running with a "soldering iron programmable" rotary switch box. As of tonight we were activating relays via the Raspberry-PI with node red massaging the radio serial data. A fancy set of desk top computer buttons will eventually cap the whole project off.. Thanks for everyone's help.. especially Dave and Alan
To steal the line from that Garth Brooks classic " I could have done without the pain, but I would have had to miss the dance"
I'm sure I will be back when I start trying to make computer desk top buttons
Dave
NR1DX
On 8/12/2021 1:13 PM, Alan Blind, WA9WUD wrote:
Dave
I have a little experience with using the Kenwood protocol. So just a guess here.
Switch to using the Node-Red Serial Request Node. Set it up as you did the receive Node. In fact, your cable should now be stored as a configuration and show up in the serial request node's pull down com selector.
Put an "inject" Node on the Input of the Serial Request Node. On the inject node, set it to inject a string, "FA;". Inject and watch the output of the Serial Request Node.
"FA;" tells the radio to send the VFO frequency, and it should reply with the frequency.
Alan
On Thu, Aug 12, 2021 at 1:00 PM Dave / NR1DX <manuals@... <mailto:manuals@...>> wrote:
Dave & Alan
OK Dave's cleanup and reinstall routine was 98% accurate and I was
able
to fill in the holes. I now have the all the other USB COM ports
cleaned
out and the FTDI port listed and connected... That is the good news
...the bad news is still no data coming out of the SERAIL-IN node. I
bypassed all the other stuff and routed the output of the SERIAL-IN
directly MSG_payload to see what if anything we were
getting...nothing.
My thinking is correct (verify) that if the SERIAL NODE is now
"connected", and my serial dongle RXD node is blinking when I change
FREQ we should see some kind of string coming out of that node (
ASCII I
suspect)
I will continue to plug away at this but if I don't solve it today
tomorrow at your convenience is fine
Dave
NR1DX
On 8/12/2021 12:08 PM, David De Coons wo2x wrote:
> To delete all the old references to serial ports in the serial
node, double click the serial node. Click the pencil to edit.
Upper left of that window select delete.
>
> Use pull down to select next serial device. Use pencil to edit.
Delete. Repeat for any remaining serial cables.
>
> Then it will prompt to create new. When you were in the
/dev/serial folder, highlight the serial cable in the serial by ID
folder. Right click and select copy path.
>
> Back in Node Red when you open the serial node and create new.
Paste the path you copied for the usb to serial adapter. Set baud
rate. Set timeout to something like 500 ms. It defaults to 10000
ms. This is important!
>
> Sorry if I am not 100% accurate with description. Doing it from
memory while out having lunch.
>
> Again let me know and I can help tomorrow.
>
> Dave wo2x
>
> Sent from my waxed string and tin cans.
>
>> On Aug 12, 2021, at 11:44 AM, Alan Blind, WA9WUD
<a.alan.blind@... <mailto:a.alan.blind@...>> wrote:
>>
>
>
>
>
-- Dave Manuals@... www.ArtekManuals.com
<>
-- This email has been checked for viruses by Avast antivirus software.
<>
--
Dave Manuals@... www.ArtekManuals.com
--
Dave Manuals@... www.ArtekManuals.com
|
I decided to move the Green Heron RT21 direct to the Pi. Got everything with that working fine.
Added connectors for N1MM+ and N3FJP AC Log. Enter a call in either log program¡¯s entry window and hit tab. Azimuth is sent to the rotor flow to track automatically. I added a gate with a button that toggles between Tracking (green) and Manual (red).
Hopefully tomorrow I will add a log entry window to Node Ted that will send the call to both logging programs for lookup and logging from Node Red. Useful when portable remote.
My thought is I will be running only one or the other log program at a time.
Any input to tweak it is welcome.
I can assist with interfacing to other programs.
Alan has also done similar with Mac Logger DX & N1MM+. My flow is a little more streamlined with goal of remote control and logging from iPhone.
Once I get the logging input done I will post the flow.
73
Dave wo2x
Sent from my waxed string and tin cans.
|
Re: Kenwood CAT to relay example.json Serial Port Success
And those are in the files area on the group.io page? Or out on the web somewhere?
Dave
NR1DX
toggle quoted message
Show quoted text
On 8/13/2021 11:02 PM, David De Coons wo2x wrote: I use UI template nodes for buttons. Much nicer.
Dave wo2x
Sent from my waxed string and tin cans.
On Aug 13, 2021, at 10:57 PM, Dave / NR1DX <manuals@...> wrote:
?In the final analysis The key to getting the serial data out of the serial input node was in getting the Input parameters setup correctly.
In my case (YMMV) in the port setup under INPUT parameters
1) "Wait for a start character of <F>, then" . All (recent) Kenwood serial frequency strings start with FA (for VFO A) or FB (VFO B).
2) "Split input <On the character><;>
Once the two changes were made the flow began reading serial data from the radio and putting out the appropriate relay numbers like a champ.
After many fails today I added the GPIO interfaces and by this evening I was setting relays based on the radio frequency
The whole point of this project was to build a home brew automatic antenna switch that selected the correct antenna based on the radio frequency the switch itself was finished several days ago and was running with a "soldering iron programmable" rotary switch box. As of tonight we were activating relays via the Raspberry-PI with node red massaging the radio serial data. A fancy set of desk top computer buttons will eventually cap the whole project off.. Thanks for everyone's help.. especially Dave and Alan
To steal the line from that Garth Brooks classic " I could have done without the pain, but I would have had to miss the dance"
I'm sure I will be back when I start trying to make computer desk top buttons
Dave
NR1DX
On 8/12/2021 1:13 PM, Alan Blind, WA9WUD wrote:
Dave
I have a little experience with using the Kenwood protocol. So just a guess here.
Switch to using the Node-Red Serial Request Node. Set it up as you did the receive Node. In fact, your cable should now be stored as a configuration and show up in the serial request node's pull down com selector.
Put an "inject" Node on the Input of the Serial Request Node. On the inject node, set it to inject a string, "FA;". Inject and watch the output of the Serial Request Node.
"FA;" tells the radio to send the VFO frequency, and it should reply with the frequency.
Alan
On Thu, Aug 12, 2021 at 1:00 PM Dave / NR1DX <manuals@... <mailto:manuals@...>> wrote:
Dave & Alan
OK Dave's cleanup and reinstall routine was 98% accurate and I was
able
to fill in the holes. I now have the all the other USB COM ports
cleaned
out and the FTDI port listed and connected... That is the good news
...the bad news is still no data coming out of the SERAIL-IN node. I
bypassed all the other stuff and routed the output of the SERIAL-IN
directly MSG_payload to see what if anything we were
getting...nothing.
My thinking is correct (verify) that if the SERIAL NODE is now
"connected", and my serial dongle RXD node is blinking when I change
FREQ we should see some kind of string coming out of that node (
ASCII I
suspect)
I will continue to plug away at this but if I don't solve it today
tomorrow at your convenience is fine
Dave
NR1DX
On 8/12/2021 12:08 PM, David De Coons wo2x wrote:
> To delete all the old references to serial ports in the serial
node, double click the serial node. Click the pencil to edit.
Upper left of that window select delete.
>
> Use pull down to select next serial device. Use pencil to edit.
Delete. Repeat for any remaining serial cables.
>
> Then it will prompt to create new. When you were in the
/dev/serial folder, highlight the serial cable in the serial by ID
folder. Right click and select copy path.
>
> Back in Node Red when you open the serial node and create new.
Paste the path you copied for the usb to serial adapter. Set baud
rate. Set timeout to something like 500 ms. It defaults to 10000
ms. This is important!
>
> Sorry if I am not 100% accurate with description. Doing it from
memory while out having lunch.
>
> Again let me know and I can help tomorrow.
>
> Dave wo2x
>
> Sent from my waxed string and tin cans.
>
>> On Aug 12, 2021, at 11:44 AM, Alan Blind, WA9WUD
<a.alan.blind@... <mailto:a.alan.blind@...>> wrote:
>>
>
>
>
>
-- Dave Manuals@... www.ArtekManuals.com
<>
-- This email has been checked for viruses by Avast antivirus software.
<>
--
Dave Manuals@... www.ArtekManuals.com
--
Dave Manuals@... www.ArtekManuals.com
|
Re: Kenwood CAT to relay example.json Serial Port Success
I use UI template nodes for buttons. Much nicer.
Dave wo2x
Sent from my waxed string and tin cans.
toggle quoted message
Show quoted text
On Aug 13, 2021, at 10:57 PM, Dave / NR1DX <manuals@...> wrote:
?In the final analysis The key to getting the serial data out of the serial input node was in getting the Input parameters setup correctly.
In my case (YMMV) in the port setup under INPUT parameters
1) "Wait for a start character of <F>, then" . All (recent) Kenwood serial frequency strings start with FA (for VFO A) or FB (VFO B).
2) "Split input <On the character><;>
Once the two changes were made the flow began reading serial data from the radio and putting out the appropriate relay numbers like a champ.
After many fails today I added the GPIO interfaces and by this evening I was setting relays based on the radio frequency
The whole point of this project was to build a home brew automatic antenna switch that selected the correct antenna based on the radio frequency the switch itself was finished several days ago and was running with a "soldering iron programmable" rotary switch box. As of tonight we were activating relays via the Raspberry-PI with node red massaging the radio serial data. A fancy set of desk top computer buttons will eventually cap the whole project off.. Thanks for everyone's help.. especially Dave and Alan
To steal the line from that Garth Brooks classic " I could have done without the pain, but I would have had to miss the dance"
I'm sure I will be back when I start trying to make computer desk top buttons
Dave
NR1DX
On 8/12/2021 1:13 PM, Alan Blind, WA9WUD wrote:
Dave
I have a little experience with using the Kenwood protocol. So just a guess here.
Switch to using the Node-Red Serial Request Node. Set it up as you did the receive Node. In fact, your cable should now be stored as a configuration and show up in the serial request node's pull down com selector.
Put an "inject" Node on the Input of the Serial Request Node. On the inject node, set it to inject a string, "FA;". Inject and watch the output of the Serial Request Node.
"FA;" tells the radio to send the VFO frequency, and it should reply with the frequency.
Alan
On Thu, Aug 12, 2021 at 1:00 PM Dave / NR1DX <manuals@... <mailto:manuals@...>> wrote:
Dave & Alan
OK Dave's cleanup and reinstall routine was 98% accurate and I was
able
to fill in the holes. I now have the all the other USB COM ports
cleaned
out and the FTDI port listed and connected... That is the good news
...the bad news is still no data coming out of the SERAIL-IN node. I
bypassed all the other stuff and routed the output of the SERIAL-IN
directly MSG_payload to see what if anything we were
getting...nothing.
My thinking is correct (verify) that if the SERIAL NODE is now
"connected", and my serial dongle RXD node is blinking when I change
FREQ we should see some kind of string coming out of that node (
ASCII I
suspect)
I will continue to plug away at this but if I don't solve it today
tomorrow at your convenience is fine
Dave
NR1DX
On 8/12/2021 12:08 PM, David De Coons wo2x wrote:
> To delete all the old references to serial ports in the serial
node, double click the serial node. Click the pencil to edit.
Upper left of that window select delete.
>
> Use pull down to select next serial device. Use pencil to edit.
Delete. Repeat for any remaining serial cables.
>
> Then it will prompt to create new. When you were in the
/dev/serial folder, highlight the serial cable in the serial by ID
folder. Right click and select copy path.
>
> Back in Node Red when you open the serial node and create new.
Paste the path you copied for the usb to serial adapter. Set baud
rate. Set timeout to something like 500 ms. It defaults to 10000
ms. This is important!
>
> Sorry if I am not 100% accurate with description. Doing it from
memory while out having lunch.
>
> Again let me know and I can help tomorrow.
>
> Dave wo2x
>
> Sent from my waxed string and tin cans.
>
>> On Aug 12, 2021, at 11:44 AM, Alan Blind, WA9WUD
<a.alan.blind@... <mailto:a.alan.blind@...>> wrote:
>>
>
>
>
>
-- Dave Manuals@... www.ArtekManuals.com
<>
-- This email has been checked for viruses by Avast antivirus software.
<>
--
Dave Manuals@... www.ArtekManuals.com
|
Kenwood CAT to relay example.json Serial Port Success
In the final analysis The key to getting the serial data out of the serial input node was in getting the Input parameters setup correctly.
In my case (YMMV) in the port setup under INPUT parameters
1) "Wait for a start character of <F>, then" . All (recent) Kenwood serial frequency strings start with FA (for VFO A) or FB (VFO B).
2) "Split input <On the character><;>
Once the two changes were made the flow began reading serial data from the radio and putting out the appropriate relay numbers like a champ.
After many fails today I added the GPIO interfaces and by this evening I was setting relays based on the radio frequency
The whole point of this project was to build a home brew automatic antenna switch that selected the correct antenna based on the radio frequency the switch itself was finished several days ago and was running with a "soldering iron programmable" rotary switch box. As of tonight we were activating relays via the Raspberry-PI with node red massaging the radio serial data. A fancy set of desk top computer buttons will eventually cap the whole project off.. Thanks for everyone's help.. especially Dave and Alan
To steal the line from that Garth Brooks classic " I could have done without the pain, but I would have had to miss the dance"
I'm sure I will be back when I start trying to make computer desk top buttons
Dave
NR1DX
toggle quoted message
Show quoted text
On 8/12/2021 1:13 PM, Alan Blind, WA9WUD wrote: Dave
I have a little experience with using the Kenwood protocol.? So just a guess here.
Switch to using the Node-Red Serial Request Node.? Set it up as you did the receive Node.? In fact, your cable should now be stored as a configuration and show up in the serial request node's pull down com selector.
Put an "inject" Node on the Input of the Serial Request Node.? On the inject node, set it to inject a string, "FA;".? Inject and watch the output of the Serial Request Node.
"FA;" tells the radio to send the VFO frequency, and it should reply with the frequency.
Alan
On Thu, Aug 12, 2021 at 1:00 PM Dave / NR1DX <manuals@... <mailto:manuals@...>> wrote:
Dave & Alan
OK Dave's cleanup and reinstall routine was 98% accurate and I was
able
to fill in the holes. I now have the all the other USB COM ports
cleaned
out and the FTDI port listed and connected... That is the good news
...the bad news is still no data coming out of the SERAIL-IN node. I
bypassed all the other stuff and routed the output of the SERIAL-IN
directly MSG_payload to see what if anything we were
getting...nothing.
My thinking is correct (verify) that if the SERIAL NODE is now
"connected", and my serial dongle RXD node is blinking when I change
FREQ we should see some kind of string coming out of that node (
ASCII I
suspect)
I will continue to plug away at this but if I don't solve it today
tomorrow at your convenience is fine
Dave
NR1DX
On 8/12/2021 12:08 PM, David De Coons wo2x wrote:
> To delete all the old references to serial ports in the serial
node, double click the serial node. Click the pencil to edit.
Upper left of that window select delete.
>
> Use pull down to select next serial device. Use pencil to edit.
Delete. Repeat for any remaining serial cables.
>
> Then it will prompt to create new. When you were in the
/dev/serial folder, highlight the serial cable in the serial by ID
folder. Right click and select copy path.
>
> Back in Node Red when you open the serial node and create new.
Paste the path you copied for the usb to serial adapter. Set baud
rate. Set timeout to something like 500 ms. It defaults to 10000
ms. This is important!
>
> Sorry if I am not 100% accurate with description. Doing it from
memory while out having lunch.
>
> Again let me know and I can help tomorrow.
>
> Dave wo2x
>
> Sent from my waxed string and tin cans.
>
>> On Aug 12, 2021, at 11:44 AM, Alan Blind, WA9WUD
<a.alan.blind@... <mailto:a.alan.blind@...>> wrote:
>>
>
>
>
>
--
Dave Manuals@... www.ArtekManuals.com
<>
--
This email has been checked for viruses by Avast antivirus software.
<>
--
Dave Manuals@... www.ArtekManuals.com
|
Re: Kenwood CAT to relay example.json..... PROGRESS
Hi
And you can use hex values too. In getting WB0SMX ERC-4 flow (based on based on WO2X PSTRotator)? flow to work here, I used 0x0D, ie 0x to show hex and 0D is a carriage return.
Mike
VK1OO
|
That's perfect. In fact. I'll just run the amp from 120. It only requires 240 when running CW. I won't be running CW when remote.
--
73,
Ed KA9EES
|
Serial "shack" control vs Ethernet ?
I love my serial data RS232 technology, hard to believe it is just over 60 years old !..... Even USB has been bent to service it judging from the number of "dongles" available on Amooozon. The events of the last 48 hours in trying to tame a simple serial data stream as I struggle to keep up with the current craze to use a computer the size of a deck of cards that is more powerful than my first IBM-PC from the early 1980's, set me to thinking, am I chasing the wrong bus ( pun intended)?
The current trend not withstanding of a small group of hams with too much disposable income, to own "remote" stations in the country which they control over the internet. My computer (home built I7-8700) , my transceiver (TS890), my amplifier (KPA1500) , my antenna controller ( Stepp-IR) all sport Ethernet ports. (OK so maybe I have just a bit too much disposable income as well.. I had to buy the XYL a $10K German sewing machine..quid pro quo) . The question comes to mind should those of us who simply (for the fun of it) want to automate/ semi automate our home station be focused on controlling and logging via the Ethernet connections within the shack rather than the plethora of RS232 cables and USB dongles?
Thoughts? Comments?
Dave
NR1DX
--
Dave Manuals@... www.ArtekManuals.com
--
This email has been checked for viruses by Avast antivirus software.
|
Re: Kenwood CAT to relay example.json..... PROGRESS
Two possible conventions for line endings: Windows: \r\n OSX/Linux/Unix: \n
From: "David De Coons wo2x" <RocketNJ@...> To: "nodered-hamradio" < [email protected]> Sent: Thursday, August 12, 2021 7:32:48 PM Subject: Re: [nodered-hamradio]Kenwood CAT to relay example.json..... PROGRESS
I think \n (ASCII char 10 is new line feed and is different than \r (ASCII char 13) which is carriage return. It would be \r\n for both, or at least that was how I remember it from my days at staring at an HP serial protocol analyzer. ? ? 73 Dave wo2x ? ? ? \n ( new line) means look for the carriage return and line feed characters, together. .? ?Char(13) Char(10) If your string only has one or the other,.it won't match. ? On Thu, Aug 12, 2021, 8:29 PM Dave / NR1DX <manuals@...> wrote: A break through of sorts late this afternoon
In the port setup is a group of boxes under INPUT.
The second row down is a line? SPLIT INPUT with two boxes which default
to [On the character]and [\n]
Changing the [\n] to "A"? ( one of the characters in the serial string
we are looking for) allowed information to start coming out of the
serial port into the rest of the flow.
??I am sure that "A" is not likely correct it certainly screws up the
serial message parsing for the later logic to act on
But it points as to where to start looking further ....... Is "\n"
supposed to be a number or \(number)? maybe?
Can anyone point me to a complete set of DOCUMENTATION? that defines
what all the choices under INPUT are and how to choose appropriately?
Dave WO2X and Alan thanks again for all your suggestions earlier. Dave a
video call tomorrow at this point is not necessary. Pointers to real
documentation if it exists appreciated though. Until that surfaces I
will likely play the "monkey at the typewriter" till I figure out what
goes in all those boxes and why.
Tomorrow I will point the output of the Serial node to Msg-Payload in
DEBUG mode and see what the data string really looks like
Dave
NR1DX
On 8/12/2021 1:00 PM, Dave / NR1DX wrote:
> Dave & Alan
>
> OK Dave's cleanup and reinstall routine was 98% accurate and I was
> able to fill in the holes. I now have the all the other USB COM ports
> cleaned out and the FTDI port listed and connected... That is the good
> news ...the bad news is still no data coming out of the SERAIL-IN
> node. I bypassed all the other stuff and routed the output of the
> SERIAL-IN? directly MSG_payload to see what if anything we were
> getting...nothing.
>
> My thinking is correct (verify) that if the SERIAL NODE is now
> "connected", and my serial dongle RXD node is blinking when I change
> FREQ we should see some kind of string coming out of that node ( ASCII
> I suspect)
>
> I will continue to plug away at this but if I don't solve it today
> tomorrow at your convenience is fine
>
> Dave
> NR1DX
>
> On 8/12/2021 12:08 PM, David De Coons wo2x wrote:
>> To delete all the old references to serial ports in the serial node,
>> double click the serial node. Click the pencil to edit. Upper left of
>> that window select delete.
>>
>> Use pull down to select next serial device. Use pencil to edit.
>> Delete. Repeat for any remaining serial cables.
>>
>> Then it will prompt to create new. When you were in the /dev/serial
>> folder, highlight the serial cable in the serial by ID folder. Right
>> click and select copy path.
>>
>> Back in Node Red when you open the serial node and create new. Paste
>> the path you copied for the usb to serial adapter. Set baud rate. Set
>> timeout to something like 500 ms. It defaults to 10000 ms. This is
>> important!
>>
>> Sorry if I am not 100% accurate with description. Doing it from
>> memory while out having lunch.
>>
>> Again let me know and I can help tomorrow.
>>
>> Dave wo2x
>>
>> Sent from my waxed string and tin cans.
>>
>>> On Aug 12, 2021, at 11:44 AM, Alan Blind, WA9WUD
>>> <a.alan.blind@...> wrote:
>>>
>>
>>
>>
>>
>
--
Dave Manuals@...
--
This email has been checked for viruses by Avast antivirus software.
|
Re: Kenwood CAT to relay example.json..... PROGRESS
Sorry I was out on a fairly long road trip today and then crashed and burned on the couch for three hours. Now with somewhat fresh mind....
OK, jogging my memory and Dave's experimenting around here is what should solve it to get the input from the Kenwood intact so you can then pass along to parse.
On the Serial In (or Serial Request), double click it to open then click on the pencil to edit. Change Split Input to On Character and the ; (semi colon) character. Each response from Kenwood is terminated with a ;
That should get the data flowing and you should see the FA responses. Then try the example flow I gave you and it should show the frequency.
For others having Serial In issues, look at the protocol for whatever device you are trying to connect to. For example, the DUC-1/Hygain rotor protocol uses a terminator of ; (just like Kenwood) and you need to set that as the split input character in the Serial node.
73
Dave wo2x
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] < [email protected]> On Behalf Of Dave / NR1DX Sent: Thursday, August 12, 2021 8:29 PM To: [email protected]Subject: Re: [nodered-hamradio]Kenwood CAT to relay example.json..... PROGRESS A break through of sorts late this afternoon In the port setup is a group of boxes under INPUT. The second row down is a line SPLIT INPUT with two boxes which default to [On the character]and [\n] Changing the [\n] to "A" ( one of the characters in the serial string we are looking for) allowed information to start coming out of the serial port into the rest of the flow. I am sure that "A" is not likely correct it certainly screws up the serial message parsing for the later logic to act on But it points as to where to start looking further ....... Is "\n" supposed to be a number or \(number) maybe? Can anyone point me to a complete set of DOCUMENTATION that defines what all the choices under INPUT are and how to choose appropriately? Dave WO2X and Alan thanks again for all your suggestions earlier. Dave a video call tomorrow at this point is not necessary. Pointers to real documentation if it exists appreciated though. Until that surfaces I will likely play the "monkey at the typewriter" till I figure out what goes in all those boxes and why. Tomorrow I will point the output of the Serial node to Msg-Payload in DEBUG mode and see what the data string really looks like Dave NR1DX On 8/12/2021 1:00 PM, Dave / NR1DX wrote: Dave & Alan
OK Dave's cleanup and reinstall routine was 98% accurate and I was
able to fill in the holes. I now have the all the other USB COM ports
cleaned out and the FTDI port listed and connected... That is the good
news ...the bad news is still no data coming out of the SERAIL-IN
node. I bypassed all the other stuff and routed the output of the
SERIAL-IN directly MSG_payload to see what if anything we were
getting...nothing.
My thinking is correct (verify) that if the SERIAL NODE is now
"connected", and my serial dongle RXD node is blinking when I change
FREQ we should see some kind of string coming out of that node ( ASCII
I suspect)
I will continue to plug away at this but if I don't solve it today
tomorrow at your convenience is fine
Dave
NR1DX
On 8/12/2021 12:08 PM, David De Coons wo2x wrote:
To delete all the old references to serial ports in the serial node,
double click the serial node. Click the pencil to edit. Upper left of
that window select delete.
Use pull down to select next serial device. Use pencil to edit.
Delete. Repeat for any remaining serial cables.
Then it will prompt to create new. When you were in the /dev/serial
folder, highlight the serial cable in the serial by ID folder. Right
click and select copy path.
Back in Node Red when you open the serial node and create new. Paste
the path you copied for the usb to serial adapter. Set baud rate. Set
timeout to something like 500 ms. It defaults to 10000 ms. This is
important!
Sorry if I am not 100% accurate with description. Doing it from
memory while out having lunch.
Again let me know and I can help tomorrow.
Dave wo2x
Sent from my waxed string and tin cans.
On Aug 12, 2021, at 11:44 AM, Alan Blind, WA9WUD
<a.alan.blind@...> wrote:
-- Dave Manuals@... www.ArtekManuals.com -- This email has been checked for viruses by Avast antivirus software.
|
Re: Kenwood CAT to relay example.json..... PROGRESS
I think \n (ASCII char 10 is new line feed and is different than \r (ASCII char 13) which is carriage return. It would be \r\n for both, or at least that was how I remember it from my days at staring at an HP serial protocol analyzer. ? ? 73 Dave wo2x ? ?
toggle quoted message
Show quoted text
From: [email protected] < [email protected]> On Behalf Of Warren Merkel Sent: Thursday, August 12, 2021 8:38 PM To: [email protected]Subject: Re: [nodered-hamradio]Kenwood CAT to relay example.json..... PROGRESS ? \n ( new line) means look for the carriage return and line feed characters, together. .? ?Char(13) Char(10) If your string only has one or the other,.it won't match. ? On Thu, Aug 12, 2021, 8:29 PM Dave / NR1DX <manuals@...> wrote: A break through of sorts late this afternoon
In the port setup is a group of boxes under INPUT.
The second row down is a line? SPLIT INPUT with two boxes which default
to [On the character]and [\n]
Changing the [\n] to "A"? ( one of the characters in the serial string
we are looking for) allowed information to start coming out of the
serial port into the rest of the flow.
??I am sure that "A" is not likely correct it certainly screws up the
serial message parsing for the later logic to act on
But it points as to where to start looking further ....... Is "\n"
supposed to be a number or \(number)? maybe?
Can anyone point me to a complete set of DOCUMENTATION? that defines
what all the choices under INPUT are and how to choose appropriately?
Dave WO2X and Alan thanks again for all your suggestions earlier. Dave a
video call tomorrow at this point is not necessary. Pointers to real
documentation if it exists appreciated though. Until that surfaces I
will likely play the "monkey at the typewriter" till I figure out what
goes in all those boxes and why.
Tomorrow I will point the output of the Serial node to Msg-Payload in
DEBUG mode and see what the data string really looks like
Dave
NR1DX
On 8/12/2021 1:00 PM, Dave / NR1DX wrote:
> Dave & Alan
>
> OK Dave's cleanup and reinstall routine was 98% accurate and I was
> able to fill in the holes. I now have the all the other USB COM ports
> cleaned out and the FTDI port listed and connected... That is the good
> news ...the bad news is still no data coming out of the SERAIL-IN
> node. I bypassed all the other stuff and routed the output of the
> SERIAL-IN? directly MSG_payload to see what if anything we were
> getting...nothing.
>
> My thinking is correct (verify) that if the SERIAL NODE is now
> "connected", and my serial dongle RXD node is blinking when I change
> FREQ we should see some kind of string coming out of that node ( ASCII
> I suspect)
>
> I will continue to plug away at this but if I don't solve it today
> tomorrow at your convenience is fine
>
> Dave
> NR1DX
>
> On 8/12/2021 12:08 PM, David De Coons wo2x wrote:
>> To delete all the old references to serial ports in the serial node,
>> double click the serial node. Click the pencil to edit. Upper left of
>> that window select delete.
>>
>> Use pull down to select next serial device. Use pencil to edit.
>> Delete. Repeat for any remaining serial cables.
>>
>> Then it will prompt to create new. When you were in the /dev/serial
>> folder, highlight the serial cable in the serial by ID folder. Right
>> click and select copy path.
>>
>> Back in Node Red when you open the serial node and create new. Paste
>> the path you copied for the usb to serial adapter. Set baud rate. Set
>> timeout to something like 500 ms. It defaults to 10000 ms. This is
>> important!
>>
>> Sorry if I am not 100% accurate with description. Doing it from
>> memory while out having lunch.
>>
>> Again let me know and I can help tomorrow.
>>
>> Dave wo2x
>>
>> Sent from my waxed string and tin cans.
>>
>>> On Aug 12, 2021, at 11:44 AM, Alan Blind, WA9WUD
>>> <a.alan.blind@...> wrote:
>>>
>>
>>
>>
>>
>
--
Dave Manuals@...
--
This email has been checked for viruses by Avast antivirus software.
|
Ed
These devices are designed to be switched from a GPIO pin. ?I have several.
They safely control 120VAC loads, with overload and surge protection. ?You could in turn use it to switch a 240 VAC load on/off through a two pole contractor, with 120VAC coil.
Alan
|
Re: Kenwood CAT to relay example.json..... PROGRESS
\n ( new line) means look for the carriage return and line feed characters, together. .? ?Char(13) Char(10)
If your string only has one or the other,.it won't match.
On Thu, Aug 12, 2021, 8:29 PM Dave / NR1DX < manuals@...> wrote: A break through of sorts late this afternoon
In the port setup is a group of boxes under INPUT.
The second row down is a line? SPLIT INPUT with two boxes which default
to [On the character]and [\n]
Changing the [\n] to "A"? ( one of the characters in the serial string
we are looking for) allowed information to start coming out of the
serial port into the rest of the flow.
??I am sure that "A" is not likely correct it certainly screws up the
serial message parsing for the later logic to act on
But it points as to where to start looking further ....... Is "\n"
supposed to be a number or \(number)? maybe?
Can anyone point me to a complete set of DOCUMENTATION? that defines
what all the choices under INPUT are and how to choose appropriately?
Dave WO2X and Alan thanks again for all your suggestions earlier. Dave a
video call tomorrow at this point is not necessary. Pointers to real
documentation if it exists appreciated though. Until that surfaces I
will likely play the "monkey at the typewriter" till I figure out what
goes in all those boxes and why.
Tomorrow I will point the output of the Serial node to Msg-Payload in
DEBUG mode and see what the data string really looks like
Dave
NR1DX
On 8/12/2021 1:00 PM, Dave / NR1DX wrote:
> Dave & Alan
>
> OK Dave's cleanup and reinstall routine was 98% accurate and I was
> able to fill in the holes. I now have the all the other USB COM ports
> cleaned out and the FTDI port listed and connected... That is the good
> news ...the bad news is still no data coming out of the SERAIL-IN
> node. I bypassed all the other stuff and routed the output of the
> SERIAL-IN? directly MSG_payload to see what if anything we were
> getting...nothing.
>
> My thinking is correct (verify) that if the SERIAL NODE is now
> "connected", and my serial dongle RXD node is blinking when I change
> FREQ we should see some kind of string coming out of that node ( ASCII
> I suspect)
>
> I will continue to plug away at this but if I don't solve it today
> tomorrow at your convenience is fine
>
> Dave
> NR1DX
>
> On 8/12/2021 12:08 PM, David De Coons wo2x wrote:
>> To delete all the old references to serial ports in the serial node,
>> double click the serial node. Click the pencil to edit. Upper left of
>> that window select delete.
>>
>> Use pull down to select next serial device. Use pencil to edit.
>> Delete. Repeat for any remaining serial cables.
>>
>> Then it will prompt to create new. When you were in the /dev/serial
>> folder, highlight the serial cable in the serial by ID folder. Right
>> click and select copy path.
>>
>> Back in Node Red when you open the serial node and create new. Paste
>> the path you copied for the usb to serial adapter. Set baud rate. Set
>> timeout to something like 500 ms. It defaults to 10000 ms. This is
>> important!
>>
>> Sorry if I am not 100% accurate with description. Doing it from
>> memory while out having lunch.
>>
>> Again let me know and I can help tomorrow.
>>
>> Dave wo2x
>>
>> Sent from my waxed string and tin cans.
>>
>>> On Aug 12, 2021, at 11:44 AM, Alan Blind, WA9WUD
>>> <a.alan.blind@...> wrote:
>>>
>>
>>
>>
>>
>
--
Dave Manuals@...
--
This email has been checked for viruses by Avast antivirus software.
|
Re: Kenwood CAT to relay example.json..... PROGRESS
A break through of sorts late this afternoon
In the port setup is a group of boxes under INPUT.
The second row down is a line? SPLIT INPUT with two boxes which default to [On the character]and [\n]
Changing the [\n] to "A"? ( one of the characters in the serial string we are looking for) allowed information to start coming out of the serial port into the rest of the flow.
?I am sure that "A" is not likely correct it certainly screws up the serial message parsing for the later logic to act on
But it points as to where to start looking further ....... Is "\n" supposed to be a number or \(number)? maybe?
Can anyone point me to a complete set of DOCUMENTATION? that defines what all the choices under INPUT are and how to choose appropriately?
Dave WO2X and Alan thanks again for all your suggestions earlier. Dave a video call tomorrow at this point is not necessary. Pointers to real documentation if it exists appreciated though. Until that surfaces I will likely play the "monkey at the typewriter" till I figure out what goes in all those boxes and why.
Tomorrow I will point the output of the Serial node to Msg-Payload in DEBUG mode and see what the data string really looks like
Dave
NR1DX
toggle quoted message
Show quoted text
On 8/12/2021 1:00 PM, Dave / NR1DX wrote: Dave & Alan
OK Dave's cleanup and reinstall routine was 98% accurate and I was able to fill in the holes. I now have the all the other USB COM ports cleaned out and the FTDI port listed and connected... That is the good news ...the bad news is still no data coming out of the SERAIL-IN node. I bypassed all the other stuff and routed the output of the SERIAL-IN? directly MSG_payload to see what if anything we were getting...nothing.
My thinking is correct (verify) that if the SERIAL NODE is now "connected", and my serial dongle RXD node is blinking when I change FREQ we should see some kind of string coming out of that node ( ASCII I suspect)
I will continue to plug away at this but if I don't solve it today tomorrow at your convenience is fine
Dave
NR1DX
On 8/12/2021 12:08 PM, David De Coons wo2x wrote:
To delete all the old references to serial ports in the serial node, double click the serial node. Click the pencil to edit. Upper left of that window select delete.
Use pull down to select next serial device. Use pencil to edit. Delete. Repeat for any remaining serial cables.
Then it will prompt to create new. When you were in the /dev/serial folder, highlight the serial cable in the serial by ID folder. Right click and select copy path.
Back in Node Red when you open the serial node and create new. Paste the path you copied for the usb to serial adapter. Set baud rate. Set timeout to something like 500 ms. It defaults to 10000 ms. This is important!
Sorry if I am not 100% accurate with description. Doing it from memory while out having lunch.
Again let me know and I can help tomorrow.
Dave wo2x
Sent from my waxed string and tin cans.
On Aug 12, 2021, at 11:44 AM, Alan Blind, WA9WUD <a.alan.blind@...> wrote:
-- Dave Manuals@... www.ArtekManuals.com
--
This email has been checked for viruses by Avast antivirus software.
|
I want to trigger this from my RPi with 3.3vdc. I am not envisioning this. Anybody got a circuit in their head?
--
73,
Ed KA9EES
|
I did a quick search of the files and internet looking a flow for my StationPro II and didn't find anything.? Has anyone done this?? I would need 8 relays to parallel the panel switches and an on screen interface.? Not complicated but before re-inventing the wheel I thought I would check.
73, George
W2GS
|
Dave wo2x
Edward Dowdy KA9EES