JP2018092288A - Protocol conversion device, protocol conversion system and equipment device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To inexpensively and efficiently connect a device where communication protocols for a management network such as BACnet are not installed, to the management network.SOLUTION: An adapter device 2 receives, from each of indoor devices 3a for operations connected to a device network 9, a model publication message including an object being a set of properties into which a function provided by the indoor device 3a for operations is modeled (in S11), stores the object in the model publication message (received in S11) into a device DB 21, and transmits a device entry message including the object stored in the device DB 21 and an address of a management network 8 which is assigned to the indoor device 3a for operations so as to be unequivocal in the management network 8, to a management device 1 via the management network 8 (in S13), thereby registering the indoor device 3a for operations with the management device 1 as a device in the management network 8.SELECTED DRAWING: Figure 2

Description

  The present invention relates to a protocol conversion device, a protocol conversion system, and equipment.

For example, BACnet (Building Automation and Control Networking Protocol (registered trademark)) has been proposed as a communication protocol of a device monitoring control system applied to building automation for managing devices in the entire building. As a result, a device group that has entered BACnet can be collectively monitored from the management apparatus.
BACnet is a communication protocol that defines a representation method and a communication method for data communicated between monitoring devices / monitored devices in facilities such as buildings and factories. In this protocol, a device is modeled as a defined abstract object, ie a collection of property data structures. By expressing various aspects of the operation of the device by property data, it is possible to access the device without requiring detailed knowledge about the device.

  Devices that enter BACnet need to support the BACnet communication protocol. In addition, devices that enter BACnet may need to be equipped with communication functions and object management functions that must be installed according to the standard. When such a function to enter BACnet is implemented in the device itself, it involves a considerable processing load, so it is difficult to install a relatively small device in terms of cost and processing capacity.

  Therefore, in order to connect a device that does not support BACnet to BACnet, it is necessary to mediate an adapter device that converts the protocol between BACnet and the device. For example, Patent Literature 1 discloses an adapter device installed between a device network to which an air conditioner is connected and BACnet. In this adapter device, an air conditioner is modeled using a template prepared for each type of air conditioner in advance, and the modeled device is entered into BACnet as a BACnet device.

JP-A-2005-130025

Since new models of air conditioners are sold one after another, the method of Patent Document 1 in which a template is prepared for each type of air conditioner for the adapter device increases the development cost of the new model. In other words, in a form in which a specific air conditioner is connected to BACnet via a dedicated adapter device, the operation is burdened.
On the other hand, in the method of connecting a device that supports BACnet directly to BACnet without using an adapter device, the cost of the device alone is increased.

  Therefore, the main object of the present invention is to connect a device not equipped with a communication protocol of a management network such as BACnet to the management network at low cost and efficiently.

In order to solve the above problems, a protocol conversion apparatus of the present invention has the following configuration.
In other words, a protocol conversion device that mediates a message communicated in the device network and a message communicated in the management network by performing protocol conversion,
From each equipment device connected to the equipment network, a device public message including an object that is a collection of properties modeling the functions provided by the equipment is received, and the object in the equipment public message is stored in the equipment database. Store and
A device entry message including an object stored in the device database and an address of the management network assigned to the facility device so as to be unique within the management network is sent to the management device via the management network. By transmitting, the equipment is registered in the management apparatus as a device of the management network.
Other means will be described later.

  According to the present invention, a device not equipped with a communication protocol for a management network such as BACnet can be connected to the management network at low cost and efficiently.

It is a block diagram of the apparatus monitoring control system regarding one Embodiment of this invention. It is a sequence diagram which shows the process outline | summary of the apparatus monitoring control system regarding one Embodiment of this invention. It is a structural example of the object model regarding one Embodiment of this invention. It is explanatory drawing of the object model regarding one Embodiment of this invention. It is the hardware block diagram and functional block diagram of the adapter apparatus regarding one Embodiment of this invention. It is the hardware block diagram and functional block diagram of the control board accommodated in the indoor unit for business regarding one Embodiment of this invention. It is a block diagram of the BACnet device database regarding one Embodiment of this invention. Fig. 6 illustrates an example packet format of a model disclosure message and a property notification message according to an embodiment of the present invention. It is a flowchart which shows the processing content of the indoor unit for business regarding one Embodiment of this invention. It is a flowchart which shows the processing content of the business indoor unit which continues from FIG. 9 regarding one Embodiment of this invention. It is a flowchart which shows the processing content of the adapter apparatus regarding one Embodiment of this invention. It is a flowchart which shows the processing content of the adapter apparatus which continues from FIG. 11 regarding one Embodiment of this invention.

  Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a configuration diagram of a device monitoring control system. The device monitoring control system is configured by connecting the management device 1 and each adapter device 2 via a management network 8, and connecting each adapter device 2 and each device via a device network 9. Hereinafter, the air conditioner 3 will be described as an example of the control target device. However, the device handled by the device monitoring control system of the present embodiment is not limited to the air conditioner 3 and can handle various devices.

  As each device of the air conditioner 3 accommodated in the adapter device 2 in the left office 3x, there are two business indoor units 3a and a business outdoor unit 3p. Each commercial indoor unit 3a is separately connected with a commercial remote controller 3b for operation. In response to the operation instruction from the commercial remote controller 3b, the commercial indoor unit 3a circulates the refrigerant through the refrigerant pipe (not shown) in conjunction with the commercial outdoor unit 3p, and moves the fan to send the conditioned air into the room. Air conditioning operation.

  As each device of the air conditioner 3 accommodated in the adapter device 2 in the right living room 3y, there is one household indoor unit 3c and a household outdoor unit 3q. The home indoor unit 3c can be remotely operated wirelessly from the home remote control 3d. Moreover, although illustration is abbreviate | omitted, the household indoor unit 3c and the household outdoor unit 3q are connected by piping through which refrigerant gas passes.

  The management network 8 is an open network in which communication is performed using a protocol suitable for device management such as BACnet. The device network 9 is a local network in which communication is performed using a protocol suitable for device control such as LonWorks. A group of devices connected to the same device network 9 is assigned a local communication address, and can communicate with each other. Further, as the device network 9, a line for directly connecting the adapter device 2 and the home indoor unit 3c and a line for directly connecting the adapter device 2 and the home outdoor unit 3q are separately provided. It is good also as a fixed form of the one-to-one connection with the domestic indoor unit 3c. In this fixed form, a communication signal between devices is not mixed in the device network 9, so that a local communication address is not necessary.

The adapter device 2 operates as a protocol converter that enables communication across two networks even if the protocol of the management network 8 and the protocol of the device network 9 are different.
The management device 1 is a device that indirectly manages each device connected to the device network 9 via the adapter device 2. The management range of the management device 1 is, for example, equipment of the entire building where the management network 8 is laid. The manager of the building can acquire the status of each device in the building or send a control instruction to each device via the management device 1 installed in a management room or the like.

FIG. 2 is a sequence diagram illustrating an outline of processing of the device monitoring control system.
First, terms used in the sequence diagram will be described. Since the management network 8 of this embodiment employs BACnet, the controlled device is modeled and defined as a collection of objects as described above. In FIG. 2, a collection of objects that define a device is described as a “model”.
Each property of each object constituting the model represents various aspects of the operation of the hardware, software, and device. For example, an object that defines the “operation / stop” setting of an air conditioner has an object type (Object_Type) property that represents that the “operation / stop” parameter to be defined is a binary value write, and the current setting state is “ It has a present value (Present_Value) property that represents whether it is “operation” or “stop”, an out-of-service property that represents whether or not the current operation is possible (details are shown in FIG. 3).
In the device monitoring control process, the management device monitors the operation state of the device by reading the property values of these objects, and controls the device by writing to the property values.
The “operation mode” is a content operated from the business remote controller 3b or the home remote controller 3d, and examples thereof include dehumidification and air blowing. Here, for each operation mode, there are objects necessary and unnecessary objects for realizing the operation mode. That is, even in the same air conditioner, the model is different for each operation mode (details are shown in FIG. 4).

In the sequence diagram of FIG. 2, the operation subject “device” on the right side is the business indoor unit 3 a connected to the device network 9 as described above. Hereinafter, although the details of the communication mechanism of the commercial indoor unit 3a will be clarified as an example of the device, other devices such as the home indoor unit 3c also have the same communication mechanism. First, a case where a new device is connected to the device network 9 will be described.
The model release message (S11) is transmitted from each device connected to the device network 9 accommodated in the adapter device 2 to the adapter device 2. This message includes a list of objects that model the functions of each device in order to notify the adapter device 2 of the functions that each device can support.

The adapter device 2 registers the list of objects notified by the model disclosure message (S11) in the device DB 21 (FIG. 5) (S12). By this registration operation, the information as the BACnet node of the adapter and the model information of the device are connected, and it becomes possible to enter the communication of the management network 8 as a new BACnet device. As a result, even a device that is not connected to the management network 8 (not equipped with the BACnet communication protocol) is connected to the management network 8 via the adapter device 2, so that the BACnet-compatible cost on the device side can be suppressed.
The device entry message (S13) is a message for publishing the new device that has transmitted the model release message (S11) from the adapter device 2 to the management network 8 as a BACnet device and declaring entry into the BACnet service. In this example, I-Am service is issued. The management apparatus 1 can know that a device is newly connected to the management network 8 as a BACnet device by receiving the device entry message (S13).
The registration success message (S14) is a message that responds to the registration target device from the adapter device 2 that the registration (S12) to the device DB 21 and the transmission of the device entry message (S13) are successful. Upon receiving this registration success message (S14), the device notifies the property value of the change value every time the device operation state changes so that the property value of the device DB 21 matches the device operation state. A property notification message (S21) is notified to the adapter device 2 as a message. The adapter 2 updates the device DB 21 to reflect the notified latest property value.
By repeating the above, the adapter can always implement the BACnet service based on the latest device information.

For example, in the case of the BACnet event service, it is assumed that a certain device detects an abnormal property value (eg, temperature display = 40 ° C.). The device notifies the adapter device 2 of a property notification message (S21) including the abnormal property. As usual, the adapter apparatus 2 updates the notified latest property value to the corresponding object property (eg, current value property of the temperature display object) in the device DB 21. Further, the event management property group of the object is referred to, and an event notification message (S22) indicating a warning is sent to the management apparatus 1 according to the setting condition (eg, alarm report service transmission when the temperature is 35 ° C. or higher). To do.
Thereby, the management apparatus 1 can make an administrator grasp | ascertain the abnormal value of an apparatus with a warning screen. Note that the BACnet alarm event service is not limited to abnormal value notification, and whenever a property value is changed, a property notification message (S21) including the changed property value is transmitted. The adapter device 2 transmits a notification message (S21) according to the setting of the event-related property of the object.

