开云体育

On Sat, Oct 19, 2019 at 02:12 PM, Maurizio IZ1MDJ wrote:

I have update the firmware to edy555 0.2.3 , all look ok .
In next step I tried to use console command , which commands is supported ?

---------------------------------------------------------------------------------------

Maurizio,
Sending the command "help" from a serial terminal will return a list of the console command supported by your firmware.

For example:

version

0.2.3

help

Commands: 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

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 :)

Same for me Maurizio
Di you find something in the meantime?
Daniel HB9IIU

On Fri, Nov 1, 2019 at 04:11 PM, Rich NE1EE wrote:

We don't really need a lot of precision, do we? How about a simple resistor
network?

It would mean that the UI would need a linear input dialog: a slope for the resistor networks, and b = 0; and for the diodes, a slope of 0 and b=nnn mV (or whatever)

--
On the banks of the Piscataqua
Rich NE1EE

On Fri, Nov 1, 2019 at 01:53 PM, Nick wrote:

On Fri, Nov 1, 2019 at 05:13 PM, Nick wrote:

Perhaps if VBATEN was set all the time in the firmware a single 16k resistor
at VBAT input (instead of D2) might suffice.

Scrub that. The bridge isn't enabled when the device is switched off because
the firmware is not running.

We don't really need a lot of precision, do we? How about a simple resistor network? Max VBAT ~3.6V with no bridge, 3.15V with bridge, linear response w slope ~= 0.75, 36 uA with no bridge > a long time to drain 450 mAh batt...
--
On the banks of the Piscataqua
Rich NE1EE

How embarrassing
There was a mistake in the VNA calibration routine in Octave

Please ignore all this.....
--
Erik, PD0EK

Nice looking!

Roy
WA0YMH

On Fri, Nov 1, 2019, 12:17 PM Harold Farrenkopf via Groups.Io <hfarrenkopf=
[email protected]> wrote:

Bought the 3D printed case off eBay with the intention of mounting
individual mini push-buttons that I had but found an old 3 by 4 keyboard
that had nice feeling buttons so I cut it up and glued it in the case's top
half. I also glued a toggle switch for the power in the lower half instead
of that cheap slide switch. Now the playing begins. Need to update firmware
with one that has better button detection because that is part of the
crappy jog switch's poor operation. Is there a version of firmware that
improves the button detection now that I have good buttons?
BTW, nice performance for the money! I've always used HP/Agilent VNA's for
work and for the last 17 years, the 8753ES with the 6GHz and TDR options.

Harold, VA3HF

Apparently only for 7+ now

.. and not even that for an acer CB5-571 Chromebook that emulates Android 7.1
The app installs fine from Play Store; simply search for nanovna.
Unfortunately, the app always reports "No device found!" to Connect.

This Chromebook can communicate with nanoVNA using Diginow Serial Terminal.

On Fri, Nov 1, 2019 at 05:13 PM, Nick wrote:

Perhaps if VBATEN was set all the time in the firmware a single 16k resistor
at VBAT input (instead of D2) might suffice.

Scrub that. The bridge isn't enabled when the device is switched off because the firmware is not running.
.

I am interested in testing other firmware than that installed on my "white with gecko logo" version of nanovna.

I have dfu-util installed in my Mageia linux desktop which reports as follows from the vna:

[baz@localhost Original]$ dfu-util -l
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to

Found DFU: [0483:df11] ver=2200, devnum=6, cfg=1, intf=0, path="4-1.5.4", alt=1, name="@Option Bytes /0x1FFFF800/01*016 e", serial="FFFFFFFEFFFF"
Found DFU: [0483:df11] ver=2200, devnum=6, cfg=1, intf=0, path="4-1.5.4", alt=0, name="@Internal Flash /0x08000000/064*0002Kg", serial="FFFFFFFEFFFF"

So question one is why does it see two different devices for the vna?

If I attempt to download the contents of either Alt 0 or Alt 1
I get around 16kB of binary file from each. Both are binary equal when compared with diff.

So question two is how big is the stock firmware and is the 16kB file that I am recovering the whole of it? If not why not?

[baz@localhost Original]$ dfu-util -d 0483:df11 -a 0 -U original.dfu -vv
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to

