I’m using a script on HE910
modules which are running thanks to timers (run this action if you’ve done it
since more than 5 seconds for instance). These timers are working thanks to the
time.time() function.
However, if the module
updates its clock through the GSM network, some of my conditions are no longer
working since time.time() goes from 1587 to 451677930 for instance.
So at each start, I run
during the initialization the command at#NITZ=0 to tell the module not to
update its clock.
However, I keep finding
modules with their clock on time (with CCLK). I have checked and NITZ is still
at 0… I don’t know when the module update its clock but I suspect it may be
before the scripts starts, 10 seconds after it has been power up (I have removed
the PIN code from the SIM cards so I guess a module may connect to the network
in less than 10 seconds…).
Do you have any idea why a
module with at#nitz=0 manage to update its clock?
Is there a command to
keep this command saved in the NVM at each start?
Thanks
The values set by following commands are stored in the profile extended section andthey depend on the specific AT instance (see +CMUX):
…
#NITZ
…
So read 3.3.1. Factory Profile And User Profiles in AT Commands Reference Guide (AT&W and co.)
Hi Cosmin,
I’ve read the sections indicated in the Telit_HE910_UE910_UL865_AT_Commands_Reference_Guide_r7 and I’m a little confused regarding what I found in section 3.3.1…
Indeed, I have found #NITZ in the table where it is said : "The values set by following commands are stored in the profile extended section and they depend on the specific AT instance (see +CMUX)", but I have also found it in the table where it is said : "The values set by following commands are stored in the profile extended section and they don’t depend on the specific AT instance (see +CMUX)".
Which one should I trust?
Hi Cosmin,
I’ve read the sections indicated in the
Telit_HE910_UE910_UL865_AT_Commands_Reference_Guide_r7 and I’m a little
confused regarding what I found in section 3.3.1…
Indeed,
I have found #NITZ in the table where it is said : "The values set by
following commands are stored in the profile extended section and they depend
on the specific AT instance (see +CMUX)", but I have also found it in
the table where it is said : "The values set by following commands are
stored in the profile extended section and they don’t depend on the specific AT instance (see +CMUX)".
Which one should I trust?
Anyway I’m know sending at the initialization of my script the at&W1 and at&P1 commands and for the moment the module remains with its clock not updated.
Thanks for your advice!
In the previous (r6) AT#NITZ appeared only in the first table. I think both tables applies:
– is a global settings so cannot be AT parser different
– the #NITZ URC applies only to the the relevant AT parser
Anyway there are no worries if you don’t use CMUX or or other multiple AT parsers situation.
Just for information, I am now using time.clock() instead of time.time() and it appears that the clock() function is not linked with the module internal clock.
So now, when I uptade the time of the clock, my timers are no longer affected by the update, thus removing all my oversized timers issues!
We use cookies to enhance your browsing experience and help us improve our websites. To improve our website, we carefully select third parties that use cookies to allow us to serve specific content and achieve the purposes set out in our cookie policy. For more information on how to make adjustments through your browser to the cookies being used on your device, please click Find Out More link. By closing this banner or continuing to browse our website, you agree to our use of such cookies. FIND OUT MORE
Normal
0
21
false
false
false
FR
X-NONE
X-NONE
MicrosoftInternetExplorer4
Hello,
I’m using a script on HE910
modules which are running thanks to timers (run this action if you’ve done it
since more than 5 seconds for instance). These timers are working thanks to the
time.time() function.
However, if the module
updates its clock through the GSM network, some of my conditions are no longer
working since time.time() goes from 1587 to 451677930 for instance.
So at each start, I run
during the initialization the command at#NITZ=0 to tell the module not to
update its clock.
However, I keep finding
modules with their clock on time (with CCLK). I have checked and NITZ is still
at 0… I don’t know when the module update its clock but I suspect it may be
before the scripts starts, 10 seconds after it has been power up (I have removed
the PIN code from the SIM cards so I guess a module may connect to the network
in less than 10 seconds…).
Do you have any idea why a
module with at#nitz=0 manage to update its clock?
Is there a command to
keep this command saved in the NVM at each start?
Thanks
So read 3.3.1. Factory Profile And User Profiles in AT Commands Reference Guide (AT&W and co.)
Hi Cosmin,
I’ve read the sections indicated in the Telit_HE910_UE910_UL865_AT_Commands_Reference_Guide_r7 and I’m a little confused regarding what I found in section 3.3.1…
Indeed, I have found #NITZ in the table where it is said : "The values set by following commands are stored in the profile extended section and they depend on the specific AT instance (see +CMUX)", but I have also found it in the table where it is said : "The values set by following commands are stored in the profile extended section and they don’t depend on the specific AT instance (see +CMUX)".
Which one should I trust?
Hi Cosmin,
I’ve read the sections indicated in the
Telit_HE910_UE910_UL865_AT_Commands_Reference_Guide_r7 and I’m a little
confused regarding what I found in section 3.3.1…
Indeed,
I have found #NITZ in the table where it is said : "The values set by
following commands are stored in the profile extended section and they depend
on the specific AT instance (see +CMUX)", but I have also found it in
the table where it is said : "The values set by following commands are
stored in the profile extended section and they don’t depend on the specific AT instance (see +CMUX)".
Which one should I trust?
Anyway I’m know sending at the initialization of my script the at&W1 and at&P1 commands and for the moment the module remains with its clock not updated.
Thanks for your advice!
In the previous (r6) AT#NITZ appeared only in the first table. I think both tables applies:
– is a global settings so cannot be AT parser different
– the #NITZ URC applies only to the the relevant AT parser
Anyway there are no worries if you don’t use CMUX or or other multiple AT parsers situation.
Just for information, I am now using time.clock() instead of time.time() and it appears that the clock() function is not linked with the module internal clock.
So now, when I uptade the time of the clock, my timers are no longer affected by the update, thus removing all my oversized timers issues!
Thank you Jean-Baptiste!