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.

Sign up for GitHub

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

Jump to bottom

Misalignment of decode over time #1

Open
timreyes opened this issue Oct 16, 2019 · 3 comments
Open

Misalignment of decode over time #1

timreyes opened this issue Oct 16, 2019 · 3 comments

Comments

@timreyes
Copy link

timreyes commented Oct 16, 2019 •
edited

Over time, DMX-512 decoded bubbles become misaligned with the data. See capture file below:

dmx512-capture-error.logicdata.zip

Proposed fix: protocol analyzer should re-sync on every start bit.
@timreyes
Copy link
Author

A fix was provided via support in 2017, but it does not help with the above .logicdata file.
DMX512 Analyzer.zip

@timreyes
Copy link
Author

timreyes commented Oct 23, 2019 •
edited

2019-10-23_1820

DMX-512-MAB-issue.zip

Due to the desync, parts of a DMX transmit may be mistakenly read as MAB, which results in dropped slots. See image above. More robust detection methods must be implemented based on DMX spec (see ticket #46657)

@timreyes
Copy link
Author

Another report of this issue:
https://discuss.saleae.com/t/dmx512-analyzer-clock-drift-prevents-proper-decoding-of-whole-frame/1603

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@timreyes