¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Serial communication with uC #nanovna-v2


 

Hi everyone!

I'm new here and wanna know about serial interface for communication with the nanovna v2_2. It is possible use some kind of uC (like arduino, esp32 or raspberry pi 0) for communicate with the device? Has anyone tried? I'm trying to capture the nanovna data, process it and make it available on the internet using a device other than an ordinary PC.


 

There is a reason why no one responded to this question in the other group.
Considering that you are unable to answer this simple question
yourself I doubt that you will be able to reimplement a fairly complicated
communication protocol that V2 uses.

Anyway if I remember correctly the V2 does not have serial breakout on
PCB and there is no firmware support. You can solder some wires to the
micro
and try to implement the serial support in the firmware.
Connecting over USB would require USB host support on the micro and that is
even more problematic. If your goal is to output the data over IP your best
bet
would be to connect the "V1" to a Raspberry Pi and modify the Python
examples
to output the data in the format that you require.

On Wed, 18 Nov 2020 at 21:38, Laps <lincoln.aps@...> wrote:

Hi everyone!

I'm new here and wanna know about serial interface for communication with
the nanovna v2_2. It is possible use some kind of uC (like arduino, esp32
or raspberry pi 0) for communicate with the device? Has anyone tried? I'm
trying to capture the nanovna data, process it and make it available on the
internet using a device other than an ordinary PC.






 

On Thu, Nov 19, 2020 at 04:55 AM, Dragan Milivojevic wrote:


There is a reason why no one responded to this question in the other group.
Considering that you are unable to answer this simple question
yourself I doubt that you will be able to reimplement a fairly complicated
communication protocol that V2 uses.

Anyway if I remember correctly the V2 does not have serial breakout on
PCB and there is no firmware support. You can solder some wires to the
micro
and try to implement the serial support in the firmware.
Connecting over USB would require USB host support on the micro and that is
even more problematic. If your goal is to output the data over IP your best
bet
would be to connect the "V1" to a Raspberry Pi and modify the Python
examples
to output the data in the format that you require.


On Wed, 18 Nov 2020 at 21:38, Laps <lincoln.aps@...> wrote:

Hi everyone!

I'm new here and wanna know about serial interface for communication with
the nanovna v2_2. It is possible use some kind of uC (like arduino, esp32
or raspberry pi 0) for communicate with the device? Has anyone tried? I'm
trying to capture the nanovna data, process it and make it available on the
internet using a device other than an ordinary PC.





Thank's for your quick reply, Dragan.

I received the device yesterday and I am still learning about the serial protocol implemented in this version. I am using the script available at: as a base and I would like to use an esp32 module with micropython to capture VNA channel 1 data. I believe that the use of raspberry pi 0 is the best for this application, since an USB host controller is required.

Sorry about the duplicate topic.


 

Laps,

The VNA appears as a Virtual com port and yes you can see it under Linux
Raspberry Pi as a serial device nad send the Binary Protocol to it

I have some c# code here for you to see how it works

if you need help converting something to c/c++ under GNU I'd be gald to help you too



Ed? WB9RAA, Prescott Valley, AZ

*Sent:* Wednesday, November 18, 2020 at 2:13 PM
*From:* "Laps" <lincoln.aps@...>
*To:* [email protected]
*Subject:* Re: [nanovna-users] Serial communication with uC #nanovna-v2
On Thu, Nov 19, 2020 at 04:55 AM, Dragan Milivojevic wrote:


There is a reason why no one responded to this question in the other group.
Considering that you are unable to answer this simple question
yourself I doubt that you will be able to reimplement a fairly complicated
communication protocol that V2 uses.

Anyway if I remember correctly the V2 does not have serial breakout on
PCB and there is no firmware support. You can solder some wires to the
micro
and try to implement the serial support in the firmware.
Connecting over USB would require USB host support on the micro and that is
even more problematic. If your goal is to output the data over IP your best
bet
would be to connect the "V1" to a Raspberry Pi and modify the Python
examples
to output the data in the format that you require.


On Wed, 18 Nov 2020 at 21:38, Laps <lincoln.aps@...> wrote:

Hi everyone!

I'm new here and wanna know about serial interface for communication with
the nanovna v2_2. It is possible use some kind of uC (like arduino, esp32
or raspberry pi 0) for communicate with the device? Has anyone tried? I'm
trying to capture the nanovna data, process it and make it available on the
internet using a device other than an ordinary PC.





Thank's for your quick reply, Dragan.

