Sub-Device Status Threshold - E1.20 RDM (Remote Device Management) Protocol Forums

sblair · August 15th, 2011

I'll let you know what it means when someone decides to implement Sub-Devices

The _CLEARED messages were not part of the original version as you know. We never looked at the _CLEARED messages in regards to use with this PID when we added them. That is an oversight.

These were intended to follow the same logic as Table 10-1. That table was not referenced in this section but it should have been. It was certainly the intent in our discussions that the same logic as Table 10-1 is used here. Such that, when setting the PID value for this to: ERROR, you would only get errors. Setting to WARNINGS would produce warning and error events. Setting to ADVISORY would get you all three and NONE would obviously mute all status messages for that sub-device.

We will need to clean the language up here in the next round to make these points clearer.

August 15th, 2011	#3
sblair Administrator Join Date: Feb 2006 Posts: 441	I'll let you know what it means when someone decides to implement Sub-Devices The _CLEARED messages were not part of the original version as you know. We never looked at the _CLEARED messages in regards to use with this PID when we added them. That is an oversight. These were intended to follow the same logic as Table 10-1. That table was not referenced in this section but it should have been. It was certainly the intent in our discussions that the same logic as Table 10-1 is used here. Such that, when setting the PID value for this to: ERROR, you would only get errors. Setting to WARNINGS would produce warning and error events. Setting to ADVISORY would get you all three and NONE would obviously mute all status messages for that sub-device. We will need to clean the language up here in the next round to make these points clearer. __________________ Scott M. Blair RDM Protocol Forums Admin