开云体育

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".

Yep! They beat up on me as well in college.

Now we at LTO try to get our STEM students to properly utilize 'scientific
notation'. I was using it in the fifth grade..........but today, even
high schoolers can't seem to grasp the standard engineering notations.

Dave - W?LEV

On Mon, Aug 31, 2020 at 6:34 PM Roger Stierman via groups.io <rogerstierman=
[email protected]> wrote:

Tell me about it. This was the only translation mistake I made when i
translated all those Russian conference proceedings in grad school (early
1980's; US-USSR relations meant NOBODY ELSE had those proceedings at the
time!). I was used to nuclear reactions (MeV strength); had never run into
someone using milli eV (meV) for chemical reactions.

Learned a lot in grad school. Still remember it.


Best Regards,
Roger WA0VYU

On 8/31/2020 1:27 PM, David Eckhardt wrote:

This may be a nit pick to some, but for those of us who learned
(correctly) that uppercase = M = Mega = 10^6 and lower case = m = milli =
10^-3, the following:

mhz = millihertz or 10E-3 Hertz (1000 Hz - audio)
MHz = Megahertz or 10E+6 Hertz (1,000,000 Hz - middle of
the BC Band - RF)

Case sensitivity *does* matter!!!!

Dave - W?LEV

--
*Dave - W?LEV*
*Just Let Darwin Work*

--
*Dave - W?LEV*
*Just Let Darwin Work*

OOOps: mhz =millihertz or 10E-3 Hertz (0.001 Hz or subsonic)

Dave - W?LEV

On Mon, Aug 31, 2020 at 6:27 PM David Eckhardt via groups.io <davearea51a=
[email protected]> wrote:

This may be a nit pick to some, but for those of us who learned
(correctly) that uppercase = M = Mega = 10^6 and lower case = m = milli =
10^-3, the following:

mhz = millihertz or 10E-3 Hertz (1000 Hz - audio)
MHz = Megahertz or 10E+6 Hertz (1,000,000 Hz - middle of
the BC Band - RF)

Case sensitivity *does* matter!!!!

Dave - W?LEV

--
*Dave - W?LEV*
*Just Let Darwin Work*

--
*Dave - W?LEV*
*Just Let Darwin Work*

This may be a nit pick to some, but for those of us who learned (correctly)
that uppercase = M = Mega = 10^6 and lower case = m = milli = 10^-3, the
following:

mhz = millihertz or 10E-3 Hertz (1000 Hz - audio)
MHz = Megahertz or 10E+6 Hertz (1,000,000 Hz - middle of
the BC Band - RF)

Case sensitivity *does* matter!!!!

Dave - W?LEV

--
*Dave - W?LEV*
*Just Let Darwin Work*

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)

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?

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)

Hello group;
Today I was trying to adjust the 300 Mhz threshold point on my h4 device. Instead of seeing the change I tried to input what I get when I enter the threshold command is
threshold {in harmonic mode}
current: 0
Also on my unit the results are bad above 900 Mhz. I have tried uploading several different versions of Dislord's sfw but no help. How do I correct this problem?? Thanks.
John

NanoVNA use si5351 chip as signal generator

On datasheet this chip can work up to 200MHz

But can work up to ~300MHz (bigger or less)

On frequency near limit generation not stable (an you can see spike)

Threshold parametr - maximum frequency for si5351, after this value used harmonics

Need in console set (for 290MHz for example, you can disable calibration and reduce this parametr while no spike)
'threshold 290000000'
And after save config (for store setting)
'saveconfig'

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

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.

As you have probably read by now, the actual value is 300MHz +/- something. Very h/w specific.
/ Gerry

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

Thank you Larry. Earlier, I only searched for 297 and only found a couple of hits in the forum, which had very little info.
I'll search for threshold this time and read up on Console Command too.

It would be quite simple to do in Python, and would be a powerful new feature for room to add to NanoVNA-Saver. Excellent suggestion. Just a strobing routine at regular intervals would do the trick. Should be a trivial task in Visual Basic as well.

I doubt it would take more than a few bytes in firmware to do the task remotely to the end of memory or battery life, but a flashy GUI for the user could consume much more. Doing it with a PC attached is most compelling.

--
73

Gary, N3GO

An interesting use for our toys, which could be extended to the Tinysa too.

However, (although I am not a programmer of these newfangled devices- (Fortran and Basic 30-40 years ago only), I think that would be too much to put in the device itself.

The ability to attach a Bluetooth transmitter to the Nano so that logging could be done by a remote computer would be more realistic. I am not sure if there has been any sucess with a bluetooth dongle yet.

Steve L. G7PSZ

Hello all,

I am new to NanoVNA (very cool) and have had success calibrating, doing basic measurements, and exporting/plotting data in other software.

What I'm looking for is a way to log data unattended. Specifically, I would like to log/record the maximum/minimum S21 over a calibrated frequency range for a set time interval. I'd like to see how the frequency changes over the course of several hours of varying temperature, without having to manually save the trace for each time of interest.

Has anyone created or encountered software that can do something like this?

Thank you very much!

Hi Ramon,
This is the generator switching to harmonic mode. Search the forum for posts using the term: threshold
It's been discussed many times. Read the Console Command document in the files section on how to use the threshold command.?



On Sat, 29 Aug 2020 at 10:19 PM, Ramon S via groups.io<ve7rvs@...> wrote: Hi all, I just got a NanoVNA-H and on wide span I see big spike at around 297 MHz, that really stands out from the others. Does anybody else see this, is this normal?
TIA.

When I was taking a graduate level course in electromagnetics quite awhile ago, one of my classmates related to me that her husband said: "it is only three equations, doesn't sound very hard to me!". That was over 30 years ago, but that quote will stick with me forever.

A big improvement! Thanks!