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

NanoVNA-Saver 0.3.10-pre (0.3.9) with NanoVNA-H4 Datapoints setting

Open PA3CCE opened this issue 3 years ago • 2 comments

Describe the bug

Datapoints setting for NanoVNA-H4 Firmware V 1.0.65 problematic.

To Reproduce Steps to reproduce the behavior:

  1. Go to "Manage"en select ""Datapoints" One can select 11, 51, 101, 201 and 401 points. (default is 101 points). a) 11 points is NO more supported by the device. b) when 401 points is selected an Error-screen pops up when "Sweep"' is started :

    "Error during sweep Stopped list index out of tange"

Expected behavior Is obvious

Desktop (please complete the following information):

  • OS: Windows 10:

  • NanoVNA-Saver version: 0.3.10-pre (0.3.9)

  • NanoVNA-H4 Firmware by DiSllord version 1.0.65

  • Note:

  • When a NanoVNA V2 device with it's latest firmware by DiSlord is used all number of datapoints provided work excellent !

PA3CCE avatar Jun 24 '21 14:06 PA3CCE

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 Oct 10 '22 08:10 github-actions[bot]

I checked this in the latest version (5;3) and the problem still is present !

PA3CCE avatar Oct 10 '22 10:10 PA3CCE

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 Jan 10 '23 08:01 github-actions[bot]

Still present in 5.4

sfabris avatar Feb 07 '23 22:02 sfabris

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 May 10 '23 08:05 github-actions[bot]