IFIX System Configuration Guide

To help System Engineers and pre-sales service engineers better use iFIX and its components to configure enterprise-level systems, this document provides detailed descriptions and examples in various aspects, for reference by project personnel. This document covers the following topics: Device connection, iFIX function module selection, database design, network design, enterprise information system and resource scheduling system integration, and redundant system design.
 
 
Chapter 1 device connection
 
Device connection is the primary problem to be solved by a factory Data Collection System. iFIX can provide convenient connection methods with various well-known devices in the world, at the same time, the development kit of the communication program is provided so that users can connect their own non-standard devices to the iFIX monitoring system. The following are several aspects.
 
1. Connection Device Type:
 
IFIX can be connected to many types of devices, including: DCs, PLC, controller, remote module, Field Bus equipment, bar code reader, intelligent instrument, weighing instrument, other computer systems or special equipment.
 
2. Connection method:
 
IFIX and devices can be connected through a serial port, an industrial network, or a standard Ethernet connection. Other methods include dialing, microwave devices, and radio transmission, leased line connection.
 
3. iFIX driver used:
 
IFIX drivers are divided into 6.x and 7.x based on different development tools.
 
6. x drivers are developed using the driver development kit Itk and can run on Windows 95/98 and Windows NT. 6. x versions of drivers support running 8 different drivers simultaneously on the same PC to connect 8 different devices. The built-in redundancy function of the driver. For details, see the description of the redundancy system.
 
7. x drivers are developed using asdk or osdk (OPC Toolkit) and can only run on Windows NT platform. The 7.x Driver provides the OLE Automation interface, which can run independently from iFIX and reference its attributes and methods in the vbprogram. This driver uses the COM/DCOM technology and can be installed and run in a C/S structure. You can remotely control the network. For example, you can install the client on the iclient, control the running of the server through the network, configure the remote driver, and control the running and status diagnosis. The 7.x driver supports the definition of an infinite device connection channel. Most of the 7.x drivers are also OPC servers and can be connected to standard OPC clients.
 
Intellution Io driver list
See http://www.intellution.com/products/fixiodrivers/
4. Use third-party drivers and OPC Server
 
Intellution has a large number of automation partners (CAP) who write a large number of commercialized drivers and OPC servers for iFIX in their projects. For more information, see the following URL:
 
For a list of third-party OPC drivers, see:
Www.softwarw.lbox.com
Www.matrikon.com
 
For a list of Intellution cap drivers, see:
Http://www.caro.net/dsi/
Http://www.sarla.com/
Http://www.novotek.com/
 
For more information, contact the Intellution office.
 
5. Example of device connection method classification:
 
PLC-AB:
 
IFIX has multiple Connection Methods for the AB PLC driver, which are described as follows:
 
ABH: it is easy to use a serial port to connect to the AB dh + network, but the speed is limited by the serial port. No other AB software or hardware is required. Driver version: 6.x
 
ABR: It is widely used. It supports kt, KTC, KTX, ktxd of AB, communication between Ethernet Card and PLC, and rslinx of AB. This software can be purchased from AB or ordered from Intellution. Note: rslinx Lite version is not available. The required rslinx version is rslinx for Windows NT and 95 v2.00.97.30 or later. The OEM version is also available.
 
Main supported PLC types include: PLC-2, PLC-3, PLC-5/250, SLC 5, micrologix 1761-l10bwa and 1761-l20bwa-5a PLCs. For more information, see the driver manual. Note that the micrologix PLC is supported only when the abr I/O driver version is 6.51 or later.
 
Field Application: Dow Corning, shikou No. 1 plant, yan'an East Road Tunnel, Shanghai
 
Abe: rarely used. AB plc is connected over Ethernet, but it must be supported by AB interchange software.
 
Abo: a third-party OPC server, which can be directly connected to the OPC client of iFIX. However, rslinx of AB is also required. Developed by matrikon Systems, Inc. See http://www.matrikon.com for details
 
 
PLC-modicon:
 
Mb1: it has two versions, 6.x and 7.x. It connects to all devices that support ModBus serial communication protocol through a serial port. It mainly includes modicon PLC and other control instruments such as Honeywell UDC, UMC, and Moore control instruments. Supports the mobus RTU and ASCII communication protocols. When using it to communicate with other compatible devices, note that the data type is different from the Data Type of modicon. V7.x supports dialing and radio connections.
 
Field Application: Wenzhou Power Plant and Yangzi Petrochemical Thermal Power Plant
 
