New Member, first post with real content
Thanks for the inclusion, I'm very newb! Most of you will learn nothing
from this, it was a learning experience for me. I'll share just in case.
I've tested the useless antenna that came with my Baofeng UV-5R and also my
DBJ-1 antenna. I'm ignoring the rubber duck, stock antenna. I think I
chucked it out already. The results are quite illuminating and, I'm sure,
no surprise to the more salty members.
The TIDRADIO NA-771 (Nagoyo knock off) I have doesn't resonate at all
within the 2M band (VSWR above 5:1) and I can't get a VSWR below 2.5:1 on
70cm. This is the 'free upgrade' antenna from Baofeng. I'm tempted to play
about with it and see if I can make it work somewhere. Maybe it needs
trimming. Maybe not, I'm about ready to put my screwdriver through the
radio.
In contrast, using exactly the same settings, the DBJ-1 resonates on 2M
with 1.43:1 SWR at 145.8MHz. On the 70cm band, only the top edge has a SWR
low enough at about 448MHz, which implies the antenna is short for 70cm?
I've attached images of the SWR sweeps. I now think I have a reference
antenna I can use to build my own and, maybe, improve on the DBJ-1 in terms
of bandwidth and power.
-Steve
KN6HIF
|
Hi,
Now from Nanovna-H4 users useful information found. Nanovna-saver check usb vid/pid to detect nanovna. I succesfully used ser2net + trueport on wifi router. Now nanovna-saver not detect com port. But manually write the com name working. Please add support manual com port selection, (disable or enable vid/pid check).
73,
Lajos
|
Re: What app to run on iPhone/Android/Windows via BLE
Is there any iOS, Android or Windows app like nanovna-saver that can
communicate with the shell interface via BLE? These iOS apps may be able to interact with nanoVNA shell via BLE: This one costs a dollar: Depending on how compatible is HC-08 with Adafruit Bluefruit LE modules, these may work for Android and iOS: Microsoft Store has BLE terminal apps: This app reportedly provides a virtual COM port for BLE devices that support Generic Attribute Profile: That would in theory enable any existing nanoVNA Windows app..
|
Re: NanoVNA-Saver and the new _H4 firmware
Herb,
Then it must have been a fortunate coincedence, it worked and therefore I thought it was OK, but now I remember that I had to start a terminal program for that, I did so some time ago. I will try again if the good operation consists, if not I will issue the command via my terminal program and see what happens.
Thanks
Jos
Op 21-2-2020 om 18:22 schreef hwalker:
toggle quoted message
Show quoted text
On Fri, Feb 21, 2020 at 09:09 AM, hwalker wrote:
On Fri, Feb 21, 2020 at 08:57 AM, Jos Stevens wrote:
I started NanoVNA-Saver from the command prompt with "Clearconfig" added and could perform a 1MHz-50MHz calibration and save it without NanaVNA-Saver being aborted.
==============================================================
Jos,
Just one thing. "clearconfig" does not work from the command prompt. It is a NanoVNA console command and has to be sent from a serial terminal. I assumed that is what you did but just wanted to verify. Otherwise, it may be just a fortunate coincidence that your issue disappeared and I would hate to pass on bad info in the future.
- Herb
|
Re: Anyone had news from Maggie King?
Earlier today I had my first item mark as shipped from AliExpress since the outbreak started. My thoughts and prayers are with the folk in Wuhan province and anyone else who catches the virus.
Douglas
--
---
Do Justly Love Mercy. Walk Humbly.
|
Re: NanoVNA-Saver and the new _H4 firmware
On Fri, Feb 21, 2020 at 09:09 AM, hwalker wrote:
On Fri, Feb 21, 2020 at 08:57 AM, Jos Stevens wrote:
I started NanoVNA-Saver from the command prompt with "Clearconfig" added and could perform a 1MHz-50MHz calibration and save it without NanaVNA-Saver being aborted.
==============================================================
Jos,
Just one thing. "clearconfig" does not work from the command prompt. It is a NanoVNA console command and has to be sent from a serial terminal. I assumed that is what you did but just wanted to verify. Otherwise, it may be just a fortunate coincidence that your issue disappeared and I would hate to pass on bad info in the future.
- Herb
|
Re: NanoVNA-Saver and the new _H4 firmware
On Fri, Feb 21, 2020 at 08:57 AM, Jos Stevens wrote:
I started NanoVNA-Saver from the command prompt with "Clearconfig" added and could perform a 1MHz-50MHz calibration and save it without NanaVNA-Saver being aborted.
==============================================================
Thanks for the feedback Jos. Should help any new H4 owners that run into the same issue - which is really what this group is about.
- Herb
|
Re: NanoVNA-Saver and the new _H4 firmware
Hi Ken, Rune and Herb,
I started NanoVNA-Saver from the command prompt with "Clearconfig" added and could perform a 1MHz-50MHz calibration and save it without NanaVNA-Saver being aborted.
Each day I learn !!
Thanks,
Jos
Op 21-2-2020 om 17:02 schreef Jos Stevens:
toggle quoted message
Show quoted text
Hi Ken
No I did not use clearconfig never had needed that before, Yesterday I tried your firmware and today Hugen's, same result, will try clearconfig.
Thanks,
Jos
Op 21-2-2020 om 16:39 schreef Ken Liao, AA6KL:
Hi Jos,
Did you use clearconfig at shell after updating firmware?? Did you use my firmware or Hugen's?? Which firmware did you have previously?
Ken
|
Re: NanoVNA-Saver and the new _H4 firmware
Kurt Paulson wrote:
"New funny behavior with NanoVNA-saver as while it sweep the NanoVNA display is blanked. By continuous sweep display black (backlight off) and only visibly by ambient light but not updated."
================================================================================
I can confirm Kurt's observation. The display dimming has actually been there since the first H4 firmware release, but I wrongly assumed it was a feature to enable faster data transfer. After selecting the "sweep" button in NanoVNA-saver the display dims to a level similar to selecting BRIGHTNESS->500 on the NanoVNA-H4. The display returns to normal brightness after the sweep is completed.
I tried manually sending a scan console command, "scan 50000 30000000", to the NanoVNA-H4 using a serial terminal and it also causes the display to dim. The display stayed dim until I sent a "resume" console command. I pretty sure this interaction between the display and the scan command is unintentional.
I'll submit an issue report to hugen regarding the behavior.
- Herb
|
Re: What app to run on iPhone/Android/Windows via BLE
Ken,
Are you or Hugen going to be adding separate serial drivers to drive the separate serial pins on the v3.4 Nanovna PCB and the Nanovna-H4 PCB?
I would like to play with that, if possible.
Thanks,
Larry
|
Re: NanoVNA-Saver and the new _H4 firmware
Hi Ken
No I did not use clearconfig never had needed that before, Yesterday I tried your firmware and today Hugen's, same result, will try clearconfig.
Thanks,
Jos
Op 21-2-2020 om 16:39 schreef Ken Liao, AA6KL:
toggle quoted message
Show quoted text
Hi Jos,
Did you use clearconfig at shell after updating firmware? Did you use my firmware or Hugen's? Which firmware did you have previously?
Ken
|
Re: NanoVNA-Saver and the new _H4 firmware
Hi Jos,
Did you use clearconfig at shell after updating firmware? Did you use my firmware or Hugen's? Which firmware did you have previously?
Ken
|
What app to run on iPhone/Android/Windows via BLE
Hi,
After changing the USB to Serial for the shell interface, and connect the BLE module HC-08, I am able to use BLE to connect to NanoVNA-H4 as the attached screen shot. Is there any iOS, Android or Windows app like nanovna-saver that can communicate with the shell interface via BLE?
The nanovna-saver checks the USB VID and PID to detect NanoVNA. If the VID and PID defined at NanoVNASaver/NanoVNASaver.py is changed to the USB BLE dongle's VID and PID and change the USB BLE speed to 19200, then nanovna-save can connect to NanoVNA via BLE. Since I don't have USB BLE dongle handy, so I only verified this with a USB UART dongle.
Also, the ChibiOS shell only allows one instance. So either BLE or USB serial can be used at a time. I am thinking of modifying the simple shell to OOP based, then I can have multiple shells for USB and UART. How to avoid two shells' command conflict with each other is another issue.
Ken
|
Hi Installed the version 0.5.0. and it has still some stray line problem in the display. It blank out display line between on measurement point to the next (at least with colour black) so it look like missing vertical lines but appears as said lines blanked out between to measurements points. Seen easy by the noisy CH1 phase trace. New funny behavior with NanoVNA-saver as while it sweep the NanoVNA display is blanked. By continuous sweep display black (backlight off) and only visibly by ambient light but not updated. Kind regards Kurt -----Oprindelig meddelelse----- Fra: [email protected] < [email protected]> P? vegne af Gyula Molnar Sendt: 21. februar 2020 10:31 Til: [email protected]Emne: Re: [nanovna-users] Firmwares Firmwares upgrade only NanoVNA-H4 version. Today, Hugen also released changes to the H-4 version. NanoVNA-H4 version compiled on Feb 21, 2020 @hugen79 hugen79 released this 3 hours ago This update file is only for the 4-inch version NanoVNA-H 4 ! ! ! 1.Fix the problem of insensitive touch screen; 2. Fixed the problem that the center frequency is higher than 1G; 3. Fix the problem of mark residue; 4. Update ChibiOS to 18.2 5. Correct the battery display ratio 6. Allow saving Smith display format settings
|
Re: NanoVNA-Saver and the new _H4 firmware
Hi Rune,
Thanks for the reply.
I'm using, as far as I know, the latest software version 0.2.2-1 and I did use the calibration assistant.
Best regards
Jos
Op 21-2-2020 om 14:50 schreef Rune Broberg:
toggle quoted message
Show quoted text
Hi Jos,
which version of NanoVNA-Saver are you using? Just for my reference.
I assume you are using the calibration assistant, and not manually pressing
the buttons for calibration?
|
Re: NanoVNA-Saver and the new _H4 firmware
Hi Jos,
which version of NanoVNA-Saver are you using? Just for my reference.
I assume you are using the calibration assistant, and not manually pressing
the buttons for calibration?
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Fri, 21 Feb 2020 at 14:40, Jos Stevens <jrs@...> wrote: Hi Herb Ken and Rune,
This morning I found the -H4 Firmware dated 21/02/2020, I don't know if
there is any difference in the firmware of yesterday, but I downloaded
and flashed it into my -H4. Then I tried to calibrate in NanoVNA-Saver
like yesterday (setting = 1MHz to 50MHz and 10 segments). Again
NanoVNA-Saver aborted 1 or 2 seconds after pressing "Apply" ; I tried
twice , first with the standard load setting 50 Ohms , second with
standard load setting 49.85 Ohms. Thereafter I tried a calibration at
50kHz to 1.5 GHz , 100 Segments setting, This time NanoVNA-Saver did NOT
abort and I could save the calibration succesfully !
I'm pretty sure there is something wrong in the firmware/software
combination, I did NOT have this behaviour when I used the -H4 firmware
of before yesterday ! As said, stand-alone the device operates correctly.
Kind regards,
Jos
Op 21-2-2020 om 13:01 schreef David Fragale via Groups.Io:
Thanks for the response Herb, I am still new to this GIT HUB program/user site source thing. I will post over there. Appreciated , Dave
Fragale KA4CNP Seminole,Fla.
In a message dated 2/20/2020 6:53:04 PM Eastern Standard Time, herbwalker2476@... writes:
On Thu, Feb 20, 2020 at 12:47 PM, David Fragale wrote:
Does this flash cure the problem of momentary markers loading
behind programmed ones..and does this cure the nasty problem of the CH Z
disappearing and needing to be reawakened to get a display of "Z" even
though I specified it be displayed and the control page actually showing it
was supposed to be present/displayed ?
=========================================================================
David,
The version 1.3 release is meant to address the NanoVNA-H4 "stray display artifacts" issue reported to hugen. The NanoVNA-H4 only has CH0
and CH1, so I'm not sure which "CH Z" or "control page" you are referring
to.
If you note an -H4 hardware or firmware related issue you should
submit it to hugen's GitHub page and he or Ken will usually try to resolve
it, as they have for other -H4 issues we have submitted. I generally
submit an issue report if no one else does, but only after verifying the
issue myself. My NanoVNA-H4 has not displayed any of the hardware or
firmware issues you have reported.
- Herb
|
Re: NanoVNA-Saver and the new _H4 firmware
Hi Herb Ken and Rune,
This morning I found the -H4 Firmware dated 21/02/2020, I don't know if there is any difference in the firmware of yesterday, but I downloaded and flashed it into my -H4. Then I tried to calibrate in NanoVNA-Saver like yesterday (setting = 1MHz to 50MHz and 10 segments). Again NanoVNA-Saver aborted? 1 or 2? seconds after pressing "Apply" ; I tried twice , first with the standard load setting 50 Ohms , second? with standard load setting 49.85 Ohms. Thereafter I tried a calibration at 50kHz to 1.5 GHz , 100 Segments setting, This time NanoVNA-Saver did NOT abort and I could save the calibration succesfully !
I'm pretty sure there is something wrong in the firmware/software combination, I did NOT have this behaviour when I used the -H4 firmware of? before yesterday ! As said, stand-alone the device operates correctly.
Kind regards,
Jos
Op 21-2-2020 om 13:01 schreef David Fragale via Groups.Io:
toggle quoted message
Show quoted text
Thanks for the response Herb, I am still new to this GIT HUB program/user site source thing.?I will post over there.?Appreciated ,?Dave Fragale?KA4CNP?Seminole,Fla.
In a message dated 2/20/2020 6:53:04 PM Eastern Standard Time, herbwalker2476@... writes:
On Thu, Feb 20, 2020 at 12:47 PM, David Fragale wrote:
? ? Does this flash cure the problem of momentary markers loading behind programmed ones..and does this cure the nasty problem of the CH Z disappearing and needing to be reawakened to get a display of "Z" even though I specified it be displayed and the control page actually showing it was supposed to be present/displayed ?
=========================================================================
David,
? ? The version 1.3 release is meant to address the NanoVNA-H4 "stray display artifacts"? issue reported to hugen.? The NanoVNA-H4 only has CH0 and CH1, so I'm not sure which "CH Z" or "control page" you are referring to.
? If you note an -H4 hardware or firmware related issue you should submit it to hugen's GitHub page and he or Ken will usually try to resolve it, as they have for other -H4 issues we have submitted.? I generally submit an issue report if no one else does, but only after verifying the issue myself.? My NanoVNA-H4 has not displayed any of the hardware or firmware issues you have reported.
- Herb
|
Hi Ken No it is not from markers. I will study it closer as it may be vertical lines only. I will revert soonest possible I have another NanoVNA with edy555 firmware I will have a look Kind regard Kurt -----Oprindelig meddelelse----- Fra: [email protected] < [email protected]> P? vegne af Ken Liao, AA6KL Sendt: 21. februar 2020 05:23 Til: [email protected]Emne: Re: [nanovna-users] #nanovna-h4 stops at boot screen Hi Kurt, Are the small stray lines from measurement curves or from markers? Did you notice any pattern that causes these stray lines? Did you see this with edy555's firmware? All the above information can help me a lot in identify the source and debug. Regards, Ken
|
Re: NanoVNA-Saver and the new _H4 firmware
Thanks for the response Herb, I am still new to this GIT HUB program/user site source thing.?I will post over there.?Appreciated ,?Dave Fragale?KA4CNP?Seminole,Fla.
toggle quoted message
Show quoted text
In a message dated 2/20/2020 6:53:04 PM Eastern Standard Time, herbwalker2476@... writes:
On Thu, Feb 20, 2020 at 12:47 PM, David Fragale wrote:
? ? Does this flash cure the problem of momentary markers loading behind programmed ones..and does this cure the nasty problem of the CH Z disappearing and needing to be reawakened to get a display of "Z" even though I specified it be displayed and the control page actually showing it was supposed to be present/displayed ?
=========================================================================
David,
? ? The version 1.3 release is meant to address the NanoVNA-H4 "stray display artifacts"? issue reported to hugen.? The NanoVNA-H4 only has CH0 and CH1, so I'm not sure which "CH Z" or "control page" you are referring to.
? If you note an -H4 hardware or firmware related issue you should submit it to hugen's GitHub page and he or Ken will usually try to resolve it, as they have for other -H4 issues we have submitted.? I generally submit an issue report if no one else does, but only after verifying the issue myself.? My NanoVNA-H4 has not displayed any of the hardware or firmware issues you have reported.
- Herb
|
On Thu, Feb 20, 2020 at 09:31 PM, hwalker wrote:
" I have verified Keith's issue regarding the input field..."
=================================================
I just upgraded to hugen's 5.0 release for the NanoVNA-H4 and it appears to have successfully merged all Ken's recent releases plus fixes the input field issue. Also, now retains the saved smith chart marker format after power off.
Well worth upgrading to. Thanks to hugen and Ken.
|
Oristo
DouglasK
Kurt Poulsen