Chapter Three
Configuration
Getting Started
Perform these steps;
1.Connect the
2.Wire the temperature controllers to the gateway’s
3.Wire a
4.Configure each controller to the same baud rate (9600 or 19200) from the front panel of the controller. Set each controller’s Modbus address to a unique number. As an example, set the first controller to address 1, the second to address 2 and so on.
5.Power up the gateway, controllers and PC.
6.Start your Internet browser. Enter the TCP/IP address of the gateway into the browsers’ address field. Two different addresses may be used to access the gateway. Either EMxxxxxx, where xxxxxx is the first six digits of the serial number, or WATxxxxxx, where xxxxxx is the last six digits of the gateways’ MAC address. The MAC address is printed on a decal in the form xx:xx:xx:xx:xx:xx.
7.Select the Gateway Setup Page. Enter User name ‘new’ and Password ‘user’ by default. The Password can be changed on the Security Configuration screen.
8.Configure the Baud Rate and range of controllers’ addresses to match those you configured in step four.
9.Click on Rescan Modbus Network
10.Click on the back button of the browser to return to the previous page.
11.Click on the refresh button of the browser and your controllers’ information should now be visible.
Note: You must click on the refresh button within the browser to capture the latest controller information. This information is automatically refreshed after 10 seconds by default. You may change this refresh time using the appropriate page.
Network Services
The
The gateway does support DNS client and Netbios name resolution. Configuration information may be entered at the EM Gateway Network Display Setup page.
Email Alarm Notification
The email function allows the user to send emails to four addresses alerting them of alarm conditions that have occurred on the controllers connected to the Gateway. A button on the Graphical User Interface (GUI) allows the user to enable or disable this feature. Emails can be generated whenever an alarm condition occurs for each controller. An email acknowledge feature requires that the user acknowledge the email message by operating the email acknowledge button before additional email alarm messages can be generated for that controller. For multiloop controllers only one email acknowledge feature is supported; if more than one loop produces an alarm, only the first alarm detected will generate an email until acknowledged.
8