Schneider Electric LUFP9 user manual Configuring the Gateway

Page 59

6. Configuring the Gateway

4)Checking the new memory occupation: If you wish to check how much of the gateway’s memory is now occupied, select “Sub-Network” and choose “Monitor” from the Sub-Network” menu. The following window appears, allowing you to see how much of the gateway’s memory is occupied by Modbus data. The part framed in red represents the memory occupation before the deletion of the two setup commands. It has been inlaid in the illustration below so that you can see the effects of the deletion operations we have just carried out.

You will note that the “TeSys U n°1” section now only has the two Modbus commands common to the eight TeSys U motor starters, and that the memory locations which corresponded to the two personalised commands are now free.

N.B. The free memory location at address 16#0012 in the gateway’s memory is no longer part of the gateway’s inputs, because there is no input data used beyond this address.

5) Transferring this configuration to the gateway Please see chapter 6.4 Transferring a Configuration to the Gateway, page 43. Check that the configuration is valid (LED s DEVICE STATUS flashing green).

6)Saving this configuration to your PC’s hard disk.

7)Checking the gateway setup: In RsNetWorx, check the values of the gateway parameters (see chapter 4.2.4 Editing gateway parameters, page 26). The value of parameter no. 7, “Input1 length”, should have changed, from “32 bytes” to “18 bytes”. The value of parameter no. 19, “Output1 length”, should have changed, from “32 bytes” to “18 bytes”.

8)Changing the amount of data received and the amount of data transmitted by the DeviceNet scanner: Still in RsNetWorx, change the value for the amount of periodic data received and the amount of periodic data transmitted by the DeviceNet scanner (see chapter 4.2.5 Configuring the DeviceNet Scanner, page 28). In the “Polled:” section, change the value of the “Rx Size:” field from 32 to 18 and the value of the “Tx Size:” field from 32 to 18.

9)Configuring the DeviceNet master PLC inputs and outputs: In RsNetWorx, establish a new correspondence between the data from the gateway and the PLC inputs (see chapter 4.2.6 Configuring Inputs from the Gateway, page 29). Do the same for the correspondence between the data transmitted to the gateway and the PLC outputs (see chapter 4.2.7 Configuring Outputs Intended for the Gateway, page 30).

We then get the two correspondences shown on the next page, derived from those used with the gateway’s default configuration.

59

