See attached Screen shots showing the SC time when turned on before updating using WIFI network time, then the SC time after updating using WIFI network and the last screen shot attachment shows todays flight log with the correct time. Conclusion: when the SC is shut off it reverts to a date & time of Januand 0150, it doesn’t retain the correct date and time and as a result all subsequent flight logs, videos, and photos are stamped with this incorrect date & time. The resulting flight log, and videos stored on the Mavic 2 zoom onboard MicroSD card, had the correct date and time. I went to where I could reconnect to WIFI and let the SC update to the correct date and this time, left the SC on, disconnected from WIFI, and flew. When I turned on the SC minutes later with no WIFI connection, to fly, I noticed the date & time was back to Januand 0150. Today I planned a waypoint flight while on WIFI verified the date and time was correct and saved the plan then shut off the SC. I verified today that the Smart Controller(SC) reverts to the Janudate and time of 0150 when shut off. It would seem obvious to me that the internal date, time and time zone in the controller shouldnt reset because its powered down. So can others confirm that turning the controller off and then back on causes the data and time to be reset (note that I dont automatically resynch with WIFI but if I do the Date and Time is lost on restart until I do resynch with wifi). I see several others reporting problems with date and time issues in other threads - and wonder if they are all related to the same issue.ĭJI support does not seem to be aware of the issue and suggested I send my controller in for repair - but that would not make sense to me if it worked with the prior firmware and others are having the same issue. This caused a lot of confusion when reading articles about this issue because in the context of timesyncd the NTP protocol is of course used but this has nothing to do with the ntp installation/ ntpd command as I understand it.After I updated the smart controller firmware to 0400 i noticed that all my pictures captured from my mavic 2 pro all ended up with the same date regardless of the day they were taken on.Īfter playing around with the controller I now find that the date and time is reset everytime I turn the controller off and back on. The old ntpd service which I suppose is installed via sudo apt-get install ntp is not the same as the NTP protocol itself. timesyncd will generally do the right thing keeping your time in sync Ntpdate is considered deprecated in favor of timedatectl (or chrony) and thereby no more installed by default. But it also implies that on an upgrade from a former release ntp/ntpdate might still be installed and therefore renders the new systemd based services disabled. While no more recommended to be used, this still also applies to ntpd being installed to retain any kind of old behavior/config that you had through an upgrade. That shall ensure that no two time syncing services are fighting. Timesyncd which seems to be the new way since Ubuntu 16.04 (with config file /etc/systemd/nf): > which is probably still installed on my system as it has been upgraded several times from older Ubuntu distributions Ntp (more exactly ntpd with its config file /etc/ntp.conf) Ok, by now I have understood that there are actually two separate ways to manage/sync the time in Ubuntu: What kind of mechanism may interfere here which resets the "Local time" to the wrong time every time again? Then I did sudo timedatectl set-time 14:25:00 to set the system clock to the specified time so that the unsynchronized system time will be rather close to the "real" time.Īfterwards the time actually seems to be (more) correct (although saying "System clock synchronized: no"): timedatectlīut suddenly (about half a minute later) I get this again (Local/Universal time != RTC time): timedatectl To do so I have included some time servers in my /etc/ntp.conf (as described here) and restarted ntp via sudo service ntp restart: server 0.de. I have a server (Ubuntu 20.04) with an asynchronous time (wrong by around 7.5 minutes RTC already seems to be equal/close to the "real" time) which I want to correct: timedatectl
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |