|
Re: Who has used the nanoVNA wiki to find information?
#wiki
links to the Wiki and FILE sections in the forum signatureI use the main page to quickly find links to even my own pages. FWIW, I expect (and try to help) Wiki main page to be mostly up-to-date, but necessarily brief. Other pages and links are for more detailed information, but less likely frequent updates, lacking feedback and fewer contributors. GitHub documentation has yet no pull requests, thankfully, since I have not yet successfully processed any test pull request.. I contemplate a substantial rewrite to /g/nanovna-users/wiki/shellcommands because format is hard to edit and information is neither more helpful nor timely than /g/nanovna-users/files/NanoVNA_Console_Commands_Oct-30-19.pdf .. which has the disadvantage of link changes when updated. |
|
Re: Voltage sensing diode
On Sat, Nov 2, 2019 at 07:41 AM, Nick wrote:
With BAV99 2 diodes and a fully charged battery set vbat_offset to 1000 andI didn't know why you liked the BAV99 until I just looked them up. Nice! Puzzled because the BAV99 data sheet says VF=0.7V max @ 1mA, and we are well below that...so I'd expect much less than 0,7V offset. Yet you report 4.2V for a 1V offset. On the whole, I really like the approach. WRT the comment re pads on the PCB, the 16K resistor would go across the D2 pads, and a 100K from D2- to gnd. I have not looked specifically at what to do, but recall from my earlier peeks at the PCB that there seem to be plenty of places to tie the 100K to gnd in the area. WRT "sufficient vbat_offset", it would be zero, so no problem. The point is that software would have to be modded from (what I think is) the current Actual = measured + sufficient vbat_offset, a form of linear equation of y=1*measured + sufficient vbat_offset to a form of linear equation of y=slope*measured + sufficient vbat_offset. where users would then have to enter both a slope and offset. ISo why resistors? Because the diode approach leaves is either sourcing special diodes such as the BAV99 or the SD103AWS, whereas the resistor approach seems more convenient. Maybe not. If I try the resistors, I'll just put in vbat_offset=1000mV, and live with the increasing (small) error as voltage drops. Theoretically, at 3V, I'd be expecting 2.25V, but I'll see 2.00...because I think of the indication as something general, I am mot too fussy about accuracy. Same goes for any behaviour we might put into the VNA based on battery voltage...if it makes the choice a little early, that's OK. The voltage regulator shuts down at 3V, so any action we consider in the future needs to be safely above the. Meanwhile, the battery symbol is just a rough gas gauge. Meanwhile, I was expecting the new battery to be 8+ lines high (based upon something QRP mentioned, but I forget), so it will be interesting to see how it relates to battery voltage...looks to be maybe 10 lines now. My car has something like this *** ** * **** *** ** * and they are grey to start, then as the values rise, what ever is lit turn from red > yellow > green. So I always have at least a red dot at the bottom, then it goes from there But I admit that the battery outline is very recognizable. -- On the banks of the Piscataqua Rich NE1EE |
|
Re: Nanovna data output
Go to this link for aHmm, that wants updating. Latest versions should be linked in Wiki main page /g/nanovna-users/wiki |
|
Re: Console command and FW 0.2.3 edy555
If you already have Python installed, then this script lets you sendI tried to use the scan and sweep,First send 'pause', then use 'scan' commands to nanoVNA and capture data directly to files from your cmd.exe or bash terminal window, without a separate serial console app e,g, PuTTY: |
|
Re: Voltage sensing diode
On Fri, Nov 1, 2019 at 10:31 PM, QRP RX wrote:
Now you can use "vbat_offset" command to setup voltage drop for your diode. :)With BAV99 2 diodes and a fully charged battery set vbat_offset to 1000 and VBAT reads 4210mV on Version screen. Very nice - thank you very much :) After flashing and restarting the nvna I did clearconfig. Got strange stuff on the screen - see pic. Restarting cleared this. Calibrates OK. Not used for any measurements yet. |
|
Re: Brick my Nano
On 02.11.2019 08:59, hb9 iiu wrote:
I think I have to install the drivers first because DFUSe Demo does not "see" my device...I had the same issue and installing drivers did not help. Windows did not recognize device in manner that did not allow it to link it with drivers at all. However, device was properly recognized on other PC without need to manually install drivers. I used that other PC to update firmware and after that, device was visible even on the PC which did not previously recognize it. -- 73, Pedja YT9TP Checkout: |
Oristo
Rich NE1EE
YT9TP - Pedja