OPERATOR INTERFACE PRODUCTS APPLICATION NOTE

Subject: Schneider Modbus RTU to Zelio 2 SR3 using GP-Pro PBIII AN# 1137 Rev A Date: 08/20/2005 Name: Bjorn den Dunnen Page: 1/8

Description: This application note shows how to set up a Modbus RTU connection between a Pro-face GP, GLC or ST using the Schneider Modbus RTU 1:n comm. driver in GP-Pro PBIII and Zelio SR3 system using the SR3-MBU01BD communication module.
Within the scope of this application note the terms ST, GP and GLC can be read as applying to any ST-400, ST-403, GP-2000/1 and GLC-2000 series hardware without exceptions unless noted otherwise. Contents 1) Cable Diagrams (ST-400 or GP/GLC-2000 Series to 1 Zelio 2 SR3-MBU01BD) 2) Communication Settings 3) Addressing 4) Error Codes 5) Disclaimer 1) Cable Diagrams Cable Diagram 1: ST-400 or ST-403.

OPERATOR INTERFACE PRODUCTS APPLICATION NOTE

Cable Diagram 2: GP-2x00, GP-2x01 and GLC-2x00 Series.

2) Communication Settings 1) Make sure you are using GP-Pro PBIII v7.x C-Package 03 (for details see Help, About) 2) In the Project Manager select Schneider Electric. and Schneider Modbus RTU 1:n comm.

OPERATOR INTERFACE PRODUCTS APPLICATION NOTE

3) In GP Settings on the Mode Settings tab select Modbus Config. No. of Nodes Number of Zelio nodes (1 - 31) Node No. This number is used in your GP-Pro project as #_ prefix to the plc registers you enter. (See Addressing for details) Modbus RTU Address This setting is your actual Zelio 2 Modbus address. Enter a different Modbus RTU Address for each Zelio in the Node No. list. 4) On the Extended Settings tab select System Area Uncheck all selected items to prevent unwanted GP/ST to Zelio communication. For details on the functions of the ST System Area refer to the PLC connection manual.

OPERATOR INTERFACE PRODUCTS APPLICATION NOTE

2) Communication Settings (continued) 5) Go to the Communication Settings tab Use the following settings and make sure to match these setting in your PLC setup: GP-Pro PBIII Communication Settings (GP Setup, Communication Settings)

Zelio Soft 2 Communication Settings (Edit, Program Configuration, Modbus Extension)

Note: Baud Rate and Parity Bit can be changed as long as the settings match.

OPERATOR INTERFACE PRODUCTS APPLICATION NOTE

3) Addressing The GP-Pro driver used is a generic Modbus RTU driver, not designed for Zelio 2 I/O specifically.

N = Node 1 - 31 D = 4 Holding Register A = Zelio 2 Address + 1

N = Node 1 - 31 D = 4 Holding Register A = Zelio 2 Address + 1 B = 00 - 15

About the address offset Modbus addressing is offset by 1: to read address 10h (16d) use N_400017 Reading / Writing an Integer value (assuming 1 PLC, Node number 1) Zelio 20h (32d) = 1_400033 Reading / Writing 1 bit in an Integer value (assuming 1 PLC, Node number 1) Zelio Run/Stop = 1_40004900 Below is a simplified view of the Zelio Soft 2 FBD editor showing the JnXT1 input form the GP/ST to the Zelio and the OnXT1 output from the Zelio to the GP/ST. (note that your are not required to send the data from the input directly to the output, the data flow below is used to illustrate the relation of J and O)

OPERATOR INTERFACE PRODUCTS APPLICATION NOTE

