tinysa@groups.io | Messages

Re: ZS-407 is here

#19043

Re: Issues with TinySA USB Connection in C#

#19042

Could you please advise how to use "scanraw" instead of "data" console command in this case.

Thx in advance.

Efficient Frequency and Power Reading via USB: Seeking Best Practices

#19041

I need to read all frequencies and their power using commands that can be sent via a USB port.
I can achieve this in a couple of ways:

1. freq_data = device.get_freq_data()

? ? data2 = device._data(2)?

2. device._send_command("scan 220000000 2500000000 450 3\r")

? ? scan = device._fetch_data()?

?

The first method works twice as fast.
Can you suggest any other commands that might achieve the same result? Perhaps there are best practices for implementing this more efficiently?

Re: Issues with TinySA USB Connection in C#

#19040

On Thu, Jan 9, 2025 at 10:01 PM, <voloshyn.v.v@...> wrote:

I started the Python script I provided yesterday, and it has been running continuously. Now, I see that more than 29,000 iterations have been executed successfully.

I knew Python's serial port driver was better than the one for C# but I didn't realize it was so much faster.? I have been running a C# script using the current firmware and the suggestions I made yesterday since 11:30 pm last night and in 6 hours I've only gotten to 8,000 iterations.? I'm better at C# but may have to consider using Python as a primary programming language for instrument control.?

?

Instrument Manufacturer ... ?2019-2024 Copyright @Erik Kaashoek
Instrument Name ........... ?tinySA ULTRA
Instrument Firmware Version ... tinySA4_v1.4-177-g1687fbc
Instrument Battery Voltage ... 4.256 Vdc

?

2025-01-09 23:23:06: 1: (-43.7, 105000720)
2025-01-09 23:23:09: 2: (-44.7, 105006293)
2025-01-09 23:23:12: 3: (-42.7, 105023508)
2025-01-09 23:23:14: 4: (-42.7, 105099651)
2025-01-09 23:23:17: 5: (-41.7, 105122494)
2025-01-09 23:23:20: 6: (-41.2, 105116515)

...........

2025-01-10 05:31:37: 8004: (-46.3, 105079387)
2025-01-10 05:31:40: 8005: (-45.8, 105129399)
2025-01-10 05:31:43: 8006: (-46.3, 105174031)
2025-01-10 05:31:46: 8007: (-45.8, 105060340)
2025-01-10 05:31:48: 8008: (-46.3, 105230012)
2025-01-10 05:31:51: 8009: (-46.3, 105040357)

?

Herb

Re: measure>harmonics, some remarks

#19039

On Wed, Jan 8, 2025 at 09:42 PM, Erik Kaashoek wrote:

Correct. There are very low level internally generated spurs at 60 MHz and it's harmonics.

This is according the spec.

?

Thanks for confirming my thought and ensuring me I did not make a mistake here.

The sa is really a great device and exploring it's characteristics is a lot of fun and education.

And sometimes surprising, like the feature to scroll through the stored images.

?

regards

?

Henk

Re: Issues with TinySA USB Connection in C#

#19038

On Thu, Jan 9, 2025 at 09:00 PM, hwalker wrote:

?

Well, this is definitely an error that appeared after
tinySA4_v1.3-435-g391dca6
HW Version: 167.

I started the Python script I provided yesterday, and it has been running continuously. Now, I see that more than 29,000 iterations have been executed successfully.

Re: Issues with TinySA USB Connection in C#

#19037

On Thu, Jan 9, 2025 at 05:23 AM, <voloshyn.v.v@...> wrote:

I see exception on this version and newer.

tinySA4_v1.3-438-gd7f97cd
HW Version:167
2025-01-09 14:26:29: 843: (-50.75, 30159987.0)?
An error occurred: could not convert string to float: '1 17 30974320 -50.75'
reseted

?

?

I did some testing over the past day and suspect that in the tight loop that you are running, without doing anything with the amplitude or frequency data, the console 'frequency' and 'data' commands eventually cannot keep up with the data flow and are causing the USB port to lock-up until the tinySA is rebooted.

?

I am not receiving any errors other than, " The operation has timed out", after a variable number of iterations occurring in either the "frequencies", "data 1" or "data 2" console commands.?

