(Master Slave Mode) This chapter explains how to connect multiple HMIs.

Transcription

1 Multi-HMI Communication (Master Slave Mode) This chapter explains how to connect multiple HMIs Overview Steps to Create a Project of Master HMI Steps to Create a Project of Slave HMI Steps to Connect with MT500 Slave HMI

2 Overview Multi-HMI Communication means that a HMI connects with a remote HMI via COM port, and read the data in the PLC connected to the remote HMI as shown in the following figure. The PLC is connected with HMI 1, and HMI 1 is connected with HMI 2 via COM port, so that HMI 2 can read the data in PLC through HMI 1. The following parts explain how to create the projects used in HMI 1 and HMI 2 by using EasyBuilder Pro Steps to Create a Project of Master HMI The following is the settings of HMI 1 in [System Parameter Settings]» [Device List]. 1. Since COM 1 of HMI 1 connects to PLC; the device list must include [Local PLC 1], and set the correct parameters. In this example the connected PLC is FATEK FB Series. 2. COM 3 of HMI 1 is used to receive commands from HMI 2; a new device must be added [Master-Slave Server] for setting communication properties of COM 3. The parameters of COM 3 in the example are set to , E, 8, 1, and uses RS232. These parameters are not required to be the same as PLC settings, but the [Data bits] must be set to 8. In general, a higher baud rate is recommended for HMI 2 to efficiently read PLC data.

3 Steps to Create a Project of Slave HMI The following is the settings of HMI 2 in [System Parameter Settings]» [Device List]. Since the PLC that HMI 2 reads is connected with HMI 1, thus for HMI 2, PLC is a remote device. Therefore, it is necessary to add a [Remote PLC] into the device list. In this example the connected PLC is FATEK FB Series. The way to create [*Remote PLC 1] is described in the following steps. 1. Add a new device. Set [PLC type] to [FATEK FB Series] and [PLC default station no.] must be set in accordance with the connected PLC. 2. Correctly set the parameters. Since COM 1 of HMI 2 connects with COM 3 of HMI 1 instead of directly connect with PLC, the settings of PLC will be ignored. HMI 2 COM 1 and HMI 1 COM 3 must set to the same communication parameters and interfaces. As shown in the following figure, use RS232, and set parameters to [115200, E, 8, 1].

4 For HMI 2, PLC is a remote device, change [Location] to [Remote], and select [COM port] to connect remote HMI (HMI 1). 4. When finished, a new device [Remote PLC] can be found in the [Device List]. This device has a * symbol, which means, even if it contains Remote in the name, it actually gives commands and gets replies through a local COM port, and therefore the connection with PLC can be checked from a local system register. [*Remote PLC 1], [*Remote PLC 2], [*Remote PLC 3] and [Local PLC 1], [Local PLC 2], [Local PLC 3] use the same system registers from the listed below.

5 28-5 Register LB-9150 LB-9151 LB-9152 LB-9200~ LB-9455 LB-9500~ LB-9755 LB-9800~ LB Description When ON, automatically connects with PLC (COM 1) when disconnected. When OFF, ignores disconnection with PLC. When ON, automatically connects with PLC (COM 2) when disconnected. When OFF, ignores disconnection with PLC. When ON, automatically connects with PLC (COM 3) when disconnected. When OFF, ignores disconnection with PLC. These local registers indicate the connection states with PLC (through COM1). LB9200 indicates the connection state with PLC (station no. 0), and LB9201 indicates the connection state with PLC (station no. 1) and so on. When ON, indicates the connection state is normal. When OFF, indicates disconnection with PLC. Set ON again, the system will then try to connect with PLC. These local registers indicate the connection states with PLC (through COM2). LB9500 indicates the connection state with PLC (station no. 0), and LB9501 indicates the connection state with PLC (station no. 1) and so on. When ON, indicates the connection state is normal. When OFF, indicates disconnection with PLC. Set ON again, the system will then try to connect with PLC. These local registers indicate the connection states with PLC (through COM3). LB9800 indicates the connection state with PLC (station no. 0), and LB9801 indicates the connection state with PLC (station no. 1) and so on. When ON, indicates the connection state is normal. When OFF, indicates disconnection with PLC. Set ON again, the system will then try to connect with PLC Steps to Connect with MT500 Slave HMI EasyBuilder Master-Slave Protocol enables MT500 to exchange data with emt3000 local data via the connected PLC Settings in EasyBuilder Pro 1. Select [Master-Slave Server] and click [Settings]. If a PLC is connected, follow the original settings.

6 Select [RS-232], click [Settings]. 3. Fill in MT500 PLC ID No. in [Parameter 1] (Refer to MT500 settings) Settings in EasyBuilder In [System Parameter Settings], set [Multiple HMI] to Slave, set [HMI-HMI link speed] to Note [Baud rate] must be identical in EasyBuilder500 and EasyBuilder Pro.

7 Double click PLC Address View.exe to check PLC ID No. and fill in [Parameter 1] of EasyBuilder. 3. Connect HMIs via Com Port RS-232, the communication is then enabled.

8 28-8 Note There will always be a PLC selected in MT500 system parameter settings, in this case, even to read/write emt3000 local data, the ID of the selected PLC of MT500 system parameters must also be filled in EasyBuilder [Parameter 1]. When using S7-200, S7-300 drivers, since MT500 reverses the high bytes and the low bytes, this will cause MT500 to misread emt3000 local data, therefore this way is not available in Master-Slave Mode. The Comparison between MT500 and emt3000: Bit/Word MT500 emt3000 Range B Ms_RB RW_Bit dddd: 0~4095 (h): 0~f B Ms_LB LB dddd: 0~9999 W Ms_RW RW ddddd: 0~65535 W Ms_LW LW dddd: 0~9999