开云体育

True dat! ??

After firmware upgrade you're needs to perform touch screen calibration. If you don't do that, touch screen may works incorrectly. In order to do touch screen calibration, open CONFIG menu and press

Hi, could I please also try your modified software? That's a very nice piece of work you did there. fpliuzzi(at)aol.com

This group has a high enough SNR. Please change Subject when changing topic. Thank you. Ted Antanaitis WA7ZZB

I call BS on that, based on a long career in embedded software development. If NanoVNA-F wants Rune's support, then they should AT LEAST provide him one, FREE.

[ I do not have but am investigating cheap Android tablets for Web-Client (e.g. refurb Lenovo Tab 4, Android 7.1) ] WebUSB wants Chrome Browser version >= 65 for Android >= 4.1

For some reason, edy555_bugfix wouldn't run correctly on my device. In particular, when I hit "back" during calibration, the menu disappeared from the screen. Then when I touched the screen that same

One can never have too many different adapters ?

Any one need 10 female to female connectors that I just ordered without looking first! :-)) :-)) Roy WA0YMH wrote:

Mike thanks for your Tips for new Users doc. Small comment: I think you mean to recommend a male to female sma adapter and not a female to female sma adapter, since the connection on the NanaVNA is

Hi Rune; I've been following your NanoVNA Saver development with much interest, and I support your wise decision to throttle back on adding features so you can focus on making sure you don't have any

Rune, So, here is a bit more detective information to the issue I have reported with newer firmware and nanoVNA-Saver 0.0.12. PC software: nanoVNA-Saver 0.0.12 Firmware version: edy555 version 0.2.2

I have webusb working on desktop (W10)in chrome. I had no success with my samsung S7 edge, connects to nanovna wasn't OK. The tip over here in the forum to use a usb hub (not powered) got the nanovna

David, The NanoVNA-F developers announced a few days back that the command set for the NanoVNA-F overlapped the NanoVNA and; therefore, should run nanovna-saver with only small changes to the code.

[email protected]> wrote: I looked at the document quickly. One thing that struck me is the recommendation to add SMA *female-female *adapters so one does damage the connectors on the NanoVNA by

Thanks for the info, Dave

Hi David, Without a NanoVNA-F to test against, I don't know that I would be able to do much to support it. But looking at the source code for the firmware, it shouldn't be too far from what the

Yes, please.? Do not contemplate a second -F group! Mike WY6K "... somewhere in the distance, there's a tower and a light, broadcastin' the resistance, through the rain and through the night..."

Yes, what Herb said! Mike WY6K "... somewhere in the distance, there's a tower and a light, broadcastin' the resistance, through the rain and through the night..."

Rune, I greatly appreciate the information you have provided above. This is very helpful in the debugging process. I think your approach is very reasonable. I will do some more testing and get back to