开云体育

A new measurement example is added to demonstrate the dynamic range of the tinySA in measuring harmonics coming from a transmitter

For those using Linux
Multiple segments is now working in tinySA-saver


The tinySA data is in the S21Gain (dB) graph. Suggest to remove all other displayed charts except S21 Gain
Make sure you set the tinySA in high or low input mode before running tinySA-saver
Screen capture works. See "manage"/"screenshot"
Apart from making the data visible I did not do ANYTHING to make it robust

That did it!

Cool, I'll give it a shot.? Thanks, Allison.

I used dfu-util and it worked.? Linux Mint 18.3.

Command line used.
?$ sudo dfu-util? -a 0 -s 0x08000000:leave -D ch.bin

I was going to use the ST software but due to screw up on their end never
got it to down load.

dfu-util is in the? debian/ubunto/mint package system.??
Make sure the cable is valid for data and your groups allow the connection.

Allison
-----------------------------------------
Please post here, direct emails go to a dead letter box.

Has anybody been able to update the firmware from Linux?? I downloaded and installed the software from ST.? I have not been able to get the GUI to run at all.? I am able to connect from the commandline, but when I try to download the firmware to the tinySA, it tells me I must connect first.? I am running Linux Mint 19.3 Cinnamon.? Any help?

The tinySA does a double conversion with a first high IF at 433MHz for its low input IF? range (till 350MHz). Performance is more then sufficient for measuring spectral purity of HF transmitters. The high range, till 960MHz, is not a harmonic mode like nanoVNA but uses a separate direct conversion IQ mixer to a IF of 700kHz. Hence the very different performance.
An experimental tinySA using harmonic modes and SW mirror elimination was able to reach above 4GHz with reduced sensitivity but this is not ready for wide use.
More technical details in the wiki?

My guess would be limitations of the spectral purity of the local oscillator. (I haven't seen the hardware design.)

The two ranges suggest that it works similarly to the NanoVNA: a signal source is being used to generate frequencies up to 320 MHz, and the third harmonic of that source is used for the higher frequency range. Enabling an even higher range to 1.5 GHz would require using the fifth harmonic of the LO or switching to a different LO design.

As those of you have used the original NanoVNA (probably just about everybody here) know, the dynamic range is severely limited on the highest range, the one that extends coverage to 1.5 GHz. That's because you're going way beyond what the Si5351A is intended to do. It is still useful for many applications of a VNA, but a dynamic range of 40dB is too low for most of the things you use a spectrum analyzer for. It's not enough, for example, to use it to detect non-compliance with FCC spectral purity requirements for transmitters. TinySA will not be a lab grade instrument and as such is probably not adequate for full compliance testing; you'll still need verification by a better equipped lab for that. But it can serve as a way of finding non-compliant designs.

Hoping to shed some light on the tinySA possibilities I created a wiki measurement example on IQ balance tuning in a single side band transmitter.

Implemented, see wiki

Herb,

The commands you recognize are the same as the nanoVNA. The returned data per trace is only one number as the power measurement is scalar and not a vector
Next to the nanoVNA level commands there are a number of low level commands. These can be used to scan any amount of points in one scan.

If you enable the tinySA.exe output logging you will see the commands used.

On Mon, May 18, 2020 at 05:28 AM, John P wrote:

.. But wait, there's more! We are slowly but slowly implementing a complete serial command handler that when complete should allow you to do anything that you can do with the touch screen. We are also re-arranging the touch screen menus into a more logical hierarchy and will eventually provide the capability to set everything vis the web interface!

=======================================
? ? I'm uncertain how the help file John posted correlates to the console commands list that Erik provided by sending the "help" console command to the tinySA.

- Herb

On Mon, May 18, 2020 at 08:38 AM, <erik@...> wrote:

Can I propose some changes

Focus is not exactly the?same as "ZEROSPAN". I?do plan on putting that option back.

The "GRID" commands will be separate. The current structure makes the?two-word idea difficult!

There are two "REG" commands; "REGISTER" and "REGDUMP"; You only have to type "REGI" or "REGD" to distinguish them.

It's still a work in progress (as is even completed software)!


?
--
John P.
WA2FZW

John,

I guess you did see the tinySA wiki


W.r.t the console commands I agree single letter commands are not easy to understand.
Can I propose some changes?

Sweep Settings:

    FOCUS->ZEROSPAN  (zerospan is the regular technical term for this type of measurement)

Display Options:

    GRID REF->REF (one word)
    GRID SCALE->SCALE (one word)

Debugging and Troubleshooting Commands:

    REGISTER->REG (less letters to retype if you are doing register level debugging)
    REF_FREQ->CAL (is is actually more a power level calibration output)

On Sun, May 17, 2020 at 05:40 AM, Gyula Molnar wrote:

If I can see clearly, the one-letter commands can be identified from the help made by John WA2ZFW

But wait, there's more! We are slowly but slowly implementing a complete serial command handler that when complete should allow you to do anything that you can do with the touch screen. We are also re-arranging the touch screen menus into a more logical hierarchy and will eventually provide the capability to set everything vis the web interface!

Is clear, I was just too lazy to implement them yet,
Triggering in the frequency domain depends a lot on the scan speed and may not be useful for narrow RBW scan (scanning is slow)
The menu tree keeps getting bigger, wonder when I will run out of memory...

Greetings Erik,

? ? ? ? ? ?Looking good!!! This feature that would permit the screen capture of a sporadic burst IMHO could prove very useful. Terrific that you can do this for both time and frequency domain displays!

? ? ? ? ? ?IMHO if it is practical to implement multiple modes of triggering that would be desirable. Oscilloscopes typically offer Auto, Normal and Single trigger modes. Situations occur where one needs a Single?trigger that captures and holds the view. For recurring cyclic situations Normal? triggering where the capture is repeated each time the trigger point is reached is very useful. Auto?triggering simply provides a recurring sweep mode whether or not a trigger point is reached. Auto is useful for obtaining a trace whether or not there is a signal present which is the typical spectrum analysis mode which you have no doubt already implemented.?

Tom, VA7TA

Here they are:
version reset freq saveconfig clearconfig data frequencies scan sweep test touchcal touchtest pause resume trace marker capture vbat vbat_offset help info color if attenuate rbw mode spur selftest x y i v a b t e s m p w o d threads

The single letter commands will need a bit of explaining :-) t.b.d.

Erik,
? ?I combined this request with another topic so you may have missed it.??When you get the time could you post what the "help" console command returns?? I'd?like to know what commands are available for use with the tinySA.? Just a list is fine, no need to explain.? I'd like to eventually contribute to the group by producing a console command document like the one by Larry on the NanoVNA groups.io.

- Herb