开云体育

You can check your attenuator using the tinySA.
Connect CAL and RF using a short SMA cable
Then set MODE/CALIBRATION OUTPUT/30MHz
Write down the measured level of the 30MHz signal
Insert your 40dB attenuator between CAL and RF
Write down the measured level of the reduced 30MHz cal output and calculate the real attenuation.

--

No ... would it matter?

tinySA Ultra, setup:

- tinySA4_v1.3-513-g92dd4b2
- HW Version:V0.4.5.1
- tinySA-App 1.1.20.1 by OneOfEleven and Erik

In 'continuous scan' (118 to 136 Mhz) the tinySA Ultra is freezing after around 5 minutes,
and the last serial message (in text mode, captured with 'Serial Port Monitor' software) is:

‘.虫补.虫1.虫±.虫..虫?.虫?.虫础.虫±.虫?.虫?.虫‘.虫础.虫础.虫补.虫?.虫?.虫?.虫?.虫?.虫1.虫1.虫..虫蚕.虫?.虫.
x..x?.}ch> vbat
vbat

Last message is 'vbat', sent by the tinySA Ultra. The battery info is missing, device is frozen, has to be switched off/on again..
Remark - apparently binary values are garbled into text by the serial port monitor software, somthing like 'x‘.xA.xA.xa.x?' etc.,

So, it looks like, this is a HW related problem.

In single scan mode of the tinySA-App, there is once a refresh for the screen on the PC only,
but on the com port, every 5 seconds the following message is exchanged. Why those idle messages ?
Looks, like, any command after 'ch>' is initiated by the software (?)

ch> vbat
vbat
4163 mV
ch> marker
marker
1 64 120559020 -8.01e+01
ch> sweep
sweep
118000000 136000000 450

This goes on for ever, no frozen tinySA Ultra com port in this mode.

73's de OE1MWW
Wolfgang

Are you using a USB 3 port?
--

Is the battery fully loaded?
--

On Sat, Dec 10, 2022 at 05:58 AM, Peter Bremer wrote:

So I think it updated, but just reporting with the wrong version number. Correct?

Correct
?
--

The latest upgrade of today v1.3-513-g92dd4b2 for the tinySA, after upgrading still reports as v1.3-512-gd99d679 (which was dated around 4th of december) but indicates a build Time: Dec 10 2022 -10:03:55
So I think it updated, but just reporting with the wrong version number. Correct?

Erik,

I upgraded the firmware on my old TinySA this morning and the firmware file that I downloaded to my PC was 1.3513. After the upgrade, my TinySA showed 1.3512 as running on the SA but the new features seem to have been implemented.
--

Posted a while ago about my tSA ultra, with a non-working touch screen. A friend brought to my attention that its version page says that the hardware version is unknown, while other units state their versions .. could it be a fake unit?

Erik,

I just ran it at 290 points per scan and probably got a couple of more minutes before it disconnected (about 12 minutes vs. 10 minutes).
--

Hi,

-I'm testing with a Yaesu FT3D Handheld Radio and a Baofeng UV-B5.? Both give me similar readings.
-Testing on 146.52 MHz
-Low input
-I did Config - Level Cal with both inputs connected as instructed on the First Use Wiki page.

I don't know of any way to measure if my attenuator is truly 40 dB.? I thought maybe if the advertized 40dB is not accurate then what I enter into the Ext Gain would make my reading off.

Thanks,
Brian

Erik,

I know that 500 points per scan results in the problem and I think that 1000 points per scan also results in the problem. I have not tried other values.
--

Thanks Erik. I'll do that. Purchased at Zeenko.

3dB difference is 50% difference in power so the power reading makes sense versus the dBm reading
What is a HT?
What frequency?
What tinySA input are you using?
Did you do a level calibration for that input?
--

I can replicate the problem.
Does the "Points per scan" setting have an impact on how soon it hangs?
--

Herb,

I let the TinySA Ultra run this morning and it disconnected after about 10 minutes of apparent normal operation. I am still running firmware 1.3-512-gd99d679 built on December 3. I updated to this version upon receipt of the TinySA Ultra yesterday. I have not updated to the version released today since Erik did not mention any fix for my problem. The log provided the following information after the disconnect:

42.222 rx: ch>
42.238 tx: sweep start 143174000
42.300 rx: sweep start 143174000
42.300 rx: ch>
42.316 tx: sweep stop 145174000
42.363 rx: sweep stop 145174000
42.379 rx: ch>
42.379 tx: scanraw 143174000 145174000 500
42.441 rx: scanraw 143174000 145174000 500
42.738 rx: 1502 bytes received
42.738 rx: ch>
42.754 tx: sweep start 143174000
42.813 rx: sweep start 143174000
42.813 rx: ch>
42.829 tx: sweep stop 145174000
42.860 rx: sweep stop 145174000
42.860 rx: ch>
42.876 tx: scanraw 143174000 145174000 500
42.907 rx: scanraw 143174000 145174000 500
43.299 rx: 1502 bytes received
43.299 rx: ch>
43.315 tx: sweep start 143174000
43.362 rx: sweep start 143174000
43.377 rx: ch>
43.393 tx: sweep stop 145174000
53.608 rx link timeout .. disconnecting

I doubt if this information will assist Erik in his troubleshooting, but per your suggestion, I am sharing this anyway.

Hello,

How accurate is the tinySA measuring/calculating power readings?? I have an HT that is set to High and reads 5 watts on a Power meter.? When I hook it up to the tinySA using a 10W 40dB attenuator, I receive a reading of 33dBm.? When I change the units to Watts I get somewhere hovering at 2.19W.? I have the Level - Ext Gain set to -40 to take into account the attenuator.? My question is, and please correct any assumptions or math I'm doing, but shouldn't the 5W output from the HT be giving me somewhere around 10 log (5000) = 36.99 dBm and measuring near the 5 Watts?

Thanks,

Brian

On Fri, Dec 9, 2022 at 11:32 PM, Peter Klein - KD7MW wrote:

For example, is going out in the backyard as far as possible ?from the radio and antenna sufficient?

You will not be able to measure harmonics that way.? Coupling between the transmitter antenna and the tinySA and its antenna vary wildly with frequency and as the distance between them varies.? You need an attenuator between the transmitter and the tinySA.? Or, since you already have a dummy load, you could build a tap, as described in these articles:









http://www.ad5x.com/images/Articles/Tap50dbRevA.pdf

I prefer coaxial attenuators, as I feel they maintain a good 50 ohm match and accurate attenuation over a wider frequency range, but if you've already got the dummy load, one of these taps is probably the quickest/cheapest way to get the measurements you want.

Contact your seller
--