开云体育

Hi Erik, The high input calibration is done with a nanovna as hf generator at 250 MHz (CW)
the output signal measured with the calibrated low input of the tinySA, that worked well and
the self test too.
Then put the vna signal on the high input. (Uncalibrated I had about 2 dBm margin of error)
After calibrating via the config menu (actual input level),the value turned out to be incorrect.
Every thing was done as your instruction video shows
At the end i loaded the previous fw version (1.3-265) and both inputs could be calibrated well.

Wim

Wim,
How did you perform the high input, or did you calibrate the hi output?
--

Hi Erik, installed the latest firmware update yesterday. when re calibrating the "hi-input" it turned out that this did not yield the desired result instead of e.g. -34.2 dBm I came to about -10 dBm actual power. The June fw version gave no problems and worked correctly, even after restoring the previous fw version everything worked well again.
It's not a big problem because uncalibrated gives the high input a fairly correct value. Despite that, I think it's worth noting.
73, the Wim PA0WFG

I've had a long think about the data and I am convinced the sidelobes are a function of the time domain measurement window. A Wiener inverse is not needed to fix that.

Mathematically, for N Hz RBW you need 1/N seconds of data. A boxcar window of that length produces sinc sidelobes in the frequency domain. Instead of a boxcar of length n, use a triangular weighted window of length 2*n. That will be sinc**2 in the frequency domain which has very low sidelobes. If you scale the data properly you can do the weight multiplication by bit shift so the filter is a shift-add operation. You can, of course, use any weighting function for the time gate and get the Fourier transform of that as the spectral spreading function of the acquisition system. For a Gaussian response, apply Gaussian weights from a table. It can also be done in a completely analog manner with an FET and a function generator.

That part I'm sure of. The matter of smaller RBW using the existing HW is rather harder. I'll address that later after I've done some more analysis.

Have Fun!
Reg

Mike,
You probably need a LNA if you are comparing relatively weak TV signals. It would be a good idea to use a 75 ohm input LNA, then the mismatch at the output to the 50 ohm tinysa would be negligible. You also need to use the pilot signal (if you can isolate it) to compare as the rest of the signal bandwidth varies with time.
www.arrl.org/files/file/Technology/TV_Channels/8_Bit_VSB.pdf
Gary
W9TD

Hi all,
?I have ordered, but not received my TinySA yet. (R&L)
? I want to compare two TV antennas. Is the TinySA sensitive enough to show the signals that a TV will receive.
The frequency range I'm interested in is 200MHz to 610MHz, Can I scan that whole band or do I need to do it in chunks?
I understand over 350MHz specs degrade, but if I'm comparing two antennasI expect they will both be degraded the same.
I'm guessing I will just have to live with the 75Ω to 50Ω mismatch. I don't think that is much.
Any hints?

Its an illegal clone infringing on our trademark

?
--

Is this official or modified clone?
https://pt.aliexpress.com/item/1005003112093679.html

Thanks to all for the help. I got most of what I was looking for (happy now). It's doing what I want, just need to spend a bit more time firming up the details. Then saving it in default startup.
Don

On Sat, Aug 14, 2021 at 05:49 PM, hwalker wrote:

Using the new experimental beta FW, as suggested by Erik, appears to be a better solution but cannot be made "sticky" as can using the "color" console command along with "saveconfig".?

You can use
PRESET/STORE/STORE 1?
or even
PRESET/STORE/STORE AS STARTUP
to save this configuration for quick recall
--

Herb,
Ah! now the light begins to shine. Okay thanks all, I will get at this latter today and see what I can accomplish.??

On Sat, Aug 14, 2021 at 02:48 PM, Don Lewis wrote:

Erik, You got me? I don't see anywhere in the menu tree where I have access to "TRACE", is it in a hidden menu? Is this in a older firmware version? I'm totally loss here. If you have the time and patience, please step me through the steps necessary to get to the Trace enable selection. I have FW 1.3-265-ga0c410f, is the process available in that version? Thanks

Don,
? There is a "release" directory and a "beta" directory that Erik uses.? The new experimental beta release 1.3-315 at?http://athome.kaashoek.com/tinySA/DFU/beta/ adds the trace menu (see the first figure below).

? The trace colors can be changed, as suggested by DiSlord, using the "color" console command with either the current release FW or the 1.3-315 beta FW.? I found changing the active trace color from yellow to red also results in the marker annotation color also changing to red and is visually unappealing.

? Using the new experimental beta FW, as suggested by Erik, appears to be a better solution but cannot be made "sticky" as can using the "color" console command along with "saveconfig".? Eriks procedure is as in the figures below (Note: the active trace could be set to green instead of red by enabling trace 2 (grn) instead of trace 3).


New TRACE menu in beta 1.3-315? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Trace 1 (ylw) set to enabled & MAX_DELAY? ? ? ? ? ? ? ? ? TRACE 3 (red) set to enabled?
? ??? ?? ???

Herb

Erik, You got me? I don't see anywhere in the menu tree where I have access to "TRACE", is it in a hidden menu? Is this in a older firmware version? I'm totally loss here. If you have the time and patience, please step me through the steps necessary to get to the Trace enable selection. I have FW 1.3-265-ga0c410f, is the process available in that version? Thanks

tinySA support color console command (i port it fom NanoVNA code):
color index hex_color

For get color in hex you can use any soft like


Example for change trace 1 color to hex = #de0707:
'color 6 0xde0707'

read current colors:
'color'
Color indexes:

First select trace 3
TRACE/TRACE/TRACE 3
now enable trace 3
TRACE/ENABLE
trace 3 is now enabled, just like trace 1.

now set trace 1 in max decay mode
select trace 1
TRACE/TRACE/TRACE 1
and enable max decay
TRACE/CALC/MAX DECAY


--

Thanks Eric, It seems that I already had the latest FW beta Version, and I want those colors reversed! So does that mean that in one of the older FW versions this would be true?
Or maybe I don't understand how to Enable the different color choices.

In beta FW you can enable the red trace as the active trace and the yellow trace also active but with delayed decay.
Give it a try.?

Is there anyway to change the colors of the traces?. I want to have the active t(fast) race, while using the delayed decay to be Yellow (not Red), In other words, the reverse as it is now. Thanks Don

Thanks Igor!

That looks to have resolved the issue. All self tests now pass.

This is the result of the tests requested by Erik: