On Jul 31, 2020, at 6:38 AM, Alan Blind <a.alan.blind@...> wrote:

I have replaced the WO2X Flex API flow with three new flows, all of which use the Pi FRStack Server as the source of Flex Data and Control.? I have not included other functions, other then to replace the WO2X functionality.

Dave's flow served me well, but it was lacking in an ability to choose which Client to bind to (multiplex operation with two clients), and to select the Slice from the bounded client.

The Client selector is on the "Connection" Flow. ? The Slice selector is on the "Active Slice" Flow.

I primarily?wanted to add a "Tune" Button to my station dashboard, which would inhibit my PG-XL amp ?from operate, during the Tune process, then return the PG-XL to operate.? Pi FRStack does all of the work to make this happen, outside of Node-Red. ? Just add a tune button to your dashboard.? My tune button changes background color depending on the ?Flex Tune status.

You will see two dashboards.? One dashboard is a "FRStack" dashboard displaying all of my Flex Radio data and controls on one dashboard.? The other dashboard has the Flex Radio inputs to my primary station control dashboard, where I have included the most used gauges and controls.? You need to modify your user interface nodes to your specific use.

Mark's FRStack flows are very comprehensive, however, my flows have not reproduced many of Mark's parameters.? Only those I need on my dashboard or for other controls.

Alan

WA9WUD

?

?

Alan,

On Jul 31, 2020, at 12:31 PM, Alan Blind <a.alan.blind@...> wrote:

Andreas, the original is preserved. ? I have copies of my version.? Dave, WO2X is the principal author of the base concept and I am sure he is retaining his original also.

Would you like a copy?

Alan

On Fri, Jul 31, 2020 at 2:10 PM Andreas Junge <andreas@...> wrote:

Alan,

Is the non-FRstack code preserved??

73, Andreas, N6NU

On Jul 31, 2020, at 6:38 AM, Alan Blind <a.alan.blind@...> wrote:

I have replaced the WO2X Flex API flow with three new flows, all of which use the Pi FRStack Server as the source of Flex Data and Control.? I have not included other functions, other then to replace the WO2X functionality.

Dave's flow served me well, but it was lacking in an ability to choose which Client to bind to (multiplex operation with two clients), and to select the Slice from the bounded client.

The Client selector is on the "Connection" Flow. ? The Slice selector is on the "Active Slice" Flow.

I primarily?wanted to add a "Tune" Button to my station dashboard, which would inhibit my PG-XL amp ?from operate, during the Tune process, then return the PG-XL to operate.? Pi FRStack does all of the work to make this happen, outside of Node-Red. ? Just add a tune button to your dashboard.? My tune button changes background color depending on the ?Flex Tune status.

You will see two dashboards.? One dashboard is a "FRStack" dashboard displaying all of my Flex Radio data and controls on one dashboard.? The other dashboard has the Flex Radio inputs to my primary station control dashboard, where I have included the most used gauges and controls.? You need to modify your user interface nodes to your specific use.

Mark's FRStack flows are very comprehensive, however, my flows have not reproduced many of Mark's parameters.? Only those I need on my dashboard or for other controls.

Alan

WA9WUD

?

On Jul 31, 2020, at 1:26 PM, David De Coons wo2x <RocketNJ@...> wrote:

Andreas,

?

The non-FRStack flows are located under my callsign in the files section.

?

73

Dave wo2x

?

?

From:?[email protected]?<[email protected]>?On Behalf Of?Andreas Junge
Sent:?Friday, July 31, 2020 2:11 PM
To:?[email protected]
Subject:?Re: [nodered-hamradio] 3 files uploaded #file-notice

?

Alan,

?

Is the non-FRstack code preserved??

?

73, Andreas, N6NU

?