CN107888649B

CN107888649B - Fault detection device

Info

Publication number: CN107888649B
Application number: CN201710865183.7A
Authority: CN
Inventors: 佐藤智洋; 小田根昌弘; 藤原将芳; 木村刚维
Original assignee: Mitsubishi Electric Building Techno Service Co Ltd
Current assignee: Mitsubishi Electric Building Solutions Corp
Priority date: 2016-09-29
Filing date: 2017-09-22
Publication date: 2022-01-11
Anticipated expiration: 2037-09-22
Also published as: CN107888649A; JP2018055450A; JP6518640B2

Abstract

The failure detection device (16) is connected to a network (21), and service information, which is information relating to an object modeled by a device to be controlled and characteristics of the object, flows through the network (21). The failure detection device (16) is provided with a service information reception unit (38), an alarm message extraction unit (42), and a name confirmation unit (44). A service information receiving unit (38) receives service information. An alarm message extraction unit (42) extracts service information including an alarm notification from the received service information. A name confirmation unit (44) requests the name of the object and the name of at least one of a normal value and an abnormal value that the current value characteristic can take, using the object identifier of the sender added to the service information including the alarm notification as the destination. Thus, a light-load failure detection system can be constructed.

Description

Fault detection device

Technical Field

The present invention relates to a failure detection device capable of detecting a failure of equipment in a building.

Background

Conventionally, a Building/Energy Management System (BEMS) for managing equipment and power of a Building is known. In BEMS, communication is performed between various Control apparatuses (network apparatuses) according to, for example, a BACnet (Building Automation and Control networking) protocol established by the american society of heating, cooling, and air conditioning engineers (ASHRAE).

Generally, a distributed control system is employed when BEMS is applied to a prescribed building. That is, the lower-level control device (B-BC: BACnet Building Controller) is set according to the equipment group category of the air-conditioning equipment, the lighting equipment, the disaster prevention equipment, and the like. Further, each lower control device is managed and operated by a higher control device (B-OWS).

When the equipment group is different from the installation person (supplier) of the upper control device, for example, company a constructs an air conditioning equipment, company B constructs an upper control device, and the like, information (service information) exchange between the lower control device and the upper control device of the equipment group may become difficult. For example, a part of information requested by the upper control device may not be provided from the lower control device, or a message output from the lower control device may be difficult to analyze due to a difference in protocol or the like.

Therefore, for example, in japanese patent application laid-open No. 2016-1384, a network analysis supporting apparatus is provided between a network (1 st network) connecting a higher-level control apparatus (management apparatus) and a lower-level control apparatus (gateway apparatus) and a network (2 nd network) connecting the lower-level control apparatus and a device group under the lower-level control apparatus. The network analysis support device stores a message content definition table and an object definition table, and analyzes a message transmitted on the 2 nd network with reference to the tables.

Further, in japanese patent application laid-open No. 2014-153827, when a communication failure occurs between a lower controller and an upper controller, the cause of the communication failure is identified by referring to a database in which information on the cause of the communication failure is stored.

Further, in japanese patent application laid-open No. 2012-215925, all object IDs of devices under the control of a lower controller are acquired, and all characteristic information of each object ID is acquired.

However, in order to grasp the entire states of all the devices in a building having a large number of equipment devices such as a high-rise building, a storage device having a large capacity is required. In addition, in order to grasp the state of each device that changes from time to time, a large number of point inspections need to be performed. Furthermore, when equipment in a building is updated, the storage device needs to be updated accordingly. Such a multipoint management system is required to construct a system with a lighter load, because it is a so-called critical technical requirement (over spec) when a management item of a building is defined, for example, when only failure detection is defined.

Disclosure of Invention

The present invention relates to a fault detection device connected to a network through which service information, which is information on an object modeled by a device to be controlled and characteristics of the object, flows. The failure detection device includes a receiving unit, an extracting unit, and a confirming unit. The receiving unit receives the service information. The extraction unit extracts service information including an alarm notification from the received service information. The confirmation unit requests the name of the object and the name of at least one of a normal value and an abnormal value that the current value characteristic can take, using the sender object identifier added to the service information including the alarm notification as a transmission destination.

According to the present invention, the service information including the alarm notification is extracted exclusively from the service information circulated in the network. Further, by inquiring the sender of the service information about the details of the alarm (the name of the object and the name of at least one of the normal value and the abnormal value that can be taken for the current value characteristics), it is not necessary to provide the master data and the like in advance, and thus it is possible to construct a fault detection system with a smaller load.

