-
Notifications
You must be signed in to change notification settings - Fork 11
Sensor Wiring Guide
Note: Some Sync Boards do not support 1.8V triggering.
Camera hardware sync verification does not require running the SDK; it only needs the trigger signal and the camera to be properly connected. Therefore, we typically use the camera's bundled software, such as Hikvision's MVS, to verify camera synchronization results.
- Open the camera software, e.g., Hikvision's MVS software
For specific software usage, refer to this page
Follow the tutorial to ensure:
- Camera name is correctly configured
- Camera trigger mode is correctly configured
- Camera exposure time is correctly configured
Afterward, the camera's acquisition frame rate will be displayed in the software interface. When correctly wired and correctly triggered, the camera's acquisition frame rate will match the frame rate set on our Sync Board.

The frame rate displayed in the highlighted area of the image should match the set frame rate — this indicates correct camera sync line connection and correct camera triggering.
Method 1:
- Set the camera frequency to a low frequency, e.g., 1Hz, and place multiple cameras in parallel
- Use the camera software to open multiple camera streams
- Wave an object in front of the lenses and observe whether the position of the moving object is consistent across the multiple captured images.

Method 2:
- Set the camera frequency to a low frequency, e.g., 1Hz, and place multiple cameras in parallel
- Use the camera software to open multiple camera streams
- Display a rapidly changing clock on a phone or other device, and observe whether the times captured by multiple cameras are consistent
Our synchronization is based on UTC time, so we need to obtain UTC time from the host computer and then send it to the LiDAR system. Therefore:
- All LiDAR synchronization requires running the SDK to obtain the correct sync time.
- UTC time will be converted to Unix timestamps, so the baseline for verifying synchronization is whether the time on this webpage and the time published by the LiDAR are essentially consistent. (LiDAR processing may have slight delays)
Any type of LiDAR can use the above method to verify synchronization status.
- Connect the cable between the LiDAR and the Sync Board
- Run the minimal SDK
- Open the LiDAR software or host computer to check synchronization status
Correct synchronization indicators:
- GPS Sync is displayed
- The current time is within 4-5 seconds slower than the time on the webpage.

Currently, devices using Livox Converter 1.0 by default include:
- Mid-40
- Mid-100
Wiring Example:

Since the PC needs to receive GPRMC data and then send it to the LiDAR via the SDK protocol, certain SDK configurations are required:
Specific modifications should be made according to the official documentation for configuration changes
RoboSense LiDAR does not support TTL-level sync data, so the TTL level must be converted to RS-232 level.
For specific sync wiring, refer to: https://blog.csdn.net/weixin_43247057/article/details/128950033
The following status displayed on the LiDAR web interface indicates synchronization:
The key point is that the GPS Data field has data.
Currently, GPS sensors only support the NMEA0183 protocol. The protocol level is 3.3V.
Currently, only external trigger signal synchronization of IMU is supported, meaning the Time Sync Board generates a pulse that triggers the IMU to acquire one data point. The Time Sync Board records each pulse trigger moment, and the IMU should acquire one data point and immediately send a frame of data to the host computer.
- Sync Board trigger line <---> IMU trigger line
- Sync Board GND <---> IMU GND
- Correct wiring
- Configure IMU frequency to a low-frequency signal, e.g., 1Hz
- Use a serial assistant or the IMU's bundled software to read IMU data
- Observe whether the IMU data feedback frequency is the set 1Hz, and whether the IMU data complies with the corresponding communication protocol