开云体育

Have you installed the drivers?
The nanoVNA uses a serial to USB device to convers on USB. Check out FTDI for the latest drivers.

Verstuurd vanaf mijn iPhone

Thanks Roger, did all of that still nothing. In win7 when I plug it in the USB never responds in any way at all like as if nothing ever was connected at all. Nothing in the device manager, and nothing under devices. Tried several times with the drivers, tried cleaning the registry, etc.....then switched to win 10 thinking it would be easy there....no luck.

Thanks!
Phil

Thanks for the response!

On the cable, just got a new fancy one from amazon and tried it this morning before sending out my email. I was hopeful that it would work and it did not.......then emailed the group.

I have opened the unit and looed to see if there was anything obvious and there was not. Also that way I could make sure the USB-C was fully engaging and it looked like it was.

Will open up again, this time with the headset on and look for a bad connector, connection, or solder as you suggest.

Thanks again!
Phil

At this moment as you can see i update UI and next release name as v1.0.1
UI fixes still not fully comleted (for see changes need reset config for apply new colors)

@DiSlord - let me ask you kindly following - your H4 branch fw version string comes from
"git describe --tags" which shows always 0.7.1...
What would you recommend to put in the VERSION string such I know what fw version has been flashed into my H4?

On Fri, Jul 17, 2020 at 10:43 AM, igor-m wrote:

On Fri, Jul 17, 2020 at 07:35 PM, Gary Hale wrote:

Guys, you have to find your SI5351 max frequency, those 310M is the value I
flashed in (for experimental reasons only) because I found out my max
frequency is 321MHz..

Try test 200-350MHz range for better search threshold limit.

PS then i work under H4 vs SI5351+SI4432 i rewrite sweep mode, now it use band table for better ajust settings
I think remove threshold as value and use this table
typedef struct {
uint32_t mode; // mode for SI5351 for set frequency (fixed PLL or fixed Multiplexer divider)
uint32_t freq; // max freq for band
union {
uint16_t div; // divider for fixed Multiplexer mode
uint16_t pll_n; // PLL n for fixed PLL mode
};
uint16_t mul; // Harmonic for main frequency
uint16_t omul; // Harmonic for offset frequency
uint16_t pow; // power (not need)
uint16_t l_gain; // l gain for AIC ADC (ref data)
uint16_t r_gain; //r gain for AIC ADC (measure data)
// uint16_t freq_align; // Not use, frequency align on set
} band_strategy_t;

It allow more easy select sweep settings for every frequency range, but more difficult then now (used threshold step)
Now used this table (for 300MHz threshold)
/*
* Frequency generation divide on band
* Band 1
* 800~10kHz fixed PLL = XTALFREQ * PLL_N_1, fractional divider
* Band 2
* 10kHz~100MHz fixed PLL = XTALFREQ * PLL_N_2, fractional divider
* Band 3
* 100~130MHz fractional PLL = 800-1040MHz, fixed divider 'fdiv = 8'
* Band 4
* 130~170MHz fractional PLL = 780-1080MHz, fixed divider 'fdiv = 6'
* Band 5
* 680~300MHz fractional PLL = 680-1200MHz, fixed divider 'fdiv = 4'
*
* For FREQ_HARMONICS = 300MHz - band range is:
* +-----------------------------------------------------------------------------------------------------------------------------------------------+
* | Band 2 | Band 3 | Band 4 | Band 5 | Band 3 | Band 4 | Band 5 |
* +-----------------------------------------------------------------------------------------------------------------------------------------------+
* | Direct mode x1 : x1 | x3 : x5 | x5-x7 | x7-x9 | x9-x11 |
* +-----------------------------------------------------------------------------------------------------------------------------------------------+
* |10kHz - 100MHz | 100 - 130MHz | 130 - 170MHz | 170 - 300MHz | 300-390MHz | 390-510MHz | 510-900MHz | 900-1500MHz | 1500-2100MHz | 2100-2700MHz |
* +-----------------------------------------------------------------------------------------------------------------------------------------------+
* | f = 50kHz-300MHz | f=100-130 | f=130-170 | f=170-300 | f=180-300 | f=214-300 | f=233-300 |
* | of = 50kHz-300MHz |of= 60- 78 |of= 78-102 |of=102-180 |of=128-215 |of=166-234 |of=190-246 |
* +-----------------------------------------------------------------------------------------------------------------------------------------------+
*/

