开云体育

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

ISSUE REPORT: New release: improved screen capture and better trigger status

 

On Sat, Jul 25, 2020 at 05:40 AM, Erik Kaashoek wrote:
New FW released: v1.0-39
New tinySA.exe release

Erik,
? ? I experienced the following issue with the new tinySA.exe release:

1. tinySA serial port not showing in drop-down list and tinySA can't connect.

Tried to load tinySA.cfg file? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Tried to connect to tinySA serial port.
? ??

2. Strangely, even though the main interface won't run and no serial port shows as selected, the screenshot function works.

By chance I tried to capture a screenshot and it worked, even though the main screen shows no device connected.



3.? I tried deleting the 'Kaashoek\SpectrumAnalyzer' directory and letting tinySA create a fresh installation without any change.

- Herb
 

I REALLY HATE the windows serial port implementation in VC
If you do not see the serial port, unplug the device from USB and wait a second and connect again.
 

On Sat, Jul 25, 2020 at 07:34 AM, hwalker wrote:
On Sat, Jul 25, 2020 at 05:40 AM, Erik Kaashoek wrote:
New FW released: v1.0-39
New tinySA.exe release

Erik,
? ? I experienced the following issue with the new tinySA.exe release:

1. tinySA serial port not showing in drop-down list and tinySA can't connect.

Tried to load tinySA.cfg file? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Tried to connect to tinySA serial port.
? ??

2. Strangely, even though the main interface won't run and no serial port shows as selected, the screenshot function works.

By chance I tried to capture a screenshot and it worked, even though the main screen shows no device connected.



3.? I tried deleting the 'Kaashoek\SpectrumAnalyzer' directory and letting tinySA create a fresh installation without any change.

- Herb
Further investigation, after seeing that the screenshot tab works, shows that pause and resume commands are being sent to the tinySA when a single trigger is performed although no sweep data appears on the tinySA.exe screen.? Again, only the Mockup device is displayed when File->Connect is selected.

- Herb
 

On Sat, Jul 25, 2020 at 07:55 AM, Erik Kaashoek wrote:
I REALLY HATE the windows serial port implementation in VC
If you do not see the serial port, unplug the device from USB and wait a second and connect again.
Erik,
? I tried unplugging the port and cycling power on the tinySA.? The Mockup device is still the only selection that shows up in the Connect dropdown list.? The primary problem is that even though the tinySA serial port is not showing up in the tinySA.exe dropdown list it is successfully receiving commands from the application. The tinySA.exe screen is not plotting whatever data is being received back and it is not properly registering the tinySA serial port in the drop down list.

?I also noticed that 'Zero Level (dB)' value under the settings tab is still defaulting to -125.

- Herb
 

Some suggestions:

- Try again to connect, sometimes it will a second time.
- Set level/dB in the settings screen to 32 as the internal data format has changed
- Set the RBW to Auto. setting to 3kHz will be extremely slow as tinySA.exe can not yet scan in fast mode
 

On Sat, Jul 25, 2020 at 08:17 AM, Erik Kaashoek wrote:
Some suggestions:

- Try again to connect, sometimes it will a second time.
- Set level/dB in the settings screen to 32 as the internal data format has changed
- Set the RBW to Auto. setting to 3kHz will be extremely slow as tinySA.exe can not yet scan in fast mode
Erik,
? ?The level/dB setting was set to a default value of '2' which is why no sweep data was displayed. Once I changed it to '32' the sweep data displayed properly.? The sweep data was displayed 3dB too low because of the Zero level(dB) setting of -125, this needs to be -128.? Are those to values initialized in the tinySA.cfg file included in the?? directory?? The cfg file in that directory is over a month old.

level/dB changed from '2' to '32', Zero Level(dB) should be -128? ? ? ? ? ? ? ? ? ? ? ? ? ? ?After level/dB changed from '2' to '32' sweep data is visible.
? ???


After the above changes, the Mockup device is still the only device shown in the SerialPortSelector but all else is working correctly.? This is probably only a issue if more than one tinySA is connected, or a tinySA and a NanoVNA are connected since they use the same VID:PID. Note: I just connected a NanoVNA to another port on my computer and, after File->Connect only displayed the Mockup device. Returning to the Spectrum screen locked up the application when a sweep was attempted.




- Herb
 

I haven't spent enough time in tinySA.exe lately with the various changes in the tinySA itself.
 

开云体育

Hi Erik

Is seem to be able to run the sweep as stop the TinySA sweep when pressing single. If pressing Run the Tiny SA screen continuous stopped which I suppose it as it should be, but I see no trace. If setting the sweep on the TinySA it does not send frequency information to the TinySA. The Com port crashes quite often

Kind regards

Kurt

?

Fra: [email protected] <[email protected]> P? vegne af Erik Kaashoek
Sendt: 25. juli 2020 16:55
Til: [email protected]
Emne: Re: [tinysa] ISSUE REPORT: New release: improved screen capture and better trigger status

?

I REALLY HATE the windows serial port implementation in VC
If you do not see the serial port, unplug the device from USB and wait a second and connect again.

 

开云体育

Hi Erik

The change of dB/Level to 32 got it to work

Kind regards

Kurt

?

Fra: [email protected] <[email protected]> P? vegne af Erik Kaashoek
Sendt: 25. juli 2020 19:16
Til: [email protected]
Emne: Re: [tinysa] ISSUE REPORT: New release: improved screen capture and better trigger status

?

I haven't spent enough time in tinySA.exe lately with the various changes in the tinySA itself.

 

开云体育

Hi Erik

Quite understandable.

Anyway it work now with various small flaws. There is no vertical lines for log sweep. On one computer the markers is not shown on another they are.

