Go to page of
Similar user manuals
-
Switch
Schneider Electric KVM0116A
46 pages 1.65 mb -
Switch
Schneider Electric KVM0108A
46 pages 1.65 mb -
Switch
Schneider Electric 100BASE-FX
6 pages 0.11 mb -
Switch
Schneider Electric KVM1116P
134 pages 6.19 mb -
Switch
Schneider Electric AP561x
26 pages 0.4 mb -
Switch
Schneider Electric 100BASE-TX
6 pages 0.11 mb -
Switch
Schneider Electric LUFP7
115 pages 3.99 mb -
Switch
Schneider Electric KVM2116P
134 pages 6.19 mb
A good user manual
The rules should oblige the seller to give the purchaser an operating instrucion of Schneider Electric LUFP7, along with an item. The lack of an instruction or false information given to customer shall constitute grounds to apply for a complaint because of nonconformity of goods with the contract. In accordance with the law, a customer can receive an instruction in non-paper form; lately graphic and electronic forms of the manuals, as well as instructional videos have been majorly used. A necessary precondition for this is the unmistakable, legible character of an instruction.
What is an instruction?
The term originates from the Latin word „instructio”, which means organizing. Therefore, in an instruction of Schneider Electric LUFP7 one could find a process description. An instruction's purpose is to teach, to ease the start-up and an item's use or performance of certain activities. An instruction is a compilation of information about an item/a service, it is a clue.
Unfortunately, only a few customers devote their time to read an instruction of Schneider Electric LUFP7. A good user manual introduces us to a number of additional functionalities of the purchased item, and also helps us to avoid the formation of most of the defects.
What should a perfect user manual contain?
First and foremost, an user manual of Schneider Electric LUFP7 should contain:
- informations concerning technical data of Schneider Electric LUFP7
- name of the manufacturer and a year of construction of the Schneider Electric LUFP7 item
- rules of operation, control and maintenance of the Schneider Electric LUFP7 item
- safety signs and mark certificates which confirm compatibility with appropriate standards
Why don't we read the manuals?
Usually it results from the lack of time and certainty about functionalities of purchased items. Unfortunately, networking and start-up of Schneider Electric LUFP7 alone are not enough. An instruction contains a number of clues concerning respective functionalities, safety rules, maintenance methods (what means should be used), eventual defects of Schneider Electric LUFP7, and methods of problem resolution. Eventually, when one still can't find the answer to his problems, he will be directed to the Schneider Electric service. Lately animated manuals and instructional videos are quite popular among customers. These kinds of user manuals are effective; they assure that a customer will familiarize himself with the whole material, and won't skip complicated, technical information of Schneider Electric LUFP7.
Why one should read the manuals?
It is mostly in the manuals where we will find the details concerning construction and possibility of the Schneider Electric LUFP7 item, and its use of respective accessory, as well as information concerning all the functions and facilities.
After a successful purchase of an item one should find a moment and get to know with every part of an instruction. Currently the manuals are carefully prearranged and translated, so they could be fully understood by its users. The manuals will serve as an informational aid.
Table of contents for the manual
-
Page 1
LUFP7 Telemecanique User’s manual Gateway Profibus-DP / Modbus RTU[...]
-
Page 2
[...]
-
Page 3
3 LUFP9 Gateway Profibus-DP / Modbus RTU Page 4[...]
-
Page 4
4 In spite of all the care taken over the writing of this docume nt, Schneider Electric SA does not give any guarantees in relation t o the informati on contai ned in it, and may not be held liabl e for any errors, nor for any damage w hich might res ult fr om its use or its applicati on. The characteristics and operation of the products and additi[...]
-
Page 5
5 Table of Contents 1. Introduction ............................................................6 1.1. Introduction to the User Guide ............................................... 6 1.2. Introduction to the LUFP7 Gateway ....................................... 7 1.3. Terminology.....................................................................[...]
-
Page 6
7 1. Introduction 1.1. Introduction to the User Guide C h a p t e r 1 Introduction (page 6) describes the gateway, the user guide that comes with it and the terms used in it. Chapter 2 Hard w are Implementation of the LUFP7 Gate w ay (page 13) gives an introductio n to the gateway and describes all the items u sed when setting it up, both inside (t[...]
-
Page 7
8 1. Introduction 1.2. Introduction to the LUFP7 Gateway The LUFP7 gateway allows a master located on a Profibus -DP network to enter into a dialogu e with the slaves on a Modbus RTU network. This is a generi c protocol converter operating in a way whi c h is transparent to the user. This gateway allows you to inte rface many products marketed by S[...]
-
Page 8
9 1. Introduction 1.4. Notational Conventions 16#•••• ............... Value expressed in hexadecimal, which is equivalent to the H••••, ••••h and 0x•••• notat ions, sometimes used in other documents. N.B. The AbcConf soft wre uses the 0x•••• notation. e.g. 16#0100 = 0x0100 = 256. 02#•••• ••••.[...]
-
Page 9
10 1. Introduction 1.5. Additional Documentation In the case of Modbus slaves, the features, se rvic es and adjustment of the Modbus communication s are not dealt with in this document. 1.6. Introduction to the Communication “System” Architecture Upstream network (Profibus-DP) ATS 4 8 VW33-A48 A TS46 VW3-G46301 Profibus-DP Master Downstream net[...]
-
Page 10
11 1. Introduction Each LUFP7 Profibus-DP / Modbus RTU gate way allo ws one of the PLCs on the Profibus-DP network to command, control and configure up to 8 Modbus slaves. Other Profibus-DP masters on that sa me network can only control them. If there are more than 8 Modbus slav es, you will need to use an appropriate number of LUFP 7 gateways. In [...]
-
Page 11
12 1. Introduction Ö Each LUFP7 gateway is shipped pre-configured so a s to make it easier to operate an d the factory settings can be used as a basis for a conf iguration which will best meet the user’s expectations. The typical operations applicable to this default configuration are described in cha pter 6 Configuri ng the Gateway, page 44. Th[...]
-
Page 12
13 1. Introduction — Managing Gateway ↔ Profibus-DP master exchanges — LUFP7 gateway 0x0000 0x00F3 Input Modbus data : Managem ent of the exchanges with the Profibus -DP m aster Free memory locatio ns : : : : : 0x0200 0x02F3 Output Modbus data Free memory locatio ns : : : : Hilscher Configura tion of Prof ibus -DP exc hanges : ♦ T y pe and [...]
-
Page 13
14 2. Hardware Implementation of the LUFP7 Gateway 2.1. On Receipt After opening the packaging, chec k t hat the following element is there: • One LUFP7 Profibus-DP / Modbus RTU gateway. 2.2. Introduction to the LUFP7 Gateway The cables and oth er accessories for connecting to Profibus-DP and M odbus networks need to be ordered separately. cd e g[...]
-
Page 14
15 2. Hardware Implementation of the LUFP7 Gateway 2.3. Mounting the Gateway on a DIN Rail Mounting the gateway 1 2 Removing the gate w ay 1 2 Start by fitting the rear base of the gateway to the upper part of the rail, pushing down wards (1) to compress the gateway’s spring. Then push the gateway against the DIN rail (2) until the base of the ga[...]
-
Page 15
16 2. Hardware Implementation of the LUFP7 Gateway 2.5. Connecting the Gateway to the Modbus Network Three typical examples of Modbus connection for the gate way and its slaves are shown below. There are many other possible Modbus connections, but they are not covered in this documen t. 2.5.1. Examples of Mod bus Connection Topologies • “Star?[...]
-
Page 16
17 2. Hardware Implementation of the LUFP7 Gateway • “Bus” topology with VW3 A8 306 TF3 dro p boxes: This topology uses VW3 A8 306 TF3 dr op boxes to connect each of the Modbus slaves to the main section o f the Modbus network. Each box should be placed in the immediate vicinity of the Mo dbus slave it is associated with. The cable for the ma[...]
-
Page 17
18 2. Hardware Implementation of the LUFP7 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 conne ctors. We recommend using a VW3 A68 306 connection cable and the TSXCSA•00 Modbus cable s. Connect the RJ45 connector on the VW3 [...]
-
Page 18
19 2. Hardware Implementation of the LUFP7 Gateway 2.5.3. Wiring Recommendations for the Modbus Net w ork • Use a shielded cable with 2 pairs of twisted conductors, • connect the reference potentials to one anothe r, • maximum length of line: 1,000 metres • maximum length of drop line / tap-off: 20 metres • do not connect more than 9 stat[...]
-
Page 19
20 2. Hardware Implementation of the LUFP7 Gateway 2) C ables: VW3 A8 306 R•• Modbus ca ble ................................... (“star” topology / “bus” topology with tap boxes) Shielded cable with a male RJ45 connector at each end. VW3 A68 306 Mo dbus cable ....................................... (“bus” topology with tap bo[...]
-
Page 20
21 2. Hardware Implementation of the LUFP7 Gateway 2.6.2. Wiring Recommendations for the Profibus -DP Network • Use a shielded cable with a twi sted pair of copper conductors, prefera bly a type A Profibus-DP cable. • Connect the reference potentials to one anothe r, • You may choose the transmissi on rate, within limits ranging from 9.6 kbit[...]
-
Page 21
22 2. Hardware Implementation of the LUFP7 Gateway To connect stations to the Profibus-DP network mo re ea sily, several accessories are offered in the Schneider Electric catalogue: – Single twisted pair type A Profibus-DP cable (100 m long): TSX PB SCA100 . If you use a different cable, please check th at its electric characteristics are as clo [...]
-
Page 22
23 2. Hardware Implementation of the LUFP7 Gateway 2.7. Configuring the Profi bus-DP Communication Features This configuration should be carried out when the gateway is powered off. This task is limited to configuring the gateway's Profibus add ress, as the communication speed on the Profibus network (9.6 k bits/s to 12 Mbits/ s) is automatica[...]
-
Page 23
24 3. Signalling The gateway’s 6 LEDs and the descriptive label on th e removable cover which hides its two coding wheels (gateway address) allow you to diag nose the status of the gate way: c e g d f h telm LUFP7 n o p q r s 1 O NLINE 2 O FFLINE 3 N OT U SED 4 F IELDBUS D IAG 5 M ODBUS 6 G ATEWA Y DEL L E D Æ Gatew ay state Off: Profibus-DP bus[...]
-
Page 24
25 4. Software Implementation of the Gateway 4.1. Introduction This chapter gives an introdu ction to a quick impl ementation of the LUFP7 gateway, using its default configuration. All LUFP7 gat eways ship pre-c onfigured . This pre-configuration means that the user does not ha ve to configure the LUFP7 gateway using AbcConf. This configuration is [...]
-
Page 25
26 4. Software Implementation of the Gateway 4.1.2. Configuring the Motor Starters Each motor starter should be configured as follows: Protocol: Modbus RTU slave Start bits 1 Modbus address 1 to 8 Parity None Bitrate 19,200 bits/s Parity bit 0 Data bits 8 Stop bits 1 When using a TeSys U motor starter with a Modbus communicati on module (LULC031 mo[...]
-
Page 26
27 4. Software Implementation of the Gateway 4.2. Gateway Configuration under PL7 PRO and SyCon T he Pr of ib u s- DP ma s t er mu st be c on fi gu r e d s o t ha t i t ha s a cc e s s t o a ll of t h e da t a d e sc ri be d i n c h a pt er s 1 0. 2. 1 Input D a t a M e m o r y A r e a , page 95, and 10.2.2 O u t p u t D a t a Me m o r y A r e a , [...]
-
Page 27
28 4. Software Implementation of the Gateway 4.2.2. Creating a Profibus-DP Net w ork under SyCon Select the “New” option from the “F ile” me nu to create a new configuration, by selecting the “PROFIBUS” network. This option creates an empty network segment in the SyCon main window. In this guide, we shall immediately save this configura[...]
-
Page 28
29 4. Software Implementation of the Gateway Double-click on the line that correspon ds to the Profibus-DP master to open the “Master Configuration” window. In the “DP Support” frame, verify that the "Auto addressing" box has been checked. Lastly, select the Profibus-DP master a nd run the “Bus Parameter…” option from the ?[...]
-
Page 29
30 4. Software Implementation of the Gateway 4.2.5. Selecting and Adding the Gate way to the Profibus-DP Network Run the “Slave…” option from the “I nsert” menu (or cli ck on the button). Move the mouse pointer (which now looks like a ) to the position where you want to add the LUFP7 gateway, then left-click. In the window that appears, s[...]
-
Page 30
31 4. Software Implementation of the Gateway • In the “Assigned maste r” frame, che ck that the Profibus-DP m aster previo usly configured is selecte d. If not, select it. N.B. Only the "Assigned ma ster" can control the DP slave to whi ch it has been allocated during the configuration phase. Other DPM 1 masters can only read its I/[...]
-
Page 31
32 4. Software Implementation of the Gateway 4.2.7. Saving and Exporting the Profibus-DP Net w ork Configuration Save the configuration by givi ng it a name (“Save” or “Save A s…” option from the “F ile” menu). The configuration of the Profibus-DP network is then saved in a “ .pb ” file. In order to export this configuration for P[...]
-
Page 32
33 4. Software Implementation of the Gateway 4.2.9. Configuring the Gate w ay I/O under PL7 PRO Using the information located in the sele cted “ .cnf ” file, PL7 PRO establishes a dire ct relation between the data for each Profibus-DP slave and its equivale nt I/O. To view the LUFP7 gateway I/O, c lick on the line of the address 2 st ation in t[...]
-
Page 33
34 4. Software Implementation of the Gateway The correspondence betwee n the cont ent of the gateway's input memo ry (see chapter 10.2.1 Input Data Memory Area, page 95) and the PLC input s “%IW4.0” to “%IW4.0.15” is given in the following table: Description Service PLC input Bit 15 .................... Bit 8 Bit 7 ....................[...]
-
Page 34
35 4. Software Implementation of the Gateway 4.2.10. Description of Services Assigned to Gate w ay Inputs/Outputs Managing the downstream Modbus net w ork: Refer to chapter 5.3 Diagnostic Only, page 41, for a detailed description of that service, and to cha pter 11.2 LU FP 7 Gateway Initialization and Diagnostics, page 98, for an advanced sample us[...]
-
Page 35
36 4. Software Implementation of the Gateway 4.2.11. Validating and Saving the Conf iguration of the TSX BP 100 Couple r Î Validate the various o perations conducted unde r PL7 PRO using the button. Î Close the configuration window of the TSX PBY 100 coupl er. Î In the PLC's hard ware configuratio n window, click on the button again. Î Sav[...]
-
Page 36
37 4. Software Implementation of the Gateway 4.2.13. Using and Monitoring the TSX PBY 100 Coupler Configur ation After validating all the changes previously made, you may check the conf iguration of the TSX PBY 100 coupler, the Profibus-DP network, and the LUFP7 gateway by downlo ading the PL7 PRO application to the PLC and conducting a monitoring [...]
-
Page 37
38 5. Gateway Initialization and Diagnostics Each of the three sub-chapters 5.2, 5.3 and 5.3.2 de scribes the princip le used to initialize and carry out diagnostics on the gate way using each of the three opt ions offered by the gatew ay. These options can be configured via AbcConf, by changing the assign ment of the “Control/Status Byte” fiel[...]
-
Page 38
39 5.2.1. Profibus-DP Master Control Word The output word located at addresses 16#0200 (MSB) and 16#0201 (LSB) in the gateway ’s output memory constitutes the Profibus-DP master command word. Its structure is described below: Bits Description 15 FB_HS_CONFIRM: Acknowle dgement bit of a gateway diagnostic The Profibus-DP master must compare the va[...]
-
Page 39
40 5. Gateway Initialization and Diagnostics Bits Description 14 FB_HS_SEND: Ne w command from the Profibus-DP m aster Before changing the value of FB_DU, the Prof ibu s -DP master must compare the values of FB_HS_SEND and ABC_HS_CONFIRM (bit 14 of the gatew ay’s status word). If these two values are different, this means that the gateway has not[...]
-
Page 40
41 5. Gateway Initialization and Diagnostics 5.2.2. Gateway Status Word The input word located at addresses 16#0 000 (MSB) and 16#0001 (LSB) in the gateway’s input memory constitutes the gateway’s status word. Its structure is describe d below: Bits Description 15 ABC_HS_SEND: New gate way diagnostic (See description of bit 15 of the Profibus-D[...]
-
Page 41
42 5. Gateway Initialization and Diagnostics The values of the EC and ED fields are described in the table below: EC Des cription of the error ED Notes 2#0000 Re-transmissions on the Modbus network Number of re- transmissions (1) Total number of re-transmi ssions carried out on the sub-network, for all slave s. 2#0001 A Modbus slave is missing Addr[...]
-
Page 42
43 5. Gateway Initialization and Diagnostics Bits Description 13 ABC_DU: Modbus exchan ges activated The gateway activates this bit to tell the Profibus-D P master that the Modbus d ata located in its input memory area have all been updated at least once since the la st activation of FB_DU (“ABC_DU” means “ABC – Data Updated”). These Mod [...]
-
Page 43
44 5. Gateway Initialization and Diagnostics 5.3.2. Profibus-DP Master Control Word The output word located at addresses 16#0200 (MSB) and 16#0201 (L SB) in the gateway’s output memory constitutes the Profibus-DP master command word. Its structure is described below: Bits Description 15 FB_HS_CONFIRM: Acknowle dgement bit of a gateway diagnostic [...]
-
Page 44
45 6. Configuring the Gateway Each part of this chapter describes a sepa rate step allowing the user to personali z e the gateway configuration, according to his own pa rticular needs. Each part gives a n introduction to a basic operat ion isolating it from the rest of the configuration and desc ribing the operations to be ca rried out using AbcCon[...]
-
Page 45
46 6. Configuring the Gateway 6.1.1. Pin Outs — LUFP7 (Configuration) — Female RJ45 Male RJ45 11 22 33 8 RS-485 D(B) 4 4 D(B) RS-485 D(A) 5 5 D(A) 66 +10 V 7 7 +10 V GND 8 8 0 V Straight POWERSUITE cable ——— RS485 / RS232 converter ——— –—— PC (COM) ——– Male RJ45 Female RJ45 Female 9-point SUB-D Male 9-point SUB-D 11 11 2[...]
-
Page 46
47 6. Configuring the Gateway 6.2. Installing AbcConf The minimum system requirem ents for AbcConf are as follows: • Processor ....................................... Pentium 133 MHz • Free hard disk space ...................... 10 Mb • RAM ................................................ 0 8 Mb • Operating system ..........................[...]
-
Page 47
48 6. Configuring the Gateway 6.4. Transferring a Confi guration to the Gateway When using AbcConf, you can transfe r the configurat ion you are editing to the gateway at any time. Choose “Down load conf iguration to ABC-LUFP ” from the “F ile” menu or clic k on the button, in the Ab cConf toolbar. AbcConf initializes a check test of the ga[...]
-
Page 48
49 6. Configuring the Gateway The upper part of this window allo ws you to choose a Modbus command, to edit its contents, then to send it to the Modbus net work (“Command ” menu). The response will then be displayed in this same part. Please se e chapter 2.10 Node monitor in the AbcCo nf user manual, entitled AnyBus Communicator – User for fu[...]
-
Page 49
50 6. Configuring the Gateway 6.6. Deleting a Modbus Slave This step allows you, for instance, to free up a locati on on the downstream Modbus network, known as the “Sub- Network” in AbcConf, in order to replace one Mod bus slave with another. In fact the gateway’s default configuration already allows it to communicate with eight TeSys U moto[...]
-
Page 50
51 6. Configuring the Gateway However, these operations are not necessa ry when del eting a single slave. Conversely, they become almo st essential when most of the Modbu s slaves are delet ed, because these deletions divid e up the gateway’s memory. Please see chapter 6.11 Adding and Setting Up a Mod bus Command, page 68, which describes all of [...]
-
Page 51
52 6. Configuring the Gateway Importing/exporting a Modbus slave configura tion: AbcConf offers the possibility of independently savi ng and loading the configuration of a node on the downstream “Sub-Network”. For inst ance, this will allow you to buil d a library of Modbus slave template s, so that you can use them in any configuration. To sav[...]
-
Page 52
53 6. Configuring the Gateway 6.8. Changing the Periodic Data Exchanged with a Modbus Slave This operation consists of replacing, addin g or delet ing periodic data ex changed with one of the Modbus slaves. With each of these operations, we shall ta ke the default configuration of the LUFP7 gateway as an example, that is to say that any changes pre[...]
-
Page 53
54 6. Configuring the Gateway 6.8.2. Replacing an Output Periodic Data Element E.g. “TeSys U n°6” motor starter. W e are trying to repl ace th e control of the “Command Register” (address 704 = 16#02C0) with the control of the “2n d Command Register” (addre ss 705 = 16#02C1). The operation co nsists of changing the value of the “Star[...]
-
Page 54
55 6. Configuring the Gateway 6.8.3. Increasing the Amount of Periodic Input Data E.g. “TeSys U n°2” m otor starter. We are trying to complete the monitoring of this mo tor starter starting from the currently monitored register, that is to say “TeSys U S tatus Register” (address 455 = 16#01C7), and going as far as the “Reserved: 2nd Warn[...]
-
Page 55
56 6. Configuring the Gateway 3) Changing the location of the Modbus data received in the gateway’s memory: As the number of bytes read (see previous step) has incre ased from 2 to 16, t he Modbus data rece ived must be placed at a different location in the gateway’s memory, and the size of the memory occupied must also b e adjusted appropriate[...]
-
Page 56
57 6. Configuring the Gateway To check that these changes have been e ntered into the configuration, choose “Monitor” from the “S ub- Network” menu again: In point 6), you shall make sure that the tota l input and ouput sizes of the configured modul es are the same as the exchange size s displayed in the “Sub-network Mo nitor.” In the c[...]
-
Page 57
58 6. Configuring the Gateway Under SyCon, all the configure d modules star t from an even addre ss (word-aligned). When you change a configuration that inclu des a one -byte module, you must remove it (“Remove module” button or double-click on the module in the list of configured module s, see page 65) before adding “IN/OUT ”, “INPUT” [...]
-
Page 58
59 6. Configuring the Gateway Description Service PLC input Bit 15 ................... Bit 8 Bit 7 ..................... Bit 0 Managing the downstrea m Modbus netw ork %IW 4 .0 .00 Gateway status word %IW4.0.1 0 Value of the motor starter c status register %IW4.0.2 0 Free memory location %IW4.0.3 0 Value of the motor starter e status register %IW4.[...]
-
Page 59
60 6. Configuring the Gateway 2) Changing the number of data bytes in the Modbus query: The number of bytes written into the memory of the “TeSys U n°4” motor starter memory increases from 2 to 4, as the number of regist ers controlled has increased from 1 to 2. Select the “Byte count” element from the “Query ” and change its value as [...]
-
Page 60
61 6. Configuring the Gateway To see which memory location s are occupied by data from the comman d you are interested in, all you have to do is uncheck the box corresponding to the “Pre set Multiple Registers” command from the “TeSys U n°4” node, as shown above. We can se e t hat the Modbus data transmitted with the qu ery corresponding t[...]
-
Page 61
62 6. Configuring the Gateway To check that these changes have been e ntered into the configuration, choose “Monitor” from the “S ub- Network” menu again: In point 6), you shall make sure that the tota l input and ouput sizes of the configured modul es are the same as the exchange size s displayed in the “Sub-network Mo nitor.” In the c[...]
-
Page 62
63 6. Configuring the Gateway In this case, all you have to do is add an “INPUT: 4 Byte (2 word)” module after the m odule configured for the gateway, as the number of input bytes in t he default configuration is even (word-aligned ). Under SyCon, all the configure d modules star t from an even addre ss (word-aligned). When you change a configu[...]
-
Page 63
64 6. Configuring the Gateway Description Service PLC output Bit 15 .................... Bit 8 Bit 7 ...................... Bit 0 Managing the downstrea m Modbus netw ork %QW 4. 0 .00 Profibus-DP master control word %QW4.0.1 0 Value of the motor starter c command register %QW4.0.2 0 Value of the motor starter d command register %QW4.0.3 0 Value of [...]
-
Page 64
65 6. Configuring the Gateway 2) Deleting the read command for a parameter: Select the persona lized “Transactions 1” command and delete it with the “ Del ” key (or “Delete” from the menu wh ose nam e corresponds to the nam e of the selected node). A request for confirmation appears, a sking you whethe r or not to proceed deleting the ?[...]
-
Page 65
66 6. Configuring the Gateway 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 no w free. N.B. The free memory location at address 16#0 012 in the gateway’s memory is no longe r p[...]
-
Page 66
67 6. Configuring the Gateway Then you should save and expo rt the co nfiguration of the Profibus-DP network, as described in chapter 4.2.7 Saving and Exporting the Profibus-DP Network Configuration, page 31. 8) Configuring the inputs and outputs of the Profib us-DP master PLC: under PL7 PRO, import the new configuration of the Profibus-DP network [...]
-
Page 67
68 6. Configuring the Gateway 6.10. Changing a Modbus Slave Configuration Configuring a Modbus slave itself remains very sim p le because it only involves the name and the Modbus address of the node to which it corresp onds. On the contrary, configuri ng Modbus commands is much more complete and is the subject of a separate obj ect of its own (see [...]
-
Page 68
69 6. Configuring the Gateway 6.11. Adding and Setting Up a Modbus Command 6.11.1. With the TeSys U Motor Starters With TeSys U motor starters, the main use of adding a Modbus command consists of allowing you to control o r monitor additional registers, without having to chang e the elements in the default configuration. So, the operation of the pe[...]
-
Page 69
70 6. Configuring the Gateway Name of the Modbus command Modbus quer y ! Frame " Slave no. Function no. No. of the 1st word ( MSB / LSB ) Number of words ( MSB / LSB ) Numbe r of b y tes …Values of the words ( MSB/LSB ) … CRC16 ( LSB / MSB ) Modbus res p onse ! Frame " Slave no. Function no. No. of the 1st word ( MSB / LSB ) Number of[...]
-
Page 70
71 6. Configuring the Gateway 6.11.2. With a Generic Modbus Slave Unlike the previou s chapter, here we will be looking at adding and setting up a Modbus command which is different from those configure d by default with t he LUFP7 gateway. We will benefit from this occasion to exhaustively describe the fields allowing you to se t up the management [...]
-
Page 71
72 6. Configuring the Gateway Name of the Modbus slave Name of the Modbus command Modbus quer y ! Frame " Slave no. Function no. Word no. ( MSB / LSB ) Value of the word ( MSB / LSB ) CRC16 ( LSB / MSB ) Modbus res p onse ! Frame " Slave no. Function no. Word no. ( MSB / LSB ) Value of the word ( MSB / LSB ) CRC16 ( LSB / MSB ) These elem[...]
-
Page 72
73 6. Configuring the Gateway 6.11.2.2. Configuring the Query Select the “Query” element from the Modbus command. The various elements of the configurat ion of the query for this command are shown opposite. The values displayed co rrespond to the default values for any new command. These elements allow you to conf igure ho w the whole command i[...]
-
Page 73
74 6. Configuring the Gateway Configuration element Description Retries This element indicates the number of re-tr ansmissio ns carried out by the gateway if there is no response from the Modbus sl ave to a query, or if the response is incorrect. This re- transmission process cease s as soon as the gateway gets a correct respo nse within a given ti[...]
-
Page 74
75 6. Configuring the Gateway Configuration element Description Update mode This element is u sed to specif y the transmissio n mode for the query on the Modbu s network. It takes one of the following four value s: - Cyclically................................. De fau lt c omm un ic ati on m ode . T he query is t ran smi tte d periodically on the Mo[...]
-
Page 75
76 6. Configuring the Gateway 6.11.2.3. Configuring the Response Next select the “Response” elem ent from the Modbus command. The various element s of the configuration of the response for this command are shown op posite. The values displayed corresp ond to the default values for any new command. These elements all ow you to configure a single[...]
-
Page 76
77 6. Configuring the Gateway Configuration element Description Trigger byte address (contd.) The Profibus-DP ma ster PLC will be able to detect the receipt of a resp onse from a Modbus slave by comparing the previous value and the current value of the associated counter (address 16#001E or 16#00 1F). If there is a unitary incrementatio n of this c[...]
-
Page 77
78 6. Configuring the Gateway Field in the frame Size in the frame Description Slave Address 1 byte This field cannot be changed by the us er and its value is greyed out to inform him of the fact. AbcCo nf updates the value of this field automatically usin g the address of the Modbus slave corresponding to the cu rrent node. N.B.: This field is com[...]
-
Page 78
79 6. Configuring the Gateway Field in the frame Size in the frame Description Preset Data (contd…) Byte swap: Specifies whether the outpu t data bytes to be transmitted to the Modbus slave must be swapped befo r e being placed in the Modbus frame or not. The three possible values are as follows: - No swapping ....... Def au lt c onf ig ur at io [...]
-
Page 79
80 6. Configuring the Gateway If the value of a field from the response of a Modbus sla ve is different from that configured via AbcConf, the response will be rejec ted by the ga teway. It will then proceed to a re-transmission of the query, provided that at least one re-t ransmission has been configured for this command (se e chapter 6.11.2.2 Conf[...]
-
Page 80
81 6. Configuring the Gateway 6.11.3. Adding a Special Modbus Command Apart from the standard Modbus co mmands covered in the previous chapt er, it is possible to create two types of special Modbus commands: Modbus commands using the same template as standard commands and Modbus commands who se nature and frame content can be com pletely changed by[...]
-
Page 81
82 6. Configuring the Gateway Constants in Byte, Word or DWord format allow you to relieve the Profibus-DP master by placing the values of these constants in Modbus qu ery frames (constants in “Query” elements) or by com paring them to the values located in the Modbus respon ses (constants in “Respo nse” element s). These comparisons are us[...]
-
Page 82
83 6. Configuring the Gateway The only command accessible from the “Fieldbu s” menu is “About Fieldbus… ”. In “on-line” mode (see chapte r 6.12.2 “ABC” Element, page 82), the window shown oppo site will be displayed. In “off-line” mode the word “Unkn own” will replace “Profibus-DP ” to show that the type of upstream ne[...]
-
Page 83
84 6. Configuring the Gateway Apart from the “Control/Status Byte” and “Module Rese t” options, the configu ration of the LUFP7 gateway’s “ABC” element should not be changed. Out of the four opt ions shown below, the last two shoul d therefore retain the values shown: “Serial” and “Ma ster Mode”. These four options allow you t[...]
-
Page 84
85 6. Configuring the Gateway - “Sub-Network Status…”: In “on-line” mode (see chapter 6.12.2 “ABC” Element, page 82), this command displays a window summa rizing the values of the gateway’s error counters. These counters a re also used by the gateway to update the value of its status word (see chapter 5.2.2 Gateway Status Word, page[...]
-
Page 85
86 6. Configuring the Gateway 6.13. Adding a Broadcaster Node A broadcaster n ode does not correspond to any Modbus slave in particular, as it appli es to all Modbus slaves. All the commands which will be co nfigured for this node will be transmitted with the “Slave Address” field set to 16#00. This means that all of the slaves will run t he co[...]
-
Page 86
87 7. Appendix A: Technical Characteristics 7.1. Environment Dimensions (excludi ng connectors) Height: 120 mm Width: 27 mm Depth: 75 mm External appearance Plastic case with device for fixing to a DIN rail. Torque PSU connector: between 5 and 7 lbs.-in. Power supply 24V insulated ±10% Maximum consumption: Around 95 mA Maximum internal consumption[...]
-
Page 87
88 7. Appendix A: Technical Characteristics Profibus-DP charac teristic s (cont'd) • Maximum number of stations: 32 stations per segment, repeater included; up to 126 sta tions with all three repeaters (repeaters included). Address 126 is reserved and should therefore not be used for exchanging data. • Possible types of stations: the re ar[...]
-
Page 88
89 7. Appendix A: Technical Characteristics Profibus-DP LUFP7 gateway specifics (cont'd) • Profibus-DP address configured using 2 coding wheels (address between 1 and 99); address 0 is not allowed. • Profibus-DP diagnosti cs service: Yes (standard 6-byte diag nostic). • "Resetting to zero" operating mode (input reading and outp[...]
-
Page 89
90 7. Appendix A: Technical Characteristics Structure of the LUFP7 gateway’s memory: Outputs • 2 bytes for the activation or inhibition of the downstream network by the gateway (see chapter 5 Gateway Initialization and Diag nostics, page 37). • 242 bytes accessible by the Profibus -DP master in the form of output data (see chapter chapitre 10[...]
-
Page 90
91 8. Appendix B: LUFP7 Gateway GSD File The LUFP7 gateway GSD file contains all the inform ation and settings for config uring the gateway under Profibus-DP. This file, “ Tele071F.gsd ”, is used by SyCon to generate info rmation that will eventually be used by the DPM1 master PLC during setup phases. Refer to chapter 4.2.4 Setting up the Gatew[...]
-
Page 91
92 8. Appendix B: LUFP7 Gateway GSD File ; Supported baudrates 9.6_supp = 1 19.2_supp = 1 45.45_supp = 1 93.75_supp = 1 187.5_supp = 1 500_supp = 1 1.5M_supp = 1 3M_supp = 1 6M_supp = 1 12M_supp = 1 Communication rates sup ported by the LUFP7 gateway. All rates should be mentioned in this section. The gateway support s all the baud rates of the Pro[...]
-
Page 92
93 8. Appendix B: LUFP7 Gateway GSD File Module = "IN/OUT: 1 Byte" 0x30 EndModule ; Module = "IN/OUT: 2 Byte ( 1 word)" 0x70 EndModule ; Module = "IN/OUT: 4 Byte ( 2 word)" 0x71 EndModule ; Module = "IN/OUT: 6 Byte ( 3 word)" 0x72 EndModule ; Module = "IN/OUT: 8 Byte ( 4 word)" 0x73 EndModule ; Modu[...]
-
Page 93
94 9. Appendix C: Default Configuration Module = "INPUT: 128 Byte (64 word)" 0x40,0x7F EndModule ; Module = "OUTPUT: 1 Byte" 0x20 EndModule ; Module = "OUTPUT: 2 Byte ( 1 word)" 0x60 EndModule ; Module = "OUTPUT: 4 Byte ( 2 word)" 0x61 EndModule ; Module = "OUTPUT: 6 Byte ( 3 word)" 0x62 EndModule ;[...]
-
Page 94
95 10. Appendix C: Default Configuration The configuration described be low correspond s to the LUFP7 gateway’s default confi guration. This chapter mainly gives the user inform ation a bout the performances obtained on the downstream Modbus network. It allows the user to decide whether, for example, he sh ould change the perio d for cyclical exc[...]
-
Page 95
96 10. Appendix C: Default Configuration 10.2. Content of the Gateway’s DPRAM Memory The LUFP7 gateway’s DPRAM memory contains all of the data exchanged b etween the gateway and the 8 TeSys U motor sta rters, as well as two specia l registers only exch anged bet ween the gateway and the Profibus-DP master (words used for managing the downst rea[...]
-
Page 96
97 10. Appendix C: Default Configuration 10.2.2. Output Data Memory Area The gateway has 244 o utput bytes. On ly the first 32 by tes are used. One should therefore configure only one 32- byte input/output module using a Profibus-DP configuration device such as SyCon. Service Address Size Description Managing the downstream Modbus network 16#0200 1[...]
-
Page 97
98 11. Appendix D: Sample Use under PL7 PRO A practical example can be found on the CD LU9 CD1. It is composed of four files. • The first file, “ LUFP7_Tutorial_EN.pb ”, is a SyCon file for a Profibus -DP network. It therefore represents the configuration of the Profibus-DP netwo rk, as it is described in the previous chapters. Thi s file is [...]
-
Page 98
99 11. Appendix D: Sample Use under PL7 PRO This description remain s concise, because it is only meant to describe the overall operation of the program and the way to use the related screen. If you need furthe r detail, don't hesitate and review the actual content of the example under PL7 PRO. The source code is comment ed by and large to hel[...]
-
Page 99
100 11. Appendix D: Sample Use under PL7 PRO • Comprehensive display of LUFP7 gateway diagnostics, via a thorough interp retation of the gateway status word (see chapter 5.2.2 Gateway Status Word, pag e 40). This interpretation i s made in the program “Handshake _lufp7”. A button appears as soon as a new di agnostic is ma de available by the [...]
-
Page 100
101 11. Appendix D: Sample Use under PL7 PRO 11.3. Controlling and Supervisi ng the 8 TeSys U Motor Starters The “Super vision Control” operating screen (see picture below) is meant to moni tor the status of the 8 Te Sys U motor starters, numbered from 1 to 8 . It is also meant to control them individuall y using several buttons. Registers 455 [...]
-
Page 101
102 11. Appendix D: Sample Use under PL7 PRO The “Sr0” sub-program is called once per motor starter from the “Cmd_mo n” program. Each of these calls should be made with a different value in the word %MW0 (between 0 and 7) as it is used to index the status word and the command word of the same motor starter. The sub-program assists t he scre[...]
-
Page 102
103 11. Appendix D: Sample Use under PL7 PRO • The second frame, “Paramete r Addr ess,” allows you to set the address of the param eter to read/write. When the “SEND command” button is bein g pushed, the va lue currently set in this frame is copied into the “Read parameter a ddress” field of the reading command (%QW4.0.10) or into the[...]
-
Page 103
104 11. Appendix D: Sample Use under PL7 PRO The “ Pkw_ser vice” program includes the ST instru ctions that us e the settings and values from the first frames of the previously described “PKW Service” operation screen. These instru ctions are mainly designed to update the PLC outputs that relate to the commands of the aper iodi c parameter [...]
-
Page 104
105 12. Appendix E: Profibus-DP Data and Diagnostics The various elements prese nted here are detailed in the documentation of the Profibus-DP master you will have to use. In the case of the TSX PBY 100 coupler of the Premium automatic controls, for exam ple, these elements are detailed in the Implementation Manual – TSX PBY 100 – PROFIBUS -DP [...]
-
Page 105
106 12. Appendix E: Profibus-DP Data and Diagnostics 12.2. Gateway Configuration Data These data are transmitted to the Profibus-DP ma ster upon gateway initialization exchang es. These exchanges enable the Profibus-DP master to set up, configure, and diagno se each of the slaves. The TSX PBY 100 coupler conducts these setup exchanges, but they are[...]
-
Page 106
107 12. Appendix E: Profibus-DP Data and Diagnostics For the LUFP7 gateway default config uration, the following response is received from the TSX PBY 100 coupler: Bytes Name Value Bytes Name Value 0-1 T otal length 16#0019 14 Group Flags 16#00 2 Number of %IW 16#10 15 Address ID (1) 16#02 3 Number of %QW 16#10 16 Modular slave 16#01 4-5 %IW offset[...]
-
Page 107
108 12. Appendix E: Profibus-DP Data and Diagnostics For the LUFP7 gateway default config uration, the following response is received from the TSX PBY 100 coupler: Bytes Name Value Bytes Name Value 0 Configured 16#01 8 Diagnostic data size 16#06 1 Operating 16#01 9 Compact diagnostic 16#00 2-3 Number of %IW 16#0010 10 Diagnostic counter (1) 16#0A 4[...]
-
Page 108
109 13. Appendix F: Modbus Commands Function code Broad cast (1) Modbus command 0 3 16#03 — Read Holding Registers 0 6 16#06 Yes Preset Single Register Only the Modbus commands shown in the right-hand table are suppo rted by the gateway. The structure of the query and response frames for each of these commands is then de scribed in the following [...]
-
Page 109
110 13. Appendix F: Modbus Commands Chapter 6.11 Adding and Setting Up a Modbus Command, page 68, also shows a few examples of correspondences betwe en the elements displayed in AbcConf and the correspo nding Modbus frame fields. See also: Chapter 6 .11.2 With a Generic Modbus Slave, page 70, and chapter 6.11.3 Adding a Special Modbus Command, page[...]
-
Page 110
111 13. Appendix F: Modbus Commands 13.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 o f Registers ( MSB) Number o f Registers (L SB) - Num ber of output / internal registers Byte Count - Number of data byt[...]
-
Page 111
112 13. Appendix F: Modbus Commands Code Name of the exception Description of the excep tion 16#01 I LLEGAL F UNCTION The query’s “Function” comman d code is not implemented in the Modbus slave software, or it is unable to process it for the moment. 16#02 I LLEGAL D ATA A DDRESS The combination of the query’s “Starting Add ress” and “[...]
-
Page 112
113 14. Appendix F : Concept and Quantum PLC The default data type of Concept with a Quantum PLC is "BOO L". As shown in the first drawing hereafter, "BOOL" sh ould not be u sed for the data storage of the LUFP7. The bytes (MSB/LSB) and bits are twisted with data type "BOOL". The data type for the LUFP7 gateway at Conc[...]
-
Page 113
114 14. Appendix F : Concept and Quantum PLC Page left intentionally blank.[...]
-
Page 114
[...]
-
Page 115
User’s Manual LUFP7 V1.1 2003-05[...]