1,612
edits
Changes
→Camera RTC synchronization
Camera RTC synchronization is done anytime the device itself is synchronized (via NTP, NITZ or GNSS).
Camera RTC synchronization is done anytime the device itself is synchronized (via NTP, NITZ or GNSS).
After 03.27.07.Rev:364 firmware we added a feature to set camera time, same as device selecting time.
After 03.27.07.Rev:364 firmware we added a feature to set camera time, same as device selecting time.
[[File:Zone.jpg|alt=|frameless]]
[[File:Zone.jpg|alt=|frameless]]
'''NOTE''' That after changes of the time it can be that you can receive files which the old-time or just do not have any video/photo on this periodical time then you change time, but then it will be back to normal work.
Time zone changes the inside clock of the camera, not only the OSD displayed time but all recordings will be done according to that.
For example, if you request a video from, say, 9:00 AM GMT+0, and the camera time is GMT+0 (matches our device's time), it is all fine. But if you were to configure time zone later to, for instance, GMT+10, the camera time will be set according to that time zone (time forwarded by 10 hours in this case). Which means that time gets forwarded with no real continuation as the camera does not understand the concept of time zones, it just uses time that we set. For continuation reasons in our device, we continue using GMT+0 in the camreq and then compensate with time zone if needed. The result of that, if we send the same request command as before (when requesting 9:00 AM video) with time zone GMT+10 set, the camera will receive video request for 7 PM (19:00) and the videos were not recorded at that time which will result in "file doesn't exist".
<br>
<br>
