开云体育

Actually, a 'mode' byte, similar to the features byte/word I had suggested would be good for that.It could reflect the live status of the device, showing its current mode.Both could work

Thanks Oristo, I tried that but no difference. Thanks Rune, you were correct. Upgraded original GEN111 02.08.19 firmware to edy555 0.2.3 07.10.19 and problem fixed. Nanovna# 1.03 now runs on 32 bit

This is impossible. "help" command implemented in the ChibiOS shell module and returns command list from array of registered commands. If "help" command returns command name, then this command is

Mine is M2.5. I know that because I have one of those multiple length standoff/nut kits from Adafruit in that size, and the nylon standoffs fit. I needed longer standoffs because I soldered header

Since most folks also have a smartphone, it seems more practical IMO to add such complexity by e.g. Android app using USB OTG. Member cho45 already an Android app for

It looks like it's significantly faster (13 milliseconds) if using scipy.signal.convolve - even though that adds another dependency to the application, I'm considering allowing it this time. -- Rune

"convolve" is a rolling sum. https://docs.scipy.org/doc/numpy/reference/generated/numpy.convolve.html https://en.wikipedia.org/wiki/Convolution For this special case of convolving with constant

I guess if I have to go to soem hard to access space to take measurements I would not be happy to rely on pause button. I would like to make snapshot that survives even turning device off. Also, when

Eric, thank you very much for the diff files. There's one small issue though - speed. Looking at the TDR response with 2**16 FFT points, and 101 data points, I get the following: IFFT 6

Hi YT9TP, Pedja - How many stored sweep captures are necessary? Using "PAUSE" keeps the most recent sweep until power off. QRP fixed a bug so that data can be retrieved by USB reconnection, provided

That would require NanoVNA to have additional memory, probably microSD card or so. It is not possible with current NanoVNA but might happen in some new hardware version. And it would be great to

Yes, it seems to me that testing for '?' in return from such commands is the easy way to test for support. Commands that simply change behavior with firmware version are problematic, unless they can

Thanks to noise, it seems highly unlikely that "data" would return identical values to repeated commands $ nt data > paused.txt $ nt data | diff - paused.txt $ nt data | diff - paused.txt | wc

If nanoVNA is paused when USB is connected, then it will return values to sweep command without exiting PAUSE $ nt sweep 10000 1500000000 101 Sending "resume" indeed causes user data to be replaced

Hi Sam, Nooelec are authorized by edy555, the original creator of the NanoVNA, to resell the device: https://www.nooelec.com/store/nanovna-bundle.html I believe they are USA based and stocked. --

QRP, is there a way to see for the app if the sweeping is paused or not? Currently, when connecting to a device, the first thing the application does is to sweep whatever range the device is set to.

Hi QRP, I'll just note, that at least early versions of the firmware (which still exist "out there") included commands in the "help" output which did not exist. I believe the "scan" command started

Hi Sam, I purchased this one: https://smile.amazon.com/gp/aw/d/B07T6LXNTV?psc=1&ref=ppx_pop_mob_b_asin_title I have been happy. Works well, is shielded, came with calibration kit & cables. It is

Sam, If you don't mind paying a bit more for the device you can go through Amazon to get one. I purchased mine through Amazon and it came within 2 days. Shipping was free because I have a prime

Does anyone have a recommendation for a seller for a good quality NanoVNA with cables and OSL? I ordered one a while back and the dealer is no longer listed on eBay and I have not received it as of