Image 59
Contents LUFP9 Page LUFP9 Page Table of contents Introduction to the user guide IntroductionAltistart Introduction to the LUFP9 GatewayTerminology Additional Documentation Notational ConventionsDownstream network no.1 ModbusModbus VW33-A48 Downstream network no.3 ModbusPrinciple Used to Configure and Operate the LUFP9 Gateway Modbus network ABC ConfiguratorDeviceNet Network LUFP9 gatewayRSNetWorx RSLogixOn Receipt Configuration Modbus RTUHardware Implementation of the LUFP9 Gateway Mounting the gateway Dismounting the gateway Powering the gatewayMounting the Gateway on a DIN Rail Examples of Modbus connection topologies Connecting the Gateway to the Modbus NetworkLUFP9 gateway Pin outs TSXCSA00Hubs, drops, taps, and line terminations Wiring recommendations for the Modbus network120 Ω Pin Connecting the LUFP9 gateway to the DeviceNet networkWire colour CablesSelector Switches DeviceNet speed 3 4 5 6 7 Configuring DeviceNet Communication FeaturesEncoding the Gateway Address Selector DeviceNet Switches Address 3 4 5 6 7Speed Address Mac ID Signalling DeviceNet Master PLC SLC500 DeviceNet upstream network Software Implementation of the GatewayIntroduction System ArchitectureManaging 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 Editing gateway parameters Selecting and Adding the Gateway to the DeviceNet NetworkSoftware Implementation of the Gateway Configuring the DeviceNet Scanner I1.2 Configuring Inputs from the GatewayService PLC input Description I1.1O1.2 Configuring Outputs Intended for the GatewayService PLC output Description O1.1Input Value Meaning MSB + LSB Description of Services Assigned to Gateway Inputs/OutputsOutput Value Meaning MSB + LSB Developing a DeviceNet Application Transferring the DeviceNet Scanner ConfigurationControl/Status Byte field Sub-chapter Gateway Initialization and DiagnosticsFull Management SummaryBits Description Fbhssend New DeviceNet master command wordFbdu Modbus exchange startup Gateway Status Word Bits Description Abchssend New gateway diagnostic11EC Error code associated with the Modbus network ED Error data item associated with the Modbus networkDescription of the error Diagnostic only DeviceNet Master Command Word Simplified Operation Connecting the Gateway to the Configuration PC Configuring the GatewayPC COM Male 9 point SUB-D LUFP9 Configuration Female RJ45RS-232 link protocol Male RJ45Importing the Gateway Configuration Installing AbcConfMonitoring the Content of the Gateway’s Memory Transferring a Configuration to the GatewayConfiguring the Gateway Deleting a Modbus Slave Procedure for deleting a Modbus slaveKeyboard shortcut Ctrl Copying a previously configured Modbus slaveAdding a Modbus Slave Adding a new type of Modbus slaveImporting/exporting a Modbus slave configuration Replacing a Periodic Input Data Element Changing the Periodic Data Exchanged With a Modbus SlaveReplacing an Output Periodic Data Element Increasing the Amount of Periodic Input Data Configuring the Gateway Configuring the Gateway I1.20 I1.17I1.18 I1.19Configuring the Gateway Configuring the Gateway Configuring the Gateway O1.18 O1.17Deleting Aperiodic Parameter Data Configuring the Gateway Changing the Name of a Modbus Slave Changing a Modbus slave ConfigurationChanging the Address of a Modbus Slave Modbus response Adding and Setting Up a Modbus CommandName of the Modbus command Modbus query With TeSys U Motor StartersWith a Generic Modbus Slave Configuring the Gateway DeviceNet Configuration Description Element Configuring the QueryConfiguring the Gateway Default communication mode. The query is transmitted Configuring the Response Field Size Description Frame Configuring the Content of the Query FrameFrame FieldSize Configuring the Content of the Response Frame Mode. The default value, CRC, should not be changedModbus Commands Based on Standard Commands Adding a Special Modbus CommandModbus Commands which Can Be Completely Changed by the User Fieldbus element Configuring the General Characteristics of the GatewayABC Element Sub-Network Element Configuring the Gateway Adding a Broadcaster Node Environment Appendix a Technical CharacteristicsCommunication Characteristics Input data area InputsGeneral data area OutputsGeneral data Output data area16#06 Appendix B Default ConfigurationConfiguring Modbus exchanges 16#10Input Data Memory Area Content of the Gateway’s Dpram Memory16#0200 Main Program LAD 2 MAINLUFP9 Appendix C Practical Example RSLogixScanvalidation Address Symbol DescriptionAddress Symbol Display Cmdreset ModuleAppendix C Practical Example RSLogix Numparam Appendix C Practical Example RSLogix Wrrunning Reserves relating to the RSLogix 500 example Address Symbol DisplayClass Required Instances Interfaces Appendix D DeviceNet ObjectsIntroduction to the Gateway’s DeviceNet Objects List of the Gateway’s DeviceNet ObjectsIdentity Object class 16#01 Graphical Representation of the Gateway’s DeviceNet ObjectsAttributes of instance 16#01 of class 16#01 Services of instance 16#01 of class 16#01DeviceNet Object class 16#03 Message Router Object class 16#02Revision index of the Assembly Object class Assembly Objects Class 16#04Services of instance 16#01 of class 16#03 Services in class 16#04Attributes of instance 16#96 of class 16#04 Modbus Outputs Services of instances 16#64 and 16#96 of class 16#04Connection Object Class 16#05 Attributes of instance 16#64 of class 16#04 Modbus InputsAttributes of class 16#05 Services in class 16#05Produced connection ID Initial comm. characteristicsWatchdog timeout action 16#83Type Value 16#01 Get State Access Name16# 20 04 24 64 30 Type ValueGet / Set Produced connection path Type Value 16#07 Get / Set Produced connection size #0 xx Type Value 16#04 Get / Set Produced connection IDAttributes of class 16#2B Services in class 16#2BAcknowledge Handler Object class 16#2B Attributes of instances 16#01 to 16#04 of class 16#05Data with ack path list Services of instance 16#01 of class 16#2BType Value 16#06 Get Data with ack path list size Attributes of class 16#A0 Services in class 16#A0Services of instance 16#01 of class 16#A0 10.10. I/O Data Input Mapping Object Class 16#A0Attributes of class 16#A1 Services in class 16#A1Services of instance 16#01 of class 16#A1 10.11. I/O Data Output Mapping Object Class 16#A1Attributes of instance 16#01 of class 16#AA Diagnostic Object Class 16#AAServices in class 16#AA Attributes of class 16#AAChanged data field Access Name Need Type Value 16#09 Get LED statusModule type DeviceNet module statusServices 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 Modbus Protocol Exception Responses Preset Multiple Registers Command 16#10Code Name Description of the exception Exception Page User’s manual V1.0 2003-03