JPH08241488A - Monitor device for prevention of disaster - Google Patents

Abstract

PURPOSE: To start a device to perform the test or the like even in the case that a terminal classification table where classification information of terminals are stored is not completed. CONSTITUTION: When the pseudo operation mode is indicated from a main CPU 11, sub-MPUs 12-1 and 12-2 request and acquire the classification information to all terminals 2 to 5 by polling and generate pseudo operation tables 21 based on these acquired classification information and transfer the data generated in pseudo operation tables 21 to the main CPU 11 and enter into the state monitor processing. The main CPU 11 acquires classification information or the like of terminals 2 to 5 from sub-MPUs 12-1 and 12-2 to generate a pseudo operation table 18 and displays its contents on a display part 14 and enters into the pseudo state monitor processing.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to type information of a plurality of types of terminals connected to a receiver, based on the type information and addresses of terminals stored in a type table created individually for each monitoring area. The present invention relates to a disaster prevention monitoring device that collates addresses and shifts to a fire monitoring state.

[0002]

2. Description of the Related Art In this type of disaster prevention monitoring device, when the receiver is powered on and started up by a power-on start, as the initialization process for all terminals, the correct type of terminal (analog smoke detector, analog heat detector) is used. Device, sensor repeater, control repeater, etc.) is automatically checked to see if it is connected.

Further, the receiver is composed of a main MPU and one or more sub MPUs, the main MPU is assigned fire judgment and management of the entire receiver, and each sub MPU is assigned a function of collecting analog data by transmission control. By
It is known that functions are dispersed. For example, one sub MPU accommodates 8 systems, one system accommodates a maximum of 127 terminals, and when the number of sub MPUs is n, the address of the terminal is (8 × n) system × 127 (terminal Polling address).

Further, when a plurality of lines are further drawn from the sensor repeater and the control repeater to house control devices such as on / off sensors, fire doors, smoke vents, and district bells, It is managed by the hardware number of "system + terminal address + line". Further, on the receiver side, a message (for example, 1F conference room, 1F kitchen) for displaying a reporting area or a failure area is set, and set to correspond to this display message and the above-mentioned hardware number. .

In such a disaster prevention monitoring device, since a process unique to each terminal is required, the receiver side is provided with a terminal type table created individually for each monitoring area, and the type etc. is set on the terminal side. It is configured to set and request the type information from the receiving side to each terminal at the time of start-up, to collect, and to shift to the fire monitoring state when the matching results of all the type information match. At this time, if the type information does not match, the startup process is interrupted, the terminal is replaced with the correct type, and then the startup is performed again.

[0006]

However, the terminal type table used when collating the terminal type information is not determined unless the construction of the device is close to the completion stage. Therefore, the terminal type table is determined. There is a problem that during the construction that has not been performed, the device cannot be started up to collect and test analog data from the sensor, and further to perform an operation test of the control device at all.

Even if the terminal type table is determined,
Especially in large-scale systems with many terminals and types, in many cases terminals are not installed according to the terminal type table.In this case, type mismatch frequently occurs and startup is interrupted each time. Raising is not complete.
Further, if the terminal is not connected as designed, the type information itself cannot be obtained.

The present invention has been made in view of the above-mentioned conventional problems, and even when the terminal type table in which the terminal type information is individually created and stored for each monitoring area is not completed. It is an object of the present invention to provide a disaster prevention monitoring device that can start up the device and perform tests and the like.

[0009]

The present invention is configured as follows in order to achieve this object. First, the present invention compares the type information and addresses of a plurality of types of terminals connected to the receiver based on the type information and addresses of the terminals stored in the type table created individually for each monitoring area, and fires. This is intended for disaster prevention monitoring devices that shift to the monitoring state.

The present invention relates to such a disaster prevention monitoring device
The pseudo-operation mode is set by the mode setting unit when starting up and the mode setting unit that prohibits the process of collating the terminal type information based on the terminal type information stored in the type table and sets the pseudo operation mode. If there is a request, type information and addresses are collected from the terminal, a pseudo operation table creation unit that creates a pseudo operation table for each terminal, and a pseudo fire that performs pseudo fire monitoring processing based on the pseudo operation table And a monitoring unit.

Further, the pseudo operation table creating section is characterized by storing the unconnected information of the sensor in the pseudo operation table when the type information and the address are requested to the terminal and there is no reply. Further, the pseudo fire monitoring unit is characterized by performing pseudo fire monitoring processing ignoring the terminal type information of the pseudo operation table.

Further, the type table stores message information for displaying the name of each district of the monitoring area for each terminal, and the pseudo operation table does not store the message information. Further, the receiver is composed of a main MPU and one or more sub MPUs,
U requests and collects type information and addresses from terminals, creates a pseudo operation table for each terminal, and creates a main MPU
It is characterized by being transferred to.

