hardware
ARES System Manual: hardware Daemon
(input)
(input)
(input)
(input)
The ARES hardware daemon serves as the primary point of contact for light bus devices. A device is any attachment or rezzed object designed to interface with ARES using one of these protocols.
Note: The device utility is recommended as an interface for the hardware daemon.
The equivalent of the
Light Bus Devices
The majority of devices designed to interface with ARES and Companion do so primarily or exclusively via the light bus, which originated as a control system for lighting attachments.
Devices using the light bus can access a wide range of information about the unit, including its name and color settings. However, a device must register with the device manager before it can modify anything.
Unregistered devices are not displayed in the interface, and the system may not be aware of their presence. Consequently they are also known as 'passive' devices, whereas devices that use registration are considered 'active' devices.
Certain devices originally designed for Companion depend on messages that trigger internal functions of that operating system. These devices cannot be understood by ARES and must be updated by the manufacturer.
Documentation on the light bus protocol is available at http://develop.nanite-systems.com/light_bus or in the ARES SDK.
(input)
@service hardware probe: probes for connected light bus devices
(input)
@service hardware debug [off|on|toggle]: displays incoming messages in the console
(input)
@service hardware restart: restarts the hardware manager
(input)
@service hardware <address> [<action>]: sends a message to the indicated address
The ARES hardware daemon serves as the primary point of contact for light bus devices. A device is any attachment or rezzed object designed to interface with ARES using one of these protocols.
Note: The device utility is recommended as an interface for the hardware daemon.
The equivalent of the
hardware daemon in Companion was called puppet.
Light Bus Devices
The majority of devices designed to interface with ARES and Companion do so primarily or exclusively via the light bus, which originated as a control system for lighting attachments.
Devices using the light bus can access a wide range of information about the unit, including its name and color settings. However, a device must register with the device manager before it can modify anything.
Unregistered devices are not displayed in the interface, and the system may not be aware of their presence. Consequently they are also known as 'passive' devices, whereas devices that use registration are considered 'active' devices.
Certain devices originally designed for Companion depend on messages that trigger internal functions of that operating system. These devices cannot be understood by ARES and must be updated by the manufacturer.
Documentation on the light bus protocol is available at http://develop.nanite-systems.com/light_bus or in the ARES SDK.