New FW release
Version V1.0-82

Changes:
- Restoring a preset that uses a different mode is working again.

Be aware that part of a preset is the stored trace. So if you want to keep a measurement for a long time (e.g. survive a power cycle or an empty battery) do a STORE TRACE and after that STORE into a preset.
Once you do a LOAD the stored trace will appear again.

Thank you for the update.? I just got my device. It looks good.

?

Nailed it.
Many thanks !

73 Manuel; DL2MAN

OK, sorry...
I saw there?s a capture function in the TinySA.exe.....?

Hi Eric,

I could not duplicate it with Version 1.0-81.
Thanks !


Regarding your other points:
You can see from my "Screenshot", that my fundamental was externally attenuated to -27,6dBm and my RBW was between 250 and 500kHz.
I was using 40dB + 20dB + 6dB = 66dB Attenuators to get 5W of Power down to that level....
But I will have a look into the Video anyway. Thanks for your help.

@ All: Thanks for the helpful tips and the warm welcome here. I?ve already downloaded tinySA.exe, but the screen looks different from your screenshots, so I guess they were taken by nanovna-win.

@OneofEleven: I already joinded your group "nanovna-beta-test". I am using NanoVNA Saver by?Rune B. Broberg for my NanoVNA and NanoVNA-F.?

73 Manuel; DL2MAN

Yes, now I know what the problem is, not time tonight, will be tomorrow.

On Wed, Sep 9, 2020 at 10:20 PM, Manuel; DL2MAN wrote:

I bought the Tiny SA for Harmonics measurement of my uSDX Multiband Sandwich

Manual,

Make sure you watch the tinySA signal identification video

about how to use the attenuator to make sure what you measure is actually present and not internally generated.
The maximum spur free dynamic range is at an RBW of 10kHz about 72dB.
Or to say differently.
If you use an RBW of 10kHz your fundamental signal should never be more than 72dB above the noise floor otherwise the fundamental will create harmonics inside the tinySA which could harm you harmonics measurement.

Just done a test ..

If I start with low mode and recall a preset saved for high mode, the problem is there - can't enter a new set of start/stop frequencies.

If I start with high mode and recall a preset saved for high mode, the problem has gone - can enter a new set of start/stop frequencies.

Looks like you've fixed the problem I had with adding new markers - they all showed 0Hz, they now show good :)

Thank you Erik.

OneOfEleven

Is this? with presets you recall when in high mode?
Or with a preset made in one mode that you recall when being in another mode.
There is some "area of uncertainty" in the dealing with the mode when handling presets.
I used to have 4 presets for low and 4 separate (numbered 5-8 for high. That may be a better approach?

New FW released
Version V1.0-81

Changes:
- Corrected a number of marker frequency bugs.

I must have been interrupted during the updating of the marker frequency mechanism and forgotten to finish it.
A number of marker frequency bugs have been solved. Let me know if there still are remaining

On Thu, Sep 10, 2020 at 08:07 AM, OneOfEleven wrote:

On Thu, Sep 10, 2020 at 03:52 PM, Manuel; DL2MAN wrote:

How do you capture those nice Screenshots ? Seems much better then fotographing the display ;)

73 Manuel; DL2MAN

For me I use my own software (currently NanoVNA-App) to capture the screens Manuel. I also use it to upload new firmware to the TinySA.

Does TinySA-saver not have the screen capture option ?

Manuel,
? If you are running Windows then I suggest either OneOfEleven's NanoVNA_Win or Erik's tinySA.exe application for capturing the tinySA screen.? For Linux or MacOS then NanoVNA-Saver is your best choice.

? ?As OneOfEleven posted, her application can also upload DFU files and has a nice built-in terminal application for communicating with the tinySA.? Those are all side benefits of her program as it is primarily written for the NanoVNA.

?- Herb

?- Herb

--

On Thu, Sep 10, 2020 at 03:52 PM, Manuel; DL2MAN wrote:

How do you capture those nice Screenshots ? Seems much better then fotographing the display ;)

73 Manuel; DL2MAN

For me I use my own software (currently NanoVNA-App) to capture the screens Manuel. I also use it to upload new firmware to the TinySA.

Does TinySA-saver not have the screen capture option ?

Thanks for trying to confirm my results !

Please allow me an off topic "Noob" Question:

How do you capture those nice Screenshots ? Seems much better then fotographing the display ;)

73 Manuel; DL2MAN

On Thu, Sep 10, 2020 at 07:01 AM, dekagon wrote:

Herb,

I cannot confirm this error. I did upgrade to version 1.0.80 too and did the following experiment:
- connected High-and Low ports with a short semiflex cable.
- CW Generator on High Port on (10 MHz) with choosen into Low Input (pic 1)
- then FREQUENCY->STOP 45 MHz (pic 2)
- turned? HARMONIC Measurement on (pic 3) -> everything looks OK
- turned HARMONIC Measure off (pic 4)

So I cannot confirm the results...

Chris,
? Yes, I could not confirm the issue using full span or using the internal calibrator signal.? Once I used an external CW signal and matched Manuel's settings as closely as possible I was able to confirm it.

? The issue is not easy to reproduce and appears to only show up under certain measurement conditions.? Once the issue is reproduced its repeatable, as Manuel noted. For me the issue is more of a distraction because its pretty obvious the marker GHz value is incorrect.? I'm sure Erik will eventually track down the cause.?

??
- Herb

开云体育

Herb,

I cannot confirm this error. I did upgrade to version 1.0.80 too and did the following experiment:
- connected High-and Low ports with a short semiflex cable.
- CW Generator on High Port on (10 MHz) with choosen into Low Input (pic 1)
- then FREQUENCY->STOP 45 MHz (pic 2)
- turned? HARMONIC Measurement on (pic 3) -> everything looks OK
- turned HARMONIC Measure off (pic 4)

So I cannot confirm the results...

I will try again with an external Signalgenerator later..

Chris

 ---
'Everything should be made as simple as possible, but not simpler.' -- Albert Einstein

On Thu, Sep 10, 2020 at 01:55 AM, Erik Kaashoek wrote:

Can you test with the latest FW?

Erik,
? Using Manuel's settings, I can confirm the issue he reported using the latest version 1.0-80.? Setting up the measurement using 'Measure->Harmonics', I could only see the GHz suffix appear briefly in the 3rd marker.? After turning off ''Measure->Harmonics' the 3rd marker mostly showed the incorrect value with GHz suffix. The correct value would appear intermittently.? Also, very strangely, a 4th marker would flash in very briefly of its own volition.?

? Incorrect 3rd marker value? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?Correct value appearing intermittently
??? ??


?- Herb

Thanks. Will test later today when back home