[0013]

According to the present invention, when the pseudo operation mode is set, the process of collating the terminal type information based on the terminal type information stored in the type table is prohibited, and the terminal type Create a pseudo operation table showing the current status of terminals by requesting and collecting information and addresses,
Since the pseudo fire monitoring process is performed based on this pseudo operation table, even if the terminal type table in which the terminal type information is individually created and stored for each monitoring area is not completed, the device is started up and tested. And so on.

[0014]

1 is a block diagram showing an embodiment of a disaster prevention monitoring apparatus according to the present invention. In FIG. 1, plural lines of transmission lines 8 are drawn out from the receiver 1, and each line of transmission lines 8 is extracted.
An analog heat sensor 2, an analog smoke sensor 3, a sensor relay 4, and a control relay 5 are serially connected to the terminal. Further, a sensor line 9 is drawn out from the sensor repeater 4 to connect the ON / OFF sensor. Further, the smoke extraction device 7 is connected to the line drawn from the control repeater 5.
And other control equipment are connected.

A maximum of 127 terminals can be connected to one transmission line 8, and a maximum of 127 types of unique addresses and type information are preset in each terminal. Also, a maximum of 4 lines can be drawn from the repeaters 4 and 5 for the sensor or control. The receiver 1 includes a main MPU 11 that manages the entire receiver, two sub MPUs 12-1 and 12-2 that perform data transmission with a terminal, an operation unit 13, a display unit 14, a power supply unit 15, and Mode setting switch (S for selecting normal operation mode or pseudo operation mode)
W) 16 is provided. The main MPU 11 has an operation processing unit 17, a pseudo operation table 18, and a ROM (type table) 19, and the type table 19 is created for each system (monitoring area) and is attached, for example, when construction is completed.

Each of the sub MPUs 12-1 and 12-2 has a table creating section 20 and a pseudo operation table 21, and the pseudo creating table 21 is created by the table creating section 20 based on the control of the main MPU 11 during the pseudo operation. The data is transferred to the pseudo operation table 18 on the main MPU 11 side. Main MPU 11 and sub MPU 12-1, 1
Each of the 2-2 has a CPU 22 and a ROM as shown in FIG.
23, RAM 24, interrupt port 25, I / O port 2
6, a serial communication port 27, a bus 28, etc., and includes a main MPU 11 and sub MPUs 12-1 and 12-2.
Transmits commands and data through the interrupt port 25 and the I / O port 26, and the sub MPU 12-1,
Data transmission between 12-2 and the terminal is performed via the serial communication port 27.

FIG. 3 shows that the sub MPUs 12-1 and 12-2 have two
The structure of the type table 19 in the case of a stand (16 lines) is shown, and this type table 19 is composed of (system number + address + line number) + type information + display message for each terminal. On the other hand, both the pseudo operation table 18 of the main MPU 11 and the pseudo operation table 21 of the sub MPUs 12-1 and 12-2 store only the physical address of the type table 19 and the type and message are empty areas. For example, it is created by acquiring the type information as shown in FIG.

Next, the operation of the embodiment shown in FIG. 1 will be described. First, as shown in the flowchart of FIG. 5, the main CPU 11 executes the initialization process of step S1 by the start by power-on, and the mode setting SW1
In step 6, it is determined whether the pseudo operation mode is set or the normal operation mode is set. If the pseudo operation mode is set, the process proceeds to step S3, and FIG.
The pseudo operation mode process shown in detail is executed in step S
The pseudo state monitoring process of No. 5 is performed.

On the other hand, when the setting of the normal operation mode is determined in step S2, the process proceeds to step S4, the normal operation mode process shown in detail in FIG. 7 is executed based on the type table 19 shown in FIG. 3, and the step S5 is executed. Shift to regular status monitoring processing. In the pseudo operation mode process of step S3 of FIG. 5, as shown in FIG. 6, the pseudo operation mode is set in step S11, the pseudo operation mode is instructed to the sub MPUs 12-1 and 12-2 in step S12, and step S13 is executed.
The terminal type information and the like are acquired from the sub MPUs 12-1 and 12-2 to create the pseudo operation table 18, and the table contents are displayed on the display unit 14.

On the other hand, in the normal operation mode process of step S4 of FIG. 5, as shown in FIG. 7, the normal operation mode is set in step S21, and the normal operation mode is set in sub-MPUs 12-1, 12-2 in step S22. In step S23, the data in the type table (ROM) 19 is sent to the sub MPUs 12-1 and 12-2 to instruct the terminal to initialize. Then, in step S24, various messages sent from the sub-MPUs 12-1 and 12-2 due to the initialization of the terminal are received and displayed on the display unit 14, and finally from the sub-MPUs 12-1 and 12-2. When the initialization end notification is received in step S25, the process is ended and the process returns to the main routine of FIG.