?

When only querying the "marker 1" console command in a tight loop I did not receive any time out errors over the course of 6hrs and over 22,000 iterations:

?

Read Marker Value Only
2025-01-09 06:01:10: 1: (-38.8, 105072304)
2025-01-09 06:01:11: 2: (-38.8, 105039346)
2025-01-09 06:01:11: 3: (-38.8, 105038222)
2025-01-09 06:01:12: 4: (-39.3, 105043709)
2025-01-09 06:01:13: 5: (-39.8, 105063102)
2025-01-09 06:01:13: 6: (-39.8, 105038222)
2025-01-09 06:01:14: 7: (-39.8, 105038222)
2025-01-09 06:01:15: 8: (-40.3, 105038222)
..........
2025-01-09 09:58:55: 22107: (-40.3, 105031589)
2025-01-09 09:58:56: 22108: (-40.3, 105059756)
2025-01-09 09:58:57: 22109: (-40.3, 105053965)
2025-01-09 09:58:57: 22110: (-40.3, 105031589)
2025-01-09 09:58:58: 22111: (-40.8, 105031589)
2025-01-09 09:58:59: 22112: (-40.3, 105040357)
2025-01-09 09:58:59: 22113: (-40.3, 105052993)

?

If instead of constantly querying "frequencies", I queried "sweep" and used the returned start, stop and points values to create a frequency array using a "LinSpace" like function, then I did not receive any time out errors over the course of 2hrs and over 5,500 iterations:

?

Read Marker and LinSpace Frequency array Values?
2025-01-09 12:07:55: 1: (-42.8, 105102399)
2025-01-09 12:07:56: 2: (-42.8, 105109582)
2025-01-09 12:07:58: 3: (-42.8, 105073001)
2025-01-09 12:07:59: 4: (-42.8, 105095900)
2025-01-09 12:08:00: 5: (-42.8, 105064811)
2025-01-09 12:08:01: 6: (-42.8, 105076975)
2025-01-09 12:08:03: 7: (-42.8, 105059756)
2025-01-09 12:08:04: 8: (-42.3, 105080071)
2025-01-09 12:08:05: 9: (-42.3, 105053965)
..........
2025-01-09 14:06:10: 5497: (-39.8, 105056503)
2025-01-09 14:06:12: 5498: (-39.8, 105055678)
2025-01-09 14:06:13: 5499: (-39.8, 105082261)
2025-01-09 14:06:14: 5500: (-39.8, 105080641)
2025-01-09 14:06:16: 5501: (-40.3, 105053075)
2025-01-09 14:06:17: 5502: (-39.8, 105104557)
2025-01-09 14:06:18: 5503: (-39.8, 105104557)

?

The "data 1" console command is a holdover from its NanoVNA origins and not of particular use.? The "data 2" console command returns the current trace data but in a tight loop the scanraw command is preferred.? QtTinySA uses the scanraw command to provide a fast and responsive graphical display of trace data.

?

If instead of constantly querying "data 1", I rather queried "scanraw", then I did not receive any time out errors over the course of 4hrs and over 5,600 iterations:

?

Read Marker, LinSpace Frequency array, and Scanraw Values?
2025-01-09 15:02:08: 1: (-38.3, 105035153)
2025-01-09 15:02:11: 2: (-37.3, 105023508)
2025-01-09 15:02:13: 3: (-37.8, 105023508)
2025-01-09 15:02:16: 4: (-38.3, 105013851)
2025-01-09 15:02:18: 5: (-40.2, 105084851)
2025-01-09 15:02:21: 6: (-40.2, 105067951)
2025-01-09 15:02:23: 7: (-40.2, 105067951)
2025-01-09 15:02:26: 8: (-40.3, 105019701)
..........
2025-01-09 19:02:30: 5657: (-38.3, 105005274)
2025-01-09 19:02:32: 5658: (-38.8, 105010397)
2025-01-09 19:02:35: 5659: (-38.3, 105010397)
2025-01-09 19:02:37: 5660: (-38.8, 105011863)
2025-01-09 19:02:40: 5661: (-38.3, 105011863)
2025-01-09 19:02:42: 5662: (-38.3, 105011863)
2025-01-09 19:02:45: 5663: (-38.3, 104978805)

