Schneider Electric LUFP9 user manual Field, Size, Frame

Page 71

6. Configuring the Gateway

Field in the

Size in the

Description

frame

frame

 

Preset Data

2 bytes

Data Location: Address, in the gateway’s output data memory (16#0202 to

 

or more for a

16#03FF), of the item of data to be transmitted in the “Preset Data” field for the

 

block of data

query’s frame.

 

 

N.B. The “Data location” field is used for each frame that allows you to

 

 

exchange some data between the Modbus slaves and the DeviceNet master.

 

 

In this case it designates the starting address of the block of data to be

 

 

transmitted.

 

 

N.B. As far as possible, ensure that the data is located at even addresses in

 

 

order to align the Modbus data (in 16-bit format) on the O:1.x outputs of the

 

 

DeviceNet scanner.

 

 

E.g. The value to be assigned to the ATS48’s CMD register should be placed

 

 

in the gateway’s output data memory area. We will be using the first free

 

 

location starting at an even address, that is to say the one located at 16#0220,

 

 

with the gateway’s default configuration.

 

 

 

 

 

Data length: Length of the block of output data, in the gateway’s memory,

 

 

whose values must be transmitted in the “Preset Data” field of the query’s

 

 

frame. It is expressed in number of bytes.

 

 

N.B. The “Data length” field is always used together with the “Data location”

 

 

field, described above.

 

 

E.g. Since the “Preset Single Register” command is used to write the value of a

 

 

single register (16-bit), the value of the “Data length” field must be set to 2.

 

 

See the documentation for each Modbus slave to find out the maximum

 

 

amount of 8-bit data which can be placed in “Data” type fields in queries and

 

 

responses for this slave. With the ATS48, for instance, it is limited to 30 16-bit

 

 

words.

 

 

Byte swap: Specifies whether the output data bytes to be transmitted to the

 

 

Modbus slave must be swapped before being placed in the Modbus frame or

 

 

not. The three possible values are as follows:

-No swapping ....... Default configuration. The data is sent in the same order as they appear in the gateway’s memory.

-Swap 2 bytes ...... The bytes to be transmitted are swapped two by two. This is the case which must be used by default, because for an item of 16-bit data, the most significant byte is placed first in the Modbus frame, whereas it is always written into the gateway’s memory by a DeviceNet master with the least significant byte first.

-Swap 4 bytes ...... The bytes to be transmitted are swapped four by four. This is rarely used, as it only relates to 32-bit data. The principle is similar to that of the previous case, “Swap 2 bytes”.

E.g. We will be using the “Swap 2 bytes” value, because the two bytes of the value to be written into the ATS48’s CMD register, as transmitted by the SLC500 PLC, are placed into the gateway’s memory in least significant / most significant order.

71

Image 71
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