flyoob/nanovna-f

NanoVNA-F, NanoVNA-Fairy, FreeRTOS version of TTRFTECH's NanoVNA.

nanovna-f's Issues

Is this being maintained?

Is there a newer version or different repository I should be pulling updates from?

Please change product name (omit PRO)

Hi, I'm an original developer of NanoVNA. I looked over codes you published to GitHub. Your improvement is excellent and porting onto freertos is essential I think.
Well, when I saw your repository name, I feel it is no good that named as PRO.
I think your improvement is great but it should not be named as better than others.
I propose that your product should be named such like NanoVNA-F (suffixed from your name) or something else.
I wish you to think about this issue seriously.

Serial port speed

increase serial port speed to standard value in config
tnx

Enhancement: Cho45 or Android app compatability

The VNA-H series has a nice, albeit no longer updated, Android app written by Cho45.

Would be nice to make the "F" work with it. I believe it's a "com port" issue as my app shows a communication port error and will not connect.

Thanks!

NanoVNA-F Update 2.3 System crash

After the update I only have a white screen. Doesn't work anymore?
Can someone help me.
Thanks in advance,
73 Harald Markus

firmware init suggestion

jog wheel left: pause in firmware splash screen until jog wheel left again

to allow user to read firmware release number, creator names/IDs, URLs, and callsign as long as the user likes before proceeding to measurement mode

Abandoned?

Just purchased a NanoVNC-F and I see this firmware is pretty old. Getting errors on calibration about unplausible values and most of what I see says to update firmware. Am I whistling in the wind to think this project will get attention in the future or did I buy a paperweight?

Informational commands on the serial port: "version" and "info"

Hello,
for NanoVNA-Saver, it would be a help if the following were implemented in the NanoVNA-F firmware:

1. A "version" command, returning something like, for example: "NanoVNA-F version 0.0.5"
   Having the version number clearly separated by spaces from the rest of the string is an advantage for my current parsing method. ;-)

2. An "info" command, returning at least the string "NanoVNA-F" (in order to recognize the device), but preferably also for example the supported frequency span, and any additional features supported by the firmware revision. Should you include a "raw scan" command at some point, that could be noted there, for example. This would allow the software to distinguish not just which functions are available, but also which versions of the functions, should they change over time in an incompatible manner.

Thank you for your support in developing NanoVNA-Saver! I am testing it out with the NanoVNA-F right now! :-)

Quick Start Guide Error

"NanoVNA-F Quick start guide - Firmware 0.2.1", 24 Aug 2020, Release 3.1, CONFIG, ABOUT shows a display image. That image is very different than the image on the device. See the image for what it should look like.

NanoVNA-F

Привет! Прошился прошивкой что тут и прибор перестал включатся ((( Подскажите как прошить через ST-link и где взять прошивку рабочею

Please add point

if is possible add a point to 101 to arbitrary in config
tnx
P.S. Very good product

Update to 0.5.0 release

Hi,

Are the any plans to update firmware to 0.5.0 release based on https://github.com/ttrftech/NanoVNA/releases ?

Thanks.

PS: Great work and good product by the way.

schematic diagram

Hello, could you lay out a schematic diagram of your version of NanoVNA?

Touch calbration

hi,
in the new release touch screen have a little problem to touch.
(before calibration, after calibration) after update a new version.
version 2.

Calibration problems at rev 0.0.4

Something is wrong with the CAL routines...
When doing S11 and S21 Calibration the errror terms are displayed on screen as described.
But when the correction is activated only the S11 trace is corrected!
Only when I have one trace (S21) on screen the correction works.
In some cases the S11 sweep only works when the marker is set e.g. to center.
I think here are some minor software bugs to find. In principle the device works fine! Thank you!

Callsign error

My callsign displays with three preceding graphic characters. callsign.txt does not show these. How can I eliminate these characters? Thank You

Access saved config/calibration to pc

Access saved config/calibration to pc
tnx
P.S. Very good product

Overlapping text displayed

In some situations the displayed text overlaps. See attached the screenshot.

In my opinion (my 2 cents), SWR doesn't need much space so may be can be moved a bit to right ?

Version: 0.1.4
HW: V2.2

Enhancements: Admittance plot and time delay with linear amplitude

Enhancement: Marker Target

Currently, under marker search, there is only Min/Max. Having a Target function would be useful. For example, setting Target to 0 would allow searching and tracking at the points where it crosses 0. Useful for certain methods of finding resonant frequencies.

Similarly, in other VNAs there is a 'Crossing' functionality for the Target menu. This will filter for either Positive/Negative/Either crossings when doing search or tracking.

Enhancement: capture command for screenshots

The NanoVNA-H firmware and variants has a "capture" command which returns the raw screen data, which can be used to make screenshots of the device. I'm adding support for this to NanoVNA-Saver. If you were to add a similar facility to the NanoVNA-F firmware, I would want to support this as well. :-)

Version 0.2.1 in NanoVNA-F Does Not Work work with NanoVNASaver 0.3.7

Sadly, NanoVNA-F, updated to Version 0.2.1 Does Not Work work with NanoVNASaver 0.3.7.

When I start up NanoVNASaver it reports this error immediately.
"NanoVNASaver.Version - ERROR - Unable to parse version: 0-2-1"

What are my options ??
I have also reported this to the NanoVNASaver section of GitHub