I read in the release notes that there is a power overshot in the Alpha release.
Can someone tell me is this when the slider power setting is less than 100% or when the max power for a band is set in the options settings to less than full power or are both setting problematic.

For build 15092022, FW 80.8, I have overshoot occur regardless of the power setting slider.

GL Tom W3FRG

Thanks Tom. When you say "regardless of any power setting slider" I assume thats only when its less than 100% or are you saying its doing it even at full power setting.
Sorry I just wont to be clear of what this will do to my connected 6m and 2m LDMOS amps.
Im currently running them with 3db pads on the input with the power settings in the "Options" menu set to 10w on 6m and 5w on 2m.
If the power overshot is going to over ride this and drive 20w on 6m and 8w on 2m I could be in trouble!

Roger ZL3RC

I don't operate 6 or 2m but over the 100% output power operating range the problem occurs.
I drive the RF 2K+ amp.

Tom W3FRG

1. The real power output is slightly model dependent.

2. In-build power meter is rather indicative. It is not scientific measurement device.

3. When setting power output slider to some %, then it is:
a. Not linear within the band (if 100% is 100W it does not mean 40% will be 40W)
b. Not corresponding on same %/output fo all bands. It is band individual.

4. There are two combined levels of output power control in ESDR3:
- via Settings-Calibration
- via Band Manager - Power
Combination of both should provide very granular power output per band.

5. When using lowered power output (for example to drive external devices) and the power level is very critical (for example - driving MOSFET ext PA), then it is highly recommended to measure and set power output individually per band, using precise external power meter.

The above is valid for at least last 5 alpha versions of ESDR3.

FYI: Below are 100% output per band on 1000W dummy load on internal and external power meter on SS2DX PCB rev11 (Gen2??):
(see attached screenshots for screen captures)
160M External meter: 112W
80M External meter: 114W
40M External meter: 118W
30M External meter: 112W
20M External meter: 103W
17M External meter: 98W
15M External meter: 107W
12M External meter: 101W
10M External meter: 105W
6M External meter: 41W

Remaining screenshots

Thanks for the detailed reply but its still not answered my question.
So are you saying the comments in the release notes is incorrect now and the problem of power overshot is gone.
Reading your comment at 5 it seams to indicate this.
"5. When using lowered power output (for example to drive external devices) and the power level is very critical (for example - driving MOSFET ext PA), then it is highly recommended to measure and set power output individually per band, using precise external power meter.

The above is valid for at least last 5 alpha versions of ESDR3."

The reason Im trying to get this clarified is Im very keen to move move over to ESDR3 but only if its going to work safely.
I dont like the idea of switching back and forth in FW versions, although other seam to think that isn't a big deal, but my years in IT system deployment tells me other wise.

Im a very keen VHF and Microwave operator and looking forward to have all my transvertes controlled from the very nice options available in ESRD3

Thanks

Roger ZL3RC

Not sure what exactly part of Release Notes you are referring. If this is in regards to "Switch from RX to TX may generate an impulse with high amplitude, be careful using external power amplifiers. Firmware bug.", then there are some news on that matter and, I believe, this part may be removed from next Notes, after EE look at the recent test results.

However, this sentence in Release notes is about completely different story, it is not related to my previous message #6

What Release Notes talking about in regards to "impulse" - is what, up until very recent, was believed to be a FW bug. It was even acknowledged by EE and waiting in a queue to fix. Fortunately (after additional investigation) this "impulse" appears to be a cosmetic kind, and not related to any real HF impulse. The key is that when (specifically in Tune mode) the Tune button pressed, the in-build power meter indicator produces visual "power jump" on very first seconds - say, you are on 20% output on SS2DX 20m band, which is roughly 15-16 watts; when Tune pressed the in-build power meter "jumps" to 17.5W and in next second-two returns to 16W. This exactly behaviour was believed to be a bug and everyone thought a real impuls +1.5W above set is produced. However it is not. It is just an effect from current implementation of in-build power meter visual effect, which tries to "simulate" analogue needle amplitude. And in backend, the external power meter register same 16W constant output from first TX millisecond.

Assuming my knowledge is correct and EE did not touch this "bug" as yet, hence, I would say, it was false alarm and no such bug exast. The details of confirming experiment were published in Telegram.

---

However, with all what was said above, please note that ESDR3 is still in alpha mode. It might go to beta very soon, this is true. However. Up until Release 1.0 it shoudl be treated "experimental". It means that you may expect bugs appear and dissapear, as minimum.

Have been using ESDR3 for a few days now and not seeing any power overshoot on going to TX.
Working mainly on 6m and 2m with power set on 6m to 8w and on 2m 4w. On both these bands I run QRO LDMOS amps which have 3db pads on the input.