Re: Default com baudrate settings? NanoVNA-H
On Mon, Feb 27, 2023 at 02:34 PM, Ray, W4BYG wrote:
Roger,
My NanoVNA-H has v.0.2.3-2-g8ac9166, (not sure of the "g"), dated Build
Oct 10, 2019. Does that fall into what you call "old FW"?
YES that is very old firmware. Many bugs and improvements to the firmware have been made by DiSlord and Hugen.
If so, Don't know what is involved in gaining "the required the binary
protocol that DiSlord implemented in the NanoVNA-H firmware a couple of
years ago.
If you update the firmware in your -H to a recent version you will get the binary transfer protocol and many other useful features. The Absolute Beginners Guide in the file section of this group tells you how to install the DFU drivers that are needed for firmware update and how to install the latest firmware. /g/nanovna-users/files/Absolute%20Beginner%20Guide%20to%20The%20NanoVNA/Absolute_Beginner_Guide_NanoVNA_v1_6.pdfYou don't have to register to get the DFU program and drivers. I have put a copy on my Box account for you... Roger
|
Could the problem be, an RP-SMA cable. Been there done that! Richard K8CYK On Mon, Feb 27, 2023, 2:34 PM John Gord via groups.io <johngord= [email protected]> wrote: I don't use NanoVNA-App, but if I recall correctly, the short and open
standards can be defined with an offset (as opposed to "ideal" with no
offset). How are they defined in your setup? If they are defined with an
offset, they will show an arc on the Smith chart when later measured.
About 100ps would account for the arc seen. (It could also be that your
Edelay is set to a non-zero value.)
--John Gord
On Mon, Feb 27, 2023 at 12:52 PM, <btomek@...> wrote:
Hello Roger and John.
I did not write exactly what the s1p files are, sorry.
short.s1p open.s1p = These are the cable measurement files with
calibration
in the NanoVNA-App application. These are the results of the calibrated cable
measurements. Here there should be a point to the left or right of the Smith
chart and not what it is.
The other files are calibration files:
5mRG223_2.cal = saved calibration to file in NanoVNA-App
5mRG223_2 load.s1p 5mRG223_2 open.s1p 5mRG223_2 short.s1p = extracted s1p
from calibration file 5mRG223_2.cal
In the NanoVNA-Saver application there is no problem, the results are as they
should be. I performed the calibration in the same way as in the NanoVNA-App.
I attach the files from NanoVNA-Saver.
short-saver.s1p open-saver.s1p = measurement files.
savercal.cal = saved calibration file.
OPEN: (from Saver)
893250375 1.0043507936078475 0.0072689050591551755
895500250 0.9953096933259286 0.003040661053564544
897750125 1.0026026659671343 0.015398351945836518
900000000 1.0121008164203733 0.010567866395416996
SHORT: (from Saver)
893250375 -0.9975612334870223 -0.007908615765804592
895500250 -1.0023639507804532 -0.01784955334584766
897750125 -1.0043480661900124 -0.004281182690156899
900000000 -0.9964829970674933 -0.00947613963899272
NanoVNA-Saver works ok in my opinion, while something is wrong with
NanoVNA-App. Or I'm doing something wrong there.
I prefer in using NanoVNA-App, so I would prefer that everything is correct
there in App.
(i missed attachment before)
John, yes, i'm shorting it exactly the same in the calibration and for the
plots i sent. My cable is an extension cord, it has a male connector on one
side and a female connector on the other. I did not use a barrel adapter.
|
Re: Default com baudrate settings? NanoVNA-H
Roger,
My NanoVNA-H has v.0.2.3-2-g8ac9166, (not sure of the "g"), dated Build Oct 10, 2019. Does that fall into what you call "old FW"?
If so, Don't know what is involved in gaining "the required the binary protocol that DiSlord implemented in the NanoVNA-H firmware a couple of years ago.
Thank you for your insight and assistance,
Ray, w4byg
toggle quoted message
Show quoted text
On 2/27/2023 13:06, Roger Need via groups.io wrote: On Sun, Feb 26, 2023 at 05:34 PM, Ray, W4BYG wrote:
Having some trouble getting my NanoVNA-H to talk to NanoVNA-App. The app
says it's connected via com 3, but it's not controlling the nano, or
exchanging any data to and from it. I've tried several baud rates, but
no dice.
The baud rate does dot matter on a USB "COM port". I suspect the reason NanoVNA app is not working on your -H is because you are using old firmware. The old firmware used text transfers for data exchange to the PC and if you connect to NanoVNA app nothing happens which is what you are seeing. NanoVNA app requires the binary protocol that DiSlord implemented in the NanoVNA firmware a couple of years ago.
Roger
-- "If you want to build a strong house, I'll give you my engineer's number. If you want to build a strong life, I'll introduce you to my carpenter." Lebron and Heather Lackey
--
This email has been checked for viruses by AVG antivirus software.
www.avg.com
|
I don't use NanoVNA-App, but if I recall correctly, the short and open standards can be defined with an offset (as opposed to "ideal" with no offset). How are they defined in your setup? If they are defined with an offset, they will show an arc on the Smith chart when later measured. About 100ps would account for the arc seen. (It could also be that your Edelay is set to a non-zero value.)
--John Gord
toggle quoted message
Show quoted text
On Mon, Feb 27, 2023 at 12:52 PM, <btomek@...> wrote:
Hello Roger and John.
I did not write exactly what the s1p files are, sorry.
short.s1p open.s1p = These are the cable measurement files with calibration
in the NanoVNA-App application. These are the results of the calibrated cable
measurements. Here there should be a point to the left or right of the Smith
chart and not what it is.
The other files are calibration files:
5mRG223_2.cal = saved calibration to file in NanoVNA-App
5mRG223_2 load.s1p 5mRG223_2 open.s1p 5mRG223_2 short.s1p = extracted s1p
from calibration file 5mRG223_2.cal
In the NanoVNA-Saver application there is no problem, the results are as they
should be. I performed the calibration in the same way as in the NanoVNA-App.
I attach the files from NanoVNA-Saver.
short-saver.s1p open-saver.s1p = measurement files.
savercal.cal = saved calibration file.
OPEN: (from Saver)
893250375 1.0043507936078475 0.0072689050591551755
895500250 0.9953096933259286 0.003040661053564544
897750125 1.0026026659671343 0.015398351945836518
900000000 1.0121008164203733 0.010567866395416996
SHORT: (from Saver)
893250375 -0.9975612334870223 -0.007908615765804592
895500250 -1.0023639507804532 -0.01784955334584766
897750125 -1.0043480661900124 -0.004281182690156899
900000000 -0.9964829970674933 -0.00947613963899272
NanoVNA-Saver works ok in my opinion, while something is wrong with
NanoVNA-App. Or I'm doing something wrong there.
I prefer in using NanoVNA-App, so I would prefer that everything is correct
there in App.
(i missed attachment before)
John, yes, i'm shorting it exactly the same in the calibration and for the
plots i sent. My cable is an extension cord, it has a male connector on one
side and a female connector on the other. I did not use a barrel adapter.
|
Hello Roger and John.
I did not write exactly what the s1p files are, sorry.
short.s1p open.s1p = These are the cable measurement files with calibration in the NanoVNA-App application. These are the results of the calibrated cable measurements. Here there should be a point to the left or right of the Smith chart and not what it is.
The other files are calibration files:
5mRG223_2.cal = saved calibration to file in NanoVNA-App
5mRG223_2 load.s1p 5mRG223_2 open.s1p 5mRG223_2 short.s1p = extracted s1p from calibration file 5mRG223_2.cal
In the NanoVNA-Saver application there is no problem, the results are as they should be. I performed the calibration in the same way as in the NanoVNA-App.
I attach the files from NanoVNA-Saver.
short-saver.s1p open-saver.s1p = measurement files.
savercal.cal = saved calibration file.
OPEN: (from Saver)
893250375 1.0043507936078475 0.0072689050591551755
895500250 0.9953096933259286 0.003040661053564544
897750125 1.0026026659671343 0.015398351945836518
900000000 1.0121008164203733 0.010567866395416996
SHORT: (from Saver)
893250375 -0.9975612334870223 -0.007908615765804592
895500250 -1.0023639507804532 -0.01784955334584766
897750125 -1.0043480661900124 -0.004281182690156899
900000000 -0.9964829970674933 -0.00947613963899272
NanoVNA-Saver works ok in my opinion, while something is wrong with NanoVNA-App. Or I'm doing something wrong there.
I prefer in using NanoVNA-App, so I would prefer that everything is correct there in App.
(i missed attachment before)
John, yes, i'm shorting it exactly the same in the calibration and for the plots i sent. My cable is an extension cord, it has a male connector on one side and a female connector on the other. I did not use a barrel adapter.
|
It looks like part of the problem may have to do with how you short the cable. Are you shorting it exactly the same in the calibration and for the plots you sent? (I assume the calibration is done with a male short and a barrel adapter. Is that how you generated the plots?} A barrel adapter could generate the arc you see on the plots.
If they are shorted the same way, how was the short defined to the calibration? If the Short is defined as non-ideal, application of the same Short will generate an arc instead of a dot when measured.
This does not explain the behavior at exactly 900 MHz.
--John Gord
toggle quoted message
Show quoted text
On Sun, Feb 26, 2023 at 12:30 PM, <btomek@...> wrote:
Hello.
If I connect a cable to the NanoVNA and calibrate OSL at the end of that
cable, and measure the same cable, I should get 1 small point to the right of
the Smith chart when the cable is open, or 1 small point to the left when the
cable is shorted.
This happens if I calibrate in the NanoVNA device and use the internal
calibration.
But this does not happen when calibrating in the NanoVNA-App. After
calibrating with the 5-meter RG223 cable in the NanoVNA-App, something goes
wrong. Smith is rotating backwards.
In addition, the last measurement point is significantly different from the
previous ones, and this last point looks correct.
OPEN:
893250375 7,452017665e-01 6,873174310e-01
895500250 7,410393953e-01 6,873663068e-01
897750125 7,427099347e-01 6,907842755e-01
900000000 1,001433492e+00 3,330142936e-03
SHORT:
893250375 -7,893709540e-01 -6,558784842e-01
895500250 -7,710666060e-01 -6,550329924e-01
897750125 -7,579773664e-01 -6,538544297e-01
900000000 -1,000591993e+00 -2,029109281e-03
If I do the calibration without a cable, directly on the SMA socket of the
NanoVNA, the graphs do not show anything disturbing. Probably the error also
exists but is so small that it is invisible.
NanoVNA-App version 1.1.209 +OD12 from OwenDuffy,
NanoVNA-App version 1.1.213 released 2023-01-22 from DiSlord has the same
issue.
NanoVNA-H4 firmware 1.2.19 from DiSlord
Is this a bug or am I doing something wrong?
|
Re: check "Dollar Tree" store. Now Dollar and a Quarter!
Here's another test you might want to try: Bring a small magnet next time and place it near the wire and see if its magnetic. If it is, you may have a little copper and a little iron, (IRON NOT GOOD).
Mike C. Sand Mtn GA
toggle quoted message
Show quoted text
On 2/27/2023 2:19 PM, Clyde Lambert wrote: Hello,
I purchased a couple of USB lead wires from Dollar Tree. They lasted about three or four weeks, then the insulation started separateing from the back of the connector housing. Also, The wire size in the $1.25 cables, are much smaller in diamiter than a standard cable.
Again we refer back to the old saying,
You get what you payed for. Cheep price, cheep product. You will never find any type of warranty on a Dollar Tree product.
However, if you are happy with their product and it fits your needs, be my guest.
Just my 2 cents worth.
Clyde KC7BJE
|
Re: check "Dollar Tree" store. Now Dollar and a Quarter!
Hello,
I purchased a couple of USB lead wires from Dollar Tree. They lasted about three or four weeks, then the insulation started separateing from the back of the connector housing. Also, The wire size in the $1.25 cables, are much smaller in diamiter than a standard cable.
Again we refer back to the old saying,
You get what you payed for. Cheep price, cheep product. You will never find any type of warranty on a Dollar Tree product.
However, if you are happy with their product and it fits your needs, be my guest.
Just my 2 cents worth.
Clyde KC7BJE
|
On Sun, Feb 26, 2023 at 12:30 PM, <btomek@...> wrote:
Hello.
If I connect a cable to the NanoVNA and calibrate OSL at the end of that
cable, and measure the same cable, I should get 1 small point to the right of
the Smith chart when the cable is open, or 1 small point to the left when the
cable is shorted.
There is not a problem/bug with NanoVNA app or Saver. Your plots are not what you should be getting with a calibration. The problem is either with your calibration method, NanoVNA or calibration loads. I suggest you do a cal right at the NanoVNA itself and verify that Short, Open and Load are at the left, middle and right of the Smith chart and that other plots look good as well. Then calibrate at the end of the cable and do the same. You can take screenshots from the NanoVNA app and verify that transferred sweep plots look good there but remember to set the cal option in NanoVNA app to VNA. Feel free to post your screenshots here for comments if you wish. Roger
|
Re: Default com baudrate settings? NanoVNA-H
On Sun, Feb 26, 2023 at 05:34 PM, Ray, W4BYG wrote:
Having some trouble getting my NanoVNA-H to talk to NanoVNA-App. The app
says it's connected via com 3, but it's not controlling the nano, or
exchanging any data to and from it. I've tried several baud rates, but
no dice.
The baud rate does dot matter on a USB "COM port". I suspect the reason NanoVNA app is not working on your -H is because you are using old firmware. The old firmware used text transfers for data exchange to the PC and if you connect to NanoVNA app nothing happens which is what you are seeing. NanoVNA app requires the binary protocol that DiSlord implemented in the NanoVNA firmware a couple of years ago. Roger
|
Re: nano vna small one is it the F
On Mon, Feb 27, 2023 at 09:17 AM, Roy J. Tellason, Sr. wrote: Which is why when I ordered my unit from R&L, I also ordered adapters to BNC
and UHF. What I forgot about was SMA M-F "connector savers" to spare the
installed connectors on the unit from much wear and tear, but I did pick a
couple of those up at a hamfest at a later date... :-)
If those adapters are rigid ones you have to be careful because PL259 cables can put a lot of strain on the SMA connector/PCB board. I prefer to use pigtail adapters made with RG-174 or RG-316. I suggest you get some connector savers soon or you will wear them out quickly. Low cost from this USA vendor. Roger
|
Re: nano vna small one is it the F
On Sunday 26 February 2023 04:54:48 pm Jim Lux wrote: On 2/25/23 5:43 AM, DougVL wrote:
NanoVNA-F for outdoors use, -H for indoors. The little 2.8 inch -H is quite inexpensive, and also works well with PC software (NanoVNA-Saver and NanoVNA-APP), showing on a larger screen. With the PC software you can also take, print and save screenshots. The PC software also has different and additional graphing and analysis features than the firmware has.
A little 28 inch -F for $40 or $50 can be worth the extra cost just for the new cable measurement features! [IMHO]
There is a 'hidden' cost to these instruments, though. Adapters! The nano comes with 2 SMA cables and the calibration kit. I have since purchased adapters for PL259, SO239, BNC, and F connectors. And each adapter comes in 4 configurations: M-M, M-F, F-F and F-M. It's also very nice to have a BNC-to-'dual binding post' connector for connecting individual wires. Testing toroid cores is my main use for the binding post adapter.
Both styles of VNA use and share the same set of adapters. Yes, it's kind of like buying a vertical mill. That's only the start -
now you need to buy all the tooling. Which is why when I ordered my unit from R&L, I also ordered adapters to BNC and UHF. What I forgot about was SMA M-F "connector savers" to spare the installed connectors on the unit from much wear and tear, but I did pick a couple of those up at a hamfest at a later date... :-) -- Member of the toughest, meanest, deadliest, most unrelenting -- and ablest -- form of life in this section of space, ?a critter that can be killed but can't be tamed. ?--Robert A. Heinlein, "The Puppet Masters" - Information is more dangerous than cannon to a society ruled by lies. --James M Dakin
|
From Wiki
SMA connectors are rated for up to 500 mating cycles,[7] but to achieve this it is necessary to properly torque the connector when making the connection.
A 5?16 inch torque wrench is required for this, set to 3¨C5 in¡¤lbf (0.3 to 0.6 N¡¤m) for brass, and 7¨C10 in¡¤lbf (0.8 to 1.1 N¡¤m) for stainless steel connectors.
|
check "Dollar Tree" store. Now Dollar and a Quarter!
On Feb 26, 2023, at 10:39 PM, KENT BRITAIN <WA5VJB@...> wrote:
Dollar Tree sells both for $1.25
On Sunday, February 26, 2023 at 09:37:00 PM CST, Clyde Lambert <clyde.lambert@...> wrote:
Try Amazon. you can get USB C TO USB A. OR USB C to USB C.
I have purchased several from them.
Clyde KC7BJE
|
Re: How can I replace the USB cable, My got misplaced in a move
Dollar Tree sells both for $1.25
toggle quoted message
Show quoted text
On Sunday, February 26, 2023 at 09:37:00 PM CST, Clyde Lambert <clyde.lambert@...> wrote:
Try Amazon. you can get USB C TO USB A. OR USB C to USB C.
I have purchased several from them.
Clyde KC7BJE
|
Re: How can I replace the USB cable, My got misplaced in a move
Try Amazon. you can get USB C TO USB A. OR USB C to USB C.
I have purchased several from them.
Clyde KC7BJE
|
test111
--
*_ . . _ _ _ _ _ _ . _ . .*
|
Re: Default com baudrate settings? NanoVNA-H
Ray, it sounds like you have a device already assigned to COM3. You need to delete it.
If your usings Windows open up the Device Manager by right clicking on the Microsoft Logo in the lower left hand corner of your screen. See if you can find a Comport listing. Select it and delete any Prolific Drivers or other ones you see there. Then restart your computer.
This might help. Not sure. But worth a try.
Doug Hayward
K8DRH
Cell: 480.773.8955
Email: dhayward@...
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] < [email protected]> On Behalf Of Ray, W4BYG Sent: Sunday, February 26, 2023 20:35 To: [email protected]Subject: [nanovna-users] Default com baudrate settings? NanoVNA-H Having some trouble getting my NanoVNA-H to talk to NanoVNA-App. The app says it's connected via com 3, but it's not controlling the nano, or exchanging any data to and from it. I've tried several baud rates, but no dice. I have not been able to locate what baud rate the Nano's default setting is. I have poured over the Nano manual. Maybe I've just missed it but so far, no help. Would appreciate that info, or how I can find it on the Nano. Ray, W4BYG -- "If you want to build a strong house, I'll give you my engineer's number. If you want to build a strong life, I'll introduce you to my carpenter." Lebron and Heather Lackey -- This email has been checked for viruses by AVG antivirus software. www.avg.com
|
Re: Default com baudrate settings? NanoVNA-H
The nanovna uses the USB protocol, so eventhough it looks like a serial
port, it doesn't use a baud rate setting. So that shouldn't matter. For
reference, though, mine shows the default 38400/8/n/1 setting in device
manager.
Your problem is likely something different.
Stan
toggle quoted message
Show quoted text
On Sun, Feb 26, 2023, 5:35 PM Ray, W4BYG <w4byg@...> wrote: Having some trouble getting my NanoVNA-H to talk to NanoVNA-App. The app
says it's connected via com 3, but it's not controlling the nano, or
exchanging any data to and from it. I've tried several baud rates, but
no dice.
I have not been able to locate what baud rate the Nano's default setting
is. I have poured over the Nano manual. Maybe I've just missed it but so
far, no help. Would appreciate that info, or how I can find it on the Nano.
Ray, W4BYG
--
"If you want to build a strong house, I'll give you my engineer's number.
If you want to build a strong life, I'll introduce you to my carpenter."
Lebron and Heather Lackey
--
This email has been checked for viruses by AVG antivirus software.
www.avg.com
|
Default com baudrate settings? NanoVNA-H
Having some trouble getting my NanoVNA-H to talk to NanoVNA-App. The app says it's connected via com 3, but it's not controlling the nano, or exchanging any data to and from it. I've tried several baud rates, but no dice.
I have not been able to locate what baud rate the Nano's default setting is. I have poured over the Nano manual. Maybe I've just missed it but so far, no help. Would appreciate that info, or how I can find it on the Nano.
Ray, W4BYG
--
"If you want to build a strong house, I'll give you my engineer's number.
If you want to build a strong life, I'll introduce you to my carpenter."
Lebron and Heather Lackey
--
This email has been checked for viruses by AVG antivirus software.
www.avg.com
|
Roger Need
Ray, W4BYG
Mike C.
Clyde Lambert
Carsten F (OZ1FTG)