Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
Is my Nanovna broken?
|
I cannot get this to work on startup using nanosaver and I get in the logfile ...
2019-10-03 07:33:37,745 - NanoVNASaver - INFO - Startup... 2019-10-03 07:33:37,829 - NanoVNASaver.SweepWorker - INFO - Initializing SweepWorker 2019-10-03 07:33:37,869 - NanoVNASaver.NanoVNASaver - INFO - Found NanoVNA (0483 5740) on port /dev/ttyACM0 2019-10-03 07:33:37,869 - NanoVNASaver.NanoVNASaver - DEBUG - Building user interface 2019-10-03 07:33:37,973 - NanoVNASaver.NanoVNASaver - DEBUG - Finished building interface 2019-10-03 07:33:51,682 - NanoVNASaver.NanoVNASaver - INFO - Opening serial port /dev/ttyACM0 2019-10-03 07:33:52,100 - NanoVNASaver.NanoVNASaver - INFO - info Kernel: 4.0.0 Compiler: GCC 5.4.1 20160919 Architecture: ARMv6-M Core Variant: Cortex-M0 Port Info: Preemption through NMI Platform: STM32F072xB Entry Level Medium Density devices Board: NanoVNA Build time: Aug 2 2019 - 16:40:01 ch> 2019-10-03 07:33:52,265 - NanoVNASaver.NanoVNASaver - INFO - Read starting frequency 100000 and end frequency 150000 2019-10-03 07:33:52,265 - NanoVNASaver.NanoVNASaver - DEBUG - Starting initial sweep 2019-10-03 07:33:52,266 - NanoVNASaver.SweepWorker - INFO - Initializing SweepWorker 2019-10-03 07:33:52,266 - NanoVNASaver.SweepWorker - INFO - 1000 sweeps 2019-10-03 07:33:52,266 - NanoVNASaver.SweepWorker - DEBUG - Parsed sweep range as 100000 to 150000 2019-10-03 07:33:52,266 - NanoVNASaver.SweepWorker - DEBUG - Sweep segment no 0 2019-10-03 07:33:52,267 - NanoVNASaver.SweepWorker - DEBUG - Setting sweep range to 100000 to 100000 2019-10-03 07:33:52,568 - NanoVNASaver.SweepWorker - DEBUG - Reading frequencies 2019-10-03 07:33:52,784 - NanoVNASaver.SweepWorker - DEBUG - Reading data 0 2019-10-03 07:33:52,994 - NanoVNASaver.SweepWorker - DEBUG - Read 101 values 2019-10-03 07:33:52,995 - NanoVNASaver.SweepWorker - WARNING - Got a non-float data value: 2147483647.147483647 2147483647.147483647 (2147483647.147483647) 2019-10-03 07:33:52,995 - NanoVNASaver.SweepWorker - DEBUG - Re-reading data 0 repeats until 2019-10-03 07:34:06,245 - NanoVNASaver.SweepWorker - CRITICAL - Tried and failed to read data 0 20 times. Giving up. 2019-10-03 07:34:06,245 - NanoVNASaver.SweepWorker - DEBUG - Sweep segment no 1 2019-10-03 07:34:06,251 - NanoVNASaver.SweepWorker - DEBUG - Stopping sweeping as signalled 2019-10-03 07:34:06,258 - NanoVNASaver.SweepWorker - DEBUG - Resetting NanoVNA sweep to full range: 100000 to 150000 2019-10-03 07:34:06,260 - NanoVNASaver.SweepWorker - DEBUG - Sending "finished" signal Anyone? No RF squirted into it, default as delivered. Cannot see more than one trace. |
|
Hi Dom,
The application is receiving some weird data from you device - a value of about 2 billion, which is supposed to be in the range -1 to +1. ? Try doing a full calibration on the nanovna, including resetting the calibration first and saving it to save slot 0. If it still fails after that, there will have to be further investigation. I hope this helps! -- Rune / 5Q5R On Thu, 3 Oct 2019, 08:35 Dom Baines M1KTA via Groups.Io, <dombaines= [email protected]> wrote: I cannot get this to work on startup using nanosaver and I get in the |
|
Oh, a different issue: You set the segment count far, far too high (1000).
Try a value of 1 first, and see if that helps :-) -- Rune / 5Q5R On Thu, 3 Oct 2019, 09:19 Rune Broberg via Groups.Io, <mihtjel= [email protected]> wrote: Hi Dom, |
|
Thanks Rune,
I'll try both options. BTW this is running Linux & Python 3.74 version at home, work is much earlier so will have to wait I guess until later. I get the same output with the previous versions. Using putty I can get into it and it seems to be functioning. Used the putty/cli command to reset the calibration data 'cal reset' and it seems to function again, I get odd 2 billion results in the 4 traces though every now and then if try to alter frequency again. 72 Dom M1KTA |
|
Thanks for the segment suggestion Rune and those off line too, I don't think it was the segment issue. It seems the callibration data had somehow been borked and nothing was correct, once did the 'cal reset' over serial it came back to life again. Will, have to redo the calibration again obviously and see if it can hold the information.
The actual device on all traces without even connecting a pc was seeing the 2 billion value. 72 Dom M1KTA |
Oristo
to navigate to use esc to dismiss