I received the device yesterday and I am still learning about the serial protocol implemented in this version. I am using the script available at: as a base and I would like to use an esp32 module with micropython to capture VNA channel 1 data. I believe that the use of raspberry pi 0 is the best for this application, since an USB host controller is required.

Sorry about the duplicate topic.


 

On 11/18/20 12:31 PM, Laps wrote:
Hi everyone!
I'm new here and wanna know about serial interface for communication with the nanovna v2_2. It is possible use some kind of uC (like arduino, esp32 or raspberry pi 0) for communicate with the device? Has anyone tried? I'm trying to capture the nanovna data, process it and make it available on the internet using a device other than an ordinary PC.
There are versions of the firmware (I don't know which, but the various wikis probably have info) that support the on-board serial port. You'll need an appropriate voltage device for the other end (3.3V TTL, I believe).

The protocol is text based and not mind bendingly complex. I would suggest you fire it up using the default USB interface (which emulates a serial port, at least on my mac) and fool with it a bit before going the "dedicated device" route. At least you'll know the problem is with your new serial interface, and not making a mistake with the messages.

check this: /g/nanovna-users/wiki/12760
I suggest getting the pdf file.
There *are* some new commands in some versions of the firmware.

There's a simple interface program in python in the NanoVNA-H source tree (called, not too oddly, nanovna.py)

NanoVNA-Saver is a substantially more complex and capable program in python that also uses the serial interface model.

If you're thinking RPi, I'd not bother with the serial port, just plug it into the USB on the Pi and be done with it.

For what it's worth, the same code works on a Beagleboard with a USB.


 

That is for "V1" not V2 and the firmware that supports it comes from
discord ...

There are versions of the firmware (I don't know which, but the various

wikis probably have info) that support the on-board serial port. You'll
need an appropriate voltage device for the other end (3.3V TTL, I believe).

The protocol is text based and not mind bendingly complex. I would
suggest you fire it up using the default USB interface (which emulates a
serial port, at least on my mac) and fool with it a bit before going the
"dedicated device" route. At least you'll know the problem is with your
new serial interface, and not making a mistake with the messages.

check this: /g/nanovna-users/wiki/12760
I suggest getting the pdf file.
There *are* some new commands in some versions of the firmware.

There's a simple interface program in python in the NanoVNA-H source
tree (called, not too oddly, nanovna.py)

NanoVNA-Saver is a substantially more complex and capable program in
python that also uses the serial interface model.

If you're thinking RPi, I'd not bother with the serial port, just plug
it into the USB on the Pi and be done with it.

For what it's worth, the same code works on a Beagleboard with a USB.






 

On Thu, Nov 19, 2020 at 07:00 AM, Jim Lux wrote:


There are versions of the firmware (I don't know which, but the various
wikis probably have info) that support the on-board serial port. You'll
need an appropriate voltage device for the other end (3.3V TTL, I believe).

The protocol is text based and not mind bendingly complex. I would
suggest you fire it up using the default USB interface (which emulates a
serial port, at least on my mac) and fool with it a bit before going the
"dedicated device" route. At least you'll know the problem is with your
new serial interface, and not making a mistake with the messages.

check this: /g/nanovna-users/wiki/12760
I suggest getting the pdf file.
There *are* some new commands in some versions of the firmware.

There's a simple interface program in python in the NanoVNA-H source
tree (called, not too oddly, nanovna.py)

NanoVNA-Saver is a substantially more complex and capable program in
python that also uses the serial interface model.

If you're thinking RPi, I'd not bother with the serial port, just plug
it into the USB on the Pi and be done with it.

For what it's worth, the same code works on a Beagleboard with a USB.
Thanks for the reply, Jim Lux.

I just bought an RPi 0, it seems to be the most practical solution for my project, since in the V2 version of the nanovna the communication protocol is binary based. I'm using the code from the nanovna.py file that you mentioned.


 

Thanks for share this information Ed March! It will be very helpful.


 

On 11/18/20 4:20 PM, Laps wrote:
On Thu, Nov 19, 2020 at 07:00 AM, Jim Lux wrote:
<snip description of where to find the code>
Thanks for the reply, Jim Lux.
I just bought an RPi 0, it seems to be the most practical solution for my project, since in the V2 version of the nanovna the communication protocol is binary based. I'm using the code from the nanovna.py file that you mentioned.
oh. You're doing a V2 - I don't know if the nanovna.py works with the V2 - maybe there's one matching the firmware for the V2.