User Manual

Siemens Building Technologies VISONIK DCS Functions and System Messages VVS18 CM2U8567E / 04.1999
Landis & Staefa Division Function PG 2-207
TCR 48 TEC room
Generate with PG.
Important: TCR and MGR points are mutually
exclusive because of the BPS card.
TCG 49 TEC group
Generate with PG.
Important: TCG and MGG points are mutually
exclusive because of the BPS card.
RWI 50 RWI Controller
Generate with PG
MX 51 Multiple status input
The MX point is generated in the VISONIK DCS using
the function PG in the same way as for an DI point.
However, the type MX must be entered at the 'Point
Type' prompt, instead of DI.
MD 52 Maximum demand point
The MD point is generated in the VISONIK DCS using
the function PG in the same way as for a ZW point.
However, the type MD must be entered at the 'Point
Type' prompt, instead of ZW.
The MD point can be addressed via
$LS1 .. 7
as soon
as a tariff group is assigned to it with the parameter
TGRP (TGRP=1..7)
MC 53 Message channel
The process image for all message channels is
generated automatically when the VISONIK DCS is
booted for the first time.
SY 54 Data Communication Server
$SY is generated automatically at the first system
boot.
FL 55 Flag point
Generate with PG.
Configuration:
When a suppression class is defined, the suppression
class numbers must correspond to the respective flag
numbers.
RI 57 DCS ring
$RI1 .. $RI6 are generated automatically at the first
system boot.
TY 58 DCS TTY interface
$TY1..$TY3 are generated automatically at the first
system boot.
The remaining $TYn must be generated manually with
the PG dialogue.
Important: Generation is password protected.
OZ 59 DCS OSTP zone
Generate with PG.
Notes on the point types AI, AO, DI, DO and CI
Parallel to the existing module points types (MOPs), five new, related types were
introduced with the integration of the BPS in the VISONIK DCS.
The five former point types
ME, PS, ST, SC, CG
can only be used for addressing I/O points on the EKL Bus and P-Bus.
Using the new, related point types
AI, AO, DI, DO, CI
all I/O points can be addressed, regardless which communication bus they are located
on (see parameter SIDEMV).