Next, the operation of the sub MPUs 12-1 and 12-2 will be described with reference to the flowchart of FIG. When the operation mode is acquired from the main CPU 11 in step S31, the operation mode is determined in step S32, and when the normal operation mode is instructed, the process proceeds to step S33, and FIG.
Also, the initialization process at the time of normal operation shown in detail in FIG. 10 is executed, and the process proceeds to the state monitoring process of step S37.

On the other hand, if the pseudo operation mode is instructed, the type information, addresses, etc. are requested and acquired from all terminals by polling in step S34, and the type information and addresses acquired in step S35 are acquired. Based on this, the pseudo operation table 21 as shown in FIG. 4 is created. Next, in step S36, the data created in the pseudo operation table 21 is transferred to the main CPU 11, and in step S37.
The process shifts to the state monitoring process.

In the example of the pseudo operation table of FIG. 4, a heat sensor is erroneously connected to the system "01" + address "001" instead of the smoke sensor to be correctly connected. Further, in the system “01” + address “002”, the type information is not returned when the terminal is not connected, and “unconnected” information is stored as the type information. Furthermore, system "1
For "6" + address "127" + line number "4", the "smoke exit" in the normal state is not returned from the terminal, but the "fire door" is returned. In this case, nothing is stored in the display message area of the pseudo operation table 18 on the main MPU 11 side and the pseudo operation table 21 on the sub MPUs 12-1 and 12-2 side.

However, the message used at the time of notification or failure in the pseudo operation mode is automatically generated from the hardware number, for example, "... system ... address ...
It is also possible to display a message such as "line". As described above, in the present invention, since the pseudo operation mode is provided and the pseudo operation tables 18 and 21 are created, some tests can be performed even if the type table 19 is not completed.

For example, the main MPU 11 and the sub MPU 1
Between 2-1 and 12-2, sub-MPUs 12-1 and 12-2
Since data is transmitted between the terminal and the terminal, if there is a transmission error, the error occurrence should not be displayed on the display unit 14 or the contents of the pseudo operation table 18 as shown in FIG. 4 should not be displayed on the display unit 14. The transmission abnormality can be checked by.

If there is no transmission abnormality, the contents of the pseudo operation table 18 as shown in FIG. 4 are displayed on the display unit 14 and collation work is performed with the design drawing to check the terminal type, the address duplication, and the terminal. You can check the unconnection of. Further, the alarm test can be performed on the analog sensors 2 and 3 and the sensor repeater 4 which are normally connected, and the smoke proof / exhaust device 7 which is normally connected.
An operation test can be performed for control devices such as.
Further, when performing the pseudo fire monitoring in the pseudo operation mode, the necessary minimum fire monitoring can be performed by performing the processing in which the type information of the pseudo operation table 18 is ignored.

Next, the initialization process during normal operation will be described with reference to the flowcharts of FIGS. 9 and 10. This process is divided into the type check process of FIG. 9 and the address duplication check process of FIG. First, in the type check process of FIG. 9, in step S41, the main MPU 11 changes to the sub MP.
ROM type table 1 for U12-1, 12-2
The terminal type information stored in 9 is transferred to the sub M
The PUs 12-1 and 12-2 request the type information by polling the terminals. Next, in step S42, the type information is collected from the terminal, and the type information transferred from the main MPU 11 is collated with the ROM table. If the type information of all terminals match in step S43, the process proceeds to step S47 and subsequent steps shown in FIG. 10 to execute the next address duplication check process. On the other hand, if there is a terminal whose type information does not match, the process proceeds to step S44 to set the type abnormal status, then the initialization process is interrupted in step S45, and the interruption flag F [n] = 1 of the terminal (however,
n is an address) and the process returns to the main routine of FIG.

In the address duplication check processing shown in FIG. 10, first, in step S47, the sub MPUs 12-1 and 12 are connected.
-2 issues an address duplication check command to the terminal by polling and requests an address duplication check. When the terminal matches the address duplication check command with its own address, the terminal returns the address data with a predetermined current, so the return current is converted into the voltage V and read in step S48.

Here, when the same address is erroneously set for two terminals, a plurality of terminals simultaneously return a predetermined current, so that the reception voltage V is normal as shown in FIG. It is almost twice as much as the time and exceeds the threshold voltage Vth. Therefore, in step S49, it is determined whether or not the voltage V is equal to or higher than the threshold voltage Vth. If V> Vth is not satisfied, the set addresses do not overlap, so the initialization process is terminated and the process returns to the main routine of FIG. .