Among the objects corresponding to the devices installed in the building, a plurality of objects corresponding to the alarm notification, such as a failure alarm object and an abnormality alarm object, are set across a plurality of equipment devices. However, during the period of removal from the building with aging, an object corresponding to the alarm notification is set for a strong device that has not been notified of the alarm at one time, for example, in a statute. In view of such construction practices, in the present invention, the master data such as the names of the target devices and the contents of the failure/abnormality corresponding to the failure alarm object and the abnormality alarm object are not previously acquired and stored for all the failure alarm objects and the abnormality alarm objects, but the specific contents of the objects that actually issue the alarm notification are inquired as needed. In this way, a light-load fault detection system can be constructed.

In the above invention, the confirmation unit may request the current value characteristic from the sender object when the service information including the alarm notification does not include the current value characteristic of the sender object and when the service information issued by the sender object after the service information including the alarm notification is issued does not include the current value characteristic.

In this way, by reliably acquiring the current value characteristic, the state of the alarm notification target device can be accurately grasped.

In the above invention, the failure detection device may include a combining unit and a transmitting unit. The synthesizing unit generates a control target device residence name in which identification information of a building of the control target device is added to the object name received from the sender object. The transmission unit transmits the name of the residence of the control target device, the current value characteristic, and at least one of a normal value and an abnormal value that can be taken by the current value characteristic to a management server provided in a building different from the building.

For example, when constructing a plurality of failure detection systems with or without failure across a plurality of building monitoring devices, there are cases where object names (machine device names) and the like are duplicated between buildings (e.g., "2-story south air-conditioning floor", and the like). Therefore, by adding the building ID provided with the failure detection device to the object name, duplication of the machine equipment name can be avoided.

According to the present invention, a fault detection system of a light load can be constructed.

Drawings

Fig. 1 is a diagram illustrating a multi-span fault detection system of the present embodiment.

Fig. 2 is a diagram illustrating a power management system of a single building.

Fig. 3 is a diagram illustrating an upper network of a power management system of a single building and a network for managing the building.

Fig. 4 is a diagram illustrating a hardware configuration of the failure detection device of the present embodiment.

Fig. 5 is a diagram illustrating functional units of the failure detection device of the present embodiment.

Fig. 6 is a diagram showing a failure detection flow of the present embodiment.

Description of the reference symbols

10a building; 12 a network line; 14 managing the building; 16 a fault detection device; 18 a management server; 20 a host control device; 21BACnet network; 22a lower-level control device; 28 machine equipment; 30 sensors; 38 a service information receiving section; a 40 binary input extraction section; 42 an alarm message extraction section; 44 a name confirmation part; 46 a name receiving section; 48 an alarm information synthesizing unit; 50 an alarm information transmitting section.

Detailed Description

A multi-span fault detection system of the present embodiment is illustrated in fig. 1. The multiple fault detection system includes a plurality of buildings (buildings) 10A, 10B, 10C … and a management building 14. Each of the

buildings

10A, 10B, and 10C … is provided with a failure detection device 16 (gateway), and failure information is transmitted from the failure detection device 16 to a management server 18 that manages the building 14 via a network line 12 such as the internet.

Conventionally, in general, in operation of a building/energy management system (BEMS), an administrator is resident in each of the

buildings

10A, 10B, and 10C … to cope with a failure alarm and an abnormality alarm of the equipment. In contrast, by constructing the multiple fault detection system shown in fig. 1, it is possible to realize the human-saving of the

buildings

10A, 10B, 10C ….

For example, at night when the number of times of transmission of the failure alarm and the abnormal alarm is relatively reduced, the administrator is left in the management building 14 only, and the administrator is left absent in the

buildings

10A, 10B, and 10C …. Further, it is assumed that when the management server 18 receives the failure alarm and the abnormality alarm, the manager managing the building 14 goes to the transmitter device of the failure alarm and the abnormality alarm. Alternatively, when the administrator managing the

building

10A, 10B, 10C … dozes off, the administrator managing the building 14 monitors the

buildings

10A, 10B, 10C … for the presence or absence of a failure/abnormality. I.e. to act on a part of the monitoring traffic.

An overview of a building/energy management system (BEMS) of a single building 10 is illustrated in fig. 2. The system includes a master Controller 20(B-OWS), a slave Controller 22(B-BC Building Controller), a fault detector 16 (gateway, G/W), a direct digital Controller 24(DDC), a remote station 26(RS), a machine 28, a sensor 30, and an operation panel 32.