Further, the database of the adapter device 2 may be rewritten not only from the device side as described above but also from a request from the management device side. For example, there is a case where the administrator requests the Write Property service in order to set a new property value such as lowering the set temperature of the business indoor unit 3a. At that time, the management device 1 notifies the adapter device 2 of a service write request message (S31) indicating which property of which device is to be written.
The adapter device 2 updates the new property value in the received service write request message (S31) to its own device DB 21 (S32). Then, the adapter device 2 updates the property of the device by notifying the device to be updated of the property write request message (S33) including the new property value. As a result, the adapter database value matches the device operation. Then, as a result of the update, a property write response message (S34) is returned from the device to the adapter device 2.
The adapter device 2 notifies the management device 1 of a service write response message (S35) for reporting that the device property has been updated as instructed by the service write request message (S31).

Some services do not change the values in the database. For example, this is a Read Property service request when the administrator wants to know the current property value such as the set temperature of the business indoor unit 3a in the office 3x. At that time, the management device 1 notifies the adapter device 2 of a service read request message (S41) indicating which property of which device is to be read.
The adapter device 2 reads the registered property value from the device DB 21 and responds to the management device 1 by including it in the service read response message (S43).

  Various messages requested from the management device 1 to the adapter device 2 such as a service write request message (S31) and a service read request message (S41) are collectively referred to as a service request message. Similarly, responses to service request messages such as a service write response message (S35) and a service read response message (S43) are collectively referred to as a service response message.

FIG. 3 is an example of an object list in which the function of the air conditioner 3 is modeled based on the BACnet device object specification. This object list is stored in the model information storage unit 32 shown in FIG.
Here, the BACnet standard definition object includes the functions of the stop setting, operation mode setting, temperature setting, humidity setting, wind speed setting, temperature display, humidity display, and error notification that the air conditioner normally provides to the user with the user remote controller. An object list modeled using a type format is shown.

The content of the object list is composed of the following 10 objects, and is a list in which the property types of the 10 objects and their values are listed.
-One device object type object representing the configuration of this air conditioner model-One binary-output type object corresponding to the operation stop setting-Two Analog-Output type objects corresponding to the set temperature and set humidity Two Multi-state-Input type objects corresponding to operation mode setting and wind speed setting ・ Two Analog-Input type objects equivalent to room temperature and humidity display ・ Binary-Input for notification of air conditioner abnormality occurrence One type object ・ One Notification Class type object

  As described above, each property of each object includes a fixed value and a value that varies depending on the state of the device. For example, many of the properties included in the device object type and the object identifier (Object_Identifier) property, object name (Object_Name) property, object type (Object_Type) property, and property list (Property_List) property that are mandatory for all object types Etc. are basic values that define the function of the device and are unchanged. In addition, the unit property, the property group indicating the execution condition of the Event service, and the property included in the Notification Class type object are often determined by the product specifications, and are often fixed values.

On the other hand, the present value (Present_Value) property, etc., is a property that represents an operation parameter of the device, and therefore changes from time to time according to the operation state of the device and may be rewritten from other devices on the BACnet network. The value of the out-of-service (Out_Of_Service) property may change between normal operation and trial operation.
For this reason, if a property of a fixed value is sent from the device to the adapter when the BAXCnet device database is constructed on the adapter side, it is not necessary to update the value of both. Only for properties with variable values, after the BACnet device data is constructed on the adapter side, the device and the adapter are informed that they have changed each other, so that the device model in the adapter matches the actual device operating parameters. There is a need to.

  Further, in the case of the present invention, many of the properties of the device object are not devices, but are set according to the BACnet function of the adapter. Therefore, on the device side, the object name (Object_Name) property, model It is only necessary to have information on some properties that you want to specify on the device side, such as the name (Model_Name) property.

  In addition, when modeling the function of a device, the model may be different if the function changes greatly depending on the operation mode of the device. For example, the air-conditioning operation model object 100 shown in FIG. 3 assumes a case where the operation mode is air-conditioning or automatic operation.

  On the other hand, as shown in FIG. 4, when the operation mode is “dehumidification”, the temperature cannot be set, so the temperature setting object is removed from the model to form nine object configurations 101, and the operation mode is “air blowing”. Since neither temperature setting nor humidity setting is possible, it can be considered that eight object configurations 102 are formed. In such a case, a plurality of models for each operation mode of the device are stored in the model information storage unit 32.

  The operation parameter management unit 33 updates a property by selecting a model corresponding to the current operation mode from the plurality of models. If the selected model is changed in accordance with the change of the operation mode of the device, the adapter communication unit 31 is instructed to send the entire object list of the latest selected model to the adapter (similar to when the device is activated). On the adapter side, when the entire object list is notified, the BACnet device database is rebuilt in such a way that the latest information is overwritten on the previously built BACnet device data.

  Each process shown in the above functional blocks is actually realized by the microcomputer 130 reading out the BACnet information management processing program stored in the memory disk 134, developing it in the RAM 133, and executing it.

FIG. 5 is a hardware configuration diagram and a functional configuration diagram of the adapter device 2.
As shown in the upper side of FIG. 5, the adapter device 2 includes a microcomputer 120, a ROM 121, a RAM 122, a power supply control unit 123, a real-time clock 124, a management network communication IF 125, and a device network communication IF 126 as hardware configurations. And.
The microcomputer 120 is a one-chip microcomputer having various general-purpose peripheral functions with a CPU (Central Processing Unit) as a core.
The ROM 121 is a memory area that holds an OS, various programs (such as a BACnet protocol conversion program), data, and the like.
The RAM 122 is a work memory area for the CPU of the microcomputer 120 to execute a program.

The power control unit 123 is a component for performing power management.
The real time clock 124 is a component for time acquisition.
The management network communication IF 125 transmits / receives data via the management network 8 according to Ethernet (registered trademark) + UDP / IP (User Datagram Protocol / Internet Protocol) adopted for BACnet communication.
The device network communication IF 126 transmits / receives data to / from each device in accordance with the protocol adopted by the device network 9.

As shown in the lower side of FIG. 5, the adapter device 2 includes a device DB 21, a service execution unit 22, a device construction unit 23, a model information processing unit 24, a management network communication unit 25, and a device as functional configurations. And a network communication unit 26.
The management network communication unit 25 controls the management network communication IF 125. The device network communication unit 26 controls the device network communication IF 126.

The model information processing unit 24 analyzes each message received from the device via the device network communication unit 26.
When the analysis result is a model disclosure message (S11), the model information processing unit 24 passes the object list data to the device construction unit 23 to construct the device DB 21 (details are shown in FIG. 7). The device DB 21 is read from the ROM 121 by the microcomputer 120 and expanded in the RAM 122.
When the analysis result is the property notification message (S21), the model information processing unit 24 notifies the service execution unit 22 of the property data in the message, thereby prompting the transmission of the event notification message (S22).

The service execution unit 22 is a central part of the protocol conversion function that manages device data in the device DB 21 and executes the BACnet service. First, when the BACnet device data is constructed in the device DB 21 in response to the model release message (S11), the service execution unit 22 broadcasts a device entry message (S13) such as an I-am service message to the management apparatus 1. As a result, entry of the constructed device into the management network 8 is declared. Thereby, the newly registered device can accept service requests from other BACnet devices connected to the management network 8.
Then, the service execution unit 22 receives the property notification message (S21) from the device and transmits an event notification message (S22) to the management apparatus 1.

Further, the service execution unit 22 analyzes each service request message received from the management device 1 via the management network communication unit 25, and responds to the management device 1 with the processing result as a service response message.
As described with reference to FIG. 2, if the service request message is a service write request message (S31), the service execution unit 22 transmits a property write request message (S33) including an updated value of the requested property to the device. On the other hand, if the service request message is a service read request message (S41), the service execution unit 22 reads the requested property from the device DB 21.

FIG. 6 is a hardware configuration diagram and a functional configuration diagram of a control board housed in the commercial indoor unit 3a. The control board of the business indoor unit 3a is a control unit for controlling the operation of the accommodated business indoor unit 3a.
As shown in the upper side of FIG. 6, the control board of the commercial indoor unit 3a includes, as a hardware configuration, a microcomputer 130, a sensor communication IF 131, a device IF 132, a RAM 133, a memory disk 134, a power supply IF 135, an air conditioner. A communication IF 136 and a remote control IF 137 are provided.

The microcomputer 130 has various general-purpose peripheral functions with the CPU as a core, and controls the operation processing and communication processing of the commercial indoor unit 3a.
The sensor communication IF 131 takes in measured values from various sensors (a suction humidity sensor, a suction temperature sensor, and a blowout temperature sensor) attached to each location of the commercial indoor unit 3a.
The device IF 132 performs monitoring control of a fan, a compressor, a heat exchanger, a drain pump, and the like in the commercial indoor unit 3a, and sends a control signal.

The RAM 133 is a work memory area for the microcomputer CPU to execute a program.
The memory disk 134 is a non-volatile area that holds the OS, various programs, data, and the like.
The power supply IF 135 performs power management.
The air conditioning communication IF 136 is connected to the device network 9 and communicates with the adapter device 2 and the business outdoor unit 3p.
The remote control IF 137 communicates with the business remote control 3b.

As shown in the lower side of FIG. 6, the control board of the commercial indoor unit 3a includes, as a functional configuration, a control unit 30, an air conditioning operation unit 36 including a management IF unit 36a, a remote control communication unit 39a, and outdoor unit communication. Unit 39b, sensor value acquisition unit 39c, and internal device IF unit 39d. The control unit 30 includes an adapter communication unit 31, a model information storage unit 32, an operation parameter management unit 33, a state acquisition unit 34, and a setting change unit 35.
The remote control communication unit 39a controls the remote control IF 137. The outdoor unit communication unit 39b controls the air conditioning communication IF 136. The sensor value acquisition unit 39c controls the sensor communication IF 131. The internal device IF unit 39d controls the device IF 132.

