personalities and footprints

[LaurentG]

Hi everybody !

I am currently working on implementing a RDM responder and I have a question concerning personalities.

A personality is associated to a number of slots, no doubt on it. So we can say each sub-device can have a different footprint depending on the selected personality.

However, when performing a GET_DEVICE_INFO, there is a DMX footprint field to fill, and it is not explicitly associated to a personality.
Does this field correspond to the maximum number of DMX slots the sub-device can consume or to the current slot count, associated to the current personality ?

I hope I am clear enough, even if it may sound confused...

[sblair]

Hey Laurent,

Yes the Personality most commonly will affect the Slot Count for both the root device and the sub-device personalities.

The Slot Count in DEVICE_INFO is intended to be the current footprint consumption based on the current Personality setting.

[ericthegeek]

A personality is associated to a number of slots, no doubt on it. So we can say each sub-device can have a different footprint depending on the selected personality.


Yes, each sub-device can have a different footprint and that footprint can change based on the currently selected personality.


However, when performing a GET_DEVICE_INFO, there is a DMX footprint field to fill, and it is not explicitly associated to a personality.
Does this field correspond to the maximum number of DMX slots the sub-device can consume or to the current slot count, associated to the current personality ?


The footprint field in DEVICE_INFO should always reflect the current personality. That means it will report a different footprint when the personality changes.

Most controllers will send a GET DEVICE_INFO after they change the personality to retrieve the information about the new personality.

As a side note: Changing personality can also change the number of sensors reported by a device (or sub-device).

[LaurentG]

Thank you for your replies !