- X.R. Junqué's website

2026-06-09 15:09:05 WinSpectrum III

Xavier

WinSpectrum III v3.0.3.113

Hello,

Following Jerry's and Marco's inquiries, there is a new version of WinSpectrum that I believe makes it easier to use, especially when changing the Start, Stop, Center, and Span frequencies.

2026-06-09 08:54:09 WinSpectrum III

Xavier

Lots of bugs?

Hi Jerry,

Thank you for your feedback.

Could you please have a look at the reply I recently sent to Marco? It may help, as the frequency fields are accepted only after pressing Enter or moving the focus to another control.

I have just tested the latest version with my own TinySA (classic version) and I can change Start/Stop frequencies without any problem.

If the issue still occurs, please delete the file log.txt, run WinSpectrum III again, reproduce the problem, and then send me the new log.txt file that is generated. This will help me determine exactly what is happening on your system.

Kind regards,

Xavier

2026-06-08 19:32:39 WinSpectrum III

Jerry

Lots of bugs?

Hi,

I just installed the latest version on my Win10 PC. Using the TinySA (not Ultra) and easily connects via COM9. Yet, I cannot do the most basic analysis. The default is to the FM broadcast band. When I try to change the settings for start and stop frequencies, it ignores them. If I try to change central frequency and span, it ignores them. I would simply like to zoom into one of the signals. I have tried everything. When I do it on the TinySA, itself, your software resets the start and stop to the default for FM broadcast band. Looks like the software is not ready for beta test.

Thank you,

Jerry VE6TL

2026-06-03 07:31:06 WinSpectrum III

Xavier

Frecuencies

Hi Marco,

You can freely enter any Start and Stop frequencies in the Settings window.

To change a frequency, click inside the corresponding field, type the desired value, and then either press Enter or move the focus to another control (for example by clicking on MHz, kHz, GHz, or another field).

For example:

Start frequency: 15 MHz

Stop frequency: 45 MHz

The frequency values are not limited to predefined selections; you can enter any valid value supported by the TinySA.

The frequency is accepted when you press Enter or leave the field.

2026-06-02 17:23:45 WinSpectrum III

Marco

Frequencys

Hi!

I managed to install and connect the WinSpectrum III with my Tiny SA Ultra. Stupid question: how can I set frequencys for the scan freely, since I am now only able to choose predetermined frequencys from the Settings window?

2026-06-01 08:05:05 Other

Xavier

VNA-SA viewer

Steve,

The facts seem to indicate that the TinySA firmware may not support the Capture command, which would explain why screen capture is not working in VNA-SA viewer.

2026-05-31 23:35:19 Other

Steve Macdonald

VNA-SA Viewer

First is a screenshot of the capture window on Winspectrum III

win1.jpg

Next, a screenshot of the 'help' command:

Win2.jpg

and last, the screen on the Samsung A8 when running VNA-SA Viewer

samsung.jpg

2026-05-31 12:38:49 WinSpectrum III

Xavier

VNA-SA viewer

Hi Steve,

Since WinVNA and WinSpectrum III can connect to the device, it appears that USB communication is working correctly and that the VID/PID values are not the issue.

What I would like to determine now is whether the device is responding correctly to the Capture command.

In WinSpectrum III, could you open the Command window and use "Send custom command" to send:

help

Please let me know the response you receive.

Also, when you open the Capture window, what exactly do you see?

A completely black screen?
A distorted image?
Random pixels/noise?
An empty window?

A screenshot would be very helpful.

2026-05-30 22:19:57 Other

Steve Macdonald

VNA-SA Viewer

Thank you for the advise.

I have installed WinVNA on my computer (Windows 11) It connects ok, but no capture rendering. Changing the screen resolutions still makes no difference. (I know that mine should be 320 x 240 for both the TinySA and VNA.)

I have installed the new VNA-SA Viewer v1.2. with the screen resolution settings.

I have tried all the suggested resolution settings, but still not rendering.

Still showing _Status: device not found or no response. It seems that the Samsung Tablet is still not seeing the TinySA and I don't why that is...

2026-05-27 22:57:36 Other

Xavier

VNA-SA viewer

Steve,

Knowing the screen width and height, in today’s new VNA-SA Viewer version 1.2 you can manually enter those values and press “Get screen”. The image should then render correctly.

