View Single Post
Old May 5th, 2017   #1
Junior Member
Join Date: Jan 2015
Posts: 3
Default How to handle DMX Footprint overrun

Hi All,

I've just had an interesting question proposed to me by some other people in my company.

How should a responded behave in a situation where the DMX_START_ADDRESS of a device (root or sub-device) is set to a value greater than (512 - DMX_FOOTPRINT)

Should this behavior be the same for both DMX_START_ADDRESS and DMX_BLOCK_ADDRESS?

My current implementation is an LED driver with 12 sub-devices, each containing 4 channels, if DMX_BLOCK_ADDRESS is used to set the start address of the sub-devices so that any have a DMX_START_ADDRESS above 512 they will set their start addresses to 512. Is there any more guidance on best/recommended practice in this situation?

Thanks in advance,

// Robb
RobbG is offline   Reply With Quote