?

Erik has indicated there may be some improvements he can make in the firmware, but I suspect that the way you are using the "frequencies" and "data" console commands in a tight loop that you will still experience some flow control related USB lockup issues when operating over an extended length of time.

?

For the best performance I suggest:

?

1. Create your frequency array in code using "sweep" and LinSpace.

2. Use "scanraw" instead of "data" console command.

3. Verify that your computer does not remove power to your USB ports to save energy.

?

I only program for my own pleasure so hopefully Erik or someone else more knowledgeable than me will correct any errors in my post.

?

Herb

Re: Issues with TinySA USB Connection in C#

#19036

Many, many thanks

This is exactly when a change was made to a part of the code that uses multiple threads.

I will need some time investigate this.

--

Designer of the tinySA
For more info go to

Re: Issues with TinySA USB Connection in C#

#19035

I think i foound version when this error appeared.

?

I see exception on this version and newer.

tinySA4_v1.3-438-gd7f97cd
HW Version:167
2025-01-09 14:26:29: 843: (-50.75, 30159987.0)?
An error occurred: could not convert string to float: '1 17 30974320 -50.75'
reseted

?

And on this version it work stable more then 1500 iterations and keep working.

tinySA4_v1.3-435-g391dca6
HW Version:167

Re: 5.8GHz wideband video signal measurements

#19034

It seems that the problem that was causing the 404 error, reported by me and other users, is fixed. I can now access the page for all products, tinySA Ultra+ and the various additional external LNAs ...

Re: ZS-407 is here

#19033

It seems that the problem that was causing the 404 error, reported by me and other users, is fixed. I can now access the page for all products, tinySA Ultra+ and the various additional external LNAs ...

Re: measure>harmonics, some remarks

#19032

On Wed, Jan 8, 2025 at 03:12 AM, pa3cqn wrote:

BTW: Something I noticed on my sa: there is a signal on 60 MHz around -100 dBm with all harmonics present that seems to be internal. Only visible if you set a small RBW to lower the noise floor.?

Correct. There are very low level internally generated spurs at 60 MHz and it's harmonics.

This is according the spec.

--

Designer of the tinySA
For more info go to

Re: New FW release: Improved correction curves for ZS406

#19031

All ultra devices use one common FW?

Inside the FW it is detected which hw is present and the differences are covered by this single sw.

So there is no special zs406 version but a FW release may contain changes relevant to only one hw.

--

Designer of the tinySA
For more info go to

Re: New FW release: Improved correction curves for ZS406

#19030

On Wed, Jan 8, 2025 at 06:06 AM, Dino Papas wrote:

Hi Erik - thanks for all the hard work, much appreciated. Do these new FW upgrades that are specifically identified as being for the new ZSXXX series of analyzers also apply to the original Ultra devices prior to the new series being introduced?

Good question...

?

Roger

Re: New FW release: Improved correction curves for ZS406

#19029

It shows which version is which in the WiKi.

All you have to do is read it.

?

Re: New FW release: Improved correction curves for ZS406

#19028

QSL

?

Thank you Erik! ?Your continued efforts are much appreciated!

Re: New FW release: Improved correction curves for ZS406

#19027

If you device has "Ultra" at the front it's a ZS405

If it has "Ultra+" you have either a ZS406 or ZS407 and the label at the back specifies which of the two

--

Designer of the tinySA
For more info go to

Re: New FW release: Improved correction curves for ZS406

#19026

I have a TinySA that has unknown type number.? I bought it used from eBay and do not know its age.

There is no such number on the label on the backside of my unit.? The only appearance of "ZeenKo" is the very bottom line on the rear label? that reads "Designed by Erik in Netherlands, Made by ZeenKo in China".? Nothing else below it.

Any thoughts?? (I am getting enormously old and I may just not be seeing the type number...)? ;-)

Dan Heather N1DH

Middleboro MA

Re: New FW release: Improved correction curves for ZS406

#19025

Also with latest FW?

CONFIG/VERSION

?

--

Designer of the tinySA
For more info go to

Re: New FW release: Improved correction curves for ZS406

#19024

It says so on the back beneath the name Zeenko.

开云体育