Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LDS data protocol should be identified #5

Open
griswaldbrooks opened this issue Mar 17, 2019 · 0 comments
Open

LDS data protocol should be identified #5

griswaldbrooks opened this issue Mar 17, 2019 · 0 comments

Comments

@griswaldbrooks
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant