Ripple-Control System RKS-16
centralized ripple-control unit
|The following information can only give a first impression of the capabilities of the systems. We also offer:
|Consistently designed hard- and software for centralized and de-centralized systemsSwistec’s RKS-family is a consistently-designed series of ripple-control systems with a homogeneous software and hardware design. It meets all customer requirements – from the activation of a single transmitter to the administration of big centralized as well as de-centralized ripple-control systems.
The following features of the hardware and software of all centralized and de-centralized systems does not dependent on the unit size:
|Concepts of our SystemsAlthough RKS-16 and RKS-870 are based on the same hardware as well as software components, there is a fundamental difference in the system setup as soon as 2 or more transmitters are involved. This difference increases with an increasing number of transmitters:
In case of structures with a central control unit, all ripple-control transmitters are controlled by this one control unit (RKS-16) – which can be doubled for redundancy purposes – via output and transfer of ripple-control gating signals. (Fig. 1)
Swistec already successfully installed units from the RKS-family in entirely centralized or decentralized as well as in mixed systems – partly even in very big systems.
In case of structures with decentralized control units (RKS-870), a local control unit (RKS-12) generates the ctual ripple-control gating signals (also called bit patterns). Here, the central control unit takes over the central mode of operation and the coordination of the local control units. (Fig. 2)
The RKS-870-system offers a special advantage since it can accommodate mixed systems that are especially suited for transition periods. As is depicted in Fig. 2, the tele-control terminal station can also control ripple-control units via conventional direct gating.
Therefore, a RKS-870-system can be designed in an identical way to Fig. 1 as a central system and during the ongoing operation with simple changes to the coniguration be transformed into a system that transmits telecontrol telegrams to decentrally installed local control units. This transformation can be done line by line, as soon as the transmission technology as well as the locally installed local control units RKS-12 are available.
|Redundancy StrategiesGenerally speaking, the option of a (n-1)-redundancy (so called “vertical redundancy”) already exists in a decentralized system (RKS-870) due to the system’s extendable setup. The term “vertical redundancy” is visualized in Fig. 2. In case of a communication line or server PC component failure, those local control units RKS-12 that are effected by the failure are taking over the ripple-control operations for the connected ripple-control transmitters. Since the time schedule of the RKS-12 relects that of the master control unit, only spontaneous operations of the master control unit are lost.
For central systems, a “horizontal redundancy” within the master control unit and an additional n-1-redundant backup system is recommended. (Fig. 3)
Transmission problems can be eliminated by either setting up a redundant backup system or by using the independently operating RKS-12 local control units. The latter combines the advantages of both systems since a potential failure of a single RKS-12 does not interfere with the other ripple-control operations.