On Mon, Mar 6, 2023 at 07:25 AM, N2MS wrote: My version of STMicroelectronics DfuSeDemo does not show a driver for Windows
11.
I would check to see if STMicroelectronics has a driver d=for Windows 11 for
DfuSeDemo. I don't know if they still support DfuSeDemo.
The Windows 10 driver works in Windows 11 Roger
|
Steve,
My version of STMicroelectronics DfuSeDemo does not show a driver for Windows 11.
I would check to see if STMicroelectronics has a driver d=for Windows 11 for DfuSeDemo. I don't know if they still support DfuSeDemo.
Mike N2MS
|
64 bit system and loaded 32 bit dfu tools, so no compat driver?
toggle quoted message
Show quoted text
On March 5, 2023 8:33:54 PM CST, Steve Bowers <bowxyz@...> wrote: Hmm. That file is there but when I point to it, windows 11 says it¡¯s a non compatible file and if I choose to use it the system mdt become unstable. I chose it anyway and the when going back to the update driver process, the dfu mode still does not show up as an option.
Thanks
Steve
On Mar 5, 2023, at 8:49 PM, Geoff Peters - AB6BT <AB6BT@...> wrote:
?C:\Program Files (x86)\STMicroelectronics\Software\DfuSe v3.0.6\Bin\Driver\Win10\x64\STTub30.sys
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
Well, It may be related to Windows 11 and I have only Windows 10 machines.
Sorry I can't be of more help.
|
Hmm. That file is there but when I point to it, windows 11 says it¡¯s a non compatible file and if I choose to use it the system mdt become unstable. I chose it anyway and the when going back to the update driver process, the dfu mode still does not show up as an option.
Thanks
Steve
toggle quoted message
Show quoted text
On Mar 5, 2023, at 8:49 PM, Geoff Peters - AB6BT <AB6BT@...> wrote:
?C:\Program Files (x86)\STMicroelectronics\Software\DfuSe v3.0.6\Bin\Driver\Win10\x64\STTub30.sys
|
C:\Program Files (x86)\STMicroelectronics\Software\DfuSe v3.0.6\Bin\Driver\Win10\x64\STTub30.sys
|
I have Windows 11 pro so maybe that¡¯s the problem.
What is the actual name of the file?
Thanks
Steve
toggle quoted message
Show quoted text
On Mar 5, 2023, at 5:36 PM, Geoff Peters - AB6BT <AB6BT@...> wrote:
?For WIndows 10, in here:
C:\Program Files (x86)\STMicroelectronics\Software\DfuSe v3.0.6\Bin\Driver\Win10
|
OneOfEleven developed the NanoVNA App for personal use and after moving on to other projects kindly posted it as open source for the community to use and modify. Owen Duffy has created a fork of the OneOfEleven App and corrected some of the errors in the program especially on the info sidebar. I assume that he is reading (but unfortunately not posting) this thread because he has written a 3 part informative blog post on calibration in the NanoVNA App. Readers interested in this topic can use these links:
Part 1 -
Part 2 -
Part 3 -
In his discussion he shows that straight line interpolation can result in worse errors than using Cubic spline interpolation. The latter is used in NanoVNA App. He also states that when operating over a wide frequency band that more scan points is better.
With that in mind I did some more tests using a NanoVNA-H4 in standalone mode and with NanoVNA App OD12 and version 5.4 of NanoVNA Saver.
Calibration conditions
-----------------------------
1. In all cases the SOL was done at the end of 3M of RG-316 coaxial cable fitted with SMA male connectors on both ends. A SMA female was used with a pin header to do the SOL calibration. A 50 ohm 0805 SMD resistor was used as one of the cal loads. See attached photo. Sweep range was 50 kHz. to 900 MHz.
2. The NanoVNA was calibrated on the device using 401 scan points with the default bandwidth setting.
3. NanoVNA Saver was configured to use 401 scan points with 5 averaged sweeps for the calibration.
4. NanoVNA App OD12 was calibrated with 401 and 3201 scan points to see if more scan points made a difference. 8 traces were time averaged and trace smoothing set to 3.
Test Conditions
--------------------
A 75 ohm 0805 SMD resistor was used as the DUT and swept over the 50 kHz. to 900 MHZ. range. Note that interpolation was NOT required/used and scan point frequencies were the same as that done for calibration.
The NanoVNA Saver and NanoVNA Standalone DUT measurements were exported as a Touchstone s1p files and imported into NanoVNA app for comparison. The results are attached.
Observations
------------------
NanoVNA standalone and NanoVNA Saver both gave results that are consistent with what is expected for this DUT. NanoVNA app had a downward trend (for 401 and 3201 scanpoints) after 200 MHz. which is not correct.
Conclusions
----------------
My suspicion is that something is wrong with the implementation of the cubic spline interpolation in NanoVNA App. Perhaps DiSlord or Owen Duffy will consider adding linear interpolation as an option and removing or fixing the cubic spline interpolation.
Roger
|
For WIndows 10, in here:
C:\Program Files (x86)\STMicroelectronics\Software\DfuSe v3.0.6\Bin\Driver\Win10
|
On Sun, Mar 5, 2023 at 11:56 AM, <btomek@...> wrote:
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?
The calibration algorithm takes a bit of effort to understand. It was discussed in a previous series of posts. /g/nanovna-users/topic/68975032?p=Created%2C%2C%2C20%2C1%2C0%2C0There is also a paper by Rytting that describes the one port SOL calibration. You need to solve 3 equations with 3 unknowns and then use the error terms to adjust the measured gamma to get the actual gamma. Roger
|
Re: DiSlord build 1.2.19, saved cal files give error when reading
Hi Sigi, I have identified the problem. I was naming my saved files as XX-METER, for easy identification. But recalls always failed. So I tried saving the file as XXMETER, with no dash, and it worked. So somehow the parsing of the file name didn't like the dash.
HTH
TheSpud
|
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 ( )
|
Roger Need
HA3HZ
