Closed YikangZhang1641 closed 6 months ago
Anyone who came from https://github.com/sheng00125/LIV_handhold or https://gitee.com/gwmunan/fast-livo_-reproduction trying to set hardware trigger might face the same problem. The original GPRMC generating code in Timer.c might work for AVIA but definitely not for mid360. Checksum should be added and global time should be "hhmmss.00" format instead of second counts.
Solved. Caused by illegal GPRMC msg. Nothing wrong with Mid360.
This happends frequently:
Before time 45.485, everything's OK. 10Hz Pointcloud and 200Hz IMU are well synchronized. Something happens. After time 45.491, no Pointcloud but only IMU packets are transferred.
Pointcloud packets are resumed at time 85.484
With no hardware changed, the Lidar would be muted for exact 40s and awake for 60s, and then repeats in the next 100s loop:
At time 145.495, pointclouds start to be missing again
until 185.488
miss at 245.495
resume at 285.493
With the PPS/GPRMC cable disconnected, "Time Sync Type" is still "GPS Sync", but everything's fine and continuous. However, if reconnected afterwards, pointclouds would be stuck again much longer, sometimes freeze forever.