Table 74 defines the structure of an MDISMotorObjectType. Any vendor specified properties that have been implemented within a project should be documented with a similar format and supplied to the DCS vendor. The addition of vendor specific properties will result in a subtype of the MDISMotorObjectType. When an MDISMotorObjectType Instance is disabled the MDISBaseObjectType defaults are followed - no additional values will be available.
Table 74 – MDISMotorObjectType
|
Attribute |
Value |
|||||
|
BrowseName |
MDISMotorObjectType |
|||||
|
IsAbstract |
False |
|||||
|
References |
Node Class |
BrowseName |
DataType |
TypeDefinition |
Other |
|
|
Subtype of the MDISBaseObjectType |
|
|||||
|
0:HasComponent |
Variable |
Running |
0:Boolean |
0:BaseDataVariableType |
M, RO |
|
|
0:HasComponent |
Variable |
Operation |
MotorOperationEnum |
0:BaseDataVariableType |
M, RO |
|
|
0:HasComponent |
Variable |
NonDefeatableStartInterlock |
0:Boolean |
0:BaseDataVariableType |
O, RO |
|
|
0:HasComponent |
Variable |
DefeatableStartInterlock |
0:Boolean |
0:BaseDataVariableType |
O, RO |
|
|
0:HasComponent |
Variable |
NonDefeatableStopInterlock |
0:Boolean |
0:BaseDataVariableType |
O, RO |
|
|
0:HasComponent |
Variable |
DefeatableStopInterlock |
0:Boolean |
0:BaseDataVariableType |
O, RO |
|
|
HasInterlock |
Variable |
<InterlockPlaceholder> |
0:Boolean |
InterlockVariableType |
OP, RO |
|
|
0:HasComponent |
Method |
Start |
See 6.11.4 |
O |
||
|
0:HasComponent |
Method |
Stop |
See 6.11.5 |
O |
||
|
0:HasComponent |
Method |
SetOperation |
See 6.11.6 |
O |
||
|
ConformanceUnits |
||||||
|
MDIS Motor Base |
||||||
Running – Feedback from the motor if it is running (or not). If the motor is running it returns True.
Operation – There are three different operation modes: Auto, Manual and Off. In Auto operation the process sends the Start and Stop command automatically (not from an Operator). In Manual operation the Start and Stop process is executed by the operator manually (e.g. by using the Start and Stop methods). When the operation mode is set to Off, the motor may not be started either automatically or manually. If Manual Operation is supported, then the Start and Stop Methods shall be exposed.
NonDefeatableStartInterlock – The Start command is interlocked and cannot be overridden.
DefeatableStartInterlock – The Start command is interlocked and can be overridden.
NonDefeatableStopInterlock – The Stop command is interlocked and cannot be overridden.
DefeatableStopInterlock – The Stop command is interlocked and can be overridden.
<InterlockPlaceholder > – The number of interlock Variables will change based on the project and even Motor instance. The Variables shall be of InterlockVariableType or a subtype of it. They shall be referenced by a HasInterlock Reference and shall contain an InterlockFor Reference. Clients can use this information to categorise the interlocks appropriately.
The MDISMotorObjectType is a subtype of MDISBaseObjectType and inherit the FaultCode Variable. The MDISMotorObjectType defines the standard FaultCodes (for bits 0-15 as defined in 6.2.2) in Table 75 (currently empty, no additional warning codes defined). All subtypes of this the MDISMotorObjectType will inherit all FaultCodes defined in this table. Subtypes may define additional FaultCodes in their own table.
Table 75 – MDISMotorObjectType FaultCode Values
|
Value |
Bit no. |
Description |
|
|
|
|
The MDISMotorObjectType defines the standard WarningCodes (for bits 0-15 as defined in 6.2.2) in Table 76 (currently empty, no additional warning codes defined). All subtypes of this the MDISMotorObjectType will inherit all WarningCodes defined in this table. Subtypes may define additional WarningCodes in their own table.
Table 76 – MDISMotorObjectType WarningCode Values
|
Value |
Bit no. |
Description |
|
|
|
|