View Single Post
Old September 23rd, 2014   #1
tharron
Junior Member
 
Join Date: Sep 2014
Posts: 10
Default EUID Decode Errors

Hi folks,

I'm working on implementing an RDM client and have gotten most of the way where I need to be. My client responds to the Un-Mute and Discovery packets just fine, but although the DUB response looks fine via packet sniffer (I'm using a DMXter4RDM) I can't get any controllers to accept it. The controller continues all the way down the binary search tree and I keep telling it I'm here, but it never sees a valid packet.

Does anyone have any ideas of where I can look? I'm hard-coding my UID to the same value as a known-good device (HE Labpack). The pre-amble bytes, the encoded UID bytes and checksum bytes all match what is sent by the HE device according to the sniffer, but the controller still rejects it anyway.

Best I can tell my timing is fixed, although I admit I had some issues before that appear to be solved. I'm just not sure where to look next.
tharron is offline   Reply With Quote