3) Addressing (continued) Address Range: The Zelio 2 SR3-MBU01 allows you to read/write 13 16-bit registers with predefined functions. Note that the SR3-MBU01 module cannot be used in combination with all Zelio modules. NOTE: The JnXT1 and OnXT1 addresses can only be used in FBD mode, LD cannot be used. This only affects the Input/Output registers, in LD mode the Clock and Status can still be used. Refer to your Zelio Soft 2 documentation for details on how to work with the Input and Output areas. Zelio Illegal 10h / 16d 11h / 17d 12h / 18d 13h / 19d 14h / 20d * 15h / 21d * 16h / 22d * 17h / 23d * No data 20h / 32d 21h / 33d 22h / 34d 23h / 35d No data 30h / 48d Illegal GP-Pro <= 1_400016 1_400017 1_400018 1_400019 1_400020 1_400021 1_400022 1_400023 1_400024 1_400025~32 1_400033 1_400034 1_400035 1_400036 1_400037~48 1_400049 >= 1_400050 Read/Write n/a R/W R/W R/W R/W R/W R/W R/W R/W R R/W R/W R/W R/W R R/W n/a Function Illegal Address, 02:02 error on read and write Output to Zelio J1XT1 (FBD mode only) Output to Zelio J2XT1 (FBD mode only) Output to Zelio J3XT1 (FBD mode only) Output to Zelio J4XT1 (FBD mode only) Input from Zelio O1XT1 (FBD mode only) Input from Zelio O2XT1 (FBD mode only) Input from Zelio O3XT1 (FBD mode only) Input from Zelio O4XT1 (FBD mode only) Read Only (No Data), 02:02 error on write Clock Clock Clock Clock Read Only (No Data), 02:02 error on write Status Illegal Address, 02:02 error on read and write

* NOTE: the Zelio Soft 2 v2.4 English manual states that the O1XT1 O4XT1 addresses can be found in addresses 0000h 0003h. Instead use the addresses shown in the table above.

OPERATOR INTERFACE PRODUCTS APPLICATION NOTE

4) Error Codes General Description of ST error codes showing up in the lower left hand corner of the screen: 02:__:___ = the standard prefix for a plc communication error __:XX:___ = the actual error code, refer to the list below for details __:__:### = the Node Number of the PLC to which the error applies Error Description Cause 02:FF.### (PLC Not Connected) There is no communication with the PLC - There has been no communication with the PLC for x seconds. - The communication cable is unplugged / wrong / damaged on the ST side. - The ERA / CSA and / or ERB / CSB lines are not connected loop on the ST side cable 02:FE.### (PLC Not Responding) The ST has successfully sent a message but there is no reply from the PLC. - A & B lines in the cable are disconnected or connected wrong. - The communication settings on ST do not match those on the PLC - The PLC Node number does not match the setup on the ST - When powered up simultaneously the ST tries to communicate before the PLC is ready. If it is go to GP Setup on the GP Settings tab add a value in the Com Port Startup Delay field. When powered up simultaneously the ST will now wait x seconds before trying to establish communication. 02:FD.### (Receive Data Error) The ST and PLC are communicating but cannot interpret the data received - During normal communication one of the peers fails, cutting a message short - Parity settings, Start / Stop bit setup mismatch between ST and PLC 02:FB.### (PLC Com. Error) The ST and PLC are communicating but the PLC cannot write the data - Your are trying to write an integer value to a 3 register - Your are trying to set, reset or toggle a bit in a 1 register 02:02.### (PLC Com. Error) Communication is established but a PLC address is illegal - An address is out of range (see addressing) - Address type in the GP-Pro editor is not according to addressing convention: check the Symbol Editor to see if there are any unassigned (and unintended) symbolic names. 02:01.### (PLC Com. Error) Illegal Command Code - Trying to read an Input Register (3) device instead of 4 (Output Register)

Error Description Cause

Error Description Cause

Error Description Cause

Error Description Cause

Error Description Cause

OPERATOR INTERFACE PRODUCTS APPLICATION NOTE

5) Disclaimer All company, product, model and brand names used in this application note are the property of their respective owners. For this application note the following hardware was used: Zelio 2 SR3-B101BD (SW 2.0.01, HW 1.0.00, FW 2.19) Zelio 2 SR3-MBU01BD (SW 1.1, HW 1.0) Zelio Soft 2 v2.4 GLC2300-LG41-24V GP2600-TC41-24V GP-Pro PBIII v7.21 ML