Thank you for a really great product! I bought my first VNA almost 4 decades ago - an HP8753A with a 85046A test head. I still use it but it is 'aging' - I consider, from what I've seen so far with the V2, that it does as much or more (except the '4 port' capability and the improved dynamic range of the HP) - and its a heck of a lot easier to get data to my computer files. The V4 looks like it will encroach on the dynamic range too.
Issues:
In general:
A. the resolution of the display combined with the very small text size (on 3.2 inch screen) is very difficult for me to read - I would like to be able to increase font size. A higher resolution screen would probably also help.
B. I would also like a 'low battery' warning -
Particular to the Update 20201013
The new keypad size is nice and easy to read, but it has displaced important information on the TDR settings display (it no longer displays what the current settings are)
The location and function of the SAVE button is no longer clear on the V2. From Configuration - the SAVE button saves the current configuration as the new boot configuration - it does not save it to one of the 5 SAVE folders. The SAVE in the Calibration menu would lead me to think I am saving a calibration set up (and I am) to one of the 5 locations - but what i am missing is a 'save machine state' memory bank. In the original nanoVNA menu, SAVE and RECALL were submenus of a button named appropriately "RECALL SAVE". Also - the configuration created and accessed by NanoVNA Saver is not retained by either the V2 or the NanoVNA Saver program (at least I haven't found that yet) - it should be automatic through a disconnect and reconnect - with a 'choice' of "last used on Saver" or "Current NanoVNA settings" rather than some arbitrary default.
In NanoVNA Saver - Sweep Settings/ Manage Bands: Adding a new Band - the END (Hz) cannot be configured with a number greater than 300M (300000000)
I assume the limitation on the V2 for "201 pts" is due to processor speed - and that is why the SAVER can offer 1023 points. Reality for me is, if I need more points (accuracy in a TDR measurement) and I am willing to wait for the result, why not give me the option - along with a warning.
Thank you for a really great product! I bought my first VNA almost 4 decades ago - an HP8753A with a 85046A test head. I still use it but it is 'aging' - I consider, from what I've seen so far with the V2, that it does as much or more (except the '4 port' capability and the improved dynamic range of the HP) - and its a heck of a lot easier to get data to my computer files. The V4 looks like it will encroach on the dynamic range too.
Issues: In general: A. the resolution of the display combined with the very small text size (on 3.2 inch screen) is very difficult for me to read - I would like to be able to increase font size. A higher resolution screen would probably also help.
B. I would also like a 'low battery' warning -
Particular to the Update 20201013
The new keypad size is nice and easy to read, but it has displaced important information on the TDR settings display (it no longer displays what the current settings are)
The location and function of the SAVE button is no longer clear on the V2. From Configuration - the SAVE button saves the current configuration as the new boot configuration - it does not save it to one of the 5 SAVE folders. The SAVE in the Calibration menu would lead me to think I am saving a calibration set up (and I am) to one of the 5 locations - but what i am missing is a 'save machine state' memory bank. In the original nanoVNA menu, SAVE and RECALL were submenus of a button named appropriately "RECALL SAVE". Also - the configuration created and accessed by NanoVNA Saver is not retained by either the V2 or the NanoVNA Saver program (at least I haven't found that yet) - it should be automatic through a disconnect and reconnect - with a 'choice' of "last used on Saver" or "Current NanoVNA settings" rather than some arbitrary default.
In NanoVNA Saver - Sweep Settings/ Manage Bands: Adding a new Band - the END (Hz) cannot be configured with a number greater than 300M (300000000)