Device Driver is a special type of plugin that defines how AggreGate Server interacts with a certain type of hardware devices. The driver is specified during creation of a Device account.
|
Tibbo regularly creates new AggreGate Server device drivers for different types of hardware devices and protocols. Please, check AggreGate website for the most recent list of available device drivers. |
|
See Device Server Plugins for the list of drivers processing Device Server data streams. |
|
See Driver Development Kit for details on creating new drivers. |
Driver Reference
The subsections of current section are devoted to different device drivers that are bundled with AggreGate core and diverse vertical market solutions.
Description of every driver includes the following:
Section |
Notes |
Driver Information |
Driver details, such as driver plugin ID, etc. |
Global Settings |
Global configuration of driver plugin. |
User-level Settings |
User-level configuration of driver plugin. |
Device Properties |
Device-level configuration of driver plugin. This includes connection settings, manually configured definitions of device resources, etc. |
Device Assets |
Description of method used by the driver to define device assets. |
Device Settings |
Description of method used by the driver to create variables corresponding to the hardware device's settings. |
Device Operations |
Description of method used by the driver to create functions/actions corresponding to the hardware device's operations. |
Device Events |
Description of method used by the driver to create event definitions corresponding to the types of events provided by hardware device. This sections also illustrates how and when are the event instances received from the hardware and converted into AggreGate events. |
Connection Handling |
Details on how and when the driver switches the device between Online and Offline status. |
Synchronization Details |
Any information on the driver-specific peculiarities of Device synchronization process. |
Every driver has up to three levels of settings:
| • | Global Settings. These affect the default behaviour of drivers. Global settings may be edited only by users with sufficient permissions. |
| • | User-level Settings. These affect the behaviour of a driver only if it is assigned to a Device that belongs to a certain user account. When the driver is communicating with a certain Device, it uses the user-level settings stored in the Device owner's account. |
| • | Device-level Settings (Device Properties). These settings define how the device driver connects to the Device, communicates with it, and processes Device data. |
Many drivers do not use all three setting levels.
Administering Device Drivers
Two context types are used to administer Device Drivers: first is the general Drivers/Plugins Configuration context, which serves as a container. The other is the Driver/Plugin Configuration context, which holds the configuration for a single driver. These appear in two places:
If a given driver doesn't contain settings on one of these levels, the corresponding Device Driver Configuration context will not be created (i.e, won't exist in the System Tree). Device Level settings for a driver may be accessed using the Edit Device Properties action of a Device context. |
|
