Q1. I occasionally have problems getting the InSite web page to appear with all the alarm information. I get all the header information, but must reload (refresh) the page several times before the alarms appear. What can I do?
Q2. I cannot view the RTU on the InSite web browser.
Q3. The alarms do not show up on the Alarm Summary page.

Q1. Why is the alarm point for the power supply always in alarm?

WinSock errors and warnings are generated by Metago Manager to indicate various network events. In some cases, these may occur as a result of problems on your network and not with the WS3500 RTU, and will require additional network troubleshooting.

To assist with troubleshooting connection issues, the WinSock errors listed below summarize possible reasons for the inability to connect, or to maintain a connection.

Q1. The operation is canceled
Q2.The connection is aborted due to timeout or other failure
Q3. The connection is reset by remote side
Q4. The attempt to connect timed out
Q5. The connection is forcefully rejected

Q1. Why is the LED Wallboard not displaying the alarms correctly?

Q1 How do I change the IP, Router, and Netmask addresses on an RTU if I
don't have the Metago Manager software to do so, or do not have a LAN connection?

The Metago RTU is shipped with default parameters (i.e. TID, IP address, router, and netmask addresses). In order to connect the RTU to your network, you must change these parameters.
It is best to isolate the RTU from the network before doing the following steps. Therefore disconnect the LAN cable from the RTU and/or the modem line cable.

Listed below are two methods for changing the connection parameters: the Console Configuration utility and entering TL-1 messages. The easiest method to use is the Console Configuration utility mainly because it is menu driven and you do not have to have any TL-1 protocol knowledge. The Console Configuration utility is only available with firmware 3.01.18 or greater and the WS3500 must have the disk-on-a-chip CPU card. Usernames and password assume the defaults from the factory, but may have been changed by your administrator.

Console Configuration Utility

1. Power up the RTU.

2. Connect a standard RS-232 DB9 straight through serial cable to the COM 1 port of the RTU and the other end of the cable to your PC.

3. Start a PC terminal session on your PC (e.g. TeraTerm, Hyperterm, or the equivalent). The port settings depend on the PC or terminal. Typically the port settings are 8 data bits, no parity, one stop bit, no flow control, and a baud rate of 57600.

4. Hit the <Return> key until the login prompt appears.

5. Enter MTC (all uppercase) at the login in prompt and hit the <Return> key. The password prompt appears.

6. Enter the word shipping (all lowercase) at the password prompt and hit the <Return> key. The WS3500 Configuration Menu appears.

7. At the > prompt, enter the number of the option, in this case 2 for Modify Configuration and hit <Return>. The WS3500 Modify Configuration Menu appears.

8. Enter the number of the option you wish to modify and hit <Return>.

9. After you have finished modifying all the parameters, enter 9 to exit the configuration menu and return to the main menu.

10. Enter 8 to restart the RTU.

Entering TL-1 Commands

1. Power up the RTU.

2. Connect a standard RS-232 DB9 straight through serial cable to the CRAFT port of the RTU and the other end of the cable to your PC.

3. Start a PC terminal session on your PC (e.g. TeraTerm, Hyperterm, or the equivalent). The port settings are:

Port: COM1
Baud Rate: 57600
Data: 8 bit
Parity: None
Stop: 1 bit
Flow Control: None

4. Enter a semi-colon and press the <Return> key to verify you have a connection. A deny message should appear in the window, similar to the following:

RTU134 01-09-19 14:10:55
M DENY
ICNV
;
5. Change the default parameters, by entering the following TL1 commands into the emulator session on your PC, substituting the correct value for each parameter. A parameter is enclosed by the <> symbols. When entering the TL1 command, you do not enter the <> symbols. An optional parameter in the TL1 message is enclosed in [] brackets.

TL-1 Message Syntax

ACT-USER:[tid]:<uid>:<ctag>::<pid>;
SET-IP:[tid]::<ctag>::<ip_address>;
ADD-ROUTER:[tid]::<ctag>::<netmask,router_ip>;
SET-SID:[tid]::<ctag>::<new_sid>;
INIT-SYS:[tid]::<ctag>::1;

Example:

