Skip to content
Trip Vest edited this page May 22, 2018 · 1 revision

Motor Implementation

  • Dummy Pixel Infrastructure. Implement desired dummy pixel infrastructure for motor control. [@msclee]
  • SACNDatagram Motor Output. Connect R byte from RGBA dummy pixel to Universe 16, Channel 1 on associated PixLite output. [TBD]
  • Canonical motor driving pattern with proper API and if applicable, function calls. [@msclee]
  • Motor Control Enabled Pattern UI Element. To show patterns with motor control enabled. [@msclee]
  • End to End Test with Motor Controller. [TBD]

Mapping

  • Update Model. Incorporate physical parametrization. [@tripish]
  • Fix strip model <-> output association. [@tripish]
  • Output Ordering Test Pattern. Light up all hub edges colored by output index. [@tripish]

Output UI

  • Implement Motor Monitor UI. Show current state of desired position for all blooms. Show warnings for pattern designers if motors are overdriven. Turn outputs ON/OFF. [@msclee]
  • Output Options. Show physical ID from data file. Field to change PixLite ID (last 2 of static IP address), toggle ON/OFF output, etc. [@msclee]

Animation Content

  • Port Content. Port pallete of content so collaborators can begin non-programmatic visualization building [@msclee]
Clone this wiki locally