LDS data protocol should be identified #5
Description
Use Case
To write a parser for LDS data, the data format must first be identified.
Gathering the data from the LDS Gen1 and Gen2 are the first steps for that.
Acceptance Criteria
GIVEN Gen1 and Gen2 packet data
WHEN analyzing the data
THEN the protocol should be identifiable and documented in a wiki.
Dev Notes
The work here should involve hooking the Gen1 and Gen2 LDS' to a logic analyzer and recording data. Given that data, we should be able to use information found here as a starting point, to identify the protocol.
Note: This is not intended to include data from the LDS when spinning and producing range data. It is likely that the data packets in each LDS frame/packet contains only error codes (numbers starting with 8000 {hex???}).
Just identifying the protocol itself is intended here.