开云体育

Taking advantage of an advice from One-of-Eleven, I have purchased a Bluetooth module HC5 that I would like connect to my nanoVNA-H (PCB 3.4) in order to remotely control it. As you probably remember, I have to measure antenna input impedance on a mockup of a 3U cubesat and I cannot have any metallic cable coming out from the satellite mokup.

Does someone know if I can find a proper version of nanoVNA-H firmware that already allows to interface, via Bluetooth, a nanoVNA to any software running on PC?

Unfortunately nanoVNA-H PCB 3.4 hasn't the connection to a SD card, otherwise the "autosave" features that One-of-Eleven recently added should have been the best way to operate.

Best regards,

Piero, I0KPT

I have purchased a Bluetooth module HC5

Many new smartphones support only BLE (Bluetooth Low Energy or Bluetooth 4.0),
which wants e.g. an HM-10 module.

On 8/31/20 3:33 AM, Piero Tognolatti wrote:

Taking advantage of an advice from One-of-Eleven, I have purchased a Bluetooth module HC5 that I would like connect to my nanoVNA-H (PCB 3.4) in order to remotely control it. As you probably remember, I have to measure antenna input impedance on a mockup of a 3U cubesat and I cannot have any metallic cable coming out from the satellite mokup.
Does someone know if I can find a proper version of nanoVNA-H firmware that already allows to interface, via Bluetooth, a nanoVNA to any software running on PC?

Normally, these Bluetooth USB extenders just look like a USB hub to the host computer. So you should just plug it in and it should work.

The HC5 devices I see on the web look like they're bare bluetooth modules, with a serial port (TxD, RxD) interface, but not a USB interface.

It's conceivable there's a TxD, RxD interface somewhere on the nanoVNA, and that it runs without needing new firmware.

But I think what you really want is more a "wireless USB extender" a virtual USB cable, if you will - that has a USB on both ends of the link. It needs to be a USB host on the end that connects to the NanoVNA.

I've looked around for wireless USB extenders, and a lot of them seem to be aimed at remote video cameras, or are fairly expensive boxes that are basically "USB over IP".

Your easiest approach might be to put a Raspberry Pi with WiFi with the NanoVNA, load NanoVNA-SAVER on the Pi, and then use VNC or SSH/X to remotely operate it.

Unfortunately nanoVNA-H PCB 3.4 hasn't the connection to a SD card, otherwise the "autosave" features that One-of-Eleven recently added should have been the best way to operate.
Best regards,
Piero, I0KPT

Bluetooth technology is one of the most poorly documented "stuff" around.
A techno geek will tell you it is all based on "bluez" library which is prime example of how such simple and undocumented library gets blindly passed to many "sophisticated" software application, including IDE and OS. It is allegedly included in Linux "core".

The main problem with bluetooth, in MY opinion , there are options, quite a few of them - both software and hardware.

Which one to pick really depends on SPECIFIC application - nothing new about that concept.

On my PC , I am using

Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

as generic bluetooth device with USB interface , roughly $5 item.

Works fine accessing CAT port on FT-857, using chirp software
work fine with NanoVNA-SAVER

On my FT-857 I have "serial to bluetooth " device - work fine, maybe HC5 would work too.


In theory , any USB / bluetooth device should be able to be connected to NanoVNA USB port - via proper adapter.

Of course NanoVNA firmware WITH bluetooth / USB option MAY be on some developer's work list.

Personally - I am curious why developers spent time building bigger, more expensive and less portable displays when adding bluetooth would let user to use ANY size of REMOTE display for few dollars.
( No , I am not interested in writing the software , got my own projects)

Issues I have with the Bank VNA-H4, has come from the difficulty getting
the PC to recognize the VBA as a valid drive. It ignores the VNA and my
latest iteration does have the Micro-sd card access, I can not 'talk' to
the hardware, directly, or indirectly, by attempted direct access to the
card in the 'cage' and attempting updates via SD card through the VNA.
Why include it, if you can not access the card inserted into it?

Sorry for the typos...my phone changed the words to make my replies almost
gibberish.
Even editing changed nothing.
Hit 'send', and the words changed and I could not correct them. My
apologies.

