开云体育

Hi Herb,I'm slowly updating the console commands as I get expanded info on how they function.?Are you referring to my pdf ot Oristo's wiki page? Larry On Wed, 23 Oct 2019 at 4:14 PM,

Why not use a dash after the data command to enable extended features. For example:? data - x y z If there is no extended data command then it will return an error with the dash.? Or...the firmware

I agree that edelay >>affects results<<. My point is that standalone device users seemingly cannot display current edelay >>setting value<<, e.g. when RECALLing another calibration. Settings RECALLed

'gamma' is no longer standalone in firmware that I use; neither in help or from the shell. Unrecognized text strings provoke the shell to echo with '?' appended Probably only the shell handling

edelay 200 picoseconds visible very good, especially at high frequencies, above 200 MHz.

You can notice difference on Series and Parallel RLC screen. Higher frequency has higher difference. 10 picoseconds is a small delay for NanoVNA you may lose difference in the noise.

These are debug commands, used to debug the code. Just ignore it :)

Tks Oristo, When a command no longer serves a purpose, like "gamma", why is it still in firmware taking up valuable space? Just a rhetorical question. Regards, - Herb

Join the club! For USB device to support SPP (virtual COM port), it must be prepared to send many bytes, so STM32 needs a buffer. Unlike other chips, STM32 integrates USB. That is why it can

You click the UNSUBSCRIBE link at the bottom of every message. Nigel A. Gunn, 1865 El Camino Drive, Xenia, OH 45385-1115, USA. tel +1 937 825 5032 Amateur Radio G8IFF W8IFF and GMRS WRBV701, e-mail

Could you please check your hardware with this firmware version? (see attachment) It has extended hardware check and if there is some problem with your hardware you will see it on display. I'm

FWIW, I would prefer 'anydata' over 'dataall' That eliminates much host script foo, so great IMO, particularly if it works with scanraw averaging.

Changing edelay from 10 to -10 by shell makes no noticeable change on DELAY format with a prominent reflection pulse and marker around 250MHz. 50x larger edelay values visibly shift the trace

Oristo, I'm slowly working my way through understand all the Wiki shellcommands. A couple of the consolecommands aren't clear to me and I was hoping you might be able to help. 1. dump - Prints

we can implement this feature for current "data" command, so it will be able to return all requested data in a single response. But unfortunately I don't see easy way on how to determine if firmware

Hi Rune, you can check firmware capability with help command. It returns list of supported commands. So, you can check if specific command is supported by this firmware with simple string word search

You can find ELECTRICAL DELAY with touch screen with using DELAY format for the track. It shows Group Delay in picoseconds. But you can change scale to 5 ns, it will be more conveniently to use with

Back to the original subject issue: ch>edelay -50 ch>edelay -50.000000000 At least for this firmware version, there is a disconnect between negative values by shell and screen menu

Updated /g/nanovna-users/wiki/shellcommands

application, it will remain as a superb achievement for years. +++++ is not seeing the NanoVNA when it is physically connected: root's privileges will be required in running the application so that