In the building/energy management system (BEMS), equipment devices are grouped according to the types of the devices (lighting, air conditioning, theft prevention, and the like), and each device group is under the control of one subordinate control device 22 (becomes a control target). In the example shown in fig. 2, the lower-level controller 22A is provided as a controller for the lighting equipment group 23, and the lower-level controller 22B is provided as a controller for the air-conditioning equipment group 25.

The

lower controllers

22A and 22B and the upper controller 20 can communicate with each other through a network 21(BACnet network) according to a BACnet (building Automation and Control) protocol. The BACnet protocol is specified in detail by Standard 135-2012 of the American society of heating, refrigeration and air Conditioning Engineers (ASHRAE) or its ISO Standard ISO16484-5, and thus the description thereof is omitted as appropriate. The

subordinate controllers

22A and 22B, the equipment 28, the sensors 30, the operation panel 32, and the like under their control can communicate with each other via a Network such as a local Operating Network for works or a vendor-standard Network in which the equipment is installed.

The host control device 20(B-OWS) mainly performs screen display and setting operations. For example, the management information of the entire system is centrally managed by browser software of the central monitoring terminal.

The subordinate controller 22(B-BC) mainly performs a control function, and manages point data, scheduling control, and the like at various measurement points in cooperation with the remote station 26(RS) and the direct digital controller 24 (DDC). The lower controller 22 also functions as a gateway, and is interposed between a communication protocol (for example, LonWorks) with the device under control and a communication protocol (BACnet) with the upper controller 20.

The remote workstation 26 and the direct digital controller 24 control the start/stop of the machine corresponding to the schedule control. Further, a stop operation (such as cutting off of power supply and full closing of the valve) of the control target device is executed upon receiving a stop command or the like from the lower-level control device 22. The detection values of the various sensors 30 are transmitted to the lower control device 22.

Fig. 3 shows an outline of the network 21 of the BACnet in the building 10 and the network line 12 between the failure detection device 16 and the management server 18. As described above, the upper controller 20, the

lower controllers

22A and 22B, and the failure detection device 16 perform signal communication on the network 21 according to the BACnet protocol. The failure detection device 16 and the management server 18 are connected to the management server 18 via a network line 12 such as the internet that does not comply with the BACnet protocol. The failure detection device 16 has a function as a gateway and connects the BACnet protocol and a protocol not conforming to the BACnet protocol.

In the BACnet protocol, control target devices such as the machine devices 28, the sensors 30, and the operation panel 32 of the building are modeled as objects, and the objects are abstracted into objects, functions, and the like. A property called property is attached to an object.

For example, a plurality of objects such as an operation/stop object, an alarm signal object, an operation mode (cooling/heating/blowing) object, an intake air temperature measurement object, an indoor temperature setting object, and an emergency stop object are set for one air conditioner. And further add properties to each object.

The failure detection device 16 of the present embodiment is exclusively responsible for alarm notification, and thus a characteristic group of a binary input object type (BI) showing 2-value information such as failure alarm/abnormal alarm and on/off information associated with alarm notification is shown in table 1 below. In addition, the numerals (70, 984000) of the data instances of Object _ Identifier and Object _ Type indicate instances, and are identification numbers for identifying objects of the same Type. In the column of the data example, parameters enclosed in braces such as { a, B, C } indicate optional parameters separated by commas.

[ TABLE 1 ]

In the BACnet protocol, operations on objects and properties such as reading, writing, notification requests for the objects and properties are referred to as "services". In the BACnet protocol, there are 36 standard services of 5 types defined as services, including, for example, a service Request (Request, Req) for a specific object and a response (Request, Rep) from the specific object. A parameter list (format) constituting a service called a service element is defined for each service. For example, table 2 below shows service elements of a unofficized Event Notification service that notifies occurrence of an Event in a form that does not require a reception confirmation from a destination.

[ TABLE 2 ]

As described later, the failure detection device 16 receives service information (operation information on objects and their characteristics) flowing through the network 21 of the BACnet, and inquires of a sender of the service information about specific service information (including alarm notification) about various characteristics. As such an inquiry service, for example, a Read Property Multiple service having service elements as shown in table 3 below is executed.

[ TABLE 3 ]

Parameter name	Request (Req)/response (Rsp)
		List of Read Access Specifications	Request for
List of Read Access results	Response (case of success)
		Error Type	Response (failure case))

Details of List of Read Access specificities, which are parameters of Table 3, are shown in Table 4 below.

[ TABLE 4 ]

The service information shown in tables 2 to 4 is distributed over the network 21 in units of messages called APDUs (Application Protocol Data Unit). The failure detection device 16 is provided with a decoder (not shown) for interpreting the APDU message. The structure of APDUs is known from ISO9545 et al, the method explained.

As described later, the failure detection device 16 is connected to the network 21, extracts failure information of a specific equipment 28 and the like from service information distributed on the network 21, and transmits the details thereof to the management server 18.

Fig. 4 illustrates a hardware configuration of the failure detection device 16. The failure detection device 16 is formed of, for example, a computer, and has a CPU 34, a memory 36, and an input/output interface 37 with an external device. The CPU 34 executes a failure detection program stored in the memory 36 or a storage medium such as a CD-ROM, and the failure detection device 16 functions as each functional unit shown in fig. 5.

Referring to fig. 5, the failure detection device 16 includes a service information receiving unit 38, a binary input extracting unit 40, an alarm message extracting unit 42, a name confirming unit 44, a name receiving unit 46, an alarm information synthesizing unit 48, and an alarm information transmitting unit 50.

The service information receiving unit 38 receives service information distributed through the network 21. When the failure detection device 16 is not recognized by the upper control device 20 and the lower control device 22 in the network 21, the service information that the service information reception unit 38 can receive is basically simultaneous transmission communication (broadcast communication) in which the transmission destination is not determined. Alternatively, a switching hub having a port mapping (forwarding) function may be connected between the upper control device 20 and the node 27 (see fig. 3) thereof, and may receive service information of unicast communication in which the upper control device 20 is set as a single transmission destination.

The binary input extracting unit 40 is connected to the service information receiving unit 38, and receives service information from the service information receiving unit 38. The Binary Input extracting unit 40 refers to the Event Object Identifier (see table 2) among the parameters of the service information, and extracts service information in which the parameter (the Object parameter not including the example) is a Binary Input (Binary Input).

The alarm message extraction unit 42 is connected to the binary input extraction unit 40, and receives service information in which Event Object Identifier is binary input. The ALARM message extraction unit 42 refers to the Notify Type in the received parameters of the service information, and extracts service information whose parameters are ALARM (ALARM notification).

In addition to the unonfirmed Event Notification service, there is a service in which parameters of a plurality of service elements, which are service information, include Event Object Identifier (or Object Identifier alone) and Notify Type. Specifically, a configured Event Notification service element, a Get Event Information service element, and the like can be given. The details of these service elements are specified in ASHRAE standard 135-. The service information can be extracted by the binary input extraction unit 40 and the alarm message extraction unit 42.

The name confirmation unit 44 is connected to the ALARM message extraction unit 42, and receives an Object _ Identifier (including an Object Identifier and an instance) of service information of Event Object Identifier (Binary Input) and Notify Type (ALARM). For example, in the example of table 2, the name confirmation part 44 receives an object identifier unique to the device, such as "BINARY _ INPUT, 984000" or "device, 70".

The name confirmation unit 44 sets an Object of Object _ Identifier _ INPUT, 984000 (device, 70) as a destination (recipient), and transmits a Read Property Multiple service request (Req) (table 3). Specifically, it requests reading of each characteristic of Object _ Name, Active _ Text, and Inactive _ Text (names of normal values) of Object _ Identifier, BINARY _ INPUT, 984000.

In addition, the extracted service information may not include a Present _ Value property (current Value property) indicating whether the current Value of the object is Active or Inactive. For example, the service element of the unofficized Event Notification service shown in table 2 does not include the Present _ Value property. In this case, an unofficienized COV Notification service that notifies that the property Value has changed is sometimes transmitted (by broadcasting) from the Object _ Identifier Object of BINARY _ INPUT, 984000, and the Present _ Value property of the service is acquired, whereby the current Value (Active/Inactive) of the Object can be obtained.

In addition, when the service information transmitted from the sender Object after the unofficized Event Notification service does not include the Present _ Value Property, the Name confirmation unit 44 may request reading of the Present _ Value Property in addition to the Object _ Name, Active _ Text, and Inactive _ Text properties when the Read Property Multiple service request is made.

The name receiving unit 46 receives a Read Property Multiple service response from the object of the BINARY _ INPUT, 984000 (or device, 70) in response to the Read Property Multiple service request transmitted by the name confirming unit 44 (RSp).

The alarm information synthesizer 48 is connected to the alarm message extractor 42 and the name receiver 46. Service information of Event Object Identifier Binary Input and Notify Type ALARM is received from the ALARM message extraction section 42. The Object _ Name, Active _ Text, and Inactive _ Text properties included in the Read Property Multiple service response are received from the Name receiving unit 46.

The alarm information synthesis unit 48 generates a control target device residence Name (for example, a-building 2 north air conditioner trouble alarm signal) obtained by adding identification information (for example, a-building) of the building in which the trouble detection device 16 is installed to an Object _ Name characteristic (for example, 2-floor north air conditioner trouble alarm signal) of a sender target including service information for alarm notification.

