Bureaucrats, dave_user, Administrators
4,650
edits
Changes
no edit summary
Basically, the product is a dual-role device: it can operate either as a '''controller''' or as a '''recorder'''.
When working as a controller, it feeds slave devices (stage lighting dimmers, special effects machines, etc.) with DMX streams. DMX data can be generated programmatically on the fly or can be retrieved from previously recorded streams.
When working as a recorder, the product "sniffs" and stores DMX data traffic traveling on the connected buses. Each DMX frame is stored onto a permanent storage device — an e.MMC or a microSD card, for instance — with an '''associated timestamp'''. Thus, the data streams can be played at a later time with the '''same timings of the original ones'''.
As shown in the block diagram, the product features a rich set of I/O's ranging from the [https://en.wikipedia.org/wiki/DMX512 DMX/RDM] channels to network interfaces. With regard to the Graphical User Interface, two displays are supported: an HDMI monitor and a local LVDS display. It is worth remembering that they can work simultaneously, for example in mirror mode.
* NXP EdgeLock SE050
* Microchip ATECC608A.
The first one is part of the [[ORCA SOM|Orca SoM]], while the second is optionally populated at the carrier board level. These components allow to implement several schemes to address security-related issues. From the software perspective, they are supported by the Linux BSP so that the user space applications can access them through high-level API's. The Linux BSP is derived from the release L5.4.70 by NXP.