Page 3 - Gateway DeviceNet / Modbus RTU
Page 5 - Table of contents; Hardware Implementation of the LUFP9
5 Table of contents 1. Introduction............................................................6 1.1. Introduction to the user guide................................................. 61.2. Introduction to the LUFP9 Gateway ....................................... 71.3. Terminology........................
Page 7 - OUTPUTS; DeviceNet master
7 1. Introduction 1.2. Introduction to the LUFP9 Gateway The LUFP9 gateway allows a master located on a DeviceNet network to enter into a dialogue with the slaves ona Modbus RTU network. This is a generic protocol converter operating in a way which is transparent to the user. This gateway allows you...
Page 9 - Introduction to the Communication “System” Architecture; DeviceNet; Downstream
9 1. Introduction 1.6. Introduction to the Communication “System” Architecture Upstream network (DeviceNet) ATS48 VW33-A48 ATS46 VW3-G46301 DeviceNet Master Downstream network no.1 (Modbus) Downstream network no.3 (Modbus) Downstream network no.2 (Modbus) Total of 16 motor starters (TeSys U model)
Page 10 - Principle Used to Configure and Operate the LUFP9 Gateway; The gateway is part of a family of products (referred to as LUFP
10 1. Introduction Each LUFP9 DeviceNet / Modbus RTU gateway allows a PLC on the DeviceNet network to command, controland configure up to 8 Modbus slaves. If there are more than 8 Modbus slaves, you will need to use anappropriate number of LUFP9 gateways. In the same way, if the exchanges with the M...
Page 11 - ABC Configurator
11 1. Introduction Ö Each LUFP9 gateway is shipped pre-configured so as to make it easier to operate and the factory settingscan be used as a basis for a configuration which will best meet the user’s expectations. The typicaloperations applicable to this default configuration are described in chapte...
Page 12 - LUFP9 gateway; Size of the input DeviceNet data
12 1. Introduction — Managing Gateway ↔ DeviceNet master exchanges — LUFP9 gateway 0x0000 0x01FF Input Modbus data : Management of exchanges with the DeviceNet master Free memory locations :::: : 0x0200 0x03FF Output Modbus Data Free memory locations :::: RSNetWorx Configuration of DeviceNet exchang...
Page 13 - Hardware Implementation of the LUFP9 Gateway; One LUFP9 DeviceNet / Modbus RTU gateway.
13 2. Hardware Implementation of the LUFP9 Gateway 2.1. On Receipt After opening the packaging, check that the following element is there: • One LUFP9 DeviceNet / Modbus RTU gateway. 2.2. Introduction to the LUFP9 Gateway The cables and other accessories for connecting to DeviceNet and Modbus networ...
Page 14 - Mounting the gateway; The spring is also used to earth the gateway (Protective Earth).; on the
14 2. Hardware Implementation of the LUFP9 Gateway 2.3. Mounting the Gateway on a DIN Rail Mounting the gateway 1 2 Dismounting the gateway 1 2 Start by fitting the rear base of the gateway to theupper part of the rail, pushing downwards (1) tocompress the gateway’s spring. Then push thegateway agai...
Page 15 - Connecting the Gateway to the Modbus Network; The connections are shown below:; Towards 8 Modbus slaves; Line
15 2. Hardware Implementation of the LUFP9 Gateway 2.5. Connecting the Gateway to the Modbus Network Three typical examples of Modbus connection for the gateway and its slaves are shown below. There are manyother possible Modbus connections, but they are not covered in this document. 2.5.1. Examples...
Page 16 - “Bus” topology with VW3 A8 306 TF3 drop boxes:; This topology uses VW3 A8 306 TF3 drop boxes to; Towards 3 Modbus slaves
16 2. Hardware Implementation of the LUFP9 Gateway • “Bus” topology with VW3 A8 306 TF3 drop boxes: This topology uses VW3 A8 306 TF3 drop boxes to connect each of the Modbus slaves to the main section of the Modbus network. Each box should be placed inthe immediate vicinity of the Modbus slave it i...
Page 17 - “Bus” topology with tap boxes:; This topology is similar to the previous one, except that it uses
17 2. Hardware Implementation of the LUFP9 Gateway • “Bus” topology with tap boxes: This topology is similar to the previous one, except that it uses TSXSCA62 subscriber connectors and/or TSXCA50 subscriber connectors. We recommend using aVW3 A68 306 connection cable and the TSXCSA•00 Modbus cables....
Page 18 - • Use a shielded cable with 2 pairs of twisted conductors,
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 met...
Page 19 - Connecting the LUFP9 gateway to the DeviceNet network; and it should be; DeviceNet cable; Pin; Pinouts; Gateway
19 2. Hardware Implementation of the LUFP9 Gateway 2) Cables: VW3 A8 306 R•• Modbus cable ...................................(“star” topology / “bus” topology with tap boxes) Shielded cable with a male RJ45 connector at eachend. VW3 A68 306 Modbus cable........................................(“b...
Page 20 - Configuring DeviceNet Communication Features; Selector; 0 x x x x x x; ON; Speed; 1 x x x x x x
20 2. Hardware Implementation of the LUFP9 Gateway 2.7. Configuring DeviceNet Communication Features This configuration should be carried out when the gateway is powered off. The block of selector switches allowing you to configure the DeviceNet communication functions is hiddenbehind the gateway co...
Page 22 - telm; The length of this timeout is; If the; LED
22 3. Signalling The gateway’s 6 LEDs and the descriptive label on the removable cover which hides its block of selectorswitches allow you to diagnose the status of the gateway: c e g d f h telm LUFP9 n o p q r s 1 N ETWORK S TATUS 2 M ODULE S TATUS 3 N OT U SED 4 N OT U SED 5 M ODBUS 6 GA TEWAY Dev...
Page 23 - Software Implementation of the Gateway; Allen
23 4. Software Implementation of the Gateway 4.1. Introduction This chapter gives an introduction to a quick implementation of the LUFP9 gateway, using its defaultconfiguration. All LUFP9 gateways ship pre-configured. This pre-configuration means that the user does not have to configure the LUFP9 ga...
Page 25 - Configuring the Gateway in RsNetWorx; Selecting and adding the master PLC’s DeviceNet scanner; This file can be found on the CD LUF9CD1 : “
25 4. Software Implementation of the Gateway 4.2. Configuring the Gateway in RsNetWorx The DeviceNet master PLC must be configured so that it has access to all of the data described inchapters 8.2.1 Input Data Memory Area, page 84 et 8.2.2 Output Data Memory Area, page 85. The following chapters des...
Page 26 - Selecting and Adding the Gateway to the DeviceNet Network
26 4. Software Implementation of the Gateway 4.2.3. Selecting and Adding the Gateway to the DeviceNet Network Select “LUFP9” from the list on the left, then add it to the DeviceNet network topology. In our example, we have assigned the Mac ID address 04 to the gateway (the configuration of the addre...
Page 27 - Schneider Electric
27 4. Software Implementation of the Gateway If you are in any doubt over what is displayed, click on the “Upload From Device” button, then on “Start Monitor”. TheRsNetWorx application then starts to read from the gateway the values of the parameters currently displayed.Click on the “Stop Monitor” b...
Page 28 - or
28 4. Software Implementation of the Gateway 4.2.5. Configuring the DeviceNet Scanner Double-click on the icon which corresponds to the DeviceNet scanner. A window then appears allowing you to configure the exchanges carried out by the scanner. Select the “Scanlist”tab and add the “LUFP9” gateway to...
Page 29 - Description
29 4. Software Implementation of the Gateway 4.2.6. Configuring Inputs from the Gateway On the “Input” tab, select the “LUFP9” gateway, then click on the “AutoMap” button. RsNetWorx thenautomatically establishes the correspondence between the 32 data bytes (8-bit format) from the gateway and thecorr...
Page 31 - Managing the downstream Modbus network:; Please see chapter 5.2 Diagnostic only, page 37, for a detailed; Aperiodic communications:
31 4. Software Implementation of the Gateway 4.2.8. Description of Services Assigned to Gateway Inputs/Outputs Managing the downstream Modbus network: Please see chapter 5.2 Diagnostic only, page 37, for a detailed description of this service. The example described in chapter 9.1 Main Program: “LAD ...
Page 32 - The DeviceNet master PLC used as an example is a SLC500, marketed by
32 4. Software Implementation of the Gateway 4.2.9. Transferring the DeviceNet Scanner Configuration Once you have finished the operations described above, make sure that the changes made have beentransmitted to the DeviceNet scanner. To do this, click on the “Download to Scanner…” button on each of...
Page 33 - Gateway Initialization and Diagnostics; Bits; The gateway’s status word contains a diagnostic
33 5. Gateway Initialization and Diagnostics Each of the three sub-chapters 5.1, 5.2 and 5.3 describes the principle used to initialize and carry outdiagnostics on the gateway using each of the three options offered by the gateway. These options can beconfigured via AbcConf, by changing the assignme...
Page 34 - The DeviceNet master command word still; It is possible to simplify this use as follows:; do not write directly in 16-bit format; in the DeviceNet master command word, because this
34 5. Gateway Initialization and Diagnostics Bits Description 14 FB_HS_SEND: New command from the DeviceNet master Before changing the value of FB_DU, the DeviceNet master must compare the values ofFB_HS_SEND and ABC_HS_CONFIRM (bit 14 of the gateway’s status word). If these two values aredifferent,...
Page 35 - been updated at least once since the last activation of FB_DU (“ABC_DU”
35 5. Gateway Initialization and Diagnostics 5.1.2. Gateway Status Word The input word located at addresses 16#0000 (MSB) and 16#0001 (LSB) in the gateway’s input memoryconstitutes the gateway’s status word. Its structure is described below: Bits Description 15 ABC_HS_SEND: New gateway diagnostic (S...
Page 36 - EC
36 5. Gateway Initialization and Diagnostics The correct use of this status word by the DeviceNet master, to read a diagnostic generated by the gateway,goes through the following steps: • Checking of (ABC_HS_SEND ≠ FB_HS_CONFIRM). • Reading of the value of ABC_DU to determine whether all of the Modb...
Page 40 - Configuring the Gateway; Connecting the Gateway to the Configuration PC; PowerSuite; Straight POWERSUITE cable; Configuration; Male; PC; converter
40 6. Configuring the Gateway Each part of this chapter describes a separate step allowing the user to personalize the gateway configuration,according to his own particular needs. Each part gives an introduction to a basic operation isolating it from therest of the configuration and describing the o...
Page 42 - AnyBus Communicator – User Manual
42 6. Configuring the Gateway 6.2. Installing AbcConf The minimum system requirements for AbcConf are as follows: • Processor........................................Pentium 133 MHz• Free hard disk space ......................10 Mb• RAM ................................................ 0 8 Mb • Operat...
Page 43 - Transferring a Configuration to the Gateway; During this; Monitoring the Content of the Gateway’s Memory
43 6. Configuring the Gateway 6.4. Transferring a Configuration to the Gateway When using AbcConf, you can transfer the configuration you are editing to the gateway at any time. Choose “Download configuration to ABC-LUFP” from the “File” menu or click on the button, in the AbcConf toolbar. AbcConf i...
Page 44 - all these bytes
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 tothe Modbus network (“Command” menu). The response will then be displayed in this same part. Please seechapter 2.10 Node monitor in the AbcConf user manual, entit...
Page 45 - never delete the first configured TeSys U motor starter; Del
45 6. Configuring the Gateway 6.6. Deleting a Modbus Slave This step allows you, for instance, to free up a location on the downstream Modbus network, known as the “Sub-Network” in AbcConf, in order to replace one Modbus slave with another. In fact the gateway’s default configuration already allows ...
Page 46 - Adding a new type of Modbus slave:; Use one of the two methods shown below:; Copying a previously configured Modbus slave:; Ctrl C; Then use one of the two methods shown below:; Ctrl V
46 6. Configuring the Gateway However, these operations are not necessary when deleting a single slave. Conversely, they become almostessential when most of the Modbus slaves are deleted, because these deletions divide up the gateway’smemory. Please see chapter 6.11 Adding and Setting Up a Modbus Co...
Page 47 - Importing/exporting a Modbus slave configuration:
47 6. Configuring the Gateway Importing/exporting a Modbus slave configuration: AbcConf offers the possibility of independently saving and loading the configuration of a node on thedownstream “Sub-Network”. For instance, this will allow you to build a library of Modbus slave templates, so thatyou ca...
Page 48 - Changing the Periodic Data Exchanged With a Modbus Slave; st default register.” This word corresponds to the PLC input
48 6. Configuring the Gateway 6.8. Changing the Periodic Data Exchanged With a Modbus Slave This operation consists of replacing, adding or deleting periodic data exchanged with one of the Modbus slaves.With each of these operations, we shall take the default configuration of the LUFP9 gateway as an...
Page 49 - Do the same for the; because the gateway checks the value of this field when it
49 6. Configuring the Gateway 6.8.2. Replacing an Output Periodic Data Element E.g. “TeSys U n°6” motor starter. We are trying to replace the control of the “Command Register” (address 704 =16#02C0) with the control of the “2nd Command Register” (address 705 = 16#02C1). The operation consists of cha...
Page 52 - Gateway, page 43. Check that the configuration is valid (LED; ) Saving this configuration to your PC’s hard disk.
52 6. Configuring the Gateway To check that these changes have been entered into the configuration, choose “Monitor” from the “Sub-Network” menu again: In point 6), you shall make sure the values of the displayed parameters are the same as theexchange sizes displayed in the “Sub-network Monitor.” In...
Page 54 - Do the same for the “Starting Address” element of the “Response”; because the gateway
54 6. Configuring the Gateway 1) Changing the number of registers controlled: This step consists of changing the value of the “No. of Registers” in the “Query” and in the “Response” for the “Preset Multiple Registers” command (Modbuscommand for writing values of a number of registers). Start by sele...
Page 55 - As far as possible, place the
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...
Page 58 - with the “
58 6. Configuring the Gateway 6.9. Deleting Aperiodic Parameter Data If your PLC application does not need the aperiodic service for reading/writing parameter data on Modbusslaves, you can delete the associated commands. If you also intend to add Modbus data, and therefore use newlocations in the ga...
Page 59 - ) Saving this configuration to your PC’s hard disk.
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 windowappears, allowing you to see how much of the gateway’s memory is occu...
Page 60 - Changing a Modbus slave Configuration; Enter
60 6. Configuring the Gateway Description Service PLC input Bit 0 ..................... Bit 7 Bit 8 .................... Bit 15 LUFP9 gateway status word Managing the downstream Modbus network I:1.1 (MSB Æ 16#xx••) (LSB Æ 16#••xx) I:1.2 Value of the motor starter c status register I:1.3 Value of the...
Page 62 - Adding and Setting Up a Modbus Command; ”. Then continue using one; highlighted in blue; Name of the Modbus command
62 6. Configuring the Gateway 6.11. Adding and Setting Up a Modbus Command 6.11.1. With TeSys U Motor Starters With TeSys U motor starters, the main use of adding a Modbus command consists of allowing you to control ormonitor additional registers, without having to change the elements in the default...
Page 63 - We strongly advise you
63 6. Configuring the Gateway Name of the Modbus command Modbus query ! Frame " Slave no.Function no.No. of the 1st word (MSB / LSB)Number of words (MSB / LSB)CRC16 (LSB / MSB) Modbus response ! Frame " Slave no.Function no.Number of bytes read…Values of the words (MSB/LSB)…CRC16 (LSB / MSB)...
Page 65 - slaves. In the case of drives marketed by
65 6. Configuring the Gateway 6.11.2.1. Managing Degraded Modes Due to the number of hardware elements and software tools used, the following table shows a summary of thevarious degraded modes in a DeviceNet application. In this case, this application includes an LUFP9 gateway,but we will not be inc...
Page 66 - This element affects the data
66 6. Configuring the Gateway 6.11.2.2. Configuring the Query Select the “Query” element from the Modbus command. Thevarious elements of the configuration of the query for this commandare shown opposite. The values displayed correspond to thedefault values for any new command. These elements allow y...
Page 67 - Retries; becomes red. This LED will only revert to a green state
67 6. Configuring the Gateway Configurationelement Description Retries This element indicates the number of re-transmissions carried out by the gateway if there isno response from the Modbus slave to a query, or if the response is incorrect. This re-transmission process ceases as soon as the gateway...
Page 69 - Trigger byte; event driven; unitary incrementation
69 6. Configuring the Gateway 6.11.2.3. Configuring the Response Next select the “Response” element from the Modbus command.The various elements of the configuration of the response for thiscommand are shown opposite. The values displayed correspond tothe default values for any new command. These el...
Page 70 - Size in the; This field is common to queries for all Modbus commands.
70 6. Configuring the Gateway 6.11.2.4. Configuring the Content of the Query Frame The window shown below is obtained using “Edit Frame” from the “Query” menu. Unlike the tree structure in themain AbcConf window, this display has the advantage of showing all of the frame’s fields at the same time as...
Page 72 - Checksum; The value of this field should therefore remain set to zero.; Edit the values which are not greyed out, one after another.
72 6. Configuring the Gateway Field in theframe Size in the frame Description Checksum 2 bytes Error check type: Type of error check for the frame. - CRC.....................Default method. This is the method adopted for the Modbus RTU protocol. - LRC .....................This method relates to the ...
Page 74 - AnyBus Communicator – User; not; objects
74 6. Configuring the Gateway Please see chapter 2.12 Command editor in the AbcConf user manual, entitled AnyBus Communicator – User Manual , for further information about creating standard Modbus commands. This manual can be found on the CD LU9CD1 : “ ABC_User_Manual.pdf ”. 6.11.3.2. Modbus Command...
Page 75 - Configuring the General Characteristics of the Gateway
75 6. Configuring the Gateway The LUFP9 gateway’s default configuration includes two “Transaction” commands. These are aperiodiccommands used for reading and writing the value of a Modbus slave parameter (necessarily a TeSys U motorstarter with the default configuration). They are configured solely ...
Page 76 - types of gateway marketed by
76 6. Configuring the Gateway The only command accessible from the “Fieldbus”menu is “About Fieldbus…”. In “on-line” mode (see chapter 6.12.2 “ABC” Element,page 76), the window shown opposite will be displayed. In “off-line” mode the word “Unknown” willreplace “DeviceNet” to show that the type of up...
Page 77 - downstream of the gateway is a serial link.
77 6. Configuring the Gateway Apart from the “Control/Status Byte” and “Module Reset” options, the configuration of the LUFP9 gateway’s“ABC” element should not be changed. Out of the four options shown below, the last two should therefore retainthe values shown: “Serial” and “Master Mode”. These fou...
Page 79 - all; - The value of the query frame’s “Slave Address” field is set to 16#00.
79 6. Configuring the Gateway 6.13. Adding a Broadcaster Node A broadcaster node does not correspond to any Modbus slave in particular, as it applies to all Modbus slaves. All the commands which will be configured for this node will be transmitted with the “Slave Address” field set to16#00. This mea...
Page 81 - Inputs
81 7. Appendix A: Technical Characteristics Specific DeviceNetfeatures of the LUFP9gateway • The LUFP9 gateway is a “group two only server” DeviceNet subscriber (cf. DeviceNet Specifications ). • Fragmentation support for transactions requiring more than 8 bytes of data.• Connections supported: 1 “E...
Page 82 - always use 16{#4000 as the starting address
82 7. Appendix A: Technical Characteristics Structure of theLUFP9 gateway’s memory: Outputs • 2 bytes for the activation or inhibition of the downstream network by the gateway (see chapter 5 Gateway Initialization and Diagnostics, page 33). • 510 bytes accessible by the DeviceNet master in the form ...
Page 84 - Content of the Gateway’s DPRAM Memory; Service
84 8. Appendix B: Default Configuration 8.2. Content of the Gateway’s DPRAM Memory The LUFP9 gateway’s DPRAM memory contains all of the data exchanged between the gateway and the8 TeSys U motor starters, as well as two special registers only exchanged between the gateway and theDeviceNet master (wor...
Page 85 - The total number of Modbus queries and responses is equal to 36
85 8. Appendix B: Default Configuration 8.2.2. Output Data Memory Area The gateway has 512 output bytes. Only the first 32 bytes are used. All of these 32 bytes make up thegateway’s output area, referenced as “Output 1” in the RsNetWorx configurator. Service Address Size Description Managing the dow...
Page 87 - ditto
87 9. Appendix C: Practical Example (RSLogix 500) The various data used by the main program are shown in the following table: Address Symbol Description I:1.1/ 0 7 → I:1/23 ABC_HS_SEND Flip flop indicating that there is a new gateway diagnostic O:1.0/ 0 0 → O:1/ 0 0 SCAN_VALIDATION Enable DeviceNet ...
Page 93 - Reserves relating to the RSLogix 500 example
93 9. Appendix C: Practical Example (RSLogix 500) Address Symbol Description S:24 INDEX_SYS Index register used in indexed addressing (prefix: ‘#’) T4:1 TIMEOUT_WR_PARAM Timer for the timeout of the parameter writing command(3 seconds) The example includes a personalized screen for monitoring the da...
Page 94 - Introduction to the Gateway’s DeviceNet Objects; Object Modelling; Path; List of the Gateway’s DeviceNet Objects; Class
94 10. Appendix D: DeviceNet Objects 10.1. Introduction to the Gateway’s DeviceNet Objects The LUFP9 gateway’s software has been developed in accordance with the Object Modelling from the DeviceNet protocol. This model leads to a method used for addressing the gateway’s data, known as Attributes , m...
Page 95 - Graphical Representation of the Gateway’s DeviceNet Objects; LUFP9 gateway memory
95 10. Appendix D: DeviceNet Objects 10.3. Graphical Representation of the Gateway’s DeviceNet Objects Connection Object Message Router DeviceNet Object Identity Object Assembly Objects Acknowledge Handler Object Diagnostic Object I/O Data OutputMapping Object I/O Data Input Mapping Object LUFP9 gat...
Page 99 - Explicit Messages; Instance ID
99 10. Appendix D: DeviceNet Objects Attributes of instance 16#64 of class 16#04 (M ODBUS I NPUTS ) ID Access Name Need Type Value 16#03 Get Data Required USINT […] (array of values) The data gathered within this attribute correspond to the data of the attribute 16#01 of instance 16#01 from the“I/O ...
Page 100 - Attributes of instance 16#01 of class 16#05: Explicit Connection
100 10. Appendix D: DeviceNet Objects The “Change-of-State / Cyclic Connection” connection (Instance ID 16#04) allows the gateway to produce itsdata only when their values change or when a timer called “heartbeat rate” times out. A minimum time limit isintended to prevent the connection from monopol...
Page 112 - Services of instance 16#01 of class 16#AA
112 10. Appendix D: DeviceNet Objects ID Access Name Need Type Value 16#11 Get IN total length Optional UINT 16#0020 This attribute indicates the total size of the input data used in the gateway’s extended memory ( IN bytes supported ), expressed as a number of bytes. This size is equal to the value...
Page 113 - Modicon Modbus; Elements under AbcConf
113 11. Appendix E: Modbus Commands Function code Broadcast (1) Modbus command 0 3 16#03 — Read Holding Registers 0 6 16#06 Yes Preset Single Register Only the Modbus commands shown inthe right-hand table are supported bythe gateway. The structure of the queryand response frames for each of thesecom...
Page 115 - Modbus Protocol Exception Responses
115 11. Appendix E: Modbus Commands 11.3. “Preset Multiple Registers” Command (16#10) Frame Field Value or properties Query Starting Address (MSB)Starting Address (LSB) - Address of the 1st output / internal register Number of Registers (MSB)Number of Registers (LSB) - Number of output / internal re...
Page 118 - User’s manual