MMP: v6.x, supporting connection to modicon PLC through Modbus plus network. Supports dual sa85 NICs, and 984 series and quantum series PLC. Support Win95 and NT, support NIC: sa85, sm85, At-984, MC-984.
 
On-site application: Hong Kong Power Company, Shanghai Wujing thermal power plant, and Jiaxing Power Plant
 
MBE: connects to the modicon Ethernet communication module through a standard Ethernet Card.
 
 
PLC-Siemens:
 
SIE: connects to the serial communication module cp525 of SIEMENS S5 PLC through a serial port. Supports the 3964R protocol and other Siemens devices that support this protocol.
 
S_7: three methods are supported to connect the Siemens S7 PLC series, namely, PROFIBUS (L2), Industrial Ethernet (H1), and standard Ethernet (TCPIP ). The three connection methods are described as follows:
PROFIBUS: supports the FMS and MPI protocols.
Required PC hardware: CP 5412-a2 PC board for Profibus
Required Siemens software: S7-5412/Windows NT version 1.10 or later
Communication Module on PLC: CP-343-5, CP-443-5 ext
It can be directly connected to the MPI communication port of the PLC.
 
Industrial Ethernet (H1 ):
Required PC hardware: CP 1413 PC board for Ethernet
Siemens software required: S7-1413/Windows NT version 1.10 or later
 
Standard Ethernet (TCPIP ):
Required PC hardware: 3-com etherlink III card-Ethernet
Required Siemens software: softnet S7 for Industrial Ethernet/Windows NT
 
Other Siemens software for diagnosing and configuring S7 PLC:
Pg/PC interface software configuration release 4.0.7.4, 153
Step 7 Software Version v3.02
 
On-site application: Unilever toothpaste and Baosteel Steel Pipe Company
 
Sl4: 7.x driver, which connects SIEMENS S5, S7, AND Ti series PLC over Ethernet from Layer 4-ISO Transport Layer of Siemens network.
S5: supports 115u, 135u, and 155u, and cp143 or cp1430 communication modules.
S7: supports 300 and 400 series PLC, but does not support CP443-TCP modules.
Ti: supports 545, 555, 560, and 565 series, and cp1434tf communication modules.
Standard Ethernet Card: 3Com
 
S7 200 PPI: third-party OPC Server Driver, supplier softwarw.lbox, support S7-212, S7-214, S7-215, S7-216 or above. Supports single master Multidrop RS485 mode and dial-up connection.
 
Note: S7 200 series PLC supports free-form protocol communication. You can define a communication program on the PLC end through software programming and use standard protocols, such as Modbus, then use the corresponding driver on the iFIX side.
 
PLC-Mitsubishi
 
MIT: 6.x driver. It uses Mitsubishi protocol format one to connect to a series PLC through serial port. It supports the CPU types Ana, Ann, ANS, And Anu. Supported platforms of 95/98/NT, and supported Mitsubishi communication cards include a1sj71c24, aj71c24, and aj71uc24.
 
On-site application: Shanghai Suntory beer
 
MIE: 6.x driver, Ethernet TCPIP connection melsec-a PLC, support melsec plc cpu type: Ann/ANS, Ana, ANS, Anu, use melsec Nic aj71e71 communication. Supports Win95, 98, and NT platforms.
 
Mitsubishi FX net DRIVER: third-party OPC server, vendor softwarrentlbox, supports all FX, fx2c, fx0n series, supports FX net RS-485 Multidrop connection. A dial-up connection is available and can be run independently.
 
MEL: Support for Mitsubishi melsecnet 10 optical fiber network connection, which is under debugging.
 
PLC-OMRON
 
OMR: drivers of version 6.x are connected to OMRON host link through serial ports. The Win95/98/NT platform supports C series, CV series, P series, and K Series.
 
OMF: 6.x driver, which connects various OMRON PLCs through OMRON's finsgateway. Supported connection methods include: OMRON Controller Link Units (OMRON Controller Link Support Board # rj8f5-clk21 must be used) OMRON Ethernet unit (using standard Ethernet), OMRON sysmac Link Units (must use OMRON sysmac Link Board #4158f5-slk21), OMRON sysmac net link unit (must use OMRON sysmac Link Board #4258f5-slk21) and communicate with C series and CV series PLC through serial connection. Support for OMRON finsgateway 2.1 is required, and only the WINNT platform is supported.
 
