开云体育

I made a case for the white one, it's a bit fiddly (washers and such) to mount because i added som distance to the back PCB as the battery was a bit cramped.
Over all, it's pretty good and adds good value. I looked at using light pipes but it wouldn't work out well, but print in a (semi) transparent plastic and you can see the LEDs through the walls.
It's licensed as CC BY-SA and the CAD models (OnShape) is published so go nuts with it and make it useful to your specific needs.

Hi Serge,
00:20 Wed 31 Jul 19 , Serge wrote:

My +1 to display as R +/-Jx.

:-)

Even will be ideal to display as line graphics: SWR, R and JX !
As some antenna analyzers done it, Rigexpert etc...

I haven't had time to work on it but it could be done, I'll take a look

Lapo, IK5NAX

18:26 Tue 30 Jul 19 , hugen@... wrote:

Since powering up from DFU mode, aic3204 fails to be initialized at power-on, which will cause I2C abnormality. Re-powering up will make aic3204 normal initialization work normally.

Ok, so it's what it has to do, no instability. Fine. One can wait some
seconds or just disconnect the battery when working on fw.

Thank you

Lapo, IK5NAX

I was hoping for a Panda, but all I got was a properly working VNA. Everything was there but instructions. Thanks to this group I knew what to expect.
Thanks
Stuart K6YAZ
Los Angeles, USA

Same experience here, eBay seller xspar. The letter in the "free gift" package had the real tracking number. The unit arrived 10 days later.
I think it is some trick to game eBay, maybe to show them faster delivery times to improve their rating or something.

Yes, I agree a dynamic real time read would be far better. At this point my feeling about their PC software... quite acceptable. I have used it to do real time alignment of filters and impedance matching. Can it be improved. SURE. In another post, the LabView interface looks quite good.

73' Alan

________________________________
From: [email protected] <[email protected]> on behalf of tuckvk3cca <tuckvk3cca@...>
Sent: Wednesday, July 31, 2019 6:36 PM
To: [email protected] <[email protected]>
Subject: Re: [nanovna-users] DL2SBA j-vna software

Possible solution can also be read by Excel, but not the same as driving nano dynamically under vna-j which has far more advanced features.Sent from my Samsung Galaxy smartphone.
-------- Original message --------From: alan victor <avictor73@...> Date: 31/07/2019 20:21 (GMT+01:00) To: [email protected] Subject: Re: [nanovna-users] DL2SBA j-vna software The file format expected from nanoVNA PC software is Touchstone. Hence, once read by their software, the file can be saved as well re read by any other routine. For example Keysight (hp) APPCAD. So if the DL2SBA SW will not read the nanoVNA direct, you could come in via another path.Alan________________________________From: [email protected] <[email protected]> on behalf of tuckvk3cca <tuckvk3cca@...>Sent: Wednesday, July 31, 2019 1:39 PMTo: [email protected] <[email protected]>Subject: [nanovna-users] DL2SBA j-vna softwareAnybody knows if I can use the above java based software with my nano. I find their pc interface rather primitive.Sent from my Samsung Galaxy smartphone.

Possible solution can also be read by Excel, but not the same as driving nano dynamically under vna-j which has far more advanced features.Sent from my Samsung Galaxy smartphone.

The file format expected from nanoVNA PC software is Touchstone. Hence, once read by their software, the file can be saved as well re read by any other routine. For example Keysight (hp) APPCAD. So if the DL2SBA SW will not read the nanoVNA direct, you could come in via another path.

Alan

________________________________
From: [email protected] <[email protected]> on behalf of tuckvk3cca <tuckvk3cca@...>
Sent: Wednesday, July 31, 2019 1:39 PM
To: [email protected] <[email protected]>
Subject: [nanovna-users] DL2SBA j-vna software

Anybody knows if I can use the above java based software with my nano. I find their pc interface rather primitive.Sent from my Samsung Galaxy smartphone.

Hi Hugen,
I added a delay of 50 milliseconds to the code, the hangup was gone.
Does the calibration function now work with such a delay?

void adc_init(void)
{
rccEnableADC1(FALSE);
ADC->CCR = 0;
ADC1->CR |= ADC_CR_ADCAL;
while (ADC1->CR & ADC_CR_ADCAL);
chThdSleepMilliseconds(50);
ADC1->CR = ADC_CR_ADEN;
while (!(ADC1->ISR & ADC_ISR_ADRDY));
}