ACT-USER::MTC:dr::shipping;
SET-IP:::dr::172.16.6.135;
ADD-ROUTER:::dr::255.255.255.0,0.0.0.0;
SET-SID:::dr::CLGYABCAN1;
INIT-SYS:::dr::1;

Note: text entered through the Craft port cannot be backspaced or deleted. Enter a semi-colon to begin a new line if a typing error has been made.

If you require more information regarding the TL1 commands, refer to the Metago Supported TL1 Messages manual that is shipped with each Main Metago RTU.

RTU134 01-09-19 14:10:55
M DENY
ICNV
;
4. Enter the Retrieve IP TL-1 command. The RTU should respond with the IP addresses that are configured on the RTU. Following is an example of the command and a normal RTU response.

Input
RTRV-IP:::abc;

Response
RTU134 01-09-19 14:10:55
M abc COMPLD
"CONFIG IP ADDRESS = 172.16.6.130"
"CDPD IP ADDRESS = 0.0.0.0"
"MODEM IP ADDRESS = 0.0.0.0"

After connecting to the RTU, you must click on the Upload Config button to upload a copy of the database from the RTU to your PC.

Q4 I know I've made changes to the database, but when I check the RTU these changes are not there. What happened?

You forgot to download your changes to the RTU before you disconnected or exited out of Metago Manager.

The changes you make on your PC do not automatically get downloaded to the RTU, unless you click on the Download Config button in the RTU Configuration tab sheet.

Q5 I use to be able to connect to the RTU, but now I can't. What happened?

It is possible that the RTU's IP address is no longer unique. Follow these steps to first determine the RTU's IP address and then test for a duplicate IP address on your network.

Determine the RTU's IP Address

1. Connect a standard RS-232 DB9 straight through serial cable to the CRAFT port of the RTU and the other end of the cable to your PC.

2. Start a PC terminal emulator session on your PC (e.g. TeraTerm, Hyperterm, or the equivalent). The port settings depend on your PC or terminal. Typically the settings are:

Port: COM1
Baud Rate: 57600
Data: 8 bit
Parity: None
Stop: 1 bit
Flow Control: None

3. Enter a semi-colon and press the <Return > key to verify you have a connection. A deny message should appear in the window, similar to the following:

Response

RTU134 01-09-19 14:10:55
M DENY
ICNV
;
4. Enter the Retrieve IP TL-1 command. The RTU should respond with the IP addresses that are configured on the RTU. Following is an example of the command and a normal RTU response.
Input

RTRV-IP:::abc;

Response

RTU134 01-09-19 14:10:55
M abc COMPLD
"CONFIG IP ADDRESS = 172.16.6.130"
"CDPD IP ADDRESS = 0.0.0.0"
"MODEM IP ADDRESS = 0.0.0.0"
;
5. Note the IP ADDRESS in the COMPLD message and proceed to testing for a duplicate address.

Testing for a duplicate IP address

1. After using the steps above to determine the RTU's IP address, disconnect the RTU from the network.

2. From a PC that is connected to the network, go to a DOS prompt, and enter the following command:

DOS command syntax:

ping <IP address of the RTU>

Example:

ping 172.16.6.132

Successful replies indicate there is another device on your network with the same IP address.
It is also possible that a network router has been reconfigured, which could be inadvertently blocking access to the RTU. Check with your network or IT group to determine if any changes affecting your subnet or specific IP address have been made.

Q6 I've configured the modem IP address, router address, and dial-out number, but I still can't connect to the RTU via the modem. Why not?

In addition to configuring the communication parameters for the modem, you must also enable the modem. There is an Enable Modem check box on the Communications tab sheet in Metago Manager.

Q1 Occasionally I have problems getting the InSite web page to appear with all the alarm information. I get all the header information, but must reload (refresh) the page several times before the alarms appear. What can I do?

This problem seems to be related to the browser cache. To disable the browser cache in Internet Explorer 5, do the following:

1. On the Tools menu in Internet Explorer, click Internet Options.

2. On the General tab, click Settings.

3. Select Every visit to the page and OK the Settings dialog box.

4. Back in the General tab, click Delete Files to delete all the files in the Temporary Internet Files folder.

Q2 I cannot view the RTU on the InSite web browser.

To have access to the WS3500 Metago InSite web browser, you must have purchased the WS3500 Metago InSite software license (Part Number 567-T067).

