Upon logging onto the upgraded WorldView, you may notice that certain buttons are greyed out such as acknowledge, block, unblock, etc. This indicates that the alarms are already acknowledged. During the initial configuration, you may have set them to a priority that auto acknowledges which is the reason for the buttons being greyed out. Basically, they can’t be acknowledged because they already have been. Change the setting for the alarm priority higher to 4 for example. In the screenshot below you can see the red background on the date for the alarms that have not been acknowledged and when you select an alarm the buttons are no longer greyed out.
Patch/Fix for VMS Operating System Related to Server Date/Time *May* be Required
If your organization is running HP VMS version 831H1I, following your next reboot, the server may appear to be hung-up. If this occurs, the server is not hung-up but rather waiting for manual input via iLo console to enter the current date and time.
This VMS O/S date check occurs every five (5) years requiring manual patching/fixing to resolve. QEI customer service staff can remote to your SCADA network and access the server’s iLo console to apply a fix and get the affected server back in operation in minutes. The fix would be applied to all of your SCADA masters as well.
To check your VMS version, at a DECTERM/PUTTY/TELNET session prompt, type PRODUCT SHOW HISTORY. If we haven’t already applied the fix at your organization, contact QEI customer service and we’ll be happy to apply the fix expeditiously.
With ConfigWiz 2, you can create a list of IP addresses for RTUs to avoid having to type
them out each time you need to read or write.
With ConfigWiz 2 open, select Tools, then IP Addresses.
You’ll see the following pop-up window where you can Add and Modify IP addresses.
A useful tip you may find easier is to initially add an IP address, then click Save and Close, where you will be directed to save your IP address list text file. Once that issaved, locate the text file and you can edit that file to add your addresses directly via Notepad.
Note to keep the same format:
Lastly, you will need to close down ConfigWiz 2 and reopen if you are modifying this
text file with ConfigWiz 2 open.
If you require data for specific time periods from your SQL database using a script can help narrow your search and provide preferential data based on your requirements. Extracting this information from a properly written script allows the customer flexibility while using a comprehensive method of gathering essential data from an SQL table.
The script below allows you to pull data from your History tables (you can replace History with any other tables e.g. Event etc.) This script uses Date/Time parameters (in ascending order). Modifying the dates to your preference will allow you to extract the information required from your query.
Whether you have a 6CPP6 or a an ePAQ 94xx and are using IP communications, there are helpful tools available.
Connect to your RTU via the RTU’s IP address using an SSH connection for an ePAQ 94xx device or use the Test
Panel and NETDIAG command on a 6CPP6. The following are some of the most useful commands available to use
for troubleshooting IP network communications from your Master or to your IED devices.
PING is essentially a ‘hello’ to a device. Pinging an IP like the example below can help determine if a device is
reachable via the network. Keep in mind, some devices like SEL RTAC’s usually have ping disabled by default. So,
if you ping, and it does not respond, that does not mean there is bad network path to the unit.
PING 192.168.0.70 (192.168.0.70): 56 data bytes
64 bytes from 192.168.0.70: icmp_seq=0 ttl=255 time=4.4 ms
64 bytes from 192.168.0.70: icmp_seq=1 ttl=255 time=1.9 ms
64 bytes from 192.168.0.70: icmp_seq=2 ttl=255 time=1.8 ms
64 bytes from 192.168.0.70: icmp_seq=3 ttl=255 time=1.9 ms
Another helpful command is the netstat command. Netstat will tell you which sockets are connected and listening.
This can be useful in finding out if devices have successfully made a connection with the RTU and what IP address
the RTU sees them as, as well as the port being used for that connection.
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 2 0 192.168.0.100:10000 220.127.116.11:1523 ESTABLISHED
tcp 0 0 127.0.0.1:57224 127.0.0.1:1024 ESTABLISHED
tcp 8 0 127.0.0.1:1024 127.0.0.1:57224 ESTABLISHED
Active UNIX domain sockets (w/o servers)
Proto RefCnt Flags Type State I-Node Path
For more commands or assistance refer to the 6NIA manuals (6NIA1 - UG-1040 or 6NIA2 - UG-1079) or contact
QEI Customer Service for further assistance.
The 0 at the end of the command is to stop the scan.
The 1 at the end of the command is to start the scan.
Typically, it is best to type it out with the 0 first then change the 0 to a 1 so you can use the up arrow to get back
to the 0 line and stop the scan rather than trying to type the whole command real quick while the scan is
You can also open a second decterm session and type the command with the 0 to stop the scan.
SCANMON DNPS03 0 0 <-- 03 IS THE COMM LINE NUMBER SCANMON DNPS03 0 1
SCANMON TCPSW 03 0 <-- 03 IS THE COMM LINE NUMBER SCANMON TCPSW 03 1
SCDUMP 03 <-- dump of real time commline point info rather than ongoing traffic monitoring
The first step when a communication channel is down, once the physical connections have been checked for proper connection, is to rebuild the comm line in Plus Editors. In Plus Editors, once logged in, download database by clicking “dBget”, go to Point Data/Comm. Find the appropriate comm line, at the bottom right of the screen find the “rebuild” and “delete” button. Always delete the comm line first, this action does not delete the comm line but stops it and allows to initiate a proper restart. After clicking “delete” click the “rebuild” button to properly restart the comm line.
There are occasions when you will need to connect to read or write a file at the device. This method is very simple to do. First you will need a DB9 to USB converter with a RS232 M/F cable. QEI recommends using the Tripp Lite Keyspan Model: USA-19HS.
If this is the first time using the dongle you will need to allow the device to load the correct drivers. Once you are connected properly you will see a green light blink on the dongle. This indicates that you are ready to connect. Next you will have to check what COM port the dongle is connected to. To do this go to the Device
Manager in the control panel. If the drivers have been successfully installed you will see the device under the Port column.
Now you are ready to connect the RS232 cable to your device. If you are using a 6CPP6 board connect the RS232 cable to Port 3. If you are using an ePAQ 9100 connect to the maintenance port on the front panel. Using ConfigWiz 1 you can read/write a file. Once you are ready to read/write a file select File on the top tool bar. This will open up a menu and you will be able to select the operation you want to perform. Remember you need to select the correct port.
If you have lost your IP address many of the QEI RTUs can be used in safe mode to quickly recover your
ConfigWiz files. These include 6ACP6 boards, ePAQs, DIOs, and the MicroPAQ. Having your unit in safe mode
should only be used for recovery and reconfiguration only. Once the unit is in safe mode you will not see a
heartbeat. To get your device into safe mode find the proper dip switch by using the diagrams listed below and
move it into the correct position. You will then need to power cycle your device and give it a few seconds to boot
back up. Make sure your laptop or computer is on the same network (example IP address 192.168.1.200 subnet
255.255.255.0). Now your device will have an IP address of 192.168.1.199 except for the DIO that is 192.168.0.95. Once you have recovered your lost IP address and/or written you configuration file from the device simply put the dip switch back to its normal position and power cycle.
ePAQ Dip Switch
6ACP6 Dip Switch
DIO Dip Switch
Below is an easy method to verify your port communication using HyperTerminal, Putty, or Tera Term.
1. Open a session using Hyper Terminal, Putty, or Tera Term.
2. Make sure you are in a test panel. If you are using ConfigWiz2 you will already be in the test panel. If
you are using a device that uses Configwiz2 you will need to type testpanel.
3. Use the PRX command followed by the port number you would like to check.
4. Wait for the next poll on your device. If everything is polling correctly you will start to see the page fill
up in Hex strings.
5. Look for both > and < symbols after the port number. > is what the device is transmitting. < is what the device is receiving.
In the event of a template mismatch error, which could occur when you open an RTU file whose template does not match the one you have loaded currently in ConfigWiz 2 take the following steps to make sure you have the correct template loaded in ConfigWiz 2.
In nearly all cases, you are not going to want to upgrade the RTU file, so click the ‘No’ button which will temporarily use the template from the RTU file.
This will not automatically change the default template in ConfigWiz 2. If you know you will be working with this file often in the near future, you should make sure you extract/load the template attached to this RTU file. If you do not, the next time you open ConfigWiz 2, you will again receive the template mismatch error.
Extract the Template from the loaded RTU file by the following method:
• Select Tools from the top tool bar of ConfigWiz 2.
• Then select Extract Template
• A window will pop up, allowing you to save the template from the RTU file to your PC.
• Choose the Directory you normally save templates to. If you do not have a specific directory, we recommend using the ConfigWiz 2 folder which is normally located at;
• ‘C:\Program Files (x86)\QEI\ConfigWiz 2.0’. Alternatively, you can create a new folder within this Directory and name it Templates, and save the file there.
• Now that you have this template file, next choose ‘File’ from the top toolbar, then ‘Load Template’. Navigate to where you saved the template file, and select, then click ‘Open’.
This template is now loaded into ConfigWiz 2 and will be the default template used next time you open the program.
Alarm and station summaries should already be saved.
From the toolbar select view and then “Hotkey Map” as shown below.
At the “Function Keys” select an empty slot, in the example below F1 is chosen, then press the “Browse” button.
Select the map or station summary to be assigned and press open
Press the “OK” button to complete the task
Simply press the assigned hotkey to recall
The Test Panel is an excellent tool to assist the customer when troubleshooting communications issues between the RTU and IED’s or Master Station. Locally, a USB type A-B cable is needed to connect your PC or laptop to the maintenance port on the ePAQ. The Test Panel can also be remotely accessed over an Ethernet network.
When in the Test Panel, use the ‘prx’ command to monitor incoming and outgoing traffic. Type ‘prx’ followed by the Port Number of the IED/Master communications you wish to monitor. To find out what the port number is, open the configuration in ConfigWiz 2. With the configuration open, you can view the port number in the list, or tree, on the left side of the ConfigWiz 2 window.
You can also view the port numbers in the right side of the screen, selecting the Ports icon:
Once the port number is known, typing ‘prx 12’ for example to monitor the communications. ‘<’ indicates inbound traffic, ‘>’ indicates outbound. The data displayed will be raw data. So, you will need to understand the protocol to determine what the messages are, or you can contact QEI and we will assist with decoding these messages if needed.
Using the Test Panel and the ‘prx’ command, you can quickly determine if the RTU is sending out polls as expected, if the RTU is receiving polls from the Master, or if the IED is responding to polls from the RTU. Using this feature may help decrease troubleshooting time and point you in the right direction as to where your communications issues may lie.
EXAMPLE: Below are Incoming and Outgoing DNP3 communications:
Below is an easy method to check your port communication using HyperTerminal, Putty or Tera Term:
1. Open a session with connection type SSH, then enter the IP address and port number in Hyper Terminal, Putty, or Tera Term.
2. Make sure you are in a test panel. If you are using ConfigWiz you will already be in the test panel. If you are using a device that uses ConfigWiz2 you will need to type testpanel.
3. Use the PRX command followed by the port number you would like checked.
4. Wait for the next poll on your device. If everything is polling correctly you will start to see the page fill up in Hex strings.
5. Look for both > and < symbols after the port number. > is what the device is transmitting. < is what the device is receiving.
If you run into a character limit when filling out the PTName (Point Name) or Desc (Description) fields in ConfigWiz 1, remember that the Enforcement of QEI Naming may be enabled, limiting the amount of characters you can use. NOTE - that with QEI Naming enforced, you’re limited to 24 characters for the Description and 6 for Point Names.
To verify or change this option, in ConfigWiz 1, click File and the User Preferences. Uncheck the Enforce QEI Naming Convention under Display Configuration. Clearing this option will allow you to use up to 48 characters for both Description and Point Names.
a. From AutoCAD, turn off any layers you don’t want displayed in WorldView.
b. Save the image as a DXF file. DXF 12 or 13 are most compatible for import into WorldView.
c. From within WorldView while logged in as privileged, open a new map or a selected layer of an existing map.
d. Select File > Import > From DXF then select the DXF image you wish to import.
As a helpful hint, SCADA operators should remember to always acknowledge your alarms as they come in or as soon as possible once they’re in an alarm state. Not doing so will result in the alarm file filling up. It is very challenging and disruptive to clear up a filled-up alarm file after the fact.
An alarm file has a fixed amount of alarms that it can hold which is 4032. 1008 is the number of blocks and each block contain 4 records which is how you arrive at the 4032 number. You can view this number by issuing the below commands on your SCADA computer.
SCADAA> rptsiz (look for file # 63)
Your Master Station might also have alarm files that you cannot see as active despite the alarms being acknowledge. The only way to get rid of this is when the file is cleared. Issue the below commands and discover for yourself.
SCADAA> SD i64.image (takes you to the 164.image folder for itanium machines)
SCADAA>run I_ALMDMPSUM.EXE and/or
SCADAA>run I_ALMDUMP.EXE (will give the same date with a different precision)