Question on #consolecommands
I'm slowly working my way through understand all the Wiki shellcommands.Join the club! 1. dump - Prints output buffer. What exactly is in the output buffer? I've haven't been able to corelate the returned numbers.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 appear as a different device in DFU mode. 2. The "trace" command returns the following example data: What are the two numbers that follow the channel number?SCALE/DIV and REFERENCE POSITION I was also going to ask about the "gamma" command and its use but I see you have a question mark in the description field, so I assume its use is not defined.Question mark was not mine; it is returned by shell in current firmware. Originally printed gamma[0]& gamma[1] - see message #101 It is presumably now replaced by 'sample gamma' I suppose 'sample' works with 'port' command, but have not tested enough to be certain. I guess that 'sample' works with 'scan' and 'data' commands (which implies 'pause') for results See message #1219 for definition of gamma AKA S11 |
When a command no longer serves a purpose, like "gamma", why is it still in firmware taking up valuable space?'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 changed when it moved to a 'sample' option. I have yet to do experiments for whether/how 'sample gamma' behaves differently from e.g. default data. |
how much work it must have been for you and Oristo to generate the Wiki page.I made only minor shellcommands tweaks before adding Erik's info today; hard work was by Larry and Buck Calabro, and Larry's PDF my preferred reference. I mostly update that Wiki page just to reduce misunderstandings; its table format seems to me not ideal for the purpose; multi-line descriptions have confusing line spacing. |
Draft nanoVNA shell [ab]user guide list - in order returned by shell 'help'A couple of the consolecommands aren't clear to meJoin the club! mostly tested on NanoVNA-Q-usb-test.dfu Some functions are possible or easier by shell commands?than screen menus, while others are unique. Listing includes questions and complaints: help - response is as poorly organized as screen menus exit - unique; restarts shell; inapplicable to screen menu ? ? ? ? ?( although it might be nice to have a screen reset menu option) info - comparable to lower part of CONFIG-VERSION threads - unique, but mostly useful for firmware development version - comparable to one line in CONFIG-VERSION reset - comparable to device power off/on; a waste IMO ? ?but may be useful for apps that get lost.. reset dfu - comparable to CONFIG-DFU ? ?also IMO a waste, given DFU may require hardware jumper ? ?when firmware configuration is corrupted. freq - comparable to STIMULUS-CW FREQ, in theory ? a waste IMO; why not just `sweep` with one point? ? My testing discovered no use for it... ? 'frequencies' after still returns 101 values in sequence...??!! offset - unique; I suppose this sets IF (stimulus - LO) ? ? ? /g/nanovna-users/message/2597 time - unique; perhaps useful for timing other commands? ? but less useful for that than e.g. linux time(1) dac - unique; seemingly not associated with ADC gain for DSP ? ? ? ? >>perhaps<< ?it may be related to touchscreen calibration ?? saveconfig comparable to CONFIG-SAVE clearconfig unique; claimed to clear ALL (e.g. cal, touchscreen) settings.. data - with no args, scatter inphase and quadrature [for current port?] ? ? ? ?- with args 0-6 "internal calibration table" frequencies - unique alternative to TRACE display for current 'sweep' ? ? ?or (if pause) 'scan' setting; needed for building Touchstone files. stat - unique; returns firmware developer stats gain - unique; sets but does not return tlv320aic3204 ADC gains power - unique; sets but does not return Si5351A output level sample - unique; (partly) presumably works with 'port' ? ? appears broken in my firmware, always returns usage when passed options?? scan - unique; like sweep, but for pause scanraw - unique; like scan, but more options: ? ? {channel(0|1)} {start(Hz)} {step(Hz)} {count} [average] sweep - comparable to STIMULUS; sets and returns test - unique, dead? watch this space - developers?? touchcal - comparable to CONFIG-TOUCH CAL touchtest - comparable to CONFIG-TOUCH TEST pause - comparable to STIMULUS-PAUSE SWEEP resume - comparable to unsetting STIMULUS-PAUSE SWEEP ? ? ?IMO, ?'pause' should have 'on' ?'off' options cal - comparable to CAL, but what is 'in' option save - comparable to CAL-SAVE recall - comparable to RECALL trace - comparable to TRACE; returns, but does not set, options: ? ?TRACE0-4 FORMAT CH0-1 scale offset edelay - comparable to DISPLAY-SCALE-ELECTRICAL DELAY ? ? ? ? ? which IMO is crazy to be under DISPLAY, ? ? ? ? ? because I suppose edelay are associated with CAL..? marker - comparable to MARKER, except actually usable ? ? ? ? ?set marker number and index, ? ? ? ? ?returns active marker numbers, indices and frequencies capture - unique; currently broken for my python scripts, since not ASCII; ? ? ? ? returns display buffer in some(??) bitmap format. vbat - unique; comparable to CONFIG-VERSION bottom line ? ? ? ? IMO waste of space; should be in info.. transform - comparable to DISPLAY-TRANSFORM ? ? ?don't know why here; does shell return TDR data? How?? threshold - unique; sets frequency for switching to Si5351A harmonics dump - unique; deprecated ?or disabled ? ? ? returns buffer with audio data from is ADC output of SA602 mixers |
|
Hi QRP -
Sorry, key part of message was: "broken for my python scripts, since not ASCII"Wrong information. capture command is not unique, it is available in allcapture - unique; currently broken for my python scripts, since not ASCII;- QRP seems to have gotten this working in his latest NanoVNA-Sharp branch - problem is in >>MY<< Python code, NOT firmware - I need to add some Python that correctly handles 'capture' response, e.g. from : def capture(self): from PIL import Image self.send_command("capture\r") b = self.serial.read(320 * 240 * 2) x = struct.unpack(">76800H", b) # convert pixel format from 565(RGB) to 8888(RGBA) arr = np.array(x, dtype=np.uint32) arr = 0xFF000000 + ((arr & 0xF800) >> 8) + ((arr & 0x07E0) << 5) + ((arr & 0x001F) << 19) return Image.frombuffer('RGBA', (320, 240), arr, 'raw', 'RGBA', 0, 1) |
|
Hi Herb -
Thanks for reviewing Some comments regarding the draft :Some further comments "time" command - Useful only if you have a RTC in the systemI think their point was that some nanoVNA >>may<< wire in a Real Time Clock. IMO, firmware anticipating hardware is doomed, but perhaps RTC was in some prototype.. Meanwhile, linux/msys time(1) utility is handy for measuring nanoVNA USB shell command response e.g. by my Python scripts. Agreed, but STM32F072CBT6 PA4 and PA5 "DAC_FC" appear unconnected:dac - unique; seemingly not associated with ADC gain for DSP.It seems to set the output voltage of an analog output of the STM uP /g/nanovna-users/attachment/4059/0/NanoVNA%20Schematic.pdf My >>guess<< was that data 0-1 returned "internal calibration table" for S11, S21data - with no args, scatter inphase and quadrature [for current port?]- "data 0" seems to return s-params for port 0 and "data 1" for port 1. while 2-6 error terms are respectively: directivity, source match, reflection tracking, transmission tracking, isolation I will be testing 'data' with 'port' vs 'data 0' and 'data 1' vs interactions with related screen menu settings |
Oristo