2026-05-27 17:27:22 Other

Xavier

VNA-SA viewer

From what you've mentioned, the screen configuration is different.

I suggest downloading WinVNA from this website and opening the Capture window. In the File menu you will find the Screen option, where you can manually change the screen resolution.

Please try these values (width × height):

320 × 240

480 × 320

800 × 480

272 × 480

480 × 272

240 × 320

After changing the resolution, press Apply and check whether the image renders correctly.

2026-05-26 23:30:30 Other

Steve Macdonald

VNA-SA Viewer

I have installed WinSpectrum III on my computer and it is communicating fine with my TinySA and VNA. It is showing a trace on the computer screen.

If I try to Capture I just get a blank black screen on both devices with the message:

Message: n/a could not retrieve the image

2026-05-25 15:21:59 Other

Xavier

VNA-SA viewer

Could you try installing WinSpectrum III on your computer and check whether it communicates correctly with both the TinySA and the NanoVNA?

You can also try the Capture menu in WinSpectrum III. If communication is working properly, you should at least be able to see the device screen captured in the application.

2026-05-24 00:24:25 Other

Steve Macdonald

VNA-SA Viewer

Thanks for your response.

I have plugged the TinySA and OTG lead into my computer.

I have checked the VID and PID with Device Manager and Ports on my computer and it is showing the correct values VID 0483 and PID 5740.

2026-05-23 08:16:12 Other

Xavier

VNA-SA viewer

Steve,

Your device may use VID/PID values other than VID=0x0483 and PID=0x5740. You should find out what the Vendor ID (VID) and Product ID (PID) values are and enter them into the VNA-SA viewer. You can find these values, for example, using USB Device Info on Google Play.

2026-05-22 22:16:10 Other

Steve Macdonald

VNA-SA Viewer

I'm not sure what the models are and firmware versions, my TinySA has a sticker on the back showing HW version: V0.3. The VNA has no sticker with any information, but it is the basic model. The VNA-SA app I downloaded is the one currently on your website. (I think V-1)

I have tried it with another Samsung A8 and after doing the settings in Developers to ensure the OTG is activated I get the same results as mine.

The app doesn't seem to have any permissions to set.

I can't understand why the app does not recognise the SA or VNA I have looked through settings and everything seems to be set ok.

Any help appreciated.

2026-05-21 12:07:39 WinSpectrum III

Xavier

VNA-SA viewer

Steve,

I would try this first:

completely close Serial USB Terminal,
reboot the tablet,
then connect the device and go directly into VNA-SA Viewer only.

2026-05-21 11:33:13 WinSpectrum III

Xavier

VNA-SA viewer

Steve,

The Samsung A8 and OTG should not be the problem. I use VNA-SA Viewer successfully on the same tablet with NanoVNA-H, H4, tinySA Ultra and Ultra+.

If Serial USB Terminal works with your TinySA, the USB link itself is OK. But if neither your VNA nor your TinySA works in VNA-SA Viewer, I would suspect something specific to VNA-SA Viewer: permissions, Android USB association, app version, or compatibility with your device/firmware.

What exact VNA/tinySA models, firmware versions, and VNA-SA Viewer version are you using?

2026-05-20 23:46:46 Other

Steve Macdonald

VNA-SA Viewer

I have installed VNA-SA Viewer in my Samsung A8 Tablet and set up all the OTG settings along with an OTG lead. (including the Developers Settings) I can't get it to work with the VNA and TinySA.

I get a screen with a black rectangle with _Status: device not found or no response

I am also using Serial USB Terminal with my TinySA, this works perfectly with my Samsung A8 Tablet.

2026-02-25 08:59:57 WinSpectrum III

Xavier

Spectrum capture

Apologies for the delayed response. Yes, WinSpectrum III can automatically save spectrum samples over a set period. Please refer to Sections 2.19 and 2.20 of the PDF manual, where this is explained in detail.

Let me know if you have any further questions — I’ll be happy to help.

2026-02-21 00:57:46 WinSpectrum III

Patrick

Spectrum capture

Does Winspectrum III have the ability to automatically store spectrum samples continuously over a set period say 1 hour for later analysis? All advice appreciated

2026-01-17 17:47:36 WinSpectrum III

Xavier

No spectrum trace

Hi Maurice,

Just to clarify, WinSpectrum III does not display any message called “No spectrum trace”.