On Fri, Jul 17, 2020 at 07:35 PM, Gary Hale wrote:

I tried it, my NANOVNA-H overheated more slowly with this setting.

Gary AG7TH

On 7/17/20 10:33, n2msqrp wrote:

The SI chip is specified up to 200Mhz. Have you tried it with this

threshold?

Mike N2NS

Guys, you have to find your SI5351 max frequency, those 310M is the value I flashed in (for experimental reasons only) because I found out my max frequency is 321MHz..

I tried it, my NANOVNA-H overheated more slowly with this setting.

Gary AG7TH

The SI chip is specified up to 200Mhz. Have you tried it with this threshold?

Mike N2NS

On Fri, Jul 17, 2020 at 03:54 PM, DiSlord wrote:

..

In nanovna.h i begin use AUDIO_CLOCK_REF (86016000U)
Try revert to #define AUDIO_CLOCK_REF ( 8000000U)
// 5ms @ 96kHz
// Define aic3204 source clock frequency (for 8MHz used fractional multiplier,
and possible little phase error)
#define AUDIO_CLOCK_REF ( 8000000U)
//#define AUDIO_CLOCK_REF (10752000U)
// Disable AIC PLL clock, use input as CODEC_CLKIN
//#define AUDIO_CLOCK_REF (86016000U)

OK, I've done, and I've also increased the default threshold to 310MHz here.
Flashed in, it runs for 25minutes already without a crash. I will use it now, and we will see.
Looks promising..

A basic question for you:? have you tried a second USB cable with the H4?
There have been instances of companies shipping cheap cables that fail quickly.?
You might also want to open the H4 housing and using a magnifying glass, make sure there are no solder shorts around the usb connector.?



On Fri, 17 Jul 2020 at 11:06 AM, p01lindsey@...<p01lindsey@...> wrote: Hello,



I have a new H4 unit that I just got a couple of weeks back.? ? Works great
until I go to us it with a PC.



What I am seeing is on win7 the laptop that I am using never sees anything
when I plug in the usb connector.? Power on, power off, plug into the usb
port on or off none of that makes a difference.? I never sees it.



So then taking it to two different win10 computers if I go into device
manager when it is plugged in they both see it but with an error.? The
message is Unknown USB Device (Device Description Request Failed).



Different computers, different operating systems, power on/power off, etc.
Same result.



The basic question I have is this a hardware or a driver issue?



Thank you in advance!

Phil

With Win7 you need to manually install the driver. See the Wiki in this group for details..

Roger

The overheating issue on my NanoVNA-H appeared early in April after I installed beta firmware titled "NanoVNA-H v0.8.3_96kHzIF_3.2kHz_sweep_points". Looking back I wonder if that firmware was a factor in sensitization of the chip.

Gary AG7TH

@ Igor-m....

I used your settings and by setting the threshold up and down many many times I found my max threshold setting @ 305150000 and can leave it there for hours, it never gets unstable.

The firmware is by Dislord V 0.9.3,4 beta.

I'm measuring a 10dB attenuator on my H4, measures 9.78 dB, not one mB change.

When I feel the box, it's hardly warm.

Jos

Op 17-7-2020 om 15:58 schreef igor-m:

Thanks for all the suggestions. I ordered an H4 and will experiment with an aluminum heat sink that bridges from the si5351 to the AIC 3204.

The si5351 was never hot to the touch, so it does not take much warming to set it off.

Gary AG7TH

Hello,



I have a new H4 unit that I just got a couple of weeks back. Works great
until I go to us it with a PC.



