Hello Erik,
Thank you. I hope, this would come in the future, and I assume it's not so difficult, as only the LO has to be programmed with log. values. The tinySA combined with a LISN helps to do easy and cheap EMC precompliance measurements at 150 kHz ... 30 MHz. The level results are comparable with those from EMC labs, but the EMC receivers are sweeping logarithmic. So, comparison would be perfect with log. sweep.

BR,
Alois

No, but it may be in the future
--

Hi,
Is there a way to switch to a logarithmic sweep, like other spectrum analyzers do?

BR, Alois

I see 1.3320 on my main screen.
--
Dennis NS8H

Erik, updated the firmware, a minor note: The DFU file is named: tinySA_v1.3-321-g5fea965.dfu, but the displayed version on the tinySA is: tinySA_v1.3-320-g3b6d29f

New FW release
Version 1.3320

Changes:
- Added a '+' sign to the indicated output level in high output mode when the level is above 0dBm.

A small cosmetic change to warn users about the possibly high output levels when in high output mode.

OK, I glad to know it is still active.? I learn a lot from the discussions.? Thanks.

开云体育

I was wondering why there is no recent activity on the TinySA message board.

On Mon, Oct 25, 2021 at 03:10 AM, OneOfEleven wrote:

Interestingly, my laptop (Dell Latitude E6540) has 4 USB ports, all of them are USB 3, I've not yet had any problems at all with the TinySA or NanoVNA

USB3 on two of my PCs (w10pro) only fails to work in DFU mode - looks like it takes forever to upload the firmware (30 minutes+) and then just stops changing the progress bar?

What I found, it "speeds up" the progress bar if I keep moving mouse :)

Moved to USB2 port, all done in seconds

Some remarks,

• According to the photo the tinySA was not calibrated. This could only have an impact on the absolute level, not on the various measurements delivering the same result. (5.2dB).
• The test frequency of 120MHz is "dangerous" as the tinySA as an internal oscillator at 30MHz and 3rd harmonic of that oscillator could provide a false signal, according to the photo this is not the case. Suggest to measure anyway at least 10 times the selected RBW away from 120MHz.
• The level resolution of the tinySA is 0.5dB. If the difference between high current and low current noise factor is below 1dB (which it is) it may just fall within the 0.5 dB times 2 uncertainty region and thus not be visible
• According to the datasheet of the BFP420 the NF depends on the input impedance. I do not see an impedance matching circuit to optimally match the 50 ohm source impedance with the impedance required for minimum noise. This implies the NF is probably very different from the optimal spec
• Any broadband external noise? ingress around 120MHz ( such as from a switched mode power supply somewhere near the amplifier) will make the measurement impossible. I do not see any shielding and the decoupling of the supply lines is limited. Reaching a NF below 1.5dB will be challenging with such an unshielded setup
• Use a rather noisy amplifier to verify the measurement method as this noisy amplifier should deliver a different result from a good low noise amplifier.

--

Glad you found the desired driver. It's good to have a range of possible solutions being shown by others (as per this thread), increases the chance of finding one that solves the problem.

Interestingly, my laptop (Dell Latitude E6540) has 4 USB ports, all of them are USB 3, I've not yet had any problems at all with the TinySA or NanoVNA or LibreVNA or the NanoVNA-V2's (or any other USB device) directly on the ports (no USB hub etc), I use Windows 10 pro 64-bit. Can't think what the problem is that so many others have with using the units on USB 3 ports, I'm guessing it's a problem with PC's using different internal USB 3 chips and so different USB hardware drivers in there OS's, but who knows.

I followed the video of Erik Kaashoek to measure the noise figure of an amplifier I built. The outcome was 5.2dm/Hz. When I swapped the my amplifier with the LNa I was using, I got the same figure. I then change the bias of my amplifier to consume only 2mA, which as per Infineon should give the lowest noise figure, I got the same 5.2dbm/Hz again.
This repeated result may be due to to me doing wrong steps or missing something. So, I documented in the attached pdf file the test setup and the steps I followed.

Are these correct?

If only there was a way to slap a display and your amazing TinySA software on it!

I followed the steps explain in the link below to measure the noise level of an amplifier I built.


The outcome was 5.2dbm/Hz. When I switch the LNA and amplifier DUT to measure the noise level of the LNA, I got the same result (the LNA is a cheap one? with no noise figure specs!) Then I modified the biasing the DUT amplifier following the recommendation for lowest noise level from the manufacturer (current 2mA instead of 18mA), and redone the measurement, I got the same 5.2 dbm/Hz.
Having the same result every time made me suspicious about the steps I did being wrong or missing.

I documented the steps I followed in the attached PDF. Did I miss anything?

Thank you so very much all !!

Tried that one but "STM device in DFU Mode" did not appear

Anyway. I did find the solution bu searching for the driver in the PC:s Dirctory :
C: / Program Files (x86) > STMicroelectronics > Software > DfuSE v3.0.6 > Driver > Win 10

Now alls sorted out. B.r / tilman

True, but if the driver isn't installed first then every cable is bad. And the driver doesn't install by default with the commonly recommended DfuSe_Demo software. This is the most common firmware issue dating back to the early NanoVNA days. Therefore the first troubleshooting point is to check the driver. It is good practice to have more than one cable around anyway, and I have at least two originals and a couple eBay generics. All good. :)

73

-Jim
NU0C

On Sun, 24 Oct 2021 09:23:08 -0500
"Zack Widup" <w9sz.zack@...> wrote:

No, but if the problem IS with the cable, that won't solve it, either.

Zack

On Sun, Oct 24, 2021 at 8:30 AM Jim Shorney <jshorney@...> wrote:

The first check is to ensure the DFU mode driver is installed. This is a
very common problem as it does not install automatically and seems to be
poorly documented. Chances are if you haven't installed it manually then it
is not there. No amount of changing USB cables will solve this, only manual
installation of the driver. Once you are sure that Device Manger knows
about the DFU driver you can start checking USB cables.

73

-Jim
NU0C

On Sun, 24 Oct 2021 07:52:19 -0500
"Zack Widup" <w9sz.zack@...> wrote:

I keep saying you may have a bad USB to USB-C cable but everyone else

seems

to think it is something else. Both the cables that came with my TinySA

and

NanoVNA were bad and I had the same problem. I bought a better brand-name
cable and it's worked fine.

Zack

On Sun, Oct 24, 2021 at 2:08 AM Tilman D Thulesius <sm0jzt@...>

wrote:

I have followed the above. But I cannot see the "STM Device in DFU

Mode".

I only see STM32 Bootloader.

Please give me some advice on how to get that in

On Sun, Oct 24, 2021 at 03:35 AM, OneOfEleven wrote:

How to swap between the STM32 BootLoader driver and the STM32 DFU mode driver
====================================================================O

OneOfEleven's visual instruction should get you out of trouble, but here are some additional points that might affect you as well:

• In some cases you will need to reboot your windows after doing driver update
• Folder shown in his instructions might "look" differently - it's the one whit your DFUSe installation files, but do NOT go any deeper then the root of that folder structure as drivers are in different subfolders
• Make sure to check the box "Include subfolders" (as in his screen shot, but easy to miss :))
• DO NOT USE USB 3.0! Very often it does not work in DFU mode even when working fine as a COM port emulation! Or at least have USB 2.0 hub!

You can find the drivers in the bin / driver folder.
--
Gyula HA3HZ