Filling Device Labels to 32 chars is an error?

[hamish]

This is my take on it.
I see nothing in the book to mandate that a responder must return the same label as was set. To suggest this rule would cause problems with PIDs such as RESET_DEVICE. Also consider the multi-controller environment of E1.33.

No, this is categorically an Advisory condition.
In the good practice guide, I agree that the better implementation is to return a string length truncated to the capability of the responder. A truncated string should also be reported as an Advisory in a test condition.

Hamish

[este_]

Thanks all for your valuable comments.

I'd like to add another issue, which was this error message:

UnMuteDeviceWithData

UnMute device info with param data.
Category: Network Management
Result: Failed
Debug
Output:
DISCOVERY: pid: DISC_UNMUTE (0x0003), sub device: 0, data: 'x'
Response: RDMResponse:, NACK Format Error, PID = 0x0003

Failed: expected one of:
RDM_TIMEOUT,
RDM_PLUGIN_DISCOVERY_NOT_SUPPORTED

As you can see, I'm doing a NACK Format Error which should be right since the format of the command does not meet the requirements of the standard. Creating a Timeout instead would not even be the second best choice since we'd be losing valuable transmission time. Any suggestions?

[hamish]

Hi Eckart

The information you require to answer your question can be found in table
Table 6-7: Response Type Field Allowable Values from Responder