Re: Pinned posts for current versions?
I use Thunderbird as my email client, I just tag all the software update posts with an appropriate color so they standout.
Other email clients provide the same function.
73,
Geoff AB6BT
toggle quoted message
Show quoted text
On 3/9/2024 10:51 AM, kdhenry@... wrote: I agree completely. I'm still not sure how to find the appropriate software versions (NanoVNA-H4) from reading this reflector.
Karl D. Henry, Architect, EIT
KE3IF
286 Arona Road, New Stanton, PA 15672
(724) 493-0531
kdhenry@...
-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Neil Preston W0NRP via groups.io
Sent: Saturday, March 9, 2024 11:56 AM
To: [email protected]
Subject: [nanovna-users] Pinned posts for current versions?
May I suggest that there be a pinned post at the top of the message list for the current version of firmware for each of the various forms of the NanoVNA?
It's getting a bit confusing.....
|
Re: Pinned posts for current versions?
I agree completely. I'm still not sure how to find the appropriate software versions (NanoVNA-H4) from reading this reflector.
Karl D. Henry, Architect, EIT
KE3IF
286 Arona Road, New Stanton, PA 15672
(724) 493-0531
kdhenry@...
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] < [email protected]> On Behalf Of Neil Preston W0NRP via groups.io Sent: Saturday, March 9, 2024 11:56 AM To: [email protected]Subject: [nanovna-users] Pinned posts for current versions? May I suggest that there be a pinned post at the top of the message list for the current version of firmware for each of the various forms of the NanoVNA? It's getting a bit confusing.....
|
Pinned posts for current versions?
May I suggest that there be a pinned post at the top of the message list for the current version of firmware for each of the various forms of the NanoVNA?
It's getting a bit confusing.....
|
Re: Which version of the firmware supports rotary encoders
³Ù³ó²¹²Ô°ì²õ£¬
I've recently taken some time to add a rotary encoder and the basic functionality is implemented, the menu bar scrolls well, but the trace scrolling shows that the marker points are moving too slowly.
I use PA1 and PA2 as the channels of the encoder, and I use interrupts to implement the function.
static const EXTConfig extcfg = {
{
{EXT_CH_MODE_DISABLED, NULL},
{EXT_CH_MODE_FALLING_EDGE | EXT_CH_MODE_AUTOSTART | EXT_MODE_GPIOA, extcb1},
{EXT_CH_MODE_FALLING_EDGE | EXT_CH_MODE_AUTOSTART | EXT_MODE_GPIOA, extcb1},
{EXT_CH_MODE_FALLING_EDGE | EXT_CH_MODE_AUTOSTART | EXT_MODE_GPIOA, extcb1},
{EXT_CH_MODE_FALLING_EDGE | EXT_CH_MODE_AUTOSTART | EXT_MODE_GPIOA, extcb2},
{EXT_CH_MODE_DISABLED, NULL},
{EXT_CH_MODE_DISABLED, NULL},
{EXT_CH_MODE_DISABLED, NULL},
{EXT_CH_MODE_DISABLED, NULL},
{EXT_CH_MODE_DISABLED, NULL},
{EXT_CH_MODE_DISABLED, NULL},
{EXT_CH_MODE_DISABLED, NULL},
{EXT_CH_MODE_DISABLED, NULL},
{EXT_CH_MODE_DISABLED, NULL},
{EXT_CH_MODE_DISABLED, NULL},
{EXT_CH_MODE_DISABLED, NULL},
{EXT_CH_MODE_DISABLED, NULL},
{EXT_CH_MODE_DISABLED, NULL},
{EXT_CH_MODE_DISABLED, NULL},
{EXT_CH_MODE_DISABLED, NULL},
{EXT_CH_MODE_DISABLED, NULL},
{EXT_CH_MODE_DISABLED, NULL},
{EXT_CH_MODE_DISABLED, NULL}
}
};
static void extcb1(EXTDriver *extp, expchannel_t channel)
{
(void)extp;
(void)channel;
#if ROTARY_ENCODER
if (!palReadLine(LINE_EXT_ENCODERPB))
operation_requested|=OP_LEVER;
//encoderDir = palReadLine(LINE_EXT_ENCODERB);
if (palReadLine(LINE_EXT_ENCODERB))
ClockWiseCounter ++;
else//if (encoderDir == antiClockWise)
antiClockWiseCounter ++;
if(ClockWiseCounter >= ENCODER_DEBOUNCE_TICKS)
{
ClockWiseCounter = 0;
antiClockWiseCounter = 0;
encoderDir = clockWise;
operation_requested|=OP_LEVER;
}
else if (antiClockWiseCounter >= ENCODER_DEBOUNCE_TICKS)
{
ClockWiseCounter = 0;
antiClockWiseCounter = 0;
encoderDir = antiClockWise;
operation_requested|=OP_LEVER;
}
#else
operation_requested|=OP_LEVER;
#endif // END OF ROTARY_ENCODER
}
|
Re: Problems Upgrading firmware on nanoNNA H4.
David,
Since it shows up as a STM device when you put it in DFU mode, it means a lot of correct things are happening (good cables, good hardware, nano in dfu mode, etc.).
As happens in some cases that have been reported here before, an incorrect DFU-mode driver gets loaded, and it doesn't work.
In device manager, under the USB controllers section, it should show up as "STM device in DFU mode".
If it has a different title (like "STM Bootloader"), it is probably the wrong driver.
In device manager, select "properties" for the STM device, and look at the driver version. Does it look something like the attached screenshot with driver version 3.0.6.1 from STMicroelectronics?
You can also select the Driver Details button, and it should show the driver file as being STTub30.sys.
The version numbers could be a bit different if you have a different version of DfuseDemo, and that would be ok, but if it is completely different, that is the problem.
If the wrong driver is there, as I suspect, try to manually update the driver, using the "Third Method" procedure on pg 42 (by Fig 72) in the Absolute Beginners Guide. This simply uses the "update driver" button for that device, and navigates to the desired driver file. By the way, when doing so, I found the DfuseDemo driver under another layer of folders for my installation, it was under c:\\Program Files(x86)\\STMicrolectronics\\DfuSe 3.0.6\bin\driver\win10\x64
If that doesn't work, you may have to force-unload the old driver. There is a prior thread in this group (from a long time ago) that details the procedure. You can also send me a direct message and I will try to talk you through it.
Stan
|
Re: Problems Upgrading firmware on nanoNNA H4.
If the VNA is put into DFU mode you MUST use the DFU driver. The STM Bootloader driver will not see it and no COM port is created. Period. It is a DFU device now, which is a directly driven device (hence "Direct Firmware Update") and does not caputere a COM port. The DFU driver for your version of Windows can be found in the DfuSe Demo folder tree and must be installed manually. 73 -Jim NU0C On Fri, 08 Mar 2024 10:53:35 -0800 "Tim Dawson" <tadawson@...> wrote: STM32 Bootloader *IS* correct - Dfuse should be able to see that if it's drivernhas been correctly installed. (Comes with Dfuse, not Whinders . . .)
On March 8, 2024 1:41:54 PM EST, David Grace <davidGW4OUU@...> wrote:
Thanks for the responses but DfuSeDemo doesnt recognise the vna either.
When connected normally it appears in Device Manager under ports as a vitual com port . When in dfu mode that disappears and reappears as a usb device ,STM32 BOOTLOADER.
However the nanovna app doesnt see that !!
________________________________
From: [email protected] <[email protected]> on behalf of Siegfried Jackstien <siegfried.jackstien@...>
Sent: 08 March 2024 17:08
To: [email protected] <[email protected]>
Subject: Re: [nanovna-users] Problems Upgrading firmware on nanoNNA H4.
and..if you use nanovna app.. and change device to update mode.. com port number may change...
select that comport... click on connect in app and the soft will say "found vna in upload mode.. do you want to upgrade fw?"
easy as baking cakes
dg9bfc sigi
Am 08.03.2024 17:48 schrieb Tim Dawson <tadawson@...>:
If you have DfuSeDemo installed, what is preventing you from doing the
upgrade with it?
Oh, and when in Dfu mode, the Nano's ID changes, so you would see it as a
Dfu device, not as the NanoVNA - that much is normal.
On March 8, 2024 11:41:17 AM EST, David Grace <davidGW4OUU@...>
wrote:
I have been unable to carry out this update. I currently have vesion 0.5.0.
I have downloaded several newer versions, have DfuSedemo installed with up to date drivers - did i say i am using windows 10.
I have aslo got NanoVNA-APP installed. this recognises the vna and will download screens from it which indicates that the lead i am using is ok,
but when i put the vna into dfu mode it no longer recognises the vna.
I have tried all this in 'administrator' mode without any luck !
Help - what am i doing wrong ?
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-- 73 -Jim NU0C
|
Re: Problems Upgrading firmware on nanoNNA H4.
STM32 Bootloader *IS* correct - Dfuse should be able to see that if it's drivernhas been correctly installed. (Comes with Dfuse, not Whinders . . .)
toggle quoted message
Show quoted text
On March 8, 2024 1:41:54 PM EST, David Grace <davidGW4OUU@...> wrote: Thanks for the responses but DfuSeDemo doesnt recognise the vna either.
When connected normally it appears in Device Manager under ports as a vitual com port . When in dfu mode that disappears and reappears as a usb device ,STM32 BOOTLOADER.
However the nanovna app doesnt see that !!
________________________________
From: [email protected] <[email protected]> on behalf of Siegfried Jackstien <siegfried.jackstien@...>
Sent: 08 March 2024 17:08
To: [email protected] <[email protected]>
Subject: Re: [nanovna-users] Problems Upgrading firmware on nanoNNA H4.
and..if you use nanovna app.. and change device to update mode.. com port number may change...
select that comport... click on connect in app and the soft will say "found vna in upload mode.. do you want to upgrade fw?"
easy as baking cakes
dg9bfc sigi
Am 08.03.2024 17:48 schrieb Tim Dawson <tadawson@...>:
If you have DfuSeDemo installed, what is preventing you from doing the
upgrade with it?
Oh, and when in Dfu mode, the Nano's ID changes, so you would see it as a
Dfu device, not as the NanoVNA - that much is normal.
On March 8, 2024 11:41:17 AM EST, David Grace <davidGW4OUU@...>
wrote:
I have been unable to carry out this update. I currently have vesion 0.5.0.
I have downloaded several newer versions, have DfuSedemo installed with up to date drivers - did i say i am using windows 10.
I have aslo got NanoVNA-APP installed. this recognises the vna and will download screens from it which indicates that the lead i am using is ok,
but when i put the vna into dfu mode it no longer recognises the vna.
I have tried all this in 'administrator' mode without any luck !
Help - what am i doing wrong ?
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
Re: Problems Upgrading firmware on nanoNNA H4.
Thanks for the responses but DfuSeDemo doesnt recognise the vna either. When connected normally it appears in Device Manager under ports as a vitual com port . When in dfu mode that disappears and reappears as a usb device ,STM32 BOOTLOADER. However the nanovna app doesnt see that !! ________________________________ From: [email protected] < [email protected]> on behalf of Siegfried Jackstien <siegfried.jackstien@...> Sent: 08 March 2024 17:08 To: [email protected] < [email protected]> Subject: Re: [nanovna-users] Problems Upgrading firmware on nanoNNA H4. and..if you use nanovna app.. and change device to update mode.. com port number may change... select that comport... click on connect in app and the soft will say "found vna in upload mode.. do you want to upgrade fw?" easy as baking cakes dg9bfc sigi Am 08.03.2024 17:48 schrieb Tim Dawson <tadawson@...>:
If you have DfuSeDemo installed, what is preventing you from doing the
upgrade with it?
Oh, and when in Dfu mode, the Nano's ID changes, so you would see it as a
Dfu device, not as the NanoVNA - that much is normal.
On March 8, 2024 11:41:17 AM EST, David Grace <davidGW4OUU@...>
wrote:
I have been unable to carry out this update. I currently have vesion 0.5.0.
I have downloaded several newer versions, have DfuSedemo installed with up to date drivers - did i say i am using windows 10.
I have aslo got NanoVNA-APP installed. this recognises the vna and will download screens from it which indicates that the lead i am using is ok,
but when i put the vna into dfu mode it no longer recognises the vna.
I have tried all this in 'administrator' mode without any luck !
Help - what am i doing wrong ?
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
Re: Problems Upgrading firmware on nanoNNA H4.
and..if you use nanovna app.. and change device to update mode.. com port number may change...
select that comport... click on connect in app and the soft will say "found vna in upload mode.. do you want to upgrade fw?"
easy as baking cakes
dg9bfc sigi
Am 08.03.2024 17:48 schrieb Tim Dawson <tadawson@...>:
toggle quoted message
Show quoted text
If you have DfuSeDemo installed, what is preventing you from doing the
upgrade with it?
Oh, and when in Dfu mode, the Nano's ID changes, so you would see it as a
Dfu device, not as the NanoVNA - that much is normal.
On March 8, 2024 11:41:17 AM EST, David Grace <davidGW4OUU@...>
wrote:
I have been unable to carry out this update.? I currently have vesion 0.5.0.
I have downloaded several newer versions, have? DfuSedemo installed with up to date drivers - did i say i am using windows 10.
I have aslo got NanoVNA-APP installed. this recognises the vna and will download screens from it which indicates that the lead i am using is ok,
but when i put the vna into dfu mode it no longer recognises the vna.
I have tried all this in 'administrator' mode without any luck !
Help - what am i doing wrong ?
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
Re: Problems Upgrading firmware on nanoNNA H4.
If you have DfuSeDemo installed, what is preventing you from doing the upgrade with it?
Oh, and when in Dfu mode, the Nano's ID changes, so you would see it as a Dfu device, not as the NanoVNA - that much is normal.
toggle quoted message
Show quoted text
On March 8, 2024 11:41:17 AM EST, David Grace <davidGW4OUU@...> wrote: I have been unable to carry out this update. I currently have vesion 0.5.0.
I have downloaded several newer versions, have DfuSedemo installed with up to date drivers - did i say i am using windows 10.
I have aslo got NanoVNA-APP installed. this recognises the vna and will download screens from it which indicates that the lead i am using is ok, but when i put the vna into dfu mode it no longer recognises the vna.
I have tried all this in 'administrator' mode without any luck !
Help - what am i doing wrong ?
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
Problems Upgrading firmware on nanoNNA H4.
I have been unable to carry out this update. I currently have vesion 0.5.0.
I have downloaded several newer versions, have DfuSedemo installed with up to date drivers - did i say i am using windows 10.
I have aslo got NanoVNA-APP installed. this recognises the vna and will download screens from it which indicates that the lead i am using is ok, but when i put the vna into dfu mode it no longer recognises the vna.
I have tried all this in 'administrator' mode without any luck !
Help - what am i doing wrong ?
|
Note that if you do the SOL calibration not with a load of 50 ¦¸ but with, for example, a load of 75 ¦¸, then the values displayed from the S11 are correct (compared to 75 ¦¸) and the same for the .s1p file For the values calculated by the box (R for example), you must make a rule of 3 but if you recalculate from the .s1p file taking into account the "normalization" to 75 ¦¸, the values will be correct.
--
F1AMM
Fran?ois
|
On Thu, Mar 7, 2024 at 10:52 AM, Brian Beezley wrote:
Maybe others can comment on their experience with various noncoaxial VNA
loads.
I have found that the impedance/match of chip resistors depends upon how it is mounted, positioning the resistive element towards or away from the ground plane, or on edge, changes its shunt capacitance and can make a big difference in tis performance. Then of course there is the way it is grounded..... I have settled on using 3, 150¦¸ resistors arrayed radially when building a termination onto a coaxial connector. 73, Don N2VGU
|
Re: DFU drivers not loading
Are you looking for DFU mode to update the firmware? If so, you might consider the VNA App program. It is similar to the VNA saver application, but it has a built in firmware upload function.
|
I suspect that there's so many applications where a 50 ohm resistor is nice (e.g. driving coax from a low Z source, as a series termination), or as a RF termination with a High Z receiver.
yeah, it's not a standard value in the sequence, but there clearly is a demand.
Last time I was buying non-inductive resistors for HF dummy loads from Caddock, they had 50 ohms.
The 49.9 is really an artifact of the standard sequence with the same ratio between successive values. The 1., 1.2, 1.5, 2.2, 3.3 etc.
toggle quoted message
Show quoted text
-----Original Message----- From: < [email protected]> Sent: Mar 7, 2024 7:52 AM To: < [email protected]> Subject: [nanovna-users] VNA Calibration Load When considering a VNA calibration load for various projects, I used to specify two 100-ohm 1% resistors in parallel, which halves stray inductance. Of course it also doubles stray capacitance, which may be a worse problem. So I started specifying a single 49.9-ohm 1% resistor. I was surprised to discover that 50-ohm 1% resistors are available. I was really surprised when I noticed the price for 0.1% parts: ;termination%20style=Axial~~SMD%2FSMT&tolerance=0.1%20%25&instock=y&sort=pricing&rp=passive-components%2Fresistors%7C~Termination%20Style It's unlikely a NanoVNA application needs 0.1% accuracy, but the parts are so cheap, why not? If you look at the Vishay datasheet for the first part, you'll see graphs for resistance magnitude and phase angle for several part sizes, most to 3 GHz. The curves look pretty good. I've never actually used these parts, but they look good on paper. Maybe others can comment on their experience with various noncoaxial VNA loads. Brian
|
One advantage of using cal loads that are very close to 50 ohms resistance is that you get better estimates when measuring high and low impedances using the S11 shunt method. I use home built calibration load that isconstructed with a precision 50 ohm 0805 SMD resistor . Used a nanoVNA-H4 to measure 1 ohm and 3000 ohm 0805 SMD components and got what I consider excellent results.
Roger
|
That's a great reference, Dragan. Thanks for posting it. It's interesting that IN3OTD found the 0805 pair to perform best. In the Vishay curves, the smaller sizes look considerably better. The Vishay 0805 curve even stops at 500 MHz while the smaller resistors go to 3 GHz. I wonder if the IN3OTD/Vishay discrepancy is due to different resistor manufacturers or to details of the test setup. Vishay curve note: Typical figures, HF-characteristic also depends on termination and circuit design.
Brian
|
On Thu, 7 Mar 2024 at 18:23, Reinier Gerritsen <reinier123@...> wrote:
I have seen measurements of homemade calibration loads. optimum was 2
resistors of 100 Ohm in parallel. It performed better than a single 49R9
resistor or 3 x 150 Ohm resistors.
Some interesting links:
Couldn't find the link evaluating different load styles.
Op 7-3-2024 om 16:52 schreef Brian Beezley:
When considering a VNA calibration load for various projects, I used to specify two 100-ohm 1% resistors in parallel, which halves stray inductance. Of course it also doubles stray capacitance, which may be a worse problem. So I started specifying a single 49.9-ohm 1% resistor. I was surprised to discover that 50-ohm 1% resistors are available. I was really surprised when I noticed the price for 0.1% parts:
It's unlikely a NanoVNA application needs 0.1% accuracy, but the parts are so cheap, why not? If you look at the Vishay datasheet for the first part,
you'll see graphs for resistance magnitude and phase angle for several part sizes, most to 3 GHz. The curves look pretty good.
I've never actually used these parts, but they look good on paper. Maybe others can comment on their experience with various noncoaxial VNA loads.
Brian
|
I have seen measurements of homemade calibration loads. optimum was 2 resistors of 100 Ohm in parallel. It performed better than a single 49R9 resistor or 3 x 150 Ohm resistors.
Some interesting links:
Couldn't find the link evaluating different load styles.
Op 7-3-2024 om 16:52 schreef Brian Beezley:
toggle quoted message
Show quoted text
When considering a VNA calibration load for various projects, I used to specify two 100-ohm 1% resistors in parallel, which halves stray inductance. Of course it also doubles stray capacitance, which may be a worse problem. So I started specifying a single 49.9-ohm 1% resistor. I was surprised to discover that 50-ohm 1% resistors are available. I was really surprised when I noticed the price for 0.1% parts:
It's unlikely a NanoVNA application needs 0.1% accuracy, but the parts are so cheap, why not? If you look at the Vishay datasheet for the first part,
you'll see graphs for resistance magnitude and phase angle for several part sizes, most to 3 GHz. The curves look pretty good.
I've never actually used these parts, but they look good on paper. Maybe others can comment on their experience with various noncoaxial VNA loads.
Brian
|
When considering a VNA calibration load for various projects, I used to specify two 100-ohm 1% resistors in parallel, which halves stray inductance. Of course it also doubles stray capacitance, which may be a worse problem. So I started specifying a single 49.9-ohm 1% resistor. I was surprised to discover that 50-ohm 1% resistors are available. I was really surprised when I noticed the price for 0.1% parts:
It's unlikely a NanoVNA application needs 0.1% accuracy, but the parts are so cheap, why not? If you look at the Vishay datasheet for the first part,
you'll see graphs for resistance magnitude and phase angle for several part sizes, most to 3 GHz. The curves look pretty good.
I've never actually used these parts, but they look good on paper. Maybe others can comment on their experience with various noncoaxial VNA loads.
Brian
|
Jim Shorney
Donald S Brant Jr
Roger Need
