I think it’s sent through ipc tunnel. But I still didn’t got right.
You can help here.
Thanks, I think I figured it out another solution: You can publish the ego-planner output to MAVROS using /setpoint_raw/local.
@chobitsfan ,
kudos for the awesome work!!
I had some queries regarding system time synchronization and synchronization between IMU and camera frames:
BRD_RTC_TYPES
to 1, which is Mavlink SYSTEM_TIME
.SYSTEM_TIME
msgs(via MAVROS) and uses the Mavlink TIMESYNC
message to synchronize the system time between FCU and RPi, right?TIMESYNC
Mavlink msg from FCU?TIMESYNC
helps you find the offset between the FCU and On-Board Computer, which you add/ subtract to the time stamp sent for the HIGHRES IMU
Mavlink msg from FCU. Am I right in understanding this?SYSTEM_TIME
and TIMESYNC
messages in helping onboard computer and FCU time sync?BRD_RTC_TYPES
is set to 1, is FCU time set to the time_unix_usec
field value from the SYSTEM_TIME
msg?TIMESYNC
msg used in this process? Is it to calculate the offset between the onboard computer time and FCU system time(the one set by Mavlink SYSTEM_TIME
msg) to account for communication offsets?Hi
SYSTEM_TIME
is only used to set FC log time, so that it is easier to know when did this flight happen. TIMESYNC
is used to measure the time offset between FC and pi. Timestamp used in vins-mono is based on pi time.