Schneider Electric LUFP9 user manual Wiring recommendations for the Modbus network, 120 Ω

Page 18

2. Hardware Implementation of the LUFP9 Gateway

2.5.3.Wiring recommendations for the Modbus network

• Use a shielded cable with 2 pairs of twisted conductors,

• connect the reference potentials to one another,

• maximum length of line: 1,000 metres

• maximum length of drop line / tap-off: 20 metres

• do not connect more than 9 stations to a bus (slaves and one LUFP9 gateway),

•cable routing: keep the bus away from power cables (at least 30 cm), make crossings at right angles if necessary, and connect the cable shielding to the earth on each unit,

•adapt the line at both ends using a line terminator (see diagram and VW3 A8 306 RC termination below).

D(B) 4

120 Ω

D(A) 5

1 nF

— Line termination recommended at both ends of the line —

— VW3 A8 306 RC line termination —

To make it easier to connect the units using the topologies described in chapter 2.5.1 Examples of Modbus connection topologies, page 15, various accessories are available in the Schneider Electric catalogue:

1) Hubs, drops, taps, and line terminations:

… LU9GC03 hub

This passive box has 8 female RJ45 connectors. Each of these connectors can

(“star” topology)

be connected to a Modbus slave, to a Modbus master, to another Modbus hub,

 

or to a line termination.

… VW3 A8 306 TF3 drop box

This passive box includes a short lead with a male RJ45 connector

(“bus” topology with VW3 A8 306 TF3

allowing it to be

connected directly

to a Modbus slave,

without

drop boxes)

having to use a

different cable. It

is fitted with

2 female RJ45

 

connectors for the connection of

two Modbus

cables

of the

 

VW3 A8 306 R•• type.

 

 

 

…2-way TSXSCA62 subscriber connector . This passive box has a printed circuit fitted with screw terminals

(“bus” topology with branch boxes)

and allows the connection of 2 subscribers to the bus (2 female

 

15 point SUB-D connectors). It includes the line termination when

 

the connector is located at the end. It is fitted with 2 screw terminals

 

for the connection of two double twisted pair Modbus cables.

… TSXCA50 tap box

This passive box allows a Modbus unit to be connected to a screw

(“bus” topology with tap boxes)

terminal. It includes the line termination when the connector is

 

located at the end. It is fitted with 2 screw terminals for the

 

connection of two double twisted pair Modbus cables.

… VW3 A8 306 RC double termination

Each of these two red passive boxes is a male RJ45 connector

(all topologies)

3 cm long containing an RC line termination (see diagram and

 

illustration above). Only the abbreviation “RC” is shown on these

 

boxes.

18

Page 17 Page 19
Image 18
Page 17 Page 19
Contents LUFP9 Page LUFP9 Page Table of contents Introduction Introduction to the user guideIntroduction to the LUFP9 Gateway TerminologyAltistart 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 NetworkConfiguration Modbus RTU Hardware Implementation of the LUFP9 GatewayOn Receipt Powering the gateway Mounting the Gateway on a DIN RailMounting the gateway Dismounting the gateway Connecting the Gateway to the Modbus Network Examples of Modbus connection topologiesLUFP9 gateway TSXCSA00 Pin outsWiring recommendations for the Modbus network 120 ΩHubs, 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 7Selector DeviceNet Switches Address 3 4 5 6 7 Speed Address Mac IDEncoding the Gateway Address Signalling System Architecture Software Implementation of the GatewayIntroduction DeviceNet Master PLC SLC500 DeviceNet upstream networkConfiguring the Motor Starters Modbus cycle timeManaging degraded modes Configuring the Gateway in RsNetWorx Installing the Gateway Description FileSelecting 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.2Description of Services Assigned to Gateway Inputs/Outputs Output Value Meaning MSB + LSBInput Value Meaning MSB + LSB Transferring the DeviceNet Scanner Configuration Developing a DeviceNet ApplicationSummary Gateway Initialization and DiagnosticsFull Management Control/Status Byte field Sub-chapterFbhssend New DeviceNet master command word Fbdu Modbus exchange startupBits 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 FrameField SizeFrame 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 Appendix a Technical Characteristics Communication 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 StateType Value Get / Set Produced connection path16# 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#2BServices of instance 16#01 of class 16#2B Type Value 16#06 Get Data with ack path list sizeData 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 Read Holding Registers Command 16#03 Preset Single Register command 16#06Frame 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