|
RDM General Implementation Discussion General Discussion and questions relating to implementing RDM in a product. |
|
Thread Tools | Search this Thread | Display Modes |
March 13th, 2009 | #1 |
Junior Member
Join Date: Feb 2007
Location: Germany
Posts: 1
|
AVR Responder Lib tested with ENTTEC
Hi all,
just before I heard of the Wybron responder Lib I finished my own for the AVR mcu family. It has less features (no message queu) but seems to be much smaller. Yesterday I tested it with the USB DMX Pro (current RDM FW) and the Controller SW and get a strange behaviour: A commercial device with my lib and enabled DMX termination is discovered but the controller sw receives no device info response (which is implemented). Device identification and the change of the start address can be done with the patch tool. A test circuit without DMX termination with the same lib is not discovered by the controller sw. (The discovery finishes after ~1s without any error messages.) The test circuit indicates the reception of valid discovery msgs and the transmission of the responses... I appreciate any hint or help. best regards, Hendrik responder source code: http://www.hoelscher-hi.de/hendrik/l...ces/rdm_in.zip responder test hardware: http://www.hoelscher-hi.de/hendrik/english/led.htm |
April 10th, 2009 | #2 |
Administrator
|
Hendrik,
As I understand it, you are able to discover the device successfully and GET/SET the DMX Address, but can't get the DEVICE_INFO message. First thing I would do is put a scope on the line and see if the device appears to be responding at all. It could be that the timing window for receiving the message is off. If you aren't seeing any response on the wire at all, then I would look at the data you're sending in the GET:DEVICE_INFO message, make sure that all the fields have valid data and the checksum is correct. It's easy for something like that to cause the responder to trash your request as being invalid...
__________________
Scott M. Blair RDM Protocol Forums Admin |
Bookmarks |
|
|