Keyboard Shortcuts
Likes
- Nanovna-Users
- Messages
Search
Re: Your NanoVNA version
hugen@ one of those clones looks just like the real thing. Since we don't have the luxury of asking sellers to open up the case, perhaps you can tell us how to tell the difference by examining the photos, or just publish Maggie K's email address and let us buy them straight from her ?
|
Re: edy555 release 0.7.0-20200223-white screen
GREAT !!
toggle quoted message
Show quoted text
I have it installed and I had no issues after the default (50K to 900M) calibration. Remember to press the onscreen RESET button just prior to running a calibration on the unit. You can save the cal to any location 0 through 4 .That will allow you to compare a few cal runs against each other. Location 0 is the power-on default. Use that if you play with a specific freq band. Just remember, the default firmware only grabs 101 cal samples, spread out over the freq span - and interpolates between them, which can be problematic. Use the NanovnaSaver PC app to cal and scan as many points as you want for a given freq span. Clear as mud? On Thursday, February 27, 2020, 3:50:22 p.m. GMT-5, n2msqrp <mstangelo@...> wrote:
Larry Success. I powered down the unit for a couple of minutes and tried the short across the P1 boot pins. This time it was successful. DfuSE Demo recognized it and I was able to successfully load the Hugen-H firmware. I would still like to check out the edy555 release 0.7.0-20200223. Has anyone had issues after running the calibration? Mike N2MS On February 27, 2020 at 3:38 PM Larry Rothman <nlroth@...> wrote: |
Re: edy555 release 0.7.0-20200223-white screen
Larry
toggle quoted message
Show quoted text
Success. I powered down the unit for a couple of minutes and tried the short across the P1 boot pins. This time it was successful. DfuSE Demo recognized it and I was able to successfully load the Hugen-H firmware. I would still like to check out the edy555 release 0.7.0-20200223. Has anyone had issues after running the calibration? Mike N2MS On February 27, 2020 at 3:38 PM Larry Rothman <nlroth@...> wrote: |
Re: edy555 release 0.7.0-20200223-white screen
Do a dearch of the forums for STlink (st-link).You can recover using that interface, which is the other set of pins along the side of the nano.
toggle quoted message
Show quoted text
On Thursday, February 27, 2020, 3:31:39 p.m. GMT-5, n2msqrp <mstangelo@...> wrote:
Herb and All, I followed your instructions and upgraded my NanoVNA-H form a Hugen-H firmware to version 0.7.0-20200223 followed by a reset and clear 1234. I tired the calibration routine but did not get inconsistent results so I tried to install the Hugen firmware but I erroneously installed Hugen-H4 firmware in by HanoVNA-H unit. Oops! When I tried to exit the DFU mode via a power reset I get a white screen upon powerup. I powered down and tried to get back into the DFU mode by shorting the P! pins but the DFU mode does not reappear nor do I see a com port connection via the Device Manager. It looks like I hosed my unit. How and I re-establesh communications to my NanaVNA-H? By the way, the inconsistent results I get after the calibration routine is that a short is displayed as 50 ohms on the Smith Chart. Thanks, Mike N2MS ? ? On February 23, 2020 at 9:07 PM hwalker < herbwalker2476@... mailto:herbwalker2476@... > wrote: |
Re: edy555 release 0.7.0-20200223-white screen
Herb and All,
toggle quoted message
Show quoted text
I followed your instructions and upgraded my NanoVNA-H form a Hugen-H firmware to version 0.7.0-20200223 followed by a reset and clear 1234. I tired the calibration routine but did not get inconsistent results so I tried to install the Hugen firmware but I erroneously installed Hugen-H4 firmware in by HanoVNA-H unit. Oops! When I tried to exit the DFU mode via a power reset I get a white screen upon powerup. I powered down and tried to get back into the DFU mode by shorting the P! pins but the DFU mode does not reappear nor do I see a com port connection via the Device Manager. It looks like I hosed my unit. How and I re-establesh communications to my NanaVNA-H? By the way, the inconsistent results I get after the calibration routine is that a short is displayed as 50 ohms on the Smith Chart. Thanks, Mike N2MS On February 23, 2020 at 9:07 PM hwalker < herbwalker2476@... mailto:herbwalker2476@... > wrote: |
Re: Nanovna white screen USB dead
#firmware
#nanovna-h4
On Thu, Feb 27, 2020 at 10:27 AM, <19.ari@...> wrote:
".. i updated from NanoVNA-H_AA_20200118 to NanoVNA-H4_20200221 version..." ========================================================= I wondered what the symptom would be if someone accidentally installed the NanoVNA-H4 firmware on the NanoVNA-H, and I guess you answered that unintentionally. Fortunately, you had a NanoVNA without a case or you would have had to take it apart in order to access the pins for getting into DFU mode. I suppose if the reverse occurred and firmware for the NanoVNA-H was installed on the NanoVNA-H4, similar symptoms would be experienced. Without the correct firmware, I'm not sure if you would still be able to get back into DFU mode on the NanoVNA-H4 by depressing the jog wheel switch while powering on. If not, opening the case to access the pins for getting into DFU mode would be necessary. Then again, getting into the DFU mode on the NanoVNA-H4 might be hardcoded in the OS and would work regardless. Probably a question for hugen or erik to answer. - Herb |
Re: Nanovna white screen USB dead
#firmware
#nanovna-h4
Hi Ari,
It's great you found your mistake. So - it appears you flashed an H4 device with H firmware. The H4 device uses an F303 micro whereas the H and older Nanovna all use the F072 micro. They are NOT the same - they have different displays and interfaces. In the future, please be sure to flash a device only with firmware designed for that specific device. Now you get to play with it! Please read the various user guides (there are several) on the forum WIKI and in the Files section. |
Re: Nanovna white screen USB dead
#firmware
#nanovna-h4
19
Hi Gyula, Peace be upon You and Yours All. "or reinstall the DfuSe demo." Your last words where the key. I could revoke the device with jumper setting. Then i saw my ignorance, i updated from NanoVNA-H_AA_20200118 to NanoVNA-H4_20200221 version. Everything good in the End, Thanks for Your inspiration. Thanks All. Sincerely ** Ari ** |
Re: edy555 release 0.7.0-20200223
#firmware
Larry, I tried every combination of generate and file name for about an hour before looking for the DFU again and finding it uploaded. The hex file gave me an error but the bin file, in every case displayed that it was generated but I couldn¡¯t fine the file. I¡¯m familiar with all these tools as I¡¯ve programmed a number of STM32F4 and F7 boards using 3 or 4 IDEs.
Thanks for the guide. I¡¯ve been in there a bunch. Jerry On Feb 26, 2020, at 3:47 PM, Larry Rothman <nlroth@...> wrote:Jerry Hancock jerry@... |
New file uploaded to [email protected]
[email protected] Notification
Hello, This email message is a notification to let you know that the following files have been uploaded to the Files area of the [email protected] group. Uploaded By: andybuyze@... Description: Cheers, |
New file uploaded to [email protected]
[email protected] Notification
Hello, This email message is a notification to let you know that the following files have been uploaded to the Files area of the [email protected] group. Uploaded By: andybuyze@... Description: Cheers, |
Re: 1/4 wavelength coaxial trap for 440 MHz Ham Band
Test it as it will be used. Connect a "T" to the stub. connect Port 0 or 1
toggle quoted message
Show quoted text
depending on which NanoVNA is being used to one side of the T. connect port 1 or 2 depending upon which NanoVNA. In other words do an S21 test. The total length of the stub will also include and length of the T to the center conductor of the pass though of the T. *Clyde K. Spencer* On Tue, Feb 25, 2020 at 5:46 PM Robert Putala KE8UW <rcp@...> wrote:
I"m having difficulty in getting a simple 1/4 wavelength, 442 MHz trap to |
Re: File updated in [email protected]
/Presentations/20191220_ON7DQ_NanoVNA_Presentation_English_V2.01.pdf
Uploaded By: Luc ON7DQ <on7dq@...> Description: NanoVNA presentation by ON7DQ for the Ostend Radio Club, in ENGLISH. V2.01 Corrected a number of typos, and replaced the term Smith Diagram with Smith Chart, which is more common. Cheers, The Groups.io Team ============================================ Many thanks for sharing, Luc! I've mentioned it on Twitter so there may be more folk joining the group to download it. 73, David GM8ARV -- SatSignal Software - Quality software for you Web: Email: david-taylor@... Twitter: @gm8arv |
Re: File updated in [email protected]
Luc,
toggle quoted message
Show quoted text
Great update to your presentation! Thanks ...Larry On Thursday, February 27, 2020, 9:20:19 a.m. GMT-5, [email protected] Notification <[email protected]> wrote:
Hello, This email message is a notification to let you know that the following files have been updated in the Files area of the [email protected] group. - /Presentations/20191220_ON7DQ_NanoVNA_Presentation_English_V2.01.pdf Uploaded By:Luc ON7DQ <on7dq@...> Description: NanoVNA presentation by ON7DQ for the Ostend Radio Club, in ENGLISH. V2.01Corrected a number of typos, and replaced the term Smith Diagram with Smith Chart, which is more common. Cheers, The Groups.io Team |
File updated in [email protected]
[email protected] Notification
Hello, This email message is a notification to let you know that the following files have been updated in the Files area of the [email protected] group. Uploaded By: Luc ON7DQ <on7dq@...> Description: Cheers, |
Re: 1/4 wavelength coaxial trap for 440 MHz Ham Band
Hi, Rob
Nice to see you here having fun with the nano. Amazing that it isn¡¯t even a year old. Changed your call, I see. I would have too with WA8UZC, I think. When I moved to Illinois, I had to get a new call as back then FCC didn¡¯t let you keep your call when you move out of call zone. WB9PMY. Gary W9TD |
Re: How to get into console?
On Thu, Feb 27, 2020 at 01:15 AM, DG4EK wrote:
Not new, already included in 3.0.2: D the latest is 3.06, preferably st. page. In my startup window I see: |