If no trace is visible, there are two common reasons:

• A sweep has not been started yet. After connecting the device, please click Scan or Continuous and wait until the first sweep completes.

• In older versions, the View → Spectrum option was not enabled by default. Please check that View → Spectrum is selected so the trace can be displayed.

The USB driver message you posted indicates that the driver is working correctly (status 0 = OK) and is not related to the display of the spectrum.

Please let me know which version you are using.

2026-01-17 17:43:19 WinSpectrum III

Xavier

No spectrum trace

Hi Maurice,

Just to clarify: WinSpectrum III does not generate any message called “No spectrum trace”.

If no trace is displayed, it usually means that a sweep has not been started yet. After connecting the device, please click Scan or Continuous and wait until the first sweep completes so the spectrum can be displayed.

The USB driver message you posted indicates that the driver was installed correctly (status 0 = OK), so it is not related to the missing trace.

Let me know if the trace appears after starting a scan.

2026-01-14 06:10:13 WinSpectrum III

Maurice

No spectrum trace

Xavier,

This is the message I get when I view "events" for the STM usb driver.

I have no idea what this means!

Driver Management has concluded the process to add Service usbser for Device Instance ID USB\VID_0483&PID_5740\400 with the following status: 0.

Any help appreciated

Gracias Maurice

2025-10-29 15:55:45 WinSpectrum III

Xavier

waterfall

Hi Wojtek,

Thanks a lot for the report.

I’ve identified the issue affecting the waterfall in v3.0.3.27 and published a fix.

Please update to WinSpectrum III v3.0.3.30 and the waterfall should display correctly.

Best regards,

Xavier

2025-10-28 19:58:12 WinSpectrum III

Wojtek

Problem with waterfall

Hi

I have TinySa Ultra+ ZS-407. I connect to PC, turn on WinSpectrum III ver. 3.0.3.27. Spectrum works, but waterfall isn't displayed :(. Could You tell me what I should to do :). Thanks for help :). Have a nice day :)

2025-10-26 23:17:23 WinSpectrum III

Xavier

Problem with waterfall

Hi Wojtek,

Thanks a lot for the report, and sorry for the delay.

I’ve identified the issue affecting the waterfall in v3.0.3.27 and published a fix.

Please update to WinSpectrum III v3.0.3.28 and the waterfall should display correctly.

Best regards,

Xavier

2025-10-25 19:36:21 WinSpectrum III

Wojtek

Problem with waterfall

Hi

I have TinySa Ultra+ ZS-407. I connect to PC, turn on WinSpectrum III ver. 3.0.3.27. Spectrum works, but waterfall isn't displayed :(. Could You tell me what I should to do :). Thanks for help :). Have a nice day :)

2025-09-25 20:54:14 WinSpectrum III

Xavier

Wine/Linux

Thanks, Jean-Roger.

By “automatic” I meant the app automatically switches to “File → Manual COM Select” when it detects Wine, so you can pick the COM port yourself.

On native Windows the app scans COM ports automatically; on Wine I prefer the explicit selection (Wine must map /dev/tty* to COMx).

73

Xavier

2025-09-25 18:49:58 WinSpectrum III

Jean-Roger F6EGK

Wine/Linux

Xavier,

I have understood why the WinSpectrumIII_Wine version crashes in Wine-9.0. I have simply forget to install the dotnet48 package ... After doing the dotnet48 installation, WinSpectrumIII_Wine flawlessly. However there is no still automatic COM port detection, if I have correctly understood the difference with WinSpectrumIII-32bits.

73 - Jean-Roger

2025-09-25 18:15:19 WinSpectrum III

Jean-Roger F6EGK

Wine/Linux

Xavier,

I have understood why the WinSpectrumIII_Wine version crashes in Wine-9.0. I have simply forget to install the dotnet48 package ... After doing the dotnet48 installation, WinSpectrumIII_Wine flawlessly. However there is no still automatic COM port detection, if I have correctly understood the difference with WinSpectrumIII-32bits.

73 - Jean-Roger

2025-09-25 17:52:21 WinSpectrum III

Jean-Roger - F6EGK

Wine/Linux

Hello Xavier,

Thanks for acheiving these new versions. Below are my first tests results :