And do not change anything for storing when sweeping as stop sweep and do what you like to do such as subtract then sweep again, els crash .
It is a big step forward. I can switch between capture and sweep provided I remember to stop the sweep. !0000point no problem ?

Kind regards

Kurt

?

Fra: [email protected] <[email protected]> P? vegne af Erik Kaashoek
Sendt: 25. juli 2020 19:16
Til: [email protected]
Emne: Re: [tinysa] ISSUE REPORT: New release: improved screen capture and better trigger status

?

I haven't spent enough time in tinySA.exe lately with the various changes in the tinySA itself.

 

开云体育

Hi Erik

Correction to my mail. The markers work on all three PC’s. MY fault not to provide an input signal of adequate strength. The small spikes on the noise line is not adequate to trigger the marker whivh is quite goof ? Sorry for the noise

However I tried the TinySA-Saver and you recommended only to use the S21 Gain. It control the TinySA for a segmented sweep but nothing seen on the S21 Gain screen Any special tricks apart from setting the S21 scales
IT shows a 0dB line ? ??Capture works fine

?

Fra: [email protected] <[email protected]> P? vegne af Kurt Poulsen
Sendt: 25. juli 2020 21:36
Til: [email protected]
Emne: Re: [tinysa] ISSUE REPORT: New release: improved screen capture and better trigger status

?

Hi Erik

Quite understandable.

Anyway it work now with various small flaws. There is no vertical lines for log sweep. On one computer the markers is not shown on another they are.

And do not change anything for storing when sweeping as stop sweep and do what you like to do such as subtract then sweep again, els crash .
It is a big step forward. I can switch between capture and sweep provided I remember to stop the sweep. !0000point no problem ?

Kind regards

Kurt

?

Fra: [email protected] <[email protected]> P? vegne af Erik Kaashoek
Sendt: 25. juli 2020 19:16
Til: [email protected]
Emne: Re: [tinysa] ISSUE REPORT: New release: improved screen capture and better trigger status

?

I haven't spent enough time in tinySA.exe lately with the various changes in the tinySA itself.

 

Something broke during the latest updates before the release.
 

On Sun, Jul 26, 2020 at 03:25 AM, Kurt Poulsen wrote:

Hi Erik

However I tried the TinySA-Saver and you recommended only to use the S21 Gain. It control the TinySA for a segmented sweep but nothing seen on the S21 Gain screen Any special tricks apart from setting the S21 scales
IT shows a 0dB line ? ??Capture works fine

?

Kurt,
? ?Erik corrected that issue in his last update to TinySA-Saver.? SweepWorker.py should have a 26 June 2020 date.

? ?

- Herb
 

Herb,

Did you test with v0.3 HW.
?I tested and it did not work.
 

I also noticed the other day that the S21 display? no longer works in tinySA-saver, but screen capture still works fine.? I had intended to test further, but my life has been so scrambled lately, I think I'm going to start? reporting anything like that immediately and not wait until I have time to explore the issue further.? If I remember correctly, I did get a straight line at zero, as if all the? data it received was zero with no variation.
 

开云体育

Hi Herb

Thank you for the hint. My download was on 25 July so 1 day too early

It works nicely

Kind regards

Kurt

?

Fra: [email protected] <[email protected]> P? vegne af hwalker
Sendt: 26. juli 2020 15:48
Til: [email protected]
Emne: Re: [tinysa] ISSUE REPORT: New release: improved screen capture and better trigger status

?

On Sun, Jul 26, 2020 at 03:25 AM, Kurt Poulsen wrote:

Hi Erik

However I tried the TinySA-Saver and you recommended only to use the S21 Gain. It control the TinySA for a segmented sweep but nothing seen on the S21 Gain screen Any special tricks apart from setting the S21 scales
IT shows a 0dB line ? ??Capture works fine

?

Kurt,
? ?Erik corrected that issue in his last update to TinySA-Saver.? SweepWorker.py should have a 26 June 2020 date.

? ?

- Herb

 

On Sun, Jul 26, 2020 at 09:04 AM, Erik Kaashoek wrote:
Herb,

Did you test with v0.3 HW.
?I tested and it did not work.
Erik,
? Yes, the screen capture I included was from my SA-20070007 v0.3 unit.? I also experienced the 'invisible trace' issue until the data 0 references were updated to data 2 in SweepWorker.py.? I can't remember if I downloaded your current TinySA-Saver repository or just made the required changes in my previous download.

? Let me know if you want me to look at anything in my current set-up.

- Herb
 

开云体育

Hi Erik and Herb

I downloaded from Erik repository. I did nor found anything on SweepWorker but I am not friend with Gibug.

I did nothing it ran straight away and came up with the S21 screen with level setting prepared. I ran the tinysa-saver.py and not an exe ?if such one exist.

Kind regards

Kurt

Fra: [email protected] <[email protected]> P? vegne af hwalker
Sendt: 26. juli 2020 19:49
Til: [email protected]
Emne: Re: [tinysa] ISSUE REPORT: New release: improved screen capture and better trigger status

?

On Sun, Jul 26, 2020 at 09:04 AM, Erik Kaashoek wrote:

Herb,

Did you test with v0.3 HW.
?I tested and it did not work.

Erik,
? Yes, the screen capture I included was from my SA-20070007 v0.3 unit.? I also experienced the 'invisible trace' issue until the data 0 references were updated to data 2 in SweepWorker.py.? I can't remember if I downloaded your current TinySA-Saver repository or just made the required changes in my previous download.

? Let me know if you want me to look at anything in my current set-up.

- Herb

1 - 18 of 18