On Mon, Aug 31, 2020, 10:11 AM ERNEST AEC-RADIO via groups.io <aecradio1=
[email protected]> wrote:

Issues I have with the Bank VNA-H4, has come from the difficulty getting
the PC to recognize the VBA as a valid drive. It ignores the VNA and my
latest iteration does have the Micro-sd card access, I can not 'talk' to
the hardware, directly, or indirectly, by attempted direct access to the
card in the 'cage' and attempting updates via SD card through the VNA.
Why include it, if you can not access the card inserted into it?

On Mon, Aug 31, 2020, 10:01 AM Anne Ranch <anneranch2442@...> wrote:

Bluetooth technology is one of the most poorly documented "stuff" around.
A techno geek will tell you it is all based on "bluez" library which is
prime example of how such simple and undocumented library gets blindly
passed to many "sophisticated" software application, including IDE and

OS.

It is allegedly included in Linux "core".

The main problem with bluetooth, in MY opinion , there are options, quite
a few of them - both software and hardware.

Which one to pick really depends on SPECIFIC application - nothing new
about that concept.

On my PC , I am using

Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

as generic bluetooth device with USB interface , roughly $5 item.

Works fine accessing CAT port on FT-857, using chirp software
work fine with NanoVNA-SAVER

On my FT-857 I have "serial to bluetooth " device - work fine, maybe HC5
would work too.


In theory , any USB / bluetooth device should be able to be connected to
NanoVNA USB port - via proper adapter.

Of course NanoVNA firmware WITH bluetooth / USB option MAY be on some
developer's work list.

Personally - I am curious why developers spent time building bigger, more
expensive and less portable displays when adding bluetooth would let

user

to use ANY size of REMOTE display for few dollars.
( No , I am not interested in writing the software , got my own projects)

On 8/31/20 10:01 AM, Anne Ranch wrote:

Bluetooth technology is one of the most poorly documented "stuff" around.

And inconsistently implemented.

The main problem with bluetooth, in MY opinion , there are options, quite a few of them - both software and hardware.

There's also a HUGE difference between "compliance testing" according to the standard and "make it work". Unfortunately the owners of the standard/trademark have never really cracked down on non-compliant devices.

Which one to pick really depends on SPECIFIC application - nothing new about that concept.
On my PC , I am using
Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
as generic bluetooth device with USB interface , roughly $5 item.
Works fine accessing CAT port on FT-857, using chirp software
work fine with NanoVNA-SAVER
On my FT-857 I have "serial to bluetooth " device - work fine, maybe HC5 would work too.
In theory , any USB / bluetooth device should be able to be connected to NanoVNA USB port - via proper adapter.

The tricky part is that the NanoVNA is expecting to see a USB "host", while a lot of BT devices are USB "devices".


Then, there's the whole USB "can be either a host or a device", particularly with USB-C and power transfer.

Of course NanoVNA firmware WITH bluetooth / USB option MAY be on some developer's work list.
Personally - I am curious why developers spent time building bigger, more expensive and less portable displays when adding bluetooth would let user to use ANY size of REMOTE display for few dollars.
( No , I am not interested in writing the software , got my own projects)

Standalone device development (firmware for such devices) is easier to validate. You're not dependent on the (not entirely well documented) behavior of the external device.

I think the ultimate solution will be something like the NanoVNA (which does the measuring) combined with an Arduino, Beagle, or Pi (which does the instrument management and provides a more sophisticated UI).

That way, VNA developers can focus on instrument performance, and provide a set of basic functionality "on the device" having to do with calibration, etc. And the ability to display as a standalone device.
But then, if you had a larger device (tablet, PC, what have you) it could have software that would interact with the NanoVNA.

Conceiveably, for instance, one could write Java code for Android (or whatever is appropriate for iOS) that would talk to the NanoVNA over the existing "emulate a serial port" interface. The tablet/phone/computer is the "USB host".

On Mon, Aug 31, 2020 at 03:34 AM, Piero Tognolatti wrote:

