DriverPropertyFlags (GVL)ΒΆ

InOut:

Scope

Name

Type

Initial

Comment

Constant

DRVPROP_CONSISTENCY

DWORD

16#1

IO-driver realizes bit-consistency by its own (atomar bit access). If this flag is 0, the bit-consistency is provided by the IO-Manager.

DRVPROP_WATCHDOG

DWORD

16#2

The io driver needs a cyclic call TO the IoDrvWatchdogTrigger INTERFACE FUNCTION. The io manager will call the io driver approximately every Watchdogtime/2. The Watchdogtime must be set in the IoConfig parameters (ID 0x70000001). ATTENTION: The io manager will pass a NULL pointer as parameter pConnector to the IIoDrv interface function IoDrvWatchdogTrigger. If this flag is 0, the driver must trigger the watchdog itself.

DRVPROP_REDUNDANCY

DWORD

16#4

IO-driver can support redundancy. If the flag DRVPROP_REDUNDANCY is 1, the redundancy is provided by the IO-Manager.

DRVPROP_ACTIVE

DWORD

16#8

If the flag DRVPROP_ACTIVE is 1, the master is active otherwise passive.

DRVPROP_ERROR_ACTIVE

DWORD

16#10

The flag DRVPROP_ERROR_ACTIVE is used to tell the redundancy component that the active master has an error and it should switchover (only on active plc).

DRVPROP_ERROR_PASSIVE

DWORD

16#20

The flag DRVPROP_ERROR_PASSIVE can be set to inform redundancy component that the communication was lost.

DRVPROP_BACKGROUND_GETDIAG

DWORD

16#40

If this property is set, the interface function IoDrvGetModuleDiagnosis() of the driver is called cyclically from a background task. NOTE: In this case, IoDrvGetModuleDiagnosis is called with: IoDrvGetModuleDiagnosis(hIoDrv, NULL); This must be handled correctly in the IO-driver!

DRVPROP_NO_SYNC

DWORD

16#80

Disable synchronization for ReadInputs/WriteOutputs/StartBusCycle in the I/O Manager (CmpIoMgr). In this case the I/O driver has to implement the synchronization of these functions itself. CmpIoMgr provides the following functions that can be used by the I/O driver for synchronization: IoMgrLockEnter(), IoMgrLockLeave()