BP Module FAQ
Common error messages and solutions
1.Bag file read error
Meaning: Error reading bag file.
Causes: ① Copy error, file corruption; ② Packaging error, very unlikely.
Solutions: ① Recopy; ② Click the repair icon in the APP;③USB drive format issue, FAT32 does not support copying data above 4GB, please format as exFAT or NTFS format
2.SLAM results may be incorrect
Meaning: SLAM process failed.
Causes: ① Too few features; ② Turning too fast; ③ Number of dynamic object features exceeds that of static objects.
Solution: ① Place the feature object; ② Recollect data; ③ Reduce the feature filter size; ④ Increase the minimum distance in the general settings.
3.Video file:VID_**.MP4 not exist
Meaning: Video file does not exist.
Cause: ① Incorrect video file copied; ② Video file lost;
Solution: ①② Copy the correct and complete video file
4.Current stitcher process isn't completed
Meaning: insv to mp4 conversion incomplete.
Causes: ① Disk speed is occupied; ② Insufficient disk space; ③ Low disk read/write speed; ④ MP4 file is damaged; ④ Antivirus software mistakenly kills the software; ⑤ Insufficient computer memory.
Solution: Check remaining disk space, use a hard drive with good read/write speed; ⑤ Requires a computer with more than 32GB of memory.
5.Move distance insufficient
Meaning: SLAM intermediate result not generated.
Causes: ① IMU and LIDAR time not synchronized; ② Initialization failed; ③ No IMU data.
Solution: ① and ③ are equipment issues; ② requires re-initialization
6.GPS time is out of sync with trajectory time,please check the trajectory
Meaning: The time difference between POS and LiDAR is too large (>1 day).
Causes: ① The time of the base station and the rover do not match; ② The GPS and LiDAR of the equipment are not synchronized.
Solution: ① Confirm whether the base station file and the rover file match; ② Consult after-sales service.
7.GCP initial transform error, please check GCP pairs
Meaning: The initial matching error of the GCP is too large.
Cause: The initial error between the control point and the GCP collection is too large.
Solution: Check the error before the GCP, ① reorganize the matching relationship between the GCP collection and the control point, ② or check if X and Y are reversed.
8.GNSS file doesn't exit
Meaning: *.gnsstraj file does not exist.
Cause: *.gnsstraj is missing or damaged, or has been modified.
Solution: Reprocess PPK or import RTK file.
9.Re-output lidata failed
Meaning: Point cloud output failed.
Cause: ① The previous lidata file is missing or damaged; ② Insufficient disk space.
Solution: Ensure sufficient disk space and re-output.
10.No origin insta video please check data
Meaning: The video file directory does not contain the original insta video.
Cause: INSV and the converted panoramic MP4 are not in the same folder.
Solution: Recopy the original INSV file.
11.Stitcher timeout break, video stitching error/Fail stitcher insv to MP4
Meaning: The merge subroutine failed.
Cause: ① Antivirus software; ② Original file is damaged.
Solution: ① Turn off antivirus software; ② Recopy the video file; ③ Reinstall the software.
GNSS
1.GPS base station file format error
Meaning: GPS base station data format error
Cause: GPS format issue
Solution: Please convert to standard RINEX (V2.11-3.03)
2.It is detected that the difference between the manually input base station position and the rough position obtained from the original data unpacking of the base station is too large, with a difference of more than 1000 meters. It is suspected that the input base station position is wrong or the base station file is wrong. Please verify !
Meaning: The difference between the coordinates of GPS single point positioning and the input base station coordinates is too large, more than 1000 meters
Cause: The entered base station coordinates are incorrect
Solution: Check the entered base station coordinates
3.It is detected that there is no common viewing time between base station data and mobile station data. It is suspected that the input original data is wrong.
Meaning: The coverage time of the GPS base station is inconsistent with that of the Rover
Causes: ① Copy the correct base station file; ② The base station file is damaged
Solution: Copy or use the correct base station file
4.The time of the mobile station is too short to meet the normal solution conditions
Meaning: The time of Rover is too short to get a fixed solution
Cause: Short collection time
Solution: It is recommended to collect data for more than 5 minutes when using PPK mode
5.The ephemeris files of the mobile station and the base station are missing and canot be solved. Please check the reason (possible cause: the data is too short or the equipment factory configuration is wrong).
Meaning: The ephemeris of the base station or Rover is lost
Cause: acquisition time is too short or factory settings error
Solution: It is recommended to collect data for more than 5 minutes when using PPK mode or contact the after-sales team
6.Failed to load file: "**.rtk". The quality of the result trajectory is too low!
Meaning: The RTK quality is too low to be loaded
Cause: RTK is a floating at all the collection time
Solution: ①: Use PPK; ② Re collect
GAP
1.Laser gap
Meaning: LiDAR data loss.
Causes: LiDAR data is lost during data collection.
Solution: ① The APP will prompt if data is lost, and fieldwork needs to recollect; ② Check if the cables are properly connected; ③ For other situations, please contact after-sales.
2.IMU gap
Meaning: IMU data loss.
Cause: IMU data loss during equipment data collection.
Solution: ① The data loss APP will prompt, and fieldwork will need to recollect; ② Check if the cables are properly connected; ③ Other situations.