Skip to content
Trip Vest edited this page May 22, 2018 · 2 revisions

Motor Control Overview

Motor controllers will (likely) be configured to accept simply desired position from LX. The motor controller control algorithms will handle:

  • Homing upon startup
  • Protection from catastrophic failure
  • Some level of smoothing and damping to produce aesthetic motor movements

Motor Control API

Desired Absolute Linear Position

0-255 Byte
0 = Home Position = Bloom totally folded (for protection against wind upon startup )
255 = Bloom totally open

For a given hub:
Universe 16
Channel 1 = Byte for Desired Absolute Linear Position

Data Flow Overview

Motor Control Data Flow Diagram

LX

  1. Each bloom will be modeled as a dummy RGBA pixel in LX.
  2. The desired position state will be stored in the RED byte.
  3. LX will load the Desired Position data into Universe 16, Channel 1 of the SACNDatagram of the corresponding PixLite.
  4. LX will output this information every frame, likely at 60 frames / second.

PixLite

PixLite will be configured to pass through Universe 16, Channel 1 to its physical DMX Output. PixLite 4 DMX512 Output

[INSERT IMAGE ADVATEK CONFIGURATION]

Motor Controller

The Motor Controller will be attached to the PixLite's physical DMX Output. It's control firmware will use the byte at Universe 16, Channel 1 to drive the motor to the desired position.

The actuation distance is roughly 32", giving about 1/8" control resolution.

Clone this wiki locally