开云体育

Ooops, I meant v1.1.208

Please read the updated notes in the Wiki for the Nanovna-App application regarding installation.

Thanks - It solved the access violation error problem.
I'll update the forum's Wiki to release 1.1.108

Cheers,Larry

I've fixed the bug - hopefully.

They may not be Teflon.

<>
Virus-free.
www.avast.com
<>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Wed, Sep 8, 2021 at 11:24 AM va3rr via groups.io <va3rr=
[email protected]> wrote:

Sage advice.

I bought some BNC connectors on Aliexpress to make some calibration loads
for FA-VA5. I've never seen 'teflon' connectors melt so quickly - lol

On Tue, Sep 7, 2021 at 03:52 PM, jmr wrote:

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.

Sage advice.

I bought some BNC connectors on Aliexpress to make some calibration loads for FA-VA5. I've never seen 'teflon' connectors melt so quickly - lol

Marc,

Seems like I am definitely not alone on this. I have tried the DFU process and have had success with tother VNA so I know it works and am familiar with using it. The other methods, Zadic and STM32CubeProgramer I have never tried.

Do you have any reference material on what that process looks like and where that can be found?
If I can wrap my head around that I will give it a try tonight.

Thanks for everyone's help in this
Andy

Hugen,

I will work to get that tonight when I get back.

Thanks,

Thanks, Roger. Very interesting. I have been using your pin socket jig a lot and have obtained good results also.

Albert

Thanks, Manfred.

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

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.

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

Please read the notes in the forum's Wiki for this app.

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

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.