Distro : Mint Xia 22.1 (XFCE desktop) base: Ubuntu 24.04 noble
Wine versions tested : wine-9.0, wine-10-0, all with a 32 bits winprefix

WinSpectrumIII_Wine

Behavior with wine-9.0

- The software starts and is quickly followed by warning messages "Unhandled exception has occured in your application ..." and crashes.

Behavior with wine-10.0

- The software starts normally, and I am able to select the COM port (/dev/ttyACM0) through CONNECT button. However the first connection try fails, but the second connection try always succeeds. Trace settings, single or continuous scan, color / fonts settings, screen captures work flawlessly. I am not sure to understand the advantage of this version, as automatic COM port detection does not work.

WinSpectrumIII-32bits

Behavior with wine-9.0

- The software starts normally, and I am able to select the COM port (/dev/ttyACM0) through CONNECT button. First connection try always succeeds. Trace settings, single or continuous scan, color / fonts settings, screen captures work flawlessly.

Behavior with wine-10.0

- Same as above.

For a common measurement configuration, I have also seen that the elementary cycle time value can change, example :

- WinSpectrumIII-32bits in a Windows 10 environment : 560 ms (stable value)

- WinSpectrumIII-32bits in a wine-9.0 or wine-10.0 environment : 470 ms or 680 ms. Value changes according to software launching trial. This is also the samething for WinSpectrumIII_Wine version.

As a provisional conclusion, the new WinSpectrumIII-32bits version seems to do the job flawlessly, at least with the two wine versions. I can't explain why the WinSpectrumIII_Wine does not work correctly with wine-9.0. I can send you the complete error messages, but they are hard to decode ... I have no 64 bits wineprefix (generally less stable), as all my Windows stuff are 32 bits versions.

Congratulations and thanks for introducing the possibility to use your software for Linux users.

73 - Jean-Roger

2025-09-23 16:43:23 WinSpectrum III

Xavier

Wine/Linux

Hi Jean-Roger,

Just a quick update: manual COM-port selection is already available in File → Manual COM port Select, and under Wine it’s enabled automatically.

On my Wine/Linux tests it works with:

- Single scan and continuous modes

- Color changes

- Capture

If you can try this build and share your results, that would be great:

https://xrjunque.nom.es/swdownload#winspectrum

73,

Xavier

2025-09-11 15:10:57 WinSpectrum III

Jean-Roger - F6EGK

Wine/Linux

Xavier,

I don't know if it could be enough, but yes, choosing the COM port could be a major step in order to see what happens.

If you plan this for the next version, I will check the behavior, and I will come back for giving the results.

Thanks.

Jean-Roger

2025-09-10 22:30:46 WinSpectrum III

Xavier

Wine/Linux

Jean-Roger,

If what is required is to be able to choose the COM port to connect to, I'll take note for the next version, is that correct?

2025-09-10 17:16:59 WinSpectrum III

Jean-Roger - F6EGK

WinSpectrum III and Wine / Linux environment

Thank you Xavier for your quick answer.

I am not sure that my first message has been correctly, sent because it is not displayed. I just repeate below, but you have already answered, even if you have juste received the title.

I try to use WinSpectrumIII (32 bits version) in a Wine / Linux environment. Unfortunately it fails to open (detect ?) the active COM port. Here I have translated ttyACM0 (Ultra SA) as COM4 port. It perfectly works with TinySA-App from Erik, as I can manually set the port COM number, and successfully get a connection. Is there any chance to use WinSpectrumIII in a Wine / Linux environment, or is there something that I can try to tweak ?

Of course, it perfectly works on the same computer in a real Windows environment.

Thank you for your all developments towards the community.

Jean-Roger

2025-09-10 10:00:09 WinSpectrum III

Xavier

Wine/Linux

Hi Jean-Roger,

For now, WinSpectrum III is Windows-only. We’ll revisit Wine/Linux support once the app is running at full speed and fully stable on Windows. USB/serial handling under Wine needs extra work, so we prefer to enable it later rather than offer a half-working setup.

If you do experiment with Wine on your side, feel free to share your results on the forum—we’ll take them into account when planning official support.

2025-09-10 08:23:44 WinSpectrum III

Jean-Roger F6EGK

Possible use in a Wine / Linux environment ?

2025-08-10 07:41:59 WinSpectrum III

Xavier

Uploading a CSV file

Hi Lo:

For sure. You may open the .CSV file, for example with Notepad, copy all the content to the clipboard, and paste it at this free and easy site: https://hastebin.com/

You'll be given a link. Please send me this link via https://xrjunque.nom.es/Contact

2025-08-09 19:47:28 WinSpectrum III

Lo

csv-Datei hochladen

Hallo Xavier,

danke für deine schnelle Antwort. Kann ich dir eine CSV-Datei schicken, die ich nicht in WinSpektrum III laden kann?

Gruß Lo

2025-08-09 11:40:32 WinSpectrum III

Xavier

Marker Settings

Hi Evan,

Thank you for your feedback. I am currently working on a major update of WinSpectrum and will take your comments into account.

2025-08-09 11:35:48 WinSpectrum III

Xavier

Uploading a CSV file

Hi Lo,

Thank you for your message. I will try to find out the CSV format used by the tinySA and enable opening it with the application.

2025-08-09 04:09:21 WinSpectrum III

Lo

csv-Datei hochladen

Da die Verbindung zum tinySA nicht funktioniert, wollte ich direkt von der SD-Karte eine csv-Datei einlesen.

Der Import einer csv-Datei direkt von der SD-Karte funktioniert nicht, es wir nichts angezeigt.

2025-08-07 10:55:57 WinSpectrum III

Evan

Marker Settings

I am having difficulty using the marker functions in the WinSpectrum III app.

The frequency accuracy continues to be reset to 14.00 when I am trying to set it to 14.002

Also, the Delta function displays 4delta1 instead of 2delta1 when trying to measure a two-tone test based on 700 and 1900 audio being mixed up to 14.0007 and 14.0019 (common two-tone test frequencies for SSB tests).

I also lose sync with the TinySA Ultra.

Version gives:

tinySA4_v1.4-201-gdb83a99

HW Version:V0.4.5.1

What am I doing wrong.

2025-07-10 21:50:23 WinSpectrum III

Xavier

Terry,

First — and just to double-check — please make sure the firmware file you're using is really for the tinySA Ultra. It's easy to accidentally grab the one for the standard tinySA, which won’t work and could cause exactly the kind of silent failure you're seeing.

For the tinySA Ultra (and Ultra+), the last release looks like this:

tinySA4_v1.4-200-g26fc821.dfu

You can download it from the official page here:

http://athome.kaashoek.com/tinySA4/DFU/

2025-07-09 23:46:28 WinSpectrum III

Terry Fugate

Firmware upgrade failure

First my Tiny SA Ultra was purchased from an authorized US vendor so I suspect it is legitimate.

Second....

I've tried to upgrade the firmware on 5 different PCs. I decided to abandon my attempts with Window 7 and use Windows 10 and 11. My wife has a Dell Win 10, HP 11 [that she hates with a passion] and 3 friends Dell, no name special, and a Leveno Win 10. The special driver installs and shows up in Device Manager, but the process doesn't complete.

Don't worry about this, I will try again this weekend with the local shortwave club datageekette. Sheila is very tech savvy.

I've started an EMI group....maybe proof I'm short a few brain cells. I worry it will turn into a snake pit of petty human behavior.

2025-07-05 18:00:43 WinSpectrum III

Xavier

DFU driver

Yes, there should be an entry in Device Manager under:

Ports (COM & LPT) → STMicroelectronics Virtual COM Port

or

Universal Serial Bus devices → STM Device in DFU Mode (when the device is in DFU mode)

If nothing shows up after running the installer, it's possible that:

The device was not properly connected,

It was not in DFU mode at the time, or

The installation did not actually install the driver (this can happen silently, especially on older systems or without admin rights).

Forum – Support, bugs & Feedback

2026-06-09

2026-06-08

2026-06-03

2026-06-02

2026-06-01

2026-05-31

2026-05-30

2026-05-27

2026-05-26

2026-05-25

2026-05-24

2026-05-23

2026-05-22

2026-05-21

2026-05-20

2026-02-25

2026-02-21

2026-01-17

2026-01-14

2025-10-29

2025-10-28

2025-10-26

2025-10-25

2025-09-25

2025-09-23

2025-09-11

2025-09-10

2025-08-10

2025-08-09

2025-08-07

2025-07-10

2025-07-09

2025-07-05

2025-07-03

2025-06-25

Post a new message