Taking advantage of an advice from One-of-Eleven, I have purchased a
Bluetooth module HC5 that I would like connect to my nanoVNA-H (PCB 3.4)
in order to remotely control it. As you probably remember, I have to
measure antenna input impedance on a mockup of a 3U cubesat and I cannot
have any metallic cable coming out from the satellite mokup.

Does someone know if I can find a proper version of nanoVNA-H firmware
that already allows to interface, via Bluetooth, a nanoVNA to any
software running on PC?

The picture below shows the internals of the NanoVNA-H PCB3.4 which has the serial pinouts which could connect to a serial Bluetooth HC05 module. Unfortunately no one has developed any firmware which they are publicly sharing that supports these serial pins or a serial Bluetooth module.

This Bluetooth capability is available on other analyzers like the one port VNA's from RigExpert so it can be done.

Roger

For some reason the picture was not loaded to my last message. Here is a link....


Roger

I think you all are making it more complicated then it needs to be. Or maybe trying to simplfy in a way that the OP doesn't intend to consider and which probably isn't really a simplification.

Either way the nanoVNA-H v3.4 pcb does have a uart (rx/tx plus Vcc/Gnd) brought out to a header. See the schematic here:
Approrpiate header seems to be P3.

That would then be connected to the coresponding pins on the HC05. Well I assume you may need to attach Tx to Rx and Rx to Tx between the two.

The OP is just looking for FW which connects the serial console to this (real) serial port rather than the (virtual) serial port across the USB. No funky USB devices or extenders or ...

As for BLE and incompatible variants of BT: maybe all true but no one says the OP is going to use a smartphone. In fact a laptop would probably make a better choice. In my experience this should work without too many hitches for a simple serial over BT link even with oldish BT 2.x devices like an HC05

And WRT:

Personally - I am curious why developers spent time building bigger, more
expensive and less portable displays when adding bluetooth would let user to
use ANY size of REMOTE display for few dollars.

Hmmm because a bunch of people want a bigger display, full stop? They don't want remote. They don't want TWO pieces of equipment, just one.
If a bigger display is the issue for someone then the option already exists to use another device through the usb cable. But many people want a bigger display and a single piece of equipment.Enough people to make it a viable product, I guess,
Others may want remote operation but that seems to be a smaller number. I believe the serial uart pinout on the v3.4 pcb was to allow those folks an option.


On Mon, Aug 31, 2020 at 10:01 AM, Anne Ranch wrote:

Bluetooth technology is one of the most poorly documented "stuff" around.
A techno geek will tell you it is all based on "bluez" library which is
prime example of how such simple and undocumented library gets blindly passed
to many "sophisticated" software application, including IDE and OS. It is
allegedly included in Linux "core".

The main problem with bluetooth, in MY opinion , there are options, quite a
few of them - both software and hardware.

Which one to pick really depends on SPECIFIC application - nothing new about
that concept.

On my PC , I am using

Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

as generic bluetooth device with USB interface , roughly $5 item.

Works fine accessing CAT port on FT-857, using chirp software
work fine with NanoVNA-SAVER

On my FT-857 I have "serial to bluetooth " device - work fine, maybe HC5 would
work too.


In theory , any USB / bluetooth device should be able to be connected to
NanoVNA USB port - via proper adapter.

Of course NanoVNA firmware WITH bluetooth / USB option MAY be on some
developer's work list.

Personally - I am curious why developers spent time building bigger, more
expensive and less portable displays when adding bluetooth would let user to
use ANY size of REMOTE display for few dollars.
( No , I am not interested in writing the software , got my own projects)

Dave VE3LHO, what you wrote is exactly what I planned to do: use the UART pins, available on PCB 3.4 of my nanoVNA-H and connect them to HC-05 BT module, in order to use my laptop to interact wireless with nanoVNA.

However, the problem that I have is to get a firmware that set and use the UART instead of the USB port.? I am looking for someone that would like to issue a modified version of the firmware.

Best regards

Piero, I0KPT

Il 31/08/2020 22:31, Dave VE3LHO wrote:

Hmmm because a bunch of people want a bigger display, full stop? They don't want remote. They don't want TWO pieces of equipment, just one.

