Thomas & Betts Limitorque MX Device Net Field Unit Discrete Output Point Object Class ID 9 09hex

Page 33

Limitorque MX DeviceNet Field Unit  FCD LMENIM2328-00 – 11/05

4.4.5Discrete Output Point Object – Class ID 9 (09hex)

The Discrete Output Point Object is used to provide an interface to a subset of the discrete outputs of the MX. The implementation of this object follows the guidelines of [1] Chapter 5‑10.

The Discrete Output Point Object is implemented with 7 instances described in Table 3.1‑29, so that each of the selected discrete outputs of the MX is connected to one instance.

The purpose of this object is to have a SINGLE-BIT access to the relays of the MX via the DeviceNet network for test and diagnostic purposes.

The Discrete Output Point Object is just another representation of the selected discrete output data in the Channel Interface Object Instance Attribute 11 (DO_Relay_Chan) see Chapter 3.2.1.2.

Table 4.39 – Discrete Output Point Object

Instance ID Channel Interface Object

Source

1

Instance Attribute 11, Bit 0

DO_Relay_Chan User

Output AS-1

2

Instance Attribute 11, Bit 1

DO_Relay_Chan User

Output AS-2

 

 

 

 

3

Instance Attribute 11, Bit 2

DO_Relay_Chan User

Output AS-3

 

 

 

 

4

Instance Attribute 11, Bit 3

DO_Relay_Chan User

Output AS-4

 

 

 

 

5

Instance Attribute 11, Bit 4

DO_Relay_Chan User

Output AR-1

 

 

 

 

6

Instance Attribute 11, Bit 5

DO_Relay_Chan User

Output AR-2

 

 

 

 

7

Instance Attribute 11, Bit 6

DO_Relay_Chan User

Output AR-3

 

 

 

 

4.4.6Analog Input Point Object – Class ID 10 (0Ahex)

The Analog Input Point Object is used to provide an interface to a subset of the analog inputs of the MX. The implementation of this object follows the guidelines of [1] Chapter 5‑11.

The Analog Input Point Object is implemented with 2 instances described in Table 3.1‑33, so that each of the selected analog inputs of the MX is connected to one instance.

The purpose of this object is to have a SINGLE access to the generic analog inputs of the MX via the DeviceNet network for test and diagnostic purposes.

The Analog Input Point Object is just another representation of the selected analog input data in the Channel Interface Object Instance Attribute 13 (AI_Analog_Input_1_Chan ) and Attribute 14 (AI_Analog_Input_1_Chan) see Chapter 3.2.1.2.

Table 4.40 – Analog Input Point Object

Instance ID Channel Interface Object

Source

1

2

Instance Attribute 13

AI_ANALOG_INPUT_1_CHAN

Instance Attribute 14

AI_ANALOG_INPUT_2_CHAN

4.4.7Analog Output Point Object – Class ID 11 (0Bhex)

The Analog Output Point Object is used to provide an interface to a subset of the analog outputs of the

MX. The implementation of this object follows the guidelines of [1] Chapter 5‑12.

The Analog Output Point Object is implemented with 1 instance described in Table 3.1‑37, so that each of the selected analog outputs of the MX is connected to one instance.

The purpose of this object is to have a SINGLE access to the generic analog outputs of the MX via the

33

DeviceNet network for test and diagnostic purposes.

The Analog Output Point Object is just another representation of the selected analog output data in the

Channel Interface Object Instance Attribute 19 (AO_Analog_Output_Chan) see Chapter 3.2.1.2.

flowserve.com

Page 32 Page 34
Image 33
Page 32 Page 34
Contents User Instructions Disclaimer Contents EDS File Declaration of DeviceNet Conformance Odva Certification Declaration of Conformity to the DeviceNet SpecificationAbbreviations Purpose How to Use this Manual User SafetyIntroduction DeviceNet System Capabilities and Features General SpecificationsUser Knowledge MX Field Unit Specifications Network specificationsIntroduction System ComponentsHardware Limitorque MXDeviceNet Field Unit DeviceNet Field UnitBelden Cable Specifications Hardware interfaceNetwork Cable Site and Network Cable Preparation Installation and ConfigurationSite Preparation Network Cable PreparationCable Preparation Installation Verification Network Cabling Installation VerificationDnfu Installation Verification Assembly Objects Object Model DiagramOutput Assembly Instance Output Assembly InstancesClass Instance Attribute Data Name Type Input Assembly Instance 11 Input Assembly Instance 10 Input Assembly InstanceDIPositionandBusModeChan DIPositionChan14 Possible values of DIPositionChan DIActuatorAlarmsChan DIActuatorFaults2Chan16 Possible values of DIActuatorFaults1Chan 18 Possible values of DIActuatorFaults2ChanDIDiscUserInputChan 20 Possible values of DIActuatorAlarmsChanDIReadDiscOutputChan DOPositionChanDIAlarms2Chan DIActuatorFaults3ChanDORelayChan CtrlStatusChanChannel Interface Object Bit 7 Bit Reserved Low BatteryName Data Description Type AttributeName Data Type Description Semantics of Value Transducer Block ObjectName Data Type Description Semantics of Value Bit 7 33 Transducer Attribute Scaled values attribute35 Identity Object Instance Attributes Identity Object Instance AttributesBit 15 Bit 10 Description Semantics of Value AttributeBehavior 36 BehaviorEvent Source Description DeviceNet Object Instance Attributes 37 DeviceNet Object Instance AttributesName Data Description Semantics of Value Type Attribute Discrete Input Point Object Class ID 8 08hex 38 Discrete Input Point ObjectInstance ID Channel Interface Object Source Analog Input Point Object Class ID 10 0Ahex Discrete Output Point Object Class ID 9 09hexAnalog Output Point Object Class ID 11 0Bhex 39 Discrete Output Point ObjectMAC ID Network ManagementBaud Rate Offline Connection Set Device Heartbeat MessageDevice Shutdown Message Configuration ConfirmationChecking Connections 43 Format of the Device Shutdown MessageView DeviceNet Status View SettingsChecking the Normal Display Access Path to Object TroubleshootingAssociated Documents EDS FileWorkmanship Regulatory Information How to Order PartsWiring Diagram Limitorque MX DeviceNet Field Unit FCD LMENIM2328-00 11/05 Flowserve.com Flowserve.com
Top Page Image Contents