Re: New FW release: Improved correction curves for ZS406
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
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
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
QSL
?
Thank you Erik! ?Your continued efforts are much appreciated!
|
Re: New FW release: Improved correction curves for ZS406
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
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
Also with latest FW?
CONFIG/VERSION
?
--
Designer of the tinySA
For more info go to
|
Re: New FW release: Improved correction curves for ZS406
It says so on the back beneath the name Zeenko.
|
Re: New FW release: Improved correction curves for ZS406
Erik,
?
How can I determine if my tinySA Ultra is a ZS406?
?
Thanks,
?
Mike N2MS
?
?
toggle quoted message
Show quoted text
On 01/08/2025 2:49 AM EST Erik Kaashoek <erik@...> wrote:
?
?
New FW release
Version V1.4193
tinySA Ultra ZS406
?
Changes:
- Improved level correction curves for the ZS406
--
Designer of the tinySA
For more info go to
_._,_._,_
.
|
Re: New FW release: Improved correction curves for ZS406
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?
?
Dino
|
measure>harmonics, some remarks
So measuring harmonics uses the multiband feature and span sets the measuring span around the fixed harmonics calculated from the center frequency.
But after setting measure 'off' multiband is still enabled. Is this a possible bug?
?
Also: if you have a personal set of multiband measurements don't forget to save this to sd, because measuring harmonics will replace your settings.
?
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.?
Some internal xtal?
|
New FW release: Improved correction curves for ZS406
New FW release
Version V1.4193
tinySA Ultra ZS406
?
Changes:
- Improved level correction curves for the ZS406
--
Designer of the tinySA
For more info go to
|
Re: What to do when a selftest fails
Hi.
I replaced U22 with an AS179-92LF that I received from Digikey yesterday.
My TinySA Ultra is now capable of calibration and passes all self-tests.
I would like to thank Erik and everyone who gave me advice.
I hope that 2025 will be a good year for everyone.
|
Re: Pre-sale, tinySA ULTRA plus
|
Display size
|
3.98” IPS-TFT LCD (480×320)
|
3.98” IPS-TFT LCD (480×320)
|
3.98” IPS-TFT LCD (480×320)
|
?
Was the older 405-model also upgraded to an IPS display, I remember talks about 1? year back, but not sure if it was effected in practise.
The unit most people have is likely the old TFT LCD display variant, which has TFT's infamous off-axis contrast & color-shifting, so the move to IPS LCDs is positive if it's a good IPS panel without too much glow/blooming.
|
Re: Issues with TinySA USB Connection in C#
Anyone that can test which older version does not have this problem?
Just to rule out I introduced a concurrency bug in some release
--
Designer of the tinySA
For more info go to
|
Re: Issues with TinySA USB Connection in C#
I have the same error on this version also
tinySA4_v1.4-99-g8bfcfd7
HW Version:V0.4.5.1 ? ?
|
Re: Issues with TinySA USB Connection in C#
i have the same orre on the latest version of TinySA firmware
tinySA4_v1.4-192-g73fe677
HW Version:V0.4.5.1 ? ? ?
2025-01-07 18:23:07: 1: (-66.8, 97976963.0)?
2025-01-07 18:23:09: 2: (-65.0, 32418392.0)?
2025-01-07 18:23:12: 3: (-65.3, 97881867.0)?
2025-01-07 18:23:14: 4: (-64.8, 98086843.0)?
2025-01-07 18:23:16: 5: (-63.0, 33212113.0)?
2025-01-07 18:23:18: 6: (-63.8, 98083796.0)?
2025-01-07 18:23:20: 7: (-63.5, 34743875.0)?
2025-01-07 18:23:22: 8: (-64.8, 98208663.0)?
2025-01-07 18:23:24: 9: (-63.5, 33492749.0)?
2025-01-07 18:23:27: 10: (-65.0, 32733354.0)?
2025-01-07 18:23:29: 11: (-65.2, 98325254.0)?
2025-01-07 18:23:31: 12: (-70.7, 371754465.0)?
2025-01-07 18:23:33: 13: (-65.2, 98178823.0)?
2025-01-07 18:23:35: 14: (-66.7, 98162583.0)?
2025-01-07 18:23:37: 15: (-63.5, 32824419.0)?
2025-01-07 18:23:40: 16: (-63.0, 33520768.0)?
2025-01-07 18:24:12: 17: (-65.2, 98137148.0)?
An error occurred: could not convert string to float: '1 19 33606812 -6.10e+01'
reseted
An error occurred: Write timeout
Traceback (most recent call last):
? File "C:\Source\TinyPyton\TinySAServer1.py", line 18, in run_server
? ? freq_data = device.get_freq_data()
? File "C:\Source\TinyPyton\TinySAModule.py", line 240, in get_freq_data
? ? return self._fetch_frequencies()
? ? ? ? ? ?~~~~~~~~~~~~~~~~~~~~~~~^^
? File "C:\Source\TinyPyton\TinySAModule.py", line 129, in _fetch_frequencies
? ? x.append(float(line))
? ? ? ? ? ? ?~~~~~^^^^^^
ValueError: could not convert string to float: '1 19 33606812 -6.10e+01'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
? File "C:\Source\TinyPyton\TinySAServer1.py", line 18, in run_server
? ? freq_data = device.get_freq_data()
? File "C:\Source\TinyPyton\TinySAModule.py", line 240, in get_freq_data
? ? return self._fetch_frequencies()
? ? ? ? ? ?~~~~~~~~~~~~~~~~~~~~~~~^^
? File "C:\Source\TinyPyton\TinySAModule.py", line 124, in _fetch_frequencies
? ? self._send_command("frequencies\r")
? ? ~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
? File "C:\Source\TinyPyton\TinySAModule.py", line 81, in _send_command
? ? self.serial.write(cmd.encode())
? ? ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
? File "C:\Users\User\AppData\Local\Programs\Python\Python313\Lib\site-packages\serial\serialwin32.py", line 325, in write
? ? raise SerialTimeoutException('Write timeout')
serial.serialutil.SerialTimeoutException: Write timeout
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
? File "C:\Source\TinyPyton\TinySAServer1.py", line 41, in <module>
? ? start_server()
? ? ~~~~~~~~~~~~^^
? File "C:\Source\TinyPyton\TinySAServer1.py", line 11, in start_server
? ? run_server(device)
? ? ~~~~~~~~~~^^^^^^^^
? File "C:\Source\TinyPyton\TinySAServer1.py", line 38, in run_server
? ? run_server(device)
? ? ~~~~~~~~~~^^^^^^^^
? File "C:\Source\TinyPyton\TinySAServer1.py", line 36, in run_server
? ? device._send_command("reset\r")
? ? ~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^
? File "C:\Source\TinyPyton\TinySAModule.py", line 83, in _send_command
? ? _ = self.serial.readline() ?# discard empty line
? File "C:\Users\User\AppData\Local\Programs\Python\Python313\Lib\site-packages\serial\serialwin32.py", line 275, in read
? ? raise SerialException("ClearCommError failed ({!r})".format(ctypes.WinError()))
serial.serialutil.SerialException: ClearCommError failed (PermissionError(13, 'The device does not recognize the command.', None, 22))
|
See FAQ in WiKi
--
Designer of the tinySA
For more info go to
|
And what LNA is used in TinySA Ultra? It seems mine is also out of order. It does not pass tests 10 and 14.
|
Re: Mesure IMD with Two Tone and TinySA Ultra
Which brings up a good point.? When testing for weak signals such as IMD you should first look for the strongest signal that your device will be exposed to.? That includes other signals that may be present at the location you are at.? My Anritsu Sitemaster and Cellmaster both alert me with a tone to warn me that a high level signal above it's allowable level is present.? This may be a high powered FM or TV station at the site.? Also, you may be tempted to reduce attenuation to be able to see the IMD, only to allow another signal to cause damage to your device.
Joe, K1ike
toggle quoted message
Show quoted text
On 1/5/2025 4:19 AM, MaxPi via groups.io wrote: Firstly, 100 watts is 50 dBm, so the output power after your attenuator (50dBm - 40dB = 10dBm) will exceed the permitted 6 dBm for the TinySA. Although I would highly recommend not to exceed 0dBm at the input, for all signals including harmonics.
|
Roger Need
Clyde Lambert
Dan Heather
Takuo Watanabe
Enchilada
Владимир Горлов