Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Nanovna-Users
- Messages
Search
Re: Using a larger battery
According to the datasheet, the IP5303 charging current is 1.0A. I think the "adaptive charging current control, excellent adapter compatibility" refers to the capability of lowering output current if the 5V adapter is unable to supply enough power.
This IC is targeted at USB power banks. 1A charging is reasonable for 18650/26650 cylindrical cells, but not for small "pouch" 500mAh batteries. In fact i've seen three nanoVNA units with swollen batteries after just two charge cycles. |
Re: Voltage sensing diode
On Fri, Nov 1, 2019 at 08:11 PM, Rich NE1EE wrote:
We don't really need a lot of precision, do we? How about a simple resistorThat could work, but no pads on the pcb for the second resistor, and not sure if NanoVNA-Q-0.4.3 will allow sufficient vbat_offset, so I'll stick with the "BAV99 2 diode solution" for now. Life too short etc! 73 Nick G3VNC |
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: Firmware and dfu-util (Linux)
On 01/11/2019 22:48, QRP RX wrote:
On Fri, Nov 1, 2019 at 07:46 PM, Barry Jackson wrote:Thanks for your reply,16 kB is a page size. It means data chunk size which controller can accept for flashing. However I am not trying to upload to the vna, I am trying to download the existing firmware for backup. The dfu-util man page says:- " -t, --transfer-size SIZE Specify the number of bytes per USB transfer. The optimal value is usually determined automatically so this option is rarely useful. If you need to use this option for a device, please report it as a bug. " Which is why I did not specify a -t option. If I do, the max limit seems to be 4096, but the resulting file size is still only 16k. What am I missing? Barry G4MKT |
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: |
Nanovna data output
I have a lot of dummy load and i would make a graph to compare the return loss of all.
With my older miniVNA i can get the data for each one because with VNAJ i can get out directly the return loss data. Next the return loss data of all DUT will all be imported with a libreoffice calc spreadsheet. I make the graph importing the spreadsheet in Qtiplot (this because QtiPlot is more useful to customize the graph). How can I do all this with nanovna? My best regards Enzo (IZ5GVP) P.s. Apologize me for my poor English... |
Re: Voltage sensing diode
On Sat, Nov 2, 2019 at 03:16 AM, Rich NE1EE wrote:
This bug present in all firmware. It is related with numpad editor and numeric editor mode. You can fix it just by pressing joystick left or right. Unfortunately fix is not so easy, because it involves a bunch of code changes. I have fix for that bug, but it requires too many changes in the code, so I didn't pushed it into code, because it may break something. |
Re: errors of "error" models
gin&pez@arg
1) The pdf document you have provided and archived for us is written for a C++ complier. This document plus the subtitle of this post "combined fortran, maxima and gnuplot code for [errors in "error" models]", implies to me your intention to port your Fortran code into the C++ environment, and provide the C++ version here for the convenience of this group. Is my interpretation of your intent correct on this? 2) Please confirm that the G-mini equation you have derived and posted here: is a "minimal" one port subset of the full set of two port equations posted here: 3) The Nominal values for the SOL standards in the G-mini equation assumptions in #17 at: /g/nanovna-users/message/4747 are (numerically) defined as perfect. Neither of the above equations provide for standards characterization influences. Are the standards inaccuracies defined and embedded in the uncertainty boundary definitions? 4) The equations defined at a) The set of Equations (0) through (8) are void of calibration/characterization data, and only require reflection SOL calibration measurements of a single port (S11?). Please confirm that both one and two port calibration is embedded in these calculations, and also confirm that SOL measurements are required on only one port, with the through reference plane defined by the SOL standards used to perform the calibration. b) Equation (0 ) and its inverse Equation (8) are unclear. I assume the upper case Gamma is the computed reflection coefficient, and the lower case gamma is the measured (DUT) reflection coefficient. Please confirm. c) In Equation (0), please confirm that S12S21 is an intermediate variable defined in equation (6), and does not imply S12 * S21. d) In Equation (0), S11 is summed with the computed result of all remaining calculations defined as Equation (0). In other words S11 + (S12S21 * G) not (S11 + S12S21) * G d) Equations (1) through (4) define the common intermediate denominator D, and intermediate numerators N11, N21N21, and N22 used in Equations (5), (6), and (7) respectively. e) Equations (5) and(7) are the final calculated reflection coefficient results. f) Equation (6) is a calculated transmission coefficient. Please explain how to differentiate between forward and reverse transmission results. g) Uncertainties due to errors in accuracy, and those accounted for through characterization of the calibration standards used (by their absence here) are removed to the DERDEI contour calculations by the relevance of their contributions to the overall uncertainty in the accuracy of the measurements. h) These equations alone will yield measurement results no better, and no less accurate than existing calibration processes, but are computationally much more efficient. 5) If my interpretation in 5 a) is correct, and only one port is required to be SOL calibrated; have you validated and compared these equations independently for each port in a full two-port system, calibrated with one set of SOL measurements performed at both ports uniquely and independently? This "validation" task cannot be completed on the NanoVNA which has only one reflection port. 6) The forthcoming C++ software (ported Fortran code) will produce the DERDEI (uncertainty) contour calculations given reflection and/or transmission coefficient measurement results and a file of uncertainty boundary estimates as inputs. It is anticipated that the DERDEI uncertainty contour tool will be independent of the calibration algorithm outlined in 4 above, and thus serve the VNA community overall, without compromise, using reflection/transmission coefficient results provided from any source. To that end; I continue to recommend the use of the Touchstone format as the data format of choice for data entry into the DERDEI tool. 73 Gary, N3GO |
Re: Voltage sensing diode
On Fri, Nov 1, 2019 at 06:31 PM, QRP RX wrote:
NanoVNA-Q 0.4.3 firmware is released:Glad to upgrade...will have to wait til Sunday to actually mod the VNA so that the battery display works... Meanwhile... After upgrading and reseting, I got the IMG. Could not get the screen to respond, so turned if off and on. Worked after that. I also figured that a good time to put a 50 O load on CHO, press CAL RESET, and take a snapshot w nanosaver 0.1.4. Hope that this is what you are looking for. -- On the banks of the Piscataqua Rich NE1EE |
Re: Firmware and dfu-util (Linux)
On Fri, Nov 1, 2019 at 07:46 PM, Barry Jackson wrote:
16 kB is a page size. It means data chunk size which controller can accept for flashing. So, software needs to split 80-100 kB firmware to 16 kB data chunks and send it one-by-one. |
Re: Console command and FW 0.2.3 edy555
On Sat, Oct 19, 2019 at 02:12 PM, Maurizio IZ1MDJ wrote:
--------------------------------------------------------------------------------------- Maurizio, Sending the command "help" from a serial terminal will return a list of the console command supported by your firmware. For example: version0.2.3 helpCommands: help exit info threads version reset freq offset time dac saveconfig clearconfig data dump frequencies port stat gain power sample scan sweep test touchcal touchtest pause resume cal save recall trace marker edelay capture vbat transform threshold - Herb |
Re: Voltage sensing diode
NanoVNA-Q 0.4.3 firmware is released:
Now you can use "vbat_offset" command to setup voltage drop for your diode. :) In order to save vbat_offset permanently you're needs to save main config with "saveconfig" command or CONFIG => SAVE menu. Also it has a new battery icon design :) |
to navigate to use esc to dismiss