Note: If you use different finsgateway connection methods, you must install different content, as shown in figure
Clk_unit0 version 2.1 must be installed for Controller Link; etn_unit version 2.1 must be installed for Ethernet; sysmaclink version 2.1 must be installed for sysmac link; serial_unit version 2.1 must be installed for serial interface.
 
On-site applications: Rainbow NEC and SEG Hitachi
 
PLC-Ge
 
Ge6: Use the ccm2 protocol of GE to communicate with various PLC of Ge. The supported operating system platforms are Win95, 98, and NT. The PLC types include: 9030/9070 series (through the cmk711 communication processor) and 1 Series (connected to the DCU port) series 5 (connected to the CCM port), Series 6 (connected to the CCM or ioccm module ). 6.x, serial port connection.
 
The logicmaster 5 software is required to set the PLC site number. The master-slave protocol of Ge is supported.
 
G90: Use the ge snp protocol to communicate with the GE Series 90 PLC. 6. x version, serial port connection, supported by Win95/98/NT platform. The communication efficiency of this protocol is higher than that of ccm2.
 
Ge9: connects to ge 9030/9070 PLC over Ethernet. The driver of version 7.x only supports the NT platform and standard Ethernet Card. However, GE Ethernet configuration software is required, for example, to connect to ge 9070 PLC,
The GE Fanuc Series 90-70 TCP/IP Ethernet software (part No: ic651ens042a) is required to configure the Ethernet communication module of the PLC. If the 9030 PLC is connected, requires 90-30/20 S series software packages (part No: ic641swp306l)
 
Gio: connects to the Ge-genius network and uses the GE Fanuc pcim (single-slot PC interface module) card. Model: ic660elb922/ic660elb921/ic660elb906. Supported devices include series 5, 6, & 90-70 devices: datagrams; Series 90-30: global data; genius I/O blocks. The corresponding pcim configuration software driver Nic is required. 6. x, supported by the Win95/98/NT platform.
 
 
DCs-Fisher rosemount
 
RNI: a third-party driver. The TCPIP is used to connect the Fisher rosemount RS/3 system. The supplier is matrikon, 7.x OPC server, and the rni api of rosemount is required for Windows NT software, the rosemount RNI version 2.x gateway software is required. Only the NT platform is supported. We recommend that you use the NT server.
 
DCs-YOKOGAWA
 
CNT: uses a serial port to connect to the yokogawa centum dcs, a third-party driver, and the cgwu-2 RS232 communication module on the DCS. The supplier is the Sarla technologies, 6.x version drive, and supports the Win95/98/NT platform.
 
CEN: connect to the V-Net & E-net of the yokogawa centum cs system over Ethernet. The acg10s Ethernet communication gateway device of YOKOGAWA is required. standard Ethernet nic and tcpip can be used on the computer side. 6. x version, supporting Win95/NT. Third-party driver, supplier: Sarla technologies.
 
DCs-Honeywell
 
TDC: a serial port connects to the TDC 2000/3000 device and communicates with Honeywell's personal computer serial interface (pcsi) unit. Third-party drivers, suppliers: Digital Systems, Inc., 6.x drivers, Win95/NT supported.
 
DCs-Foxboro
 
FIA: connects to the Foxboro Ia system through Ethernet tcpip. The third-party driver is provided by matrikon Systems, Inc. and supports Win95/NT.
 
DCs-Moore APACS
 
Retrial: connects Moore's APACS in multiple ways, and supports 3Com ethernet card and Moore's RNI/Nim M-Bus card. Moore MS Windows NT 32-bit Runtime API (P/N 15939n656v4. 03) is required for configuring APACS M-BUS and Ethernet. 6. x driver, NT platform.
 
Field Application: Guangdong Huangpu Power Plant
 
DCs-Bailey
 
CIU: serial port connection Bailey Infi-90 or net-90 DCS, DCS Communication card for Bailey net-90 ciu02, Bailey net-90 ciu03 and Bailey Infi-90 ciu04. Third-party driver, supplier: SE-ACE innovations, inc., 6.x driver, support Win95/NT.
 
Ops: Serial Port connected to Bailey Infi-90 or net-90 DCs, the supported communication modules are ciu02, ciu03, ciu04, ici01, inpci02. It has an OPC interface and supports all Bailey DCS data types and functional blocks. A third-party driver. The supplier is previse Inc. and must be purchased with the opscon system. This system can replace the Bailey DCS operating station. All data fully complies with OPC standards. For details, see the description of iFIX third-party components.
 
DCs-Westinghouse
 
