Common tasks that may need to be configured:
1: Both the iFIX Client and SCADA node need to be correctly licensed and not running in DEMO mode. In iFIX demo mode networking is disabled.
2: Configure the Windows Hosts file for both the SCADA Node and the Client Node if using static IP addresses.
The Host file is located in the %SystemRoot%\System32\drivers\etc\hosts directory
- If using static IP addresses each machine should have the static IP address with the machine name.
- If machine name is different from SCADA Node/Client Node names you have to have duplicate entries in Hosts file using both the machine names and Node names on separate lines.
- You should be able to ping each way (from SCADA Node to Client Node and vise-versa) by Node Name/Machine Name/IP address. This will not work if you can't ping machines.
- Using static IP addresses is strongly recommended, but not mandatory.
- Use DHCP and a DNS server to resolve node names to IP addresses.
3: Avoid using reserved names (i.e. Fix, Fix32) for the Client Node Name and SCADA Node Name.
Client Node Configuration:
- On the Client Node you need to have the SCADA Node listed in the Remote Node list in the SCU in Configure|Networks|Remote Nodes.
- TCP/IP or NetBios needs to be selected.
- Dynamic Connections option should be unchecked.
- If you want to be able to see the Process Database and the Pictures residing on the SCADA Node you can map the PIC path to the SCADA or store local copies of the picture on the VIEW node, but you should NOT map the PDB path.
- When creating links on Client Screen you should see the name of the SCADA Node and all tags in the Process Database residing on this SCADA Node.
- SCADA support should NOT be enabled on a Client Node.
- Alarm Network Service needs to be enabled.
4: You will NOT need the name of the Process Database that resides on the SCADA node in your SCU.
5: SCADA Node Configuration:
- On the SCADA Node enable SCADA support in the SCU.
- Network support should be enabled using TCP/IP or NetBios.
- Alarm Network Service needs to be enabled.
6: Test Communication Between the SCADA and Client nodes:
- Create a new Client screen and add a datalink.
- In the expression editor select the node name of the Remote SCADA Node.
- You see tags from the PDB on the Remote SCADA Node. Select a tag and go to Run mode to see if you get a value in Client screen.
- Changing value on the SCADA Node should be reflected on the Client screen residing on Client node.
If still unable to configure Client Node use TCPtest.exe to troubleshoot further. This utility resides in the root directory of iFix (i.e. C:\Dynamics for iFix 3.5 and older; c:\Program Files\GE Fanuc\Proficy iFix for iFix 4.0 - 5.0; c:\Program Files (x86) \Proficy\Proficy iFix for iFix 5.8).
Scenario 1 (Forwards) SCADA to CLIENT connectivity
[SCADA1] tcptest /s /p2011
[CLIENT1] tcptest /c /rSCADA1 /P2011
Scenario 2 (Reverse) CLIENT to SCADA connectivity
[SCADA1] tcptest /c /rCLIENT1 /P2011
[CLIENT1] tcptest /s /P2011
7: Check for any activity on the Network that has recently changed,such an IP address or network card the communication issue may occurs after a reboot of the SCADA. Consider rebuilding the SCU for the node that is not communicating.
8: Run the NETDIAG diagnostic utility;. This utility resides in the root directory of iFIX. After launching the diagnostic utility select the Dump button to collect a NETDIAG.DAT file as run on each machine.
By default this file is saved in the C:\Program Files (x86)\Proficy\Proficy iFIX\APP directory and can be reviewed in Notepad.
9: Run TCPViEW for Windows
TCPView is a Windows program that will show you detailed listings of all TCP and UDP endpoints on your system, including the local and remote addresses and state of TCP connections.
TCPView provides a more informative and conveniently presented subset of the Netstat program that ships with Windows.
While running TCPVIEW - Go to view in the menu then change the update speed to 5 secs or paused to slow or stop the display down In options uncheck resolve the address to see both the local and remote addressing
Also select to show/display unresolved endpoints
Look for port 2010 on both machines
Next, select save - save the result as *.text file for each machine respectively
10: iFIX may be running as a service - to determine if Session Isolation is involved
- Run the Windows TASKMANAGER
- Select View from the menu options
- Choose the option to select columns
- Enable the checkbox beside Session ID
To determine the running sessionID select the Processes tab ( Anything running in Session 0 is running as a SERVICE)
11: Run the Wireshark Protocol Analyzer
Download the current stable Windows release of Wireshark at http://www.wireshark.org/download.html to the iFIX NODE where you will be performing the capture.
- Install Wireshark. Keep everything at their default selections.
During the install you will be asked to install WinPcap to which you will click the Install button.
Complete the install and run Wireshark.
- If the problem for which you are performing a capture can be triggered immediately or in the very near future (several minutes), move on to step 4. Performing a capture over a great length of time will involve configuring a rotational capture.
The first thing that needs to be done is to obtain a baseline capture for 10 minutes. This will tell us the approximate size the capture file will be over a 10 minute time period. Working with capture files over 100 MB in size can be slow and this is why a baseline is important. To perform a baseline capture, perform the following ...
- Choose the leftmost toolbar button "List the available capture interfaces.." to open a list of available capture interfaces (NIC cards) on your computer.
- Find the interface that your Proficy product is communicating on and hit the Start button. Wait 10 minutes, stop the capture, and note the file size of the resultant *.pcap file.
- With the knowledge you gained in step 3b above, you can approximate how many minutes it will take to reach a file size of about 100 MB. Also, based on your hard drive capacity, you will have an idea of how many 100 MB files you would like to capture before Wireshark rotates and replaces the very first capture with a new one.
- Choose the Capture menu>Options command. This opens the Capture Options dialog box. Make sure the Interface drop down box contains "Local" and that the correct interface card to perform the capture on is selected. In the "Capture Files" section, click the Browse button to select the location for your capture files and provide the initial capture file name. Click OK. Also, in this section, select the "Use Multiple Files" checkbox. Choose the "Next file every" checkbox that suites your needs; a new file based on file size or a new file based on time. Select the "Ring buffer with" checkbox and choose the maximum number of capture files before the oldest capture file is overwritten.
- Click the Start button. Move to step 5.
- Choose the leftmost toolbar button "List the available capture interfaces.." to open a list of available capture interfaces (NIC cards) on your computer. Find the interface that your Proficy product is communicating on and hit the Start button.
- When the problem presents itself, stop the capture by choosing Ctrl+E.