Há uma entrada no site da GE, que resume que existem 4 tipos de cabos para se comunicar com toda a gama de CLPs fabricados depois de 1990. (Além do cabo de conexão Ethernet padrão RJ45-RJ45)
Abaixo estão listados os ativos e o preço em abril de 2017:
IC690ACC901. ATIVO NA FORÇA DE VENDAS. (RS422 DB15 macho para RS232 DB9 para se comunicar com as portas da CPU 90-30)
IC200CBL001. ATIVO NA FORÇA DE VENDAS. (9 pinos M a DB9, RS-232. PAC & VersaMax.A cabo de extensão padrão de 9 pinos, direto aqui funciona. ( Station Manager on RX7i only))
IC200CBL500. ATIVO NA FORÇA DE VENDAS. (RJ-45 a DB9, RS-232. (NÃO Ethernet) VersaMax Micro)
IC693CBL316 ATIVO NA FORÇA DE VENDAS. [RJ-25/11 a DB9, RS-232. Encontrado nas CPUs RX3i IC695CPE305 e CPE310 e em algumas CPUs 90-30, também em módulos Ethernet e CPUs como ‘Portas do Gerenciador de Estação’. (NO SNP or RTU on Station Manager. ports )
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
3: Avoid using reserved names (i.e. Fix, Fix32) for the Client Node Name and SCADA Node Name.
Client Node Configuration:
4: You will NOT need the name of the Process Database that resides on the SCADA node in your SCU.
5: SCADA Node Configuration:
6: Test Communication Between the SCADA and Client nodes:
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.