|
Posted to the Node Red files section is the V1.1 of the SPE Linear
flow. A picture of the updated dashboard is attached. Thanks to my beta
testers! Users are encouraged to contact me if they encounter any issues with the flow.
Material changes since V1.0 included in this release are:
- Text on the antenna button updated to clearly
show ATU status
- Power level button for low power changed from
yellow to purple to improve readability
- SWR display previously displayed 2 decimal
digits to the right of the decimal point but was rounded to 1 decimal digit.
The rounding has been eliminated.
- Addition of Power On and Power Off buttons. Both
should be fully functional. There is no interlock on power off with the state
(operate/standby) and mode (RX/TX). That means it is possible to power the SPE
off in the middle of a TX cycle.
- Power ¡°Off¡± is implemented via USB commands to
the SPE per the application programmer's interface (API) documentation.
- Power ¡°On¡± is a different matter. This is done
through a Python script which must be created on the Node Red server. The Read
Me has the required commands. This requires Python to be present on the Node
Red server and it looks like the RPi Node Red distribution includes Python.
This has only been tested on a RPi Node Red server.
- The addition of a dashboard "USB
Status" indicator to display status of the Node Red <-> SPE
communication's link.
- The addition of a new bottom row to the
dashboard for Power ¡°On¡±, USB Status and Power ¡°Off¡± buttons/indicators.
- Correction of the I PA and V PA gauges to
display "Amps" and "Volts" instead of "Units".
- Change of the USB Timeout from 500ms to 200ms as
the flow gets backed up when the SPE is powered off and later powered back on.
The dashboard was very slow (seconds to minutes) to respond to button pushes.
Customizations you must make (reference the flow's Read Me and
other Warning nodes at the top of the flow):
- Update the USB device name in the flow to
reflect your USB device name. Suggest using the /dev/serial/by-id/...... path in
the definition.
- For power ¡°On¡± functionality, test the
availability of Python on your node red server and add the Python SPE shutdown
script.
- If you want temperature gauges displayed in
Fahrenheit, follow the instructions in the Read Me. This will adjust the
temperature gauges to the Fahrenheit equivalent of 25C (min), 65C (max), 50C
(segment 1) and 60C (segment 2).
Required Palette Components (reference the flow¡¯s Read Me):
- node-red-contrib-ui-level
- node-red-dashboard
- node-red-node-rbe (replaced by the
"filter" node and may already be part of your palette)
Outstanding bugs:
- PWR gauge shows full scale and missing zero
after browser refresh.
|
I will give it a try , the last version it was ?not easy to change Fahrenheit to Celsius unit change. ?I like the Fahrenheit:( ??¡á? The color adjustment thru the CSS is different.
toggle quoted message
Show quoted text
On Apr 30, 2022, at 4:54 PM, Ronald Panetta, WB2WGH <ron@...> wrote:
? Posted to the Node Red files section is the V1.1 of the SPE Linear
flow. A picture of the updated dashboard is attached. Thanks to my beta
testers! Users are encouraged to contact me if they encounter any issues with the flow.
Material changes since V1.0 included in this release are:
- Text on the antenna button updated to clearly
show ATU status
- Power level button for low power changed from
yellow to purple to improve readability
- SWR display previously displayed 2 decimal
digits to the right of the decimal point but was rounded to 1 decimal digit.
The rounding has been eliminated.
- Addition of Power On and Power Off buttons. Both
should be fully functional. There is no interlock on power off with the state
(operate/standby) and mode (RX/TX). That means it is possible to power the SPE
off in the middle of a TX cycle.
- Power ¡°Off¡± is implemented via USB commands to
the SPE per the application programmer's interface (API) documentation.
- Power ¡°On¡± is a different matter. This is done
through a Python script which must be created on the Node Red server. The Read
Me has the required commands. This requires Python to be present on the Node
Red server and it looks like the RPi Node Red distribution includes Python.
This has only been tested on a RPi Node Red server.
- The addition of a dashboard "USB
Status" indicator to display status of the Node Red <-> SPE
communication's link.
- The addition of a new bottom row to the
dashboard for Power ¡°On¡±, USB Status and Power ¡°Off¡± buttons/indicators.
- Correction of the I PA and V PA gauges to
display "Amps" and "Volts" instead of "Units".
- Change of the USB Timeout from 500ms to 200ms as
the flow gets backed up when the SPE is powered off and later powered back on.
The dashboard was very slow (seconds to minutes) to respond to button pushes.
Customizations you must make (reference the flow's Read Me and
other Warning nodes at the top of the flow):
- Update the USB device name in the flow to
reflect your USB device name. Suggest using the /dev/serial/by-id/...... path in
the definition.
- For power ¡°On¡± functionality, test the
availability of Python on your node red server and add the Python SPE shutdown
script.
- If you want temperature gauges displayed in
Fahrenheit, follow the instructions in the Read Me. This will adjust the
temperature gauges to the Fahrenheit equivalent of 25C (min), 65C (max), 50C
(segment 1) and 60C (segment 2).
Required Palette Components (reference the flow¡¯s Read Me):
- node-red-contrib-ui-level
- node-red-dashboard
- node-red-node-rbe (replaced by the
"filter" node and may already be part of your palette)
Outstanding bugs:
- PWR gauge shows full scale and missing zero
after browser refresh.
--
Nick
W7NIK?
|
Nick, regarding temperature units (C vs F), the flow by default reports C. You indicated it was not easy to change to degrees F. To change to F is a 2 step process:? - Set the SPE to report F via the front panel setup menu
- Change he initialization node in the flow
- flow.set("temperature_units" , "C"); comment this line out
//flow.set("temperature_units" , "F"); uncomment this line
That should report degrees F in the dashboard and the meter limits will adjust accordingly. I made the assumption that if one wants degrees F, they would have already made the change via the SPE front panel.which is why I didn't do the C to F conversion in the flow.?
73, Ron WB2WGH
I will give it a try , the last version it was ?not easy to change Fahrenheit to Celsius unit change.? I like the Fahrenheit:( ??¡á? The color adjustment thru the CSS is different.
On Apr 30, 2022, at 4:54 PM, Ronald Panetta, WB2WGH <ron@...> wrote:
? Posted to the Node Red files section is the V1.1 of the SPE Linear
flow. A picture of the updated dashboard is attached. Thanks to my beta
testers! Users are encouraged to contact me if they encounter any issues with the flow.
Material changes since V1.0 included in this release are:
- Text on the antenna button updated to clearly
show ATU status
- Power level button for low power changed from
yellow to purple to improve readability
- SWR display previously displayed 2 decimal
digits to the right of the decimal point but was rounded to 1 decimal digit.
The rounding has been eliminated.
- Addition of Power On and Power Off buttons. Both
should be fully functional. There is no interlock on power off with the state
(operate/standby) and mode (RX/TX). That means it is possible to power the SPE
off in the middle of a TX cycle.
- Power ¡°Off¡± is implemented via USB commands to
the SPE per the application programmer's interface (API) documentation.
- Power ¡°On¡± is a different matter. This is done
through a Python script which must be created on the Node Red server. The Read
Me has the required commands. This requires Python to be present on the Node
Red server and it looks like the RPi Node Red distribution includes Python.
This has only been tested on a RPi Node Red server.
- The addition of a dashboard "USB
Status" indicator to display status of the Node Red <-> SPE
communication's link.
- The addition of a new bottom row to the
dashboard for Power ¡°On¡±, USB Status and Power ¡°Off¡± buttons/indicators.
- Correction of the I PA and V PA gauges to
display "Amps" and "Volts" instead of "Units".
- Change of the USB Timeout from 500ms to 200ms as
the flow gets backed up when the SPE is powered off and later powered back on.
The dashboard was very slow (seconds to minutes) to respond to button pushes.
Customizations you must make (reference the flow's Read Me and
other Warning nodes at the top of the flow):
- Update the USB device name in the flow to
reflect your USB device name. Suggest using the /dev/serial/by-id/...... path in
the definition.
- For power ¡°On¡± functionality, test the
availability of Python on your node red server and add the Python SPE shutdown
script.
- If you want temperature gauges displayed in
Fahrenheit, follow the instructions in the Read Me. This will adjust the
temperature gauges to the Fahrenheit equivalent of 25C (min), 65C (max), 50C
(segment 1) and 60C (segment 2).
Required Palette Components (reference the flow¡¯s Read Me):
- node-red-contrib-ui-level
- node-red-dashboard
- node-red-node-rbe (replaced by the
"filter" node and may already be part of your palette)
Outstanding bugs:
- PWR gauge shows full scale and missing zero
after browser refresh.
--
Nick
W7NIK?
|
Adrian, with respect to the power gauge color transitions and maximum, there is much discussion and debate on the speexpertamps? page regarding drive level and suggested power thresholds. I prefer not to entangle my flow in that discussion?and debate. In my flow, I simply use the following algorithm for the gauge color thresholds and maximums: - Green to yellow transition:? advertised power?level - 50W
- Yellow to red transition:? ? ? advertised power level
- Maximum:? ? ? ? ? ? ? ? ? ? ? ? ? ?advertised power level?+ 100W
I have added in the read me?another user customization item referencing the node where the thresholds are set and in that node "PWR Meter Range" I added notes on the default algorithm I use and how to change it.
So armed with that additional guidance to be included in the next release, I now defer to each individual user to customize the thresholds to their liking. BTW, I did notice a few cut/paste typos for the 1.3K-FA thresholds which are now corrected and will be included in the flow's next release.
Ron WB2WGH
On Sat, Apr 30, 2022 at 9:40 PM Adrian Fewster < vk4tux@...> wrote:
Ron I changed my meter scaling to ;
??????????? case "15K":
??????????????? switch (pwr_lvl)
??????????????? {
??????????????????? case "L":? // 500W
??????????????????????? msg1.control = { min: 0, max: 800, seg1:
450, seg2: 750};
??????????????????????? label = "800W";
??????????????????????? break;
??????????????????? case "M":? // 1000W
??????????????????????? msg1.control = { min: 0, max: 1300, seg1:
950, seg2: 1250};
??????????????????????? label = "1300W";
??????????????????????? break;
??????????????????? case "H":? // 1500W
??????????????????????? msg1.control = { min: 0, max: 1700, seg1:
1450 , seg2: 1650};
??????????????????????? label = "1600W";
??????????????????????? break;
??????????????? }
The SPE Low characteristics for best efficiency are best above
the SPE Low default suggestion.
It is much better to run 700- 800w in Low than Mid, with I PA in
the 1K80H manufacturer spec 24 - 30 amp,
with a 10 deg C lower temperature.? This works well with recent
FW, No overdrive issues under 800w.
This works well for me, and I retained the single color bar,
which still
changes color on the seg points. No refresh colorization.
The LDMOS works best in the 24 -30 amp rage using voltage to
control power with best heat to RF efficiency.
regards
Adrian
On 1/5/22 11:30, Nick M via
wrote:
I will give it a try , the last version it was ?not
easy to change Fahrenheit to Celsius unit change.? I like the
Fahrenheit:( ??¡á?
The color adjustment thru the CSS is different.
On Apr 30, 2022, at 4:54 PM, Ronald
Panetta, WB2WGH <ron@...> wrote:
?
Posted
to the Node Red files section is the V1.1 of the SPE
Linear
flow. A picture of the updated dashboard is attached.
Thanks to my beta
testers! Users are encouraged to contact me if they
encounter any issues with the flow.
Material
changes since V1.0 included in this release are:
- Text on the antenna button updated to clearly
show ATU status
- Power level button for low power changed from
yellow to purple to improve readability
- SWR display previously displayed 2 decimal
digits to the right of the decimal point but was
rounded to 1 decimal digit.
The rounding has been eliminated.
- Addition of Power On and Power Off buttons. Both
should be fully functional. There is no interlock on
power off with the state
(operate/standby) and mode (RX/TX). That means it is
possible to power the SPE
off in the middle of a TX cycle.
- Power ¡°Off¡± is implemented via USB commands to
the SPE per the application programmer's interface
(API) documentation.
- Power ¡°On¡± is a different matter. This is done
through a Python script which must be created on the
Node Red server. The Read
Me has the required commands. This requires Python to
be present on the Node
Red server and it looks like the RPi Node Red
distribution includes Python.
This has only been tested on a RPi Node Red server.
- The addition of a dashboard "USB
Status" indicator to display status of the Node Red
<-> SPE
communication's link.
- The addition of a new bottom row to the
dashboard for Power ¡°On¡±, USB Status and Power ¡°Off¡±
buttons/indicators.
- Correction of the I PA and V PA gauges to
display "Amps" and "Volts" instead of "Units".
- Change of the USB Timeout from 500ms to 200ms as
the flow gets backed up when the SPE is powered off
and later powered back on.
The dashboard was very slow (seconds to minutes) to
respond to button pushes.
Customizations
you must make (reference the flow's Read Me and
other Warning nodes at the top of the flow):
- Update the USB device name in the flow to
reflect your USB device name. Suggest using the
/dev/serial/by-id/...... path in
the definition.
- For power ¡°On¡± functionality, test the
availability of Python on your node red server and add
the Python SPE shutdown
script.
- If you want temperature gauges displayed in
Fahrenheit, follow the instructions in the Read Me.
This will adjust the
temperature gauges to the Fahrenheit equivalent of 25C
(min), 65C (max), 50C
(segment 1) and 60C (segment 2).
Required
Palette Components (reference the flow¡¯s Read Me):
- node-red-contrib-ui-level
- node-red-dashboard
- node-red-node-rbe (replaced by the
"filter" node and may already be part of your palette)
Outstanding
bugs:
- PWR gauge shows full scale and missing zero
after browser refresh.
--
Nick
W7NIK?
|
Adrian agreed. Ron WB2WGH?
On Sun, May 1, 2022, 10:01 AM Adrian Fewster < vk4tux@...> wrote:
Ron, Yes I expected that. It was just a fyi for what I feel works
best here.
I think there is some confusion over the efficiency alarm. Most
of my questions to SPE
remain un-answered. I don't suggest you introduce those there,
but just sharing what I have done here.
Thankyou
Adrian
On 1/5/22 23:30, Ronald Panetta, WB2WGH
wrote:
Adrian, with respect to the power gauge color
transitions and maximum, there is much discussion and debate on
the speexpertamps? page regarding drive
level and suggested power thresholds. I prefer not to entangle
my flow in that discussion?and debate. In my flow, I simply use
the following algorithm for the gauge color thresholds and
maximums:
- Green to yellow transition:? advertised power?level -
50W
- Yellow to red transition:? ? ? advertised power level
- Maximum:? ? ? ? ? ? ? ? ? ? ? ? ? ?advertised power
level?+ 100W
I have added in the read me?another user customization
item referencing the node where the thresholds are set and
in that node "PWR Meter Range" I added notes on the default
algorithm I use and how to change it.
So armed with that additional guidance to be included in
the next release, I now defer to each individual user to
customize the thresholds to their liking. BTW, I did notice a
few cut/paste typos for the 1.3K-FA thresholds which are now
corrected and will be included in the flow's next release.
Ron WB2WGH
On Sat, Apr 30, 2022 at 9:40
PM Adrian Fewster < vk4tux@...>
wrote:
Ron I changed my meter scaling to ;
??????????? case "15K":
??????????????? switch (pwr_lvl)
??????????????? {
??????????????????? case "L":? // 500W
??????????????????????? msg1.control = { min: 0, max: 800,
seg1: 450, seg2: 750};
??????????????????????? label = "800W";
??????????????????????? break;
??????????????????? case "M":? // 1000W
??????????????????????? msg1.control = { min: 0, max:
1300, seg1: 950, seg2: 1250};
??????????????????????? label = "1300W";
??????????????????????? break;
??????????????????? case "H":? // 1500W
??????????????????????? msg1.control = { min: 0, max:
1700, seg1: 1450 , seg2: 1650};
??????????????????????? label = "1600W";
??????????????????????? break;
??????????????? }
The SPE Low characteristics for best efficiency are best
above the SPE Low default suggestion.
It is much better to run 700- 800w in Low than Mid, with
I PA in the 1K80H manufacturer spec 24 - 30 amp,
with a 10 deg C lower temperature.? This works well with
recent FW, No overdrive issues under 800w.
This works well for me, and I retained the single color
bar, which still
changes color on the seg points. No refresh colorization.
The LDMOS works best in the 24 -30 amp rage using voltage
to control power with best heat to RF efficiency.
regards
Adrian
On 1/5/22 11:30, Nick M via
wrote:
I will give it a try , the last version it
was ?not easy to change Fahrenheit to Celsius unit
change.? I like the Fahrenheit:( ??¡á?
The color adjustment thru the CSS is
different.
On Apr 30, 2022, at 4:54 PM,
Ronald Panetta, WB2WGH <ron@...>
wrote:
?
Posted
to the Node Red files section is the V1.1 of the
SPE Linear flow. A picture of the updated
dashboard is attached. Thanks to my beta
testers! Users are encouraged to contact me if
they encounter any issues with the flow.
Material
changes since V1.0 included in this release are:
- Text on the antenna button updated to
clearly show ATU status
- Power level button for low power changed
from yellow to purple to improve readability
- SWR display previously displayed 2 decimal
digits to the right of the decimal point but
was rounded to 1 decimal digit. The rounding
has been eliminated.
- Addition of Power On and Power Off buttons.
Both should be fully functional. There is no
interlock on power off with the state
(operate/standby) and mode (RX/TX). That means
it is possible to power the SPE off in the
middle of a TX cycle.
- Power ¡°Off¡± is implemented via USB commands
to the SPE per the application programmer's
interface (API) documentation.
- Power ¡°On¡± is a different matter. This is
done through a Python script which must be
created on the Node Red server. The Read Me
has the required commands. This requires
Python to be present on the Node Red server
and it looks like the RPi Node Red
distribution includes Python. This has only
been tested on a RPi Node Red server.
- The addition of a dashboard "USB Status"
indicator to display status of the Node Red
<-> SPE communication's link.
- The addition of a new bottom row to the
dashboard for Power ¡°On¡±, USB Status and Power
¡°Off¡± buttons/indicators.
- Correction of the I PA and V PA gauges to
display "Amps" and "Volts" instead of "Units".
- Change of the USB Timeout from 500ms to
200ms as the flow gets backed up when the SPE
is powered off and later powered back on. The
dashboard was very slow (seconds to minutes)
to respond to button pushes.
Customizations
you must make (reference the flow's Read Me and
other Warning nodes at the top of the flow):
- Update the USB device name in the flow to
reflect your USB device name. Suggest using
the /dev/serial/by-id/...... path in the
definition.
- For power ¡°On¡± functionality, test the
availability of Python on your node red server
and add the Python SPE shutdown script.
- If you want temperature gauges displayed in
Fahrenheit, follow the instructions in the
Read Me. This will adjust the temperature
gauges to the Fahrenheit equivalent of 25C
(min), 65C (max), 50C (segment 1) and 60C
(segment 2).
Required
Palette Components (reference the flow¡¯s Read
Me):
- node-red-contrib-ui-level
- node-red-dashboard
- node-red-node-rbe (replaced by the "filter"
node and may already be part of your palette)
Outstanding
bugs:
- PWR gauge shows full scale and missing zero
after browser refresh.
--
Nick
W7NIK?
--
|
I got it to show the correct number , i don't know how to modify units, Undefined :(
in the gauge , the units use? say F with deg ,?
I need little help :)
--
Nick
W7NIK
|
Spe 2k , what does log? do ,? keeps a log in the SPE ?
--
Nick
W7NIK
|
Nick, I will need to look into the undefined on degrees F. Will get back to you on that and maybe do a Zoom session.?
With respect to logging, there is a comment node on the logging functionality at the top of the flow. Logging when enabled?creates/appends CSV data returned from the SPE to a file on the Node Red server. Every 20th sample is saved so at the default polling rate of 250ms, a sample is saved every 5 seconds. The original intent was for objective evidence should the SPE fail (the 1.3K and 1.5K have high failure rates). Per that same comment node the fields are:
I discovered afterwards, with a little bit of Excel magic, one can do some statistical analysis on the data. Here are some examples:
15M power output (drive level on L is a bit low): 17M power output (have not used on M or H power levels but L drive a little low):
20M: Drive levels OK on all three settings:
Ron WB2WGH
Spe 2k , what does log? do ,? keeps a log in the SPE ?
--
Nick
W7NIK
|
Klutz at the keyboard.. Let's try this again!
Ron WB2WGH ---------- Forwarded message --------- From: Ronald Panetta <ron@...>Date: Sun, May 1, 2022 at 7:29 PM Subject: Re: [nodered-hamradio] SPE Linear V1.1 flow uploaded to files section To: < [email protected]> Nick, I will need to look into the undefined on degrees F. Will get back to you on that and maybe do a Zoom session.?
With respect to logging, there is a comment node on the logging functionality at the top of the flow. Logging when enabled?creates/appends CSV data returned from the SPE to a file on the Node Red server. Every 20th sample is saved so at the default polling rate of 250ms, a sample is saved every 5 seconds. The original intent was for objective evidence should the SPE fail (the 1.3K and 1.5K have high failure rates). Per that same comment node the fields are:
Date,Time,Model,Operate/Standby,RX/TX,Bank,Input,Band,TX Ant,RX Ant,PWR LVL,PWR Out,ATU SWR,Ant SWR,PA V,PA I,Upper Temp,Lower Temp,Comb Temp,Warnings,Alarms
I discovered afterwards, with a little bit of Excel magic, one can do some statistical analysis on the data. Here are some examples:
15M power output (drive level on L is a bit low): 17M power output (have not used on M or H power levels but L drive a little low):
20M: Drive levels OK on all three settings:
Ron WB2WGH
Spe 2k , what does log? do ,? keeps a log in the SPE ?
--
Nick
W7NIK
|
Nick, the only change you needed to make in the flow was to edit the "Initialization" function node as follows. Add a comment (double slash) to the flow.set for degrees C and remove the double slash from the degrees F line as shown below. That assumes you already have the SPE configured to report Degrees F on the front panel. You may have to refresh your dashboard's browser for the change to be visible on the dashboard. If that doesn't work, we can do a quick Zoom session.
I got it to show the correct number , i don't know how to modify units, Undefined :(
in the gauge , the units use? say F with deg ,?
I need little help :)
--
Nick
W7NIK
|
That did? it ,thank you Ron
--
Nick
W7NIK
|
Adrian, your welcome. I will have to check 6M and get back to you. Ron
On Sun, May 1, 2022, 8:43 PM Adrian Fewster < vk4tux@...> wrote:
Ron, Your SPE flow has been very useful here to reveal previously
unrealized data.
How is your 6m input swr compared to the other HF bands on the 1.5KFA ?
Mine was 1.5:1 wheres the other bands were perfect. Using the MP inbuilt
ATU just on 6m
made that look nicer, and also removed little alc spikes that I saw
before this treatment.
Being able to see all values in one glance is a great tool to have.
Thankyou
73
Adrian
|
|
|
Adrian, the SPE does not report input power level. Take a look at the API document I sent you. I am reporting all data the SPE provides through the status query. By level H, are you referring to power level (minimum, middle, maximum). That is already part of the UI. Ron WB2WGH?
On Mon, May 2, 2022, 10:15 PM Adrian Fewster < vk4tux@...> wrote: Ron is it possible to add an input pwr gauge or better ; level H to the
SPE ui please ?
Thankyou
Adrian
|
Power out is another calibration thing.? Really hard to measure real power anyways to a decent accuracy. If you have a couple of devices +/-5% you are doing really good...+/-10% is more realistic for most meters.
I have an LP-700 and it is NIST quality but only claims this: Power Range¡??? ??? ??? ???????????? 0.1W to 3KW PEP (1500W Average)
Absolute Power Accuracy¡?? ?? +/- 5% at 7 MHz, 10 to 1500W.
Flatness¡??? ?? ? ? ? ? ? ? ? ? ? ?? ?? Better than +/- 3% from 1.8 to 54 MHz
?????????????????????????????????????????????? (+/- 1% typical from 1.8 to 30 MHz)
The old Bird wattmeter doesn't come close to the LP-700/500 as it claims +/-5% of full scale And 5W is the minimum plug size compared to 0.1W for the LP series. That's why you need so many plugs for the age-old Bird to get the full scale close to what you're measuring for accuracy. By the time you buy all the plugs to cover what the LP-700/500 can cover you've definitely blown your budget.? Bird's newer 4421A claims +/-3% but wont' tell you the price without a quote.? Getting to +/-1% costs $5000 for just the sensor but the also gives 25KW so works for commercial broadcast.
Mike W9MDB
On Tuesday, May 3, 2022, 04:07:03 AM CDT, Adrian Fewster <vk4tux@...> wrote:
Ron, So added pwr out to the MP ui,
The actual PO is a bit more than PO set, by 1 or 2 watts ;
On 3/5/22 14:40, Ronald Panetta, WB2WGH
wrote:
Adrian, the SPE does not report input power level. Take a
look at the API document I sent you. I am reporting all data
the SPE provides through the status query. By level H, are you
referring to power level (minimum, middle, maximum). That is
already part of the UI.
Ron WB2WGH?
On Mon, May 2, 2022, 10:15
PM Adrian Fewster < vk4tux@...>
wrote:
Ron is
it possible to add an input pwr gauge or better ; level H
to the
SPE ui please ?
Thankyou
Adrian
|
Adrian, as you discovered and Michael pointed out, there are many other ways to get exciter output/SPE power input. In my case, I have an LP-700 with sensors on both exciter and SPE outputs along with SmartSDR displaying the power setting. I don't regularly use them to "measure" drive power but rather use SmartSDR to monitor the drive setting (0-100W) to ensure drive setting is commensurate with the SPE band/power setting. With the 1.5K-FA on the low setting, measuring typical drive levels of about 7 watts accurately may be an good exercise for NIST (US National Institute for Standards and Technology) but not for me.
The main reason for LP-700 sensor on the exciter output is for trapezoid linearity monitoring and, as you requested earlier, SWR measurements. Redundancy in instrumentation is also valuable when unusual reading occur.
As to horizontal metering, I provide the dashboard configured to my sense of form/function and encourage any users to modify it to meet their needs. I think that is the general philosophy with uploaded flows.
Ron WB2WGH?
On Tue, May 3, 2022, 3:01 AM Adrian Fewster < vk4tux@...> wrote:
Ok, On that, was not sure if it could be CAT exported. H was for
horizontal.
Pwr in usually shows about 70% of actual on the SPE. I might add
a pwr out on the MP,
as pwr set is not necessarily the read pwr out.
Thankyou
Adrian
On 3/5/22 14:40, Ronald Panetta, WB2WGH
wrote:
Adrian, the SPE does not report input power level. Take a
look at the API document I sent you. I am reporting all data
the SPE provides through the status query. By level H, are you
referring to power level (minimum, middle, maximum). That is
already part of the UI.
Ron WB2WGH?
On Mon, May 2, 2022, 10:15
PM Adrian Fewster < vk4tux@...>
wrote:
Ron is
it possible to add an input pwr gauge or better ; level H
to the
SPE ui please ?
Thankyou
Adrian
|
Hi Ron, I have SPE 2K and all my messages coming back from the amp are 76 Bytes long. So they don't go further than the Switch which wants them to be 75 Bytes long. En example of a message:
???C,20K,O,R,x,1,05,1b,0r,M,0000, 0.00, 0.00,35.2, 0.0, 24, 25, 24,N,N,o,
My amp is just back from SPE ITA with a new firmware, but I cannot check the version as it is on a remote site.?
73 Simon, S53ZO 
|
Simon, thank you!!!! I had a report of this issue but have no clue who it was and been looking for someone with the issue. The 75 vs 76 byte message seems to be unique to the 2K and not present in all 2Ks. I have a 1.5K Series 2 so I have to rely on others for testing with other models.
Let me compare your example message with mine and figure out what is different. I am confident in can fix the flow to accommodate the 76 byte status message. I'll get back to you later today.
73, Ron WB2WGH?
Hi Ron,
I have SPE 2K and all my messages coming back from the amp are 76 Bytes long. So they don't go further than the Switch which wants them to be 75 Bytes long.
En example of a message:
???C,20K,O,R,x,1,05,1b,0r,M,0000, 0.00, 0.00,35.2, 0.0, 24, 25, 24,N,N,o,
My amp is just back from SPE ITA with a new firmware, but I cannot check the version as it is on a remote site.?
73
Simon, S53ZO
|
You can use an if statement and msg.payload length command to route the parsing correctly.?
Not seeing the actual payload that is how I would attack the problem.?
73 Dave wo2x Sent from my waxed string and tin cans.?
toggle quoted message
Show quoted text
On May 4, 2022, at 8:57 AM, Ronald Panetta, WB2WGH <ron@...> wrote:
? Simon, thank you!!!! I had a report of this issue but have no clue who it was and been looking for someone with the issue. The 75 vs 76 byte message seems to be unique to the 2K and not present in all 2Ks. I have a 1.5K Series 2 so I have to rely on others for testing with other models.
Let me compare your example message with mine and figure out what is different. I am confident in can fix the flow to accommodate the 76 byte status message. I'll get back to you later today.
73, Ron WB2WGH? Hi Ron,
I have SPE 2K and all my messages coming back from the amp are 76 Bytes long. So they don't go further than the Switch which wants them to be 75 Bytes long.
En example of a message:
???C,20K,O,R,x,1,05,1b,0r,M,0000, 0.00, 0.00,35.2, 0.0, 24, 25, 24,N,N,o,
My amp is just back from SPE ITA with a new firmware, but I cannot check the version as it is on a remote site.?
73
Simon, S53ZO
|
My 2k also does 76 , but there is a node where it says everything else over 75
--
Nick
W7NIK
|
Dave wo2x