开云体育

Hi Erik Back in business with the TinySA.exe, thank you. I had initially no COM port at all. By a closer inspection it was assigned to COM7 which also was used for 4 virtual cables on that specific

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

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

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

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

I have conducted multiple tests before shipment to ensure that the shipment passes the test, but I am not sure that there is still a problem after you receive it. I will further test. Sorry, you can

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

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

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

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

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

leveloffset low 7.7 leveloffset high 100.0

What is the value of low and high leveloffset?

Picture:

SMA appears to be okay, Level calibrate completes OK.