Pixelstring on RDM
Hi all,
assume following product:
- A string of RGB pixels, being RDM compatible
- The string can contain anything between 1 and 100 pixels
- The DMX Footprint can therefore be anywhere between 3 and 300 DMX channels.
What is the most appropriate way of implementing this?
A) Have unique Device Model ID for each possible string length / pixel quantity.
-> The leads to generating 100 different Device Model IDs, each with a static DMX512 footprint
-> The device will then change its Device Model ID when the amount of pixels is modified (by the user)
B) Have a single Device Model ID for all possible string lengths / pixel quantities, and use DMX512 footprint according to string length.
-> This leads to the situation that (for example) device A of this Model ID reports a DMX152 footprint of 150 channels (as it has 50 pixels), whereas device B (with the same Model ID) report a DMX512 footprint of 300 channels (as it has 100 pixels).
C) Have a single Device Model ID for all possible string lengths / pixel quantities, and identify each pixel as sub-device.
-> This leads to the situation that (for example) device A of this Model ID reports that it has 50 sub-devices (as it has 50 pixels), whereas device B (with the same Model ID) reports that it has 100 sub-devices (as it has 100 pixels).
It it allowed for two devices with the same Device Model ID to:
B) Report different DMX512 footprint values
C) Report different Sub-Device Counts
Best Regards,
W
|