The air-conditioning operation unit 36 performs air-conditioning operation according to the setting of the user as an air-conditioner via each communication unit (remote control communication unit 39a, outdoor unit communication unit 39b, sensor value acquisition unit 39c, and internal device IF unit 39d). Execute. The management IF unit 36 a of the air conditioning operation unit 36 is an interface for the air conditioning operation unit 36 to indirectly manage the operation of the control unit 30.
The management IF unit 36a adapts the adapter device to the device on the management network 8 such as the operation state of the device with respect to the control unit 30 and the setting parameter of the air-conditioning operation set by the user with the business remote controller 3b while performing the air-conditioning operation management. 2 Provide data to be provided via 2.
In addition, the management IF unit 36a receives information such as the air conditioning operation setting parameters received from the devices on the management network 8 by the control unit 30 via the adapter device 2, and changes the mode and set temperature of the air conditioning operation, for example. Execute the process.

  The adapter communication unit 31 is connected to the adapter device 2 via the device network 9. The adapter communication unit 31 transmits each message (S11, S21, S34) described in FIG. 2 to the adapter device 2 and receives each message (S14, S33) from the adapter device 2. Here, the adapter communication unit 31 exchanges data (properties, etc.) included in each message to be transmitted / received with the operation parameter management unit 33.

  The operation parameter management unit 33 stores a model (object list) for each operation mode of the device in the model information storage unit 32. The stored model is read from the model information storage unit 32 at the timing of initial activation of the device or the timing of operation mode change, and stored in the model disclosure message (S11). The operation parameter management unit 33 notifies the adapter device 2 of the model disclosure message (S11) via the adapter communication unit 31. Thereby, the registration data for each device in the device DB 21 in the adapter device 2 is reconstructed with the latest model (object list).

The properties of each object include a fixed value that is not changed and a property whose value can be changed depending on the operation state of the device. The status acquisition unit 34 is notified of the property status change (the latest value of the changed property) detected by the air conditioning operation unit 36. The state acquisition unit 34 notifies the operation parameter management unit 33 of the state change.
The operation parameter management unit 33 converts the acquired change state information into the property value of the model, and sets the model property value in the model information storage unit 32. Further, the latest value of the property value is included in the property notification message (S21) and notified to the adapter apparatus 2, so that the latest value is reflected in the device DB 21.

The setting change unit 35 receives the update value of the property value in the property write request message (S33) acquired by the operation parameter management unit 33 via the adapter communication unit 31, and reflects the update value in the change in the operation of the air conditioner. Let Specifically, in the reflection process, the setting change unit 35 converts the property value update value into the operation information of the business remote controller 3b, and writes it into a predetermined area of the shared memory buffer area provided in the RAM 133. In this way, the operation change trigger is set in the management IF unit 36a. The commercial indoor unit 3a calls a handle routine corresponding to the command content specified by this trigger, and reflects the specified operation in the air conditioning operation.
Thereby, property update such as changing the number of rotations of the fan connected to the device IF 132 is executed.

  Usually, the equipment such as the commercial indoor unit 3a already has a mechanism for updating the operation information of the remote controller handled by the commercial remote controller 3b to the input value and a mechanism for displaying the current value. There are many cases. Therefore, by extending these mechanisms already installed in the equipment, the operation parameter information expressed by the properties of the BACnet object handled by the adapter device 2 and the operation information of the remote control handled by LonWorks etc. are mutually converted. The amount of development is small.

FIG. 7 shows an example of the BACnet device database 300 that is an example of the structure of the device DB 21 and BACnet device data created by the device construction unit 23.
The device DB 21 of this adapter is configured to construct one BACnet device for each device. In FIG. 7, an area for storing a maximum of 10 BACnet device data is provided (area number column 301). BACnet device data of air conditioner 3 is built in “1”. Of course, the maximum number that can be handled is arbitrary.

  In each area, a device address column 302 for inputting a device address in the device network 9 is provided in order to associate which device information is in which area. When constructing a new BACnet device, the device construction unit 23 searches for a free area, sets a device address in the device address field 302, fills each data field based on the model information, and stores the BACnet device data. Create.

  In order to enter the BACnet network (management network 8) as a BACnet device, a BACnet address is required together with an address defined by a communication protocol specified for lower-layer communication. In this example, since Ethernet (registered trademark) and UDP / IP are used as lower communication protocols, the device construction unit 23 allocates a virtual IP address so as not to overlap other devices of the management network 8 for each device model. Are set in the IP address column 303, a BACnet / IP address is created based on the allocated IP address, and is set in the BACnet address column 304.

The lower communication layer address and BACnet address setting method vary depending on the type of lower communication employed. Further, because the object ID of the device object must be unique through the BACnet internetwork according to the BACnet regulations, the value of the device object ID sent from the device as the object model data is the other value of the management network 8. If it overlaps with the device object ID of the device, a new non-overlapping value is issued and set in the device ID column 305.
If they do not overlap, the device object ID sent from the device is used as it is. The object property list that is the main body of the model information is input to the object field 306 in the same form as the model of the device in FIG. Through the above processing, the device construction unit 23 constructs BACnet device data of the connected device in the device DB 21.

