Thank you, Roger.
73,
Gary
toggle quoted message
Show quoted text
At 11:55 AM 3/7/2023, you wrote: On Mon, Mar 6, 2023 at 05:44 PM, Gary - W6GVS wrote:
Exactly where is the file you mention below? I've been unable to
locate it. Thanks.
73,
Gary - W6GVS
At 02:56 PM 3/5/2023, you wrote:
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?
Attached to this message...
Roger
|
On Mon, Mar 6, 2023 at 05:44 PM, Gary - W6GVS wrote:
Exactly where is the file you mention below? I've been unable to
locate it. Thanks.
73,
Gary - W6GVS
At 02:56 PM 3/5/2023, you wrote:
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?
Attached to this message... Roger
|
Yes. Otherwise how would it get the firmware updated.
Thanks
Steve
toggle quoted message
Show quoted text
On Mar 6, 2023, at 7:40 PM, Geoff Peters - AB6BT <AB6BT@...> wrote:
?Hi Steve,
Sorry that doesn't work for you. Are you doing this with the device connected?
Perhaps someone else has an idea...
|
Exactly where is the file you mention below? I've been unable to locate it. Thanks.
73,
Gary - W6GVS
toggle quoted message
Show quoted text
At 02:56 PM 3/5/2023, you wrote: 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?
|
Hi Steve,
Sorry that doesn't work for you. Are you doing this with the device connected?
Perhaps someone else has an idea...
|
Geoff Peters. I have that file but when I follow the instructions, heres what I get. It in the path you listed. On Sun, 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
|
Sorry Steve, I do not know anything about updating the nano. I just use mine as it was sent to me.
Larry? N8CWU
toggle quoted message
Show quoted text
On 3/5/2023 3:38 PM, Steve Bowers wrote: 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.
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
|
Thanks.? More power to nanovna. On Sat, Mar 4, 2023 at 11:15?AM Chris Gardner via groups.io <seaman98= [email protected]> wrote: No problem, enjoy your H4!
On Mar 4, 2023, at 11:17, Steve Bowers <bowxyz@...> wrote:
?Awesome!! Much obliged!!!
Thanks
Steve
On Mar 4, 2023, at 10:57 AM, Chris Gardner via groups.io <seaman98= [email protected]> wrote:
?Greetings, May I suggest that you obtain a copy of this document
(Absolute Beginners Guide). I am sure you will find the information there.
Log In (
/g/nanovna-users/files/Absolute%20Beginner%20Guide%20to%20The%20NanoVNA/Absolute_Beginner_Guide_NanoVNA_v1_5.pdf
)
groups.io (
/g/nanovna-users/files/Absolute%20Beginner%20Guide%20to%20The%20NanoVNA/Absolute_Beginner_Guide_NanoVNA_v1_5.pdf
)
apple-icon-180x180.png (
/g/nanovna-users/files/Absolute%20Beginner%20Guide%20to%20The%20NanoVNA/Absolute_Beginner_Guide_NanoVNA_v1_5.pdf
)
(
/g/nanovna-users/files/Absolute%20Beginner%20Guide%20to%20The%20NanoVNA/Absolute_Beginner_Guide_NanoVNA_v1_5.pdf
)
73¡¯²õ
On Mar 4, 2023, at 09:25, bowxyz@... wrote:
? Help. Newly purchased Nano VNA H4 March 2, 2023.
I've read several posts on the H4 model about firmware and each mention
identifying the proper version and the URL that is listed. Mine does
not
have a URL listed. Version is 1.1.01 [p:401, IF20k, ADC:384k,
Lcd480x320.
Build Time Dec 30, 2021.
I'm sure there are probably newer versions but I am unsure as to the
process to properly update.
Any help would be greatly appreciated.
<apple-icon-180x180.png>
|
The last I looked, support for DfuSeDemo had been dropped in favor of StmCube, which, fortunately, supports far more platforms.
toggle quoted message
Show quoted text
On March 6, 2023 9:25:53 AM CST, N2MS <mstangelo@...> wrote: 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
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
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
|
Roger Need
Larry Krist - N8CWU
