axumaircast:start
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| axumaircast:start [2019/07/19 16:37] – support | axumaircast:start [2022/07/18 09:19] (current) – support | ||
|---|---|---|---|
| Line 19: | Line 19: | ||
| \\ | \\ | ||
| {{ : | {{ : | ||
| + | \\ | ||
| + | This node can be renamed to Aircast.\\ | ||
| \\ | \\ | ||
| {{ : | {{ : | ||
| + | \\ | ||
| + | When you go to __Surface configuration__ you'll find the Aircast node.\\ | ||
| \\ | \\ | ||
| {{ : | {{ : | ||
| + | \\ | ||
| + | When you press the __configure__ button you'll see the empty function list for this node.\\ | ||
| \\ | \\ | ||
| {{ : | {{ : | ||
| + | \\ | ||
| + | Now you can configure the Actuators that will trigger the 16 virtual busses that will go to Aircast.\\ | ||
| + | \\ | ||
| + | So when you for example configure __Module x: Fader on__ the Axum will send a trigger to Aircast when that fader is going from off to on.\\ | ||
| \\ | \\ | ||
| {{ : | {{ : | ||
| + | \\ | ||
| + | Now at the Aircast __Control Panel__ in the __D&R Axum (Mambanet)__ at the __Commands__ tab you can configure for each Actuator what the function needs to be when the Axum sends it's trigger.\\ | ||
| + | \\ | ||
| \\ | \\ | ||
| {{ : | {{ : | ||
| \\ | \\ | ||
| + | Multiple functions can be configured this way.\\ | ||
| + | \\ | ||
| + | [[https:// | ||
| + | \\ | ||
| + | [[start: | ||
| + | \\ | ||
axumaircast/start.1563547073.txt.gz · Last modified: 2019/07/19 16:37 (external edit)