Device Driver

A device driver is required to control a device by Chromeleon. Each controllable instrument or integrated system has its own device driver that is activated when Chromeleon is started. The device driver translates the instructions (commands) into device-specific digital commands that are then converted into "real control commands" after the data has been transferred to the instrument. In the opposite direction, the signals of all instruments (readings, status information, etc.) are converted so that Chromeleon can read them and display them on the screen.

Device drivers are also capable of monitoring regularly requested or automatically given device parameters in a target/actual value comparison. Unexpected events can be corrected or displayed in an error message. We can only guarantee for Dionex devices that the device driver fully supports all instrument functions. Support of third-party devices may be limited. If you can change the settings to modify the functionality of the driver (for example, if you can specify the shared A/D channels, relays, or remote inputs), this action is performed in the Server Configuration Program

The names of the device drivers are derived from the corresponding instruments.

If a separate device driver is not available for your instrument, special drivers often allow at least partial control of a device. (For more information, refer to Configuring the Chromeleon Server  Controlling Devices without a Separate Device Driver in the Administrator Help section.) In special cases, you can use the generic device driver to create a user-defined device driver. (For more information, refer to Hardware Installation  The Generic Device Driver in the Administrator Help section.)