FSI Foreign Subsystem Integration Engineering Guidelines Document no. Edition Supersedes e1144 01.
Foreign Subsystem Integration - Engineering Guidelines TABLE OF CONTENTS 1 INTRODUCTION____________________________________________________________ 5 1.1 Related Documentation _______________________________________________________________________ 6 2 PHYSICAL LEVEL __________________________________________________________ 7 2.1 Serial line characteristics _____________________________________________________________________ 7 2.
Foreign Subsystem Integration - Engineering Guidelines 1 INTRODUCTION LMS alarm is an Alarm Monitoring System (LMS stands for Local Monitoring System) designed for an effective and easy central management of a large set of safety and security devices. An LMS modular systems is made up of: • • • PC based workstation(s) equipped with Windows application software Communication network devices Safety and security subsystems (e.g.
Foreign Subsystem Integration - Engineering Guidelines Scope of this document is to provide clear technical guidelines to engineers interested to integrate a new subsystemlevel device in an LMS modular system. Please note that relay-contact interfacing will not be discussed here, even though this approach is very well possible whenever the cost of a communication software development cannot be budgeted.
Foreign Subsystem Integration - Engineering Guidelines 2 PHYSICAL LEVEL 2.1 Serial line characteristics The physical link between LMS modular and the subsystem is a RS-232c asynchronous serial interface line with data leads only: TX, RX and GROUND. Serial line must be dedicated and permanently available, no switched line can be used. No control of modem signals (RTS, CTS, DTR, DSR, DCD) is provided.
Foreign Subsystem Integration - Engineering Guidelines Also, a communication gateway can be placed in-between so as to allow the centralization of more subsystems onto one or more workstation (fig. 2.2) Gateways can have two configurations: GW-00 for up to 20 subsystems and 4 RS 232c RS 232c RS 232c RS 232c GATEWAY SUB A SUB B SUB C Subsystems Fig. 2.2 workstations (see [4]) and GW-01 for up to 4 subsystems and 2 workstations (see [5]).
Foreign Subsystem Integration - Engineering Guidelines 3 DATA LINK LEVEL RS 232c RS 232c RS 232c RS 232c GATEWAY GW-00 Subsystems GATEWAY GW-01 Subsystems Fig. 2.3 In any of the architectures depicted in the previous section, data is transferred to and from the subsystem with the CDDL data link protocol, which is extensively described in [2]. In general, CDDL can be indicated as a point-to-point, byte oriented, polling-selecting, binary protocol. Data and design subject to change without notice.
Foreign Subsystem Integration - Engineering Guidelines 4 APPLICATION LEVEL 4.1 Subsystem information model The information transmitted by the subsystem to LMS modular must allow the monitoring workstation to generate a complete representation model of the subsystem process. LMS modular is not only a logger of what goes on in the subsystem connected to it. Instead, it handles a real-time image database which represents in any moment the physical events in progress.
Foreign Subsystem Integration - Engineering Guidelines 4.2 Point database LMS modular database collects the subsystem image information in multi-state datapoints. Each subsystem is modelled in LMS modular by a specific set of multi-state point. Each "change of state" message coming from the subsystem is interpreted by LMS modular and results in a change of state of the datapoint devoted to the representation of that specific piece of information. (refer to Fig. 4.2).
Foreign Subsystem Integration - Engineering Guidelines We will see in the next sections how the subsystem can transfer the change of state information to LMS modular. However, we can now state that the subsystem is expected to generate the specific message whenever a change of its condition occurs.
Foreign Subsystem Integration - Engineering Guidelines 4.4 Subsystem model design It is now clear how to design a multi-state point model of a subsystem: 1) 2) 3) we need to list all the subsystem parts, components, elements that deserve to be presented by LMS modular workstations to the final users. This list results to be the actual point list where the subsystem process image will be stored.
Foreign Subsystem Integration - Engineering Guidelines 5 LMS MODULAR SUBSYSTEM HANDLING 5.1 LMS modular presentation of database information As described above, LMS modular is able to handle a point database that can store a process image based on multistate points. Also, the LMS modular workstation provides an effective graphic and alphanumeric display of the datapoints so as to dynamically present to the final users the evolution of the field-level process on a user-friendly interface (see Fig. 5.1).
Foreign Subsystem Integration - Engineering Guidelines 5.2 LMS modular process control Besides the pure representation of the information on the screen, LMS modular can provide control functions that allow operators to modify the conditions of the subsystem process.
Foreign Subsystem Integration - Engineering Guidelines An example of an alarm treatment is given in figures 5.2 and 5.3. In Fig. 5.2 the sequence of messages is depicted: the subsystem informs LMS modular about the alarm events and also about the execution of ack and reset commands. Fig. 5.3 illustrates the point state diagram.
Foreign Subsystem Integration - Engineering Guidelines alarm event Security point ALARM NOT ACKNOWLEDGED Security point NORMAL subsequent alarm alarm acknowledge Security point ALARM ACKNOWLEDGED alarm reset Fig. 5.3 In order to allow a complete control of the ack and reset functions, LMS modular handles a specific attribute information associated to each point state.
Foreign Subsystem Integration - Engineering Guidelines In figs. 5.4 and 5.5, the examples of fig. 4.3 and 5.3 are presented again, with the new Treatment Flag information added. POWER SUPPLY POINT (no ACK / no RESET needed) mains fault BATTERY State value = 1 Treat. flag = 1 NORMAL State value = 0 Treat. flag = 0 mains OK battery low BATTERY LOW State value = 2 Treat. flag = 1 mains OK Fig. 5.4 SECURITY ALARM POINT (ACK and RESET needed) alarm event ALARM NOT ACKNOWLEDGED State value = 1 Treat.
Foreign Subsystem Integration - Engineering Guidelines 6 CDSF PROTOCOL The Cerberus Dati Standard Format (CDSF) protocol, described in [3]; supports the application message functions above described in section 4 and 5. Both "Change of state" and "control command" messages are available as 16 byte long, CDSF frames. 6.
Foreign Subsystem Integration - Engineering Guidelines 6.
Foreign Subsystem Integration - Engineering Guidelines 7 ANNEX A - EXAMPLES OF SUBSYSTEM MODELLING 7.1 A1. Fire detection unit This example deals with a 3 zone fire detection control panel. The subsystem is modeled as described in the following table: Please note that the meaning of points 1 and 2 is the same for any subsystem.
Foreign Subsystem Integration - Engineering Guidelines 8 ANNEX B - EXAMPLES OF CONTROL COMMAND LISTS 8.1 B1. Fire detection unit Command no Description 1 2 3 4 5 Point(s) 0 Status request 0 0 0 0 0 all 0 Date/time synchronization 1 YYMM DDHH MMSS 0 - 1 Acknowledgment point no or 0=general 0 0 0 0 any 2 Reset point no or 0=general 0 0 0 0 any 3 Exclude zone point no. 0 0 0 0 zones 4 Include zone point no. 0 0 0 0 zones 8.2 B2.
Foreign Subsystem Integration - Engineering Guidelines 9 ANNEX C - SUBSYSTEM MODEL DESIGN CHECKLIST # 1 Descriptions Multi-state datapoint list Database limits 32000 points 8 lists for type 2 Datapoint states 3 Command list 4 Command parameters 5 Datapoint views in management 16 states for point 5 parameters for command (1st = point number) Data and design subject to change without notice. Supply subject to availability © Copyright by CERBERUS AG, CH-8708 Männedorf, Switzerland 1994 E1144.