WDP: connects the wdpf DCS System of Westinghouse through a serial port. It supports the SIU communication module of DCS and third-party drivers. Suppliers: FM Systems, Inc., 6.x drivers, and Win95/NT drivers.
 
Controller-Fisher remote operations Controller
 
ROC: supports Fisher ROC 300 series (306,312, and 364) and 407 (floboss), and supports multiple connection modes: direct connection, multi-drop (422/485), Telephone Dialing, wireless communication. V5.x supports the Win95/NT platform. Provides advanced diagnosis, alarm and event information routing, and event trigger report.
 
Controller-Foxboro 760,761,762 Loop Controller
 
Fb7: Use Serial Port to connect Foxboro 760,761 C, 743c, 762c, 743cb controller, use RS-232 to RS-485 converter or RS-485 port card. Third-party drivers, suppliers: FM Systems, Inc., 6.x drivers, Win95/NT supported.
 
BEL: connect Foxboro 761 series controller using serial port, use RS-232 to RS-485 converter. Third-party drivers, suppliers: Sarla technologies (P) Ltd., 6.x drivers, support for Win95/NT.
 
Controller-Honeywell/EIM 620 (s9000)
 
EIM: Ethernet mode, supports 620-12, 620-1633, 620-36, s9100e, UDC 9000, logic controller, controller communication module support: EIM 620-0089 Ethernet module and elpm 620-0073 Ethernet module. With TCPIP, Ethernet connections support 10 base2 coaxial cables or 10 base5 AuI coarse cables. 6. x driver, supporting Win95/NT.
 
On-site application: Shanghai Wujing Chemical Plant
 
Controller-Honeywell UDC
 
UDC: the serial port connects to the UDC controller, supports rs422/485 communication options, 6.x driver, and Win95/NT.
 
Controller-Moore series controller
 
M32: Serial Port connected to the Moore controller. Supported types: mycro 351, 352, 353, 382. Connect various controllers through mycro 320 independent computer interface (ICI. 7. x driver, NT platform.
Note: The ROM in 320 must be BBA, not BCA.
 
Controller-opto22 mistic
 
OPM: Version 6.x, NT platform, m4rtu controller and mistic controller. connection modes include ARCNET, Ethernet, and serial port. Optocontrol V2.1 API software support is required.
 
Field Application: Baosteel roll Company
 
Controller-ABB Kent Taylor mod 31
 
A30: 7.x, NT platform, supporting ABB devices: 1701j recorder, 1701n, 1702r, 1703r, 1711r, 2002n base unit, 2002 p regulatory control ID, supported communication card: 1720n communication link for ICN, 1733n Model A-mini link for ICN. ABB's PC-30 software is required to configure ABB devices.
 
Other famous devices:
 
AD5: Alibaba Cloud Adam 5000 Series Data Collection Module driver, 6.x, third-party driver, supplier: Sarla technologies (p) Ltd .. Serial port connection: supports the Win95/NT platform and RS232/485 modes. Supported modules include 5017, 5018, 5024, 5051, 5056, and 5060.
 
DNP: a third-party driver that supports DNP v3.00 protocol level 2 subset definition and can be connected to all devices that comply with this Protocol, 6.x, 95/NT platform, supplier: triangle microworks, Inc .. Supports interrupt information, data records with time tags, and event sorting. Common devices using this Protocol are: bitronics, Inc. Alpha series meters; arga controls dm15/25 series meters; Harris d20 RTU; ABB dpu2000r relay; Siemens MJ-X voltage regulator. This Protocol is the RTU-IED device connection protocol recommended by the IEEE electrotechnical Association. There are commercial products in China, but only NT is supported.
 
Application site: Shanghai Light Rail Pearl Line Power Distribution Station
 
U51: connect the Fisher-rosemount model 1151 smart pressure transmitter through a serial port. It supports HART protocol, third-party development, and NT platform. The supplier is Digital Systems, Inc ..
 
Lni: A LonWorks driver developed by a third party. It supports any LonWorks network device and can use communication cards: pclta, PCNSS-10, and slta. We need Echelon software, pclta. sys & ldv32.dll for NT, ldvpclta. sys & wldv. dll or ldvslta. sys & wldv. DLL for Win95. Supplier: Bach Systems, Inc ..
 
Field Application: Department of automation, Shanghai Jiao Tong University

This article from the csdn blog, reproduced please indicate the source: http://blog.csdn.net/ch_zh_80/archive/2006/08/28/1132436.aspx