Schneider Electric LUFP9 user manual Configuring the Gateway

Page 55

6. Configuring the Gateway

3)Changing the location of the Modbus data transmitted into the gateway’s memory: As the number of bytes written (see previous step) has increased from 2 to 4, the Modbus data to be transmitted to the “TeSys U n°4” motor starter must be placed at a different location in the gateway’s memory, and the size of the memory occupied must also be adjusted appropriately.

If you are not certain how much of the gateway’s memory is currently occupied, select “Sub-Network” and choose “Monitor” from the Sub-Network” menu. The window shown below appears, allowing you to see how much of the gateway’s memory is occupied.

To see which memory locations are occupied by data from the command you are interested in, all you have to do is uncheck the box corresponding to the “Preset Multiple Registers” command from the “TeSys U n°4” node, as shown above. We can see that the Modbus data transmitted with the query corresponding to this command occupy 2 bytes located from address 16#0208.

Memory locations 16#0200 and 16#0201 are reserved (see chapter 5 Gateway Initialization and Diagnostics, page 33). So you will not be able to place any Modbus data in these locations.

The sizes displayed above the graphics areas of this window (“In Area 32 bytes” and “Out Area 32 bytes”) correspond to the total input and ouput sizes you must check under RsNetWorx (see point 6) on next page) and configure for the DeviceNet scanner (see point 7) ).

If you wish to place the 4 bytes of Modbus data which will be transmitted by the gateway for this command into memory, once the changes have been made, we will have to move all the other output data by 2 bytes, which may be tedious, or change the memory location of the block of data transmitted. In the example described here, we will be using the second solution, although the first solution is actually preferable, in principle, as it avoids leaving any “holes” in the gateway’s memory, thus optimising the transfer of all of the data from the DeviceNet master PLC. Furthermore, the 1747-SDN scanner can only exchange 32 output words with the master PLC. Leaving “holes” of this sort in the gateway’s memory is therefore not recommended in cases of large configurations.

We will place the 4 bytes of data from address 16#0220 (544 in decimal). N.B. As far as possible, place the data at even addresses in order to align the Modbus data (in 16-bit format) on the O:1.x outputs of the 1747- SDN DeviceNet scanner.

Close the “Sub-network Monitor” window, then once you are back in the main AbcConf window, select the “Data length” and “Data location” fields of the “Data” element from the “Query” one after another and change their values as shown at the top of the next page. AbcConf will automatically convert any value entered in decimal to hexadecimal.

55

Image 55
Contents LUFP9 Page LUFP9 Page Table of contents Introduction to the user guide IntroductionTerminology Introduction to the LUFP9 GatewayAltistart 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 RSLogixHardware Implementation of the LUFP9 Gateway Configuration Modbus RTUOn Receipt Mounting the Gateway on a DIN Rail Powering the gatewayMounting the gateway Dismounting the gateway Examples of Modbus connection topologies Connecting the Gateway to the Modbus NetworkLUFP9 gateway Pin outs TSXCSA00120 Ω Wiring recommendations for the Modbus networkHubs, drops, taps, and line terminations Pin Connecting the LUFP9 gateway to the DeviceNet networkWire colour CablesSelector Switches DeviceNet speed 3 4 5 6 7 Configuring DeviceNet Communication FeaturesSpeed Address Mac ID Selector DeviceNet Switches Address 3 4 5 6 7Encoding the Gateway Address Signalling DeviceNet Master PLC SLC500 DeviceNet upstream network Software Implementation of the GatewayIntroduction System ArchitectureModbus 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 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.1Output Value Meaning MSB + LSB Description of Services Assigned to Gateway Inputs/OutputsInput Value Meaning MSB + LSB Developing a DeviceNet Application Transferring the DeviceNet Scanner ConfigurationControl/Status Byte field Sub-chapter Gateway Initialization and DiagnosticsFull Management SummaryFbdu Modbus exchange startup Fbhssend New DeviceNet master command wordBits Description 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 FrameSize FieldFrame 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 Communication Characteristics Appendix a Technical CharacteristicsEnvironment 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 NameGet / Set Produced connection path Type Value16# 20 04 24 64 30 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#05Type Value 16#06 Get Data with ack path list size Services of instance 16#01 of class 16#2BData with ack path list 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 Preset Single Register command 16#06 Read Holding Registers Command 16#03Frame Field Value or properties Modbus Protocol Exception Responses Preset Multiple Registers Command 16#10Code Name Description of the exception Exception Page User’s manual V1.0 2003-03