Schneider Electric user manual Principle Used to Configure and Operate the LUFP9 Gateway

Page 10

1. Introduction

Each LUFP9 DeviceNet / Modbus RTU gateway allows a PLC on the DeviceNet network to command, control and configure up to 8 Modbus slaves. If there are more than 8 Modbus slaves, you will need to use an appropriate number of LUFP9 gateways. In the same way, if the exchanges with the Modbus slaves require more than 25 Modbus commands (that is to say more than 50 queries and responses), you will have to distribute the Modbus slaves over several gateways.

The LUFP9 gateway behaves both as a DeviceNet slave on the upstream network and as a Modbus RTU master on the downstream network.

See chapter 7.2 Communication Characteristics, page 80, if you would like to read about the technical communication characteristics of the LUFP9 gateway.

The gateway can carry out its data exchanges (inputs and outputs of all types) with the Modbus slaves cyclically, aperiodically or in an event-driven way. All of these Modbus exchanges make up the gateway’s “Modbus scanner” and we use the “ABC-LUFP Configurator” software application to configure this scanner’s exchanges. Each item of data exchanged in this way is made available to the DeviceNet master, which can gain access to it in a number of ways (cyclical, aperiodic or event-driven exchanges).

N.B. If, for example, a communication is periodic on the Modbus network, the corresponding data does not have to be exchanged periodically on the DeviceNet network and vice versa.

The diagram on the page to the left illustrates the distribution of several slaves over three downstream Modbus RTU networks, each of these networks being interfaced with the DeviceNet master PLC using an LUFP9 gateway.

1.7. Principle Used to Configure and Operate the LUFP9 Gateway

The gateway is part of a family of products (referred to as LUFPz) designed to meet generic needs for connection between two networks using different communication protocols.

The software elements common to all these gateways (a configuration tool known as “ABC-LUFP Configurator” and the on-board Modbus software) cohabit with the specific features of the network upstream of each of them (DeviceNet in the case of the LUFP9 gateway) generically. This is one of the reasons why the interfacing between the upstream network and the Modbus network is carried out entirely via the gateway’s physical memory.

ÖThe exchanges between the gateway (which operates as a Modbus master) and the Modbus slaves are wholly configured using the “ABC-LUFP Configurator”. This configuration tool goes into great detail (setting timers for exchanges, communication modes, frame content, etc.), which makes it all the more delicate to use. So a whole chapter in this guide (chapter 6 Configuring the Gateway, page 40) has been devoted to this tool.

By configuring the queries and responses for Modbus commands via this tool the user can create links between a part of the content of the corresponding Modbus frames and the content of the gateway’s physical memory (input memory for the content of the Modbus responses and output memory for the content of the queries).

ÖThe exchanges between the DeviceNet master PLC and the LUFP9 gateway should be configured in such a way that the DeviceNet master can read the input data and write the output data from the gateway, but only the data used for the Modbus exchanges (see previous point).

10

Page 9 Page 11
Image 10
Page 9 Page 11
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
Top Page Image Contents