开云体育

Hello guys,

I am writing this message to understand why my VNA-H4 has the internal clock that runs a lot, compared to that of the PC.
I'll explain better what I mean.

After the firmware update to DiSlord version 1.0.69, I proceeded to configure the internal date and time of the instrument, via serial connection (linux terminal command: minicom -D /dev/ttyACM0 ).

I typed the single following commands, to configure the date and time.

time y 21
time m 7
time d 28
time h 15
time min 07
time sec 30

everything worked perfectly, but ...? after about an hour I could see that the time on the VNA-H4, compared to the same PC, had advanced by about 20 seconds.

in addition to this, I report another problem.

If I turn off the VNA, the advancement of the time also stops and resumes only when the instrument is turned on, remaining delayed by the time it was off.
I believe that the internal RTC system is not self-powered when the device is off.? In this way the correct use of the date and time of the instrument is compromised.

Do you have any ideas about it?

My best regards to everyone,

'73 de Paolo IV3BVK (K1BVK)


--
Paolo Garbin - IV3BVK - K1BVK

WW LOC JN65GX - 33074 Fontanafredda (PN)
Inviato con Thunderbird su Distribuzione Linux random

Nota di riservatezza / Confidentiality note
Il messaggio può contenere informazioni strettamente confidenziali, urgenti e coperte da segreto professionale. Salvo che non sia espressamente autorizzato è, pertanto, strettamente proibito qualsiasi uso, comunicazione, copia o diffusione non autorizzata dei contenuti di questo documento. La diffusione, distribuzione e/o copiatura dei documenti trasmessi da parte di qualsiasi soggetto diverso dal destinatario è proibita sia ai sensi dell'art. 616 c.p. sia ai sensi del D.Lgs. 196/2003. Nel caso in cui abbiate ricevuto per errore la presente comunicazione, vogliate cortesemente darcene immediata notizia e cancellare questo messaggio dal Vostro sistema. In ogni caso, il mittente, in ragione del mezzo di trasmissione utilizzato, non assume alcuna responsabilità in merito alla segretezza e riservatezza delle informazioni contenute nel presente messaggio e nei relativi allegati.

This message may contain information which are strictly confidential, urgent and protected by professional secrecy. It is then strictly prohibited, unless expressly authorized, any use, disclosure, copying or distribution of the content of this communication. If you have received this communication in error, please notify us immediately and then delete it from your system. In any case, considering the means of transmission, we do not undertake any liability with respect to the secrecy and confidentiality of the information contained in this e-mail and in its attachments.

The HE model does NOT come with a built-in 32KHz xtal. So, the clock will behave erratic because the cpu is using the built-in reference that runs when the Nano is powered but halts when the unit is off.?
You must manually install a 32KHz xtal for the unit to keep constant and accurate time. My units (H & H4 ) both have xtals and slowly gain a couple of minutes per week.?
So, it appears your H4 does not have an external 32KHz xtal. I got mine from old PC motherboards and had to pad one with an 8pf cap to slow it down a little.?
Scroll through the photos on the forum and you'll find an image of the H4 with the xtal soldered to p14 and p15 along the bottom. The firmware automatically senses it and runs accordingly.?


On Wed., 28 Jul. 2021 at 9:17 a.m., Paolo Garbin IV3BVK<iv3bvk@...> wrote: Hello guys,

I am writing this message to understand why my VNA-H4 has the internal
clock that runs a lot, compared to that of the PC.
I'll explain better what I mean.

After the firmware update to DiSlord version 1.0.69, I proceeded to
configure the internal date and time of the instrument, via serial
connection (linux terminal command: minicom -D /dev/ttyACM0 ).

I typed the single following commands, to configure the date and time.

time y 21
time m 7
time d 28
time h 15
time min 07
time sec 30

everything worked perfectly, but ...? after about an hour I could see
that the time on the VNA-H4, compared to the same PC, had advanced by
about 20 seconds.

in addition to this, I report another problem.

If I turn off the VNA, the advancement of the time also stops and
resumes only when the instrument is turned on, remaining delayed by the
time it was off.
I believe that the internal RTC system is not self-powered when the
device is off.? In this way the correct use of the date and time of the
instrument is compromised.

Do you have any ideas about it?

My best regards to everyone,

'73 de Paolo IV3BVK (K1BVK)


--
Paolo Garbin - IV3BVK - K1BVK

WW LOC JN65GX - 33074 Fontanafredda (PN)
Inviato con Thunderbird su Distribuzione Linux random

Nota di riservatezza / Confidentiality note
Il messaggio può contenere informazioni strettamente confidenziali, urgenti e coperte da segreto professionale. Salvo che non sia espressamente autorizzato è, pertanto, strettamente proibito qualsiasi uso, comunicazione, copia o diffusione non autorizzata dei contenuti di questo documento. La diffusione, distribuzione e/o copiatura dei documenti trasmessi da parte di qualsiasi soggetto diverso dal destinatario è proibita sia ai sensi dell'art. 616 c.p. sia ai sensi del D.Lgs. 196/2003. Nel caso in cui abbiate ricevuto per errore la presente comunicazione, vogliate cortesemente darcene immediata notizia e cancellare questo messaggio dal Vostro sistema. In ogni caso, il mittente, in ragione del mezzo di trasmissione utilizzato, non assume alcuna responsabilità in merito alla segretezza e riservatezza delle informazioni contenute nel presente messaggio e nei relativi allegati.

