|
That's exactly what it does.? But it was sending '\n' then PS1;? -- that seemed to work for all other Yaesu rigs.
The document does talk about sending PS1; twice so I've changed it to that.? Could be it wants a little more dummy data.
Mike W9MDB
toggle quoted message
Show quoted text
On Sunday, May 8, 2022, 05:29:51 AM CDT, Adrian Fewster <vk4tux@...> wrote: Looking at the CAT manual ; I would need to use something to auto send the cmd twice as above, or is the rigctl cmd set to do this double action Mike ? This seems to explain mu double bttn press needed ? 73 Adrian Fewster On 8/5/22 20:10, Adrian Fewster via groups.io wrote: ??
Mike, Thanks for the rigctld cmd stanza today for On/Off and status.
I setup as below, and tested this afternoon.
The operation is reliable with some quirk's
The OFF button is pressed twice for a quick OFF reaction.
Pressing only once seems to hang with no reaction.
Turning ON using the same double press, the radio always turns on,
but it takes a minute to do so, but this the reliable when repeated.
I tested with rigctld tcp server as the only real comport client, and
??also sharing with Commander, that did not make a difference.
??The rigctld server seems to hibernate a bit looking at the verbose.
Waiting 1 minute for ON is ok, as long as reliable.
73
Adrian Fewster
|
I need debug info from rigctld please.
Mike W9MDB
toggle quoted message
Show quoted text
On Sunday, May 8, 2022, 07:14:58 AM CDT, Adrian Fewster <vk4tux@...> wrote: Mike, Changed out the dll, and same behavior requiring double button press done slowly. 1 press for OFF just hangs. The delay until On now is a bit varied between 1 to 3 minutes. Thankyou. 73 Adrian Fewster On 8/5/22 21:40, Michael Black via groups.io wrote: That's exactly what it does.? But it was sending '\n' then PS1;? -- that seemed to work for all other Yaesu rigs.
The document does talk about sending PS1; twice so I've changed it to that.? Could be it wants a little more dummy data.
Mike W9MDB
|
Add this to the rigctld command line
-vvvvv -Z >log.txt 2>&1
Then send the log.txt
Mike W9MDB
toggle quoted message
Show quoted text
On Sunday, May 8, 2022, 07:39:42 AM CDT, Adrian Fewster <vk4tux@...> wrote: Ok, Mike, because node-red is running there will be a lot more verbose, what is the best best method on windows server; rigctld cmd to pipe output for a log please to suit what you need ? Adrian On 8/5/22 22:35, Michael Black via groups.io wrote: I need debug info from rigctld please.
Mike W9MDB
|
Evidently you're working on one or more flows for a Yaesu rig, the FTdx101. I'm using a Yaesu FTdx3000 and FT991A and while I'm sure the CAT command controls are likely different in many ways, it could be a starting point.
As I'm barely conversant with Node Red and just finished a tutorial setting up my new SPE Expert 1.3K-FA Series 3 Amplifier with a Node Red flow by Ron WB2WGH I doubt I'll have anything to contribute, but it would be useful for my learning to follow along.
Does the flow live somewhere that I might copy it down to my machine or is it only in private development? I don't want to be pushy and intrude in your work, but if you're ready to share even an alpha version please let me know--or I can step back.
On Sun, May 8, 2022 at 8:45 AM Michael Black via <mdblack98= [email protected]> wrote: Add this to the rigctld command line
-vvvvv -Z >log.txt 2>&1
Then send the log.txt
Mike W9MDB
On Sunday, May 8, 2022, 07:39:42 AM CDT, Adrian Fewster <vk4tux@...> wrote:
Ok, Mike, because node-red is running there will be a lot more verbose,
what is the best best method on windows server; rigctld cmd to pipe
output for a log please to suit what you need ?
Adrian
On 8/5/22 22:35, Michael Black via wrote:
> I need debug info from rigctld please.
>
> Mike W9MDB
>
>
>
|
Thank you, Adrian, and thanks to Vance whose rig choice coincides with my own. There's a steep learning curve here for me and I still need to get Node Red running in a docker instance.
Very exciting to have the chance to work with all this node red flows and the possibilities offered.
On Sun, May 8, 2022 at 7:04 PM Adrian Fewster < vk4tux@...> wrote:
Steve, This is what I started with thanks to, and credit to Vance
;
| Name? |
Type |
Uploaded?By |
Size |
Created |
Updated |
?rigctld_get.json???Report File
flow with all the rigctld get commands. There are some
dashboard nodes that I set up for use with my fdtx3000, but
the main chunk of this stuff should work with any radio
using hamlib |
File |
Vance Martin |
91 kB |
Apr 17 |
Apr 17 |
Vance Martin does not appear to be active here on the group, and
I did email his qrz addy without result.
The FT-991 is cat compatible with the FTDX101, and is the SPE cat
choice to suit as you know.
I setup a rigctld server on the windows host connected to the
FTDX101 here,
My bat file ;
..........................................................................................................................
::
rigctld FTDX101MP
cd
C:\Program Files\hamlib-w64-4.5~git\bin
start
cmd.exe /k "rigctld -m 1044 -r com16 -s 38400 -t 4532 -vv"
.........................................................................................................................
and then tcp access from node red on a separate Debian PC here.
In settings.js the IP port variables are added ;
<snip>
?*
?* The settings are split into the following sections:
?*? - Flow File and User Directory Settings
?*? - Security
?*? - Server Settings
?*? - Runtime Settings
?*? - Editor Settings
?*? - Node Settings
?*
?**/
process.env.RIGADDRESS = '192.168.0.19'
process.env.RIGPORT = '4532'
module.exports = {
/****
?* Flow File and User Directory Settings
?*? - flowFile
?*? - credentialSecret
?*? - flowFilePretty
?*? - userDir
?*? - nodesDir
?***/
??? /** The file containing the flows. If not set, defaults to
flows_<hostname>.json **/
??? flowFile: 'SPE_Linear_V1.10PC.json',
<snip>
See the info in Vance's flow above for those details etc.
Please email direct with your progress, it would be great to
share notes.
73
Adrian Fewster
On 9/5/22 08:06, Steve K3FZT wrote:
Evidently you're working on one or more flows for a
Yaesu rig, the FTdx101. I'm using a Yaesu FTdx3000 and FT991A
and while I'm sure the CAT command controls are likely different
in many ways, it could be a starting point.
As I'm barely conversant with Node Red and just finished a
tutorial setting up my new SPE Expert 1.3K-FA Series 3
Amplifier with a Node Red flow by Ron WB2WGH I doubt I'll have
anything to contribute, but it would be useful for my learning
to follow along.
Does the flow live somewhere that I might copy it down to
my machine or is it only in private development? I don't want
to be pushy and intrude in your work, but if you're ready to
share even an alpha version please let me know--or I can step
back.
On Sun, May 8, 2022 at 8:45 AM
Michael Black via <mdblack98= [email protected]>
wrote:
Add
this to the rigctld command line
-vvvvv -Z >log.txt 2>&1
Then send the log.txt
Mike W9MDB
On Sunday, May 8, 2022, 07:39:42 AM CDT, Adrian Fewster <vk4tux@...>
wrote:
Ok, Mike, because node-red is running there will be a lot more
verbose,
what is the best best method on windows server; rigctld cmd to
pipe
output for a log please to suit what you need ?
Adrian
On 8/5/22 22:35, Michael Black via
wrote:
> I need debug info from rigctld please.
>
> Mike W9MDB
>
>
>
|
Adrian, in the food for thought category, I am adding a link out in the SPE flow that passes to exciter flows, a drive power level that is defined in an SPE function node. That function node has a user configured N x 4 wide array for the drive levels. 4 wide (SPE standby, low, middle and maximum. N long, one per band. Simon, S53ZO is currently beta testing the updated SPE flow.
A link in to your flow might be worth considering. Thoughts? Ron WB2WGH?
On Tue, May 10, 2022, 1:01 PM Adrian Fewster < vk4tux@...> wrote:
Also got mode control done tonight, started with a numeric input
and script, but it did not play well.
Went to a dropdown control which was also unreliable until I
dropped the added tcp request
node and instead used/shared with, the already existing for the
get node ;
Got (seen in vid) a Rigctld 'RPRT0' quick return interim to mode
changes, but it always works with correct display.
I may add a filter etc to take that out.
<stop> Thinking about this now, I updated the mode read
script ;
//do any needed mode manipulations here
msg.payload = msg.payload.substring(0, msg.payload.indexOf("\n"));
if (msg.payload == "PKTUSB") {
??? msg.payload = "DATA-U"
}
if (msg.payload == "PKTLSB") {
??? msg.payload = "DATA-L"
}
if (msg.payload == "RPRT 0") {
??? msg.payload = ""
}
return msg;
<solved> all good RPRT 0 no longer seen.
72
vk4tux
|
Adrian, yes this is similar to the Flex/SPE CAT model but managed through Node Red. In my case, I would not use it as I am Flex based and have the SPE programmed with?the by band/powerlevel settings. I do have some reservations given "Murphy" (if something can go wrong it will). I would hate to have something in the Node Red environment result in an "accidental" high drive level and fry the SPE. To your point about locking in a low drive level is a good safety net. Anyway, it will be in the flow with lots of cautions regarding its use. I'll shoot you and Simon an updated version in the next few days to play with.
73, Ron WB2WGH?
On Tue, May 10, 2022 at 7:28 PM Adrian Fewster < vk4tux@...> wrote: Ron, that sounds interesting. I know SPE Flex cat profile provides a
drive feedback to the Flex radio gear
supporting it for drive control. Is this something similar to that ? I
did test Pegasus software with the FTDX101 and SPE on Flex CAT,
and that worked. Commander , which I use now with SPE ond 2nd port
tracking first, also supports Flex cat, but I use FT-991.
That setup allows the SPE to cat track the sub vfo when in split and or TX.
I have my FTDX101 Max pwr set low on HF and 6m, locked in so I cannot
adj the drive excessive by accident. It is a great feature.
Happy to test anything you want to try Ron, Thankyou.
73
Adrian Fewster
On 11/5/22 03:18, Ronald Panetta, WB2WGH wrote:
> Adrian, in the food for thought category, I am adding a link out in
> the SPE flow that passes to exciter flows, a drive power level that is
> defined in an SPE function node. That function node has a user
> configured N x 4 wide array for the drive levels. 4 wide (SPE standby,
> low, middle and maximum. N long, one per band. Simon, S53ZO is
> currently beta testing the updated SPE flow.
>
> A link in to your flow might be worth considering. Thoughts?
>
> Ron WB2WGH
>
|
I am building a flow for the Elecraft K4D and used the number node for power set. That way I can go up or down 1 watt at a time. Might be worth looking into for your flow.?
73 Dave wo2x Sent from my waxed string and tin cans.?
toggle quoted message
Show quoted text
On May 10, 2022, at 11:33 PM, Adrian Fewster <vk4tux@...> wrote:
?
Ron , I added a dropdown for power set also here ;
I found using a slider less reliable, and some tcp request points
seem to work better than others,
however this this now works nicely. Can add larger values later,
but these are amp drive levels.
The dropdown is great for saving space.
73
Adrian Fewster
On 11/5/22 10:50, Ronald Panetta,
WB2WGH wrote:
Adrian, yes this is similar to the Flex/SPE CAT
model but managed through Node Red. In my case, I would not use
it as I am Flex based and have the SPE programmed with?the by
band/powerlevel settings. I do have some reservations given
"Murphy" (if something can go wrong it will). I would hate to
have something in the Node Red environment result in an
"accidental" high drive level and fry the SPE. To your point
about locking in a low drive level is a good safety net. Anyway,
it will be in the flow with lots of cautions regarding its use.
I'll shoot you and Simon an updated version in the next few days
to play with.
73, Ron WB2WGH?
On Tue, May 10, 2022 at 7:28
PM Adrian Fewster < vk4tux@...>
wrote:
Ron,
that sounds interesting. I know SPE Flex cat profile provides
a
drive feedback to the Flex radio gear
supporting it for drive control. Is this something similar to
that ? I
did test Pegasus software with the FTDX101 and SPE on Flex
CAT,
and that worked. Commander , which I use now with SPE ond 2nd
port
tracking first, also supports Flex cat, but I use FT-991.
That setup allows the SPE to cat track the sub vfo when in
split and or TX.
I have my FTDX101 Max pwr set low on HF and 6m, locked in so I
cannot
adj the drive excessive by accident. It is a great feature.
Happy to test anything you want to try Ron, Thankyou.
73
Adrian Fewster
On 11/5/22 03:18, Ronald Panetta, WB2WGH wrote:
> Adrian, in the food for thought category, I am adding a
link out in
> the SPE flow that passes to exciter flows, a drive power
level that is
> defined in an SPE function node. That function node has a
user
> configured N x 4 wide array for the drive levels. 4 wide
(SPE standby,
> low, middle and maximum. N long, one per band. Simon,
S53ZO is
> currently beta testing the updated SPE flow.
>
> A link in to your flow might be worth considering.
Thoughts?
>
> Ron WB2WGH
>
--
|
toggle quoted message
Show quoted text
On Tue, May 10, 2022, 11:33 PM Adrian Fewster < vk4tux@...> wrote:
Ron , I added a dropdown for power set also here ;
I found using a slider less reliable, and some tcp request points
seem to work better than others,
however this this now works nicely. Can add larger values later,
but these are amp drive levels.
The dropdown is great for saving space.
73
Adrian Fewster
On 11/5/22 10:50, Ronald Panetta,
WB2WGH wrote:
Adrian, yes this is similar to the Flex/SPE CAT
model but managed through Node Red. In my case, I would not use
it as I am Flex based and have the SPE programmed with?the by
band/powerlevel settings. I do have some reservations given
"Murphy" (if something can go wrong it will). I would hate to
have something in the Node Red environment result in an
"accidental" high drive level and fry the SPE. To your point
about locking in a low drive level is a good safety net. Anyway,
it will be in the flow with lots of cautions regarding its use.
I'll shoot you and Simon an updated version in the next few days
to play with.
73, Ron WB2WGH?
On Tue, May 10, 2022 at 7:28
PM Adrian Fewster < vk4tux@...>
wrote:
Ron,
that sounds interesting. I know SPE Flex cat profile provides
a
drive feedback to the Flex radio gear
supporting it for drive control. Is this something similar to
that ? I
did test Pegasus software with the FTDX101 and SPE on Flex
CAT,
and that worked. Commander , which I use now with SPE ond 2nd
port
tracking first, also supports Flex cat, but I use FT-991.
That setup allows the SPE to cat track the sub vfo when in
split and or TX.
I have my FTDX101 Max pwr set low on HF and 6m, locked in so I
cannot
adj the drive excessive by accident. It is a great feature.
Happy to test anything you want to try Ron, Thankyou.
73
Adrian Fewster
On 11/5/22 03:18, Ronald Panetta, WB2WGH wrote:
> Adrian, in the food for thought category, I am adding a
link out in
> the SPE flow that passes to exciter flows, a drive power
level that is
> defined in an SPE function node. That function node has a
user
> configured N x 4 wide array for the drive levels. 4 wide
(SPE standby,
> low, middle and maximum. N long, one per band. Simon,
S53ZO is
> currently beta testing the updated SPE flow.
>
> A link in to your flow might be worth considering.
Thoughts?
>
> Ron WB2WGH
>
--
|
I am polling current power setting in K4 every 10 seconds. I parse the power level and then feed that into the numeric node. ? When I use the numeric node to change power the numeric node sends current power + 1 to a function node so if power was 29 watts and I click up it sends 30 to a function node. I use the following in the function node to format it before sending it to the TCP request node which sends the commands to the K4. The K4 need power sent as PC050H; or PC100H; The H tells the radio to use the 100 watt PA. You can use an L instead if you need low power (under 10 watts) which then bypasses the internal 100 watt PA. ? msg.payload?=?"PC"?+?msg.payload.toString().padStart(3,"0")?+"H;"; return?msg; ? 73 Dave wo2x ? ?
toggle quoted message
Show quoted text
From: [email protected] < [email protected]> On Behalf Of Adrian Fewster Sent: Sunday, May 15, 2022 8:29 PM To: [email protected]Subject: Re: [nodered-hamradio] FTDX101 ON OFF ? Dave, With your numeric input, how did you keep the set value at the last frequency set, rather than drop back to the range minimum? ? Thankyou ? Adrian Fewster On 11/5/22 13:40, David De Coons wo2x wrote: I am building a flow for the Elecraft K4D and used the number node for power set. That way I can go up or down 1 watt at a time. Might be worth looking into for your flow.? Dave wo2x ? Sent from my waxed string and tin cans.?
On May 10, 2022, at 11:33 PM, Adrian Fewster <vk4tux@...> wrote:
? Ron , I added a dropdown for power set also here ; 
? I found using a slider less reliable, and some tcp request points seem to work better than others, however this this now works nicely. Can add larger values later, but these are amp drive levels. The dropdown is great for saving space. ? 73 ? Adrian Fewster ? On 11/5/22 10:50, Ronald Panetta, WB2WGH wrote: Adrian, yes this is similar to the Flex/SPE CAT model but managed through Node Red. In my case, I would not use it as I am Flex based and have the SPE programmed with?the by band/powerlevel settings. I do have some reservations given "Murphy" (if something can go wrong it will). I would hate to have something in the Node Red environment result in an "accidental" high drive level and fry the SPE. To your point about locking in a low drive level is a good safety net. Anyway, it will be in the flow with lots of cautions regarding its use. I'll shoot you and Simon an updated version in the next few days to play with. ? On Tue, May 10, 2022 at 7:28 PM Adrian Fewster <vk4tux@...> wrote: Ron, that sounds interesting. I know SPE Flex cat profile provides a
drive feedback to the Flex radio gear
supporting it for drive control. Is this something similar to that ? I
did test Pegasus software with the FTDX101 and SPE on Flex CAT,
and that worked. Commander , which I use now with SPE ond 2nd port
tracking first, also supports Flex cat, but I use FT-991.
That setup allows the SPE to cat track the sub vfo when in split and or TX.
I have my FTDX101 Max pwr set low on HF and 6m, locked in so I cannot
adj the drive excessive by accident. It is a great feature.
Happy to test anything you want to try Ron, Thankyou.
73
Adrian Fewster
On 11/5/22 03:18, Ronald Panetta, WB2WGH wrote:
> Adrian, in the food for thought category, I am adding a link out in
> the SPE flow that passes to exciter flows, a drive power level that is
> defined in an SPE function node. That function node has a user
> configured N x 4 wide array for the drive levels. 4 wide (SPE standby,
> low, middle and maximum. N long, one per band. Simon, S53ZO is
> currently beta testing the updated SPE flow.
>
> A link in to your flow might be worth considering. Thoughts?
>
> Ron WB2WGH
>
--
|
To send from one flow to another use the link in and link out nodes.
73
toggle quoted message
Show quoted text
On May 26, 2022, at 1:43 AM, Adrian Fewster <vk4tux@...> wrote:
?Ron, also I think in yor case the SPE is talking the Flex via the physical cat connection between the two.
I have done what you mention with Pegusus software and it work, however we wont to keep it inhouse node red.
So to send a string from one flow to another in the same groupo, can we use udp ?
See??
Or there an easier way to link differrent flows ?
Once we have the string with change node / function anything would be possible to set the FTDX101 regarding SPE power profile.
When a SPE drops a power profile level on certain alarms the drive would auto follow to suit.
73
Adrian Fewster
|
Adrian, I continue to work on the exciter drive level feature. In the past I never did any checksum validation of status (if you use the logging feature you will notice some garbage records). I am rolling in checksum validation to minimize any possible erroneous drive levels. The good news is no changes are required to the dashboard. Once I am comfortable with the update I'll get a beta out to you and Simon.
Ron WB2WGH?
On Thu, May 26, 2022, 1:04 AM Adrian Fewster < vk4tux@...> wrote: On Tue, May 10, 2022 at 10:18 AM, Ronald Panetta, WB2WGH wrote:
Adrian, in the food for thought category, I am adding a link out in the SPE flow that passes to exciter flows, a drive power level that is defined in an SPE function node. That function node has a user configured N x 4 wide array for the drive levels. 4 wide (SPE standby, low, middle and maximum. N long, one per band. Simon, S53ZO is currently beta testing the updated SPE flow.
?
A link in to your flow might be worth considering. Thoughts?
Ron WB2WGH?
Ron, did you have any more on this that I can try out please ? I could probably squeeze something else in. regards Adrian 
|
Easy to pass info between flows. Check out the "Link in" and "Link out" nodes. They are invisible connectors that connect nodes intra and/or inter flow. I think there are a few in the SPE flow.
Ron WB2WGH?
On Thu, May 26, 2022, 1:46 AM Adrian Fewster < vk4tux@...> wrote: [Edited Message Follows]
Ron, also I think in yor case the SPE is talking the Flex via the physical cat connection between the two.
I have done what you mention with Pegasus software and it works, however we want to keep it in-house node red.
So to send a string from one flow to another in the same group, can we use udp ?
See??
Or there an easier way to link differrent flows ?
Once we have the string with change node / function anything would be possible to set the FTDX101 regarding SPE power profile.
When a SPE drops a power profile level on certain alarms the drive would auto follow as set to suit.
73
Adrian Fewster
|
Adrian, I have already coded an option for exciter drive level "output" parameter based on band and SPE power level setting. The user configures the table in Node Red much like the SOE does it for Flex. I have not released that version yet for beta rest but can and will get you a beta in the next few days.?
The challenge has been to ensure the lookup is performed on "valid" SPE data. Without blgetting into the details, sometimes the CSV data is corrupt (bad checksum or wrap around of the data). That has resulted in adding additional code to verify packet validity as I don't want to perform a drive level lookup based on bad data.?
I'll get you a beta shortly. Ron WB2WGH?
I see using
msg.payload.col10? in debug
"H"
27/06/2022, 17:03:54msg.payload.col10 : string[1]
"M"
27/06/2022, 17:03:54msg.payload.col10 : string[1]
"M"
27/06/2022, 17:03:55msg.payload.col10 : string[1]
"M"
27/06/2022, 17:03:55msg.payload.col10 : string[1]
"M"
27/06/2022, 17:03:57msg.payload.col10 : string[1]
"L"
27/06/2022, 17:03:57msg.payload.col10 : string[1]
"L"
27/06/2022, 17:03:57msg.payload.col10 : string[1]
"L"
which should be simple to tap.
73
Adrian
|
Adrian, thanks for the video. I'll get you the SPE beta version tomorrow. Provides similar functionality to your tweak, table driven (you customize the table), 4 drive level columns (standby, L, M, H) and a row per band. A link out node to couple with a corresponding exciter flow's link in. Ron WB2WGH?
Ron, A little vid of my basic setup ;
regards
Adrian
|
Adrian, not easily done as there are a number of unrelated changes. It should be easy to populate the table with your power settings. Let me get you the flow when in the shack tomorrow. Ron WB2WGH?
Ron, Are you able to export the added sections you can email me, so I can just import those into my existing respective flows please ?
Mainly because of my custom SPE power scales and type etc.
Thankyou
Adrian
|
Adrian, Glad the beta upgrade is working well. As to your comment regarding frequency sync, I think not. The API provides front panel like functions and frequency sync is not one of them if I understand you correctly.
As to the updated beta flow: - Can you temporarily add the "wraparound" LED to your dashboard. If he LED should go red (I think it will):
- It can be cleared via a dashboard button push (e.g. change state or power level). I'd like to get a sense as to how often?it happens.
- Prior to clearing the "wraparound" LED, try making a change on the SPE front panel (e.g., state, power level., ...). I suspect the change will NOT be reflected in the dashboard.?
- These are the issues I've been wrestling with for the last month or so on the flow. I might have a solution but have not tried it yet.
- From the video, it looks like the USB Status indicator still flashes with button pushes. Please confirm
- I assume if you switch from operate to standby, the standby power level is passed to the exciter?
73, Ron WB2WGH
Ron, your SPE flow txcr drive control works great as expected ;
I don't think this is possible, as frequency monitor in SPE can only be done by txcr cat connection,
but
I wondered if it was possible via the SPE nod-red instruction. so that node-red could provide the?
TXCR<> SPE frequency sync for band change / atu function etc. Impossible yes ?
73
Adrian
|
Adrian
Can you take the input from FTdx101D and send it out a USB to serial to the SPE amp set to Yaesu CAT??
I did similar with Elecraft K4D CAT into Node Red then immediately sent it out two USB to Serial cables to Power Genius and Tuner Genius set to Elecraft protocol. That way Node Red received the CAT data and I split it in Node Red to amp and tuner.?
73 Dave wo2x Sent from my waxed string and tin cans.?
toggle quoted message
Show quoted text
On Jun 28, 2022, at 9:09 PM, Adrian Fewster <vk4tux@...> wrote:
?Ron, Yes the stanby power works well.
I separated and imported the linkout section only and imported to my existing flow,
to keep my other SPE custom changes. I kept my existing link network for this and just disabled
to try yours alongside. I wrote a new script function on link in to handle the number translation
to rigctld power instructions.
I have noticed no errors and I have two levels of safety in my max txcr power setting and the link
in value must match?the function script to get a result.
How are you handling the traffic at link in for Flex ? Are the values sent direct or interpreted first ?
Thankyou
Adrian
|
Adrian, with respect to the Flex, the SPE has the table internal to the SPE. The user programs the SPE with the band/power level exciter settings much like I did in the flow. The process is documented in the SPE manual.
Ron WB2WGH
Ron, Yes the stanby power works well.
I separated and imported the linkout section only and imported to my existing flow,
to keep my other SPE custom changes. I kept my existing link network for this and just disabled
to try yours alongside. I wrote a new script function on link in to handle the number translation
to rigctld power instructions.
I have noticed no errors and I have two levels of safety in my max txcr power setting and the link
in value must match?the function script to get a result.
How are you handling the traffic at link in for Flex ? Are the values sent direct or interpreted first ?
Thankyou
Adrian
|
Ok. Not knowing your or Ron¡¯s flow exactly I was just putting it out there.?
I have taken basic frequency info from within Node Red and created a Kenwood or Yaesu formatted CAT out.?
If there is a way you can send the frequency of VFO A in non-split or VFO B in split then building the CAT out is pretty easy. ?Feed msg.vfoa and msg.vfob and msg.splitstatus into a function node and you could have it produce a msg.freq out.?
Would something like that work? You would just need to tap the two VFO frequencies and status of split (on or off).?
I¡¯ll be back home tomorrow night.?
73 Dave wo2x Sent from my waxed string and tin cans.?
toggle quoted message
Show quoted text
On Jun 28, 2022, at 11:51 PM, Adrian Fewster <vk4tux@...> wrote:
?On Tue, Jun 28, 2022 at 06:17 PM, David De Coons wo2x wrote:
Adrian
?
Can you take the input from FTdx101D and send it out a USB to serial to the SPE amp set to Yaesu CAT??
?
I did similar with Elecraft K4D CAT into Node Red then immediately sent it out two USB to Serial cables to Power Genius and Tuner Genius set to Elecraft protocol. That way Node Red received the CAT data and I split it in Node Red to amp and tuner.?
?
73
Dave wo2x
Dave, Ron is the expert on this, however the SPE flow uses the SPE term program ; "?usb port for this purpose, and not the cat connection. Now if a node red? serial port with cat profile/translation tables could be available as a node to emulate the Commander/Pegusus feature, then those programs could be set aside and not needed. The reason for the comport follow instead of direct txcr connection on CAT, here is that it allows the SPE to follow the sub VFO in TX/split etc. As my FTDX101 is using the rigctld server instead of direct CAT, it is probably more difficult. It is always interesting to see what is possible. regards Adrian
|
Dave wo2x