When the BACnet device data is constructed, the service execution unit 22 creates an I-am service message and declares it via the management network communication unit 25 in order to declare that the constructed device has entered the BACnet network (management network 8). Thereafter, service requests from other BACnet devices connected to the management network 8 are accepted.
The management network communication unit 25 receives a communication message from another BACnet device connected to the management network 8. If the message is a device addressed to a device in the device DB 21, the management network communication unit 25 takes the message and passes it to the service execution unit 22. The electronic statement created by the execution unit 22 is transmitted to the management network 8.

The service execution unit 22 is a central part of the protocol conversion function that manages device data in the device DB 21 and executes the BACnet service. Hereinafter, the role of the service execution unit 22 will be described.
The first role is to interpret the BACnet service request message acquired by the management network communication unit 25 and to create a response message by referring to or changing device information in the device DB 21.
The second role is to receive the property value change notification from the model information processing unit 24, change the device information in the device DB 21, and execute the BACnet alarm / event service.
The third role is to pass the contents to the service execution unit 22 to notify the device when there is a changed property value as a result of executing the BACnet service.
Each process shown by the above functional blocks is actually realized by the microcomputer 120 reading out the BACnet protocol conversion program and the BACnet device database stored in the ROM 121, developing them in the RAM 122, and executing them.

FIG. 8 shows packet format examples of the model disclosure message (S11) and the property notification message (S21).
In the model disclosure message (S11) indicated by reference numeral 111, the following data is stored in the model header in order from the top of the packet.
・ Destination (device address of adapter device 2)
・ Sender (own device address)
A data type “model notification” indicating a model disclosure message (S11)
-Number of objects included (M)
・ Data length of contained objects

  The M object information following the model header is obtained by sequentially storing the number of properties (N) included in the object, the data length of the object, and N properties following the object delimiter code. Each property stored is composed of a property ID, a property value data size, and a property value.

In the property notification message (S21) indicated by reference numeral 112, the following data is stored in the property header in order from the beginning of the packet.
・ Destination (device address of adapter device 2)
・ Sender (own device address)
Data type “property” indicating property notification message (S21)
・ The number of included properties (N)
Data length of contained property The N properties following the property header are composed of the object ID, property ID, property value data size, and property value of the object to which it belongs.

FIG. 9 is a flowchart showing the processing contents of the commercial indoor unit 3a. As preprocessing of this flowchart, when the business indoor unit 3a is turned on, a program for operating the control unit 30 is started. The control unit 30 enters the connected device network 9 and starts communication with the business outdoor unit 3p.
As S <b> 101, the control unit 30 inquires whether the adapter device 2 exists on the device network 9. If Yes in S101, the process proceeds to S111, and if No (no response from the adapter device 2), the process is terminated. The business indoor unit 3a may voluntarily connect to the adapter device 2 (Push type communication), or may respond to a model acquisition request from the adapter device 2 to the business indoor unit 3a. Good (Pull type communication).

  As S <b> 111, the control unit 30 reads, from the RAM 133, operation parameter information for constructing the current model of the business indoor unit 3 a in the device DB 21. Note that a reading destination of a variation value (described in FIG. 3) such as a current value (Present_Value) in the operation parameter information is, for example, a shared memory buffer area provided in the RAM 133. In the shared memory buffer area, the management IF unit 36a writes the latest current value at a predetermined cycle.

In step S <b> 112, the control unit 30 selects a model to be used from the current operation mode setting value, reads it from the memory disk 134, and copies the read data to the model management work area of the RAM 133. Note that which operation mode requires which object (model) is as described with reference to FIG. 4. The table of FIG. 4 and the specific data contents (property values) of each object list are as follows. Is stored in a model storage area in the memory disk 134, for example.
As S113, the control unit 30 updates the variation value among the property values of the object (model) copied in S112 with the property value of the operation parameter information read in S111. That is, data prepared in advance is used as the fixed value of the property, and the latest data currently in operation is used as the variable value of the property.

As S <b> 114, the control unit 30 creates a model disclosure message (S <b> 11) including a list of objects reflecting the latest operation state in S <b> 113 and transmits it to the adapter device 2 via the device network 9.
As S115, the control unit 30 waits for reception of a registration success message (S14) as a response to S114.

As S121, the control unit 30 reads and acquires the latest operating parameter information of the air conditioner from the RAM 133 by the same method as S111.
In S122, the control unit 30 compares the operation parameter information acquired in S121 with the property value of the model management work area in the RAM 133, and determines whether there is a parameter whose value has changed. If Yes in S122, the process proceeds to S123, and if No, the process proceeds to the terminal A (S131 in FIG. 10).
As S123, the control unit 30 determines whether it is necessary to change the model for the parameter whose value has been changed in S122. If Yes in S123, the process returns to S112 (model rebuilding process), and if No, the process proceeds to S124. Note that “the model needs to be changed” is, for example, a case where the operation mode is changed from the cooling operation to the dehumidifying operation.

As S <b> 124, the control unit 30 transmits a property notification message (S <b> 21) including the parameter whose value is determined to be changed in S <b> 122 out of the operation parameter information read out in S <b> 121 to the adapter device 2 via the device network 9. To do.
In S125, the control unit 30 updates the property value of the model management work area in the RAM 133 with the latest value read in S121. Then, the process proceeds to terminal A (S131 in FIG. 10).

