Re: NanoVNA-App 1.1.207 crashes , 1.1.206 does not
the mem_0 is a file that is filled when live sweeping...
when the program starts it looks for this file, as the curve from last measurement comes up.. ( I think :-) )
i see this, because data in this file, is exact the last saved data from the last measurement...
probably this is a bug, that it can not start with empty data...
here is the file in annex
suc6 with it
|
Re: NanoVNA-App 1.1.207 crashes , 1.1.206 does not
Hi Jemp,
I've had the same issue with the error noted and have looked for the file <mem_0.s2p> you mentioned in , but I don't see it listed.
Out of curiosity I copied mem_1.s2p and renamed it. The program load ok now, but I don't know what the effects are to the operation of the VNA.
Comments?
Rich
|
I have a USB 3 on the PC that has an 8 port hub plugged into it, I can't use that hub it won't see the VNA. Now plugged into that hub I have a unit that has 2 USB 3s, 2 other USB and 2 slots for inserting disc drives. I can use the USB 3s on this unit with no problems, even though I can't get a connection using the hub it is plugged into!!??
Rhys
GW0DIV
|
Hello All,
I am new to the group and ended up here as I had major problem upgrading the firmware in my NanoVNA-H. I may have missed a crucial piece of info in my approach (please flag it up if I have!) but now I want to share my solution how it worked for me. I had the same issue of previous members with DefuSeDemo not recognising the VNA in Windows10, first off-the supplied USB cable does not work but you do get the message on windows stating a device has malfunctioned giving you the impression it's not just a charging lead, change the lead first! So I went down the Zadic route of installing the drivers which got me further to the point of 'STM32 BOOTLOADER' now showing in device manager under 'USB Devices' but I could not get it to show "STM device in DFU mode" in device manager even though the VNA was definitely in this state. I could not get past this stage no matter what I tried so I gave up on DefuSeDemo and tried STM32CubeProgrammer loading the v1.0.4.5 bin version (changing from V0.4.5.1), and it worked immediately, no issues! Hope this helps someone else.
|
Re: NanoVNA-App 1.1.207 crashes , 1.1.206 does not
Tnx for all reply's.. real Ham Spirit
Found the solution.. error comes from not finding mem_0.s2p file
Most likely a small bug in searching and needing it
So copy this file from the github into any folder with, the exe file and it will work..
Try it and give feedback.
Jemp
|
Re: NanoVNA-App 1.1.207 crashes , 1.1.206 does not
Please read the notes in the forum's Wiki for this app.
toggle quoted message
Show quoted text
On Wednesday, September 8, 2021, 06:27:38 a.m. EDT, Jempi ( ON7MA ) <on7ma@...> wrote:
Dear VNA Users
I downloaded new nanaVNA-App from OneOfEleven, 1.1.207.. from which I believe it is a superb program..( for me the best and nicest , since I use it from the earliest versions )
I see that it crashes immediately.. ( uses on W10-x64 ), see picture? , access violation...
Should there be any special recommendations about it or solution ?
Tnx for any help or support..?
Jemp
|
Re: NanoVNA-App 1.1.207 crashes , 1.1.206 does not
There's a known problem with that version.
(Google for the thread)
Use 1.1.206 instead.
Mike
------------------------------------------------------------------------
*From:* Jempi ( ON7MA ) [mailto:on7ma@...]
*Sent:* Wednesday, 8 September 2021, 11:27 am
*Subject:* [nanovna-users] NanoVNA-App 1.1.207 crashes , 1.1.206 does not
toggle quoted message
Show quoted text
Dear VNA Users
I downloaded new nanaVNA-App from OneOfEleven, 1.1.207.. from which I believe it is a superb program..( for me the best and nicest , since I use it from the earliest versions )
I see that it crashes immediately.. ( uses on W10-x64 ), see picture , access violation...
Should there be any special recommendations about it or solution ?
Tnx for any help or support..
Jemp
|
NanoVNA-App 1.1.207 crashes , 1.1.206 does not
Dear VNA Users
I downloaded new nanaVNA-App from OneOfEleven, 1.1.207.. from which I believe it is a superb program..( for me the best and nicest , since I use it from the earliest versions )
I see that it crashes immediately.. ( uses on W10-x64 ), see picture , access violation...
Should there be any special recommendations about it or solution ?
Tnx for any help or support..
Jemp
|
Hello Group.
I have a question about the origin of the interference on the frequency 585.018MHz. Is it possible to do something about it, for example by adding a capacitor somewhere on the PCB, replacing a component, or some other way. On two different H4s this interference is present, but on one it is much weaker (dev1), not disturbing, and on the other it is visible (dev2).
Changing the 300MHz to 280MHz threshold does not affect this interference.
FW: DiSlord 1.0.69
Calibration NOT apply.
Open S11, and Open S21
Thanks in advance.
|
It looks like there is a problem with the USB connection or the MCU is not entering DFU mode correctly, can I see a picture of the inside of the NanoVNA?
|
Sigh....
I tried to uninstall and reinstall it sven different ways to sunday but no luck. The reply I keep getting is the driver I have is the best.
|
Re: Sweep and stimulus timing
I not see big difference in speed for fixed PLL or fixed div mode.
But for NanoVNA faster fixed PLL mode:
- in this mode possible use one PLL for generate freq and freq + offset and second PLL for generate clock foor AIC codec, for one point need only update two channel dividers
For fixed divider need update both PLL and one channel divider for AIC codec, more slow.
Most fast work in < 100 MHz range (used fixed PLL mode)
Lock time in less then 200us (~100 us for fixed PLL, and ~160us for fixed DIV mode)
Measure in 4k BW need 48 samples on 192k ADC speed, drop next 48 samples for switch to another channel and measure next 48 samples (144 samples for one point) and need time for set frequency and wait lock (another 48 or 96 samples drop) so yes for measure one point need ~1.25ms
For screen update need ~30-70ms
|
Re: Sweep and stimulus timing
Thanks for posting the two images. If I understand the Si5351A clock generator, there could be two different cases.
In the case of no change in PLL frequency, only the Multisynth Divider would be used and the frequency change would be very fast. The datasheet advertises "Glitchless frequency changes" on page 1.
If the PLL frequency needed to be changed during a sweep, I believe the lock time could be close to a millisecond or longer. That would not be a problem but it would be noticeable with each data point requiring only a few milliseconds.
73, Kent
AA6P
|
The SMA jack cal kit and test connector shown by Roger is going to be much better than the other jigs IMO. If anyone does want to make one I'd recommend trying to buy the connectors as branded parts from a decent supplier. I'd avoid searching for the cheapest ones from the far east via ebay. There might not be much advantage in performance but these connectors will be used a lot possibly for a few years so I'd recommend getting something with accurate machining and decent materials so it doesn't cause premature wear in other SMA cables or adaptors.
I've got various SMA based cal kits here and my earliest one that I still use for casual stuff is over 15 years old. I'd favour buying the chunkier end launch ones made by Suhner or Johnson but these are a bit more expensive. They are much nicer to use for dev work and I buy them regularly. Usually 25 at a time for a decent discount.
|
On Tue, Sep 7, 2021 at 10:14 AM, Donald S Brant Jr wrote:
I have made such standards in the past and have found that using 3 x 150¦¸ or
4 x 200¦¸ resistors makes a significantly-better load that a single 49.9¦¸
one, likely due to paralleling the resistors' inductances.
73, Don N2VGU. Yes using more than one resistor for the load gives better results. I got the idea for doing this from an article posted online. He shows performance with SMA male and female parts. Roger
|
Albert, Looking at the jigs, I don't understand the benefit of using Manfred's, since
it has large areas of plane on both conductors. Doesn't that introduce more
parasitic capacitance than Roger's small jumper pin fixture?
The benefit is simply that one can easily and quickly clamp components of vastly different sizes to it. And the downside is that measurement accuracy is worsened by the uncertainty of where exactly on the planes each component terminal makes contact. So I would not use this jig to measure the stray inductance of an SMD resistor, for example. The result might be too imprecise. A jig like Roger's is better for that task, as it gives far better reproducibility of the parasitic reactances and resistances. But while Roger is still soldering his parts to his connectors, I have already finished the measuremnts! That's the advantage of mine: Speed and convenience. If you want the best flexibility, simply build both! They are easy and cheap enough to make. Don't worry about the capacitance between the two contact areas of my jig. It's single-sided board, so the capacitance is probably less than 1pF, and the NanoVNA's calibration totally takes care of it. And the large planes help in reducing the series inductance, which is what varies most when clamping a component to different spots of the planes. I'm using my jig a lot, and haven't seen a need to build another so far. But of course I'm very aware that it has its limitations. Mainly an uncertainty of about 2nH due to different contact spots of the shorting strap and the component under test. And when just clamping the parts to the jig, there is also a variable resistance there, so for critical ESR measurements it's better to solder down the parts (and alos the calibrators, of course). Note that my jig gives the choice between clamping and soldering, at all times! Hmm, I'm getting good at advertising! ;-)
|
I have made such standards in the past and have found that using 3 x 150¦¸ or 4 x 200¦¸ resistors makes a significantly-better load that a single 49.9¦¸ one, likely due to paralleling the resistors' inductances.
Extending the outer conductor on the open standard with a piece of brass tubing also improves its performance by minimizing its radiation; the tube is essentially a waveguide below cutoff. This is only apparent at X-band and above.
73, Don N2VGU.
|
This is a reply to all of the respondents:
I learn all the time from from posts like these. The interactions of these most learned of people always amaze me and is reminiscent of the nearly 40 years I spent in aerospace where sages of all disciplines would combine to create solutions that might seem impossible were it not that they really work.
One of my problems is that I know enough to be dangerous to myself and others and I learn this on a daily basis. I say all this because this topic is a perfect example in which I want to learn but my limited knowledge of certain electro-physical phenomena comes to an end. Various references (i.e., classic texts) to these phenomena are practically (physically/financially) out-of-reach, so, I carefully tease knowledge from what people like Roger, Don, Manfred, et al., spill out onto to these posts.
For example, "I think" I intuitively (or entertain the illusion that) understand the reason that the planes of Manfred's circuit board jig have little parasitic effect at certain (most) frequencies but I would not be able to supply the proof. (That was always my problem in advanced topics in calculus.)
A common problem is sometimes I get lost in "lingo" or what to you all is common terminology and need to resort to the vast "knowledge" of the internet. (Uggh!)
Anyway, I'm whining and the real purpose of my post is to thank you all for sharing your knowledge as I have seldom seen anything so practical in academic circles and you all expound on topics of a clearly useful purpose which supplies me with many "Aha!" moments.
So, thanks again, as this has been a highly useful and informative topic for me and has likely explained some problems I've had measuring components.
Will
W6SWF
|
This is another method I use to test components when I am interested in higher frequencies and/or improved accuracy. It gives a better reference plane than the SMA pin jack method and is also useful when you want to establish the reference plane at the end of a SMA cable for other types of measurements.
Four SMA PCB mount jacks are required. The legs and and the centre pin are removed on three of them to make open short and cal loads. On the open you cut the centre pin flush with the dielectric and then use a dremmel tool to remove a bit more - this reduces fringing capacitance. For the short you take a piece of copper foil slightly smaller than the bottom surface area of the jack. Push it over the centre pin and then solder the entire bottom area to the metal surface of the jack. Then clip off the excess center pin. For the load I used a 49.9 ohm 0805 SMD resistor that I had in the parts bin. I used my DE-5000 LCR meter with Kelvin clips to handpick one that was as close to 50 ohms as possible. Two 100 ohm SMD resistors would be slightly better if you have them available.
The fourth jack is used for the component under test. It can be a leaded component or an SMD part. I remove all the legs but one. Shorten the remaining leg and the center pin to reduce inductance and then tack solder the component to the centre pin and leg. Connect it to the cable and make your measurement.
Roger
|
In my case I had to actually go to the mentioned folder and install the "STM device in DFU mode" as it did not appear as one of the choices of available drivers.
Hope it works for you...let us know. Apparently this problem is not uncommon as the correct driver installs automatically for some but not others.
Thanks again to Don KB5QR who's post helped me out.
73, Dave - W3NP
toggle quoted message
Show quoted text
On 9/7/2021 12:00 PM, Andy-kf7vol wrote: That's what I needed. I will give that a try when I get home tonight.
Thanks, Dave!
On Tue, Sep 7, 2021 at 8:57 AM Dave W3NP <w3np@...> wrote:
I had the same or similar problem last week when upgrading my H4. It
was a driver problem. Windows kept loading the STM32 Bootloader driver
and I needed the "STM device in DFU mode" driver ......I found this post
by Don KB5QR and it got me on the right road:
/"I ran into the same problem with Windows 10 not seeing my NanoVNA in
DFU mode. I found the fix via a Google search that led me to forum on
www.deviationtx.com. One of the members by the handle of "Nuggetz"
suggested that the driver in use was not the DFU version. This is what
he did, and it worked for me:
Connect the NanoVNA and put it in DFU mode. Go into device manager and
find the STM device under "Universal Serial Bus devices" (at the very
bottom of the window). Expand this item and you will probably see "Hub
Controller" and "STM32 BOOTLOADER". Right Click on "STM32 BOOTLOADER"
and select update driver then choose "Browse my computer for drivers".
After that, select "Let me pick from a list of available drivers on my
computer".
The driver choices you see there should include "STM device in DFU
mode". Select the DFU mode one and that'll do it.
If you don't see both "STM32 BOOTLOADER" and "STM device in DFU mode",
/_*then you probably need to install the driver using the
dpinst_amd64.exe utility, found in the Win10 folder under Program
Files(x86)/STMicroelectronics/Software/DfuSe v3.0.6/Bin/Driver.*_/
/ /
Hope this Helps.
73,
/
/Don, KB5QR"/
/
/
I was able to complete the upgrade without any further issues. Thanks
Don!!!
73, Dave - W3NP
On 9/7/2021 11:16 AM, Andy-kf7vol wrote:
Good Morning,
I didn't make any driver change after having a success story updating my H model. When I plug in the H4 and hold the button down and power on to DFU
mode it still is not recognized.
|
Jempi ( ON7MA )
Roger Need
Donald S Brant Jr
2sheds
