Schneider Electric LUFP9 Acknowledge Handler Object class 16#2B, Attributes of class 16#2B

Page 106

10. Appendix D: DeviceNet Objects

Attributes of instances 16#01 to 16#04 of class 16#05

Service code

Name of the service

Need

Description

16#0E

Get_Attribute_Single

Required

This service allows to read the value of one of the attributes from

 

 

 

one of the instances of the “Connection Object.”

16#10

Set_Attribute_Single

Optional

This service allows to write the value of one of the attributes from

 

 

 

one of the instances of the “Connection Object.”

10.9. Acknowledge Handler Object (class 16#2B)

The “Acknowledge Handler” object has only one instance (Instance ID = 16#01). This object is used by connections whose producer needs to know whether its data has been received by its recipient(s) (consumers). This object is described in chapter 6-31. of volume II of the DeviceNet specifications.

Attributes of class 16#2B

ID

Access

Name

Need

Type

Value

Description

16#01

Get

Revision

Optional

UINT

1

Revision index of the “Acknowledge Handler Object”

 

 

 

 

 

 

class.

16#02

Get

Max

Optional

UINT

1

Maximum number of any instance created within the

 

 

instance

 

 

 

“Acknowledge Handler Object” class.

Services in class 16#2B

Service code

Name of the service

Need

Description

16#0E

Get_Attribute_Single

Required

This service allows to read the value of one of the attributes of the

 

 

 

class.

Attributes of instance 16#01 of class 16#2B

ID

Access

Name

Need

Type

Value

16#01

Get / Set

Acknowledge timer

Required

UINT

20 (unit: 1ms)

The value of this attribute determines the waiting time for acknowledgement of the message from a connection. Once this time has elapsed, the gateway proceeds to re-transmit the message which has just failed to be acknowledged. The value of this attribute ranges from 1 to 65,535, and its default value is 20.

16#02

Get / Set

Retry limit

Required

USINT

1

This attribute determines the maximum number of times that the acknowledge timeout can be successively triggered for the same message, and therefore the number of re-transmissions allowed for each message. The value of this attribute ranges from 0 to 255, and its default value is 1.

16#03

Get / Set

COS producing connection instance

Required

UINT

4

The value of this attribute is set to the instance number (Instance ID) of the “Connection Object” class corresponding to the “Change-of-State” connection associated with the “Acknowledge Handler” object. This association allows the latter to transmit the acknowledgements it receives to the corresponding connection if they are addressed to it.

16#04

Get

Ack list size

Optional

BYTE

1

This attribute represents the maximum number of members which can be placed in the ack list. If the value of this attribute is null, the size of the list is dynamic, which is not the case with the LUFP9 gateway.

16#05

Get

Ack list

Optional

BYTE , USINT […]

0 , (empty list)

This attribute corresponds to the list of active instances of the “Connection Object” class for which the receipt of an acknowledgement is required. It is made up of two elements: The number of members (BYTE) and the list of the associated instance numbers from the “Connection Object” class (USINT […]). The size of the list is set to the value of the first element. By default, the list is empty (no term of the USINT type […]) and only the BYTE element is created.

E.g. “1, 4“ for a list comprising a single instance of the “Connection Object” class. This instance (16#04) corresponds to the “Change-of-State / Cyclic (Acknowledged) Connection”).

106

Image 106
Contents LUFP9 Page LUFP9 Page Table of contents Introduction Introduction to the user guideTerminology Introduction to the LUFP9 GatewayAltistart Notational Conventions Additional DocumentationDownstream network no.3 Modbus ModbusModbus VW33-A48 Downstream network no.1Principle Used to Configure and Operate the LUFP9 Gateway ABC Configurator Modbus networkRSLogix LUFP9 gatewayRSNetWorx DeviceNet NetworkHardware Implementation of the LUFP9 Gateway Configuration Modbus RTUOn Receipt Mounting the Gateway on a DIN Rail Powering the gatewayMounting the gateway Dismounting the gateway Connecting the Gateway to the Modbus Network Examples of Modbus connection topologiesLUFP9 gateway TSXCSA00 Pin outs120 Ω Wiring recommendations for the Modbus networkHubs, drops, taps, and line terminations Cables Connecting the LUFP9 gateway to the DeviceNet networkWire colour PinConfiguring DeviceNet Communication Features Selector Switches DeviceNet speed 3 4 5 6 7Speed Address Mac ID Selector DeviceNet Switches Address 3 4 5 6 7Encoding the Gateway Address Signalling System Architecture Software Implementation of the GatewayIntroduction DeviceNet Master PLC SLC500 DeviceNet upstream networkModbus cycle time Configuring the Motor StartersManaging degraded modes Installing the Gateway Description File Configuring the Gateway in RsNetWorxSelecting and adding the master PLC’s DeviceNet scanner Selecting and Adding the Gateway to the DeviceNet Network Editing gateway parametersSoftware Implementation of the Gateway Configuring the DeviceNet Scanner I1.1 Configuring Inputs from the GatewayService PLC input Description I1.2O1.1 Configuring Outputs Intended for the GatewayService PLC output Description O1.2Output Value Meaning MSB + LSB Description of Services Assigned to Gateway Inputs/OutputsInput Value Meaning MSB + LSB Transferring the DeviceNet Scanner Configuration Developing a DeviceNet ApplicationSummary Gateway Initialization and DiagnosticsFull Management Control/Status Byte field Sub-chapterFbdu Modbus exchange startup Fbhssend New DeviceNet master command wordBits Description ED Error data item associated with the Modbus network Bits Description Abchssend New gateway diagnostic11EC Error code associated with the Modbus network Gateway Status WordDescription of the error Diagnostic only DeviceNet Master Command Word Simplified Operation Configuring the Gateway Connecting the Gateway to the Configuration PCMale RJ45 LUFP9 Configuration Female RJ45RS-232 link protocol PC COM Male 9 point SUB-DInstalling AbcConf Importing the Gateway ConfigurationTransferring a Configuration to the Gateway Monitoring the Content of the Gateway’s MemoryConfiguring the Gateway Procedure for deleting a Modbus slave Deleting a Modbus SlaveAdding a new type of Modbus slave Copying a previously configured Modbus slaveAdding a Modbus Slave Keyboard shortcut CtrlImporting/exporting a Modbus slave configuration Changing the Periodic Data Exchanged With a Modbus Slave Replacing a Periodic Input Data ElementReplacing an Output Periodic Data Element Increasing the Amount of Periodic Input Data Configuring the Gateway Configuring the Gateway I1.19 I1.17I1.18 I1.20Configuring the Gateway Configuring the Gateway Configuring the Gateway O1.17 O1.18Deleting Aperiodic Parameter Data Configuring the Gateway Changing a Modbus slave Configuration Changing the Name of a Modbus SlaveChanging the Address of a Modbus Slave With TeSys U Motor Starters Adding and Setting Up a Modbus CommandName of the Modbus command Modbus query Modbus responseWith a Generic Modbus Slave Configuring the Gateway DeviceNet Configuring the Query Configuration Description ElementConfiguring the Gateway Default communication mode. The query is transmitted Configuring the Response Configuring the Content of the Query Frame Field Size Description FrameSize FieldFrame Mode. The default value, CRC, should not be changed Configuring the Content of the Response FrameAdding a Special Modbus Command Modbus Commands Based on Standard CommandsModbus Commands which Can Be Completely Changed by the User Configuring the General Characteristics of the Gateway Fieldbus elementABC Element Sub-Network Element Configuring the Gateway Adding a Broadcaster Node Communication Characteristics Appendix a Technical CharacteristicsEnvironment Inputs Input data areaOutput data area OutputsGeneral data General data area16#10 Appendix B Default ConfigurationConfiguring Modbus exchanges 16#06Content of the Gateway’s Dpram Memory Input Data Memory Area16#0200 Appendix C Practical Example RSLogix Main Program LAD 2 MAINLUFP9Address Symbol Description ScanvalidationCmdreset Module Address Symbol DisplayAppendix C Practical Example RSLogix Numparam Appendix C Practical Example RSLogix Wrrunning Address Symbol Display Reserves relating to the RSLogix 500 exampleList of the Gateway’s DeviceNet Objects Appendix D DeviceNet ObjectsIntroduction to the Gateway’s DeviceNet Objects Class Required Instances InterfacesGraphical Representation of the Gateway’s DeviceNet Objects Identity Object class 16#01Services of instance 16#01 of class 16#01 Attributes of instance 16#01 of class 16#01Message Router Object class 16#02 DeviceNet Object class 16#03Services in class 16#04 Assembly Objects Class 16#04Services of instance 16#01 of class 16#03 Revision index of the Assembly Object classAttributes of instance 16#64 of class 16#04 Modbus Inputs Services of instances 16#64 and 16#96 of class 16#04Connection Object Class 16#05 Attributes of instance 16#96 of class 16#04 Modbus OutputsServices in class 16#05 Attributes of class 16#0516#83 Initial comm. characteristicsWatchdog timeout action Produced connection IDAccess Name Type Value 16#01 Get StateGet / Set Produced connection path Type Value16# 20 04 24 64 30 Type Value 16#07 Get / Set Produced connection size Type Value 16#04 Get / Set Produced connection ID #0 xxAttributes of instances 16#01 to 16#04 of class 16#05 Services in class 16#2BAcknowledge Handler Object class 16#2B Attributes of class 16#2BType Value 16#06 Get Data with ack path list size Services of instance 16#01 of class 16#2BData with ack path list 10.10. I/O Data Input Mapping Object Class 16#A0 Services in class 16#A0Services of instance 16#01 of class 16#A0 Attributes of class 16#A010.11. I/O Data Output Mapping Object Class 16#A1 Services in class 16#A1Services of instance 16#01 of class 16#A1 Attributes of class 16#A1Attributes of class 16#AA Diagnostic Object Class 16#AAServices in class 16#AA Attributes of instance 16#01 of class 16#AADeviceNet module status Access Name Need Type Value 16#09 Get LED statusModule type Changed data fieldServices of instance 16#01 of class 16#AA Appendix E Modbus Commands Preset Single Register command 16#06 Read Holding Registers Command 16#03Frame Field Value or properties Preset Multiple Registers Command 16#10 Modbus Protocol Exception ResponsesCode Name Description of the exception Exception Page User’s manual V1.0 2003-03