View Single Post
Old December 9th, 2013   #5
ericthegeek
Task Group Member
 
Join Date: Aug 2008
Posts: 375
Default

I skimmed Enttec's documents.

Are you using this Enttec RDM Library for Windows:
http://www.enttec.com/?main_menu=Products&pn=70533

Or are you using their USB Protocol directly?
http://www.enttec.com/docs/dmx_usb_pro_api_spec.pdf

Since you mentioned disabling the Transaction Number, it appears you must be using the USB protocol (since the RDM Library spec doesn't mention a way to disable the Transaction Number sequencing).

Did you see the following in the "RDM Implemention Details" section of the USB protocol document?

"The Widget UID consists of the Enttec manufacturer ID concatenated with the Widget Serial Number, as follows: UID[0]=hex 45, UID[1]=hex 4E, UID[2]=SN[3], UID[3]=SN[2], UID[4]=SN[1], UID[5]=SN[0]."

Are you using this UID in the "Source UID" field for your RDM Requests? (If this UID is in the "Source UID" for a request, the responder should copy it into the "Destination UID" for the response.). It may be that the RDM USB Pro will only accept responses with this UID.


As a side note: You're making life unnecessarily hard on yourself by trying to implement both the controller and the responder by yourself right out of the gate. There is good RDM test equipment available these days that can tell you exactly what's wrong rather than you having to guess. I'll put in a shameless plug for a DMXter4RDM with the Advanced RDM option because it's designed for exactly this kind of development work, but I'm not exactly unbiased since I've worked for GDC. There are other products available too.
ericthegeek is offline   Reply With Quote