I connected a GPS device with my LiDAR following this instruction: https://forum.ouster.at/d/74-how-to-synchronize-gps-with-ouster-sensor-rev-d
The LiDAR is able to receive NMEA messages correctly. I checked it with the time API and the NMEA messages get updated every second. The problem is the PPS signal. The LED inside of the sensor box lights up every second indicating the working PPS. However in Ouster studio the timestamps reset every 4 Seconds.
For example: raw timestamps go from 8000000000 (8 seconds) to 12000000000 (12 seconds) and back to 8000000000. It does not update to the current unix timestamp of the NMEA message unless one of two things happen:
I reconfigure the sync_pulse_in_polarity from ACTIVE_LOW to ACTIVE_HIGH and then back to ACTIVE_LOW. It updates once to the current unix timestamp and the same behaviour starts again. It counts for 4 seconds and returns to the old unix timestamp. The PPS signal should trigger on ACTIVE_HIGH which makes this behaviour even more suprising. The PPS signal is locked for one second with this method.
When the Ouster Studio freezes the terminal does not receive any more RECV packets. However in the web api the PPS signal is suddenly locked and it updates the unix timestamps correctly. The ouster studio freezes after around 25 Minutes and I am literally doing nothing.
If the PPS signal is locked the api looks as follows (link to picture):
The GPS I am using is this one: https://static.garmin.com/pumac/GPS_18x_Tech_Specs.pdf
Any idea to explain this behaviour would help, thank you.