■ Software Input and Output
SEE ALSO
For details on software input and output, see the following:
A4, “Software Inputs/Outputs”
■ Various Types of Process I/O ¡ £
The I/O units used by process control stations vary with the FCS models, I/O module location, communication bus and so on.
● Process I/O of PFCS and SFCS ¡ £
PFCS and SFCS can connect the processor unit directly to the I/O module nests. Via the I/O modules installed in the nests, the control stations can communicate with the filed devices for process control.
● Process I/O of KFCS2 and KFCS £
KFCS2 and KFCS can connect FCU to the nodes using ESB bus (Extended Serial Backboard Bus), furthermore, connection can be established from the local nodes to remote nodes via ER bus (Enhanced Remote Bus).
Via the I/O modules installed in local nodes and remote nodes, the control station can communicate with the field devices for process control.
The following figure illustrates the connection of local nodes and remote nodes.
C
FCU: Field Control Unit PW3X, PSU: Power Supply Unit CP345: Processor Unit SB301,SB401: ESB Bus Interface Card IOM: Input/Output Module EB401, EB501: ER Bus Interface card
● FCS I/O Interfaces of LFCS2 and LFCS £
LFCS2 and LFCS can connect FCU to the nodes using RIO bus. Via the I/O modules installed in the nodes, the control station can communicate with the filed devices for pro-cess control.
● FCS I/O Interfaces of Migrated-FCS for FIO (RFCS5/RFCS2) £
RFCS5 and RFCS2 can connect FCU to the nodes using SI bus. Via the I/O modules (for the old version FCS) installed in the nodes, the control station can communicate with the filed devices for process control.
Moreover, like KFCS2 and KFCS, Migrated-FCS2 can connect to local nodes and remote nodes, via the I/O modules installed in local nodes and remote nodes, the control station can communicate with the field devices for process control.
SEE ALSO
For more information about the I/O cards regarding to SI bus, see the following:
A2.1, “Process I/O” in the instruction manual for Migrated-FCS (FIO) (IM 33Q01B41-01E)
■ Process I/O
Process I/O stands for the interface for the signal communication between Field devices and field control station. An FCS receives signals from field process detection devices and send control signals to field control devices.
SEE ALSO
For more information about process I/O, see the following:
A3, “Process Inputs/Outputs”
■ Communication I/O Modules ¡ £
Communication I/O modules are used for communicating with subsystems such as a PLC (Programmable Logic Controller) for exchanging the process data.
The following modules are available for FCS to communicate with subsystems.
• ACM11: RS-232C communication module (*1)
• ACM12: RS-422/RS-485 communication module (*1)
• ACM21: RS-232C communication card (*2)
• ACM22: RS-422/RS-485 communication card (*2)
• ACM71: Ethernet communication module (*2)
• ACP71: PROFIBUS communication module (*2)
• ALR111: RS-232C serial communication module (*3)
• ALR121: RS-422/RS-485 serial communication module (*3)
• AL E111: Ethernet communication module (*3)
• ALP111: PROFIBUS-DPV1 communication module (*3)
*1: ¡£ Applicable to PFCS, LFCS2, LFCS and SFCS
*2: ¡£ Applicable to Enhanced Type PFCS, SFCS
*3: ¡£ Applicable to KFCS2, KFCS
SEE ALSO
For more information about communication I/O modules, see the followings:
J2, “Communication I/O Module”
K2, “Communication I/O Module”
N2, “PROFIBUS-DP (ACP71)”
N3, “PROFIBUS-DP (ALP111)”
● ACM11: RS-232C Communication Module : PFCS/LFCS2/LFCS/SFCS
This is a module to communicate with a subsystem using RS-232C interface for exchang-ing process data. This module can be installed in (AMN33) communication module nest.
Besides, a subsystem communication package for this module is required.
● ACM12: RS-422/RS-485 Communication Module : PFCS/LFCS2/LFCS/
SFCS
This is a module to communicate with a subsystem using RS-422 or RS-485 interface for exchanging process data. This module can be installed in (AMN33) communication module nest.
Besides, a subsystem communication package for this module is required.
● ACM21: RS-232C Communication Card : Enhanced Type PFCS/SFCS
● ACM22: RS-422/RS-485 Communication Card : Enhanced Type PFCS/
SFCS
This is a module to communicate with a subsystem using RS-422 or RS-485 interface for exchanging process data. This module can be installed in (AMN51) communication module nest.
Besides, subsystem communication tasks created with FCS-C are required for this module.
● ACM71: Ethernet Communication Module : Enhanced Type PFCS/SFCS
This is a module to communicate with a subsystem using Ethernet interface for exchanging process data. This module can be installed in (AMN51) communication module nest.
Besides, a subsystem communication package for this module is required.
● ACP71: PROFIBUS Communication Module : Enhanced Type PFCS/SFCS
This is a module to communicate with the field devices connected on PROFIBUS-DP fieldbus for exchanging process data. This module can be installed in (AMN52) communi-cation module nest.
Besides, PROFIBUS Communication Package for this module is required.
● ALR111: Serial Communication Module (RS-232C) : KFCS2/KFCS £
ALR111 is a RS-232C module for communicating with subsystems. This module can be installed to a nest (ANB10S/D) of local node or a KFCS2 nest (ANR10S/D) of remote node.
Besides, a communication package is required when performing communication with subsystems.
● ALR121: Serial Communication Module (RS-422/RS485) : KFCS2/KFCS
£
ALR121 is a RS-422/RS-485 module for communicating with subsystems. This module can be installed to a nest (ANB10S/D) of local node or a KFCS2 nest (ANR10S/D) of remote node.
Besides, a communication package is required when performing communication with subsystems..
● ALE111: Ethernet Communication Module (RS-422/RS485) : KFCS2/KFCS
ALE111 is an Ethernet communicating module used for communicating with subsystems.
This module can be installed to a nest (ANB10S/D) of local node or a KFCS2 nest (ANR10S/D) of remote node.
Besides, a communication package is required when performing communication with subsystems.
● ALP111: PROFIBUS-DPV1 Communication Module : KFCS2/KFCS
This is a module to communicate with the field devices connected on PROFIBUS-DP/
DPV1 fieldbus for exchanging process data. This module can be installed to a nest (ANB10S/D) of local node.
Besides,PROFIBUS Communication Package for this module is required.
■ Fieldbus Inputs and Outputs ¡ £
The process data of field devices connected on fieldbus can be accessed via the fieldbus I/O.
A fieldbus communication I/O module can be applied for connecting FCS with fieldbus.
Besides, FOUNDATION fieldbus communication packages are required.
SEE ALSO
• For more information about PFCS/LFCS2/LFCS/SFCS Fieldbus I/O, see FOUNDATION fieldbus Tools (IM 33S05P10-01E)
• For more information about KFCS2/KFCS Fieldbus I/O, see the following:
FOUNDATION fieldbus Reference (IM 33Y05P10-01E)
● ACF11: Fieldbus Communication Module : PFCS/LFCS2/LFCS/SFCS
ACF111 is a module for communicating with Fieldbus devices. ACF111 can be installed in a communication module nest (AMN33). FCS is communicating with Fieldbus devices via the ACF111.
ACF111 has the following capabilities:
• Can be used as Link Active Scheduler (LAS) to manage the Fieldbus communication schedule.
• Can pass the data from FCS to field devices and vise versa.
• Can supply powers to the Fieldbus devices.
● ALF111: Fieldbus Communication Module : KFCS2/KFCS £
ALF111 is a module for communicating with Fieldbus devices. ALF111 can be installed in a local node or in a remote node. FCS is communicating with Fieldbus devices via the ALF111.
ALF111 has the following capabilities:
• Can be used as Link Active Scheduler (LAS) to manage the Fieldbus communication schedule.
• Can pass the data from FCS to field devices and vise versa.
■ Identifiers of Process Inputs/Outputs ¡ £
Process inputs/outputs are identified by element numbers assigned.
Since plant operation may require to identify all the I/O signals with unique names, so that all the I/O signals can be tagged or assigned with a user-defined label, thus as to assign a contact input or output with a tag name or to assign an analog input or output channel with a user-defined label.
TIP
From a SEBOL program, a Visual Basic program or a Windows application (other than CS 3000 HMI
● Format of Terminal Number : PFCS/LFCS2/LFCS/SFCS
▼ Terminal
A terminal of a process I/O or a Fieldbus I/O can be numbered in accordance with its physical position and the I/O module location.
The format of a terminal number is as follows.
%Znnusmm
%Z: Identifier of process I/O (Fixed) nn: 01 (Fixed) (*1) (*2)
Node Number (01 - 08) (*2) u : Unit Number (1 - 5) s : Slot Number (1 -4) mm: Terminal Number (01 - 32)
*1: ¡ In PFCS, nn is fixed as 01.
*2: £ In SFCS, nn is fixed as 01. In LFCS2 and LFCS, nn stands for node number (01 to 08).
IMPORTANT
When using Multipoint Control Analog I/O Module with signal conversion connector (AMC80/ZVM) , the following points need to be noted.
AMC80/ZVM is the Multipoint Control Analog I/O Module (AMC80) attached with a signal conversion connector (in which, the output is converted to 1 to 5 V DC, pin-assignment is rearranged).
The pin arrangement of AMC80/ZVM assigns the channels 1 to 8 for input and channel 9 to 16 for output; while on the AMC80 I/O builder, the odd number channels for input and the even number channels for output. The relations between the signal channels on AMC80 connector and on AMC80 I/O builder are shown as follows.
Channels
● Format of Terminal Number : KFCS2/KFCS £
▼ Terminal
A terminal of a process I/O or a Fieldbus I/O can be numbered in accordance with its physical position and the I/O module location.
The format of a terminal number is as follows.
%Znnusmm
%Z: Identifier of process I/O (Fixed) nn: Node Number (01 - 10)
If the database in KFCS2 is remote node expanded type, the range of node number becomes 01 to 15.
u : Unit Number (1 - 8)
s : For a Fieldbus communication module, s stands for segment number (1 -4).