FIG. 10 is a flowchart showing the processing contents of the business indoor unit 3a continued from FIG.
As S131, the control unit 30 determines whether or not the property write request message (S33) has been received from the adapter device 2. If Yes in S131, the process proceeds to S132, and if No, the process proceeds to S135.
As S132, the control unit 30 determines whether or not the property to be changed included in the property write request message (S33) is an operation parameter change (current value change). If Yes in S132, the process proceeds to S133, and if No, the process proceeds to S135.
As S133, the control unit 30 sets a trigger that uses the current value of the property write request message (S33) as an operation parameter of the business remote controller 3b. This trigger is as described above in the description of the setting changing unit 35 in FIG.
As S134, the control unit 30 also updates the property value of the model management work area of the RAM 133 with the current value of the property write request message (S33). And the control part 30 transmits that the update was completed to the adapter apparatus 2 as a property write response message (S34).

As S135, the control unit 30 determines whether or not the connection with the adapter device 2 is terminated. If Yes in S135, the process proceeds to S135, and if No, the process returns to the terminal B (S121 in FIG. 9) to continue communication with other devices on the management network 8. Note that the term “end of connection” means, for example, that communication with the adapter device 2 is disconnected or that the business indoor unit 3a itself is instructed to be turned off.
In S136, the control unit 30 writes the object list of the model management work area in the RAM 133 to the memory disk 134, and ends the process. Note that the object list written in S136 is read in the next S112.

FIG. 11 is a flowchart showing the processing contents of the adapter device 2. As preprocessing of this flowchart, when the adapter device 2 is powered on, the device DB 21 and the programs of the processing units (service execution unit 22 to device network communication unit 26) are loaded from the ROM 121 to the RAM 122. Then, it enters the management network 8 and the device network 9 mediated by the adapter device 2 to enable communication.
As S201, the device construction unit 23 determines whether or not a model disclosure message (S11) has been received from a device such as the business indoor unit 3a via the device network 9. If Yes in S201, the process proceeds to S202, and if No, the process proceeds to S211.

As S202, the device construction unit 23 checks whether or not the data area of the device address of the received model disclosure message (S11) has already been allocated in the device DB 21. If Yes in S201, the process proceeds to S205, and if No, the process proceeds to S203.
As S203, the device construction unit 23 newly allocates a data area that is not yet used in the device DB 21 for the received model disclosure message (S11).
As S204, the device construction unit 23 issues each address (IP address, BACnet address, device ID) in the device DB 21 for the device that is the transmission source of the model disclosure message (S11).

As S205, the device construction unit 23 substitutes the object list in the received model publication message (S11) into the device DB 21, thereby constructing the device that is the transmission source of the model publication message (S11) as a BACnet device.
In S206, the device construction unit 23 transmits the device entry message (S13), which is an I-am message for the device registered in S205, from the management network communication IF 125 to each device (management device 1 or the like) in the management network 8. By reporting, the entry of the newly constructed device to the management network 8 is declared.
As S207, when the network entry as a BACnet device is successful by the device entry message (S13) of S206, the device construction unit 23 notifies the registration success message (S14) to the transmission source device of the model disclosure message (S11). To do. On the other hand, when the network entry fails due to insufficient memory capacity of the device DB 21, an error message may be notified instead of the registration success message (S14).

As S <b> 211, the device construction unit 23 determines whether or not a property notification message (S <b> 21) has been received from a device connected to the device network 9. If Yes in S211, the process proceeds to S212, and if No, the process proceeds to the terminal C (S221 in FIG. 12).
As S212, the device construction unit 23 identifies the changed location in the device DB 21 from the device address, the object ID, and the property ID of the property notification message (S21), and uses the latest value notified of the identified changed location. Update.
As S213, the device construction unit 23 sends an event notification message (S22) when the value change in S212 needs to transmit some alarm or event service (for example, when the current value of the alarm display object changes). It is created and transmitted through the management network communication IF 125. Then, the process proceeds to terminal C (S221 in FIG. 12).

FIG. 12 is a flowchart showing the processing contents of the adapter device 2 continued from FIG.
In step S <b> 221, the service execution unit 22 determines whether a service request message has been received from another BACnet device (such as the management apparatus 1) connected to the management network 8. If Yes in S221, the process proceeds to S222, and if No, the process returns to the terminal D (S201 in FIG. 11).
In S222, the service execution unit 22 determines whether the received service request message is a service write request message (S31). If Yes in S222, the process proceeds to S223, and if No, the process proceeds to S225. If the service request message is a service read request message (S41), the branch is No and the process proceeds to S225.

As S223, the service execution unit 22 identifies the changed location in the device DB 21 from the device ID, object ID, and property ID in the service write request message (S31), and is notified of the identified changed location. Update with the latest value (S32).
In S224, the service execution unit 22 creates a property write request message (S33) including the property value updated in S223, and transmits it to the connected device through the device network communication IF 126.
In S225, the service execution unit 22 transmits a service response message to the service request message received in S221 to the management network 8 via the management network communication IF 125. When the service request message is a service read request message (S41), the service read response message (S43) includes a result of reading the requested data content (property value) from the device DB 21 (S42). .