Opening DFU capable USB device...
ID 0483:df11
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 2048
Limiting default upload to 16384 bytes
Upload [=========================] 100% 16384 bytes
Upload done.
[baz@localhost Original]$

NOTE dfu-util refers to *Upload* from device where I would refer to *download* from the device. :\

I notice that some .dfu firmware files that I have seen are in the 80kB to 100kB plus so the 16kB looks wrong to me.

However I want to be sure that I have a backup of the original before attempting an install of a different firmware.

I have attached a much more verbose output from the download if it helps anyone.

Only constructive comments please as threads are bloating beyond sanity in the list

Barry
G4MKT

Bought the 3D printed case off eBay with the intention of mounting individual mini push-buttons that I had but found an old 3 by 4 keyboard that had nice feeling buttons so I cut it up and glued it in the case's top half. I also glued a toggle switch for the power in the lower half instead of that cheap slide switch. Now the playing begins. Need to update firmware with one that has better button detection because that is part of the crappy jog switch's poor operation. Is there a version of firmware that improves the button detection now that I have good buttons?
BTW, nice performance for the money! I've always used HP/Agilent VNA's for work and for the last 17 years, the 8753ES with the 6GHz and TDR options.

Harold, VA3HF

On Fri, Nov 1, 2019 at 01:55 PM, Rich NE1EE wrote:

I was thinking yesterday that the ST would present a very high impedance on
VBAT when a) the unit is running, so VBAT is internally switched off, and b)
VBATEN is off, so the bridge is not in the loop.

When the VBATEN bit is set the bridge divider is enabled and the input impedance of the VBAT pin will be 100kOhm.

When the VBATEN bit is unset Table 32 of the data sheet indicates that IDD_VBAT (the RTC domain supply current) is only ~1.3uA at 3.6V and 25degC. So the input impedance will be ~2.8MOhm.

The DMMs I have here have too low an impedance to measure VBAT, accurately, at least when VBATEN is unset.

The only way I could make anything like a reliable measurement was with a 'scope and a x10 10MOhm probe. You can easily see when VBATEN is set or unset per Raymond's excellent pictures.

Let's assume we are using a silicon diode for D2.

When VBATEN is set the diode current will be ~40uA and Vf ~0.45V. If the maximum charge voltage of the battery is 4.2V then VBAT will not go above 3.75V which is within the 4.0V maximum.

But when VBATEN is unset the diode current will only be ~1.5uA and Vf ~0.25V. So VBAT could reach 3.95V which is very close to the 4.0V maximum. In fact I measured 4.00V on the 'scope this afternoon with a single silicon diode as the battery approached full charge.

I previously installed a single SOD323 diode marked A6. Today I made some measurements of the battery voltage using that diode with a 'scope, and was consistently seeing Vf ~0.25V when VBATEN was unset i.e. most of the time.

(I now believe this diode to be a BAS316 silicon type, not a Schottky as I previously thought.)

I replaced the BAS316 with half a BAV99 in a SOT23 package marked A7p with identical results i.e. Vf ~0.25V (which kinda confirms the BAS316 theory).

CONCLUSIONS

I do not think a single silicon diode is adequate to protect the STM32 under all charge conditions. So I turned the package through 90deg and reconnected the BAV99 with both diodes in series, from pin 1 to pin2 to VBAT. This drops about 0.5V and allows for a 0.25V margin on the VBAT maximum voltage limit. Pin 3 on the right hand side of the picture is not connected.

When the battery is fully charged QRP's NanoVNA-Q firmware now shows VBAT = 3635mV, which is only a whisker above the 3.6V maximum input to the ADC.

I am not convinced that a diode is the best way to fix this. A diode gives an *offset* which is fine for VBAT protection. But for VBAT measurement a simple voltage divider at the VBAT input could be used to *scale* the battery voltage to the ADC input voltage.

Perhaps if VBATEN was set all the time in the firmware a single 16k resistor at VBAT input (instead of D2) might suffice.

The VBAT current would of course be higher at ~40uA but with a 450mAh battery that wouldn't be too much of a problem.

Nah - not going to work. You cannot be sure the needle has actually caused one layer to blend into another.?

Get an old soldering tip and heat-fuse the layers in a number of areas although I'm not sure the internal structure of the material is conductive.

