Schneider Electric LUFP9 Read Holding Registers Command 16#03, Frame Field Value or properties

Page 114

11. Appendix E: Modbus Commands

Chapter 6.11 Adding and Setting Up a Modbus Command, page 62, also shows a few examples of correspondences between the elements displayed in AbcConf and the corresponding Modbus frame fields.

See also: Chapter 6.11.2 With a Generic Modbus Slave, page 63, and chapter 6.11.3 Adding a Special Modbus Command, page 73, if the implementation of one of these commands would be incompatible with its implementation in the gateway, for example. You then have to create a special Modbus command to compensate for this incompatibility.

N.B. here, the notions of “input” and “output” (and assimilated) are irrelevant, as all Modbus commands have access to all of a Modbus slave’s memory. However, these names are retained in order to comply with the terms used in the standard Modbus documentation.

11.1. “Read Holding Registers” Command (16#03)

Frame

Field

Value or properties

Query

Starting Address (MSB)

- Address of the 1st output / internal register

Starting Address (LSB)

 

 

 

Number of points (MSB)

- Number of output / internal registers

 

Number of points (LSB)

 

 

Response

Byte count

- Number of data bytes = number of output / internal registers × 2

 

Data (first register / MSB)

- Byte swap = “Swap 2 bytes” (or “No swapping”)

 

Data (first register / LSB)

 

- Data length = Value of the “Byte count” field

 

………

 

Data (last register / MSB)

- Data location = Address in the gateway’s input memory

 

Data (last register / LSB)

 

 

11.2. “Preset Single Register” command (16#06)

Frame

Field

Value or properties

Query

Register (MSB)

- Address of the output / internal register

 

Register (LSB)

 

 

 

Preset data (MSB)

- Byte swap = “Swap 2 bytes” (or “No swapping”)

 

 

- Data length = 16#0002

 

Preset data (LSB)

 

- Data location = Address in the gateway’s output memory

Response

Register (MSB)

- Byte swap = “Swap 2 bytes” (or “No swapping”)

 

 

- Data length = 16#0002

 

Register (LSB)

 

- Data location = Address in the gateway’s input memory

 

Preset data (MSB)

 

N.B. This data is an echo to the query. So in most cases there is no need

 

Preset data (LSB)

 

to feed them back to the DeviceNet master.

Instead of creating a link between the echo of the response to the “Preset Single Register” command (16#06) and the memory area dedicated to the DeviceNet inputs (16#0002- 16#01FF), you’d better link it with the address 16#0400.

114

Image 114
Contents LUFP9 Page LUFP9 Page Table of contents Introduction Introduction to the user guideIntroduction to the LUFP9 Gateway TerminologyAltistart 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 NetworkConfiguration Modbus RTU Hardware Implementation of the LUFP9 GatewayOn Receipt Powering the gateway Mounting the Gateway on a DIN RailMounting the gateway Dismounting the gateway Connecting the Gateway to the Modbus Network Examples of Modbus connection topologiesLUFP9 gateway TSXCSA00 Pin outsWiring recommendations for the Modbus network 120 ΩHubs, 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 7Selector DeviceNet Switches Address 3 4 5 6 7 Speed Address Mac IDEncoding the Gateway Address Signalling System Architecture Software Implementation of the GatewayIntroduction DeviceNet Master PLC SLC500 DeviceNet upstream networkConfiguring the Motor Starters Modbus cycle timeManaging degraded modes Configuring the Gateway in RsNetWorx Installing the Gateway Description FileSelecting 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.2Description of Services Assigned to Gateway Inputs/Outputs Output Value Meaning MSB + LSBInput Value Meaning MSB + LSB Transferring the DeviceNet Scanner Configuration Developing a DeviceNet ApplicationSummary Gateway Initialization and DiagnosticsFull Management Control/Status Byte field Sub-chapterFbhssend New DeviceNet master command word Fbdu Modbus exchange startupBits 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 FrameField SizeFrame 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 Appendix a Technical Characteristics Communication 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 StateType Value Get / Set Produced connection path16# 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#2BServices of instance 16#01 of class 16#2B Type Value 16#06 Get Data with ack path list sizeData 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#AA DeviceNet module status Access Name Need Type Value 16#09 Get LED status Module type Changed data fieldServices of instance 16#01 of class 16#AA Appendix E Modbus Commands Read Holding Registers Command 16#03 Preset Single Register command 16#06Frame 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