E1.20 RDM (Remote Device Management) Protocol Forums  

Go Back   E1.20 RDM (Remote Device Management) Protocol Forums > RDM Developer Forums > RDM Interpretation Questions

RDM Interpretation Questions Discussion and questions relating to interpreting and understanding the E1.20 RDM Standard.

 
 
Thread Tools Search this Thread Display Modes
Prev Previous Post   Next Post Next
Old March 7th, 2014   #5
nomis52
Task Group Member
 
Join Date: May 2010
Location: San Franciscio
Posts: 57
Default

Quote:
Originally Posted by este_ View Post

Note: Even if you do not support GET_LOCK_PIN, the OLA responders tests try a "GetLockPinWithData" and claim a

"Response: RDMResponse:, Get NACK Unsupported command class, PID: 0x0640"
as
"Failed: expected one of:
CC: Get, PID 0x0640, NACK Format Error
CC: Get, PID 0x0640, ACK, fieds [], values {}"

This may be misleading. You simply cannot generate any answer when you don't support that PID or command class.
It reminds me of the question:
"Which part of 'NO' don't you understand?"

This has been fixed. In the future please report bugs like this on the rdm-testing@ mailing list or file issues in the tracker https://github.com/OpenLightingProject/ola/issues

Simon
nomis52 is offline   Reply With Quote
 

Bookmarks

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
ACT_TIMER to Set messages nic123 RDM Interpretation Questions 3 April 18th, 2014 12:01 PM
DMX_BLOCK_ADDRESS (Set) hamish RDM Interpretation Questions 7 June 26th, 2013 02:53 AM
Sub-device response to SET/GET DMX512 start address p_richart RDM Interpretation Questions 2 September 29th, 2006 09:27 AM


All times are GMT -6. The time now is 01:22 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2026, vBulletin Solutions, Inc.