Schneider Electric LUFP9 user manual Configuring the Gateway

Page 44

6. Configuring the Gateway

The upper part of this window allows you to choose a Modbus command, to edit its contents, then to send it to the Modbus network (“Command” menu). The response will then be displayed in this same part. Please see chapter 2.10 Node monitor in the AbcConf user manual, entitled AnyBus Communicator – User Manual, for further information about how to use this window. This manual can be found on the CD LU9CD1 : “ABC_User_Manual.pdf”.

The lower part of this window allows you to view the content of the gateway’s memory, but only the bytes used in queries and responses frames for commands and transactions configured for the selected node. The values of the gateway’s two reserved words (addresses 16#0000-16#0001 and 16#0200-16#0201) are also shown, whichever node is selected.

In the window shown above, the data displayed correspond to the values at the memory locations designated by the “Data” fields in the commands and transactions configured for the “TeSys U no. 1” node, that is to say the following commands: “Read Holding Registers”, “Preset Multiple Registers”, “Transactions 1”, and “Transactions 2”.

N.B. The data exchanged with the Modbus slave previously selected are displayed LSB-first, that is in the LSB / MSB order (as read from left to right, with growing memory addresses), provided that the “Byte Swap” option from the “Data” or “Preset Data” element of the corresponding Modbus command was set to “Swap 2 bytes” (see chapter 6.11.2.5 Configuring the Content of the Response Frame, page 72). For the two reserved words dedicated to the management of the downstream Modbus network, it is the contrary: MSB-first.

However, but only as far as the “TeSys U n°1” node is concerned, the data beginning at addresses 16#0013, 16#0018, 16#0212, and 16#0218 (see chapter 8.2 Content of the Gateway’s DPRAM Memory, page 84) follow the same byte order than the content of the frames they are related to (see Appendix E: Modbus Commands, page 113), from first to last byte (checksum excluded), and following growing adresses in the memory of the gateway. Finally, bytes 16#001E, 16#001F, 16#021E, and 16#021F correspond to the reception and emission counters for these frames (“Trigger bytes” from Transactions 1 and 2). But all these bytes are swapped two by two between the gateway and the DeviceNet master.

A brief description of the toolbar buttons of this window is given below:

Stop / Start communications with the selected node.

Select / Send the Modbus command shown in the upper part of the window

Stop / Resume refreshing the data displayed in the lower part of the window

44

Image 44
Contents LUFP9 Page LUFP9 Page Table of contents Introduction Introduction to the user guideAltistart Introduction to the LUFP9 GatewayTerminology Notational Conventions Additional DocumentationModbus Modbus VW33-A48Downstream network no.3 Modbus Downstream network no.1Principle Used to Configure and Operate the LUFP9 Gateway ABC Configurator Modbus networkLUFP9 gateway RSNetWorxRSLogix DeviceNet NetworkOn Receipt Configuration Modbus RTUHardware Implementation of the LUFP9 Gateway Mounting the gateway Dismounting the gateway Powering the gatewayMounting the Gateway on a DIN Rail Connecting the Gateway to the Modbus Network Examples of Modbus connection topologiesLUFP9 gateway TSXCSA00 Pin outsHubs, drops, taps, and line terminations Wiring recommendations for the Modbus network120 Ω Connecting the LUFP9 gateway to the DeviceNet network Wire colourCables PinConfiguring DeviceNet Communication Features Selector Switches DeviceNet speed 3 4 5 6 7Encoding the Gateway Address Selector DeviceNet Switches Address 3 4 5 6 7Speed Address Mac ID Signalling Software Implementation of the Gateway IntroductionSystem Architecture DeviceNet Master PLC SLC500 DeviceNet upstream networkManaging degraded modes Configuring the Motor StartersModbus cycle time Selecting and adding the master PLC’s DeviceNet scanner Configuring the Gateway in RsNetWorxInstalling the Gateway Description File Selecting and Adding the Gateway to the DeviceNet Network Editing gateway parametersSoftware Implementation of the Gateway Configuring the DeviceNet Scanner Configuring Inputs from the Gateway Service PLC input DescriptionI1.1 I1.2Configuring Outputs Intended for the Gateway Service PLC output DescriptionO1.1 O1.2Input Value Meaning MSB + LSB Description of Services Assigned to Gateway Inputs/OutputsOutput Value Meaning MSB + LSB Transferring the DeviceNet Scanner Configuration Developing a DeviceNet ApplicationGateway Initialization and Diagnostics Full ManagementSummary Control/Status Byte field Sub-chapterBits Description Fbhssend New DeviceNet master command wordFbdu Modbus exchange startup Bits Description Abchssend New gateway diagnostic 11EC Error code associated with the Modbus networkED Error data item 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 PC LUFP9 Configuration Female RJ45 RS-232 link protocol Male RJ45 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 SlaveCopying a previously configured Modbus slave Adding a Modbus SlaveAdding a new type of 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.17 I1.18I1.19 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 Adding and Setting Up a Modbus Command Name of the Modbus command Modbus queryWith TeSys U Motor Starters 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 FrameFrame FieldSize 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 Environment Appendix a Technical CharacteristicsCommunication Characteristics Inputs Input data areaOutputs General dataOutput data area General data areaAppendix B Default Configuration Configuring Modbus exchanges16#10 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 exampleAppendix D DeviceNet Objects Introduction to the Gateway’s DeviceNet ObjectsList of 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#03Assembly Objects Class 16#04 Services of instance 16#01 of class 16#03Services in class 16#04 Revision index of the Assembly Object classServices of instances 16#64 and 16#96 of class 16#04 Connection Object Class 16#05Attributes of instance 16#64 of class 16#04 Modbus Inputs Attributes of instance 16#96 of class 16#04 Modbus OutputsServices in class 16#05 Attributes of class 16#05Initial comm. characteristics Watchdog timeout action16#83 Produced connection IDAccess Name Type Value 16#01 Get State16# 20 04 24 64 30 Type ValueGet / Set Produced connection path Type Value 16#07 Get / Set Produced connection size Type Value 16#04 Get / Set Produced connection ID #0 xxServices in class 16#2B Acknowledge Handler Object class 16#2BAttributes of instances 16#01 to 16#04 of class 16#05 Attributes of class 16#2BData with ack path list Services of instance 16#01 of class 16#2BType Value 16#06 Get Data with ack path list size Services in class 16#A0 Services of instance 16#01 of class 16#A010.10. I/O Data Input Mapping Object Class 16#A0 Attributes of class 16#A0Services in class 16#A1 Services of instance 16#01 of class 16#A110.11. I/O Data Output Mapping Object Class 16#A1 Attributes of class 16#A1Diagnostic Object Class 16#AA Services in class 16#AAAttributes of class 16#AA Attributes of instance 16#01 of class 16#AAAccess Name Need Type Value 16#09 Get LED status Module typeDeviceNet module status Changed data fieldServices of instance 16#01 of class 16#AA Appendix E Modbus Commands Frame Field Value or properties Read Holding Registers Command 16#03Preset Single Register command 16#06 Preset Multiple Registers Command 16#10 Modbus Protocol Exception ResponsesCode Name Description of the exception Exception Page User’s manual V1.0 2003-03