Communication Driver-Device interface log flags

Messages created for the following log flags are specific to an individual Communication Driver and contain information about communications between the Communication Driver and device.

DASProtFail

An error in the protocol occurred, for example, device disconnected. The program can continue, and, in fact, this category is expected during normal operation of the program. Must be set on by the generic DAS code when the Communication Driver starts.

DASProtWarn

Something unexpected occurred in the protocol, for example, a requested item with an otherwise valid item name is not supported by this device. Must be set on by the generic DAS code when the Communication Driver starts.

DASTrace

General diagnostic messages of a protocol-specific nature. For example, you can provide the number of items in a message for a specific protocol, then optimize based on the number.

DASVerbose

Modifies all other DAS logging flags. When on, provides detailed messages.

DASSend

Protocol messages sent to the device are logged to this category.

DASReceive

Protocol messages received from the device are logged to this category.

DASStateCat1, DASStateCat2, DASStateCat3, DASStateCat4

These are general categories for use by the server developer. As DeviceEngine-generated state machines are created by the Communication Driver, they can be told to log state machine messages to one of the following: DASStateCat1, DASStateCat2, DASStateCat3, or DASStateCat4. These messages indicate when a state is made the active state, when a state handler is run, when a state handler completes, and when a timeout occurs for a state machine.

DASStateMachine

By default, DeviceEngine-generated state machines created by the Communication Driver log to this category unless specifically told to log to one of the DASStateCatN categories. In addition, general state machine messages are logged to this category. These messages indicate when a state machine is created and deleted.