开云体育

Geoff,? I can see them both, the oscilloscope input loaded with 50 Ohm: - Cal output 10 MHz -35dBm , approx 10 mVpp. - Low output ON -18.5dBm approx. 65mVpp.

Toni, I suppose you are referring to the Cal Output, and that is probably too low for the oscilloscope.? I am referring to the Low Output which is -18dBm, and I was able to display that waveform on

-36 dBm = 3.5 mV

Here is an image of the unit after level calibration has completed: Here is an image of the unit after I "Touch screen to continue": And I'm still unable to get my oscilloscope to display a waveform,

The red numbers at left top and bottom indicate the device is not calibrate. Has the red text "path: HARM" disappeared? -- Designer of the tinySA For more info go to https://tinysa.org/wiki

Bill, Thanks for your input. I have upgraded the firmware and the red 110 message appears after I have done a reset, clear config and level cal. Geoff

The red 110 in the lower left corner indicates that you have not done CONFIG -> LEVEL CAL You need to (re)do this after doing a Clear Config and/or FW upgrade If the above does not make sense, then

Erik, Thanks for your suggestion. Unfortunately, after starting it with the jig wheel pressed to the left, there was no change. I forgot to mention that at the lower left corner a red "-110 dB"

The text "Path: HARM" is a remainder of an internal setting that should have been removed after the test/calibration. Switch of the the tinySA and on again and see if this is gone. If not, switch off,

I just received my TinySA Ultra. Earlier, I was able to get a clean sine wave on my Tektronix 2213A. I wanted to do a frequency correction as on the TinySA basic version. I connected "CAL" terminal to

Another issue with the app: when attempting to set the range to zero or scroll down to zero, the graph disappears. https://www.youtube.com/watch?v=wSA5phshMTA

Hi Erik The 189 alows running (sweep) again... The screen capture with refresh is a bit cranky... Thanks a lot for the fast reaction!!

hi Erik, It is working again, hartelijk dank 73, PA0MIK

New FW release Version V1.4189 For ZS405 (original tinySA Ultra) and ZS406 Changes: - Bug solved: TinySA-App can not control tinySA - Improved level correction table for ZS406 WARNING: This FW

Hi Not showing a scan on version 185.

Just tested it, tinySA4_v1.4-185-g1dd6b07 works too for me.

tinySA4_v1.4-177-g1687fbc.bin ( http://athome.kaashoek.com/tinySA4/DFU/old/tinySA4_v1.4-177-g1687fbc.bin ) works fine

/g/tinysa/topic/109991384 /g/tinysa/topic/new_fw_release_bug_fixes_and/109769305 Yes, this is an issue with the latest firmware version. Roll back to version 177; it

If you your <Start> frequency is set to 0MHz in tinySA-App, you will not see a display after clicking the scan buttons. Try setting your <Start> frequency to something like 0.1MHz and tinySA-App

Hi, Iwant to use a tinySA-ultra with the tinySA-App. By clicking on connect button tiny SA seems to be connected because single scan and multi scan buttons are highlighted. After clicking on one of