On Tue, Aug 11, 2020 at 08:21 AM, hwalker wrote:

In a future release of tinySA.exe would you consider adding a dialog box under 'Settings' that allows the user to send console commands and display responses??

Good suggestion

Hello Erik,
do you plan to release also a linux version of the tinySA software? This would be a great idea for us linux users...
I am personally using debian buster 10.5 and do not have problems with running tinySA-Saver or nanoVNA-Saver but
the windows software seems to be equpped with more features.
I am still waiting for my tinySA and I am happy to get it in my hands. It cannot last a long time cause the parcel is already
in Luxembourg :)

best regards
Chris

Erik,
? In a future release of tinySA.exe would you consider adding a dialog box under 'Settings' that allows the user to send console commands and display responses??

? It would allow the user from within tinySA.exe to perform tasks like 'clearconfig 1234' and check settings such as 'leveloffset' without shutting down tinySA.exe and starting-up another application such as PuTTY.

? Just a suggestion.

?- Herb

开云体育

On Tue, Aug 11, 2020 at 05:36 AM, hwalker wrote:

Otherwise TinySA.exe is working well - thus far.

Yeah I know about the multiple port listing.?

I found there is some problem with aborting a scan. This often leads to all kind of problems.
Best way to abort a scan is to tap the screen of the tinySA.
The RBW setting on tinySA.exe is also not working.
More work to do

On Tue, Aug 11, 2020 at 04:01 AM, Erik Kaashoek wrote:

I uploaded an updated? tinySA.exe?

Changes:
- Bug solved: not able to restore saved configuration
- Bug solved: No com port listed but still connected to tinySA

The second bug may have caused various other unexplained behavior which, hopefully, should now be gone.

Erik,
? I updated to the new tinySA.exe (wish I could say version number instead of 'new').? The update went much smoother than previous versions (i.e. no configuration file err msg).?

? When it rains it pours - instead of no serial port listed, I have the tinySA serial port listed twice:

??

? Better than only having the mock-up item listed.? Otherwise TinySA.exe is working well - thus far.? Measured levels match the tinySA display without needing fudging.? Same with trace visibility.? Thanks for the new 'Storage' tab.

- Herb

I uploaded an updated? tinySA.exe?

Changes:
- Bug solved: not able to restore saved configuration
- Bug solved: No com port listed but still connected to tinySA

The second bug may have caused various other unexplained behavior which, hopefully, should now be gone.

David,

Your tinySA do not perform as should. Probably both the TX/RX switches have a short at one side of the switch causing wrong low level calibration and failure of selftest 10. Suggest you contact your seller to get this resolved.

Herb,
If I set leveloffset low to -10.0 and run (selftest 0 10) I get almost exactly what you got at 0.?


But a Config | Self Test gives:

When Level Cal is run, the number it comes up with is 8.2, which causes Test 3 and Test 4 to fail.

Can the level cal be calibrated normally?

On Mon, Aug 10, 2020 at 05:34 PM, hwalker wrote:

..I don't see any significant difference between your settings and mine. My scan time is faster but that's insignificant. I am kind of wondering where your battery icon went to, but that's unrelated...?
=====================================

The scan time difference and missing battery icon were due to the Spur:ON status panel readout.? It wasn't turned on during my single selftest 10. The measured level was still the same at -38.3dBm.

- Herb

On Mon, Aug 10, 2020 at 04:30 PM, David Lee wrote:

Further testing shows that self tests 1-9 will pass with leveloffset low values between 0.2 and 7.3
Test 10 still failing.

? David,
? You've made some progress.? A leveloffset low value of 0.2 would be as expected. I looked at selftest 10 on my tinySA with a leveloffset low value of 0.? You can run any of the selftests individually by 'selftest 0 x' where x is the desired selftest number. So for selftest 10, 'selftest 0 10'.? The following is what I see:

? leveloffset low = 0
??

I don't see any significant difference between your settings and mine. My scan time is faster but that's insignificant. I am kind of wondering where your battery icon went to, but that's unrelated.? Your test 10 signal level is 10dB higher than mine which explains the error message.

Erik is in a different time zone so it will be a few hours before he responds.??

- Herb

- Herb

Further testing shows that self tests 1-9 will pass with leveloffset low values between 0.2 and 7.3
Test 10 still failing.

Pictures:
Level 0.0


Level 8.2 (As set by Level Cal)


Level 6.0

Herb,

Set all values as per your post.?

Results:
If leveloffset low set to 0.0 , test 3 fails with "Signal level critical"
If leveloffset low set to 8.2 (value set by Level Cal), test 3 and test 4 fail with "Stopband Critical"

I tried experimenting with a few other values, if I set leveloffset low to 6.0 tests 1-9 pass

In all cases test 10 fails with "Signal level critical"

Dave

On Mon, Aug 10, 2020 at 01:46 PM, David Lee wrote:

I noticed that the wiki shows two different values for correction table slot 4. Under firmware update it shows a value of 50000000 0.0? Under USB command: correction it shows slot 4 as?30000000 0.0 (the setting I am using now)
If I reset the level cal, then do the selftest, only Test 10 fails with "signal level critical"

David,
? Erik used precision components in the production level tinySa and some of the Wiki content may not reflect current correction table values.

? Before you updated to the new firmware version you leveloffset values should have been close to the following:
? leveloffset low 0

? leveloffset high 100

? and your correction table values should have been as follows:

0 10000 6.0

1 100000 2.8

2 200000 1.6

3 500000 -0.4

4 50000000 0.0

5 140000000 -0.4

6 200000000 0.4

7 300000000 3.0

8 330000000 4.0

9 350000000 8.1

With those values performing a selftest should run without error unless your calibrator signal level is a lot off from -25dBm.

Try the following from a serial terminal:
1. enter <clearconfig 1234>
2. enter <reset>
3. re-establish your serial connection
4. enter <leveloffset low 0>
5. enter <saveconfig>
6. run a selftest? [Config->Self Test on the tinySA or <selftest 0> from the serial terminal]

The self test should run without error.? If you entered a leveloffset low value of 3 when it should have been 0, all your values will be 3dB too high which would explain why your selftest failed.? If the above doesn't solve your issue then hopefully Erik can offer another solution.

If the above works its not necessary to run a Config->Level Cal as it sets the leveloffset low value as you did manually.? Also, as a final check there should be no red values displayed in the side status panel.

- Herb?

I noticed that the wiki shows two different values for correction table slot 4. Under firmware update it shows a value of 50000000 0.0? Under USB command: correction it shows slot 4 as?30000000 0.0 (the setting I am using now)
If I reset the level cal, then do the selftest, only Test 10 fails with "signal level critical"

leveloffset low 7.7
leveloffset high 100.0