Or... I've attached a photo of black antistatic conductive foam.If you have any, place something like food wrap (discharge it!) between the foam and your board as the foam conducts.I show 24K ohm and the probes are just laying on top. If I compress, the resistance goes down to 4-5K.



On Friday, November 1, 2019, 12:13:14 p.m. GMT-4, Oristo <ormpoa@...> wrote:

> You're probably making a big capacitor by stacking the sheets with the

adhesive layer between each.

This motivated pinning stacks together; no joy..

The attached script assumes calibration stimulations matching scan ranges
for roughly equal samples per frequency decade.

You're probably making a big capacitor by stacking the sheets with the
adhesive layer between each.

This motivated pinning stacks together; no joy..

The attached script assumes calibration stimulations matching scan ranges
for roughly equal samples per frequency decade.

I have two older Android Phones, (Galaxy S III,
needs battery, and Galaxy S5). Free if you come
and get them.
I am in Vail, Arizona (20m SSE of Tucson).

73, Dick, W1KSZ
________________________________
From: [email protected] <[email protected]> on behalf of Larry Rothman <nlroth@...>
Sent: Friday, November 1, 2019 7:25 AM
To: [email protected] <[email protected]>
Subject: Re: [nanovna-users] Measuring swr

Or - have a look at the XDA forums for a new ROM:


On Friday, November 1, 2019, 10:17:16 a.m. GMT-4, Michael Dooley via Groups.Io <msdooley@...> wrote:

I bought my samsung galaxy note 3 a couple years ago to experiment on. At the time I had an iphone and the space debris (and satellite) tracking software I wanted to use was (and still is) only available for android.
I did not buy it as a phone, but as an android device. It cost me $15.00.

So instead of using your current phone, check with your friends and see if they will sell (or give) you their old android device to play with!
Mike de N5BGZ

On Friday, November 1, 2019, 03:21:15 AM CDT, Oristo <ormpoa@...> wrote:

> Pretty much the only way around it is to root your phone and install a 7.0 or

higher rom from XDA or one of the other sites that offer un-official upgrades.

.. or rebuild the app, specifying support for older Androids.
Build tools warns about most dependency issues.

Bruce,?
According to the IP5303 chip spec, it has an adaptive charge control and overcharge protection.

/g/nanovna-users/message/4298?
My experience with these chips is that they charge at a low rate - the 1.2A is the inverter output, not the charge current.
I charged an 1100mAH cellphone battery that I originally stuck on my 1st Nano - no issues but it took a long time to charge - but boy, did it ever have a long runtime.
...Larry

Hi Joe,This was done on the 1st (White Gecko) Nano I purchased (it had no shielding).I found it improved the noise level slightly (visually on the display) from what it was before, but I never really took any quantifiable measurements at the time.Sorry.

Lithium batteries are designed to be charged at a somewhat constant rate. Chargers are designed to limit that rate to whatever is safe for a battery. The charger in the nanoVNA is probably designed to deliver the current need to charge the 500 mah battery and no more. A larger capacity battery will require more charge time but there should be no issue with charging it with the built in charger. Just don't try to substitute a battery with higher voltage. You will destroy the battery and the charger.

Bruce, K4TQL

I know that many developers protect their work from deliberate claims of prior ownership. But, I suspect that many do not. There are three types of protection: copyright, patent, and trademark. Two of these, patents and trademarks, need to be registered to provide protection. Copyrights do not. A copyright will protect even if you don't register it. Registration will determine if you are truly the original author.

If I were a developer or author, I would at least copyright my work. It's easy to do. You just place a copyright mark on your work so that it can be obviously seen. If you want more protection, mail a copy of your work to yourself and keep it sealed. The postmark will give an indication of the date it was created. This is also good practice for patents and trademarks if you need to prove precedence of your work.

This link will tell you what protections copyrights give:

Check it out.

Bruce, K4TQL

Larry,
I see in the picture you posted the other day
/g/nanovna-users/attachment/223/0/Battery-PCB-MiscShields.jpg
that you have added extra shielding. I have a couple of questions on that. Did the shielding help the noise level? And also how do you measure the noise level?
I'm new at this and as far as I know the thing to do is to look at the LOGMAG trace with the corresponding port open and note how much the trace wiggles. Ideally the trace would be 1 at all frequencies since all energy is always reflected.