开云体育

Hi Phil, If you decide to flash or even backup your current installed FW, after you install the DeFuSe utility (assuming your using Windows) replace the DeFuSe.exe with the version I modified in the

Once again thank you for you kind replies. Jerry suffice to say you are probably quite right, what I have works when I find a problem (other than where to get the parameters I was looking for) then

Hey Jerry, have a look at "SD Card Socket" on Amazon, see if something there meets your requirements,. Multipacks (4 or more) for about $5 and if you have prime, no shipping and two day delivery.

Tried removing my SD Card socket. This one was contact down, but my mileage definitely did vary a bit after that. Took a 250 Watt Weller heat gun to it for 3 minutes, when all the solder was molten

Be careful with the type of TF /SD socket you use - if you're thinking of soldering it to your H4 some mount backwards to others (ie: pins are reversed and the card inserts with the contacts face up

Hi Phil, If you are not already overwhelmed by all other advice ... check out the slides from my 4 hour presentation on Theory and Practice of the Nanovna.

I've got an SD card socket from a failing chromebook, intend to transplant it to my nanovna-H4 someday soon. And I really like the addition of a simple TTL UART to these devices. Both much

Yes, I'm aware of using over USB but I am wondering about a standalone solution. (see other forum msg)

NanoVNA H and H4 have SD card support for store s1p/s2p files and screenshots If use external software (like NanoVNA-App) you can save on CPU every measure (see screenshots) You can use Bluetooth (or

Jerry, I had suggested to DiSlord if it would be possible to add an SPI based flash chip to the nanovna firmware but never heard back. Something like that would be ideal for streaming data to - but

Thanks Stan, I had seen that number off to the right of time in ns, but couldn't figure out what it was. In part because the "m" looked like an "n" on this tiny screen. But now that I know what it is,

Christian, My apologies for the rather grumpy reply of my earlier post. If you have a fix, by all means submit it to the repositories. They will either include it or not. In my defense, that struck me

Thank you ! I'm sure several of us will build/flash/play with it and provide feedback in the forum. Cheers, Larry

Ok, as a first step I made my changes public in my own fork/repo: https://github.com/czietz/NanoVNA-H/tree/window_loss. Sorry, no prebuilt binaries; but this way at least those of you who compile

All valid comments for one reason or another. Many folks do ask for improved functionality, and the relatively few people actively developing for the box as volunteers can easily feel like they're

Hi Christian, my opinion is that your proposal to correct the artifact that currently are present on FW available versions is strongly welcomed! At least I strongly believe that any upgrade is

Some of the coders that contribute to this project are a bit thin skinned and people here are kind of protective of them. Anyway if you have found a flaw (which this is) you should definitely post

Hi Christian, Only one member reply talked about 'pissing-off' the devs, which happened when a former forum member demanded that a dev share their code - and the dev shut down their repo to

Larry, I'm all for contributing changes back to the community. I'm a maintainer of multiple open-source SW projects, too. However, the feedback I got to my first email when I courteously wanted to

So Christian - you're telling the forum members that Nano's firmware is not accurate (in one area) and that you've fixed it in you own private repo, but you're not willing to share the changes with