<- tb8:surround_configuration|Surround Configuration (5.1) ^ tb8:start|Toolbox8 Software ^ tb8:authorisation_overview|Authorisation Overview -> {{tag>ember_plus ember+ external_control IP}} ====== Ember+ Configuration ====== The Ember+ protocol is available in the DHD Firmware. The implementation was realised as controlled device – the so-called Ember+ provider. The following functions are currently featured: * Receiving 50 GPIs per mixing console via Ember+. * Sending 50 GPOs per mixing console via Ember+. * receiving and sending global labels, for example to change labels of DHD fader channels or send text messages to a TFT screen. * Controlling fader levels. * [[tb8:emberplus#ember_plus_audio_routing_in_dhd_devices|Audio Routing]]. /* FIXME Beim Routing I/O Namen ändern inclusive? - lt. Daniel soll das wohl erstmal nicht möglich sein.*/ [{{ :tb8:emberplus.png?nolink |//Ember+ Device in I/O Device window//}}] To add an Ember+ Device in TB8, go to ''/I/O Overview page''. Click ''Add'' and select ''52-7999 Ember GPI/GPO Connect''. [{{ :tb8:embergpi7999.png?nolink |//Virtual Ember+ I/O Device//}}] You have now 50 GPIs and 50 GPOs and also control data for all assigned fader channels available to work with. **Note**\\ The GPO node in the Ember+ tree is filtered. Only GPOs with a configured logic source are listed. The data transmission is realised via TCP/IP. The DHD system has to be connected by suitable network technology with the controlling system – the Ember+-Consumer – in order to allow this TCP/IP data transmission. **Note**\\ The Ember+ data are received and sent directly by the controller of the DSP Core for each mixing console. An interfacing PC is not necessary. /* This also means that the Ember+ interface is not being implemented via the DHD Operation Server. */ **Note**\\ The Ember+ implementation has been tested with the Ember+ Viewer and with VSM (Virtual Studio Manager). **Note**\\ Ember+ runs on Port 9000 on all DHD devices. === Ember+ Audio Routing in DHD Devices === DHD devices provide the possibility to perform I/O routings within the DSP cores via Ember+. The Routing option is provided as ''Routing'' node in Ember+. To enable this option, simply add the ''52-7999 Ember GPI/GPO Connect'' in your ''/I/O Overview page''. The routing matrix visible in the Ember+-tree will include only physical inputs and physical outputs. For routing other signals available on the TDM bus, the Ember+ implementation of the DHDOS/DHDOM needs to be used. There you can create individual routing matrices with much more I/O options. **Important**\\ The I/O routing via Ember+ is available only for 52/XC2, 52/XS2, 52/XD2 cores (52-7420, 52-7423, 52-7410, 52-1810, 52-1830, 52-7456) == Ember+ Provider for DHDOS 52-8573 == Ember+ functionality is also provided in DHDOS/DHDOM, for example to set crosspoints in routing matrices created with the DHD Routing Software. See [[os:start|DHDOS Documentation]] and [[om:start|DHDOM Documentation]] for more information.