AA0Z KumoSpace Node Red meeting this Thursday evening at 9 p.m. Eastern U.S.
Kyle, AA0Z, mentioned having a KumoSpace Node Red hang out/ meeting this coming Thursday evening at 9 p.m. Eastern U.S./6 p.m. Pacific.
Come join us and bring your Node Red questions, suggestions, and expertise.
Kyle,
Please post a link for the KumoSpace meet.
73 on behalf of the admins,
Dave wo2x
|
Re: Node-Red V3.x: Junction Node, Not Backward Compatible
Hi Alan,
Thanks. Remember to not do things at 3:30 a.m.
Added the missing node. Cleaned ALL remnants of unused nodes, groups, spacers, etc. exported unused flows and deleted all remnants of them. Got Node Red nice and clean, then exported the four flows and uploaded as one json along with instructions. Now v17. Going to nap for a bit.?
I suggest you upload your standalone version which can work without PG XL or Flex Radio flows and notate that in description. I removed the MQTT stuff before upload as most users are on one Node Red server.
The six meter issue appears the tuner does like the complex impedance it sees from my Yagi or “optimized G5RV” but does work fine into Bird dummy load. I have looked at messages from tuner and do not see any message indicating failed tuning. I have sent an email to Tuner Genius alpha list as well as Marko. The status message shows tuning=1 while tuning and 0 when not.?
Maybe future enhancement to have two triggers. Store SWR using the M| message but use tuning 1/0 to know when the tune step finishes, so somehow use the M| message to a temp SWR variable and the tuning value. If tuning value = o and temp SWR message length > 0 then continue as normal but if tuning = 0 and temp SWR message length <1 then set No Tune for SWR message. This would require a lot of work plus setting the temp SWR to “” before start of tune. Might be better off if tuning hangs then may just be antenna doesn’t like that band and move on.
I think we’ve exhausted enough time on this. Let’s see what shakes out.?
You’ve done a ton of heavy lifting, including catching my errors that slip through.
Thanks
toggle quoted message
Show quoted text
On Jul 24, 2022, at 11:11 AM, Alan Blind, WA9WUD <a.alan.blind@...> wrote:
?Here is a screenshot, Node-Red, v2 of the "removed" junction node. ?As Dave said, after the Junction node was removed. Node-Red all good, after I deleted the node. 
|
Hi All ? I just posted v17 of the Tuner Sweep package (Flex Radio, PG XL, TG XL, and Tuner Sweep flows). Found a problem when I modified my flows in Node Red version 3 then Alan opered it in Node Red version 2 and sent it back to me. It is now fixed and compatible with either NR versions 2 or 3. ? FYI, I had used a junction node in my Flex Radio flow (new node part of Node Red v3). The node was deleted by NR v2 since it is not supported but the connecting nodes were left unconnected. ? Sorry about that. Don’t do things at 3:30 a.m. ! ? 73 Dave wo2x ?
|
File /!1! Flows by Type/TUNERS/Tuner Sweep v 17 package.zip uploaded
#file-notice
The following files and folders have been uploaded to
the Files area of the [email protected] group.
By: David De Coons wo2x <RocketNJ@...>
Description:
Another update for the Tuner Sweep flow. Now 20 WPM CWID and several bug fixes. Updated Tuner Sweep flow to easily program the memories on the Flex Tuner Genius. In the zip file is a json which contains the Flex Radio, Power Genius XL, Tuner Genius XL, and Tuner Sweep flows. These flows have link nodes between the flows and should be used together. Also attached is a Tuner Sweep v16 Instructions pdf file which explains how to set up each flow and how to use the Tuner Sweep flow. There is also a demonstration video available at https://youtu.be/Tl-e5CX38tw We have made several revisions of this, including having links in and out of the Flex Radio, Power Genius XL, and Tuner Genius XL flows. We have added CW ID @ 30 wpm to ID after each tune. It will reset the CW speed to your previous setting once completed. If you have the Flex Radio, Power Genius, and Tuner Genius flows installed, it may be easier to uninstall them then deploy in the Node Red editor. Then import the Tuner Sweep Package v15.json file. This will import the Flex Radio, Power Genius, Tuner Genius, and Tuner Sweep flows, along with the links between the four flows. Many thanks to Alan, WA9WUD for his initial idea and most of the programming on this flow.
|
Re: Node-Red V3.x: Junction Node, Not Backward Compatible
Maybe a good subject for this Thursday’s AA0Z Kumospace Meeting. ?
How to upgrade Node Red and upgrade your nodes.
toggle quoted message
Show quoted text
On Jul 24, 2022, at 11:11 AM, Alan Blind, WA9WUD <a.alan.blind@...> wrote:
?Here is a screenshot, Node-Red, v2 of the "removed" junction node. ?As Dave said, after the Junction node was removed. Node-Red all good, after I deleted the node. 
|
Re: Node-Red V3.x: Junction Node, Not Backward Compatible
Here is a screenshot, Node-Red, v2 of the "removed" junction node. ?As Dave said, after the Junction node was removed. Node-Red all good, after I deleted the node. 
|
Re: Node-Red V3.x: Junction Node, Not Backward Compatible
Dave, FYI.
My experience, was using the Tuner Sweep upload from this morning, I loaded it to a V2 Node-Red, and even thought the junction node was removed, V2 complained there was an unsupported node.
I then found where the junction node, was removed from, and found what looked like a "disabled" junction node, but it was not wired in. ?I deleted the disabled junction node, and all was good, no more complaining from Node-Red v2.
Alan
|
Re: Node-Red V3.x: Junction Node, Not Backward Compatible
Also note - the v16 of the flow posted last night does not use the junction node.
Several of use have upgraded without issue to Node Red v3. I suggest users upgrade so in case someone writes a flow based on the new features in NR 3 you can use those flows without issue.
After upgrading to Node Red version 3 go into the Palette Manager and update any nodes that need to be upgraded.
73
toggle quoted message
Show quoted text
On Jul 24, 2022, at 9:15 AM, Alan Blind, WA9WUD <a.alan.blind@...> wrote:
?My "test" RPI is running Node-Red v3. ?My production NUC Ubuntu machine is running Node-Red v2.
I used the new "Junction" node on my V3 Node-Red and then tried loading it to my V2 Node-Red. ? It blew up!
Caution---- the new Node-Red v3 "Junction" node is not backward compatible.
Also, I found that simply removing the Junction in V3 did not wholly remove the node when I again tried to install it in V2. ? What a mess.
If you load Dave's Tuner Sweep Flow on a v2 Node-Red, you will need to remove the remnants of the Junction Node manually.
Alan. WA9WUD
|
Node-Red V3.x: Junction Node, Not Backward Compatible
My "test" RPI is running Node-Red v3. ?My production NUC Ubuntu machine is running Node-Red v2.
I used the new "Junction" node on my V3 Node-Red and then tried loading it to my V2 Node-Red. ? It blew up!
Caution---- the new Node-Red v3 "Junction" node is not backward compatible.
Also, I found that simply removing the Junction in V3 did not wholly remove the node when I again tried to install it in V2. ? What a mess.
If you load Dave's Tuner Sweep Flow on a v2 Node-Red, you will need to remove the remnants of the Junction Node manually.
Alan. WA9WUD
|
Tuner Sweep package v16 uploaded
Hi All ? I uploaded the Tuner Sweep v16 package which includes the Flex Radio, PG XL, and TG XL flows as well as Alan’s Tuner Sweep flow. ? Alan and I did a lot of debugging with this release. The CW ID speed is now 20 WPM. You can change the speed in the flow with the Node Red editor if needed. ? I do not have a 6 meter antenna so I was testing with my 5 band Yagi and G5RV. At certain points the complex impedance was more than the tuner would handle so as it was tuning and got to that spot the automatic tuning would stop. So if you see that, check your antenna. It may not be good on some bands. G5RV type antennas are famous for not liking 15 meters. This drove me nuts trying to debug since the tuner does not give a failed message back to let you know it cannot tune the antenna at a certain point. ? Instructions are included in the zip file along with the json that contains the 4 flows. /g/nodered-hamradio/files/%211%21%20Flows%20by%20Type/TUNERS/Tuner%20Sweep%20v%2016%20Package.zip ? ? Enjoy! ? Dave wo2x ? ? ?
|
File /!1! Flows by Type/TUNERS/Tuner Sweep v 16 Package.zip uploaded
#file-notice
The following files and folders have been uploaded to
the Files area of the [email protected] group.
By: David De Coons wo2x <RocketNJ@...>
Description:
Another update for the Tuner Sweep flow. Now 20 WPM CWID and several bug fixes.
Updated Tuner Sweep flow to easily program the memories on the Flex Tuner Genius. In the zip file is a json which contains the Flex Radio, Power Genius XL, Tuner Genius XL, and Tuner Sweep flows. These flows have link nodes between the flows and should be used together. Also attached is a Tuner Sweep v16 Instructions pdf file which explains how to set up each flow and how to use the Tuner Sweep flow. There is also a demonstration video available at https://youtu.be/Tl-e5CX38tw
We have made several revisions of this, including having links in and out of the Flex Radio, Power Genius XL, and Tuner Genius XL flows. We have added CW ID @ 30 wpm to ID after each tune. It will reset the CW speed to your previous setting once completed. If you have the Flex Radio, Power Genius, and Tuner Genius flows installed, it may be easier to uninstall them then deploy in the Node Red editor. Then import the Tuner Sweep Package v15.json file. This will import the Flex Radio, Power Genius, Tuner Genius, and Tuner Sweep flows, along with the links between the four flows.
Many thanks to Alan, WA9WUD for his initial idea and most of the programming on this flow.
|
Re: File /!1! Flows by Type/TUNERS/Tuner Sweep package v15.zip uploaded
#file-notice
Hi All, ? Alan did a major rewrite of the flow to clean it up quite a bit. More efficient and Almost 100% The directions are the same in the version 14 and I will update the document One more issue with 6 meters I am tracking down now. ? The nice thing is once this is run on each band you shouldn’t need to touch the TG XL tuning unless something changes (ice, etc) ? We’re going to release two different versions of the flow. One will have the Flex Radio, PG XL, and TG XL flows included while the other will be a standalone flow for those that do not have a Flex amp. ? The flow can be adapted to use with radios other than Flex. The “issue” will be the automatic CW ID after each tune. ? 73 Dave wo2x ? ?
toggle quoted message
Show quoted text
From: [email protected] < [email protected]> On Behalf Of Mike / K5JR Sent: Friday, July 22, 2022 10:24 PM To: [email protected]Subject: Re: [nodered-hamradio] File /!1! Flows by Type/TUNERS/Tuner Sweep package v15.zip uploaded #file-notice ? Thanks. The ability for the user to set the speed (set once and forget) is a good thing. I don’t believe that all countries have a 20 wpm limit. Some are more (or no limit) and some may be less.?
On Jul 22, 2022, at 8:30 PM, David De Coons wo2x <RocketNJ@...> wrote:
?It is VERY easy to edit one node and change CW to 20 won. I will test the “popping” Bret reported then change the CW speed. Look for v16 tomorrow. Reason for the high number is my standalone Flex Radio flow was v11 and I didn’t want to start at v1 and confuse people.? Once the rest of the bugs are shaken out I will update the standalone FlexRadio, PG XL and TG XL flows.? I already have an idea for the popping. I think it has something to do with too many things subscribed to the radio simultaneously. I think the flow is sending TCP commands to the radio after the tuning is complete. Should be easy to track down.? Dave wo2x Sent from my waxed string and tin cans.?
On Jul 22, 2022, at 8:21 PM, Chuck W9WLX <w9wlx@...> wrote:
?A lot of great work done here, thanks!? Here's the tough part of the message:? A CW ID at 30 WPM does not solve the original issue since it is not a legal CW ID in this circumstance.?
Here is a snip of Part 97.119(b)
(b) The call sign must be transmitted with an emission authorized for the transmitting channel in one of the following ways: (1) By a CW emission. When keyed by an automatic device used only for identification, the speed must not exceed 20 words per minute; (2) By a phone emission in the English language. Use of a phonetic alphabet as an aid for correct station identification is encouraged; (3) By a RTTY emission using a specified digital code when all or part of the communications are transmitted by a RTTY or data emission; (4) By an image emission conforming to the applicable transmission standards, either color or monochrome, of of the FCC Rules when all or part of the communications are transmitted in the same image emission
|
Re: File /!1! Flows by Type/TUNERS/Tuner Sweep package v15.zip uploaded
#file-notice
I already do a sub meter all in my Flex Radio flow so using the second request node now has two non clients subscribed to meters.?
Dave wo2x Sent from my waxed string and tin cans.?
toggle quoted message
Show quoted text
On Jul 23, 2022, at 6:27 AM, Alan Blind, WA9WUD <a.alan.blind@...> wrote:
? I prefer the Tuner Flow to be able to work stand-alone if someone prefers to use it without interfacing with the WO2X package (such as me). ?
Here is my suggestion to reduce sending sub-commands, particularly?the "sub meter all" command:
Also, there are two triggers into the "Tune Off" command function, "gate closed" and "reset defaults".
I wanted to send the tune off command when the gate is closed, in case the Flex got stuck in tune, so when the gate is closed, it send a tune off command.
We can remove the trigger from "reset defaults" as it is redundant now to "gate closed" (since we added the trigger from gate closed to reset defaults.
Alan
On Fri, Jul 22, 2022 at 11:24 PM David De Coons wo2x < RocketNJ@...> wrote: Hi Mike?
In the CWX section of the flow (in the editor) you can open the function node that sets CWX parameters and change speed. I’d rather not have it on the dash but the user is welcome to change it if needed.?
I changed the speed to 20 won as default and think I have a fox in place for the popping Bret was experiencing. I have sent him a flow to test the popping. If all goes well I will post version 16 tomorrow morning.?
For those curious, there is a link from the Tuner Sweep flow to the Flex Radio flow Flex Tequest node (where all commands to radio are sent). It goes through a gate node on the Tuner Sweep flow. The gate was opening, allowing communications to the radio during the tuning process but the gate was not closing when finished. It is now, so there should be no data from Tuner Sweep flow to the radio when the Radio Gate button is red in Tuner Sweep Control dashboard.?
The Tuner Sweep flow is pretty complicated as it has to handle different scenarios such as tuner in circuit, tuner bypassed (either a segment is bypassed or manually bypassed, and low power, meaning tuner does not see enough RF (tune power low or wrong TX ant). Luckily Alan built the flow in blocks so it makes troubleshooting a little easier.?
73 Dave wo2x Sent from my waxed string and tin cans.? ?Thanks. The ability for the user to set the speed (set once and forget) is a good thing. I don’t believe that all countries have a 20 wpm limit. Some are more (or no limit) and some may be less.? tnx Mike / K5JR Alpharetta GA On Jul 22, 2022, at 8:30 PM, David De Coons wo2x < RocketNJ@...> wrote: ?It is VERY easy to edit one node and change CW to 20 won. I will test the “popping” Bret reported then change the CW speed. Look for v16 tomorrow. Reason for the high number is my standalone Flex Radio flow was v11 and I didn’t want to start at v1 and confuse people.?
Once the rest of the bugs are shaken out I will update the standalone FlexRadio, PG XL and TG XL flows.?
I already have an idea for the popping. I think it has something to do with too many things subscribed to the radio simultaneously. I think the flow is sending TCP commands to the radio after the tuning is complete. Should be easy to track down.?
Thanks? Dave wo2x Sent from my waxed string and tin cans.? On Jul 22, 2022, at 8:21 PM, Chuck W9WLX <w9wlx@...> wrote:
?A lot of great work done here, thanks!? Here's the tough part of the message:? A CW ID at 30 WPM does not solve the original issue since it is not a legal CW ID in this circumstance.? Here is a snip of Part 97.119(b)
(b) The call sign must be transmitted with an emission authorized for the transmitting channel in one of the following ways:
(1) By a CW emission. When keyed by an automatic device used only for identification, the speed must not exceed 20 words per minute;
(2) By a phone emission in the English language. Use of a phonetic alphabet as an aid for correct station identification is encouraged;
(3) By a RTTY emission using a specified digital code when all or part of the communications are transmitted by a RTTY or data emission;
(4) By an image emission conforming to the applicable transmission standards, either color or monochrome, of of the FCC Rules when all or part of the communications are transmitted in the same image emission
|
Re: File /!1! Flows by Type/TUNERS/Tuner Sweep package v15.zip uploaded
#file-notice
I prefer the Tuner Flow to be able to work stand-alone if someone prefers to use it without interfacing with the WO2X package (such as me). ?
Here is my suggestion to reduce sending sub-commands, particularly?the "sub meter all" command:
Also, there are two triggers into the "Tune Off" command function, "gate closed" and "reset defaults".
I wanted to send the tune off command when the gate is closed, in case the Flex got stuck in tune, so when the gate is closed, it send a tune off command.
We can remove the trigger from "reset defaults" as it is redundant now to "gate closed" (since we added the trigger from gate closed to reset defaults.
Alan
On Fri, Jul 22, 2022 at 11:24 PM David De Coons wo2x < RocketNJ@...> wrote: Hi Mike?
In the CWX section of the flow (in the editor) you can open the function node that sets CWX parameters and change speed. I’d rather not have it on the dash but the user is welcome to change it if needed.?
I changed the speed to 20 won as default and think I have a fox in place for the popping Bret was experiencing. I have sent him a flow to test the popping. If all goes well I will post version 16 tomorrow morning.?
For those curious, there is a link from the Tuner Sweep flow to the Flex Radio flow Flex Tequest node (where all commands to radio are sent). It goes through a gate node on the Tuner Sweep flow. The gate was opening, allowing communications to the radio during the tuning process but the gate was not closing when finished. It is now, so there should be no data from Tuner Sweep flow to the radio when the Radio Gate button is red in Tuner Sweep Control dashboard.?
The Tuner Sweep flow is pretty complicated as it has to handle different scenarios such as tuner in circuit, tuner bypassed (either a segment is bypassed or manually bypassed, and low power, meaning tuner does not see enough RF (tune power low or wrong TX ant). Luckily Alan built the flow in blocks so it makes troubleshooting a little easier.?
73 Dave wo2x Sent from my waxed string and tin cans.? ?Thanks. The ability for the user to set the speed (set once and forget) is a good thing. I don’t believe that all countries have a 20 wpm limit. Some are more (or no limit) and some may be less.? tnx Mike / K5JR Alpharetta GA On Jul 22, 2022, at 8:30 PM, David De Coons wo2x < RocketNJ@...> wrote: ?It is VERY easy to edit one node and change CW to 20 won. I will test the “popping” Bret reported then change the CW speed. Look for v16 tomorrow. Reason for the high number is my standalone Flex Radio flow was v11 and I didn’t want to start at v1 and confuse people.?
Once the rest of the bugs are shaken out I will update the standalone FlexRadio, PG XL and TG XL flows.?
I already have an idea for the popping. I think it has something to do with too many things subscribed to the radio simultaneously. I think the flow is sending TCP commands to the radio after the tuning is complete. Should be easy to track down.?
Thanks? Dave wo2x Sent from my waxed string and tin cans.? On Jul 22, 2022, at 8:21 PM, Chuck W9WLX <w9wlx@...> wrote:
?A lot of great work done here, thanks!? Here's the tough part of the message:? A CW ID at 30 WPM does not solve the original issue since it is not a legal CW ID in this circumstance.? Here is a snip of Part 97.119(b)
(b) The call sign must be transmitted with an emission authorized for the transmitting channel in one of the following ways:
(1) By a CW emission. When keyed by an automatic device used only for identification, the speed must not exceed 20 words per minute;
(2) By a phone emission in the English language. Use of a phonetic alphabet as an aid for correct station identification is encouraged;
(3) By a RTTY emission using a specified digital code when all or part of the communications are transmitted by a RTTY or data emission;
(4) By an image emission conforming to the applicable transmission standards, either color or monochrome, of of the FCC Rules when all or part of the communications are transmitted in the same image emission
|
Re: File /!1! Flows by Type/TUNERS/Tuner Sweep package v15.zip uploaded
#file-notice
Hi Mike?
In the CWX section of the flow (in the editor) you can open the function node that sets CWX parameters and change speed. I’d rather not have it on the dash but the user is welcome to change it if needed.?
I changed the speed to 20 won as default and think I have a fox in place for the popping Bret was experiencing. I have sent him a flow to test the popping. If all goes well I will post version 16 tomorrow morning.?
For those curious, there is a link from the Tuner Sweep flow to the Flex Radio flow Flex Tequest node (where all commands to radio are sent). It goes through a gate node on the Tuner Sweep flow. The gate was opening, allowing communications to the radio during the tuning process but the gate was not closing when finished. It is now, so there should be no data from Tuner Sweep flow to the radio when the Radio Gate button is red in Tuner Sweep Control dashboard.?
The Tuner Sweep flow is pretty complicated as it has to handle different scenarios such as tuner in circuit, tuner bypassed (either a segment is bypassed or manually bypassed, and low power, meaning tuner does not see enough RF (tune power low or wrong TX ant). Luckily Alan built the flow in blocks so it makes troubleshooting a little easier.?
73 Dave wo2x Sent from my waxed string and tin cans.?
toggle quoted message
Show quoted text
On Jul 22, 2022, at 10:24 PM, Mike / K5JR <k5jr.flex@...> wrote:
? Thanks. The ability for the user to set the speed (set once and forget) is a good thing. I don’t believe that all countries have a 20 wpm limit. Some are more (or no limit) and some may be less.? tnx Mike / K5JR Alpharetta GA
On Jul 22, 2022, at 8:30 PM, David De Coons wo2x <RocketNJ@...> wrote:
? It is VERY easy to edit one node and change CW to 20 won. I will test the “popping” Bret reported then change the CW speed. Look for v16 tomorrow. Reason for the high number is my standalone Flex Radio flow was v11 and I didn’t want to start at v1 and confuse people.?
Once the rest of the bugs are shaken out I will update the standalone FlexRadio, PG XL and TG XL flows.?
I already have an idea for the popping. I think it has something to do with too many things subscribed to the radio simultaneously. I think the flow is sending TCP commands to the radio after the tuning is complete. Should be easy to track down.?
Thanks? Dave wo2x Sent from my waxed string and tin cans.? On Jul 22, 2022, at 8:21 PM, Chuck W9WLX <w9wlx@...> wrote:
?A lot of great work done here, thanks!? Here's the tough part of the message:? A CW ID at 30 WPM does not solve the original issue since it is not a legal CW ID in this circumstance.? Here is a snip of Part 97.119(b)
(b) The call sign must be transmitted with an emission authorized for the transmitting channel in one of the following ways:
(1) By a CW emission. When keyed by an automatic device used only for identification, the speed must not exceed 20 words per minute;
(2) By a phone emission in the English language. Use of a phonetic alphabet as an aid for correct station identification is encouraged;
(3) By a RTTY emission using a specified digital code when all or part of the communications are transmitted by a RTTY or data emission;
(4) By an image emission conforming to the applicable transmission standards, either color or monochrome, of of the FCC Rules when all or part of the communications are transmitted in the same image emission
|
Re: File /!1! Flows by Type/TUNERS/Tuner Sweep package v15.zip uploaded
#file-notice
Thanks. The ability for the user to set the speed (set once and forget) is a good thing. I don’t believe that all countries have a 20 wpm limit. Some are more (or no limit) and some may be less.? tnx Mike / K5JR Alpharetta GA
toggle quoted message
Show quoted text
On Jul 22, 2022, at 8:30 PM, David De Coons wo2x <RocketNJ@...> wrote: ? It is VERY easy to edit one node and change CW to 20 won. I will test the “popping” Bret reported then change the CW speed. Look for v16 tomorrow. Reason for the high number is my standalone Flex Radio flow was v11 and I didn’t want to start at v1 and confuse people.?
Once the rest of the bugs are shaken out I will update the standalone FlexRadio, PG XL and TG XL flows.?
I already have an idea for the popping. I think it has something to do with too many things subscribed to the radio simultaneously. I think the flow is sending TCP commands to the radio after the tuning is complete. Should be easy to track down.?
Thanks? Dave wo2x Sent from my waxed string and tin cans.? On Jul 22, 2022, at 8:21 PM, Chuck W9WLX <w9wlx@...> wrote:
?A lot of great work done here, thanks!? Here's the tough part of the message:? A CW ID at 30 WPM does not solve the original issue since it is not a legal CW ID in this circumstance.? Here is a snip of Part 97.119(b)
(b) The call sign must be transmitted with an emission authorized for the transmitting channel in one of the following ways:
(1) By a CW emission. When keyed by an automatic device used only for identification, the speed must not exceed 20 words per minute;
(2) By a phone emission in the English language. Use of a phonetic alphabet as an aid for correct station identification is encouraged;
(3) By a RTTY emission using a specified digital code when all or part of the communications are transmitted by a RTTY or data emission;
(4) By an image emission conforming to the applicable transmission standards, either color or monochrome, of of the FCC Rules when all or part of the communications are transmitted in the same image emission
|
Re: File /!1! Flows by Type/TUNERS/Tuner Sweep package v15.zip uploaded
#file-notice
It is VERY easy to edit one node and change CW to 20 won. I will test the “popping” Bret reported then change the CW speed. Look for v16 tomorrow. Reason for the high number is my standalone Flex Radio flow was v11 and I didn’t want to start at v1 and confuse people.?
Once the rest of the bugs are shaken out I will update the standalone FlexRadio, PG XL and TG XL flows.?
I already have an idea for the popping. I think it has something to do with too many things subscribed to the radio simultaneously. I think the flow is sending TCP commands to the radio after the tuning is complete. Should be easy to track down.?
Thanks? Dave wo2x Sent from my waxed string and tin cans.?
toggle quoted message
Show quoted text
On Jul 22, 2022, at 8:21 PM, Chuck W9WLX <w9wlx@...> wrote:
?A lot of great work done here, thanks!? Here's the tough part of the message:? A CW ID at 30 WPM does not solve the original issue since it is not a legal CW ID in this circumstance.? Here is a snip of Part 97.119(b)
(b) The call sign must be transmitted with an emission authorized for the transmitting channel in one of the following ways:
(1) By a CW emission. When keyed by an automatic device used only for identification, the speed must not exceed 20 words per minute;
(2) By a phone emission in the English language. Use of a phonetic alphabet as an aid for correct station identification is encouraged;
(3) By a RTTY emission using a specified digital code when all or part of the communications are transmitted by a RTTY or data emission;
(4) By an image emission conforming to the applicable transmission standards, either color or monochrome, of of the FCC Rules when all or part of the communications are transmitted in the same image emission
|
Re: File /!1! Flows by Type/TUNERS/Tuner Sweep package v15.zip uploaded
#file-notice
A lot of great work done here, thanks!? Here's the tough part of the message:? A CW ID at 30 WPM does not solve the original issue since it is not a legal CW ID in this circumstance.? Here is a snip of Part 97.119(b)
(b) The call sign must be transmitted with an emission authorized for the transmitting channel in one of the following ways:
(1) By a CW emission. When keyed by an automatic device used only for identification, the speed must not exceed 20 words per minute;
(2) By a phone emission in the English language. Use of a phonetic alphabet as an aid for correct station identification is encouraged;
(3) By a RTTY emission using a specified digital code when all or part of the communications are transmitted by a RTTY or data emission;
(4) By an image emission conforming to the applicable transmission standards, either color or monochrome, of of the FCC Rules when all or part of the communications are transmitted in the same image emission
|
Re: File /!1! Flows by Type/TUNERS/Tuner Sweep package v15.zip uploaded
#file-notice
Hi Dave and Nice update, Thanks a lot
I have a lot of Poping in the RX audio after I do a "Tune Sweep" until I power down the Pi, then powering it back up I have not popping until I do another "Tune Sweep" The only time I usually get the Poping is when the Node-Red makes a connection when It logs into the radio like normal UNTIL I so another sweep. This reminds me of the early days of NOde-Red and FRStack last year or when ever it was when it was updating to the radio all the time and not being turned off.
The old version 14 didn't have the popping unless it was changing states on the radio RX / TX.
WOOPS I think I had a LINK wrong in the FlexRadio flow and had a loop going back to the on the "FlexRadio request Input" It's not connected to anything I guess.
Sorry?
Thanks again for all your long hours working on this and hope this helps
--
YMMV
73
Bret
WX7Y
|
New Tuner Sweep flow package with several updates, enhancements, and bug fixes uploaded
Hi All
Alan, WA9WUD and I spent quite a bit of time improving his Tuner Sweep flow. Alan added the ability to automatically send your call as CW @ 30 wpm after each tune to keep in line with FCC guidelines. There are a number of enhancements and fixes including the ability to save the tuner sweep results and retrieve them at a later date along with changing the default path to save the results.
The package which contains my Flex Radio, PG XL, TG XL and thye Tuner Sweep flows along with a pdf with instructions can be downloaded from?/g/nodered-hamradio/files/%211%21%20Flows%20by%20Type/TUNERS/Tuner%20Sweep%20package%20v15.zip
I have made a demo video showing the Tuner Sweep flow in operation on 12 and 40 meters. Note - on 40 I have my antenna bypassed in a segment of the band in the tuner setup.
The video at this time is still in the process of rendering for higher definition on YouTube.
I am posting the instructions at the end of this email also.
Special thanks to Alan, WA9WUD for his idea for this flow and doing most of the programming.
73
Dave wo2x
Tuner Sweep v 15 Instructions
?
First, thanks to Alan, WA9WUD for doing most of the work on this flow. It was his original idea to put together a flow to automate the process of training the Tuner Genius XL memories.
A companion video is located at https://youtu.be/Tl-e5CX38tw
We have made several revisions of this, including having links in and out of the Flex Radio, Power Genius XL, and Tuner Genius XL flows. We have added CW ID @ 30 wpm to ID after each tune. It will reset the CW speed to your previous setting once completed.
If you have the Flex Radio, Power Genius, and Tuner Genius flows installed, it may be easier to uninstall them then deploy in the Node Red editor. Then import the Tuner Sweep Package v15.json file. This will import the Flex Radio, Power Genius, Tuner Genius, and Tuner Sweep flows, along with the links between the four flows.
In the Flex Radio flow, set the IP address of the radio in the Ping node.
In the Power Genius flow, set the IP address of the PG XL (as seen on front of amp or in PG XL app)
In the Tuner Genius flow, set the IP address of the TG XL (as seen on front of tuner or in TG XL app)
In the Tuner Sweep flow set the path to save sweep results. It defaults to /home/pi/Documents/tuner_sweeps/? , Make sure you change it if your user name for the Pi is different than the default pi.
Set radio TUNE power in the TX Band Settings table (in whatever client you use to connect to the radio) to 25 watts per band. This will ensure enough power for the TG XL to tune properly.
Once all above is done deploy in the editor.
?
Using the Tuner Sweep Flow with full band coverage
1.?????? On the Tuner Sweep dashboard there is a text entry window where you need to enter your callsign then press enter. This sets the CW ID that is sent out after each tune to keep within the FCC rules.
2.?????? Use the Band Select pulldown to select a band you want to have auto tune.
3.?????? Click the red Radio Gate Closed. It will turn green and say Radio Gate Open.
4.?????? You should see your callsign in the top box and band to be tuned in next line. In the green box under Reset Defaults you should see the start and end frequency range. You will also see the default steps (memories) for that band. Smaller segment bands such as 12, 17, and 30 meters use 2 steps as default while larger bands such as 10, 40 and 80 use all ten. Please note – the tuner supports up to ten memories per band per antenna with a maximum of four antennas per band. 160 meter can have up to 20 memories per antenna.
5.?????? Click the red Start Sweep button.
6.?????? Once completed, the Tuner Sweep Graph will show the results. The SWR bars are color coded. Blue indicates the tuner was in circuit for that frequency. Green indicates the tuner was bypassed for that frequency and red indicates the final SWR for that frequency was greater than 2.0:1 . Please note – If you get SWR-0 in red then the tuner is not detecting enough power from the radio. Check your TUNE power setting as well as your TX antenna setting.
7.?????? Skip down to Saving Sweep Results section
?
Using the Tuner Sweep Flow using custom start and stop frequencies
1.?????? On the Tuner Sweep dashboard there is a text entry window where you need to enter your callsign then press enter. This sets the CW ID that is sent out after each tune to keep within the FCC rules.
2.?????? Use the Band Select pulldown to select a band you want to have auto tune.
3.?????? Click the Start Frequency Enter box and enter a start frequency in MHz then press Enter.
4.?????? Click the Stop Frequency Enter box and enter a start frequency in MHz then press Enter.
5.?????? Select number of tuning memories using the Steps pull down if you want to select the number of memories lower than default for that band.
6.?????? Click the red Radio Gate Closed. It will turn green and say Radio Gate Open.
7.?????? You should see your callsign in the top box and band to be tuned in next line. In the green box under Reset Defaults you should see the start and end frequency range. You will also see the default steps (memories) for that band. Smaller segment bands such as 12, 17, and 30 meters use 2 steps as default while larger bands such as 10, 40 and 80 use all ten. Please note – the tuner supports up to ten memories per band per antenna with a maximum of four antennas per band. 160 meter can have up to 20 memories per antenna.
8.?????? Click the red Start Sweep button.
9.?????? Once completed, the Tuner Sweep Graph will show the results. The SWR bars are color coded. Blue indicates the tuner was in circuit for that frequency. Green indicates the tuner was bypassed for that frequency and red indicates the final SWR for that frequency was greater than 2.0:1
10.?? Skip down to Saving Sweep Results section
?
Saving Tune Sweep results
1.?????? Upon completion of the tuner sweep, the Enter Sweep Name window will default to the band, date and time of the sweep. Example 12M_2022_7_20_22_15
2.?????? You can use the default name or click the Enter Sweep Name window and erase the default entry and type in a custom name then press Enter
3.?????? Click Save Sweep. This saves the results in a text file on the Raspberry Pi. The default path on the Pi is /home/pi/Documents/tuner_sweeps . Note – this is assuming your user name on the Pi is the default user Pi, otherwise it would be the user name you used when setting up the Pi operating system. You can edit this default path in the Sweep Memory Controls section of the Tuner Sweep flow in the Node Red editor.
4.?????? You can recall any saved sweep for viewing in the Tuner Sweep Graph window by using the Sweeps pull down and selecting a sweep, then click the green box underneath to display the saved sweep results.
5.?????? While a sweep file is selected you can click DELETE SWEEP FILE to delete an individual sweep result.
6.?????? Or you can delete all saved sweep results by clicking on CLEAR ALL SWEEPS.
?
?
?
|
Dave wo2x