开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育
  1. Tinysa
  2. Messages
Expanded Topics Messages Polls
Date
Re: Self Test Errors

 

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
Re: Self Test Errors

 

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
Re: Self Test Errors

 

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

 

Pictures:
Level 0.0


Level 8.2 (As set by Level Cal)


Level 6.0
Re: Self Test Errors

 

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
Re: Self Test Errors

 

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?
Re: Self Test Errors

 

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"
Re: Self Test Errors

 

leveloffset low 7.7
leveloffset high 100.0
Re: Self Test Errors

 

What is the value of low and high leveloffset?
Re: Self Test Errors

 

Picture:
Re: Self Test Errors

 

SMA appears to be okay, Level calibrate completes OK.
Re: Self Test Errors

 

Please post pictures of the failing tests (screen captures or use camera or phone) so I can diagnose the problem
Make sure the coax SMA connectors are well fastened, use only your fingers for tightening.
Self Test Errors

 

New Tiny SA received yesterday. Unit came with v1.0-39. Updated using .dfu file to v1.0-49. Reset and cleared the configuration data, restored settings per wiki instructions.

Self test reports?
Test? 4: Stopband critical
Test 10: Signal level critical

Source and resolution of these errors?

Dave
Re: PC SW for tinySA

 

On Mon, Aug 10, 2020 at 06:27 AM, hwalker wrote:
? I can see why Evan was confused.
Yes. I need to spend some time on tinySA.exe
Re: PC SW for tinySA

 

On Mon, Aug 10, 2020 at 02:21 AM, Evan Hand wrote:
Erik,
I now cannot get the TinySA to show up on any of the 4 Windows10 computers that I have tried.? ?As I stated in my first email, it did respond for a short time after I rebooted my computer.? Now it will not respond at all.

Erik,
? I updated to the latest TinySA.exe and noticed the following issues that would be confusing to new users. My system is a DELL laptop running WIN10 x64:

? 1. Every time I start the program I get the following error message. The?C:\Users\admin\AppData\Roaming\Kaashoek\SpectrumAnalyzer\?__SAlast.cfg has a date showing it was updated by the program so what is the source of the error message?

? ? ??

?2. When I click <OK> above, I get a TinySA application screen with randomly generated data.? The menu bar doesn't appear until I make a mouse move.? Selecting the File->Connect menu item gives me the following screen.? Like the issue Evan reported, only a Mockup selection is presented in the drop-down box.? Since I don't want to do a Mockup run I back out of the menu by selecting <Cancel>

? ?

?3. If I select the <Single> or <Run> button the application executes as expected even though the SerialPortSelector menu does not show the tinySA connected.? The Capture tab also works as expected.

? ??? ? ?

? I can see why Evan was confused.

?- Herb
Re: PC SW for tinySA

 

I did not.? Luckily I have one from my NanoVNA.? That cable works.

Thank you for your help.
73
Evan
AC9TU
Re: PC SW for tinySA

 

开云体育

Hi Evan

Did you also test using another USB cable ?
Kind regards

Kurt

?

?

Fra: [email protected] <[email protected]> P? vegne af Evan Hand
Sendt: 10. august 2020 13:20
Til: [email protected]
Emne: Re: [tinysa] PC SW for tinySA

?

I did check on the Device Manager for the port.? I did not see the TinySA or a port that could be the TinySA (an unknown port).? I did this for 5 different computers.

Evan

Re: PC SW for tinySA

 

I assume you did try a different USB cable and the tinySA was switched on when testing the connection?
Is the red led next to the USB connector blinking and the battery charging?
Re: PC SW for tinySA

 

I did check on the Device Manager for the port.? I did not see the TinySA or a port that could be the TinySA (an unknown port).? I did this for 5 different computers.

Evan
Re: PC SW for tinySA

 

On Mon, Aug 10, 2020 at 02:21 AM, Evan Hand wrote:
I now cannot get the TinySA to show up on any of the 4 Windows10 computers that I have tried.
I added some connection debug info to the wiki

Scroll down till the part related to the windows device manager and follow the instructions.
I
18981 - 19000 of 19566