07-05-2011, 08:53 AM
Hi,
i\'ve a startup response that turns ON some outputs on Comfort and on two SEM\'s
After a reset, the outputs on Comfort are set to ON, but not on SEM\'s
I suspect that SEM\'s take more time to reset and to start communicating over the bus.
For now, i\'m using a TIMER to delay the change of outputs state, but i think that the startup event should fire only after all devices (UCM\'s, SEM\'s, etc.) are ready for operation.
;-)
i\'ve a startup response that turns ON some outputs on Comfort and on two SEM\'s
After a reset, the outputs on Comfort are set to ON, but not on SEM\'s
I suspect that SEM\'s take more time to reset and to start communicating over the bus.
For now, i\'m using a TIMER to delay the change of outputs state, but i think that the startup event should fire only after all devices (UCM\'s, SEM\'s, etc.) are ready for operation.
;-)
