|
Hi there,
I'm new to NanoVNA and I hope, I do not ask stupid questions, please excuse me, if this is the case.
I got my NanoVNA H4 last week and played around with it since that time. Today I performed a firmware update using DisLord's version 1.0.69. Everything seemed to work after the update but I noticed very quickly, that after some time (5-10 min) all four traces start freezing or at least the refresh rate drops down to nearly 1 refresh per 1.5 minute.
In that situation, when I switch to the Bandwith menu and go for 333 Hz, the blue line on the top of the screen moves extremely slow from the left to the right. One cycle is approx. the above mentioned 1.5 minutes.
The issue is only with the trace refresh rate, navigating through the menus is smooth and responsive.
The only way to get the NanoVNA back to work, is to perform a "clear config / reset" from the config menu. But in that case, I loose all my calibration and config data.
I didn't see this behaviour with the original fw and my thoughts were, that something could be wrong with the 1.0.69 version. I downgraded to the previous Dislord's fw 1.0.64 but also with that version I experience the same issue.
The occurrence of the issue is random. Sometimes it occurs immediately after I switch the device on and sometimes it happens after 10 minutes of work with it. One time, I also faced the issue during a calibration session. It occurred in that moment, the device was capturing the "Thru" (Ch1 - Ch2) data. On the top of the calibration screen, you could see that the blue line moved extremely slow.
I already searched the Wiki and some older threads for some advices but I couldn't find something adequate.
Is there anyone, who experienced the same issue? Because I coulnd't find something in all the threads around that firmware, I have the feeling, that the issue is up to my device :-(.
I am grateful for any help and tips.
Thanks a lot,
Gerd
|
I have to wonder why you have loaded such an old version . . . 1.2.00 is the current build. Have you tried that yet?
toggle quoted message
Show quoted text
On July 4, 2022 1:32:54 PM CDT, Gooser5000 <g.soffner@...> wrote: Hi there,
I'm new to NanoVNA and I hope, I do not ask stupid questions, please excuse me, if this is the case.
I got my NanoVNA H4 last week and played around with it since that time. Today I performed a firmware update using DisLord's version 1.0.69. Everything seemed to work after the update but I noticed very quickly, that after some time (5-10 min) all four traces start freezing or at least the refresh rate drops down to nearly 1 refresh per 1.5 minute.
In that situation, when I switch to the Bandwith menu and go for 333 Hz, the blue line on the top of the screen moves extremely slow from the left to the right. One cycle is approx. the above mentioned 1.5 minutes.
The issue is only with the trace refresh rate, navigating through the menus is smooth and responsive.
The only way to get the NanoVNA back to work, is to perform a "clear config / reset" from the config menu. But in that case, I loose all my calibration and config data.
I didn't see this behaviour with the original fw and my thoughts were, that something could be wrong with the 1.0.69 version. I downgraded to the previous Dislord's fw 1.0.64 but also with that version I experience the same issue.
The occurrence of the issue is random. Sometimes it occurs immediately after I switch the device on and sometimes it happens after 10 minutes of work with it. One time, I also faced the issue during a calibration session. It occurred in that moment, the device was capturing the "Thru" (Ch1 - Ch2) data. On the top of the calibration screen, you could see that the blue line moved extremely slow.
I already searched the Wiki and some older threads for some advices but I couldn't find something adequate.
Is there anyone, who experienced the same issue? Because I coulnd't find something in all the threads around that firmware, I have the feeling, that the issue is up to my device :-(.
I am grateful for any help and tips.
Thanks a lot,
Gerd
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
Hi TIm,
thank's a lot for your response. No, I didn't try the 1.2.00 build. The 1.0.69 was the most recent firmware, I found in the files section of this group. Could you please provide a link, where I can find the 1.2.00?
Thank you very much for your help!
|
toggle quoted message
Show quoted text
On July 4, 2022 2:42:49 PM CDT, Gooser5000 <g.soffner@...> wrote: Hi TIm,
thank's a lot for your response. No, I didn't try the 1.2.00 build. The 1.0.69 was the most recent firmware, I found in the files section of this group. Could you please provide a link, where I can find the 1.2.00?
Thank you very much for your help!
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
|
|
Gerd and others,
Use the nano with the firmware that comes with it. It does most of the things a ham needs out of the box. THEN when you are very familiar with it you can update the firmware. Why is everyone so willing to mess the the basics before learning how to use a new instrument? Not the best use of a new piece of test gear, at least in my opinion.
Dave K8WPE
David J. Wilcox¡¯s iPad
toggle quoted message
Show quoted text
On Jul 4, 2022, at 2:33 PM, Gooser5000 <g.soffner@...> wrote:
?Hi there,
I'm new to NanoVNA and I hope, I do not ask stupid questions, please excuse me, if this is the case.
I got my NanoVNA H4 last week and played around with it since that time. Today I performed a firmware update using DisLord's version 1.0.69. Everything seemed to work after the update but I noticed very quickly, that after some time (5-10 min) all four traces start freezing or at least the refresh rate drops down to nearly 1 refresh per 1.5 minute.
In that situation, when I switch to the Bandwith menu and go for 333 Hz, the blue line on the top of the screen moves extremely slow from the left to the right. One cycle is approx. the above mentioned 1.5 minutes.
The issue is only with the trace refresh rate, navigating through the menus is smooth and responsive.
The only way to get the NanoVNA back to work, is to perform a "clear config / reset" from the config menu. But in that case, I loose all my calibration and config data.
I didn't see this behaviour with the original fw and my thoughts were, that something could be wrong with the 1.0.69 version. I downgraded to the previous Dislord's fw 1.0.64 but also with that version I experience the same issue.
The occurrence of the issue is random. Sometimes it occurs immediately after I switch the device on and sometimes it happens after 10 minutes of work with it. One time, I also faced the issue during a calibration session. It occurred in that moment, the device was capturing the "Thru" (Ch1 - Ch2) data. On the top of the calibration screen, you could see that the blue line moved extremely slow.
I already searched the Wiki and some older threads for some advices but I couldn't find something adequate.
Is there anyone, who experienced the same issue? Because I coulnd't find something in all the threads around that firmware, I have the feeling, that the issue is up to my device :-(.
I am grateful for any help and tips.
Thanks a lot,
Gerd
|
A lot of folks, myself included, like to keep firmware current, as there are many improvements and bug fixes in the new releases. There is little that is more frustrating than trying to learn a new instrument while also dealing with bugs.
The first thing I do when I get a commercial instrument into the lab is to check that the firmware is up to date, or make it so.
When you call for tech support, the first question is usually, "what firmware revision are you running?"
73, Don N2VGU
|
I'm in the 'upgrade 1st' column. You are probably going to want to learn the upgrade procedure anyway and that's not tied to operating proficiency. In addition to bug fixes, newer FW will better track written documentation like menu trees.
|
Why
It is very simple. It often happens that the update of an on -board ? software goes wrong and that we can no longer go back. It is traumatic.
|
As am I. Why learn something outdated and then pootentially have to releard the current version. Do it once . . . .
toggle quoted message
Show quoted text
On July 5, 2022 11:07:48 AM CDT, Rebel Thompson <hamnotspam@...> wrote: I'm in the 'upgrade 1st' column. You are probably going to want to learn the upgrade procedure anyway and that's not tied to operating proficiency. In addition to bug fixes, newer FW will better track written documentation like menu trees.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
On Tue, Jul 5, 2022 at 11:24 AM, F1AMM wrote:
Why
It is very simple. It often happens that the update of an on -board ?
software goes wrong and that we can no longer go back. It is traumatic.
You can dump current firmware on NanoVNA Use DFU mode and Upload Action (and set firmware filename) For load new firmware need use Upgrade Action and select file.
|
If it ain't broke, don't fix it. At least not until you know it well enough to know what needs to be fixed. I have had too many cases where a software update broke more than it fixed.
SherpaDoug WA1UWP
|
But old firmware DOES have "broke" stuff in the form of bugs, etc., that is why the authors push out the new releases.
73, Don N2VGU
|
I understand these comments but have read so many emails where the questioner was advised to go back to a certain firmware because the ¡°latest greatest¡± wasn¡¯t working. Just my opinion. Some are luckier than others. I tend to be unlucky with upgrades.
Dave K8WPE
David J. Wilcox¡¯s iPad
toggle quoted message
Show quoted text
On Jul 5, 2022, at 8:00 PM, Donald S Brant Jr <dsbrantjr@...> wrote:
?But old firmware DOES have "broke" stuff in the form of bugs, etc., that is why the authors push out the new releases.
73, Don N2VGU
|
Hello
I had the same problem you have.
For me, with a H4 also, FW originally was 1.0.39.
Then i updated and up until 1.0.53 the traces work at "normal" speed. (i tested this, starting from 1.0.69, it was slow like you describe it. 1.0.64 doesn't work at all on my H4, black screen)
I tested clear config and restart with 1.2.00, no luck. (i reduced the sweep points to 51 and it took "only" about 20 sek for a sweep, but no useful readout connected to my DemoKit 6.5MHz BSF)
Then i saw in the vna beta group, that there is a 1.2.02 version.
I installed it and heureka, it sweeps even faster, than 1.0.53.
I hope that helps
73 de HB9SFG
|
On Wed, Jul 6, 2022 at 10:26 PM, <t.rohner@...> wrote:
HB9SFG
Hello and many thanks for the infomation. Good to hear, there is a solution that fixes the problem. The 1.0.53 is also for my Nano the latest version that worked without the mentioned issue. Recently I updated to 1.2.00, which is much more stable but also with this version I faced the same issue. The problem seems to be hardware dependent. I will look for version 1.2.02 and give it a try. Many thanks and 73 Gerd
|
Gooser5000
David Wilcox K8WPE
Donald S Brant Jr
Douglas Butler