After I successfully connected to the GPS, I found that the event stamp obtained was the London area timestamp, without adding the time zone offset, I manually added the offset to the timestamp obtained from gps, but I found that the time on the MP was correct, but the time zone was obviously added to the time zone offset when the log was generated, in layman’s terms, the time system on the log file automatically added the time zone offset, and the time on the MP was not added, how to deal with this
Try setting the correct value into the BRD_RTC_TZ_MIN parameter.
You would have got this right the first time if you had been using the ArduPilot Methodic Configurator software, available in chinese.
1 Like
I tried to modify the parameter you suggested in Mission Planner, but it didn’t work, apparently having no effect on either the system time or the log time in Mission Planner. Then, I attempted to change the time at which the log files are generated. This only resulted in the correct time for the first log file generated after the first unlock post-power-up. Subsequent unlocks after power-up still resulted in the time being off by eight hours.
For instance, as shown in the image, I created a new log at 22:38. At that time, the time was correct. However, when I tried to recreate it at 42 minutes later, the previous file seemed to have an error and showed up as six in the morning of the next day.
Why double posting?
Don’t change the Firmware only the parameter BRD_RTC_TC_MIN
Time of FC and time of Missionplanner are not aligned if the FC uses GPS-timesource BRD_RTC_TYPES = 1