What I am seeing is on win7 the laptop that I am using never sees anything
when I plug in the usb connector. Power on, power off, plug into the usb
port on or off none of that makes a difference. I never sees it.



So then taking it to two different win10 computers if I go into device
manager when it is plugged in they both see it but with an error. The
message is Unknown USB Device (Device Description Request Failed).



Different computers, different operating systems, power on/power off, etc.
Same result.



The basic question I have is this a hardware or a driver issue?



Thank you in advance!

Phil

My tests with threshold:
In the latest H4 source the threshold is set 300.000.100 Hz.
I set 201p, 1kHz BW, start=900M, stop=1000M
I started to increase the threshold till the display shows mess.

ch> threshold 322000000 << immediately started to mess

I returned back and with threshold 321.000.000 it runs stable for 20minutes already.. Hmm..

Frankly, I doubt the crashes I see here with the latest fw (and with 0846, 0847) are caused by the overheating of the SI5153..

On Fri, Jul 17, 2020 at 05:33 AM, igor-m wrote:

Q / A: Какая может быть разница между v 0.8.4.5fw
(который работает стабильно здесь) и
последним ???

In nanovna.h i begin use AUDIO_CLOCK_REF (86016000U)
Try revert to #define AUDIO_CLOCK_REF ( 8000000U)
// 5ms @ 96kHz
// Define aic3204 source clock frequency (for 8MHz used fractional multiplier, and possible little phase error)
#define AUDIO_CLOCK_REF ( 8000000U)
//#define AUDIO_CLOCK_REF (10752000U)
// Disable AIC PLL clock, use input as CODEC_CLKIN
//#define AUDIO_CLOCK_REF (86016000U)

On Fri, Jul 17, 2020 at 12:29 AM, igor-m wrote:

As I indicated in one of my posts, my new H4 crashes with
0.8.4.7fw every 10-15mins
0.8.4.6fw every 10-15mins
0.8.4.5fw does not crash.
all at around 25degC ambient. I haven't mess with the threshold. You may try a
different firmware..

I built the latest H4 fw version (pulled from Dislord's github 1.5h back) with sdcard and 32kHz xtal.
Soldered xtal and socket in, flashed the fw in (shows old fw version on the LCD).
Set time (do not use leading 0), set vbat offset, re-calibrated my 4 ranges.
Did a measurement and saved s-data and LCD-shot - it works !! :)

Bad news - it crashed after about 5 minutes (the usb cable disconnected, voltage 4.17V).
It shows messy data, but the system works.

Q/A: What could be the difference between v 0.8.4.5fw (which works stable here), and the latest???

It's important to note that this thread has 3 periods of comments that are somewhat out of sync.
1. My original comments that were ... well, whatever.
2. My recent reply to clarify that I did not accept the summary dismissal of the material without intelligent review of the material.
3. The possibly up-to-date comments addressing changes that were possibly made to the device and software in the interim.

There have been several threads and private comments regarding the lack of engineering, the lack of supporting documentation, the lack of adequate user training and operational guides, and the difficulty getting in touch w the developers. I did offer early on to write docs,
because I have experience in that area, and I have and want to use the device. My request was to be able to work with a developer to have access to adequate info. The replies were to the effect that I should just start using the device and that way I would learn what I needed to write the docs. The irony was apparently lost on the developers. I decided not to waste my time, because I have other projects on the table. I just finished a project with a manufacturer of ham-related products, and they were very good...though understandably not wordy...about keeping in touch as the project progressed.

I am still impressed with the whole idea of a NanoVNA, and the energy of the developers, and the energy of those who have stepped up to develop supporting software that has so increased the usefulness of the devices. However, the steady stream of questions here, many of them duplicates, and the reports of errors in released version of firmware and software, further convince me that the field is missing some important concepts about how to effectively develop products and software.

~R~
72/73 de Rich NE1EE
On the banks of the Piscataqua



--
72/73 de Rich NE1EE
On the banks of the Piscataqua