|
My H4 arrived very fast. Ordered it directly at the hugen store on alibaba.
Unfortunately when turning it on it stops and freezes at the blue boot screen.
Switching to DFU mode worked (good not zo need a menu for that!) and I was able to flash to the 18.01.2020 H4 firmware without any problems.
Problem remains now showing the new firmware in the blue boot screen but freezing.
Letting the battery going to zero and the reloading brought also no results.
Any ideas?
|
I have heard that there are cases where the touch display is "pinched" by the case and this may result in faulty touch screen operation.
Maybe try taking it out of the case and then try rebooting.
Also try disconnecting the battery and then reconnecting to see if that clears the processor.
If you are on Windows 10 it will load the driver when you plug it in. If not you will need to load the driver and this is described in this groups Wiki. When plugged in should see the COM port in Device Manager. Then try to use a Terminal program like Putty or TeraTerm to connect to the Nano and see if it will respond to terminal commands (see Wiki). Some problems are resolved by "clearconfig 1234".
Hopefully Hugen or one of the other H-4 gurus will have some suggestions.
Roger...
|
I have heard that there are cases where the touch display is "pinched" by the
case and this may result in faulty touch screen operation.
Maybe try taking it out of the case and then try rebooting. Good call. Also try disconnecting the battery and then reconnecting to see if that clears
the processor. No, that would not be useful, given that it boots to the version screen. FWIW, the power switch already disconnects power to the processor. If you are on Windows 10 it will load the driver when you plug it in. If not
you will need to load the driver and this is described in this groups Wiki.
When plugged in should see the COM port in Device Manager. Then try to use a
Terminal program like Putty or TeraTerm to connect to the Nano and see if it
will respond to terminal commands (see Wiki). Some problems are resolved by "clearconfig 1234". Yes, I would try that next, if unpinching the display does not help. Be aware that "clearconfig 1234" does not take effect until after reboot; it resets flash for data variables, but NOT those already loaded into active memory.
|
Oristo,
Thanks for clarifying some of the things that might be wrong. I hope he gets it working. It must be very frustrating for Hans-Martin to finally get his new H4 and it is not working...
Roger
|
On Thu, Jan 30, 2020 at 10:52 PM, Hans-Martin Kurka wrote:
My H4 arrived very fast. Ordered it directly at the hugen store on alibaba.
Unfortunately when turning it on it stops and freezes at the blue boot screen.
Switching to DFU mode worked (good not zo need a menu for that!) and I was
able to flash to the 18.01.2020 H4 firmware without any problems.
Problem remains now showing the new firmware in the blue boot screen but
freezing.
Letting the battery going to zero and the reloading brought also no results.
Any ideas?
Hi Hans-Martin, Probably the problem with you is what I had. Unfortunately, the plastic box rests on the touch screen, causing pressure. As a result, there is a malfunction. This disorder may take different forms: the home screen does not appear if you sign in, another feature will not work I was logged in but the menu switch had only one impression, no other option. The solution I saw was lifting the plastic on the front. If this works well, you can remove the traces of experimentation so far: If there was no upgrade, as it was not working, it is advisable to enter clearconfig 1234 with a terminal program. I fixed the bug like this: see /g/nanovna-users/message/10333I hope I could help you. 73, Gyula HA3HZ
|
Really annoying error on a new device. However, the fault is not an electrical fault.
This is a mechanical fault because the tangent is forced to operate by an imaginary pressure.
|
|
|
Ok thank you!
Highly appreciated.
I will try that in the next days as I am not that much familiar with it.
--
Am 31.01.20, 09:40 schrieb Gyula Molnar <gyula.ha3hz@...>:
toggle quoted message
Show quoted text
|
I am very sorry for the failure caused by our insufficient assembly accuracy. I have noticed this problem and will improve it in future products. Unfortunately, factories in China are currently unable to start production of the revised version. You can modify it as suggested by Gyula Molnar /g/nanovna-users/message/10369. Sorry again for our mistake. hugen
|
Hi Hugen Please also take action on the opening for the USB C connection which is blocked for entry by excess material of the upper part of the case. The hole need enlargement by milling off the "lip". Also what to do about many stray trace / dots from previous traces ? Kind regards Kurt -----Oprindelig meddelelse----- Fra: [email protected] < [email protected]> P? vegne af hugen@... Sendt: 31. januar 2020 15:23 Til: [email protected]Emne: Re: [nanovna-users] #nanovna-h4 stops at boot screen I am very sorry for the failure caused by our insufficient assembly accuracy. I have noticed this problem and will improve it in future products. Unfortunately, factories in China are currently unable to start production of the revised version. You can modify it as suggested by Gyula Molnar /g/nanovna-users/message/10369. Sorry again for our mistake. hugen
|
On Fri, Jan 31, 2020 at 04:05 PM, Kurt Poulsen wrote: Hi Hugen Please also take action on the opening for the USB C connection which is blocked for entry by excess material of the upper part of the case. The hole need enlargement by milling off the "lip". Also what to do about many stray trace / dots from previous traces ? ============================================== Kurt, I submitted an issue report to hugen about the USB-C port opening along with the center frequency above 1 GHZ lock-up at . In my "Hints and Kinks" for the NanoVNA-H4, /g/nanovna-users/message/10354 , I noted the stray artifacts remaining from previous sweeps. Some times the only way to clear a stray artifact is to manually force a refresh by going into the Display->Trace menu and deselecting and reselecting a trace. I really only need to do this if I am performing a screen capture and want to clear any stray artifacts before hand. After updating to the January 18th, 2020 release, I don't seem to get the really persistent artifacts as often, but they are still there. I'm guessing the firmware currently does not do a complete refresh between sweeps, but with the faster F303 processor I would think it would only be a minimal penalty for doing so. I'm pretty much just waiting for the completion of Chinese New Year before I expect any firmware updates to address the issues. You are the only one besides myself who has complained about the stray display artifacts on this forum, so I haven't submitted a GitHub issue about it to hugen. I don't make it a habit of submitting an issue report until at list one other person has verified it. You can always tell the early users of new hardware or software, they are the ones with a few arrows sticking out of their backs. - Herb
|
On Sat, Feb 1, 2020 at 10:15 AM, hwalker wrote:
On Fri, Jan 31, 2020 at 04:05 PM, Kurt Poulsen wrote:
Hi Hugen
Please also take action on the opening for the USB C connection which is
blocked for entry by excess material of the upper part of the case. The hole
need enlargement by milling off the "lip". Also what to do about many stray
trace / dots from previous traces ?
==============================================
- Herb
Thank you for your feedback. I have manually fixed the shell error, but due to the impact of 2019-nCOV, we need March to start selling the revised version. hugen
|
I untightened the screws of the plastic case a bit today and that already helped and solved the screen blocking!!! So change in the case dimensions will be a next step for further future development as already announced here. Upgrade to 1.2 also without problems Thanks again and take care everyone around the globe and good fortune especially to all the chinese friends involved in nanovna 73 de DK2HM *Gesendet:* Montag, 03. Februar 2020 um 06:40 Uhr *Von:* hugen@... *An:* [email protected]*Betreff:* Re: [nanovna-users] #nanovna-h4 stops at boot screen On Sat, Feb 1, 2020 at 10:15 AM, hwalker wrote:
On Fri, Jan 31, 2020 at 04:05 PM, Kurt Poulsen wrote:
Hi Hugen
Please also take action on the opening for the USB C connection which is
blocked for entry by excess material of the upper part of the case. The hole
need enlargement by milling off the "lip". Also what to do about many stray
trace / dots from previous traces ?
==============================================
- Herb
Thank you for your feedback. I have manually fixed the shell error, but due to the impact of 2019-nCOV, we need March to start selling the revised version. hugen
|
On Wed, Feb 5, 2020 at 02:29 PM, Hans-Martin Kurka wrote:
I untightened the screws of the plastic case a bit today and that already
helped and solved the screen blocking!!!
So change in the case dimensions will be a next step for further future
development as already announced here.
Upgrade to 1.2 also without problems
Thanks again and take care everyone around the globe and good fortune
especially to all the Chinese friends involved in nanovna
Nice to hear that you got it working.. Have fun with your new NanoVNA Roger
|
Hi Herb Thank you for the comment. I like you sense of humor ? Kind regards Kurt -----Oprindelig meddelelse----- Fra: [email protected] < [email protected]> P? vegne af hwalker Sendt: 1. februar 2020 03:16 Til: [email protected]Emne: Re: [nanovna-users] #nanovna-h4 stops at boot screen
On Fri, Jan 31, 2020 at 04:05 PM, Kurt Poulsen wrote: Hi Hugen Please also take action on the opening for the USB C connection which is blocked for entry by excess material of the upper part of the case. The hole need enlargement by milling off the "lip". Also what to do about many stray trace / dots from previous traces ? ============================================== Kurt, I submitted an issue report to hugen about the USB-C port opening along with the center frequency above 1 GHZ lock-up at <> . In my "Hints and Kinks" for the NanoVNA-H4, < /g/nanovna-users/message/10354> /g/nanovna-users/message/10354 , I noted the stray artifacts remaining from previous sweeps. Some times the only way to clear a stray artifact is to manually force a refresh by going into the Display->Trace menu and deselecting and reselecting a trace. I really only need to do this if I am performing a screen capture and want to clear any stray artifacts before hand. After updating to the January 18th, 2020 release, I don't seem to get the really persistent artifacts as often, but they are still there. I'm guessing the firmware currently does not do a complete refresh between sweeps, but with the faster F303 processor I would think it would only be a minimal penalty for doing so. I'm pretty much just waiting for the completion of Chinese New Year before I expect any firmware updates to address the issues. You are the only one besides myself who has complained about the stray display artifacts on this forum, so I haven't submitted a GitHub issue about it to hugen. I don't make it a habit of submitting an issue report until at list one other person has verified it. You can always tell the early users of new hardware or software, they are the ones with a few arrows sticking out of their backs. - Herb
|
So, I received notice that my H4 was shipped by China post yesterday. Do I need M3 sized washers to address the display issue?
tia de va3rr
|
On Sat, Feb 15, 2020 at 08:06 AM, Russ@va3rr wrote:
So, I received notice that my H4 was shipped by China post yesterday. Do I need M3 sized washers to address the display issue?
====================================================================================
Russ,
hugen posted the following about a week ago:
" I'm very sorry for this problem, and I will fix the plastic case as soon as the Chinese factory resumes normal work."
So the issue may already have been addressed in the H4 you are receiving. If not, then in most cases you do not get the "stops at boot screen" symptom but may notice the following.
If a screen menu is brought up and pressure is applied to the right side of the case, random menu choices occur.
In that case, installing the washer should correct the problem. On my H4 you have to deliberately squeeze the right side pretty hard to notice the problem, so I haven't bothered installing the washer.
- Herb
|
Kurt and Herb,
I fixed the stray display artifacts left by moving markers. Please give a try and let me know if there is still any issue.
Ken
|
Ken,
I upgraded to version 1.3 and have been running various tests for about an hour without noticing any persistent stray display artifacts. Thanks for the release and I'll let you know if I experience any ver 1.3 related issues.
Another member has reported a NanoVNA-saver calibration issue after loading ver 1.3, but so far I have not been able to duplicate it with my NanoVNA-H4.
- Herb
|
Hi Keen Thank you I did update the H4 and used is for a couple of hours. It look good. Only in rare cases there is small straylines, e.g. just one yellow one, and it disappear very quickly. So to speak like what happens on the H version now and then. Kind regards Kurt -----Oprindelig meddelelse----- Fra: [email protected] < [email protected]> P? vegne af Ken Liao, AA6KL Sendt: 20. februar 2020 14:03 Til: [email protected]Emne: Re: [nanovna-users] #nanovna-h4 stops at boot screen Kurt and Herb, I fixed the stray display artifacts left by moving markers. Please give a try and let me know if there is still any issue. Ken
|
Roger Need
Oristo
Gyula Molnar
Kurt Poulsen
va3rr