As of 2022 there are many badly performing clones on the market. V2/3GHz NanoVNA uses parts like ADF4350 and AD8342 which are costly and clones have been cutting costs by using salvaged or reject parts.
See official store and look for V2 Plus4/V2 Plus4 Pro versions only to avoid getting a bad clone. We have stopped selling V2.2 versions since October 2020, so all V2 hardware that are not Plus or Plus4 are not made by us and we can not guarantee performance.
Hi
I have downloaded and installed this new release of 09092020 for V2_2 but do
not see any information what the new release has of changes.
Does anyone knows ?
Kind regards
Kurt
My bugfix for markers of 2.2ghz and higher is in.
Rest of the changes are for v2+ support I guess.
Hello Wouter
Thank you for the info
I suppose the 4 inch version can be used for the SAA-2N ?
Kind regards
Kurt
Fra: NanoVNAV2@groups.io <NanoVNAV2@groups.io> På vegne af Wouter van Gulik
Sendt: 10. september 2020 19:30
Til: NanoVNAV2@groups.io
Emne: Re: [nanovnav2] The new release of 09092020 for V2_2
My bugfix for markers of 2.2ghz and higher is in.
Rest of the changes are for v2+ support I guess.
yepp ... i use it on mine
and fired that also to a v2 modded with a 4 inch (so nearly same thing
now except the connectors and switch location)
regards sigi
Am 10.09.2020 um 20:58 schrieb Kurt Poulsen:
Hi Sigi
Thank you
Kind regards
Kurt
Fra: NanoVNAV2@groups.io <NanoVNAV2@groups.io> På vegne af Siegfried Jackstien
Sendt: 10. september 2020 23:01
Til: NanoVNAV2@groups.io
Emne: Re: [nanovnav2] The new release of 09092020 for V2_2
yepp ... i use it on mine
and fired that also to a v2 modded with a 4 inch (so nearly same thing now except the connectors and switch location)
regards sigi
Am 10.09.2020 um 20:58 schrieb Kurt Poulsen:
Hello Wouter
Thank you for the info
I suppose the 4 inch version can be used for the SAA-2N ?
Kind regards
Kurt
Fra: NanoVNAV2@groups.io <mailto:NanoVNAV2@groups.io> <mailto:NanoVNAV2@groups.io> <NanoVNAV2@groups.io> På vegne af Wouter van Gulik
Sendt: 10. september 2020 19:30
Til: NanoVNAV2@groups.io <mailto:NanoVNAV2@groups.io>
Emne: Re: [nanovnav2] The new release of 09092020 for V2_2
My bugfix for markers of 2.2ghz and higher is in.
Rest of the changes are for v2+ support I guess.
I just fixed another AGC related bug. This should fix the first point
S21 problem. Here is the updated firmware, see attached, but don't share
the binaries publicly yet until I do another release to avoid potential
GPL issues.
I forgot to turn off a debug option when building the binaries in my
last post, use these instead:
Gabriel,
Too late. I already loaded the binary for V2_2 and the first point issue is resolved (tks very much!). The only issue I had after loading the new V2_2 binary is touch calibration was way off and I had to use the buttons to access the touch calibration button.
Any benefit in re- loading the binaries with the debug option off - other than smaller size?
Again, tks for letting me try the binary before the public release. Since you have not yet released a 4” product, I didn’t think this would be on your radar.
Best Regards,
- Herb
From: OwO
Sent: Thursday, September 10, 2020 10:08 PM
To: NanoVNAV2@groups.io
Subject: Re: [nanovnav2] The new release of 09092020 for V2_2
I forgot to turn off a debug option when building the binaries in my
last post, use these instead:
The debug option shows the baseband gain setting in place of S11, so if
you want to make S11 measurements you probably want to flash the
firmware in the last post instead.
Many users have modded their devices with a 4 inch display, so we will
continue to maintain the 4 inch V2_2 firmware.
Gabriel,
Good to see this version displays 'SOLT' in the calibration panel instead of just 'D'. Also, if only S21 measurements are being made and you change parameters, the new firmware allows you to perform a 'Through' calibration without needing to do a full SOLT calibration.
The modern interface introduced by DiSlord and OneOfEleven on the NanoVNA finally makes its appearance on the V2.
Probably some other small features like the addition of 'Q Factor' that I missed.
Nice work.
-Herb
About Dislord and 1-11
Do you mean that the soft is compatible with the new program of OneOfEleven, nanoVNA-Win, since this is a very good and powerfull and compact program.. ?
This would be a fantastic feature to make the V2_2 compatbile with this software..
JP
Hi Gabriel
Same problem with the 09092020 release regarding touch panel. Button access needed + save
Kind regards
Kurt
Fra: NanoVNAV2@groups.io <NanoVNAV2@groups.io> På vegne af hwalker
Sendt: 11. september 2020 05:21
Til: NanoVNAV2@groups.io
Emne: Re: [nanovnav2] The new release of 09092020 for V2_2
Gabriel,
Too late. I already loaded the binary for V2_2 and the first point issue is resolved (tks very much!). The only issue I had after loading the new V2_2 binary is touch calibration was way off and I had to use the buttons to access the touch calibration button.
Any benefit in re- loading the binaries with the debug option off - other than smaller size?
Again, tks for letting me try the binary before the public release. Since you have not yet released a 4” product, I didn’t think this would be on your radar.
Best Regards,
* Herb
From: OwO <mailto:OwOwOwOwO123@outlook.com>
Sent: Thursday, September 10, 2020 10:08 PM
To: NanoVNAV2@groups.io <mailto:NanoVNAV2@groups.io>
Subject: Re: [nanovnav2] The new release of 09092020 for V2_2
I forgot to turn off a debug option when building the binaries in my
last post, use these instead:
Hi Gabrielle
V2_2-ili9341.bin works fine on my Tindie V2_2 but this happens frequently as seen in the attached image
Kind regards
Kurt
I am expecting delivery of the 4 SAA2N from R&L electronics today. Is this
firmwsre suitable for this model?
Mike N2MS
> On 09/10/2020 11:29 PM OwO inch <
[owowowowo123@outlook.com](mailto:owowowowo123@outlook.com)> wrote:
>
>
>
>
>
>
>
> The debug option shows the baseband gain setting in place of S11, so if
>
> you want to make S11 measurements you probably want to flash the
>
> firmware in the last post instead.
>
>
>
>
> Many users have modded their devices with a 4 inch display, so we will
>
> continue to maintain the 4 inch V2_2 firmware.
>
>
>
>
>
>
_._,_._,_
* * *
i just flashed newest fw on my 2n ... works superb
have to plug on the smaller lcd on the open frame unit to test the 9341
version ... the 4 inch version did not show that ... but i just made a
few tests so far on the 2n (with the 4 inch firmware)
did you have that in "normal" or flipped display setup?? calibrated
touch screen??
as far as i could test the newest binary it works good ... first point
fault seems to be solved .. and i do not see the 1 db jumps ... if it is
stable (next hours/days will show) then i would say its ok
greetz sigi dg9bfc
ps ... and time will show how often we can flash firmware or store
calibrations before the chip wears out hi hi
Am 11.09.2020 um 11:30 schrieb Kurt Poulsen:
On Fri, Sep 11, 2020 at 01:43 AM, Jempi ( ON7MA ) wrote:
>
> About Dislord and 1-11
>
> Do you mean that the soft is compatible with the new program of
> OneOfEleven, nanoVNA-Win, since this is a very good and powerfull and
> compact program.. ?
>
> This would be a fantastic feature to make the V2_2 compatbile with this
> software..
JP,
The reference to OneOfEleven and DiSlord was in regards to the new modern 3D button UI that is introduced in release of 09092020 for V2_2. The UI was first introduced on the NanoVNA platform by OneOfEleven and subsequently supported by DiSlord.
Because the programming interface of the V2 is not backwards compatible to the NanoVNA, getting the V2 to work on NanoVNA_Win would require a major re-write by the program's author.
Gabriel at one time said she would give consideration to adding backwards compatibility to the NanoVNA for console commands in a V2+ future product. That would be the best way to take advantage of some of programs like NanoVNA_Win that are being developed for the NanoVNA.
- Herb
i just flashed last binary (with debug off) on my 2n ... yes it works fine
greetz sigi dg9bfc
ps ... FOUR??? ... bunch order for 3 friends and you?? :-)
Am 11.09.2020 um 12:07 schrieb n2msqrp:
On Fri, Sep 11, 2020 at 05:11 AM, n2msqrp wrote:
I am expecting delivery of the 4 SAA2N from R&L electronics today. Is this firmware suitable for this model?
===========================================================
Mike,
The v2_2-st7796.bin binary is suitable. Just be aware that this firmware is currently in beta test and not yet an official release. Also, Gabriel does not support the SAA-2N so if you run into problems related to that platform you'll have to depend on her generosity or go to the manufacturer regarding a reply.
- Herb
Hi,
@Sigi - I think in the case of wear out the flash :)
while waiting for Plus4 version,
vy73
Slawek/SP9BSL
On Fri, Sep 11, 2020 at 01:31 PM, Kurt Poulsen wrote:
>
> Hi Gabrielle
> V2_2-ili9341.bin works fine on my Tindie V2_2 but this happens frequently
> as seen in the attached image
> Kind regards
> Kurt
I have seen the same on my Tindie model. It was already reproducible with commit e017aab, but commit b8e793d was still fine.
On Thu, Sep 10, 2020 at 09:04 PM, hwalker wrote:
>
> Good to see this version displays 'SOLT' in the calibration panel instead
> of just 'D'. Also, if only S21 measurements are being made and you change
> parameters, the new firmware allows you to perform a 'Through' calibration
> without needing to do a full SOLT calibration.
>
> The modern interface introduced by DiSlord and OneOfEleven on the NanoVNA
> finally makes its appearance on the V2.
>
> Probably some other small features like the addition of 'Q Factor' that I
> missed.
I port code for UI and Q factor (and update calibration status panel) in my part update for V2 ( https://github.com/nanovna/NanoVNA-V2-firmware/pull/23 ).
NanoVNA-App not support data exchange vs V2 (it use different format)
PS not fully related to V2. On my test vs H4 data exchange speed not depend from points count. On H4 i have ~470 points/sec in exchange vs CPU (~570 internal measure) and not depend how i get it by 101 points in 4 time or 401 in one time (if use binary format and not apply calibration, for calculate interpolation need additional time). So 1024 points not need (it use a lot of memory, and this memory can be used for increase normal work measure points from 201 to ~300-400 points)
On Thu, Sep 10, 2020 at 09:04 PM, hwalker wrote:
>
> Gabriel,
> Good to see this version displays 'SOLT' in the calibration panel instead
> of just 'D'. Also, if only S21 measurements are being made and you change
> parameters, the new firmware allows you to perform a 'Through' calibration
> without needing to do a full SOLT calibration.
>
> The modern interface introduced by DiSlord and OneOfEleven on the NanoVNA
> finally makes its appearance on the V2.
>
> Probably some other small features like the addition of 'Q Factor' that I
> missed.
I port Q factor and UI code from NanoVNA to V2 in this PR ( https://github.com/nanovna/NanoVNA-V2-firmware/pull/23 ) also fix format and update for calibration status.
NanoVNA-App not support data exchange format for V2
==================================
About data exchange, V2 use 1024 uncalibrated points for CPU exchange, this need a lot of memory. But as my H4 test exchange speed not depend from points count (if use binary bormat and not apply calibration) i have ~470 points/sec speed exchange in 101 points at one time or 465 points/sec for 401 for get 8k points from device (internal device measure speed ~ 570 points/sec)
This memory can be used for increase device points count from 201 to 301-401 points. And for CPU exchange use it.
Same as Mike here. My SAA2N arrived yesterday. I'm sure it will be functional as is but Mike, if you see any significant improvements with a particular firmware for that particular device I'm sure the community would like to know about it - or at the very least, I would like to know about it.
SeanKB8JNEInfo good on QRZ
PS, it's a fairly heavy unit. If you've had another type already, it's a lot heavier.
Spell checked by the NSA.
On Fri, Sep 11, 2020 at 8:25 AM, hwalker<herbwalker2476@gmail.com> wrote: On Fri, Sep 11, 2020 at 05:11 AM, n2msqrp wrote:
I am expecting delivery of the 4 SAA2N from R&L electronics today. Is this firmware suitable for this model? ===========================================================
Mike,
The v2_2-st7796.bin binary is suitable. Just be aware that this firmware is currently in beta test and not yet an official release. Also, Gabriel does not support the SAA-2N so if you run into problems related to that platform you'll have to depend on her generosity or go to the manufacturer regarding a reply.
- Herb
On Fri, Sep 11, 2020 at 06:23 AM, mchenryproj wrote:
>
> Same as Mike here. My SAA2N arrived yesterday. I'm sure it will be
> functional as is but Mike, if you see any significant improvements with a
> particular firmware for that particular device I'm sure the community
> would like to know about it - or at the very least, I would like to know
> about it
Sean,
If you look back through the "new release of 09092020 for V2_2" topic messages you'll find that changes to the user interface (UI) and firmware bug fixes make the new firmware well worth upgrading to. The caveat is that the firmware is not yet an official release, so if you install it you should consider yourself to be a voluntary beta tester.
I enjoy being one of the first to try out a new feature - even if it means I may need to re-load the firmware a few times while the developer is working things out. If that's not your bag of tea then you might want to wait for the official GitHub release before doing a firmware update.
- Herb
I can`t post messages?
On Thu, Sep 10, 2020 at 09:04 PM, hwalker wrote:
>
> Gabriel,
> Good to see this version displays 'SOLT' in the calibration panel instead
> of just 'D'. Also, if only S21 measurements are being made and you change
> parameters, the new firmware allows you to perform a 'Through' calibration
> without needing to do a full SOLT calibration.
>
> The modern interface introduced by DiSlord and OneOfEleven on the NanoVNA
> finally makes its appearance on the V2.
>
> Probably some other small features like the addition of 'Q Factor' that I
> missed.
>
>
>
I port Q factor and UI code from NanoVNA to V2 in this one of my PR to code. also fix format and update for calibration status.
NanoVNA-App not support data exchange format for V2
==================================
About data exchange, V2 use 1024 uncalibrated points for CPU exchange, this need a lot of memory. But as my H4 test exchange speed not depend from points count (if use binary bormat and not apply calibration) i have ~470 points/sec speed exchange in 101 points at one time or 465 points/sec for 401 for get 8k points from device (internal device measure speed ~ 570 points/sec)
This memory can be used for increase device points count from 201 to 301-401 points. And for CPU exchange use it.
Thanks Herb. I did all that years back with various cell phones, installing custom build ROMs and such. I can wait for the official versions. What bugs me is the number of forks these things can take. It's wonderful to be able to re-engineer a product to specific needs or to make updates and bug fixes but it gets hard to follow all the chains. At this point I'm not exactly sure who makes the official firmware for whatever the version is I have from R&L. I'll have to play with it and write down the specs from the info tab and try to follow along.
Like I say, it's great we can do that but if there is an official version, I'll wait it out, unless the original developers stop at some point, which inevitably happens.
Thanks for the info. I'll be saving this thread.
Sean
Spell checked by the NSA.
On Fri, Sep 11, 2020 at 9:39 AM, hwalker<herbwalker2476@gmail.com> wrote: On Fri, Sep 11, 2020 at 06:23 AM, mchenryproj wrote:
Same as Mike here. My SAA2N arrived yesterday. I'm sure it will be functional as is but Mike, if you see any significant improvements with a particular firmware for that particular device I'm sure the community would like to know about it - or at the very least, I would like to know about it
Sean,
If you look back through the "new release of 09092020 for V2_2" topic messages you'll find that changes to the user interface (UI) and firmware bug fixes make the new firmware well worth upgrading to. The caveat is that the firmware is not yet an official release, so if you install it you should consider yourself to be a voluntary beta tester.
I enjoy being one of the first to try out a new feature - even if it means I may need to re-load the firmware a few times while the developer is working things out. If that's not your bag of tea then you might want to wait for the official GitHub release before doing a firmware update.
- Herb
Sorry, looks like there was a delay in groups.io sending me new member
approvals, I have everyone approved now.
There is a table here that shows what device variants there are and what
firmware variant to use:
https://github.com/nanovna/NanoVNA-V2-firmware/blob/master/firmware_chooser.png
If there are still S21 gain errors with the last firmware I posted,
select CONFIG > DMESG in the menu, and post the messages that start with
"BBGAIN".
Would anyone know which version the 4 inch SAA2N sold by R&L would be? If not
now can I determine the version?
R&L ordered 100 of them and they quickly sold out.
Mike N2MS
> On 09/11/2020 10:08 AM OwO <
[owowowowo123@outlook.com](mailto:owowowowo123@outlook.com)> wrote:
>
>
>
>
>
>
>
> Sorry, looks like there was a delay in groups.io sending me new member
>
> approvals, I have everyone approved now.
>
>
>
>
> There is a table here that shows what device variants there are and what
>
> firmware variant to use:
>
>
<https://github.com/nanovna/NanoVNA-V2-firmware/blob/master/firmware_chooser.png>
>
>
>
>
> If there are still S21 gain errors with the last firmware I posted,
>
> select CONFIG > DMESG in the menu, and post the messages that start with
>
> "BBGAIN".
>
>
>
>
On Fri, Sep 11, 2020 at 07:36 AM, n2msqrp wrote:
Would anyone know which version the 4 inch SAA2N sold by R&L would be? If not now can I determine the version?
=====================================
Mike,
In the firmware chooser table that Gabriel has provided it is the V2_2 version.
- Herb
On Fri, Sep 11, 2020 at 07:36 AM, n2msqrp wrote:
Would anyone know which version the 4 inch SAA2N sold by R&L would be? If not now can I determine the version?
R&L ordered 100 of them and they quickly sold out.
================================================================
Mike,
The tinySA spectrum analyzers sold out just as quickly. Someone must have bulk pre-ordered both devices.
- Herb
As for my order, it was an upgrade replacement from an H4 I bought from them that arrived damaged. My SAA2N has been on order for a few weeks but arrived yesterday.
I would look at their web page every few days until I saw they were available again then sent them an email reminder about the return/swap.
I actually work for a rival company in the Amateur Radio field but those guys are OK. Fast and friendly. (As is my place by the way, we just don't carry those)
Sean
Spell checked by the NSA.
On Fri, Sep 11, 2020 at 10:46 AM, hwalker<herbwalker2476@gmail.com> wrote: On Fri, Sep 11, 2020 at 07:36 AM, n2msqrp wrote:
Would anyone know which version the 4 inch SAA2N sold by R&L would be? If not now can I determine the version? R&L ordered 100 of them and they quickly sold out. ================================================================
Mike,
The tinySA spectrum analyzers sold out just as quickly. Someone must have bulk pre-ordered both devices.
- Herb
> About data exchange, V2 use 1024 uncalibrated points for CPU exchange,
> this need a lot of memory. But as my H4 test exchange speed not depend
> from points count (if use binary bormat and not apply calibration) i
> have ~470 points/sec speed exchange in 101 points at one time or 465
> points/sec for 401 for get 8k points from device (internal device
> measure speed ~ 570 points/sec)
> This memory can be used for increase device points count from 201 to
> 301-401 points. And for CPU exchange use it.
> _._,_._,_
The 1024-entry array stores ECAL data which is frequency dependent, so
every time sweep parameters are changed the device has to do a full ECAL
which slows down the first sweep by a factor of 2. That's why segmented
sweep isn't recommended on the V2. Although plus4 gets rid of ecal
completely because it uses a different reflection bridge design that has
high native directivity and low device to device variance. But this new
bridge design was only verified recently so unfortunately it won't make
it to V2_2 and V2 plus for some time, so ECAL is still needed.
Thanks. I will play with the version on the unit for now. I will then decide
to try the beta or official release.
Mike N2MS
> On 09/11/2020 10:41 AM hwalker <herbwalker2476@gmail.com> wrote:
>
>
>
>
>
>
>
> On Fri, Sep 11, 2020 at 07:36 AM, n2msqrp wrote:
>
>
>
> Would anyone know which version the 4 inch SAA2N sold by R&L would be? If
not now can I determine the version?
>
>
>
>
> =====================================
>
> Mike,
> In the firmware chooser table that Gabriel has provided it is the V2_2
version.
>
> \- Herb
_._,_._,_
* * *
Where can one find the explanation of differences/new features of
the V2 Plus and V2 plus4 variants?
I presume these are still unreleased and in testing?
On Fri, 11 Sep 2020 at 16:08, OwO <OwOwOwOwO123@outlook.com> wrote:
I have an S-A-A-2 VNA2_2 that I purchased from R&L Electronics. None of these versions of the firmware work with my VNA. The only version that I have found that works is binary-ili9341.bin from release 20200619 ( https://github.com/nanovna/NanoVNA-V2-firmware/tree/20200619 ). The analyzer is very nice but it sure is hard to figure out what works with mine since there are so many versions of everything out there.
Terry
On Fri, Sep 11, 2020 at 08:11 PM, Terry wrote:
>
> I have an S-A-A-2 VNA2_2 that I purchased from R&L Electronics. None of
> these versions of the firmware work with my VNA. The only version that I
> have found that works is binary-ili9341.bin from release 20200619 (
> https://github.com/nanovna/NanoVNA-V2-firmware/tree/20200619 ). The
> analyzer is very nice but it sure is hard to figure out what works with
> mine since there are so many versions of everything out there.
Terry,
Gabriel released a firmware_chooser table on her GitHub page which makes choosing the correct firmware for each version V2 straight forward. There are only 3 versions of the V2 (V2_2, V2 Plus, and V2 Plus 4). Each version, excluding the V2 Plus 4, can either be fitted with a 2.8", 3.2", or 4" display module. The V2 Plus 4 can only be fitted with a 4" display module.
The V2 Plus and V2 Plus 4 are currently under development by Gabriel and the V2 Plus and V2 Plus 4 binaries are pre-release versions.
The binaries for the V2_2 are applicable to all currently produced V2 products. The V2 products with 2.8" or 3.2" displays require the V2_2-ili9341.bin binary. The V2 products with 4" displays require the V2_2-st7796.bin binary.
Your 2.8" V2 device should work with the V2_2-ili9341.bin binary.
- Herb
On Fri, Sep 11, 2020 at 08:11 PM, Dragan Milivojevic wrote:
>
> Where can one find the explanation of differences/new features of
> the V2 Plus and V2 plus4 variants?
> I presume these are still unreleased and in testing?
>
Dragan,
The V2 Plus and V2 Plus 4 will be Gabriel's first follow-up products to the SAA-2 (V2). In order to retain full copyright and distributing control, Gabriel has indicated that these, and future products, will be commercial releases and only the firmware will be open source.
I think that is a smart decision on her part since open source hardware projects seem to only induce contributions on the software and firmware side, while the hardware side is just copied and manufactured by others without further technical innovation.
Since the V2 Plus and V2 Plus 4 will be commercial products, I don't expect Gabriel will reveal much more info than she already has prior to each product's launch. The following is what she has posted on this forum:
V2 Plus will have a small improvement over the V2 on sweep speed (200 points/s) and a bit lower noise.
V2 Plus 4 is the 4 inch version, working at 400 points/s sweep (highest that the UI plotting code can handle). It will come with a 3D enclosure.
The V2 Plus 4 gets rid of ecal completely because it uses a different reflection bridge design that has high native directivity and low device to device variance. The bridge design was not verified in time to make it to the V2 plus, so ECAL will still be needed.
- Herb
Well, we can make an educated guess on the V2 Plus from what has been published. It looks like it will use a higher IF frequency (and higher ADC sampling rate) to get higher sweep rate/lower noise, so the bandwidth of the IF amp section will need to be increased as well. The good news is that you could probably upgrade that yourself by changing a few passives. There may be other changes that are not as immediately obvious of course.
K bn
JF
Herb,
Thanks for the reply. Unfortunately v2_2-ili9341.bin doesn't seem to work properly with my VNA. The display looks normal when I turn the unit on. When I tap the screen to bring up the menu the menu font looks different. Then when I tap any of the menu items to select it the menu goes away and I'm back to the start up screen. It doesn't matter which button I choose.
I can connect the VNA to my PC and run it with VNA_QT and everything works perfectly.
Not sure what I'm doing wrong but I hope it's something simple.
Terry
Thanks Herb, I guess I will wait for the rest of the lineup to show up.
Hopefully by that time they will actually sort out the shipping so that
I can actually order one that I can be sure it is built properly.
On Sat, 12 Sep 2020 at 14:30, hwalker <herbwalker2476@gmail.com> wrote:
Try to do the screen calibration.
On Sat, 12 Sep 2020 at 16:16, Terry <terry.w7ami@gmail.com> wrote:
On Sat, Sep 12, 2020 at 07:21 AM, Dragan Milivojevic wrote:
>
> Try to do the screen calibration.
>
Terry wrote: Unfortunately v2_2-ili9341.bin doesn't seem to work properly with my VNA. The display looks normal when I turn the unit on. When I tap the screen to bring up the menu the menu font looks different. Then when I tap any of the menu items to select it the menu goes away and I'm back to the start up screen. It doesn't matter which button I choose.
=============================================
Terry,
Dragan is probably right. When I installed the new release I had similar touch screen issues and had to power cycle the V2 and do a touch screen calibration. From my previous post:
" The only issue I had after loading the new V2_2 binary is touch calibration was way off and I had to use the buttons to access the touch calibration button."
Don't forget to do a save after doing the touch test verification.
- Herb
Dragan,
That fixed the issue but it wasn't straight forward. I had to tap the screen to bring up the menu and the tap on various places on the left hand side of the screen until I found the area that corresponded to the "Config" button. Then repeat the process to find the area that the "Touch Cal" button was responding to.
Any way, problem solved. Thank you very much.
Terry
You are welcome.
As Herb wrote you can use the buttons to get to that option next time.
Small inconvenience when using the non official version of hardware.
On Sat, 12 Sep 2020 at 18:20, Terry <terry.w7ami@gmail.com> wrote:
Dragan and Herb,
Thanks. The buttons would have been easier. Thanks again for your help.
Terry
Different display modules have different connection to Touch module
So correct default touch calibration settings for some modules - inverted for another.
On flash firmware config reset (for apply color settings in new UI stored in config section)
After Touth calibration and save, no need more recalibrate (config not reset on new update) and all should work
On Fri, Sep 11, 2020 at 07:08 AM, OwO wrote:
If there are still S21 gain errors with the last firmware I posted, select CONFIG > DMESG in the menu, and post the messages that start with "BBGAIN"
==============================================
Gabriel,
I 'm not sure if "s21 gain errors you referred to are the "first point issue" or the "1 dB trace toggling issue" Kurt Poulsen reported. After updating to V2_2 release 09092020 for the 4" display, the "first point issue" was resolved.
At the time, I couldn't reproduce the "1 dB trace toggling issue" Kurt Poulsen reported but today while testing a 15dB attenuator it reared its head.
The BBGAIN values if they are of interest are:
BBGAIN 0: 0.00 dB
BBGAIN 1: -5.55 dB
BBGAIN 2: -9.35 dB
BBGAIN 3: -18.44 dB
The attenuator is a vintage Stoddart model 90511-15. There is not much data on the web other than it is a 50ohm, 15dB attenuator. I re-tested some attenuators that previously did not exhibit the toggling behavior and they were all still fine. Putting the Stoddart attenuator back into the set-up returned the toggling behavior.
The Stoddart attenuator is possibly phase unstable and V2 does not like it. It actually locked up the display while I was dragging a second marker to to document the toggling levels. I had the perform a power cycle to re-gain control. The attenuator is definitely in going into my questionable component bin.
Anyway, I'm chalking the issue up as a bad component since I could not repeat it with known good components.
I hope your V2 Plus and V2 Plus 4 products finally include a screen shot command as it makes these issues easier to document than taking a photo.
- Herb
Hi Terry and others facing this problem
By using the buttons you can step thru the menu system and chose the touch screen calibration then do the save and it work as expected
Kind regards
Kurt
Fra: NanoVNAV2@groups.io <NanoVNAV2@groups.io> På vegne af Terry
Sendt: 12. september 2020 18:21
Til: NanoVNAV2@groups.io
Emne: Re: [nanovnav2] The new release of 09092020 for V2_2
Dragan,
That fixed the issue but it wasn't straight forward. I had to tap the screen to bring up the menu and the tap on various places on the left hand side of the screen until I found the area that corresponded to the "Config" button. Then repeat the process to find the area that the "Touch Cal" button was responding to.
Any way, problem solved. Thank you very much.
Terry
> The BBGAIN values if they are of interest are:
> BBGAIN 0: 0.00 dB
> BBGAIN 1: -5.55 dB
> BBGAIN 2: -9.35 dB
> BBGAIN 3: -18.44 dB
The last BBGAIN value is incorrect, it should be around -19.7dB. I can't
think of any explanation for the 1dB jump yet especially since the
firmware calibrates BB gain on startup so any static errors shouldn't
affect measurements. If this issue shows up on multiple devices it's
unlikely soldering related. I haven't seen this bug on my devices yet,
but if anyone can reproduce it on a Tindie-bought one please email me
and I'll walk you through some further troubleshooting.
i do know changes ... yes higher if so a few components do change in bb
amp (sorry i was told NOT to publish)
dg9bfc sigi
Am 12.09.2020 um 12:55 schrieb switchabl@mailbox.org:
Hi Gabrielle
I am using the Tindie version presently and will give it a try with a continuously variable attenuator I have, but how to derive the BBGAIN 1 to 4 when connected to the VNA-QT ?
Kind regards
Kurt
The BBGAIN is only visible on the device screen in the DMESG menu, it
doesn't change during operation (it is measured once at bootup) so just
check the BBGAIN before connecting nanovna-qt.
On 13/09/2020 17:55, Kurt Poulsen wrote:
On Sat, Sep 12, 2020 at 03:02 PM, hwalker wrote:
>
> It actually locked up the display while I was dragging a second marker to
> to document the toggling levels. I had the perform a power cycle to
> re-gain control. The attenuator is definitely in going into my
> questionable component bin.
No it V2 problem. Come from fast SPI speed switch for get Touch position and draw marker on LCD.
In this case V2 hang on long time marker drag (more fast on 4` and little more slow on 2.8`)
Dear Herb,
I think you need to calibrate the touch screen. The current default calibration must be mirrored.
To get to the screen calibration you will have to navigate with the push buttons. It took me several attempts (when I upgraded the 2.8” screen for a 3.2” one). Once you get there, when it says touch for the top left, touch on the bottom right and likewise for the bottom right, touch top left.
Try it.
steve L. G7PSZ
On Sun, Sep 13, 2020 at 04:26 AM, Stephen Laurence wrote:
>
> Dear Herb,
>
> I think you need to calibrate the touch screen. The current default
> calibration must be mirrored.
>
> To get to the screen calibration you will have to navigate with the push
> buttons. It took me several attempts (when I upgraded the 2.8” screen for
> a 3.2” one). Once you get there, when it says touch for the top left,
> touch on the bottom right and likewise for the bottom right, touch top
> left.
>
>
Steve,
I think you had another user in mind. Right after Gabriel posted the new releases I commented that I had to perform a touch screen calibration using the push buttons because my screen calibration was so far off. Still, thanks for your input.
- Herb
I tried with a step attenuator today and I don't quite see 1dB errors, but I can get the S21 to jump by 0.3dB.
NanoVNA V2_2 from Tindie
NanoVNA-Qt, SOLT calibration
Sweep: 10-3000MHz, 201 points, nWait=-1, nValues=1
DUT: Minicircuits ZX76-31 step attenuator (31dB in 1dB steps), at 17dB attenuation (+ 1.5-3.0dB insertion loss)
Firmware: 22a90b9 (from this thread), cw-branch based on b8e793d (both show the exact same behaviour)
BBGAIN 0: 0.00 dB
BBGAIN 1: -5.66 dB
BBGAIN 2: -9.56 dB
BBGAIN 3: -19.88 dB
Every second sweep is lower by a constant offset of 0.3dB. The offset seemed be quite stable across several restarts (and two firmware updates).
On Sun, Sep 13, 2020 at 05:40 AM, @switchabl wrote:
>
> ... I tried with a step attenuator today and I don't quite see 1dB errors,
> but I can get the S21 to jump by 0.3dB.
>
> NanoVNA V2_2 from Tindie ...
The toggling trace issue has only been reported on the 4" SAA-2N. The 2.8" SAA-2 is fine.
- Herb
Well, mine definitely does it. It is only 0.3dB and maybe this is actually the accuracy limit of the gain calibration, but it is there and seems quite reproducible.
0.3dB gain error might be due to noise during gain calibration; I think
there needs to be more averaging during gain cal, I'll look into it
tomorrow. Is the error always 0.3dB or does it change if you reboot the
device?
On 14/09/2020 01:06, switchabl@mailbox.org wrote:
As far as I can tell it is relatively stable. I flashed to the newest firmware (and back afterwards), so I rebooted several times and it didn't change noticably (see the message below for more details).
Hi Gabrielle
No it has been exactly 1dB when I use
VNA-QT but now when using the stand alone SAA-2N the jump is 1dB and the static error with levels below “threshold/triggerlevel” is +0.8/+0.9dB. As you see on the attached picture also happen above the 148MHz. The continuously variable attenuator I use must be adjusted very sensitive to provoke the correct level where the phenomena happens.
Kind regards
Kurt
Fra: NanoVNAV2@groups.io <NanoVNAV2@groups.io> På vegne af OwO
Sendt: 13. september 2020 19:19
Til: NanoVNAV2@groups.io
Emne: Re: [nanovnav2] The new release of 09092020 for V2_2
0.3dB gain error might be due to noise during gain calibration; I think there needs to be more averaging during gain cal, I'll look into it tomorrow. Is the error always 0.3dB or does it change if you reboot the device?
On 14/09/2020 01:06, switchabl@mailbox.org <mailto:switchabl@mailbox.org> wrote:
Well, mine definitely does it. It is only 0.3dB and maybe this is actually the accuracy limit of the gain calibration, but it is there and seems quite reproducible.
Hi Gabrielle
I updated the SAA-2N to the unofficial version you published on Friday 11 and it behaves much much better. Still there is the problem with the error for the s21 level below a certain input threshold to port 2, as seen on attached image. However if I calibrate to a span from 130 to 150MHz I can no longer provoke it (I could with the June 19 version and very dramatic spike at 148MHz and first point jump either positive or negative pending input level) but by the scan from 100 to 900MHz I can provoke it. As before a critical adjustment of the continuous variable attenuator needed.
The switching is at 148MHz and also a bit higher as seen and a 1db jump
The touch screen calibration is still an issue to solve button usage needed.
Kind regards
Kurt
Fra: NanoVNAV2@groups.io <NanoVNAV2@groups.io> På vegne af OwO
Sendt: 13. september 2020 19:19
Til: NanoVNAV2@groups.io
Emne: Re: [nanovnav2] The new release of 09092020 for V2_2
0.3dB gain error might be due to noise during gain calibration; I think there needs to be more averaging during gain cal, I'll look into it tomorrow. Is the error always 0.3dB or does it change if you reboot the device?
On 14/09/2020 01:06, switchabl@mailbox.org <mailto:switchabl@mailbox.org> wrote:
Well, mine definitely does it. It is only 0.3dB and maybe this is actually the accuracy limit of the gain calibration, but it is there and seems quite reproducible.
@switchabl can you try this debug firmware and see if the 0.3dB jump is
correlated with changes in gain step (shown in S11 trace):
https://groups.io/g/NanoVNAV2/message/91
On 14/09/2020 01:39, switchabl@mailbox.org wrote:
Hi Gabrielle
I did also the test. Image 1476 is before updating to the test version and marker 2 represent the right level so the switching from wrong level to the left is so to speak delayed
Test version is image 1477 and as not able to calibrate the trace is slanted and the S11 follow S21
Kind regards
Kurt
Fra: NanoVNAV2@groups.io <NanoVNAV2@groups.io> På vegne af OwO
Sendt: 14. september 2020 06:13
Til: NanoVNAV2@groups.io
Emne: Re: [nanovnav2] The new release of 09092020 for V2_2
@switchabl can you try this debug firmware and see if the 0.3dB jump is correlated with changes in gain step (shown in S11 trace): https://groups.io/g/NanoVNAV2/message/91
On 14/09/2020 01:39, switchabl@mailbox.org <mailto:switchabl@mailbox.org> wrote:
As far as I can tell it is relatively stable. I flashed to the newest firmware (and back afterwards), so I rebooted several times and it didn't change noticably (see the message below for more details).
Hi Gabrielle
Just a comment. Even when uncalibrated for the debug version the problem happen for the same dB attenuator setting being 15dB. So it has to do with the absolute level at port2. I add one more image which 16dB attenuator setting and there is a very small bump on S21 in the start for the same period of the sweep
Kind regards
Kurt
Fra: NanoVNAV2@groups.io <NanoVNAV2@groups.io> På vegne af OwO
Sendt: 14. september 2020 06:13
Til: NanoVNAV2@groups.io
Emne: Re: [nanovnav2] The new release of 09092020 for V2_2
@switchabl can you try this debug firmware and see if the 0.3dB jump is correlated with changes in gain step (shown in S11 trace): <https://groups.io/g/NanoVNAV2/message/91> https://groups.io/g/NanoVNAV2/message/91
On 14/09/2020 01:39, <mailto:switchabl@mailbox.org> switchabl@mailbox.org wrote:
As far as I can tell it is relatively stable. I flashed to the newest firmware (and back afterwards), so I rebooted several times and it didn't change noticably (see the message below for more details).
To reply to this topic, join https://groups.io/g/NanoVNAV2
