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

Are you saying that you're putting a Broadcast UID in the "Destination UID" field for the GET_COMMAND_RESPONSE packet? This may be a quirk of the Enttec software API, but it's unlikely to work with many RDM controllers. The "Destination UID" field for a response should be the UID of the RDM controller that sent the GET request. The broadcast UIDs "BROADCAST_ALL_DEVICES_ID" and "ALL_DEVICES_ID" are only defined for requests in section 5.2 of the RDM Standard.

I've never used the Enttec API for windows. Does your windows software pass fully formed RDM packets to the API, and the API simply passes them along to the 485 wire? Or, do you just send the payload to the API, and the Enttec software takes care of building the packet? It may be that you have to ask the API for the RDM USB PRO's UID, then include that UID when building RDM requests.
ericthegeek is offline   Reply With Quote