This is one way technical discussion turns into pointless social exchange.
I DID NOT ASK FOR "FULL STOP".

Yes, this thread MAY end up in pointless social exchange about who wants what IF THE PARTICIPANTS CHOOSE TO DO SO .

I vote to encourage real developers , not us social participants, to take a serious look at implementing wireless I/O irregardless WHAT ( we guess) MASSES "want".

PS
Last time I look there are processors with HARDWARE implementing WI-FI and/or bluetooth "on the chip" already ...
Anybody game ?

Please see inline:
On Tue, Sep 1, 2020 at 09:51 AM, Anne Ranch wrote:

Hmmm because a bunch of people want a bigger display, full stop? They don't
want remote. They don't want TWO pieces of equipment, just one.

This is one way technical discussion turns into pointless social exchange.
I DID NOT ASK FOR "FULL STOP".

I apologize if you found my "full stop" offensive. It was not meant to be. It was intended to emphasize the previous point, which I stand behind, that many people in messages in this forum asked for a larger display. You may characterize this as "social exchange" or perhaps speculation on my part but I believe there were more of those requests than for pretty much any other change, some only asked for that and some posters asked to *not* have BT/Wifi possibly due to fears about added interference and spurs. Thus: "full stop".

Yes, this thread MAY end up in pointless social exchange about who wants what
IF THE PARTICIPANTS CHOOSE TO DO SO .

In my own defence I was responding to your:

Personally - I am curious why developers spent time building bigger, more
expensive and less portable displays when adding bluetooth would let user to
use ANY size of REMOTE display for few dollars.

so I was following not leading the thread in that direction.

I vote to encourage real developers , not us social participants, to take a
serious look at implementing wireless I/O irregardless WHAT ( we guess) MASSES
"want".

OK fair enough. Let's stop the "why this not that" discussion .

PS
Last time I look there are processors with HARDWARE implementing WI-FI and/or
bluetooth "on the chip" already ...
Anybody game ?

I assume you are referring to something like an ESP which could support one or both of these?
There is, of course, no built in Wifi or BT hardware in the exisiting, standard nanoVNA-H ver3.4.
I guess my response is that the HC05 is such a device. Its is a Cambridge Silicon Radio (CSR) chip with firmware that supports serial over BT. So I guess it fits your criteria.

How does a 6 pin module plug into a 4 pin socket?

Larry, K4MLA

"How does a 6 pin module plug into a 4 pin socket?"

There are so many possible responses! [ Not "answers" ]
- Using a 'hardware multiplexing socket' (still to be developed)
- Very carefully
- with much difficulty
- with the assistance of a suitably large hammer

Sorry, folks, I couldn't resist this one! I just wish it had been posted on April 1.

Doug, K8RFT

Status and enable on the HC05 aren't needed. Only Vcc, Gnd, Rx , and Tx need to be connected. And Rx and Tx are probably labeled from the perspective of the module they are on so probably need to be cross connected Tx on HC05 to Tx on nano and vice versa.

Arrrgh. correcting my typo

And Rx and Tx are probably labeled from the perspective of
the module they are on so probably need to be cross connected Tx on HC05 to Tx
on nano and vice versa.

Which should be "Tx on HC05 to Rx on nano ..."

Looking at the schematic of the rev3.4 pcb I think there may be an issue with using this connection with HC05/HC06 type BT modules.

The power pin on P3 is connected to the 3.3V Vdd of the nano. The HC05/HC06 modules usually take 3.5V to 6V in as power, have their own onboard 3.3V LDO regulator, and are 3.3V logic levels on their Rx/Tx

I am not sure what the LDO regulator on the HC05 board will do with 3.3V input. There may be other more suitable BT modules than an HC05. Or the HC05 may work.

I'm just now seeing this! Already ordered the module!

Question, does the module fit inside the nanoVNAH4 case?

Thanks!
Brian

Bring the necessary connection points to the back of a "female" type socket, so you only need to plug it in when you want to use it.

--
*** If you are not part of the solution, then you are the problem. ( ) ***