View Single Post
Old November 24th, 2015   #2
dj41354
Member
 
Join Date: Nov 2015
Posts: 30
Default

Had a quick conversation with Bob Goddard. He suggested I build a custom packet (an easy one like GET_DMX_START_ADDRESS) and then get the timing information..
I had a little trouble getting it.. but think I finally was successful..

RESPONDER TIMING MIN PRV MAX
RESPONSE DELAY IN us 178 178 178
BREAK LENGTH IN us 256 258 258
MAB LENGTH IN us 87 87 89
INTERSLOT TIME IN us 40 45
TOTAL LENGTH IN us 2541 4179 4179
DISC. FIRST ACTIVITY (EMPTY)
DISC. LAST ACTIVITY (EMPTY)
UNICAST 5 / 9
DISCOVER 0 / 0
UNICAST RETRY COUNT 0
NOISE BEFORE BREAK 0
NSC PACKET COUNT 2686

When I did this (build a custom packet) it seemed happy with the response.
On my logic analyzer, I'm like 180usec from the last stop bit (of the controller) to my responder asserting the leading edge of the break.
Is there some kind of weirdness when not using BUILD CUSTOM PACKET that is causing me an issue?
Thanks..
Doug.
dj41354 is offline   Reply With Quote