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

Timer.h / Responder: Response -> Controller: Any Packet #177

Open
kudiltz opened this issue Oct 25, 2024 · 2 comments
Open

Timer.h / Responder: Response -> Controller: Any Packet #177

kudiltz opened this issue Oct 25, 2024 · 2 comments

Comments

@kudiltz
Copy link

kudiltz commented Oct 25, 2024

Testing RDM controller against a number of responders hung the UART on two different responders. Most have not had this issue, though.

Looking closer, the timing between response to mute and the next controller transaction appears to be 77uS:
image

From the standard at least 176 is required:
image

I see nearly all of the other timing requirements in this table are accounted for. Am I missing this one?

Generally very good marks on the rest of the tests I've run the controller through! So, thank again.

@ebeam-bob
Copy link

@kudiltz What tool did you use to trace all that packet timing? I'd like to know what hardware and software you used.

@kudiltz
Copy link
Author

kudiltz commented Oct 31, 2024

@kudiltz What tool did you use to trace all that packet timing? I'd like to know what hardware and software you used.

@ebeam-bob I had an opportunity to use a DMXter4A RDM from Goddard: http://www.goddarddesign.com/
which has USB connection to teminal emulator like Terra Term.

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

2 participants