With the current firmware 1.3-347-g31eb02e (obtained from http://athome.kaashoek.com/tinySA/DFU/), I notice a typo in the "sweep accuracy" menu:

It says "PEEDUP" instead of "SPEEDUP". Furthermore the display of the actual value seems broken. It's always shown as "0s", regardless of what I enter.

PS: I also wonder what the undocumented(?) "NOISE SOURCE" option does. I could not even find it in the source code in this repo.

In "HIGH" mode, for the start, stop, and center frequency, the keypad input shows "0..720 MHz", whereas it should be "240..960 MHz":

I guess the reason is this line...

Hi, not sure if it's been mentioned at all but there is a marker bug on the original TinySA using the latest firmware.

2 traces enabled, the usual trace-1 yellow and an added trace-2 green set the calc maxd.
2 markers enabled on trace-2 set to 'tracking'

As the peaks on trace-2 slowly fall back down, it leaves remnants of the markers on those peaks in the display squares. I'm guessing that you're not redrawing where the markers were (individual display cell), so they are being left hanging there.

See attached video

The ultra looks good by the way ! can't afford one but larger screen/GHZ span looks very nice.

Boa tarde, me chamo Alex comprei um tinySA no caso quero gerer CSN para WWb6 da Shure, porem ele não esta abrindo no wwB6 shure por conta do padrao Exemplo 560.000,-61.00 precisava sair assim meu email [email protected]

I've got a TinySA Ultra here, believed genuine and marked HW V0.4.5.1 which was working fine until this afternoon, when (I think) I noticed that STORE AS STARTUP was checked and unchecked it.

The result of that was a register dump overlaying the graticule, cycling power gets to that point repeatedly even if the battery has been disconnected.

I've upgraded via DFU to tinySA4_v1.4-99-g8bfcfd7.bin, noting that DFU told me "DFU state(10) = dfuERROR, status(10) = Device's firmware is corrupt. It cannot return to run-time (non-DFU) operations". It ran for a while, but then (I think) I did something else with either STORE AS STARTUP or LOAD STARTUP and once more got to the "register dump over graticule" state.

I'm now in a position where any startup- even immediately after an apparently-successful reload over DFU, immediately takes me to "register dump over graticule" state with no menu accessibility etc. Hence, "half-bricked" :-)

How do I recover from this, and what can I do to help pin down the problem so that it doesn't affect other users?

Hi,
just wondering if you could use glscopeclient for the TinySA. I stumbeled over the SW when looking for a opensource oscilloscope.
The SW seems to be useable for different HW.

https://github.com/glscopeclient/scopehal-apps

Developer: @azonenberg

He also has some youtube videos demonstrating the SW here

And in discord I spotted him in the Thunderscope (open source oscilloscope) discord server

git describe --tags
v1.4-46-g94410c0

Building the latest commit for tinySA4 with

TARGET=F303 make clean
TARGET=F303 make

fails with this message

Compiling main.c
In file included from main.c:1111:
sa_core.c:157:19: error: conflicting types for 'path_text'
 const char *const path_text[]=PATH_TEXT;
                   ^~~~~~~~~
In file included from main.c:22:
nanovna.h:1745:20: note: previous declaration of 'path_text' was here
 extern const char *path_text[];
                    ^~~~~~~~~
make: *** [ChibiOS/os/common/startup/ARMCMx/compilers/GCC/rules.mk:216: build/obj/main.o] Fehler 1

tinySA builds w/o issue, not yet tested.

1. When using MEASURE/SNR, does the TinySA adjust the displayed averaged noise up by 2.5 dB to correct for averaging of logarithmic values?
2. When using MEASURE/SNR, does the TinySA adjust for actually measuring (S+N)/N?

Kindly reply directly to [email protected]
Thank you
S Dutka, PE

After building from source and updating firmware released Sept. 28, the white waterfall that came from the vendor was not fixed. Also, firmware reflects v1.1-17 whereas firmware located at "http://athome.kaashoek.com/tinySA/DFU/" reflects v1.1-21.

This photo reflects the firmware version after update:

And this photo reflects the same white waterfall that I got from the vendor but after the update:

Not sure why the v1.1-17 did not fix the white waterfall but I'll try updating firmware to v1.1-21 and see if that fixes it. Not sure if I'll need to completely wipe the old firmware or what???

The screen capture shows artefacts at the bottom of the image in the far right column. This is independent of the respective device and the recording program used; NanoVNA also shows the same artefacts. NanoVNA version 1.2.15, the issue existed also with versions 1.0.64 and 1.1.x, also latest tinySA version.

see also DiSlord/NanoVNA-D#41

Another user's tinySA also shows this, so it is obviously a systematic problem.
https://groups.io/g/tinysa/message/7071

When the Tiny SA is switched off it loses all the changes that have been made to the configuration, for example to MODE, LEVEL, FREQUENCY, etc. Would it be possible to retain the configuration in order to save time when the unit is switched on again?

I recently upgraded firmware on my TinySA (not a clone, bought from the Zeenko store on AliExpress) to v1.3-317-g9d882970.dfu. I then noticed that the battery voltage would never read above 3.7 volts and was showing in yellow, and the battery ICON displaying 1/2 to 1/4 full. I opened the case, and measured the actual battery voltage, and it was at 4.1 volts. I then re-loaded firmware v1.3-265-ga0c410f.dfu into the TinySA, and the battery voltage is now showing green and at 4.23v with the USB cable plugged in. Previously I had let it charge up for several hours, and the RED led would go out. But the battery voltage was only showing never more than 3.7v. There may be a problem with the latest firmware issue in the analog battery voltage reading area.

The self test #12: states attenuator fail.
How can this be corrected?

I compute the Noise Figure of the TinySA on HIGH in as follows:

• No Input

• Frequency = 488, 506, 542 & 569 MHz

• Span = 6 MHz

• TRACE/CALC/AVER16

• MARKER/SEARCH MARKER/FREQUENCY

• Displayed Average Noise Floor (DANF) = -117.2 dBm/42kHz

• Ambient Temperature = 296K
  ================================
  10log(kTBNf) = DANF + 2.51 dB
  10log(kT) = -173.89 dBm/Hz, 10*log(B) = 46.23 dBHz, 2.51 dB corrects for averaging of logarithmic values

• Solving for Nf,
  Nf = -117.2 + 2.51 - (-173.89) - 46.23 = 12.97 dB

  Do you agree?
  Does the 2.51 dB apply?

trying o install new firmware. dfuse demo cant see the device. device is present as STM32 BOOTLOADER

Hello dear.

1st of all, I would like to give developer my hot thanks for this great device which has really great testing abilities in compare to it's small size ! Really it is a complement for victor network analyzer SV4401A making very strong testing & lab tool !

However, we have difficulty to set it as fast real time with good visualization for useful signals waterfall for ICOM 7100 transceiver.

We modify ICOM 7100 by adding an output port for it's IF from official points for that in it's board. It work 100% with SDR receiver. However, I preferred to use TinySA Ultra for this purpose because I have no SDR receiver. SDR receiver is owned by my friend .....

We have difficulty to set TinySA Ultra as waterfall for ICOM 7100. The chief difficulties are:

1. it is slow. When we increase RBW it will become fast but the visualization of useful signal (it's carve will be smaller)
2. we need to set a marker (single marker) to point constantly to frequency that radio at at. We failed for that.

We tried center/span mode, then set span at 400 KHz. We make "Marker1" only active marker & set it's type as "Normal" then set "central" for this marker. But we did not get a marker point to frequency that the radio dealer set on to ...

I'm already opened a thread on www.qrz.com forum - see following link:
https://forums.qrz.com/index.php?threads/how-to-set-tinysa-to-make-real-time-spectroscpe-for-icom-7100.869913/
but we did not, yet, reach to solution .....

My call sign is: YI1YJK

Any help is appreciated.

Regards.

EXPERT CONFIG ->INTERNALS (internals access code) : 1234

Clear unlock code : 1234
Ultra unlock code : 1234 X

Ultra unlock code : 4321 O

Hi,

I have aTinySA since one week now (I received it 2021 july 6) and since that it was working very well.

I bought it on amazon :
(https://www.amazon.ca/Analyseur-Minuscule-analyseur-fr%C3%A9quence-g%C3%A9n%C3%A9rateur/dp/B08HT3V28L/ref=sr_1_1_sspa?__mk_fr_CA=%C3%85M%C3%85%C5%BD%C3%95%C3%91&crid=3Q046KQMTMULC&dchild=1&keywords=tinysa+spectrum+analyzer&qid=1626365795&sprefix=tinysa%2Caps%2C167&sr=8-1-spons&psc=1&spLa=ZW5jcnlwdGVkUXVhbGlmaWVyPUEzNlRERUtRT0M0SUI5JmVuY3J5cHRlZElkPUEwNjI3ODA4UVBCSEIwQU00WEJQJmVuY3J5cHRlZEFkSWQ9QTA2MzIwNTQyQUs0NTlSQkVYNUxLJndpZGdldE5hbWU9c3BfYXRmJmFjdGlvbj1jbGlja1JlZGlyZWN0JmRvTm90TG9nQ2xpY2s9dHJ1ZQ==)

See the photo for the HW version and serial number : http://home.ca.inter.net/~carlgaron/dscf5156p.jpg

Today when selecting an item on the menu of the tinysa (frequency menu) the whole screen become white. When I touch the white screen nothing happen. See this video :

https://youtu.be/6OPSOH3j-rU

Now I can’t use the tinySA anymore! I found for a reset button but there is no reset button. Is there a way to make it work or should I return it to amazon?

I made the update of the firmware by following the instruction on your website (VDD and BOOT0 connected together). The upgrade was successfull. I switch the tinySA off and on : same problem, the whole screen is white.

Here is a a copy-paste of the information of the firmware I loaded :

tinySA v0.3
2019-2020 Copyright @erik Kaashoek
2016-2020 Copyright @edy555
SW licensed under GPL. See: https://github.com/erikkaashoek/tinySA
Version: tinySA_v1.3-265-ga0c410f
Build Time: Jun 5 2021 - 12:23:59
Kernel: 4.0.0
Compiler: GCC 7.2.1 20170904 (release) [ARM/embedded-7-branch revision 255204]
Architecture: ARMv6-M Core Variant: Cortex-M0
Port Info: Preemption through NMI
Platform: STM32F072xB Entry Level Medium Density devices
ESD protected

I try the tinySA with tinySA-App on my computer, as you can see the tinySA is working but I have the white screen. So I can't use it whithout a computer which is not very useful. http://home.ca.inter.net/~carlgaron/tinysa_logmag_s11_2021-07-16_12-21-16.png

Maybe a hardware screen problem???

Hello, hello, is there anybody in there? I want to know if anyone has read this message. If I have to return the product to amazon I must do so next week. If I don't have an answer from you soon, I will assume that no one is reading my message and that there is no solution to my problem! Thank you!

I returned the unit to Amazon for a refund. Thank you anyway for the support!!! ;-)

Hi Erik,
When I measure the NF of a wideband RF amplifier by the ULTRA , strictly according the procedure mentioned in the WIKI,
I get negetive NF's as a result.
First I measured the amplification per frequency by uing the LiteVNA.
Please what could be wrong ?
Jos

I've written my own DAQ software for a particular RF project. I am using the scanraw command through USB.

So: scanraw 1M 4M 1000

All the serial data ends up in RxBuf.

I get back 'x' then hi and lo byte. In Matlab I scale this by:

        hi = uint8(RxBuf(ix(k)+1));        % hi bit left shift  ( get decimal 5)
        lo = uint8(RxBuf(ix(k)+2));         %                        ( get decimal 125)
        build(t,bidx) = double(hi)*256 + double(lo);       (shift hi byte left 8 bits and add lo) = 1405

The documentation says the hi/low bytes are scaled by 32, but I get number that seem random and are not even in the ballpark of the -90dBm of most of the readings.

If I scale by 16 and make it negative, it's in the right ballpark: -1405/16 = -87.8125 dBm

So, how are they scaled?

Do I convert to a signed 16 bit int first?

Thanks, I'll post my code when I have it all working.

make stops with this error:

Compiling ui.c
ui.c:3898:21: error: 'FMT_TBL_FILE' undeclared here (not in a function); did you mean 'MT_TITLE'?
   { MT_CALLBACK,    FMT_TBL_FILE,  "TABLE"S_RARROW"\nSD",     menu_sdcard_cb},
                     ^~~~~~~~~~~~
                     MT_TITLE
ui.c:3898:63: error: 'menu_sdcard_cb' undeclared here (not in a function); did you mean 'menu_scale_cb'?
   { MT_CALLBACK,    FMT_TBL_FILE,  "TABLE"S_RARROW"\nSD",     menu_sdcard_cb},
                                                               ^~~~~~~~~~~~~~
                                                               menu_scale_cb
ui.c:3898:3: warning: missing initializer for field 'reference' of 'menuitem_t' {aka 'const struct <anonymous>'} [-Wmissing-field-initializers]
   { MT_CALLBACK,    FMT_TBL_FILE,  "TABLE"S_RARROW"\nSD",     menu_sdcard_cb},
   ^
In file included from ui.c:24:
nanovna.h:1448:15: note: 'reference' declared here
   const void *reference;
               ^~~~~~~~~

caused by this function:

static const menuitem_t menu_limit_select[] = {
  { MT_ADV_CALLBACK | MT_REPEATS,   DATA_STARTS_REPEATS(0,LIMITS_MAX), MT_CUSTOM_LABEL, menu_limit_select_acb },
  { MT_CA   LLBACK,    FMT_TBL_FILE,  "TABLE"S_RARROW"\nSD",     menu_sdcard_cb},
#ifdef __SD_FILE_BROWSER__
  { MT_CALLBACK, FMT_TBL_FILE, "SD"S_RARROW"\nTABLE",            menu_sdcard_browse_cb },
#endif
  { MT_NONE, 0, NULL, menu_back} // next-> menu_back
};

Displaying the firmware version running on the TinySA in the PC screen would be very useful.

A check on the PC application (upon startup) could even indicate if there is a version conflict between the PC software and the TinySA firmware itself. I got burned on the version incompatibility issue with the second last version of TinySA firmware and the latest PC program.

I've been using v1.3-429 to capture random ~8ms RF bursts of data on the 315MHz ISM band and I noticed that I'm no longer able to capture these data bursts with v1.3-5x. What has changed to prevent me from capturing short bursts of data with v1.3-5x ? I've tried versions: v1.3-504, v1.3-506 and v1.3-513 without success.

Thank you in advance for your support,

Regards,
Rej. VE3MPV

Hello!  I bought the original tinysa Ultra.  There is an inconvenience in the work of recording the trace on the sd card. It is possible to upgrade the recording function using the icon on the display (for screenshots) to start recording and stop to stop.  Or set the continuous recording time on the sd card.

Hi

I'm trying to flash the newest firmware. Is there any special dfu-util version, required? 0.9 shows success, but when I then check the version in the menue it still shows 0.3:

Attempted both, the dfu file and the bin file:

dfu-util -d "0483:df11" -a 0 -D tinySA_v1.1-74-gd87d2a2.dfu -S FFFFFFFEFFFF

dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

Opening DFU capable USB device...
ID 0483:df11
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuERROR, status = 10
dfuERROR, clearing status
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 2048
DfuSe interface name: "Internal Flash "
file contains 1 DFU images
parsing DFU image 1
image for alternate setting 0, (1 elements, total size = 108576)
parsing element 1, address = 0x08000000, size = 108568
Download [=========================] 100% 108568 bytes
Download done.
done parsing DfuSe file

dfu-util -d "0483:df11" -a 0 -s 0x08000000:leave -D tinySA_v1.1-74-gd87d2a2.bin -S FFFFFFFEFFFF

dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device...
ID 0483:df11
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 2048
DfuSe interface name: "Internal Flash "
Downloading to address = 0x08000000, size = 108564
Download [=========================] 100% 108564 bytes
Download done.
File downloaded successfully
Transitioning to dfuMANIFEST state

I would like to use the Ultra as a signal generator to see the filter curve of a 10,7 MHz filter at an oscilloscope. By setting the sweep time to 50 msec it seems that the sweep time isn´t 50 msec but approx 500 msec. Using the TinySA all works fine

Following setup:

Ultra RF output to the 10,7 MHz filter input
Ultra Cal output to oscilloscope ext. trigger input
Filter output to oscillosocpe y-input

Ultra setting:
frequency 10,7MHz
sweep span 1 MHz
sweep time 50 msec
sweep points 201

Regression with d758676

https://groups.io/g/tinysa/message/10620

TinySA Ultra.pdf

I'm not sure if you have seen this, but at AM mod freq < RBW the noise floor looks wrong.
at 1kHz RBW
1 kHz AM looks good
take a look at these frequencies:
699 Hz
399 Hz
199 Hz

Newly received failed test 3 and then lock up, problems keep multiplying and now now config possible

Hello Erik,
when I build from your cloned repo I still get Versions like tinySA_v1.2-nnn-gxxx... because tag v1.2 is newer than v1.3, as seen on the GitHub tags page (see below).
According to your download page 2af1845 is v1.3-3, so v1.3 should be 12a96bb from Mon Mar 29 08:58:52 2021 +0200 but it is 232494b from 26 Feb 2021 while v1.2 is two days later from 28 Feb 2021.

tinySA_v1.3-3-g2af1845.bin and tinySA4_v1.3-3-g2af1845.bin

git log shows this:

commit 2af18458bc248b9c1ef683caf79cd0cba8c89465
Author: erikkaashoek <[email protected]>
Date:   Tue Mar 30 15:02:08 2021 +0200

    More spur improvements

commit a42a1f50216a3df31a3e102204686f6f8f07916d
Author: erikkaashoek <[email protected]>
Date:   Tue Mar 30 13:49:58 2021 +0200

    Added NEAR SPUR

commit 02f06319d8b93cda32f52a6afac9420fccf5f8d1
Author: erikkaashoek <[email protected]>
Date:   Mon Mar 29 17:45:46 2021 +0200

    Correction updates

commit 12a96bba04f2bae690076569a21f214e4a4ace88
Author: erikkaashoek <[email protected]>
Date:   Mon Mar 29 08:58:52 2021 +0200

    Repaired test status and marker colors

GitHub tags page:

Why can't the inbuilt signal generator be used to calibrate the HIGH input in the same way as it can for the LOW input?

I have attached a screen shot showing the issue.

Is the firmware for the SA4/Ultra posted anywhere? I just received one in the mail running 1.3-506 and I'd like to see if there are any updates.

in "MODE" setup, tapping outside options (see yellow circle) I got a crash dump
100% repro
SW: tinySA_v1.0-62

at slow sweep speeds the marker ops are not latched and the user button click is ignored
I was looking at 10 MHz signal at 20 kHz span. did peak detect then marker->ref level
nothing happens even if I hold the button

So just got this analyzer in the mail and the place where the c cable goes looks like it’s missing or so high in the box like it’s been pushed in or pulled up when made. Is there anything we can do to exchange this iteam

I am not sure this is an issue and I can not find an answer on the net - on my new TinySA Ultra (4.5.1 tinySA4_v1.3-506-g8291e1e) after self-test and calibration I observe a spike (a thin yellow strip) along amplitude axis for frequency very close to 0. The strip is present no matter what frequency range is selected. I have not tried less than 100KHz. If TinySA blocks DC, what could be the cause of the spectra close to 0? A number of available pictures of the device show similar behavior.

Hello, is it necessary to calibrate every firmware update?

Hello Erik,

I have learned that V4.3 is the active branch.
(Does this also apply to the small F072 variant? The last version tinySA_v1.3-429-gc224fa9.bin on your server is still from the DiSlordChanges branch).

The build process under Linux (debian stable) fails because of the upper/lower case of the file names, which does not matter under Windows:

git status
On branch V4.3
Your branch is up to date with 'origin/V4.3'.

make
...
Compiling main.c
In file included from sa_core.c:18,
                 from main.c:1092:
si4432.h:185:10: fatal error: si446x_defs.h: No such file or directory
 #include "si446x_defs.h"
          ^~~~~~~~~~~~~~~
compilation terminated.

because the file si446x_defs.h does not exist, but there's Si446x_defs.h.

Same for si446x.h (Si446x.h exists)

In file included from sa_core.c:18,
                 from main.c:1092:
si4432.h:186:10: fatal error: si446x.h: No such file or directory
 #include "si446x.h"
          ^~~~~~~~~~
compilation terminated.

and SI446x_cmd.h (si446x_cmd.h exists)

Compiling si4468.c
si4468.c:902:10: fatal error: SI446x_cmd.h: No such file or directory
 #include "SI446x_cmd.h"
          ^~~~~~~~~~~~~~
compilation terminated.

Suggestion: use lower case names only (as for the other HW related files, e.g.: ili9341.c and tlv320aic3204.c)

mv Si446x_defs.h si446x_defs.h
mv Si446x.h si446x.h

and adjust the names in these files:

grep -n '\#include \"S[iI]44' *.c *.h
si4468.c:902:#include "SI446x_cmd.h"
si446x.h:14://#include "Si446x_config.h"
Si446x.h:14://#include "Si446x_config.h"

https://www.amazon.com/gp/product/B08FB5XT7B/ref=ox_sc_act_title_1?smid=A2QLMFTY03XGKY&psc=1

Have you started including a unique serial number in the printed label for each device rather than adding it afterwards to a standard label? If not then are these two units fakes?

Sending pause via USB serial disables the battery and voltage display in the lower left screen, see screen capture:

Capturing without pause shows the battery and voltage:

Pausing via menu DISPLAY/PAUSE SWEEP and doing a screen capture also shows the battery and voltage:

The captured images reflect exactly what I see on the tinySA screen - menu pause shows batt, serial pause doesn't.

This is a minor issue, it exists since some time, my oldest capture without battery dates from 13-Nov-2022 (v1.3-493):

70MHz center 50MHz span, Lo enabled. external mixer. filter measured with VNA:

filter measured with SA:

filter measured with TinySA Ultra:

Power TinySA on and press round knob, main menu comes up and I select config, then get no info screen, press round knob or tap screen and get REFER DELTA NOISE TRACKING, etc info screen. I can select delete or back and get no info screen. Keep hanging in that loop.

Hello,

Can you please confirm if the tinySA can:

1- Measure the antennas SWR for f < 5.4GHz?
2- Measure the gain of a LNA for f < 5.4GHz ?

Thank you

Hello, the device works well(At the moment almost all my work has been focused in the 0.1-800MHz range), but I have found a small defect. When I save a trace in dbuv and reload it on the screen, it appears as a measure in dbm. For example, I save a trace of 60dbuv and when I load it I get a trace of 160dbuv.

It might also be good to perform the power measurements in dbvu.

I answered myself. The solution is as simple as saving the trace in dbm and then importing it in both dbm and dbuv

Best regards

2a7785b (1.4052) is the last version where the touch opens the menu. Later commits do not respond to a touch on the normal screen, but a touch on the CONFIG/VERSION screen ends the mode and returns to normal screen.

Nevertheless the tinySA3 build is broken since 442a835 (see also PR #59), my simple fix is:

--- a/nanovna.h
+++ b/nanovna.h
@@ -18,7 +18,7 @@
  */
 #include "ch.h"
 
-//#ifdef TINYSA_F303
+#ifdef TINYSA_F303
 #ifdef TINYSA_F072
 #error "Remove comment for #ifdef TINYSA_F303"
 #endif
@@ -26,7 +26,7 @@
 #define TINYSA4
 #endif
 #define TINYSA4_PROTO
-//#endif
+#endif
 
 #ifdef TINYSA_F072
 #ifdef TINYSA_F303

Maybe it's something I did, but the following 3 mode options have disappeared from my tinysa ultra version 1.4-49-g4f5396a.
The mode options that have disappeared are: switch to high in, switch to low out, switch to high out. Is it something I did while getting familiar with this nifty little gem or is it a bug. Can I fix it with a new download?

Lo input doesnt work at all. Selftest stopped at test3. Level cal. says Signal level to low. I´we changed cables, it doesn´t work.
It started with suggestions to change cable between Lo and HI inputs but test doesn´t pass successfully. tinySA bought from ELESHOP.EU