RUI/Gateway & Modbus® TCP Configuration & Programming Example Using KEPServerEX 4.0 ® Configuring the EZ-ZONE RUI/Gateway 1. This White Paper is not meant to be an exhaustive step-by-step discussion in configuring the RUI/Gateway, for this work has already been done in two other published EZ-ZONE® user manuals.
RUI/Gateway & Modbus® TCP Configuration & Programming Example Using KEPServerEX 4.0 3. Some notables regarding the graphic above. In the steps that follow we are going to focus on four of the prompts shown: a. Modbus® Enable (Mb;E) b. Gateway instance (GTW) c. Gateway enable (du;En) d. Modbus® offset (M;oF) 4. Notice in the graphic in step 2 that the RUI/Gateway has 2 “Com” instances.
RUI/Gateway & Modbus® TCP Configuration & Programming Example Using KEPServerEX 4.0 9. Provide a name for the channel. 10. In this example the device driver selected will be “Modbus Ethernet”.
RUI/Gateway & Modbus® TCP Configuration & Programming Example Using KEPServerEX 4.0 11. Select the appropriate hardware (network adapter) used on the network. 12. Next, select the appropriate write optimization method.
RUI/Gateway & Modbus® TCP Configuration & Programming Example Using KEPServerEX 4.0 13. The next selection allows for multiple masters on the network. When multiple masters exist on a network talking (reading & writing) to the same slaves, possible conflicts between masters can exist when performing a write operation. 14. Click finish to complete this part of the configuration.
RUI/Gateway & Modbus® TCP Configuration & Programming Example Using KEPServerEX 4.0 15. Once the channel configuration is complete it is now time to configure a device (RUI/Gateway). 16. Select the Modbus® driver.
RUI/Gateway & Modbus® TCP Configuration & Programming Example Using KEPServerEX 4.0 17. Recall that in steps 1-3 it was said that there are other configuration steps that need to be addressed that are not covered in this paper. As an example of those parameters that need to be set on the RUI/Gateway we see the IP address coming into focus. Enter the Modbus® TCP/IP address of the RUI/Gateway. 18. Set timing according to your network requirements.
RUI/Gateway & Modbus® TCP Configuration & Programming Example Using KEPServerEX 4.0 19. If communications fail between KEPServerEX and RUI/Gateway stop polling device. 20. Generate unique input / output (I/O) tags for the RUI/Gateway.
RUI/Gateway & Modbus® TCP Configuration & Programming Example Using KEPServerEX 4.0 21. Use the defaults for port number and IP protocol. 22. Use the defaults as shown.
RUI/Gateway & Modbus® TCP Configuration & Programming Example Using KEPServerEX 4.0 23. The graphic below shows the default Modbus® word order which also represents the default Modbus® word order for the RUI/Gateway (Low/High). 24. Coil access is not used with the RUI/Gateway. The number of registers shown limits KEPServerEX in the maximum number of registers which can be read at a time.
RUI/Gateway & Modbus® TCP Configuration & Programming Example Using KEPServerEX 4.0 25. KEPServerEX allows for imported tags via a text file. 26. Any tag returning an exception error will no longer be polled.
RUI/Gateway & Modbus® TCP Configuration & Programming Example Using KEPServerEX 4.0 27. This concludes the device (RUI/Gateway) configuration. 28. Tag creation. In step 5 some prompts were shown indicating further explanation would follow, well, here we are. The Gateway Instance and the Gateway Enable prompts must be set as shown in step 5 for this particular network. The Gateway Instance corresponds to the address given to the PM control and the Gateway Enable simply requires a “Yes” or “No” response.
RUI/Gateway & Modbus® TCP Configuration & Programming Example Using KEPServerEX 4.0 each: PV1 of PM1 = 400361 (offset = 0) PV1 of PM2 = 405361 (offset = 5000) PV1 of PM3 = 410361 (offset = 10000) PV1 of PM4 = 415361 (offset = 15000) 29. Now that we know the finer details of the Modbus® offset prompts lets go back to KEPServerEX and look closer at the tag configuration and properties.
RUI/Gateway & Modbus® TCP Configuration & Programming Example Using KEPServerEX 4.0 30. To create similar tags for PV2 - PV4 simply click on the duplicate icon (circle) and change the fields accordingly (squares). 31. Once each of the Process Variables are configured and made available to KEPServerEX a similar screen as shown below should be displayed. 32. The above examples represent tags for inputs where a similar procedure beginning at step 29 can be used to create output tags.
RUI/Gateway & Modbus® TCP Configuration & Programming Example Using KEPServerEX 4.0 said, look closely at the addresses given in defining the CLSP for each of the four PM controls. 33. In the screen shot above we now see a series of inputs and outputs that have been configured within KEPServerEX.
RUI/Gateway & Modbus® TCP Configuration & Programming Example Using KEPServerEX 4.0 34. To better understand the following discussion and examples download and read the section entitled “User Programmable Memory Blocks” found in the EZ-ZONE® PM Communications user manual.
RUI/Gateway & Modbus® TCP Configuration & Programming Example Using KEPServerEX 4.0 36. In the screen shot that follows one can see the factory defaults for the Assembly Definition Addresses (block of 80 words) as they are being read through the RUI/Gateway. As explained in the EZ-ZONE® PM Communications user manual and above as well, the enumerated values shown in each of these Modbus® registers represents the actual Modbus® registers for each of the 80 corresponding Assembly Working Addresses.
RUI/Gateway & Modbus® TCP Configuration & Programming Example Using KEPServerEX 4.0 38. Changing an element in the assembly is EZ. A new tag was created as shown below. Notice the address identified as well as the data type.
RUI/Gateway & Modbus® TCP Configuration & Programming Example Using KEPServerEX 4.0 39. The address shown above represents pointer 12 as shown in the EZ-ZONE® PM Communications user manual under the sub-heading of “User Programmable Memory Blocks”. Again, focus on the address below. This particular address represents the Assembly Working Address for pointer 12. 40. Now that the tags are created execute the OPC quick client as illustrated in step 33.
RUI/Gateway & Modbus® TCP Configuration & Programming Example Using KEPServerEX 4.0 42. Lastly, in the screen shot below, notice that the 12th pointer has indeed been changed to Idle Set Point (circle) and the tag created to reflect this (arrow) shows the current Idle Set Point for PM1. Compare this to the default assembly found in step 37 above.