In S226, the service execution unit 22 determines whether or not the adapter device 2 has been instructed to turn off the power. If Yes in S226, the process proceeds to S227, and if No, the process returns to the terminal D (S201 in FIG. 11).
In step S <b> 227, the service execution unit 22 stores the device DB 21 expanded on the RAM 122 in the ROM 121. The stored device DB 21 is loaded at the next power-on.

  As described above, the adapter device 2 according to the present embodiment is based on the data contents (objects and properties) notified from the devices of the device network 9 by the model disclosure message (S11) and the property notification message (S21). A device is registered in the management network 8 with a device entry message (S13). Therefore, it is not necessary for each device to directly perform processing related to the BACnet protocol in response to the mediation processing of the adapter device 2, and low-cost and efficient BACnet protocol conversion can be performed in the entire system.

Also, the device side notifies the adapter (object) as an aggregate of properties to the adapter device 2, and the adapter device 2 side shares the functions to create a BACnet message based on the object (model). .
As a result, the adapter device 2 only needs to handle a data structure that does not depend on a device called an object (model) (high versatility), and therefore can provide a (general purpose) adapter device 2 that can be connected to any device. .
As described above, the adapter device 2 can perform processing related to the BACnet protocol without any influence on the type and operation of the device. This eliminates the need to use vendor-free.

In addition, this invention is not limited to an above-described Example, Various modifications are included. For example, the above-described embodiments have been described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described.
Further, a part of the configuration of one embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of one embodiment.
Further, it is possible to add, delete, and replace other configurations for a part of the configuration of each embodiment. Each of the above-described configurations, functions, processing units, processing means, and the like may be realized by hardware by designing a part or all of them with, for example, an integrated circuit.
Each of the above-described configurations, functions, and the like may be realized by software by interpreting and executing a program that realizes each function by the processor.

Information such as programs, tables, and files for realizing each function is stored in memory, a hard disk, a recording device such as an SSD (Solid State Drive), an IC (Integrated Circuit) card, an SD card, a DVD (Digital Versatile Disc), etc. Can be placed on any recording medium.
Further, the control lines and information lines indicate what is considered necessary for the explanation, and not all the control lines and information lines on the product are necessarily shown. Actually, it may be considered that almost all the components are connected to each other.
Furthermore, the communication means for connecting the devices is not limited to the wireless LAN, but may be changed to a wired LAN or other communication means.

1 management device 2 adapter device (protocol conversion device)
3a Commercial indoor unit (equipment)
3b Commercial remote control 3c Home indoor unit (equipment)
3d home remote control 3p outdoor unit for business use 3q outdoor unit for home use 3x business space 3y home space 8 management network 9 device network 21 device DB (device database)
DESCRIPTION OF SYMBOLS 22 Service execution part 23 Device construction part 24 Model information processing part 25 Management network communication part 26 Equipment network communication part 30 Control part 31 Adapter communication part 32 Model information storage part 33 Operation parameter management part 34 Status acquisition part 35 Setting change part 36 Air conditioning Operation unit 36a Management IF unit 39a Remote control communication unit 39b Outdoor unit communication unit 39c Sensor value acquisition unit 39d Internal device IF unit

Claims (7)

A protocol conversion device that performs protocol conversion between a message communicated in a device network and a message communicated in a management network,
From each equipment device connected to the equipment network, a device public message including an object that is a collection of properties modeling the functions provided by the equipment is received, and the object in the equipment public message is stored in the equipment database. Store and
A device entry message including an object stored in the device database and an address of the management network assigned to the facility device so as to be unique within the management network is sent to the management device via the management network. The protocol conversion apparatus, wherein the equipment is registered in the management apparatus as a device of the management network by transmitting. When the protocol converter receives a property notification message to update the property of the object stored in the device database from the equipment via the device network, the update content is reflected in the device database. The protocol conversion device according to claim 1, wherein when the reflected property content requires a warning, an event notification message indicating the warning is transmitted to the management device via the management network. When the protocol conversion device receives a service write request message for updating the property of the object stored in the device database from the management device via the management network, the update content is reflected in the device database. The protocol conversion according to claim 1, wherein the content of the reflected property is notified to the facility device via the device network to change the control content of the facility device. apparatus. When the protocol conversion device receives a service read request message for reading the property of the object stored in the device database from the management device via the management network, the protocol conversion device reads the corresponding property from the device database. The protocol conversion device according to claim 1, wherein a service read response message including the read property is transmitted to the management device. It is comprised including the protocol converter of any one of Claim 1 thru | or 4, and the said installation apparatus,
The protocol conversion device and a plurality of the equipment devices are connected via the device network,
The protocol conversion system transmits and receives each message to / from a predetermined equipment using a device address assigned to each equipment in the equipment network. It is comprised including the protocol converter of any one of Claim 1 thru | or 4, and the said installation apparatus,
The device network is configured by lines directly connected to each of the plurality of facility devices from the protocol conversion device,
The protocol conversion system, wherein the protocol conversion device transmits and receives each message to and from the predetermined equipment via a directly connected line. A facility device accommodated in a protocol conversion device that performs protocol conversion between a message communicated in a device network and a message communicated in a management network,
By sending a device public message including an object that is a collection of properties modeling the functions provided by itself to the protocol converter, the object in the device public message is stored in the device database in the protocol converter. As well as
By sending a device entry message including an object stored in the device database and an address of the management network that is unique within the management network to the equipment device to the management device via the management network. The equipment is registered in the management apparatus as a device of the management network.

Images