My PCB Version 3.1 NanoVNA

Anybody knows if I can use the above java based software with my nano. I find their pc interface rather primitive.Sent from my Samsung Galaxy smartphone.

Thanks - I didn't think to look at the reset circuit of the DSP.
It's an easy fix.

With regards to upper frequency limits of this device, might there be a way to extend it to just beyond the 902-928MHz HAM band - maybe to 950MHz?
I know response will be not great, but it will still be useful performing rough checking on antenna systems.

You have done excellent work on this unit - thanks!

Regards,
Larry

Hi Lapo

My +1 to display as R +/-Jx.

Even will be ideal to display as line graphics: SWR, R and JX !
As some antenna analyzers done it, Rigexpert etc...


73,
Serge

On Sat, Jul 27, 2019 at 06:55 PM, Joe Rocci wrote:

Huge
The "Reference" links at the bottom of the GitHub page don't work.

Joe

The link has been corrected.

On Wed, Jul 31, 2019 at 09:29 AM, Larry Rothman wrote:

Hugen,
Can you please tell me what you changed so I can fix my white unit?
I assume it is an issue with the charger/inverter circuit design?

Thanks,
Larry

On Tue, Jul 30, 2019 at 09:21 PM, <hugen@...> wrote:

The white gecko copied the design of my earlier version, there is a power-on

timing issue, and my new hardware has fixed this problem.

Try to add c38 on my schematic.

Hugen,
Can you please tell me what you changed so I can fix my white unit?
I assume it is an issue with the charger/inverter circuit design?

Thanks,
Larry

On Tue, Jul 30, 2019 at 01:36 AM, Lapo Pieri wrote:

Hi,
02:32 Mon 29 Jul 19 , hugen@... wrote:

You may have pressed the touch screen while adc is initializing.

No, I don't I'm sure

It might be better to add a wait.

I agree. I don't know STM32, I usually develop on NXP LPCxxxx but it seems
to me good.

void adc_init(void)
{
rccEnableADC1(FALSE);

/* Calibration procedure.*/
ADC->CCR = 0;
while (ADC1->CR & ADC_CR_ADEN)
;
ADC1->CR |= ADC_CR_ADCAL;
while (ADC1->CR & ADC_CR_ADCAL)
;

ADC1->CR = ADC_CR_ADEN;
while (!(ADC1->ISR & ADC_ISR_ADRDY))
;
}

Ok, now it works but after a full power-down.
I mean: after re-build and fw load
($ dfu-util -d 0483:df11 -a 0 -s 0x08000000:leave -D build_900/ch.bin)
on subsequent reset it hangs again just after start and stop frequency
printout; switching off and then on rapidly (blue led remains on) it hangs
again. Switching off, waiting for blue led to go down and switching on again
it works. Why?

Many thanks!

Lapo, IK5NAX

Since powering up from DFU mode, aic3204 fails to be initialized at power-on, which will cause I2C abnormality. Re-powering up will make aic3204 normal initialization work normally.

Such a change will cause the adc to fail to calibrate properly, although this will not cause major errors, but it is not recommended.
Do not compile the 1300Mhz version, there will be a big error above 900MHz!
The white gecko copied the design of my earlier version, there is a power-on timing issue, and my new hardware has fixed this problem.

Larry Rothman,
Once again, with the original firmware there are no problems with the inclusion. I corrected the code, now nothing freezes.

void adc_init(void) {
rccEnableADC1(FALSE);
ADC->CCR = 0;
ADC1->CR |= ADC_CR_ADCAL;
ADC1->CR = ADC_CR_ADEN;
while (!(ADC1->ISR & ADC_ISR_ADRDY));
}

I just had a look at hugen's schematic.
He runs a battery charger/inverter chip off of the battery to get +5v.
He then uses a 3.2v LDO regulator (XC6206P322MR) chip to run most of the electronics.
I'm wondering if some of the copies of the original design are using an inferior 3.2v regulator chip or subb'ed it with something else.

It might not fix your issue, which appears to be S/W, but I know that others have some power-up issues like I have with my gecko.

Just a thought...

Larry

One thing you might want to try is to compile a DFU for hugen's 300MHz firmware, then use any free ARM disassembler and compare your compile to Hugen's.
You may be able to zero-in on the problem area.

If you do find the problem, please share with the forum members.
I hope this helps.

Larry