Driver objects |
DNP332 -> Creating variables -> Driver objects and datatypes -> Driver objects |
Show all Hide all |
The following object types are available in this driver:
Driver object type |
Channel type |
Read / Write |
Supported data types |
Comment |
---|---|---|---|---|
Analog inputs |
68 |
L |
REAL |
|
Analog Output Statuses |
69 |
L / S |
UDINT, DINT, REAL, UINT, INT |
|
Binary inputs |
64 |
L |
BOOL |
|
Binary Inputs Double |
71 |
L |
USINT |
|
Binary Output Statuses |
65 |
L / S |
BOOL, USINT |
|
Frozen Counters |
67 |
L / S |
BOOL, UDINT, DINT, USINT, UINT, INT, SINT |
|
Running Counters |
66 |
L / S |
BOOL, UDINT, DINT, USINT, UINT, INT, SINT |
|
String Data |
70 |
L / S |
STRING |
|
Driver variable |
35 |
L / S |
BOOL, SINT, USINT, INT, UINT, DINT, UDINT, REAL, STRING |
Variables for the statistical analysis of communication. Find out more in the chapter about the Driver variables |
Commands
By way of Command input
, you can first send a
Select and then an Operate to data points. The SBO timeout can be
configured in the driver configuration. After sending a Select, a
counter starts running. After the configured SBO timeout has
passed, a COT_actterm with a set PN bit will be sent back. If the
Select action is cancelled, a COT_deact will be sent back to notify
you of this. After the SBO timeout has passed, a COT_deactcon will
be sent. If you send an Operate within the timeout, the procedure
will stay as usual.