This message may contain information which are strictly confidential, urgent and protected by professional secrecy. It is then strictly prohibited, unless expressly authorized, any use, disclosure, copying or distribution of the content of this communication. If you have received this communication in error, please notify us immediately and then delete it from your system. In any case, considering the means of transmission, we do not undertake any liability with respect to the secrecy and confidentiality of the information contained in this e-mail and in its attachments.

Refer to the photo here for the location of the external 32KHz xtal on the H4;

/g/nanovna-users/message/14649

Many thanks Larry,

you were precise and very fast in your response. I will try to find the components and make the modification you indicated.

'73 de Paolo IV3BVK

--
Paolo Garbin - IV3BVK - K1BVK

WW LOC JN65GX - 33074 Fontanafredda (PN)
Inviato con Thunderbird su Distribuzione Linux random

Nota di riservatezza / Confidentiality note
Il messaggio può contenere informazioni strettamente confidenziali, urgenti e coperte da segreto professionale. Salvo che non sia espressamente autorizzato è, pertanto, strettamente proibito qualsiasi uso, comunicazione, copia o diffusione non autorizzata dei contenuti di questo documento. La diffusione, distribuzione e/o copiatura dei documenti trasmessi da parte di qualsiasi soggetto diverso dal destinatario è proibita sia ai sensi dell'art. 616 c.p. sia ai sensi del D.Lgs. 196/2003. Nel caso in cui abbiate ricevuto per errore la presente comunicazione, vogliate cortesemente darcene immediata notizia e cancellare questo messaggio dal Vostro sistema. In ogni caso, il mittente, in ragione del mezzo di trasmissione utilizzato, non assume alcuna responsabilità in merito alla segretezza e riservatezza delle informazioni contenute nel presente messaggio e nei relativi allegati.

This message may contain information which are strictly confidential, urgent and protected by professional secrecy. It is then strictly prohibited, unless expressly authorized, any use, disclosure, copying or distribution of the content of this communication. If you have received this communication in error, please notify us immediately and then delete it from your system. In any case, considering the means of transmission, we do not undertake any liability with respect to the secrecy and confidentiality of the information contained in this e-mail and in its attachments.

On Wed, Jul 28, 2021 at 06:16 AM, Paolo Garbin IV3BVK wrote:

Hello guys,

I am writing this message to understand why my VNA-H4 has the internal
clock that runs a lot, compared to that of the PC.
I'll explain better what I mean.

After the firmware update to DiSlord version 1.0.69, I proceeded to
configure the internal date and time of the instrument, via serial
connection (linux terminal command: minicom -D /dev/ttyACM0 ).

I typed the single following commands, to configure the date and time.

time y 21
time m 7
time d 28
time h 15
time min 07
time sec 30

I own a -H4 that does not have the Xtal installed. The time under Version says 2000/01/01 00:00:07 (LSE)

I have tried to use the commands above to set the time and they appear to be accepted without an error message but the time does not change. Just stays stuck on 2000/01/01 00:00:07.

What am I doing wrong?

The reason I am trying to get the time going is because I thought it might have something to do with writing files to the SD card. I can successfully write screenshot bmp, s1p and s2p files but only with one name "VNA_000101_000007". If I attempt to output a second screenshot it just overwrites the existing file. I thought maybe it had something to do with time stamping the file.

Any help appreciated...

Roger

Roger,
Try setting the time using OneOfEleven's Nanovna-App. It's under Settings. I had a similar issue with my H4 with 1.0.44 through 1.0.47 FW. The app uses the binary mode to set the time.?
Note that if you select the version screen while connected to the PC, the connection will drop and you'll have to refresh.?
... Larry


On Fri., 30 Jul. 2021 at 7:01 p.m., Roger Need via groups.io<sailtamarack@...> wrote: On Wed, Jul 28, 2021 at 06:16 AM, Paolo Garbin IV3BVK wrote:

Hello guys,

I am writing this message to understand why my VNA-H4 has the internal
clock that runs a lot, compared to that of the PC.
I'll explain better what I mean.

After the firmware update to DiSlord version 1.0.69, I proceeded to
configure the internal date and time of the instrument, via serial
connection (linux terminal command: minicom -D /dev/ttyACM0 ).

I typed the single following commands, to configure the date and time.

time y 21
time m 7
time d 28
time h 15
time min 07
time sec 30

I own a -H4 that does not have the Xtal installed.? The time under Version says 2000/01/01 00:00:07 (LSE)

I have tried to use the commands above to set the time and they appear to be accepted without an error message but the time does not change.? Just stays stuck on 2000/01/01 00:00:07.

What am I doing wrong?

The reason I am trying to get the time going is because I thought it might have something to do with writing files to the SD card.? I can successfully write screenshot bmp, s1p and s2p files but only with one name? "VNA_000101_000007".? If I attempt to output a second screenshot it just overwrites the existing file.? I thought maybe it had something to do with time stamping the file.

Any help appreciated...

Roger

I add xtal autodetect (for more easy support vs xtal and no), but in some rare cases LSE mode enabled if no xtal on device. Need remove battery and reset this state.
But better instal it for more stable work.