Does not find the STM Device in DFU Mode file. I manually tried to locate
and it is not found anywhere. I searched both rprogram x64 and x86 STM
Electronics folders and cannot find a compatible driver. It always loads
the bootloader file.
What is the name of the file? I might be looking for something else.
toggle quoted message
Show quoted text
On Sun, Mar 5, 2023 at 11:33?AM N2MS <mstangelo@...> wrote: Steve,
I had a similar problem. DFUseDemo was loaded with the Bootloader driver
which I use with STM32 CubeProgrammer for my Malahite DSP2 receiver. It
uses the bootloader mode to update firmware. Sometimes when I exit it saves
the bootloader driver.
To change drivers for the DFU Mode perform the following:
Start DFuSe Demo. If it does not detect any device in DFU mode do the
following:
Start the Device Manager
- Under "Universal Serial Bus devices" you should see "STM32 BOOTLOADER"
- right click on "STM32 BOOTLOADER" and select "Update Driver"
- select "Browse my computer for drivers"
- select "Let me pick from a list of available drivers on my computer"
- Under "Select the device driver you want to install for this hardware".
Check the "Show compatible hardware" box
- You should see the "STM Device in DFU Mode" and "STM32 Bootloader"
drivers.
- Select the "STM Device in DFU Mode" driver.
- Select "Next" and it should display "Windows has successfully updated
your drivers" Close this box
- The Device Manager should show:
"Universal Serial Bus Controllers"
"STM Device in DFU Mode"
- DfuSe Demo will detect the device in under DFU Mode.
Mike N2MS
On 03/05/2023 8:45 AM Steve Bowers <bowxyz@...> wrote:
I got to the point of starting DiFUse and also downloaded the latest
firmware.
Following the directions in the beginners guide I started the DFU demo
program and started the nano in DFU mode as instructed.
However all I see in device manager is STM Bootloader and not Nano in DFU
mode under the USB controllers.
Going back to the DFU demo program and selecting the drop down box where I
should be seeing the device, nothing is there.
I double checked to make sure the Nano is being seen in device manager by
cycling the power switch. Turning it off removes it from the device manager
USB ports.
Any ideas?
Steve
|
@Roger, thank you for these tests that confirm the problem, you did a good job! measure without cable calibration can not work good so question is ... did you calibrate out that 3m cable??
if calibrated (and calibration IS LOADED ALSO!!) then nanovna_app shows near perfect results compared to internal calibration @Siegfried - after all, the whole topic is about getting an incorrect result despite calibrating the cable. Did you measure this 13cm antenna through a calibrated cable? what length was it? can you share the results? I checked what happens if I change the data in the calibration file to random for one single frequency 888750625, but in NanoVNA-Saver. A similar test I did earlier /g/nanovna-users/message/31595. And now it happens as expected, the result only for this one frequency modified in the calibration file changes, and the neighboring ones remain unchanged. In NanoVNA-App, this affects 4 adjacent results, even though the measurement range and measurement frequencies are the same as in the calibration file, so interpolation should not work here. Original: 886500750 0.9987047176708422 0.00105312817688446 888750625 1.0003020639355351 0.0006683727808330564 891000500 1.0002212815243825 -9.12623904043544e-05 After modify 888750625 in cal file: 886500750 0.9987047176708422 0.00105312817688446 888750625 0.5261937827007473 0.027498192196368145 891000500 1.0002212815243825 -9.12623904043544e-05 Full files in attachment. By the way, can I find somewhere a simple formula, one for the dummies, how to calculate this calibration correction? I simply have uncalibrated S parameters for 4 measurements: - Open, Short, Load - DUT I want to correct the DUT measurement using these OSLs. I looked through the file "NanoVNA traces and formulas.doc" and did not find this there. Maybe there is a newer version of this file somewhere that contains this, or is it somewhere else?
|
Re: DiSlord build 1.2.19, saved cal files give error when reading
Sigi,
let's just say yes, today DiSlord uploaded v1.2.20 for NanoVNA-H and NanoVNA-H4.
v1.3.15 still applies to NanoVNA V2 family and LiteVNA! :D
--
Gyula HA3HZ ( )
|
Re: NanoVNA-H4 Port Models
I use my NanoVNA from 0.4 to 150 MHz. I wonder of installing a 10uF coupling capacitor with the 1uF would help the low frequency response. Can anyone recommend a SMD part from Mouser or Digikey?
Thanks,
Mike N2MS
toggle quoted message
Show quoted text
On 03/05/2023 8:22 AM Brian Beezley <k6sti@...> wrote:
I've been looking into the S21 and Y21 methods of calculating an unknown impedance connected between the two VNA ports. The port impedances play a role. I used Micro-Cap to model the NanoVNA-H4 rev 4.3 port networks and calculate their input impedance. I used data sheet values for the semiconductor impedances. Port 1 is on the left in the schematic. Blue/red curves are for port 1 and green/brown are for port 2. Even though the AC-coupling filter corners are only a kHz or two, the phase shift they cause extends much higher. I have seen the effect on measurements at a few hundred kHz.
Brian
|
Steve,
I had a similar problem. DFUseDemo was loaded with the Bootloader driver which I use with STM32 CubeProgrammer for my Malahite DSP2 receiver. It uses the bootloader mode to update firmware. Sometimes when I exit it saves the bootloader driver.
To change drivers for the DFU Mode perform the following:
Start DFuSe Demo. If it does not detect any device in DFU mode do the following:
Start the Device Manager
- Under "Universal Serial Bus devices" you should see "STM32 BOOTLOADER"
- right click on "STM32 BOOTLOADER" and select "Update Driver"
- select "Browse my computer for drivers"
- select "Let me pick from a list of available drivers on my computer"
- Under "Select the device driver you want to install for this hardware". Check the "Show compatible hardware" box
- You should see the "STM Device in DFU Mode" and "STM32 Bootloader" drivers.
- Select the "STM Device in DFU Mode" driver.
- Select "Next" and it should display "Windows has successfully updated your drivers" Close this box
- The Device Manager should show:
"Universal Serial Bus Controllers"
"STM Device in DFU Mode"
- DfuSe Demo will detect the device in under DFU Mode.
Mike N2MS
toggle quoted message
Show quoted text
On 03/05/2023 8:45 AM Steve Bowers <bowxyz@...> wrote:
I got to the point of starting DiFUse and also downloaded the latest
firmware.
Following the directions in the beginners guide I started the DFU demo
program and started the nano in DFU mode as instructed.
However all I see in device manager is STM Bootloader and not Nano in DFU
mode under the USB controllers.
Going back to the DFU demo program and selecting the drop down box where I
should be seeing the device, nothing is there.
I double checked to make sure the Nano is being seen in device manager by
cycling the power switch. Turning it off removes it from the device manager
USB ports.
Any ideas?
Steve
|
I got to the point of starting DiFUse and also downloaded the latest firmware. Following the directions in the beginners guide I started the DFU demo program and started the nano in DFU mode as instructed. However all I see in device manager is STM Bootloader and not Nano in DFU mode under the USB controllers. Going back to the DFU demo program and selecting the drop down box where I should be seeing the device, nothing is there. I double checked to make sure the Nano is being seen in device manager by cycling the power switch. Turning it off removes it from the device manager USB ports. Any ideas? Steve On Sat, Mar 4, 2023 at 10:42?PM Steve Bowers via groups.io <bowxyz= [email protected]> wrote: Awesome. Much obliged!
Thanks
Steve
On Mar 4, 2023, at 7:11 PM, robert miles <bob@...> wrote:
?I found the youtube videos by W2AEW on the nanovna to be excellent. He does one on updating the H4 from a dfu file
#320: How to update the NanoVNA-H4 firmware using Windows 10 and .DFU
file ( )
youtu.be ( )
( )
Coupled with the beginners guide supplied by Roger et al it should get you going.
Regards
Bob
GM4CAQ
On 4 Mar 2023, at 8:32 pm, Steve Bowers <bowxyz@...> wrote:
? That¡¯s great! Much obliged!
Thanks
Steve
On Mar 4, 2023, at 12:39 PM, Roger Need via groups.io
<sailtamarack@...> wrote:
?On Sat, Mar 4, 2023 at 09:24 AM, Steve Bowers wrote:
I¡¯m trying but I¡¯m getting some erratic information. I¡¯m sure it¡¯s
user error.
I put a copy of the Absolute Beginner's Guide on my Box account for
you to
download. Download button in upper right hand corner. Here is the
link.
Roger
<hqdefault.jpg>
|
Re: DiSlord build 1.2.19, saved cal files give error when reading
here a copy from test team (only mail not the file)
NanoVNA-H/H4 v1.2.20:
Update SD card code:
- Add block write (allow faster write big amount of data like flash dump)
- Fixed several bugs in work (i hope now lot of card problems solved)
- Update card init procedure
- Less code size
PS not found my NanoVNA-H device (all test made on H4 model), so please test card code on it.
... end copy
so you see diSlord worked on the sd card part .. hopefully solving a few problems
greetz sigi dg9bfc
Am 05.03.2023 um 09:23 schrieb HA3HZ:
toggle quoted message
Show quoted text
Hi Sigi,
You are talking about NanoVNA v2, where 1.3.15 is indeed the latest. In contrast, 1.2.19 is the latest version for H and H4.
|
Re: DiSlord build 1.2.19, saved cal files give error when reading
for half an hour :-)
dislord just uploaded a newer to the test group 1.2.20 for h and h4
dg9bfc sigi
Am 05.03.2023 um 09:23 schrieb HA3HZ:
toggle quoted message
Show quoted text
Hi Sigi,
You are talking about NanoVNA v2, where 1.3.15 is indeed the latest. In contrast, 1.2.19 is the latest version for H and H4.
|
Hi Igor,
if you still need a new display, I recommend this one. In 2020, during an installation, a warm part softened in the middle of the display and left a mark. So I ordered and tested a new display, which works fine.
I received the display shown in the attached picture. I can't find this link, I found this link from the seller:
I hope the ST7796U designation does not make a difference in use.
--
Gyula HA3HZ ( )
|
Re: DiSlord build 1.2.19, saved cal files give error when reading
TheSpud,
I recommend a complete memory wipe before uploading the new firmware.
That will probably help. link:
--
Gyula HA3HZ ( )
|
Re: DiSlord build 1.2.19, saved cal files give error when reading
Hi Sigi,
You are talking about NanoVNA v2, where 1.3.15 is indeed the latest. In contrast, 1.2.19 is the latest version for H and H4.
--
Gyula HA3HZ ( )
|
Re: DiSlord build 1.2.19, saved cal files give error when reading
maybe you saved files without doing a full calibration (SOLT) so there are values missing?
dg9bfc sigi
ps as i have noted .. 1.3.15 is newest
Am 05.03.2023 um 02:27 schrieb TheSpud via groups.io:
toggle quoted message
Show quoted text
Because of the problems with 1.2.14 missing the read from SD menu, I downloaded 1.2.19 and attempted to save my cal files again. They saved without errors, but when I try to read them I get format error.
Please advise what is most recent version that supports writing and reading from the SD card.
Thanks
|
try resetting connectors maybe?? there could be just a bad contact
try both .. the connector between the boards .. and also the flat band cable (loosen clamp on the flatband .. pull out, reseat and tighten clamp)
also a cold solder joint may cause such things (inspect solder spots around the flat cable)
good luck
dg9bfc sigi
Am 04.03.2023 um 17:32 schrieb Igor - PY3IG:
toggle quoted message
Show quoted text
A user has the nanovna H4 with this display defect. Suggestions before switching to a new display?
Igor.
|
Re: DiSlord build 1.2.19, saved cal files give error when reading
Hi Siegfried, I went back to 1.2.0 and am seeing the format error again.
My hardware is 4.3_MS
Where can I find 1.3.15?
Thanks
|
Awesome. Much obliged!
Thanks
Steve
toggle quoted message
Show quoted text
On Mar 4, 2023, at 7:11 PM, robert miles <bob@...> wrote:
?I found the youtube videos by W2AEW on the nanovna to be excellent. He does one on updating the H4 from a dfu file
#320: How to update the NanoVNA-H4 firmware using Windows 10 and .DFU file ( )
youtu.be ( )
( )
Coupled with the beginners guide supplied by Roger et al it should get you going.
Regards
Bob
GM4CAQ
On 4 Mar 2023, at 8:32 pm, Steve Bowers <bowxyz@...> wrote:
? That¡¯s great! Much obliged!
Thanks
Steve
On Mar 4, 2023, at 12:39 PM, Roger Need via groups.io
<sailtamarack@...> wrote:
?On Sat, Mar 4, 2023 at 09:24 AM, Steve Bowers wrote:
I¡¯m trying but I¡¯m getting some erratic information. I¡¯m sure it¡¯s
user error.
I put a copy of the Absolute Beginner's Guide on my Box account for you to
download. Download button in upper right hand corner. Here is the link.
Roger
<hqdefault.jpg>
|
i measured a patch antenna for 13cm with nanovna app and with calibration in the device and in nanovna app and if i compare smith of nanovna app and smith in the unit .. they look quite similar (if not exactly the same) ...
and measure a 13cm circular polarized antenna is not that easy (on 13 cm every adaptor can be seen in smith)
but ...
the unit uses the avg setting on boot that you have saved in slot 0 (first slot)
if you have a low setting there .. then also measure via app is done with a low average number and so calibration is not "smooth" ... (in other words calibration data has noise in it)
you want a high avg number (many measured and averaged points per step) ... then do a calibration (say 5 to 10 runs) ... and save that file
now you can set avg low in slot 0 (say avg2) ... so when using the software scanning goes a bit faster at 400 points per second
avg setting in unit and avg setting in the soft are two different things (averaging in calibration is a third one .. grin)
so what i do is ... at first i do a slow run (high avg setting in device) to search my correction values (others say do a calibration)
after that i set avg lower (to have a faster readout while tuning an antenna or whatever) ...
same thing for calibrating the software
i first save a high avg number in slot 0 (yes then also scanning in the soft is slower!!) .. do the calibration run .. save that file ... reload it (to make it active) ... then save a lower avg number in slot 0 and do my measurements ...
its a bit tricky to understand that (how does avg in the device correspond with avg in soft?!?)
i try an easy example
calibration in device ... avg set to x5 ... say we do 1 meg steps and only a few (just an example!!)
devide does make stepping as follows
1,1,1,1,1,2,2,2,2,2,3,3,3,3,3,4,4,4,4,4,5,5,5,5,5... etc etc (so each point is done 5 times before stepping to next one ... noise is calibrated out that way cause noise is random)
calibration run then also uses 5 values for each point (BEFORE STEPPING TO NEXT!!)
calibration with average in the soft is a bit different
avg in calibration goes (say 5 steps and x5 avg)
12345,12345,12345,12345,12345 (and then save that file after you did those 5 runs with open short and load)
it is different if you measure a value 5 times beore you step to the next ... or if you do 5 times the same 12345 run (and average those 5 runs)
i used easy examples (only 5 steps and not 401) just to show the principle and differences)
no idea if any of you understand all my rubbish hi hi ... but .. i can do NOT find any faults here comparing nano app ... and the device itself
IF I DO THE CALIBRATION CORRECT WAY!!! (means above procedure ... use high avg IN THE UNIT first .. save file, activate and then go from there)
only v2plus4 is a bit different ... even with lower avg number it is not as noisy cause the averaging is done in the bootloader and not in main fw
(dislord may better explain how all these things interact and i do not know how it is done in the newer lite vna or other newer units)
dg9bfc sigi
Am 04.03.2023 um 04:42 schrieb Roger Need via groups.io:
toggle quoted message
Show quoted text
On Fri, Mar 3, 2023 at 05:54 PM, Siegfried Jackstien wrote:
if you calibrate the cable out then all should show near similar results
.. not??
measure without cable calibration can not work good so question is ...
did you calibrate out that 3m cable??
if calibrated (and calibration IS LOADED ALSO!!) then nanovna_app shows
near perfect results compared to internal calibration
only slight variations depending how high you have set averaging in the
device
higher average gives smoother curves but also a more exact calibration ...
dg9bfc sigi
This was a comparison of how well each one calibrated the same cable and measured a 1K DUT. A new calibration using the same cal loads was done at the end of the 3M cable for each test and then they were compared. The results for NanoVNA App, NanoVNA Saver and Standalone VNA should all be very close because they all are all calibrated the same and used the same 1K SMD resistor as the DUT. Averaging was not used in these tests - just one sweep.
The standalone NanoVNA-H4 and NanoVNA Saver gave very similar results. NanoVNA did NOT do well. As "btomek" pointed out in hos first post there is something wrong with the NanoVNA App calibration algorithm.
Try it your self and see what you get and post your results...
Roger
|
Re: DiSlord build 1.2.19, saved cal files give error when reading
1.3.15 is most actual
(what hw you have??)
dg9bfc sigi
Am 05.03.2023 um 02:27 schrieb TheSpud via groups.io:
toggle quoted message
Show quoted text
Because of the problems with 1.2.14 missing the read from SD menu, I downloaded 1.2.19 and attempted to save my cal files again. They saved without errors, but when I try to read them I get format error.
Please advise what is most recent version that supports writing and reading from the SD card.
Thanks
|
DiSlord build 1.2.19, saved cal files give error when reading
Because of the problems with 1.2.14 missing the read from SD menu, I downloaded 1.2.19 and attempted to save my cal files again. They saved without errors, but when I try to read them I get format error.
Please advise what is most recent version that supports writing and reading from the SD card.
Thanks
|
I found the youtube videos by W2AEW on the nanovna to be excellent. ?He does one on updating the H4 from a dfu file
#320: How to update the NanoVNA-H4 firmware using Windows 10 and .DFU file ( )
youtu.be ( )
( )
Coupled with the beginners guide supplied by Roger et al it should get you going.
Regards
Bob
GM4CAQ
toggle quoted message
Show quoted text
On 4 Mar 2023, at 8:32 pm, Steve Bowers <bowxyz@...> wrote:
? That¡¯s great! ?Much obliged!
Thanks
Steve
On Mar 4, 2023, at 12:39 PM, Roger Need via groups.io
<sailtamarack@...> wrote:
?On Sat, Mar ?4, 2023 at 09:24 AM, Steve Bowers wrote:
I¡¯m trying but I¡¯m getting some erratic information. ?I¡¯m sure it¡¯s
user error.
I put a copy of the Absolute Beginner's Guide on my Box account for you to
download. ?Download button in upper right hand corner. ?Here is the link.
Roger
|
I have determined that the problem is with the nanoVNA device. It will not
communicate with any of my PCs. I have two with Windows 10 and one with
Windows 7. The nanoVNA works well as stand alone, but will not communicate
with a computer.
Thanks to all for the help that you have been!!
David
toggle quoted message
Show quoted text
On Thu, Mar 2, 2023 at 2:46?PM robert miles <bob@...> wrote: Hi david
I am not at home right now so not near my laptop but this might help?
On 2 Mar 2023, at 4:44 pm, David Reams <dwr.kj4de@...> wrote:
???It looks like it is conflicting with another port. Below is what I am
seeing on my laptop:
[image: image.png]
[image: image.png]
It appears that it is trying to conflict with Port 3. What is the best way
to solve the port contradiction?
Again, thanks for your help!!!
David
On Wed, Mar 1, 2023 at 4:36?€?AM robert miles <bob@...> wrote:
Hi David
If you right click on the STM Device in dfu mode and select properties.
Go to update driver.
Browse to the install directory for the STM software ( prob in programs
x86) and press enter.
That should fix it.
Other thing to check is that the com port assigned to the STM USB driver
is correct and not clashing with another in device manager.
Worked for me with W10 on 64 bit machine.
On 1 Mar 2023, at 12:35 am, David Reams <dwr.kj4de@...> wrote: ???I am still unable to get the nanoVNA to assign a port. I have
Windows 10
and the nanoVNA will not automatically assign a port and the program
suggested above does not assign a port. When I place the nanoVNA in DFU
mode it does show "STM Device in DFU Mode". under Universal Serial bus
Controllers. Otherwise it shows "Unknown device" if not in DFU mode. No
port assignment is indicated at all. I might be having a problem with
the nanoVNA equipment itself. When not connected to a PC, the device works
fine.
Maybe this problem can be solved, but if there is, in fact, a problem with
the device, no solution would be forthcoming.
Again, thanks for all of your help!!
David
.
On Tue, Feb 28, 2023 at 1:31?€?PM Roger Need via groups.io
<sailtamarack=
[email protected]> wrote:
On Mon, Feb 27, 2023 at 06:33 PM, David Reams wrote:
Can you give me some more information on the STM boot loader and a source to
download?
David,
There are two different drivers required when using a NanoVNA-H or
NanoVNA-H4. One is required to get a COMxx: port so that your PC can
exchange data with a NanoVNA. The other driver is required when you
want
to do firmware updates on your device.
COM port driver
---------------------
With Windows 10 and Windows 11 the required driver will be installed
by
Windows when you connect your NanoVNA to a USB port. With Windows 7
and
Windows 8 you have to manually install the driver and then plug in
your
NanoVNA. If Windows 10 fails to install the driver (rarely happens)
you
can use the Windows 8 driver. You can check that the driver is
working
by
plugging in and turning on your NanoVNA and then going into Device
Manager
and looking under ports to get the COM port number that has been
assigned
If you power off the NanoVNA the COM port should disappear from Device
Manager. I have put a copy of the drivers on my BOX account for you
to
download. Here is a link where you can download it >>
Unzip and select the 32 or 64 bit version for your computer.
Firmware Upgrade driver
---------------------------------
This driver is only required when you want to upgrade your firmware.
It
does not assign a COM port when the NanoVNA is plugged in and in DFU
mode.
DFU mode is activated in different ways depending on your device and
the
firmware installed. Old devices had to be put in DFU mode by opening
the
case and shorting the Boot0 and DFU pins. In other cases DFU was
accessed
by a Menu selection. DFU mode on the -H4 is activated by depressing
the
rocker switch down and powering on the anoVNA. When in DFU mode the
screen
will be black. You can check that the driver is installed correctly
by
looking under USB controllers and seeing if it shows that your device
is in
DFU mode (see attached screenshot). I have posted a link to the DfuSe
package on my Box account for you. It will install the DFU driver and
the
DfuSe firmware upgrade application.
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.pdf
You don't have to register to get the DFU program and drivers. I have
put
a copy on my Box account for you...
Roger
<image.png>
<image.png>
|
HA3HZ
