开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育
  1. Tinysa
  2. Topics

New FW release: Add marker PEAK SEARCH

 

New FW released
Version v0.1-58

Changes:
- Added MARKER/SEARCH MARKER/PEAK SEARCH which disables the tracking attribute of the active marker and positions the active marker as the global maximum level
- Corrected a small error in marker search which could cause a 0.5dB error in finding a maximum or minimum

This search option is useful to quickly find a global maximum, even if this maximum is less than the NOISE LEVEL above the surrounding signals
Be aware a possible zero Hz peak is not automatically excluded in the search, to avoid, set the start frequency of the sweep to an appropriate value.
 

Wow Erik!? I wasn't expecting a change until your next major release - if any.? I noticed the following after updating to 0.1-58 and doing 1.) clearconfig 1234, 2.) reset, 3.) leveloffset low 0 (saved from previous version), 4.) devceid 20070007 and 5.) saveconfig:

1. The marker->peak button places the selected marker at the first global peak as expected.? An unexpected behavior is that immediately afterwards the wheel does not work to move the marker left or right.? At wider spans, the behavior is that the wheel will move the marker right but not left.? The marker can be dragged left or right using the stylus, after which the wheel works normally.? The expected behavior was that the selected marker would be positioned to the global maximum value but otherwise would have normal marker mode behavior.? This unwanted behavior is particularly noticeable when the display is paused.

2. I also noticed that when the display is paused, and with multiple markers displayed, selecting a marker with the stylus doesn't update the marker selection until some other operation is performed.

3. A bug seems to have slipped in where the internal attenuation is not properly corrected for.? This is unrelated to the new peak search feature but may be related to your 0.5dB error correction.

-20dBm external signal? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? same signal with internal 3dB attenuation
? ? ?

I recommend that users skip this update.

- Herb
 

Herb,

Please download again and the attenuation problem should be solved.
I will look into the other issues
 

开云体育

Hi Erik

The calibration procedure has been corrupted with this new version. Actual power calibration at -20dBm input find a marker value at -40dBm at first attempt. At second attempt to calibrate ?-20dBm marker data as it should. If you power then off and on again then the marker level is 0dBm for -20dBm input level.
The Level Cal is also harmed as the same 20dB jump is also present when power off and on again.

Kind regards

Kurt

?

?

Fra: [email protected] <[email protected]> P? vegne af Erik Kaashoek
Sendt: 24. august 2020 13:48
Til: [email protected]
Emne: [tinysa] New FW release: Add marker PEAK SEARCH

?

New FW released
Version v0.1-58

Changes:
- Added MARKER/SEARCH MARKER/PEAK SEARCH which disables the tracking attribute of the active marker and positions the active marker as the global maximum level
- Corrected a small error in marker search which could cause a 0.5dB error in finding a maximum or minimum

This search option is useful to quickly find a global maximum, even if this maximum is less than the NOISE LEVEL above the surrounding signals
Be aware a possible zero Hz peak is not automatically excluded in the search, to avoid, set the start frequency of the sweep to an appropriate value.

 

Release V1.0-59 that solved problems 1 and 3
Solving problem 2: when multiple marders AND display paused AND dragging a marker the marker info is not updated
will take some more time.
 

On Mon, Aug 24, 2020 at 08:38 AM, Kurt Poulsen wrote:
The calibration procedure has been corrupted with this new version.
Kurt,

Thanks for testing to quickly!
The level cal problem was caused by the attenuator problem and is solved in v1.0-59
 

开云体育

Hi Erik

I did see you made a new update and all three TinySA is updated and calibration is OK, thank you

Kind regards

Kurt

?

Fra: [email protected] <[email protected]> P? vegne af Erik Kaashoek
Sendt: 24. august 2020 17:50
Til: [email protected]
Emne: Re: [tinysa] New FW release: Add marker PEAK SEARCH

?

On Mon, Aug 24, 2020 at 08:38 AM, Kurt Poulsen wrote:

The calibration procedure has been corrupted with this new version.

Kurt,

Thanks for testing to quickly!
The level cal problem was caused by the attenuator problem and is solved in v1.0-59

 

开云体育

UPS

It was version revised 0.1.0-58 I updated to so here we go again ?

Kind regards

Kurt

?

Fra: [email protected] <[email protected]> P? vegne af Erik Kaashoek
Sendt: 24. august 2020 17:50
Til: [email protected]
Emne: Re: [tinysa] New FW release: Add marker PEAK SEARCH

?

On Mon, Aug 24, 2020 at 08:38 AM, Kurt Poulsen wrote:

The calibration procedure has been corrupted with this new version.

Kurt,

Thanks for testing to quickly!
The level cal problem was caused by the attenuator problem and is solved in v1.0-59

 

On Mon, Aug 24, 2020 at 08:48 AM, Erik Kaashoek wrote:
Release V1.0-59 that solved problems 1 and 3
Solving problem 2: when multiple marders AND display paused AND dragging a marker the marker info is not updated
will take some more time.
Erik,
? Just updated to v1.0-59.? Internal attenuation issue is resolved.? Still having issue with problem 1 as follows:

Turn on marker 2? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?marker->peak search.? Afterwards can only use the wheel to?
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?move right from peak. Left from peak is not working.
? ? ? ? ? ??


- Herb
 

On Mon, Aug 24, 2020 at 10:45 AM, hwalker wrote:
Just updated to v1.0-59.? Internal attenuation issue is resolved.? Still having issue with problem 1 as follows:
Herb,

After a marker search should using the lever jump from maximum to maximum or just move the marker to any position? Or should this depend on what previous action was done (e.g. left/right marker search (jump) or peak search (any position)
 

On Tue, Aug 25, 2020 at 07:44 AM, Erik Kaashoek wrote:


After a marker search should using the lever jump from maximum to maximum or just move the marker to any position? Or should this depend on what previous action was done (e.g. left/right marker search (jump) or peak search (any position
==============================================
Erik,
? Both of those actions make sense to me.? My expected behavior was that after peak search the marker would be in normal mode.? If the user wanted to jump peak to peak afterwards they could search max-left/right, otherwise the lever would just move the marker to any position.

- Herb

1 - 11 of 11