If you have the license, you must have enabled the InSite option when you downloaded the configuration to the RTU. The InSite option is found on the RTU Configuration tab sheet in Metago Manager.

Q3 The alarms do not show up on the Alarm Summary page.

For points to show up on the Alarm Summary page, they must be enabled, have a priority of critical, major, minor, or routine and actually be in alarm. You can quickly check the point definition on InSite by accessing the appropriate point definition page.

Q1 Why is the alarm point for the power supply always in alarm?

Ensure that the jumper (JMP1) on the power supply is jumpered to the normally open position.

Q1 The operation is canceled.

This WinSock error will occur if a "blocking socket call" (communication scheme used by Metago Manager) is interrupted unexpectedly.

If this error occurs, disconnect and reset the RTU, and then re-connect and retry the operation.

Q2 The connection is aborted due to timeout or other failure.

You may receive this error message for the following reasons:

1. The connection to the RTU is lost unexpectedly. The RTU may have rebooted, lost power, or the network cable became disconnected. Verify that the RTU is running and all the cables are properly connected.

2. There may be a duplicate IP address on your network. Disconnect the RTU from the network and then issue a ping command. If a reply message is displayed, this indicates another device on your network has the same IP Address as the RTU.

Q3 The connection is reset by remote side.

This error will occur if the connection to the RTU is explicitly dropped by the RTU. This may occur if data has been lost and the RTU determines that the connection is no longer viable for data transfer.

This error may also be caused by a malfunction of the RTU's operating system.
If this error occurs, disconnect and reset the RTU, and then re-connect and retry the operation.

Q4 The attempt to connect timed out.

You may receive the Timeout on Connection Attempt error message for the following reasons:

1. The RTU is not powered up. Ensure that the RTU is powered up. The +5v and -48v LEDs should be illuminated. The RUN LED should be flashing.

2. The RTU is not physically connected to the LAN. If the RTU is connected to the LAN, the ACT and LNK LEDs should be illuminated and flashing.

3. You have inadvertently typed in an incorrect IP address for the RTU you are attempting to connect to. Double-check to make sure the IP Address entered in Metago Manager is the same IP Address configured on the RTU.

Q5 The connection is forcefully rejected.

You may receive the "Connection is Forcefully Rejected" error message for the following reasons:

1. Someone is already connected to the upgrade port. Check to make sure no one else is connected to the RTU via Metago Manager. If there is, have that person disconnect from the RTU and wait for the RTU to reboot before you attempt to connect to it again.

2. If the connection was lost, the router may still be holding a connection to the RTU. In this case, you can either reset the port on the router or reset the RTU. To reset the RTU, you can

(a) Connect to the RTU via a TCP/IP connection or directly to the Craft port. Log on to the RTU with a user account that has a permission level of 5 and then issue the Init System command. Following is an example of the TL1 commands and the normal response to the commands.

Input
act-user::MTC:ct::shipping;

Response
RTU130 02-02-14 14:23:26
M ct COMPLD;

Input
init-sys:::ct::1;

Response
RTU130 02-02-14 14:23:50
M ct COMPLD
;
Note: Wait for the RTU to reboot before attempting to connect to it again.

(b) Press the Reset button on the front of the RTU. Then wait for the RTU to reboot before attempting to connect to it again.

3. The upgrade port in Metago Manager may be incorrect. Double check to make sure that the upgrade port entered in Metago Manager is the same as that configured on the RTU.

Q1 Why is the LED Wallboard not displaying the alarms correctly?

In order for the RTU to display the alarms, you must have previously configured the RS-422/-485 port on the RTU for the LED Wallboard. Also, the LED wallboard must be connected to the port on the RTU prior to powering up the RTU.

Configure the RS-422/-485 port, by doing the following:

1. Access the Metago Setup utility.

2. Connect to the RTU.

3. Click on the RS422/485 Port tab.

4. Click on the pull-down menu button for the port in question and select LED Display from the list.

5. Click on the Settings button and configure the port for 7 bits, Even parity, 2 stop bits, and a baud rate of 9600.

6. Click on the Upgrade Config button to download the new configuration to the RTU.

7. Click on the Reset button to reset the RTU.

8. Exit the Metago Setup utility.