开云体育

On Tue, Oct 22, 2019 at 08:54 PM, <neb40gsm@...> wrote:

Using the console command vbat on
my modified software the voltage reading shows 3.718V.

you're needs to check voltage reading with disconnected USB cable. Otherwise USB power will be applied to the battery and you will get wrong reading...

Hi Rune,

First of all my compliments for your excellent software!
I took the liberty to implement the cable impedance profile in the TDR menu as published in
I succeeded in creating the following graph by changing the Chart.py and NanoVNASaver.py rel 0.1.3.(see attachments)
The measurements were done with two length of coax with different impedance. (S1P file enclosed)
Could this be a future option for next releases?

Regards,

Eric
PS. Due to my inexperience with python I did not manage to include a second Y-axis for the resistance values.

I first want to break out the port I/O kernel (really stolen from Rune)
so that multiple nanoVNA commands may be sent in a single nVargs.py invocation

nVargs.py now implements multiple commands per invocation, surrounded by (unlogged) `pause` and `resume`
Both it and nVcmd.py are tweaked to eliminate redundant trailing newline.


If e.g. nanVNA is calibrated for four frequency bands:
50-658, 666-8660, 9800-114000, 126000-1500000

.. then a single invocation can collect data for all four bands, e.g.

py nVargs.py "recall 0" "data 0" "recall 1" "data 0" recall 2" "data 0" "recall 3" "data 0"

Double-quotes are required for passing multi-word commands to the script as e.g. 8, rather than 16, arguments..


Output for all for sets of data redirect to a single file.

Except the wanted harmonics combination , all other combinations of harmonic products fall outside the audio band.
If you would use the same harmonic for both test signal and LO the other harmonics would also end in the audio band with the worst being the fundamental.
Suppose you use the 3rd harmonic of 200MHz with 5kHz offset you will get 5kHz from mixing the third harmonics at 600MHz but the fundamentals at 200MHz will mix to 5/3 kHz. And the third harmonic of that product is also at 5kHz
This is voided by using 1:1, 3:5, 5:7 and 7:9 combinations

I also vote for hobby version.
Two tracks are good enough and large fonts are must.

Unless your hobby is actually debugging firmware,
why not stick with Hugen AA releases?
They are fairly frequent, if less exciting..

Could it be setup so that selecting a text field causes that field to toggle between large font and small font mode?

si5351 allows to use frequency steps smaller than 1 Hz,
but NanoVNA has limitation, it store frequency as integer value,
so it cannot work with frequency step smaller than 1 Hz

101 steps for 50kHz to 1500MHz spreads them thinly.
I appreciate the storage impact, and when not testing a particular DUT
tend to calibrate for 4 bands of roughly equal octaves:
50-658, 666-8660, 9800-114000, 126000-1500000
.. but it would seem more useful for nanoVNA to implement logarithmic rather than linear steps.

necessaryevil86,

Before you make the order, it’s better to ask seller the detail spec. the list below is what the current NanoVNA supports.

- 3.3V (5V if jump wire)
- 4-wire SPI. It seems the eBay one is parallel
- Raw resistive touch signals, X+, X-, Y+, and Y-. The eBay one is SPI with interrupt (TP_IRQ). If you purchase this one, you not only have to do some jump wiring, but also modify the touch related C code. You can refer to the NanioVNA-F, which uses SPI for touch function.

Ken

Hi Erik,

I looked at your github page and found this line that I couldn't understand. Could you explain it a little more? I wasn't clear on how the mixing removes unwanted harmonics.

"Using Arduino and SI5351 (on 5$ ebay breakout module) to generate test signal and 5kHz offset mixing signal. Both can be square wave as the mixing removes all unwanted harmonics (like Nano VNA)"

Thanks,

Sanjay

On 22.10.2019 19:54, neb40gsm via Groups.Io wrote:

Installed diode D2 with about 0.2V forward voltage drop, the actual measured voltage of the battery is 4.01V, Using the console command vbat on
my modified software the voltage reading shows 3.718V.

Idea: new option to calibrate battery meter which allows user to measure actual voltage and set it as calibrated value.


--
73,
Pedja YT9TP

Checkout:

Installed diode D2 with about 0.2V forward voltage drop, the actual measured voltage of the battery is 4.01V, Using the console command vbat on
my modified software the voltage reading shows 3.718V.

On Tue, Oct 22, 2019 at 09:11 AM, Daniel Marks wrote:

You might want to check out the VNA I designed

Mark,

Thanks, I already studied your design.
Can you also do a comparative measurement with nanoVNA?

return data without the echoed command

By popular demand, a dedicated script:



I needed to sort Python string handling anyway..

You might want to check out the VNA I designed



which is a VNA based on the EU1KY bridge but similar to the NanoVNA with
S11 and S21 capability. It also conveniently features a breakout header
for all of the signals so they can all be controlled and sampled from an
external PC if desired.

The VNA I designed can measure from about 1 to 20000 ohms because of the
bridge design, which is based on current and voltage sensing rather than a
50 ohm output, but it computes what would have been observed with a perfect
50 ohm output port.

A subfolder of the github Tapr-vna is named "Arduino"
It contains the arduino SW required to run on a arduino nano that controls the SI5351 over I2S and the reflection/transmission switch
So tapr-vna communicates over a com port with the arduino SW .
The output of the "audio bridge.pdf" schematic (Audioright/audioleft) go to the line input of a PC
The two sine generators on the same schematic are the two outputs of the SI5351. (so they are not sinus but square wave)
If you want you can also copy the nanoVNA schematic w.r.t to SI5351 and SA612.
Does this help?

Well, it is a rainy day so I tried to do the upgrade.

I went to the [email protected] | Wiki Main Menu and under Firmware and under "Easy windows firmware update" downloaded the "How to write firmware (Windows GUI)" document.

To make it easier I printed out the document. Since I have a DFU file I skipped the first two pages on the DFU File Manager.

I already downloaded DfuSe Demo.

I had DIP IC socket pins with the correct 2.54mm spacing so I shorted two pins together and inserted the shunt into the two rightmost pins P1 VDD and BOOT0.

I switched on the unit and got the white screen and removed the pins.

I switched down the unit and powered up to verify gen111.taobao.com was still working.

I switched down the unit into inserted the pin shunt into P1 and powered up into the white screen boot mode.

I connected the unit to my laptop and started DfuSe Demo. It did not recognize the device so I started Device Manager. It showed the ST driver with an error. I ran update driver and searched for a driver wpdate (This is a Windows 10 laptop).

It found and installed the ST driver and DfuSe Demo found the DFU Device.

Be sure to read the directions at the bottom of page 4. The first step is to save the existing DFU file with the Upload Action Choose and Load options. I saved the existing file and labeled it gen111

I did the upgrade with the NanoVNA-0.3.0m.dfu file. I selected Choose and after a couple of messages the bottom bar turned green and ended with "Target 00: Verify successful" I left the DFU mode. My unit did not automatically reboot so I switched the unit off and on.

The screen came on. I selected the CONFIG and VERSION touchscreen buttons and it shows Version 0.3.0m

Success!

Since I only have one screen on this laptop I usually print upgrade instruction and read them a couple of times before starting. I usually print two pages per sheet to save paper:-) The document is next to my laptop while upgrading and I add notes as I upgrade.

I will continue playing with this great little VNA. I use NanoVNA SERVER and will try NAnoVNASHARP and the NanoVNA WebApp.

Mike N2MS

Erik -
Regarding your home build VNA, I would like to find out more about how you interface the Si5351 to your PC
On your Github page, " the Doc section shows the VNA current bridge and the nano-vna schematics. I am assuming that you don't have the micro and DSP chip in your home built version, so could you tell us more about the interface?

Thank you!

It works great for me - except that the capture button doesn't work.
I get "ERROR - Capture command is not supported". Then followed by "response 11 bytes".

The graphs are very good but the Smith Chart no longer shows frequency as it used to do.
It shows loads of other new stuff that I'm sure will be useful, just not frequency - which is very useful to me.

Kind regards
Tony

On Tue, Oct 22, 2019 at 04:16 PM, Raymond Domp Frank wrote:

A new version is never a mature version. Old bugs may have been killed but new
(buggy?) features and behaviour will have been introduced.
It may be powerful and feature-rich, but it's not mature.

That doesn't mean that I'm not longing for a bit of time to try this version out!

Raymond

On Tue, Oct 22, 2019 at 03:42 PM, n2msqrp wrote:

This looks like a mature version.

A new version is never a mature version. Old bugs may have been killed but new (buggy?) features and behaviour will have been introduced.
It may be powerful and feature-rich, but it's not mature.

Raymond