开云体育

On Sat, Oct 5, 2019 at 07:12 AM, <hugen@...> wrote:

AA version font requires a larger flash, resulting in saving the settings of
the flash address overlaps with the program flash and I will modify the aa
version later.

Is there a previous "stable" version of type "800_aa" ("without bugs")?
I am glad that you will continue with the modification of the 800_AA version. Thank's for your job.

Why can't I use "DMR-CLEAR_MEMORY_DFU.dfu"?
Thanks

Hi Bryan,

I was able to duplicate your measurement, also with a 68 pF capacitor.
On this screenshot, it's easy to see the effects of frequency on this capacitor, and what you should watch out for.

While profiling (and learning) the NanoVNA myself, I'm coming to the realization that this is a pretty good component tester.

There are limits to resistor values, the precision gets increasingly lower when you go above 1K Ohm, but is great for lower value resistors (<100Ohm) due to the 50 Ohm bridge and calibration point.
For inductors and capacitors the Nano is performing very well, IF you keep an eye on the Smith chart and the (R+jx) factor. You may have to adjust the maximum frequency to stay in the proper half of the chart, as I stumbled on in my first attempts. ("trap for young players")

Enjoy!

I don't know the exact numbers but the cost target is certainly not 100 USD, especially if the target retail price is under $60 ;)

To get some idea the LCD costs on the order of $4, and the MCU $1.5. Any cost increase over $1 requires extensive justification and (most likely) shaving costs elsewhere. A bigger display compounds the cost increase because the PCB also has to be bigger (+$3), the MCU has to be in a bigger package (+$1.5), and of course the LCD itself is a bit more expensive (+$2). In total that is $7.5 of additions which realistically means +$22.5 in retail price, which make a huge difference in competitiveness of the product. To get an idea compare the sell volume of the NanoVNA-H (4000 units/month) to the NanoVNA-F (100 units/month).

Hello

Re LCD size.

What if e.g. a RPi4 is used as the digital board? I understand that the component cost target is 100 USD. A single RPi is 35 USD so in volume it is probably cheaper. The ADC would have to be on the RF board then, but the RPi would cater for more displays options I think. Another added benefit is the modular design.

For stand alone lab use a display larger than 3,5" would be really nice.

Bo

Hi

During alignment or design iterations of a filter seeing the 1 dB, 3 dB, 6 dB and "many" dB points are quite handy.

Bo

1) I installed the NanoVNA-H__800_ch_20191003 version and now it no longer crashes (after the screen calibration, with or without saving).
With 4 tracks the fonts are now very small ... this is a problem for me.

2) In session "Upgrade or Verify Action", the program does not allow me to load the file DMR-CLEAR_MEMORY_DFU.dfu ... Response: "This file doesn't have a correct format..."
Why?

On Sat, Oct 5, 2019 at 01:43 PM, @in3elx wrote:

On Sat, Oct 5, 2019 at 02:28 AM, Larry Rothman wrote:

If you calibrate the touchscreen, it will lock-up at boot.?Please

confirm.?

On Fri, 4 Oct 2019 at 7:59 PM, in3elx@...<in3elx@...> wrote:

I

installed the NanoVNA__800_aa_20191003 firmware. I think this is fine, it

has

improved to 300Mhz ...

I confirm, it also crashes with the "aa" version of 03 October ...
1) press CONFIG
2) I press TOUCH CAL
3) eseguo calibrazione
4) restart
5) blocked initial screen (with info...frozen boot ..)

Now I try to clean and then install NanoVNA-H__800_ch_20191003.

AA version font requires a larger flash, resulting in saving the settings of the flash address overlaps with the program flash and I will modify the aa version later.

On Sat, Oct 5, 2019 at 02:28 AM, Larry Rothman wrote:

If you calibrate the touchscreen, it will lock-up at boot.?Please confirm.?