The alarm information transmitting unit 50 is connected to the alarm information synthesizing unit 48. The alarm information transmitting unit 50 transmits 4 pieces of information including the name of the residence of the control target device to be the sender of the service information including the alarm notification, the Present _ Value (e.g., Active), the Active _ Text (e.g., "abnormal fan rotation speed"), and the Active _ Text (e.g., "normal fan rotation") to the management server 18.

Since Active _ Text (for example, "abnormal fan rotation speed") and Inactive _ Text (for example, "normal fan rotation") are in a pair relationship, if either one is a characteristic indicating an abnormality, the other is a characteristic indicating a normality. Therefore, at least one of Active _ Text (for example, "abnormal fan rotation speed") and Inactive _ Text (for example, "normal fan rotation") may be transmitted to the management server 18.

Fig. 6 illustrates a failure detection flow of the failure detection device 16 according to the present embodiment. When the service information receiving unit 38 receives the service information distributed over the network 21, the procedure is started. The service information received by the service information receiving unit 38 is sent to the binary input extracting unit 40. The Binary Input extracting unit 40 refers to the Object Identifier or the Event Object Identifier of the received service information, and determines whether or not the value is Binary Input (S10).

In the case where the values of both the Object Identifier and the Event Object Identifier are not Binary Input, the present flow ends. On the other hand, in the case where the value of Object Identifier or Event Object Identifier is Binary Input, the service information is transmitted to the warning message extraction section 42.

The ALARM message extraction unit 42 refers to the Notify Type of the received service information, and determines whether or not the value is ALARM (ALARM notification) (S12). In the case of not ALARM, the present flow ends. In the case of ALARM, an Object _ Identifier (including an Object Identifier and an instance) including service information of ALARM as a parameter is sent to the name confirmation unit 44. Then, the service information is sent to the alarm information combining unit 48.

The name confirmation section 44 outputs the Read Property Multiple service having the Object _ Identifier transmitted from the alarm message extraction section 42 as the transmission destination (recipient) (S14). At this time, the query Object property includes Object _ Name, Active _ Text (abnormal value Name), and Inactive _ Text (normal value Name). As described above, the Present _ Value property may be included in the query object as appropriate.

When receiving the reply of the Read Property Multiple service, the name receiving unit 46 transmits the received Property to the alarm information synthesizing unit 48. The alarm information synthesis unit 48 generates a control target equipment residence Name (for example, a north air conditioner trouble alarm signal on floor 2) obtained by adding identification information (for example, a building a) of the building in which the trouble detection device 16 itself is installed to the Object _ Name (for example, a north air conditioner trouble alarm signal on floor 2).

Then, the alarm information transmitting unit 50 transmits 4 pieces of information, i.e., the control target device residence name, Present _ Value, Active _ Text, and Inactive _ Text, to the management server 18 (multi-management system) that manages the building 14 (S18).

The data received by the management server 18 is, for example, "object machine and signal: a building 2 layer north air conditioner fault alarm signal, current value: active, Active name: fan rotational speed anomaly, Inactive name: the fan rotates normally ". After visually confirming the message, the manager managing the building prepares a tool required for repair according to the Active name and goes to the building provided with the target machine.

Claims

1. A failure detection device connected to a network through which service information, which is information on an object and characteristics of the object, the object being a model of a device to be controlled installed in a building according to a building automation and control networking protocol, is distributed, the failure detection device comprising:

a receiving section that receives the service information, a notification type of the service information including an event notification or an alarm notification;

an extraction unit that extracts service information including an alarm notification from the received service information; and

a confirmation unit that requests, as a transmission destination, a name and an object name of at least one of a normal value and an abnormal value that a current value characteristic can take, with a sender object identifier that is added to the service information including the alarm notification and that identifies a sender object of the alarm notification,

when the service information including the alarm notification does not include the current value characteristic of the sender object and the service information issued by the sender object after the service information including the alarm notification is issued does not include the current value characteristic, the confirmation unit requests the sender object for the current value characteristic, which is a normal value or an abnormal value.

2. The fault detection device of claim 1,

the failure detection device includes:

a synthesizing unit that generates a control target device residence name generated by adding identification information to the object name, the object name being obtained by being received from the sender object, the identification information being identification information of a building in which the failure detection device is installed; and

and a transmission unit that transmits a name of at least one of a normal value and an abnormal value that can be taken by the current value characteristic, the control target device residence name, and the current value characteristic to a management server provided in a building different from the building.