开云体育

Interesting: Does the use of the ADF4350 mean the minimum frequency will be 137MHz+? Or do you have plans for handling that? Are you and your project associated to edy555/ttrftech, to hugen, or to

Forgot to mention...the 85050B’s calculation were for 1500 MHz (corrected this -- I'd originally typed 900 MHz) - Jeff

This post is somewhat off topic but I am so happy with what I achieved I felt I earned some bragging rights For those that need a nanoVNA V2 for tuning their 2GHz antennas there is no real reason to

Steve, That's good information. Some Linux user's with bricked devices may not have been aware that a Windows PC might be able to recognize the device (if they still had a Windows PC available) and

reply to kb3cs That's certainly annoying. I'd like to have a reference for where these regulations abide. Do you have it handy? thanx W5VZB

On Sun, Sep 29, 2019 at 04:16 AM, Kurt Poulsen wrote: Hi Kurt, Thanks for the reply. > > My humble opinion is like your indications that L and C coefficient are not > relevant for the calibration kit

I finally got mine unbricked using "conventional" methods. Here's the story: 1) Used ubuntu dfu-tool to load CLEAR_MEMORY_DFU.dfu . That left the NanoVNA white screened. 2) Tried to use dfu-tool to

Steve, The following is what another user wrote: // Begin Quote // There are two ways to update firmware: DFU and ST-LINK. So, it depends on what method you're want to use. 1) DFU update. This is

It's alive ! For anyone patient enough to be following this, here's what happened and what fixed it: 1) Used ubuntu dfu-tool to load CLEAR_MEMORY_DFU.dfu . That left the NanoVNA white screened. 2)

Mine using Kapersky Antivirus have a same problem with hanging black screen after execute the program. Then turn off protection for a while, voila.. it running flawlessly. Regards

Hi Dave, You are probably right. I chose this kit because, of the 50-ohm cal-kits listed by Keysight as supported for the 8753D, it seemed to have the worst higher-order capacitance terms, thus a good

Hi Jim, You are essentially correct, but I was thinking more of Rune's Nanovna-Saver application (which allows the user to specify C0-C3, L0-L3, and delays for the two) rather than the NanoVNA,

I don’t see any document they have provided - plenty of links to other tools, but I am still at a loss of knowing much about what they are actually doing. or tools (for sure have no plans to install

Did you succeed in getting your NanoVNA unbricked with ST-LINK ? I'm in the same boat. Before throwing good money after bad, I would like to hear from folks who have successfully used ST-LINK to

However the NanoVNA has already a build in correction for the open in the That is acceptable if your DUT has a male SMA connector, but it is not if you wish to use any other sort of connector. That is

Yes

Sorry to be such a PITA, but at this point I'm nervous about bricking it... When I select your white.dfu, then press Upload, I get this message box: Your device was plugged in DFU mode. So the DFU

Last firmware 29.09.2019

Install the program, the device should be detected (switch the jumper to boot mode again). Indicate the path to the firmware and flash.

Making progress. This time, with jumper, Windows installed the driver and it now shows in device manager. I am intentionally not touching anything until I get the next step from you. I have downloaded