🎉That's great news! I'll check it out this weekend. Thanks Tim!

from thorium-hardware.

Use Cases

1. Flight director wants to control the lights for a mission

• Flight director starts the server and all the clients
• Flight director Controls the lights based on mission specific events using controls in the Core

2. Flight director is doing maintenance in the simulator room

• Flight director starts the computer that controls the lights (= has a USB connection to the DMX / LED controller)
• Flight director uses the lighting client to turn on / off all the lights

3. Client computer should be able to run in headless mode

• Same steps as in 1.

Ressources

• https://github.com/Thorium-Sim/thorium-node-client
• https://github.com/Thorium-Sim/thorium-react-client

from thorium-hardware.

Those use cases look good to me

from thorium-hardware.

Possibly have an arduino connected to the network and the DMX universe to control the lighting system.
http://playground.arduino.cc/Learning/DMX

from thorium-hardware.

Solutions for the Use Cases

1. Flight director wants to control the lights for a mission

• Create a lighting client in Node
• Lighting client connects to the Thorium-Server and waits for messages
• Lighting client connects to luminave and sends the messages from Thorium-Server to luminave
• luminave has the actual connection to the DMX & LED lights

2. Flight director is doing maintenance in the simulator room

• luminave has to be started on the computer that controls the lights
• Flight director is using luminave to turn on / off the lights

3. Client computer should be able to run in headless mode

• Same as 1. but luminave also has to work in headless mode (either by providing a Node implementation or by making sure that the browser is started automatically on the client, but it's just not used)

from thorium-hardware.

V1

I suggest the following architecture as V1 to move forward and see how this will play out in the Magellan simulator at the CMSC:

Concept for CMSC

• luminave frontend manages the DMX fixtures by sending the universe to the luminave-fivetwelve module
• luminave-fivetwelve is using the DMX512 Controller directly over USB (in this case a enttec DMX USB Pro)
• The DMX fixtures inside the simulator are attached to the DMX Controller
• luminave backend should provide a GraphQL API
• luminave-thorium will consume the Thorium backend GraphQL API to tell luminave which lights should be activated and which scene/animation should be used

Both the luminave backend and the luminave-thorium modules are not created yet, everything else exists.

Out of the box

The other parts of this diagram are part of what luminave frontend already supports out of the box and might be useful in the future:

• WebUSB DMX512 Controller to create an Arduino based DMX Controller that can be used over WebUSB directly in the browser to control one DMX512 universe
• WebUSB NeoPixel Controller to create an Arduino based NeoPixel Controller that can be used over WebUSB directly in the browser to control any kind of NeoPixels
• You can attach any MIDI controller to mange scenes & animations

Disclaimer

I'm the creator of luminave.

from thorium-hardware.

I'm done with creating everything to use lighting inside of Thorium to control lights using luminave. I have written a documentation on how to use it. Feedback is super welcome.

from thorium-hardware.