View Single Post
Old February 5th, 2009   #5
sblair
Administrator
 
Join Date: Feb 2006
Posts: 433
Send a message via AIM to sblair Send a message via MSN to sblair
Default

Andy,

This was something that was discussed a lot during development and we did try to put some hard rules in place where we could.

Section 10.4.1 states the following:

Quote:
Devices with the same Manufacturer ID, Device Model ID, and Software Version ID response for the DEVICE_INFO parameter shall report an identical list for the SUPPORTED_PARAMETERS message. This allows the controller to reduce the quantity of information stored for identical devices.



That is one big reduction there. This eliminates asking every device for supported parameter lists. Slot descriptions could be different obviously depending on protocol mode but also on model ID or sub-device related info. Imagine an X-Spot with different modules in it for example.

10.5.1 also states:

Quote:

Device Model ID:

This field identifies the Device Model ID of the Root Device or the Sub-Device. The Manufacturer shall not use the same ID to represent more than one unique model type.

A text description for the Device Model ID can be retrieved from the device using the DEVICE_MODEL_DESCRIPTION Parameter.


While not out-right stating it, it does appear pretty clear here that for the same Device Model ID you should get the same text description back.

In the same section:
Quote:

Any devices from the same manufacturer with differing software shall not report back the same Software Version ID.


In Section 10.5.4:
Quote:
10.5.4 Get Manufacturer Label (MANUFACTURER_LABEL)


This parameter provides an ASCII text response with the Manufacturer name for the device of up to 32 characters. The Manufacturer name must be consistent between all products manufactured within an ESTA Manufacturer ID.
This is another reduction for getting the same information from all the devices.

Hopefully these help some, please let me know if there are any other specific ones that are in question also.





__________________
Scott M. Blair
RDM Protocol Forums Admin
sblair is offline   Reply With Quote