Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
NanoVNA-H4 Hints and Kinks
#nanovna-h4
|
Members have started receiving the NanoVNA-H4 (H4) and reporting various hints and kinks (mostly the latter). I thought it would be a good idea to start a topic where users could look for this information under one topic.
Kinks: 1. Several users have reported that the opening for the USB-C connector needed to be widened. Gyula Molnar provided an example fix in message #10333. 2. There has been wide spread feedback that setting the frequency range above 1 GHz, using center frequency and span, results in the H4 locking up and requiring power cycling. The work around until hugen announces a fix is to only use start and stop frequencies to set the range above 1 GHz. 3. The H4 display sometime exhibits artifacts from the previous sweep that don't clear when the display refreshes. The 2.8" display had similar issues but it is more noticeable on the 4" display. You can force a refresh that clears the artifacts by performing a trace selection. 4. Gyula Molnar reported that the menu switch on his H4 did not initially work and of receiving a subsequent error message: "error: si5351_init failed". Both were apparently solved by fully charging the battery. Hints: 1. The H4 enters the DFU mode differently than in the past. Use the following procedure to enter DFU on the H4. - Power off NanoVNA-H4 - Press down the jog switch - Power on - Release jog switch The screen should black out and DFU Demo should report an STM device in DFU mode. Follow normal upgrade procedure from that point. 2. The H4 maintains excellent backwards software command compatibility and works with NanoVNA-saver, NanoVNASharp and NanoVNAPartner. The screen capture command will not work, if present, in any of these programs because of the larger screen size. The necessary software change is minor and hopefully the developers will catch up soon. Until then, you can use Oristo's python capture script at after making the following modifications. - change 320 and 240 to 320 and 480 at lines 46 and 73 Comment: pixel dimensions of NanoVNA-H4 display are 320 by 480 - change x value to: x = struct.unpack(">153600H", b) Comment: Number of half bytes has doubled - change img value to: img = Image.frombuffer('RGBA', (480, 320), arr, 'raw', 'RGBA', 0, 1) Comment: Converted image - change COM3 at line 11 to appropriate comport 3. The H4 firmware is NOT backwards compatible with the NanoVNA-H. Too many changes had to be made to accommodate the new Cortex-M4 MCU (F303) and the 4" display to maintain compatibility. hugen now maintains separate NanoVNA-H4 and NanoVNA-H firmwares. Do not make the mistake of installing NanoVNA-H firmware in a NanoVNA-H4. 4. The brightness menu has been substituted for the DFU menu on the H4. Users can now adjust the display brightness for best inside or outdoor viewing. 5. A new marker menu is available (courtesy of an edy555 merge). Users who would rather have the smith chart display in terms other than L/C can now do so. 6. The slightly annoying "feature", where the power LED stays on for a few moments after switching the NanoVNA-H off, seems to be gone forever on the NanoVNA-H4 (and NanoVNA-H v3.4). Feel free to add to the items above after getting confirmation of the kink from another member, if possible. I have submitted an issue report to hugen ( ) regarding the case opening and center frequency kinks. He responded that he will look into both issues when he returns after the Chinese New Year. - Herb |
|
Another verified kink (Item 5) added:
Members have started receiving the NanoVNA-H4 (H4) and reporting various hints and kinks (mostly the latter). I thought it would be a good idea to start a topic where users could look for this information under one topic. Kinks: 1. Several users have reported that the opening for the USB-C connector needed to be widened. Gyula Molnar provided an example fix in message #10333. 2. There has been wide spread feedback that setting the frequency range above 1 GHz, using center frequency and span, results in the H4 locking up and requiring power cycling. The work around until hugen announces a fix is to only use start and stop frequencies to set the range above 1 GHz. 3. The H4 display sometime exhibits artifacts from the previous sweep that don't clear when the display refreshes. The 2.8" display had similar issues but it is more noticeable on the 4" display. You can force a refresh that clears the artifacts by performing a trace selection. 4. Gyula Molnar reported that the menu switch on his H4 did not initially work and of receiving a subsequent error message: "error: si5351_init failed". Both were apparently solved by fully charging the battery. 5. A Russian user posted the following, which I have verified on my H4: The cut-out under the touch screen is narrower than required. If a menu is brought up and pressure is applied to the right side of the case, the device begins to run around the menu. You can permanently solve this issue by disassembling the case and on the non-sensory part of the display, the right edge to the silver line inclusive, stick 1 layer of extra tape to the board. I haven't verified the fix, but I have verified that if a menu is present applying pressure to right hand side of the case will cause random menu selection. Hints: 1. The H4 enters the DFU mode differently than in the past. Use the following procedure to enter DFU on the H4. - Power off NanoVNA-H4 - Press down the jog switch - Power on - Release jog switch The screen should black out and DFU Demo should report an STM device in DFU mode. Follow normal upgrade procedure from that point. 2. The H4 maintains excellent backwards software command compatibility and works with NanoVNA-saver, NanoVNASharp and NanoVNAPartner. The screen capture command will not work, if present, in any of these programs because of the larger screen size. The necessary software change is minor and hopefully the developers will catch up soon. Until then, you can use Oristo's python capture script at after making the following modifications. - change 320 and 240 to 320 and 480 at lines 46 and 73 Comment: pixel dimensions of NanoVNA-H4 display are 320 by 480 - change x value to: x = struct.unpack(">153600H", b) Comment: Number of half bytes has doubled - change img value to: img = Image.frombuffer('RGBA', (480, 320), arr, 'raw', 'RGBA', 0, 1) Comment: Converted image - change COM3 at line 11 to appropriate comport 3. The H4 firmware is NOT backwards compatible with the NanoVNA-H. Too many changes had to be made to accommodate the new Cortex-M4 MCU (F303) and the 4" display to maintain compatibility. hugen now maintains separate NanoVNA-H4 and NanoVNA-H firmwares. Do not make the mistake of installing NanoVNA-H firmware in a NanoVNA-H4. 4. The brightness menu has been substituted for the DFU menu on the H4. Users can now adjust the display brightness for best inside or outdoor viewing. 5. A new marker menu is available (courtesy of an edy555 merge). Users who would rather have the smith chart display in terms other than L/C can now do so. 6. The slightly annoying "feature", where the power LED stays on for a few moments after switching the NanoVNA-H off, seems to be gone forever on the NanoVNA-H4 (and NanoVNA-H v3.4). Feel free to add to the items above after getting confirmation of the kink from another member, if possible. I have submitted an issue report to hugen ( ) regarding the case opening and center frequency kinks. He responded that he will look into both issues when he returns after the Chinese New Year. - Herb |
|
Minor fix for typing above:
The "error: si5351_init failed" message occurred while charging the battery from the USB port on the computer after trying to turn on the device when it was turned off. Solution: When charging the battery, I do not turn on the device while charging turn on the device and there will be no such error message. I probably need to look for a menu switch error later on. See 5. Gyula |
|
On Tue, Jan 28, 2020 at 04:54 AM, Gyula Molnar wrote:
Touchscreen rework ¨C insert 4 pcs plastic washer. =============================================== Gyula, Kudo's! That is a much cleaner solution than the extra tape on the Russian forum. I will submit an issue report to hugen with your proposed solution. - Herb |
|
I submitted an issue #25 to hugen a few days ago that, "Setting the frequency range above 1 GHz, using center frequency and span, results in the H4 locking up and requiring power cycling."
I received feedback that the issue has been debugged and will be fixed in the next hugen NanoVNA-H4 firmware release. - Herb |
|
Hi, I just bought an H4, came across the current state of screenshot limitations and at least for NanoVNA-WebClient submitted a pull request to fix it: . You can test it yourself by running the web client locally on your PC but it would be great to get something like this merged and built for mobile distribution too. Is cho45 in this group?
|
|
I guess it did not copy what I was replying to, in the older messages it says
toggle quoted message
Show quoted text
Gyula Molnar 01/28/20 #10364 </g/nanovna-users/message/10364> Minor fix for typing above: The "error: si5351_init failed" message occurred while charging the battery from the USB port on the computer after trying to turn on the device when it was turned off. Solution: When charging the battery, I do not turn on the device while charging turn on the device and there will be no such error message. I probably need to look for a menu switch error later on. See 5. Gyula but no where does it say to to get out of that acreen. Joe WB9SBD On 8/26/2021 1:29 PM, Joe WB9SBD wrote:
But how do you fix the error? |
|
The latest version of FW have the ability to adjust the maximum cut-over of the si5351 around the 300MHz mark.
toggle quoted message
Show quoted text
Also, I took another look at your photo - you have an H4, not an H which means you can only use the H4 firmware on your device. Not to worry - flashing is very simple: 1. install defuse-demo software (it's not a demo, that's just the name). 2-download DiSlord's 1.0.69 firmware for the H4 (it may be in an archive with other versions), 3-plug Nano into PC and place your H4 into DFU mode by holding in the jog sw and turning it on - screen will stay off but you'll hear the familiar notes to show the PC sees the device. 4-open DeFuse s/w and you'll see in the top left your unit should be in DFU mode. 5-in the Lower LEFT select CHOOSE and get your H4 firmware, then flash with the UPGRADE button (NOT upload). 6-power-cycle & Done On Thursday, August 26, 2021, 02:29:22 p.m. EDT, Joe WB9SBD <nss@...> wrote:
But how do you fix the error? Mine is stuck with that screen Joe WB9SBD nss@... |
|
.....Installing the latest FW will fix MANY issues.
toggle quoted message
Show quoted text
On Thursday, August 26, 2021, 02:34:25 p.m. EDT, Joe WB9SBD <nss@...> wrote:
I guess it did not copy what I was replying to, in the older messages it says Gyula Molnar 01/28/20 #10364 </g/nanovna-users/message/10364> Minor fix for typing above: The "error: si5351_init failed" message occurred while charging the battery from the USB port on the computer after trying to turn on the device when it was turned off. Solution: When charging the battery, I do not turn on the device while charging turn on the device and there will be no such error message. I probably need to look for a menu switch error later on. See 5. Gyula but no where does it say to to get out of that acreen. Joe WB9SBD On 8/26/2021 1:29 PM, Joe WB9SBD wrote: But how do you fix the error? |
|
I am sorry about loosing it.
toggle quoted message
Show quoted text
I just never ever bought anything that did not come with any documentation.? and yes NanoVNA-H4 I went to the site /g/nanovna-users/files and looked around and did even a search and nothing with that name is there. Sorry. Joe WB9SBD On 8/26/2021 1:56 PM, Larry Rothman wrote:
The latest version of FW have the ability to adjust the maximum cut-over of the si5351 around the 300MHz mark. |
|
Hello Joe!
Please try here /g/nanovna-users/files/Absolute%20Beginner%20Guide%20to%20The%20NanoVNA Brgds Vladimir, dl7pga |
|
Joe - have a look at the message before yours...
toggle quoted message
Show quoted text
/g/nanovna-users/message/24234 On Thursday, August 26, 2021, 03:09:05 p.m. EDT, Joe WB9SBD <nss@...> wrote:
I am sorry about loosing it. I just never ever bought anything that did not come with any documentation.? and yes NanoVNA-H4 I went to the site /g/nanovna-users/files and looked around and did even a search and nothing with that name is there. Sorry. Joe WB9SBD On 8/26/2021 1:56 PM, Larry Rothman wrote: ? The latest version of FW have the ability to adjust the maximum cut-over of the si5351 around the 300MHz mark. |
|
Thanks Larry,
toggle quoted message
Show quoted text
Is that one the latest and greatest for the NanoVNA-H4? /g/nanovna-users/files/Dislord%27s%20Nanovna%20-H%20Firmware/NanoVNA%20v1.0.69%20fw%20pack.zip Joe WB9SBD On 8/26/2021 2:53 PM, Larry Rothman wrote:
Joe - have a look at the message before yours... |
|
Yes. Unzip it and only use the H4 file.?
toggle quoted message
Show quoted text
On Thu., 26 Aug. 2021 at 5:33 p.m., Joe WB9SBD<nss@...> wrote: Thanks Larry, Is that one the latest and greatest for the NanoVNA-H4? /g/nanovna-users/files/Dislord%27s%20Nanovna%20-H%20Firmware/NanoVNA%20v1.0.69%20fw%20pack.zip Joe WB9SBD On 8/26/2021 2:53 PM, Larry Rothman wrote:
? Joe - have a look at the message before yours... |
|
how about the DfuSE DEMO software? file?
toggle quoted message
Show quoted text
Reading the "manual" you linked to and they say you can install the needed driver with that or alone, so what's best? Joe On 8/26/2021 4:44 PM, Larry Rothman wrote:
Yes. Unzip it and only use the H4 file. |
|
Joe,
toggle quoted message
Show quoted text
Grab a copy of the Absolute Beginners Guide from the files area and read through it. Also browse the forum Wiki.? Those two will provide quite a lot of answers.? On Thu., 26 Aug. 2021 at 5:50 p.m., Joe WB9SBD<nss@...> wrote: how about the DfuSE DEMO software? file? Reading the "manual" you linked to and they say you can install the needed driver with that or alone, so what's best? Joe On 8/26/2021 4:44 PM, Larry Rothman wrote:
Yes. Unzip it and only use the H4 file. |
|
On Thu, 26 Aug 2021 14:08:55 -0500
"Joe WB9SBD" <nss@...> wrote: I just never ever bought anything that did not come with any This is something you have to get used to. Lots of things are sold without paper documentation these days to lower production cost. You are expected to get the documentation online. This is the new normal. 73 -Jim NU0C |
Gyula Molnar
Vladimir Lebedev
Jim Shorney
to navigate to use esc to dismiss