Date: Fri, 29 Mar 2024 10:25:02 +0100 (CET)
Message-ID: <1472545712.111622.1711704302356@srvdoc.doc.ipesoft.com>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_111621_1373917741.1711704302356"
------=_Part_111621_1373917741.1711704302356
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Server protocols - general implementation rule=
s
Introduction=
Ope=
ration rules of servers protocols
Changes and modifications
Document revisions<=
/a>
Introduction
Since the version V7.0, D2000 system also supports some protocols, in wh=
ich the process D2000 KOM imp=
lements the server (slave) side. It is concerning the following protocols:<=
/p>
This document describes the general rules which are valid for output I/O tags (output tags=
for D2000 system, input ones for client). There are also "mixed" client-se=
rver protocols (IEC 87=
0-5-104 Server ,IEC 870-5=
-104, IEC 870-5-10=
4 Sinaut), which have two types of output I/O tags:
- 'client' output I/O tags - the same as for the other protocols,
- 'server' output I/O tags - their specifications are described in the do=
cument.
Operation rules of server pr=
otocols
- The values of 'server' output I/O tags are written also while the communication line / station fails, does not communicate=
or is down. They are to be send to the client after reconnecting the clien=
t.
- When communication is interrupted, the values of 'server' output I/O tags are not invalid=
ated.
- Writing a 'server' output I/O tag is as follows:=20
- During write, the output I/O tag does not pass through the status Transient.&nbs=
p;From this point of view, it is the same as setting the parameter Output mode in the tab Output control to t=
he value Command in the I/O tag configuration.
- If the communication with client is interrupted at the time of write, t=
he write is marked as unsuccessful (it can be detected e.g. in ESL script u=
sing the actions ON ERROR, WAIT) but its value is valid, current=
ly adjusted (in order to give new and valid value to the client after estab=
lishing the communication)
- If the communication with client is OK at the time of write, the write =
is marked as successful
- Configuration of the parameter Output mode<=
/a> for output I/O tag for 'server' and 'mixed' protocols is as follows:=20
- If the the parameter Output mode is set=
to Value, the particular 'server' output I/O tag will not pass through the status Transient (see the previous point). The only difference between Va=
lue and Command is shown in control windows in the process =
D2000 HI. Command allows to repeat writing any value consecutively (e.g. for out=
put I/O tag of Dout type, there are enabled the buttons ON and OFF a=
t the same time - for value outputs, there is enabled just the opposite but=
ton to the current one).
- For 'client' output I/O tags in the protocols of the series IEC104, transition through th=
e status Transient depends on the ASDU type, which is set in the con=
figuration of corresponding output I/O tag. ASDUs of the value type (1-40)&=
nbsp;are not being confirmed and therefore they do not pass through the sta=
tus Transient. ASDUs of command type (45-64) are being confirmed a=
nd therefore these output I/O tags pass through the status Transient (confirmation/not conformation of value/command I/O tags is defined by c=
ontrast to D2000 system).
For 'client' output =
I/O tags in 'mixed' protocols, which will be implemented in the future,=
the behavior will depends on the particular protocol.
Changes and modifications
-
Document revisions
- Ver. 1.0 =E2=80=93 December 15th 2004
------=_Part_111621_1373917741.1711704302356--