On the other hand, if V> Vth in step S49, the set addresses are duplicated, so the flow advances to step S50 to set the address duplication failure status, and in the next step S51, the initialization processing is interrupted and the terminal is also terminated. The interruption flag F [n] is set to F [n] = 1, and the process returns to the main routine of FIG. In the above embodiment, the transition to the pseudo operation mode is manually set by the mode setting switch 16. However, for example, at the time of start-up, it is determined whether or not the ROM type table 19 is connected. Alternatively, the pseudo operation mode may be automatically set.

In the above embodiment, the receiver is provided with two sub MPUs, but the number of sub MPUs can be appropriately determined according to the number of terminals. Of course, the present invention is not limited by the numerical values shown in the embodiments.

[0032]

As described above, according to the present invention, when the pseudo operation mode is set, the process of collating the terminal type information based on the terminal type information stored in the type table is prohibited, By requesting and collecting type information and addresses from the terminal, creating a pseudo operation table showing the state of the terminal at that time, and performing pseudo fire monitoring processing based on this pseudo operation table, the type information of the terminal is Even when the terminal type table created and stored individually for each monitoring area is not completed, the apparatus can be started up and a test or the like can be performed.

[Brief description of drawings]

FIG. 1 is a block diagram showing an embodiment of a disaster prevention monitoring device according to the present invention.

FIG. 2 is a block diagram showing respective configurations of a main MPU and a sub-main MPU of FIG.

FIG. 3 is an explanatory diagram showing a configuration of a type table of FIG.

FIG. 4 is an explanatory diagram showing a configuration of a pseudo operation table of FIG.

5 is a flow chart showing the operation of the main MPU of FIG. 1 at startup.

FIG. 6 is a flowchart showing details of the pseudo operation mode process of FIG.

FIG. 7 is a flowchart showing details of normal operation mode processing in FIG.

FIG. 8 is a flowchart showing details of the operation of the sub MPU of FIG.

9 is a flowchart showing the details of the type check process in the initialization process during normal operation in FIG.

10 is a flowchart showing details of address duplication check processing in the initialization processing during normal operation in FIG.

FIG. 11 is an explanatory diagram of received voltage when addresses are duplicated.

[Explanation of symbols]

 1: Receiver 2: Analog heat detector 3: Analog smoke detector 4: Sensor repeater 5: Control repeater 6: ON / OFF sensor 7: Smoke control device 8: Transmission line 9: Line 11: Main MPU 12-1, 12-2: Sub MPU 13: Operation part 14: Display part 15: Power supply part 16: Mode setting switch 17: Operation processing part 18, 21: Pseudo operation table 19: ROM (type table) 20: Table creation unit 22: CPU 23: ROM 24: RAM 25: Interrupt port 26: I / O port 27: Serial communication port 28: Bus

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Kei Shimizu 2-1043 Kamiosaki, Shinagawa-ku, Tokyo Within Ho Chiki Co., Ltd.

Claims (5)

[Claims] 1. A fire monitoring state is entered by collating the type information and addresses of a plurality of types of terminals connected to a receiver based on the type information and addresses of the terminals stored in a type table created in advance. In the disaster prevention monitoring device, the mode setting unit that prohibits the process of collating the terminal type information based on the terminal type information stored in the type table and sets the pseudo operation mode, and the mode setting unit at the time of startup When the pseudo operation mode is set, a pseudo operation table creation unit that requests and collects type information and addresses from the terminal and creates a pseudo operation table for each terminal, and a pseudo operation table based on the pseudo operation table And a pseudo fire monitoring unit that performs the fire monitoring process of 1. 2. The disaster prevention monitoring apparatus according to claim 1, wherein the pseudo operation table creating section pseudo operates the unconnected information of the sensor when requesting type information and address to the terminal and no reply is returned. Disaster prevention monitoring device characterized by storing in a table. 3. The disaster prevention monitoring device according to claim 1, wherein the pseudo fire monitoring unit performs a pseudo fire monitoring process ignoring the terminal type information of the pseudo operation table. . 4. The disaster prevention monitoring apparatus according to claim 1, wherein the type table stores message information for displaying a name or the like of each district of the monitoring area for each terminal, The disaster prevention monitoring device characterized in that the message information is not stored in the operation table. 5. The disaster prevention monitoring device according to claim 1, wherein the receiver is composed of a main MPU and one or more sub MPUs, and the sub MPU requests type information and address from the terminal. A disaster prevention monitoring device, which collects and creates a pseudo operation table for each terminal and transfers it to the main MPU.