开云体育

Hello everyone, I have a nano VNA that is now refusing to read correctly after calibration it seems. After running a one port calibration using the calibration assistant, using the supplied open,

Before I screw up my Nano, I was wanting to know if you load the wrong version of FW into say H4 that was written for the H, first can you, and if so can you reverse it back to the correct FW? Gary

Reg, All of DiSlord's firmware for the H4 supports 50, 101 and 201 points. He uploaded his last release a few days ago - search his name and you'll find it. It also has a nicer menu now.? ... Larry

Hi Enrique, NanoVNA-Saver 3.6 runs well on Windows 10 64 bit, at least for me, you can download it here : https://github.com/NanoVNA-Saver/nanovna-saver/releases Jos Op 15-7-2020 om 01:52 schreef

I've got a black 2.8" clone and a recent Hugen H-4 from R&L Electronics. I suspect that the STM32F103 version can't do more than 101 points except via a PC, but it seems to me the STM32F303 version

The lid is in the picture to the right of the base and NanoVNA. I keep the case and accessories in a canvas zipper bag with allows for additional adapters for different kinds on cables you may come

Seems to me it needs a lid and space for the cables, cal kit, adapters, etc. Of course *which* adapters is a very loaded question. For the moment the very nice box it came in will do for me.

Rees, At 1dB/div, a REFERENCE POSITION value of 14 puts a -10dB response at mid-screen. Is that what you are looking for, or do you want a more intuitive entry method? --John Gord

Hi Developper Team, Since a week I have a NanoVna-H4 with SW version 0.5.0 It is a nice instrument for investigation of someone's designs. After playing with the possibilities of this instrument I

Try NanoVNA-Saver 0.2.2-1, as far as I know it is 32 bit and an exe is available for windows. It works when the newer versions won't. https://github.com/NanoVNA-Saver/nanovna-saver/releases/tag/v0.2.2

Hello, I need help. I have a NanoVNA-H which goes to 900 MHZ which I purchased from GigaParts . I ordered that to use while waiting for my NanoVNA V2 from Tindie which should arrive very soon. As

https://go.teledynelecroy.com/l/48392/2020-05-15/7yfrt2?utm_source=linkedin&utm_medium=linkedin&utm_campaign=20-07-16+Bogatin+Sparam+Masterclass+Part+1+

Phil, The connector is obviously defective and the unit is new, ask the seller to replace it - can't hurt to try.? ... Larry On Fri, 17 Jul 2020 at 3:51 PM, p01lindsey@...<p01lindsey@...>

Larry, thanks for the lead. After checking the board etc., looked inside the USB-C connector itself and one of the sides had maybe 3 of the pins smashed and shorted inside. So new connector needed, I

Have you installed the drivers? The nanoVNA uses a serial to USB device to convers on USB. Check out FTDI for the latest drivers. Verstuurd vanaf mijn iPhone

Thanks Roger, did all of that still nothing. In win7 when I plug it in the USB never responds in any way at all like as if nothing ever was connected at all. Nothing in the device manager, and nothing

Thanks for the response! On the cable, just got a new fancy one from amazon and tried it this morning before sending out my email. I was hopeful that it would work and it did not.......then emailed

At this moment as you can see i update UI and next release name as v1.0.1 UI fixes still not fully comleted (for see changes need reset config for apply new colors)

@DiSlord - let me ask you kindly following - your H4 branch fw version string comes from "git describe --tags" which shows always 0.7.1... What would you recommend to put in the VERSION string such I

Try test 200-350MHz range for better search threshold limit. PS then i work under H4 vs SI5351+SI4432 i rewrite sweep mode, now it use band table for better ajust settings I think remove threshold as