I try port most code from H/H4 (not finish, but... it work)

Changes:
- rewritten control code si53351 (ported from H, almost unchanged, only work on harmonics is cut out)
- accelerated work on the i2c bus with si53351 (it is software, but the decrease in delays made it possible to speed up the work of the si5351)
- accelerated work on the SPI bus with ADF (it is software, but the decrease in latencies made it possible to speed up the work with the ADF4350)
- new measurement timings are installed
All this made it possible to understand the measurement speed by a factor of 2 (and for SI up to 140 MHz by more than 4 times), you can further increase the speed by choosing AVGx1 (by default 2x), this will still increase the speed, but at the cost of a slight deterioration in quality at high frequencies
For V2 / V2Plus frequency step up to 140MHz - 1Hz, above 140MHz - 375Hz
For V2Plus4 up to 140MHz, it seems like 10Hz, above 10k (it seems like this code is hidden, I can't say for sure)

Now for the rendering and interface
- ported the code for drawing the screen from H, this gave in some cases more than twice the screen refresh rate (especially when there are many long lines), not to be confused with the measurement speed
- added track | Z |
- the FPU module is used for calculations
- removed unnecessary buffers and so on, this allowed the free memory to be used to increase the number of points to 371
- the UI system has been redesigned, which made it possible to move the markers with the rocker, change the type of graph, size, and anchor point on H when paused.
- The Time Domain code has been rewritten, it is 2 times faster (and taking into account FPU, about 10 times)
- full support for NanoVNA-App for control from it
- add 6 markers support
- add grid text (DISPLAY->SCALE/DIV )

This is from the main one, which I don't remember yet, I ported almost everything from H, the main thing was that I wanted to speed up the work and remove the annoying impossibility of working with a rocker to set markers during a pause (well, and change the track)
The main thing I work with is V2Plus, so on a regular V2 I could miss something.

Once again about the timings, the new AVGx2 mode is analogous to the old AVGx1 in quality (the new AVGx1 mode speeds up, but at the expense of a small loss of quality)

ATTENTION the firmware is compiled with FPU enabled, so if you have FPU version on the screen - no, they will not work (later i compile some fw vs disabled FPU support)

Amazing work ! Thank you for not forgetting the v2 owners !!

Thank you for this great work, and for all what you do for the NanoVNA and tinySA community. It's really outstanding.

Just one question : I think it is not possible to put here the variable RBW function. Is it related to available commands, or something else ?

Jean-Roger

Exist Display->Avg option, it analog of rbw (but different device use different tables/size for calculation correct RBW can`t show in options)

Ok, thank you for your explanation. It remains not so accurate as for a H4, but quite useful.

Jean-Roger

It sounds like a massive undertaking.

It seems that dynamic range will be improved slightly with a significant increase in sweep speed.

Have you kept the pulsed signal which seems to be a feature of the v2 architecture so as to facilitate ecal? The reduced frequency step size will enable a worthwhile improvement to narrow band sweeps, but will it enable measurement of crystals?

Steve L

V2/V2Plus can measure crystals (frequency step up to 140MHz, 1Hz) vs some limits V2Plus4 not

Here crystal measure on V2Plus:

here is V2Plus4 crystal measure try:

No, this screenshot from test version (i want understand how it work on more points) in it not possible save calibration (as can see not calibrated)

ah ok ... understood ... you made it just for tests ...

aehem .. what about also add some avg on the plus4?? should smooth the
curve out a bit i think

greetz sigi dg9bfc

ps how was your setup ... any pictures or a description??

Am 07.04.2021 um 20:33 schrieb DiSlord:

> No, this screenshot from test version (i want understand how it work
> on more points) in it not possible save calibration (as can see not
> calibrated)
>

Test 3000 - 4500 MHz

a good 9cm filter ;-)

dg9bfc sigi

Am 10.04.2021 um 17:24 schrieb Aleksander Shalygin:

> Test 3000 - 4500 MHz
>

Er, yes, and you have broken through the 4.4ghz limit of all the v2 nanovnas.
I thought it was a hardware limitation.

Steve L

the hardware limit is "around" 4.45 ...some a few megs higher some a bit
lower

4.4 g left enough safety margin

dg9bfc sigi

Am 10.04.2021 um 17:42 schrieb Stephen Laurence:

> Er, yes, and you have broken through the 4.4ghz limit of all the v2
> nanovnas.
> I thought it was a hardware limitation.
>
> Steve L
>

Hello,
in the highest part of the passband I see a S21 higher than 0 dB. This looks a calibration error, since the filter cannot amplify. Did you calibrate with a kit able to go to 4 GHz?
Marco.

Hi Dislord,

Keep up the good work. I love the screen layout and speed improvements you've made.
Waiting for future updates on this project.

Amazing work ! Tested on v2.2 LCD 4 "320x480 with FPU. The speed and number of points are perfect. I haven't been able to run the NanoVNA-App yet, after connecting via OTG the NAnoVNA display will stop redrawing, but after pressing "connect" on smartphone it will be displayed "No device found!".

Excellent work from DiSlord. Thanks for this update for nanaVNA2. I've tested with an nanaoVNA-2 that boxed and change the Display to 4" and the version with FPU, works great, even though I guess there is a small bug, when frequency control changes from the SI oscillator to the MAX oscillator.

As you will see in the attached pictures there is Gain change in 140 MHz, around 2dB, that is observable in the Device, as well in all the softwares I used (nanoVNA-App, nanoSaver, VNA-QT).

I recall reading I don't now if in this group or in the one dedicated to nanaVNA, there was a bug in one of the early versions that showed a similar behavior.

I hope DiSlord will be so kind to review it, as the improvements he has ported to the nanoVNA2 users, is incredible.

Regards

Alex
EA4BFK

PS: Pictures are from a LNA for 145 MHz with a BPF

Recalibrate device. Better made full SOLT calibration.

I’ve clean (reset ) the memory slots and recalibrated (SOLT) again and the issue remains. I’ll post some screen shots later today.

Alex
EA4BFK

You calibrate device in measure range?
Or made calibration in full range, after switch to 100-200MHz?

Hello

I have a NanoV2 and modified to V2_2 Plus with the C and R
I have a 4" display ST7796
Can I use this firmware or is there a special one..
Tnx

JP

Also curious on the question stated previous, what are the differences between the v2plus and v2 version of this firm and does the v2plus firm with these changes work correctly on a v2 modded into a plus with R/C mods?

FW need CPU unit vs FPU module (see version screen FPU: yes should present), or need use noFPU variant (not compiled for V2Plus)

For V2 - need use V2 variant, V2Plus - V2Plus, for V2Plus4 - V2Plus4
Not need install on V2 hardware V2Plus firmware, not work, need made hw mod (install R/C and write correct bootloader vs device serial code)
Not need install on V2Plus hw, V2 firmware

Possible different screensize small screen 2.8 and 3.5 screen - need use 320x240, for 4 inch screen need use 480x320

That is what we were asking, is if a v2 with v2plus bootloader and r/c mods would work with v2plus dislord firmware with all the changes done to it, and what are the differences between the v2 and v2plus firmware in function (is sweep even faster or still the same as v2 non plus since you overhauled so much in the firmware already)

And sadly owo does not make bootloaders anymore for users that are willing to
upgrade v2 to v2plus

I already asked cause a friend from me wanted to upgrade to the plus version

Greetz sigi dg9bfc





Am 27.05.2021 21:16 schrieb DiSlord <dislordlive@gmail.com>:

> FW need CPU unit vs FPU module (see version screen FPU: yes should present),
or need use noFPU variant (not compiled for V2Plus)
>
> For V2 - need use V2 variant, V2Plus - V2Plus, for V2Plus4 - V2Plus4
> Not need install on V2 hardware V2Plus firmware, not work, need made hw mod
(install R/C and write correct bootloader vs device serial code)
> Not need install on V2Plus hw, V2 firmware
>
> Possible different screensize small screen 2.8 and 3.5 screen - need use
320x240, for 4 inch screen need use 480x320
>



_._,_._,_

* * *

If you have a bl for your v2 to convert it to plus the yes
Works fine
I have modded a v2 (saa2n) and it works good with dislords fw


Gesendet von Mail für Windows 10

Von: endevite
Gesendet: Freitag, 28. Mai 2021 05:18
An: NanoVNAV2@groups.io
Betreff: Re: [nanovnav2] firmware for V2, it contain most features from H/H4

That is what we were asking, is if a v2 with v2plus bootloader and r/c mods would work with v2plus dislord firmware with all the changes done to it, and what are the differences between the v2 and v2plus firmware in function (is sweep even faster or still the same as v2 non plus since you overhauled so much in the firmware already)

One minor problem for some....

It seems that you-know-who has stopped providing bespoke bootloaders for the old v2, partly because it must have become tiresome, and also most of the requests recently were probably for clones. Personally, I am quite happy with my four unmodified V2 devices; an original V2.2, two V2N and a Black and Gold. I think the latter three would be defined as “clones” by OwO/ Gabrielle/ Gab-Chan.

I will try Dislord’s firmware on one of the V2N devices. The Black and Gold has the Obijan firmware on it. I want to find a stable long-lasting firmware for when interest in “develpoing” it runs out.

Steve L

Hi,

I own a NanoVNA V2 black and gold and it runs fine on Dislords latest
firmware.

Regards

Jos

Op 30-5-2021 om 18:10 schreef Stephen Laurence:
> One minor problem for some....
>
> It seems that you-know-who has stopped providing bespoke bootloaders
> for the old v2, partly because it must have become tiresome, and also
> most of the requests recently were probably for clones. Personally, I
> am quite happy with my four unmodified V2 devices; an original V2.2,
> two V2N and a Black and Gold. I think the latter three would be
> defined as “clones” by OwO/ Gabrielle/ Gab-Chan.
>
> I will try Dislord’s firmware on one of the V2N devices. The Black and
> Gold has the Obijan firmware on it. I want to find a stable
> long-lasting firmware for when interest in “develpoing” it runs out.
>
> Steve L
>


--
Dit e-mailbericht is gecontroleerd op virussen met Avast antivirussoftware.
https://www.avast.com/antivirus

Hello pac-man players,
What is a Devel-Poing? A new four parameter measurement? Has anyone of you ever done any HV measurements al all?
OE6CCP

> Am 2021/05/30 um 18:10 schrieb Stephen Laurence <Gaslaurence@gmail.com>:
>
> One minor problem for some....
>
> It seems that you-know-who has stopped providing bespoke bootloaders for the old v2, partly because it must have become tiresome, and also most of the requests recently were probably for clones. Personally, I am quite happy with my four unmodified V2 devices; an original V2.2, two V2N and a Black and Gold. I think the latter three would be defined as “clones” by OwO/ Gabrielle/ Gab-Chan.
>
> I will try Dislord’s firmware on one of the V2N devices. The Black and Gold has the Obijan firmware on it. I want to find a stable long-lasting firmware for when interest in “develpoing” it runs out.
>
> Steve L
>

Because people have been getting the wrong idea, doing the modifications
doesn't actually upgrade your device to plus but simply unlocks faster
sweep timing. People have been coming to me complaining about inaccurate
or noisy measurements after the "upgrade", so I think this whole upgrade
thing is doing more harm than good. Just leave your devices as is, even
if you did the 3 capacitors change it will still run V2_2 firmware just
fine, no need to undo it.