...
- Control Center type
- Local Control Center (LCC)
In LCC, there are only data values that are transmitted to the partner centers. It means, that only the output I/O tags (Ao, Co, Dout) are relevant for this station. If the I/O tag value is changed, by the control objects, data are then published outward of D2000 System. In the opposite direction - to LCC, the values can be transmitted by the commands. These objects could be the input values (Ai, Ci, Di, Qi).
Exactly one station of LCC type must be configured on the line. - Remote Control Center (RCC)
In RCC, there are only data values that are transmitted form the partner centers to D2000 System. It means, that only the input I/O tag values (Ai, Ci, Di, Qi) are relevant for this station. The values of output I/O tags are transmitted as commands via RCC from D2000 System.
One or more stations of RCC type can be configured on the line.
- Domain
- For LCC - Local Domain
It is a domain name that executes Local Control Center for the remote client (center). The text string is max. 32 characters. It consists of alphanumeric characters ("a…z", "A…Z", and "0…9"), underscore ("_") or dollar sign ("$"). The first sign must be a letter. - For RCC - Remote Domain
It is a domain name that executes Remote Control Center for a local client (D2000). The text string is max. 32 characters. It consists of alphanumeric characters ("a…z", "A…Z", and "0…9"), underscore ("_") or dollar sign ("$"). The first sign must be a letter.
The Browse button, which is enabled only for RCC, enables (if a KOM process is running and if a communication is established) to obtain a list of domains from a remote control center. For browsing functionality to work, the remote control centre must support handling of getNameList request with parameter ObjectClass=DOMAIN.
- Remote Control Centre Parameters
Permitted only for RCC.- Initiate
It enables an active initiation of TCP connection to the remote control center. It means, D2000 System initiates this connection. - Role
The parameter Service Role belongs to Bilateral Table Agreement. It indicates the ICCP activity that is required for Remote Control Center - Client, Server, or Client & Server. The value is set according to an agreement with the partner local center. Usually, when enabling the parameter Initiate, you should set a pro-active communication, i.e. Client or Client & Server value.
If the Initiate parameter is on, a handler task is created for every RCC with Client or Client & Server role and connects to the ICCP server according to the line configuration.
If the Initiate parameter is off, the KOM process is waiting for ICCP client to connect, and according to the station's protocol parameters (TSEL, SSEL, PSEL, AP Title, AE Qualifier) is matching an ICCP client to a RCC with Server or Client & Server roles.
Kotva |
---|
| stanica_parametre |
---|
| stanica_parametre |
---|
|
Station protocol parameters
...
The identification of incoming client is executed according to all address parameters, i.e. TSEL, SSEL, PSEL, AP Title and AE Qualifier. If the connected ICCP client provides different address parameters than which do not match parameters configured on any RCC-type station configured in D2000 system, the connection is rejected.
Note 2Too much So many parameters needed for setting the "Data Set Transfer Set" can seem complicated. To set RBE (Report By Exception) parameter (i.e. the functionality of "Conformance Block" No. 2, "Extended Data Set Condition Monitoring") is, however, very important.
...