nanovna-saver icon indicating copy to clipboard operation
nanovna-saver copied to clipboard

Sweep - Got a non plausible data value

Open CloneTV opened this issue 4 years ago • 1 comments

Describe the bug On connect device

To Reproduce Steps to reproduce the behavior:

  1. Click on 'connect'
  2. See error

2020-12-29 06:23:14,745 - NanoVNASaver.SweepWorker - WARNING - Got a non plausible data value: (-15.090496063 -8.315801620) 2020-12-29 06:23:15,140 - NanoVNASaver.SweepWorker - WARNING - Got a non plausible data value: (-15.090496063 -8.315801620) 2020-12-29 06:23:15,535 - NanoVNASaver.SweepWorker - WARNING - Got a non plausible data value: (-15.090496063 -8.315801620) 2020-12-29 06:23:15,931 - NanoVNASaver.SweepWorker - WARNING - Got a non plausible data value: (-15.090496063 -8.315801620) 2020-12-29 06:23:16,331 - NanoVNASaver.SweepWorker - WARNING - Got a non plausible data value: (-15.090496063 -8.315801620) 2020-12-29 06:23:16,536 - NanoVNASaver.SweepWorker - ERROR - Tried and failed to read data 1 5 times. 2020-12-29 06:23:16,841 - NanoVNASaver.SweepWorker - WARNING - Got a non plausible data value: (-15.090496063 -8.315801620) 2020-12-29 06:23:17,236 - NanoVNASaver.SweepWorker - WARNING - Got a non plausible data value: (-15.090496063 -8.315801620) 2020-12-29 06:23:17,627 - NanoVNASaver.SweepWorker - WARNING - Got a non plausible data value: (-15.090496063 -8.315801620) 2020-12-29 06:23:18,018 - NanoVNASaver.SweepWorker - WARNING - Got a non plausible data value: (-15.090496063 -8.315801620) 2020-12-29 06:23:18,413 - NanoVNASaver.SweepWorker - WARNING - Got a non plausible data value: (-15.090496063 -8.315801620) 2020-12-29 06:23:18,614 - NanoVNASaver.SweepWorker - CRITICAL - Tried and failed to read data 1 10 times. Giving up. 2020-12-29 06:23:18,614 - NanoVNASaver.SweepWorker - ERROR - Failed reading data 1 10 times. Data outside expected valid ranges, or in an unexpected format.

Desktop:

  • OS: Windows 10
  • Python version: in latest package version
  • NanoVNA-Saver version: v0.3.8

Device & Firmware

Kernel: 4.0.0 Compiler: GCC 8.3.1 20190703 (release) [gcc-8-branch revision 273027] Architecture: ARMv6-M Core Variant: Cortex-M0 Port Info: Preemption through NMI Platform: STM32F072xB Entry Level Medium Density devices Board: NanoVNA-H Build time: Dec 26 2019 - 19:32:30

CloneTV avatar Dec 28 '20 23:12 CloneTV

Same as this issue https://github.com/NanoVNA-Saver/nanovna-saver/issues/460 probably. It was opened after yours, and got more response, I feel for you ~

Long story short,

  • either deactivate setting "Validate received data" in device "Manage" menu
  • or do a full calibration OPEN+SHORT+LOAD+ISOLN+TRHU of our nanoVNA in directly on the device.

fredericgermain avatar Aug 10 '22 21:08 fredericgermain

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a 👍 Because this issue is marked as stale, it will be closed and locked in 7 days if no further activity occurs. Thank you for your contributions!

github-actions[bot] avatar Nov 09 '22 08:11 github-actions[bot]