|
New video: Observing Modulation
https://www.youtube.com/watch?v=FjOar_MQjUQ&t
|
|
I was going to try and observe modulation but when the span is 10 kHz and the RBW 3 kHz, the bins are very obvious. I was at 100 kHz span but the carrier looked flat-topped so I examined closer and found out why. This is not how a real spectrum analyzer works, but I suppose there is nothing that can be done about it. Gary W9TD
|
|
Tiny SA installation
8
Sorry to show my ignorance (or just poor memory). I've just got my SA and updated the firmware and now want to install SA-Saver on my PC. I've already got nanoVNA running on the PC but I've forgotten how I installed nanoVNA Saver in those distant days before Covid. I've downloaded the SA Saver source code files to my PC (Win10) but can't work out how to get an installation; thought I was supposed to be looking for a exe file according to Eric's Github site? Maybe I missed the exe file somewhere? I don't understand the instructions there but then I'm not really a software geek! Some plain English explanation would be helpful please? regards Nigel G8AYM
|
|
New video: First Use
4
https://www.youtube.com/watch?v=NFqxdGcWSdw A short video demonstrating the selftest and the power calibration, using both the internal level calibration generator and an external calibration signal
|
|
New video: SIgnal Identification
4
https://www.youtube.com/watch?v=H5Q9m5877Vk A short video demonstration how to use various functions of the tinySA to identify if a signal you see is actually present at the input or internally generated.
|
|
New FW release Version V1.0-76 Changes: - Removed the 1kHz frequency grid as it did not add value - Corrected a bug causing spur avoidance to fail when the manually selecter RBW was smaller than the automatic selected RBW - Implemented an AGC override in high mode to avoid overload of the IF - Added a user selectable mirror masking option in high mode These are some complex changes so I'd like to hear if this all went well. The spur avoidance table is filled till 100MHz. Not sure if there are any relevant spurs at higher frequencies. Ingress from strong transmitters and the remaining MCU clock harmonics are not impacted by spur removal as these are actual signal. If you still see real spurs let me know the start/stop frequency and the active RBW and preferably send also a screen capture The tinySA high mode had big problems showing a strong signal in a small span. In this case a 300MHz signal at -50dBm To the right of the actual signal at 300MHz you see some disturbance and at 301.8MHz there is a mirror of the 300MHz signal First step implemented is an override of the automatic AGC, this cleaned up much of the disturbances between the actual signal and the mirror The steps you see are due to the limited granularity of the AGC override and are unavoidable. But these also help to recognise some intervention is happening. The second step has been to add a MIRROR MASKING in the high mode FREQ menu. When enabled this forcefully removes all signals that could have been caused by mirrors The signal at 301.8MHz is replaced by a constant level plateau so you can see when this is done. The MIRROR MASKING may fail in certain situations. Let me know if it is usable If the signal is very strong all will fail but you should get an overload warning. Feedback is welcome.
|
|
New FW release: High mode attenuation included in auto AGC and Mirror masking
New FW released Version V1.0-77 Changes: - Show "Mask: ON" in status panel when mirror masking is active - Take high mode input attenuation into account when overriding AGC or doing mirror masking
|
|
TinySA LOW Input Level Accuracy Test Results - Looking Good!
2
Greetings All, I decided to compare the TinySA level tracking accuracy to my HP8656B high quality signal generator. I first completed the internal calibration of the tinySA in accordance with the tinySA First Use Youtube video. The HP8656B design permits the stepping of the frequency and output level in user defined increments which I set to 10 MHz and 10 dB respectively. For this test I stepped the frequency from 10 to 150 MHz in 10 MHz increments and from 200 to 340 MHz in larger increments. For each frequency step I recorded the measured level for each of the 0 to -70 dBm output level steps. In all 152 measurements were recorded. All the comparisons matched within 0.8dB or closer, the vast majority were 0.5dB or closer and roughly 40 of the measurements matched exactly. See the attached pdf file for the specific measurement data. As I did not have a type N to SMA coaxial test lead I had to use some adapters to connect the generator to the tinySA. This may have resulted in some minor impedance discontinuities in the test lead. Thus the results might have been even better without the adapters. Tom VA7TA
|
|
Calibration Question
4
In the 'first use' video it shows the high and low levels being red before calibration and white when successfully calibrated. When in high input mode the high and low levels are shown levels are still red after calibration but they go back to white when I go back to low input mode. I assume this is normal? Or do I need to calibrate in both high and low modes? Many thanks.
|
|
New video: Level calibration of high input
7
https://www.youtube.com/watch?v=ToJUc-Va1PM A short video describing how to do the level calibration of the high input using the calibrated low input
|
|
Updating Newly Received tinySA
Hi Group, Got my tinySA today and immediately set about upgrading the FW. I got through the DFU file backup and upgrade process okay (but the boot screen still indicates V0.3 for some reason) but when I attempt the BIN upgrade (maybe this is my problem, is it either DFU or BIN, not both?), I get" "Invalid DFU suffix signature A valid DFU suffix will be required in a future dfu-util release!!! Cannot open DFU device 0483:df11 No DFU capable USB device available" This after I edited the .bat to point to the current FW version BIN file name. I am worried I am asking a dumb question and this all should not be so hard! Any advice? Thanks and 73, Robert, WA2T
|
|
Nevermind!
2
For part of my problem anyway. I see the FW version is in fact changing, it is further down in the Version screen. So, I have upgraded successfully after all. But, I still might like to know why the computer I am using does not seem to recognize the tinySA as a USB com device when trying to do the BIN upgrade. Maybe hold down the jog wheel when powering up (a total guess)? Lastly, upon further study of the upgrade page, I now believe it is indeed either DFU or BIN, not both. 73, Robert, WA2T
|
|
|
|
New FW release: Fixed crash and other improvements
3
New FW released Version V1.0-80 Changes: - Fixed a crash when touching in empty space below an active menu - Improved auto level handling, tell me if you notice any unwanted difference - STORE STARTUP is now used at startup. This could cause problems with starting the tinySA. Let me know it you experience startup problems.
|
|
back to the end of the line
7
I ordered tinySA from Aliexpress in July. They said it should arrive in October. I went to their web site to see if there were any updates. They said "Bill who?". There is no record or my order there. Nothing is awaiting shipment. I checked my payment records and apparently they didn't take the money out of my credit card. My order just vanished into the cyber abyss. So I found another company selling these (for a higher price). Now the delivery date is pushed back to November! Maybe some day I will actually have one. -shrug- I am pretty sure the firmware for mine has not yet been written now. 73, Bill KU8H -- bark less - wag more
|
|
Frequency entry bug
5
Hi Erik There has been a bug in your firmware from the very beginning which can be a problem. After setting up some presets and recalling them, I then try and set a new start frequency but it doesn't allow me too, it always sets it to 350MHz (when on high input mode), even worse if I then try and change the stop frequency. The only way to overcome it and set a desired scan range is to power cycle the unit, select either low or high mode and then enter a new scan range - without recalling any presets before hand. If you can't reproduce the problem I'll post a short video of what I do when it gets into this state to show what happens if you want.
|
|
Hi Eric, Let?s start with the big thank you: I received the NanoVNA only 3 days ago and there were already 4 Firmware upgrades. Even though it?s already a really mighty little tool, that cannot be beat for the price, you still keep making it better and better. Thank you for your effort and the work you?re putting in, to make the pro tools accessible to the HAM?s around the world. I bought the Tiny SA for Harmonics measurement of my uSDX Multiband Sandwich, and I see a minor bug, when doing this: It?s showing the wrong delta frequencies: Base frequency here is 14.060 MHz (CW): It?s shwoing +3,81MHz for first harmonic (labelled 2TD) and + 4,291GHz for the second harmonic (labelled 3TD) etc. I?m sure that the "Giga-Hertz" part ain?t right. And I assume it should show a delta of the amount around base freqency for first harmonic, labelled 2TD. Or do I get something wrong in the interpretation of the results ? Best 73 Manuel; DL2MAN
|
|
New FW released Version V1.0-81 Changes: - Corrected a number of marker frequency bugs. I must have been interrupted during the updating of the marker frequency mechanism and forgotten to finish it. A number of marker frequency bugs have been solved. Let me know if there still are remaining
|
|
New FW release: Restore to different mode repaired
2
New FW release Version V1.0-82 Changes: - Restoring a preset that uses a different mode is working again. Be aware that part of a preset is the stored trace. So if you want to keep a measurement for a long time (e.g. survive a power cycle or an empty battery) do a STORE TRACE and after that STORE into a preset. Once you do a LOAD the stored trace will appear again.
|
|
New video: Frequency Menu
A short video demonstrating the Frequency menu of the tinySA
|
Image Name
Sat 8:39am
Sat 8:39am