Re: Nodered and Denkovi 8 Relay USB boards
Hi Harry, While there are many relay boards out there, actually have the LP Remote extension board (the one with the 16 relays on it), which uses 2 8-port MCP23008 i2c port expanders, which drive a ULN2803A 8 channel darlington relay driver each. The board is connected through i2c to the Raspberry Pi. In Node Red I installed node-red-contrib-redplc-rpi-mcp23008 node (search for it in the palette), which I found was the only one of several out there that actually worked. The only caveat though is that it will only work on a raspberry pi and the pi must have a 32bit operating system. Although it took me a little while to figure out how exactly this node worked, I eventually got it working flawlessly. So no need to throw away the LP remote board if you don't want to.
However, looking to the future, I have a nagging feeling that the 32bit operating system could well become obsolete. I contacted the programmer, but he had no interest in updating the software (part of it is written in C++, compiled on a 32 bit system). So I kept searching and am now at the stage of rewriting/upgrading an existing node that will handle a whole range of i2c port expanders (MCP23008, MCP23017, PCF8574, PCF8574A and PCF8575). I have written most of the node software and will be testing soon (I have one of each chip available). No promises on when it will be available, though. But as I said my current setup does work flawlessly. The nice thing about ditching the LP Remote main board was that I no longer had to deal with the on-board pic controller and had the power and versatility of Node-Red at my disposal. 73 de Joe, AB1DO
------ Original Message ------
From: willisw200@...
To: [email protected]
Sent: Wednesday, January 11, 2023 2:39 PM
Subject: Re: [nodered-hamradio] Nodered and Denkovi 8 Relay USB boards
Thanks Alan for the info. So far all I have done with Node-Red is down load it to my win 10 machine. I have connected to the palette and watched a utube video which described the process for creating a flow. I do not know what MQTT is but will look into it¡have a lot to learn! I will check out the DLI boards and also the Denkovi boards you mentioned. Thanks¡Harry ¨C W0LS There are several relay board types, and everyone has a favorite. My favorites are the DLI Relay switches and the GPIO pin-based relay boards. Both have flows posed on this site. You asked about the Denkovi relay boards. The Denkovi USB boards are difficult to interface with Node-Red. However, the Denkovi MQTT and Web Based TCP boards are easily controlled from Node-Red. The Denkovi Documentation for these boards has the MQTT commands and the HTTP commands, which Node-Red can be easily used to send. On Wed, Jan 11, 2023 at 12:29 PM Harry Williams <willisw200@...> wrote: Hi...I am new to this group and Node Red. Currently I am using a product called LP-REMOTE (N8LP product) to control up to 16 relays. It is starting to have problems and I would like to replace it. So I see all this stuff about Node Red in the Flex community so I am thinking of replacing it with a small Node-Red dashboard to control a couple of Denkovi 8 Relay USB boards. I searched this group for Denkovi and found plenty of references to the boards I have but have not found a successful implemenation. Do any of you know if Node Red will work with these boards or if I should look to another relay board that has proven to work. My goal is a small dashboard with just relay switches at least for now. I would be deploying it on a Win 10 computer.
|
Re: Nodered and Denkovi 8 Relay USB boards
Thanks Alan for the info. So far all I have done with Node-Red is down load it to my win 10 machine. I have connected to the palette and watched a utube video which described the process for creating a flow. I do not know what MQTT is but
will look into it¡have a lot to learn! I will check out the DLI boards and also the Denkovi boards you mentioned.
?
Thanks¡Harry ¨C W0LS
?
toggle quoted message
Show quoted text
From: [email protected] < [email protected]>
On Behalf Of Alan Blind, WA9WUD
Sent: Wednesday, January 11, 2023 12:44
To: [email protected]
Subject: Re: [nodered-hamradio] Nodered and Denkovi 8 Relay USB boards
?
There are several?relay board types, and everyone has a favorite.? My favorites are the DLI Relay switches and the GPIO pin-based relay boards.? Both have flows posed on this site.
You asked about the Denkovi relay boards.? The Denkovi USB boards are difficult to interface with Node-Red.
However, the Denkovi MQTT and Web Based TCP boards are easily controlled from Node-Red.
The Denkovi Documentation for these boards has the MQTT commands and the HTTP commands, which?Node-Red can be easily used to send.
?
On Wed, Jan 11, 2023 at 12:29 PM Harry Williams <willisw200@...> wrote:
Hi...I am new to this group and Node Red. Currently I am using a product called LP-REMOTE (N8LP product) to control up to 16 relays. It is starting to have problems and I would like to replace it. So I see all this stuff about Node Red
in the Flex community so I am thinking of replacing it with a small Node-Red dashboard to control a couple of Denkovi 8 Relay USB boards. I searched this group for Denkovi and found plenty of references to the boards I have but have not found a successful
implemenation. Do any of you know if Node Red will work with these boards or if I should look to another relay board that has proven to work. My goal is a small dashboard with just relay switches at least for now. I would be deploying it on a Win 10 computer.
|
Re: Nodered and Denkovi 8 Relay USB boards
Harry
There are several?relay board types, and everyone has a favorite.? My favorites are the DLI Relay switches and the GPIO pin-based relay boards.? Both have flows posed on this site.
You asked about the Denkovi relay boards.? The Denkovi USB boards are difficult to interface with Node-Red.
However, the Denkovi MQTT and Web Based TCP boards are easily controlled from Node-Red.
The Denkovi Documentation for these boards has the MQTT commands and the HTTP commands, which?Node-Red can be easily used to send.
Alan. WA9WUD
On Wed, Jan 11, 2023 at 12:29 PM Harry Williams < willisw200@...> wrote: Hi...I am new to this group and Node Red. Currently I am using a product called LP-REMOTE (N8LP product) to control up to 16 relays. It is starting to have problems and I would like to replace it. So I see all this stuff about Node Red in the Flex community so I am thinking of replacing it with a small Node-Red dashboard to control a couple of Denkovi 8 Relay USB boards. I searched this group for Denkovi and found plenty of references to the boards I have but have not found a successful implemenation. Do any of you know if Node Red will work with these boards or if I should look to another relay board that has proven to work. My goal is a small dashboard with just relay switches at least for now. I would be deploying it on a Win 10 computer.
?
Thanks....Harry - W0LS
|
Nodered and Denkovi 8 Relay USB boards
Hi...I am new to this group and Node Red. Currently I am using a product called LP-REMOTE (N8LP product) to control up to 16 relays. It is starting to have problems and I would like to replace it. So I see all this stuff about Node Red in the Flex community so I am thinking of replacing it with a small Node-Red dashboard to control a couple of Denkovi 8 Relay USB boards. I searched this group for Denkovi and found plenty of references to the boards I have but have not found a successful implemenation. Do any of you know if Node Red will work with these boards or if I should look to another relay board that has proven to work. My goal is a small dashboard with just relay switches at least for now. I would be deploying it on a Win 10 computer.
?
Thanks....Harry - W0LS
|
Good Luck!
I run my main shack dashboard on a Debian mini-pc but it should work on the Pi4 as well.
The biggest issues I had getting the flow working was the timing to get the 9500 streaming the telemetry data.
I¡¯m interested if it will work the same on another 9500 with a different computer.
You may have to tweak the timing on the connection.
I just received a Zimaboard 12v computer someone posted about a few days ago.
I¡¯m going to play around with it and may load Debian and my flows to see if a different Node-Red server works the same.
73,
George / W7GES
toggle quoted message
Show quoted text
On Jan 10, 2023, at 7:32 PM, Dave wo2x <RocketNJ@...> wrote:
?Thanks George,
I¡¯m building up a Pi4 to send to Hawaii where the 9500 is located. I¡¯ll pick the TX frequency off my FlexRadio flow.
I have to change a few things around with the rotor flow for the controller there and hope to mail it out tomorrow.
73
Dave wo2x
On Jan 10, 2023, at 9:21 PM, George / W7GES <geo.skoubis@...> wrote:
?Here is a picture and the flow. I do have another version that I set up for rig 1 as I can configure my Node-Red dashboard for MS instead of SO2R.
There are some extra nodes in the flow from development / trouble-shooting. When I had everything working I left it to make sure it ran in the long run and I've been working on other station improvements.
I have the 9500 USB connected directly to the Node-Red server but it's easy enough to change.
The "Parse XML TXFreq" node will need to be changed for RadioNR1 vs RadioNR2 if you actually use N1MM to determine the band you are on. It works for me because this is a contest dashboard and I use a General DX "contest" database if I'm DXing and can run FT8 / RTTY / CW / SSB on one rig and another mode on the other.
Of course feel free to email me if you have any questions. The connection to get the 9500 data streaming is non-intuitive!
Hopefully a second set of eyes looking at the flow can really improve it.
73,
George / W7GES
-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Dave wo2x
Sent: Tuesday, January 10, 2023 6:46 PM
To: [email protected]
Subject: Re: [nodered-hamradio] Alpha 9500
Thanks George.
I have an idea on ¡°fixing¡± the split issue. I¡¯ll take a look at the flow and see if my idea will fly.
73
Dave wo2x
Sent from my waxed string and tin cans.
On Jan 10, 2023, at 8:43 PM, George / W7GES <geo.skoubis@...> wrote:
?Hi Dave,
I have one.
It¡¯s integrated with N1MM UDP so it reads my rig frequency and changes to the correct band segment.
It doesn¡¯t work well split as it hunts between segments but I have it set up on radio 2 for SO2R contesting and don¡¯t operate split with that rig anyway or it would annoy me enough to fix it.
I will send it in a few minutes from my computer as I am on my cell now.
73,
George / W7GES
On Jan 10, 2023, at 1:29 PM, Dave wo2x <RocketNJ@...> wrote: ?Hi all
I know a while back there was talk about a flow for an Alpha 9500.
Before I venture down the road with investigating if Node Red will work with the 9500 I figure I¡¯d ask here if anyone has done any work to integrate it.
73
Dave wo2x
Sent from my waxed string and tin cans.
<Alpha_9500_W7GES_v007.json>
<2022_0724_nodered2.png>
|
Thanks George,
I¡¯m building up a Pi4 to send to Hawaii where the 9500 is located. I¡¯ll pick the TX frequency off my FlexRadio flow.
I have to change a few things around with the rotor flow for the controller there and hope to mail it out tomorrow.
73
Dave wo2x
toggle quoted message
Show quoted text
On Jan 10, 2023, at 9:21 PM, George / W7GES <geo.skoubis@...> wrote:
?Here is a picture and the flow. I do have another version that I set up for rig 1 as I can configure my Node-Red dashboard for MS instead of SO2R.
There are some extra nodes in the flow from development / trouble-shooting. When I had everything working I left it to make sure it ran in the long run and I've been working on other station improvements.
I have the 9500 USB connected directly to the Node-Red server but it's easy enough to change.
The "Parse XML TXFreq" node will need to be changed for RadioNR1 vs RadioNR2 if you actually use N1MM to determine the band you are on. It works for me because this is a contest dashboard and I use a General DX "contest" database if I'm DXing and can run FT8 / RTTY / CW / SSB on one rig and another mode on the other.
Of course feel free to email me if you have any questions. The connection to get the 9500 data streaming is non-intuitive!
Hopefully a second set of eyes looking at the flow can really improve it.
73,
George / W7GES
-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Dave wo2x
Sent: Tuesday, January 10, 2023 6:46 PM
To: [email protected]
Subject: Re: [nodered-hamradio] Alpha 9500
Thanks George.
I have an idea on ¡°fixing¡± the split issue. I¡¯ll take a look at the flow and see if my idea will fly.
73
Dave wo2x
Sent from my waxed string and tin cans.
On Jan 10, 2023, at 8:43 PM, George / W7GES <geo.skoubis@...> wrote:
?Hi Dave,
I have one.
It¡¯s integrated with N1MM UDP so it reads my rig frequency and changes to the correct band segment.
It doesn¡¯t work well split as it hunts between segments but I have it set up on radio 2 for SO2R contesting and don¡¯t operate split with that rig anyway or it would annoy me enough to fix it.
I will send it in a few minutes from my computer as I am on my cell now.
73,
George / W7GES
On Jan 10, 2023, at 1:29 PM, Dave wo2x <RocketNJ@...> wrote: ?Hi all
I know a while back there was talk about a flow for an Alpha 9500.
Before I venture down the road with investigating if Node Red will work with the 9500 I figure I¡¯d ask here if anyone has done any work to integrate it.
73
Dave wo2x
Sent from my waxed string and tin cans.
<Alpha_9500_W7GES_v007.json>
<2022_0724_nodered2.png>
|
One more comment. In the ARRL RTTY RU this weekend I found running with the 9500 much quieter than my PGXL! I generally set the 9500 to 1k out and only cranked it up to 1.5k if someone moved in on my frequency. I used the other rig and PGXL as S&P on another band.
In a SSB or CW contest either amp is great... (and of course no 6 meters with the 9500!).
George / W7GES
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] < [email protected]> On Behalf Of George / W7GES via groups.io Sent: Tuesday, January 10, 2023 7:22 PM To: [email protected]Subject: Re: [nodered-hamradio] Alpha 9500 Here is a picture and the flow. I do have another version that I set up for rig 1 as I can configure my Node-Red dashboard for MS instead of SO2R. There are some extra nodes in the flow from development / trouble-shooting. When I had everything working I left it to make sure it ran in the long run and I've been working on other station improvements. I have the 9500 USB connected directly to the Node-Red server but it's easy enough to change. The "Parse XML TXFreq" node will need to be changed for RadioNR1 vs RadioNR2 if you actually use N1MM to determine the band you are on. It works for me because this is a contest dashboard and I use a General DX "contest" database if I'm DXing and can run FT8 / RTTY / CW / SSB on one rig and another mode on the other. Of course feel free to email me if you have any questions. The connection to get the 9500 data streaming is non-intuitive! Hopefully a second set of eyes looking at the flow can really improve it. 73, George / W7GES -----Original Message----- From: [email protected] < [email protected]> On Behalf Of Dave wo2x Sent: Tuesday, January 10, 2023 6:46 PM To: [email protected]Subject: Re: [nodered-hamradio] Alpha 9500 Thanks George. I have an idea on ¡°fixing¡± the split issue. I¡¯ll take a look at the flow and see if my idea will fly. 73 Dave wo2x Sent from my waxed string and tin cans. On Jan 10, 2023, at 8:43 PM, George / W7GES <geo.skoubis@...> wrote:
?Hi Dave,
I have one.
It¡¯s integrated with N1MM UDP so it reads my rig frequency and changes to the correct band segment.
It doesn¡¯t work well split as it hunts between segments but I have it set up on radio 2 for SO2R contesting and don¡¯t operate split with that rig anyway or it would annoy me enough to fix it.
I will send it in a few minutes from my computer as I am on my cell now.
73,
George / W7GES
On Jan 10, 2023, at 1:29 PM, Dave wo2x <RocketNJ@...> wrote:
?Hi all
I know a while back there was talk about a flow for an Alpha 9500.
Before I venture down the road with investigating if Node Red will work with the 9500 I figure I¡¯d ask here if anyone has done any work to integrate it.
73
Dave wo2x
Sent from my waxed string and tin cans.
|
Here is a picture and the flow. I do have another version that I set up for rig 1 as I can configure my Node-Red dashboard for MS instead of SO2R.
There are some extra nodes in the flow from development / trouble-shooting. When I had everything working I left it to make sure it ran in the long run and I've been working on other station improvements.
I have the 9500 USB connected directly to the Node-Red server but it's easy enough to change.
The "Parse XML TXFreq" node will need to be changed for RadioNR1 vs RadioNR2 if you actually use N1MM to determine the band you are on. It works for me because this is a contest dashboard and I use a General DX "contest" database if I'm DXing and can run FT8 / RTTY / CW / SSB on one rig and another mode on the other.
Of course feel free to email me if you have any questions. The connection to get the 9500 data streaming is non-intuitive!
Hopefully a second set of eyes looking at the flow can really improve it.
73,
George / W7GES
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] < [email protected]> On Behalf Of Dave wo2x Sent: Tuesday, January 10, 2023 6:46 PM To: [email protected]Subject: Re: [nodered-hamradio] Alpha 9500 Thanks George. I have an idea on ¡°fixing¡± the split issue. I¡¯ll take a look at the flow and see if my idea will fly. 73 Dave wo2x Sent from my waxed string and tin cans. On Jan 10, 2023, at 8:43 PM, George / W7GES <geo.skoubis@...> wrote:
?Hi Dave,
I have one.
It¡¯s integrated with N1MM UDP so it reads my rig frequency and changes to the correct band segment.
It doesn¡¯t work well split as it hunts between segments but I have it set up on radio 2 for SO2R contesting and don¡¯t operate split with that rig anyway or it would annoy me enough to fix it.
I will send it in a few minutes from my computer as I am on my cell now.
73,
George / W7GES
On Jan 10, 2023, at 1:29 PM, Dave wo2x <RocketNJ@...> wrote:
?Hi all
I know a while back there was talk about a flow for an Alpha 9500.
Before I venture down the road with investigating if Node Red will work with the 9500 I figure I¡¯d ask here if anyone has done any work to integrate it.
73
Dave wo2x
Sent from my waxed string and tin cans.
|
Thanks George.
I have an idea on ¡°fixing¡± the split issue. I¡¯ll take a look at the flow and see if my idea will fly.
73
Dave wo2x
Sent from my waxed string and tin cans.
toggle quoted message
Show quoted text
On Jan 10, 2023, at 8:43 PM, George / W7GES <geo.skoubis@...> wrote:
?Hi Dave,
I have one.
It¡¯s integrated with N1MM UDP so it reads my rig frequency and changes to the correct band segment.
It doesn¡¯t work well split as it hunts between segments but I have it set up on radio 2 for SO2R contesting and don¡¯t operate split with that rig anyway or it would annoy me enough to fix it.
I will send it in a few minutes from my computer as I am on my cell now.
73,
George / W7GES
On Jan 10, 2023, at 1:29 PM, Dave wo2x <RocketNJ@...> wrote:
?Hi all
I know a while back there was talk about a flow for an Alpha 9500.
Before I venture down the road with investigating if Node Red will work with the 9500 I figure I¡¯d ask here if anyone has done any work to integrate it.
73
Dave wo2x
Sent from my waxed string and tin cans.
|
Hi Dave,
I have one.
It¡¯s integrated with N1MM UDP so it reads my rig frequency and changes to the correct band segment.
It doesn¡¯t work well split as it hunts between segments but I have it set up on radio 2 for SO2R contesting and don¡¯t operate split with that rig anyway or it would annoy me enough to fix it.
I will send it in a few minutes from my computer as I am on my cell now.
73,
George / W7GES
toggle quoted message
Show quoted text
On Jan 10, 2023, at 1:29 PM, Dave wo2x <RocketNJ@...> wrote:
?Hi all
I know a while back there was talk about a flow for an Alpha 9500.
Before I venture down the road with investigating if Node Red will work with the 9500 I figure I¡¯d ask here if anyone has done any work to integrate it.
73
Dave wo2x
Sent from my waxed string and tin cans.
|
Re: SPE Linear V1.1 flow uploaded to files section
Nick, the Read Me node will have the flow version. The "Log" button starts a CSV (command separated value) log on the Node Red server logging the vdata returned form the SPE flows. I import the data into Excel and can do some analysis on output power? for digital drive levels. The original intent was to capture alarm data for any triggered alarms. I believe there is a comment node that gives additional insight. This works on all 3 models (1.3K, 1.5K and 2K). 73, Ron WB2WGH?
Hi Ron? I don¡¯t know what version I am using , but it is working great.? Spe2k? I have log graphic not sure what it does ? Maybe for 1k or 1.3 k On Jan 10, 2023, at 1:09 PM, Ronald Panetta, WB2WGH <ron@...> wrote:
? Ken, down in the shack. Yes, 200ms is what I have in the flow but depending on how you update the USB port configuration you may end up with the incorrect timeout. You should be polling at 250ms with a timeout of 200ms. That seems to work well. If you are interested in testing? a beta?for a future release, send me an email to my QRZ listed email address and I'll email you the beta flow. Below is a screen snapshot of the new dashboard and the current change history since V1.1.?
73, Ron WB2WGH
- ? ? ? ? ? - Corrected copy/paste typos for the 1.3K-FA power gauge maximum and color transitions. - ? ? ? ? ? - Added comments in the Read Me and "PWR Meter Range" with guidance on adjusting gauge - ? ? ? ? ? ? color transitions and maximums. - ? ? ? ? ? - Added debug node after buffer to string conversion - ? ? ? ? ? - Cleaned up and deleted historical commented out code from assorted function nodes - ? ? ? ? ? - Added capability to define exciter drive power level. User must customize the "Define - ? ? ? ? ? ? Exciter Drive Power" function node. - ? ? ? ? ? - Reworked case statement for band display. As mentioned above, the SPE returns band data - ? ? ? ? ? ? as string and numeric depending on band. Rather than mix string and numeric comparisons - ? ? ? ? ? ? in the case statement, using parseInt() which always yeilds a numeric, regardless of - ? ? ? ? ? ? input type, prior to the case, eliminates this issue. - ? ? ? ? ? - ===Interim release (V1.2b1) tofor "node-red-node-serialport" in the read me - ? ? ? ? ? - If operating mode (standby/operate) comes back with an unexpected character, force the - ? ? ? ? ? ? optional "Define Exciter Drive Power" to report zero since we don't know what state the - ? ? ? ? ? ? SPE is and we don't want to blow it up. - ? ? ? ? ? - Last byte of status messages were getting cut off (CR returned and LF dropped) due to - ? ? ? ? ? ? USB request node requesting 75 bytes instead of 76. Also changed "6, 76, Other Byte - ? ? ? ? ? ? Buffer?" switch node to for 76 byte buffers. - ? ? ? ? ? - As a FYI, even though the "Buffer Size?" switch node checks for smaller packets, they - ? ? ? ? ? ? never make it out of the "USB Request" node as with no consistent delimiter, a 76 byte - ? ? ? ? ? ? fixed length query is used and all smaller confirmations will result in a timeout. - ? ? ? ? ? - Consolidated logging flow variable initialization into the master initialization node - ? ? ? ? ? - Changed buffer length and checksum validation along with "SPE Responding" logic to - ? ? ? ? ? ? eliminate "USB Status" indicator momentary red blips when changing SPE settings. The short - ? ? ? ? ? ? packets resulting from a change (e.g., change power level) result in a valid but short - ? ? ? ? ? ? packet with timeouts as the 76 byte length is not achieved. Logic has to account for that - ? ? ? ? ? ? in both SPE powered on and off states. - ? ? ? ? ? - Flow layout cleanup (no functional changes) - ? ? ? ? ? - Discovered packets sometimes wrap around due to inability to detect start and end of frames. - ? ? ? ? ? ? Landed on 0xAA for start with 76 byte packets (original design). Tried silence after first - ? ? ? ? ? ? byte and others, none worked well. The addition of checksum detection raised the issue as - ? ? ? ? ? ? bad frames previously went unnoticed. - ? ? ? ? ? - Added wrap around detection to see how many of the bad frames were the result of wrap arounds. - ? ? ? ? ? ? 76 byte status packets should look like AA AA AA ....... CR LF. Sometimes a sync issue - ? ? ? ? ? ? would occur and they would wrap around as AA AA ....... CR LF AA. - ? ? ? ? ? - Reduced V PA gauge minimum value from 35V to 30V to accommodate the 2K-FA - ? ? ? ? ? - ===Interim release (V1.2b2) to Nick Adrian VK4TUX - ? ? ? ? ? - Added checksum status indicator and shrunk USB Status indicator to make room - ? ? ? ? ? - Changed the checksum status indicator to a button to allow users to force a recovery from - ? ? ? ? ? ? buffer wrap around conditions. - ? ? ? ? ? - Disable hot switching from standby to operate while in TX mode - ? ? ? ? ? - Disable hot switching power on to power off while in TX mode - ? ? ? ? ? - Disable hot switching of power level (low, middle, maximum) while in TX mode - ? ? ? ? ? - Added clarification on displaying C or F inside the Initialization node On Tue, Jan 10, 2023 at 3:14 PM Ken Kayser < kxkayser@...> wrote: Hi Ron.? Found the culprit.? In my USB definition, I left the "Default response timeout"? ?to the default of 1000.? When I set it to 200, as in yours, all is great.? Fantastic flow.? Thanks again.
--
--
Nick
W7NIK?
|
Re: SPE Linear V1.1 flow uploaded to files section
Hi Ron? I don¡¯t know what version I am using , but it is working great. ?Spe2k? I have log graphic not sure what it does ? Maybe for 1k or 1.3 k
toggle quoted message
Show quoted text
On Jan 10, 2023, at 1:09 PM, Ronald Panetta, WB2WGH <ron@...> wrote:
? Ken, down in the shack. Yes, 200ms is what I have in the flow but depending on how you update the USB port configuration you may end up with the incorrect timeout. You should be polling at 250ms with a timeout of 200ms. That seems to work well. If you are interested in testing? a beta?for a future release, send me an email to my QRZ listed email address and I'll email you the beta flow. Below is a screen snapshot of the new dashboard and the current change history since V1.1.?
73, Ron WB2WGH
- ? ? ? ? ? - Corrected copy/paste typos for the 1.3K-FA power gauge maximum and color transitions. - ? ? ? ? ? - Added comments in the Read Me and "PWR Meter Range" with guidance on adjusting gauge - ? ? ? ? ? ? color transitions and maximums. - ? ? ? ? ? - Added debug node after buffer to string conversion - ? ? ? ? ? - Cleaned up and deleted historical commented out code from assorted function nodes - ? ? ? ? ? - Added capability to define exciter drive power level. User must customize the "Define - ? ? ? ? ? ? Exciter Drive Power" function node. - ? ? ? ? ? - Reworked case statement for band display. As mentioned above, the SPE returns band data - ? ? ? ? ? ? as string and numeric depending on band. Rather than mix string and numeric comparisons - ? ? ? ? ? ? in the case statement, using parseInt() which always yeilds a numeric, regardless of - ? ? ? ? ? ? input type, prior to the case, eliminates this issue. - ? ? ? ? ? - ===Interim release (V1.2b1) tofor "node-red-node-serialport" in the read me - ? ? ? ? ? - If operating mode (standby/operate) comes back with an unexpected character, force the - ? ? ? ? ? ? optional "Define Exciter Drive Power" to report zero since we don't know what state the - ? ? ? ? ? ? SPE is and we don't want to blow it up. - ? ? ? ? ? - Last byte of status messages were getting cut off (CR returned and LF dropped) due to - ? ? ? ? ? ? USB request node requesting 75 bytes instead of 76. Also changed "6, 76, Other Byte - ? ? ? ? ? ? Buffer?" switch node to for 76 byte buffers. - ? ? ? ? ? - As a FYI, even though the "Buffer Size?" switch node checks for smaller packets, they - ? ? ? ? ? ? never make it out of the "USB Request" node as with no consistent delimiter, a 76 byte - ? ? ? ? ? ? fixed length query is used and all smaller confirmations will result in a timeout. - ? ? ? ? ? - Consolidated logging flow variable initialization into the master initialization node - ? ? ? ? ? - Changed buffer length and checksum validation along with "SPE Responding" logic to - ? ? ? ? ? ? eliminate "USB Status" indicator momentary red blips when changing SPE settings. The short - ? ? ? ? ? ? packets resulting from a change (e.g., change power level) result in a valid but short - ? ? ? ? ? ? packet with timeouts as the 76 byte length is not achieved. Logic has to account for that - ? ? ? ? ? ? in both SPE powered on and off states. - ? ? ? ? ? - Flow layout cleanup (no functional changes) - ? ? ? ? ? - Discovered packets sometimes wrap around due to inability to detect start and end of frames. - ? ? ? ? ? ? Landed on 0xAA for start with 76 byte packets (original design). Tried silence after first - ? ? ? ? ? ? byte and others, none worked well. The addition of checksum detection raised the issue as - ? ? ? ? ? ? bad frames previously went unnoticed. - ? ? ? ? ? - Added wrap around detection to see how many of the bad frames were the result of wrap arounds. - ? ? ? ? ? ? 76 byte status packets should look like AA AA AA ....... CR LF. Sometimes a sync issue - ? ? ? ? ? ? would occur and they would wrap around as AA AA ....... CR LF AA. - ? ? ? ? ? - Reduced V PA gauge minimum value from 35V to 30V to accommodate the 2K-FA - ? ? ? ? ? - ===Interim release (V1.2b2) to Nick Adrian VK4TUX - ? ? ? ? ? - Added checksum status indicator and shrunk USB Status indicator to make room - ? ? ? ? ? - Changed the checksum status indicator to a button to allow users to force a recovery from - ? ? ? ? ? ? buffer wrap around conditions. - ? ? ? ? ? - Disable hot switching from standby to operate while in TX mode - ? ? ? ? ? - Disable hot switching power on to power off while in TX mode - ? ? ? ? ? - Disable hot switching of power level (low, middle, maximum) while in TX mode - ? ? ? ? ? - Added clarification on displaying C or F inside the Initialization node On Tue, Jan 10, 2023 at 3:14 PM Ken Kayser < kxkayser@...> wrote: Hi Ron.? Found the culprit.? In my USB definition, I left the "Default response timeout"? ?to the default of 1000.? When I set it to 200, as in yours, all is great.? Fantastic flow.? Thanks again.
--
--
Nick
W7NIK?
|
Scott!!!
Yeah! That's what I was searching!
Thks a lot!?
Now I try to customize the flow with my antenna and other info :-)
For the power on and off I'm able to use my moxa com port, when I shutdown the moxa the amplifier goes off.
Ron thank you very much too also for your helpful feedback.
Best 73
HB9EDM - Marco
|
Re: SPE Linear V1.1 flow uploaded to files section
Ken, down in the shack. Yes, 200ms is what I have in the flow but depending on how you update the USB port configuration you may end up with the incorrect timeout. You should be polling at 250ms with a timeout of 200ms. That seems to work well. If you are interested in testing? a beta?for a future release, send me an email to my QRZ listed email address and I'll email you the beta flow. Below is a screen snapshot of the new dashboard and the current change history since V1.1.?
73, Ron WB2WGH
 - ? ? ? ? ? - Corrected copy/paste typos for the 1.3K-FA power gauge maximum and color transitions. - ? ? ? ? ? - Added comments in the Read Me and "PWR Meter Range" with guidance on adjusting gauge - ? ? ? ? ? ? color transitions and maximums. - ? ? ? ? ? - Added debug node after buffer to string conversion - ? ? ? ? ? - Cleaned up and deleted historical commented out code from assorted function nodes - ? ? ? ? ? - Added capability to define exciter drive power level. User must customize the "Define - ? ? ? ? ? ? Exciter Drive Power" function node. - ? ? ? ? ? - Reworked case statement for band display. As mentioned above, the SPE returns band data - ? ? ? ? ? ? as string and numeric depending on band. Rather than mix string and numeric comparisons - ? ? ? ? ? ? in the case statement, using parseInt() which always yeilds a numeric, regardless of - ? ? ? ? ? ? input type, prior to the case, eliminates this issue. - ? ? ? ? ? - ===Interim release (V1.2b1) tofor "node-red-node-serialport" in the read me - ? ? ? ? ? - If operating mode (standby/operate) comes back with an unexpected character, force the - ? ? ? ? ? ? optional "Define Exciter Drive Power" to report zero since we don't know what state the - ? ? ? ? ? ? SPE is and we don't want to blow it up. - ? ? ? ? ? - Last byte of status messages were getting cut off (CR returned and LF dropped) due to - ? ? ? ? ? ? USB request node requesting 75 bytes instead of 76. Also changed "6, 76, Other Byte - ? ? ? ? ? ? Buffer?" switch node to for 76 byte buffers. - ? ? ? ? ? - As a FYI, even though the "Buffer Size?" switch node checks for smaller packets, they - ? ? ? ? ? ? never make it out of the "USB Request" node as with no consistent delimiter, a 76 byte - ? ? ? ? ? ? fixed length query is used and all smaller confirmations will result in a timeout. - ? ? ? ? ? - Consolidated logging flow variable initialization into the master initialization node - ? ? ? ? ? - Changed buffer length and checksum validation along with "SPE Responding" logic to - ? ? ? ? ? ? eliminate "USB Status" indicator momentary red blips when changing SPE settings. The short - ? ? ? ? ? ? packets resulting from a change (e.g., change power level) result in a valid but short - ? ? ? ? ? ? packet with timeouts as the 76 byte length is not achieved. Logic has to account for that - ? ? ? ? ? ? in both SPE powered on and off states. - ? ? ? ? ? - Flow layout cleanup (no functional changes) - ? ? ? ? ? - Discovered packets sometimes wrap around due to inability to detect start and end of frames. - ? ? ? ? ? ? Landed on 0xAA for start with 76 byte packets (original design). Tried silence after first - ? ? ? ? ? ? byte and others, none worked well. The addition of checksum detection raised the issue as - ? ? ? ? ? ? bad frames previously went unnoticed. - ? ? ? ? ? - Added wrap around detection to see how many of the bad frames were the result of wrap arounds. - ? ? ? ? ? ? 76 byte status packets should look like AA AA AA ....... CR LF. Sometimes a sync issue - ? ? ? ? ? ? would occur and they would wrap around as AA AA ....... CR LF AA. - ? ? ? ? ? - Reduced V PA gauge minimum value from 35V to 30V to accommodate the 2K-FA - ? ? ? ? ? - ===Interim release (V1.2b2) to Nick Adrian VK4TUX - ? ? ? ? ? - Added checksum status indicator and shrunk USB Status indicator to make room - ? ? ? ? ? - Changed the checksum status indicator to a button to allow users to force a recovery from - ? ? ? ? ? ? buffer wrap around conditions. - ? ? ? ? ? - Disable hot switching from standby to operate while in TX mode - ? ? ? ? ? - Disable hot switching power on to power off while in TX mode - ? ? ? ? ? - Disable hot switching of power level (low, middle, maximum) while in TX mode - ? ? ? ? ? - Added clarification on displaying C or F inside the Initialization node
On Tue, Jan 10, 2023 at 3:14 PM Ken Kayser < kxkayser@...> wrote: Hi Ron.? Found the culprit.? In my USB definition, I left the "Default response timeout"? ?to the default of 1000.? When I set it to 200, as in yours, all is great.? Fantastic flow.? Thanks again.
|
Re: SPE Linear V1.1 flow uploaded to files section
Ken, glad you got the issue resolved.? I think I reworked the timing on a pending update. I'll check that when I'm down in the shack.
73, Ron WB2WGH?
On Tue, Jan 10, 2023, 3:14 PM Ken Kayser < kxkayser@...> wrote: Hi Ron.? Found the culprit.? In my USB definition, I left the "Default response timeout"? ?to the default of 1000.? When I set it to 200, as in yours, all is great.? Fantastic flow.? Thanks again.
|
Hi all
I know a while back there was talk about a flow for an Alpha 9500.
Before I venture down the road with investigating if Node Red will work with the 9500 I figure I¡¯d ask here if anyone has done any work to integrate it.
73
Dave wo2x
Sent from my waxed string and tin cans.
|
Re: SPE Linear V1.1 flow uploaded to files section
Hi Ron.? Found the culprit.? In my USB definition, I left the "Default response timeout"? ?to the default of 1000.? When I set it to 200, as in yours, all is great.? Fantastic flow.? Thanks again.
|
Re: Field Day (Contesting) Dashboard Install Video
Nothing specifically for WFD but we will have a dedicated dashboard for Field Day 2023. We are working on a new release right now so I would suggest upgrading after we publish the new flow in a couple of weeks.
Kyle
AA0Z
|
Scott, thanks for providing thus to Marco. That should provide a pretty good baseline for the 1K. 73, Ron WB2WGH?
On Tue, Jan 10, 2023, 11:16 AM Scott Dupuie < groupsio@...> wrote: Marco,
Here is my flow for the 1K-FA. It is a totally different protocol than for the 1.3K and later.
You need to change the serial port nodes to match your serial port path.
I am not currently using a python script to turn on the amplifier as others have done because it causes instability in my node-red installation. Either Node-RED or Mac OS X does not appear to like you altering the DTR line outside of the Node-RED application. So, presently I do not have a solution for turning on the amplifier. I plan to use a 12V trigger in the DB15 port controlled by the ON/OFF switch in my flow, but that is not done yet.
My flow is set up to control the frequency of the 1K-FA from Node-RED rather than from the radio directly. If this is not how you want to use it, you will need to modify the flow. The inputs and outputs to this flow are to interface with my other gear. You can simply leave them unconnected and the flow should still work.
73,
Scott
AK5SD
|
Marco,
Here is my flow for the 1K-FA. It is a totally different protocol than for the 1.3K and later.
You need to change the serial port nodes to match your serial port path.
I am not currently using a python script to turn on the amplifier as others have done because it causes instability in my node-red installation. Either Node-RED or Mac OS X does not appear to like you altering the DTR line outside of the Node-RED application. So, presently I do not have a solution for turning on the amplifier. I plan to use a 12V trigger in the DB15 port controlled by the ON/OFF switch in my flow, but that is not done yet.
My flow is set up to control the frequency of the 1K-FA from Node-RED rather than from the radio directly. If this is not how you want to use it, you will need to modify the flow. The inputs and outputs to this flow are to interface with my other gear. You can simply leave them unconnected and the flow should still work.
73,
Scott
AK5SD
|
Dave wo2x
Ken Kayser
Kyle AA0Z
Scott Dupuie