On Fri, 4 Oct 2019 at 7:59 PM, in3elx@...<in3elx@...> wrote: I
installed the NanoVNA__800_aa_20191003 firmware. I think this is fine, it has
improved to 300Mhz ...

I confirm, it also crashes with the "aa" version of 03 October ...
1) press CONFIG
2) I press TOUCH CAL
3) eseguo calibrazione
4) restart
5) blocked initial screen (with info...frozen boot ..)

Now I try to clean and then install NanoVNA-H__800_ch_20191003.

Rune,
Thanks, let us know if you get any additional info. Do you know how things are progressing between nanoVNA-saver and the NanoVNA-F? The command set doesn't seem to be as homogeneous as the NanoVNA-F developers insinuated.

Herb

Mike,
I agree on all points. I come from a test and measurement background, so -3 dB was always drummed into me with regards to equipment purchasing and test standards. I was only fore warning Rune that if he added automatic S21 filter measurements for -6 dB and -60 dB rise and fall points, to get ready for the ground swell of people requesting the -3 dB point points be included also.

If I design a Butterworth filter I already know its going to fall off at -20 dB/decade, but I need to verify my -3 dB point to ensure my has not started falling off too soon or too late.

Herb

On Fri, Oct 4, 2019 at 07:13 PM, Oristo wrote:

The latest build code is 10KHz-1.5GHz

Is there a good recent aa 10KHz-1.5GHz build?

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

The 10khz-1.5GHz is not an official build but was done by one of our members at the request of another member. The newest build was in the message a few posts back, /g/nanovna-users/message/4073 .

Herb

I see anomalies in the plots if using more than a value of '1' in the "Segments" cell. See attached image:
this is a 320 MHz Low Pass Filter and the protrusion around 500 MHz on the gain plot is one of the anomalies.
Is NanoVNA-Saver only intended to work with certain firmware versions? That could be my issue.


Version info:
ch> version
0.2.2
ch> info
Kernel: 4.0.0
Compiler: GCC 8.2.1 20181213 (release) [gcc-8-branch revision 267074]
Architecture: ARMv6-M
Core Variant: Cortex-M0
Port Info: Preemption through NMI
Platform: STM32F072xB Entry Level Medium Density devices
Board: NanoVNA
Build time: Sep 29 2019 - 02:24:31

Herb, bandwidth is always stated with respect to 3 db points.? But rolloff is 6 to 60db.
Mike WY6K


"... somewhere in the distance, there's a tower and a light, broadcastin' the resistance, through the rain and through the night..."

Please perform a touchscreen calibration, save, touchtest and cycle the power

I have bad hand-eye coordination and break code claimed good,
so did not even try, just installed DMR's rar

The latest build code is 10KHz-1.5GHz

Is there a good recent aa 10KHz-1.5GHz build?

Why are you selling?
Mike WY6K


"... somewhere in the distance, there's a tower and a light, broadcastin' the resistance, through the rain and through the night..."

Please perform a touchscreen calibration, save, touchtest and cycle the power.?Does it lock-up?



On Fri, 4 Oct 2019 at 9:28 PM, Oristo<ormpoa@...> wrote: > Do not use hugen's Oct 2 'AA' firmware versions.

?They cause the nano to lock-up after touchscreen calibration.

Doh!!? I just installed NanoVNA-H__900_aa_20191003.dfu for hacking a new menu tree

Do not use hugen's Oct 2 'AA' firmware versions.
?They cause the nano to lock-up after touchscreen calibration.

Doh!! I just installed NanoVNA-H__900_aa_20191003.dfu for hacking a new menu tree

If you calibrate the touchscreen, it will lock-up at boot.?Please confirm.?



On Fri, 4 Oct 2019 at 7:59 PM, in3elx@...<in3elx@...> wrote: I installed the NanoVNA__800_aa_20191003 firmware. I think this is fine, it has improved to 300Mhz ...

I installed the NanoVNA__800_aa_20191003 firmware. I think this is fine, it has improved to 300Mhz ...