-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
4G wrong time in Svalbard #69
Comments
After quite some tests I'm pretty sure the code is correct. The value we're reading from the 4G module is bad, but we don't know which value it's because it's not logged. And I've not reproduced the issue locally. So it looks like the bug is in the 4G network in Svalbard, like the 4G operator is sending bad time data. |
Issue #69 - Rewrite the setTimeFrom4G function from the API, now we have control As a consequence the logic is leaner (1st update system time then rtc) - Fix bug when timezone is negative (int8_t instead of uint8_t) - Log debug line with the raw value we read from the 4G module - Workaround, don't update time at midnight local time
The main changes from the commit pushed: Workaround. Don't update the time at midnight local time. This way when deployed this issue should be fixed. But this should be considered a temporary fix. Also, now we log the raw line we read from the 4G module. So when deployed and the SD card retrieved we will know exactly the bad data. |
Open questions:
|
Done today:
TODO:
|
Could this be a time convention problem? One system is using 00:00:00-23:59:59 and the other uses 00:00:01-24:00:00. 2009:12:31:24:00:00 is the same time as 2010:01:01:00:00:00 |
Please post the mote's log file, the exact value sent by the 4G network should be there, so we can know exactly what it is sending. https://github.com/spectraphilic/wasp_sketches/blob/master/libraries/WaspUIO/network_4g.cpp#L193 |
This is what we can see in the log files:
Fixed the workaround in commit 122f5a8 so we skip 2 hours instead of 1. |
To be clear this cannot be a code bug, ours or libelium's, as we're just sending the So this can only be a bug in the LE9100 module or in the 4G network. Actually I tested this in Spain in April and it worked, so this can only come from the 4G network in Norway (is it Telenor?):
|
We have this in the log files from Svalbard:
At midnight (local time) the clock jumps 1 day to the future, and 2 hours later the clock is back to the right time.
The 4G networks was scheduled to run once every 2 hours.
The text was updated successfully, but these errors were encountered: