Patent Grant
9816718
This application is a U.S. national stage application of International Application No. PCT/JP2012/056549 filed on Mar. 14, 2012, the disclosure of which is incorporated herein by reference.
The present disclosure relates to a control device, an air conditioning system and an equipment system.
Conventionally, air conditioning systems having multiple air conditioners and a control device thereof connected via a general-purpose network are sometimes installed in large-scale buildings, such as a retail store or an office building. The control device controls the multiple air conditioners in accordance with a preset algorithm. It is disclosed that a system controls indoor device (indoor units) divided into multiple groups beforehand, group by group in order to control the multiple indoor device (indoor units) in a building with minimal operation (see, for example, Patent Literatures 1 and 2).
Moreover, a central managing system that collectively control the multiple air conditioners is required to comprehend the system linkage of the air conditioners. Hence, a central managing system that automatically recognizes a system linkage is disclosed (see, for example, Patent Literature 3).
Patent Literature 1: Unexamined Japanese Patent Application Kokai Publication No 2003-185234
Patent Literature 2: Unexamined Japanese Patent Application Kokai Publication No. 2009-299951
Patent Literature 3: Unexamined Japanese Patent Application Kokai Publication No. 2003-122345
in a retail store or an office building, there are needs to install an energy-saving algorithm in the control device to reduce the electricity charges, and to change a grouping of the air conditioners or the control algorithm flexibly and easily in accordance with changes of a layout and so on.
According to the conventional control devices, however, a grouping registration of the facility devices of the air conditioner and the like is manually carried out. Hence, a large workload is required to modify an air conditioner group to a group more suitable to a situation (for example, better comforts and energy-saving performance).
The present disclosure has been made in view of the aforementioned circumstances, and it is an objective to provide a control device that enables automatic and flexible grouping of facility devices.
To accomplish the above objective, a control device according to the present disclosure controls a plurality of facility devices, and the control device includes: a communicator that receives control information from each of the plurality of facility devices; a control determiner that outputs a control information request for collectively obtaining pieces of the control information of the plurality of facility devices in accordance with a predetermined control algorithm, the control information request containing a condition of the facility devices to be included in a possessing device group possessing the control information to be obtained, and a kind of the control information to be obtained; a connection relationship manager that manages information on a connection relationship among the plurality of facility devices; a connection route database that stores information on a connection route from a reference device in the plurality of facility devices to another facility device; a device grouper that creates the possessing device group based on the connection route database and information managed by the connection relationship manager in accordance with a group creation instruction based on the control information request; and an information collective obtainer that obtains the control information of the facility device in the possessing device group through the communicator, and that creates a data array of the obtained control information.
According to the present disclosure, with reference to information managed by the connection route database that stores information on a connection route from a reference device to another facility device, and by the connection relationship manager based on a condition of the facility device in the possessing device group that possesses control information in the control algorithm based on the connection relationship of the facility device and the kind of the control information to be obtained, and the like, a group of facility devices that automatically and collectively obtain the control information is created. According to this configuration, grouping of the facility devices can be automatically flexibly carried out without manual setting of the group.
Embodiments of the present disclosure will be explained in detail with reference to the accompanying drawings.
First of all, an explanation will be given of a first embodiment of the present disclosure.
Equal to or greater than one outdoor unit, indoor unit, and remote controller, respectively, as air conditioners are connected to communication network 2. In
Each of the remote controllers 6a to 6f is connected to one or more indoor unit. In addition, a central managing controller that is a master remote controller collectively controlling all remote controllers 6a to 6f may be provided in some cases, but it is presumed that no central managing controller is provided in this embodiment.
As illustrated in
The device control determiner 11 decides the control content to each facility device (outdoor unit or indoor unit). The device control determiner 11 is implemented with a program that runs in accordance with a predetermined control algorithm. This program can be updated through an external inputting using a personal computer or the like. The control algorithm can be updated upon this updating.
More specifically, the device control determiner 11 outputs a control information request to collectively obtain control information of the each facility devices in accordance with the executed control algorithm. More specifically, the device control determiner 11 outputs a control information request containing the condition of the facility device in a data managing device group that is a management target, the condition of the facility device in a data possessing device group having control information to be obtained, and the kind of the control information to be obtained.
The data managing device group is a group of devices to be managed actually, and is a device group having a number of array elements of data and an arrangement of respective elements decided when data is obtained. The data possessing device group is a device group having data to be obtained actually.
The device control determiner 11 eventually obtains the control information in a format in accordance with a control algorithm, that is, information having undergone mapping for each grouped device that is a management target. This obtained information is referred to as a mapped group control information set.
In addition, the device control determiner 11 transmits a control instruction containing a device ID and a control information kind to the communicator 17 in accordance with the decided control content.
The connection route database 15 stores information on a connection route from a reference device that is a reference among the multiple facility devices to another facility device. That is, the connection route database 15 stores a connection route indicating a route that should be traced when a device group satisfying a specified connection relationship with the reference device is created. The connection route is information indicating through which route between the reference device and the device t connected therewith information can be transmitted.
An explanation will now be given of the structure of the connection route database 15.
The connection relationship number is an identification number allocated in accordance with a connection relationship. The connection relationship is specified and data is managed based on the connection relationship number. In this embodiment, the connection relationship number corresponds to a condition on a connection relationship.
The reference device attribute is information indicating the attributes of the reference device, that is, the kind of the reference device. Namely, the attributes represents the kind of device, such as “outdoor unit” and “remote controller”.
The connection route attribute array is an array indicating a sequence of the attributes from the reference device to the facility device indicated by the connection relationship number.
The connection route database 15 outputs, when, as a connection route inquiry, the connection relationship number (a condition of a group belonging to the connection relationship) and the reference device attribute are input therein, a corresponding connection route attribute array (a sequence of the attributes of facility devices). As will be discussed later, the device grouper 14 traces the sequence of the attributes in the connection route obtained from the connection route database 15, thereby specifying the facility devices in the data managing device group and the data possessing device group.
In this case, an explanation will be given of, as an example, a connection route from the outdoor unit to the remote controller. A route from the outdoor unit to the closest remote controller is through an indoor unit connected to the outdoor unit and reaches the remote controller connected with that indoor unit. In this case, a connection relationship number that is 3, the closest remote controller, and the outdoor unit that is a reference device attribute are input, and the connection route database 15 outputs an attribute array that is from connected indoor unit ID to connected remote controller ID.
The connection among the devices is often a not one-to-one connection. Every time the connection route is traced, the number of devices obtained as a search result increases or decreases. In addition, in the table in
The connection relationship manager 16 manages information regarding which device each facility device is connected to, that is, information on respective connection relationships of the multiple facility devices. More specifically, the connection relationship manager 16 includes a device attribute database 23, and a connection destination database 24.
An explanation will now be given of the structure of the device attribute database 23.
Next, an explanation will be given of the structure of the connection destination database 24.
The connection relationship manager 16 refers to the device attribute database 23 when receiving an inquiry for the reference device attribute including the device ID, and replies with the reference device attribute. In addition, the connection relationship manager 16 refers to the connection destination database 24 when receiving an inquiry for the connection destination device ID including the device ID from the device grouper 14 or the like, and replies with a device ID set (attribute) of the facility device to which the facility device transmitting the inquiry is directly connected. As will be discussed later, the device grouper 14 traces the sequence of attributes in the connection route based on the attribute of the facility device sent in reply by the connection relationship manager 16.
The device grouper 14 groups the air conditioners. More specifically, the device grouper 14 creates, in accordance with data-managing device-group creating instructions that are output by the device data mapper 12 in accordance with a control information request that is output by the device control determiner 11, a data managing device group based on the connection route database 15 and information managed by the connection relationship manger 16, and replies with a data managing device group ID set. In addition, the device grouper 14 creates, in accordance with a data-possessing device-group creating instructions that are output by the information collective obtainer 13 in accordance with the control information request output by the device control determiner 11, a data managing device group based on the connection route database 15 and information managed by the connection relationship manager 16, and replies a data possessing device group ID set.
The data managing device group creating instruction and the data possessing device group creating instruction have the identification ID of a device (hereinafter, referred to as a “reference device”) that is a reference for a connection, and the way of connection (connection relationship) between the reference device, a refrigerant pipe, a network, and a power line specified. In addition, the data managing device group ID set and the data possessing device group ID set are each a grouped ID set (data managing device ID) of the facility devices satisfying the connection relationship.
The information collective obtainer 13 obtains the control information from the facility device in the data possessing device group via the communicator 17, and creates a data array of the obtained control information. More specifically, the information collective obtainer 13 transmits the data possessing device group creating instruction to the device grouper 14 when receiving a mapping data creation instruction, and receives the data possessing device group ID set from the device grouper 14. The information collective obtainer 13 obtains the control information from each facility device in the data possessing device group ID set via the communicator 17, creates a data array of the control information, and sends a reply such a data array as mapping data to the device data mapper 12.
The device data mapper 12 transmits the data managing device group creating instruction to the device grouper 14 in accordance with the control information request transmitted from the device control determiner 11, and receives the data managing device group ID set. The device data mapper 12 transmits, to the information collective obtainer 13, the condition of the facility device in the data possessing device group possessing the control information to be obtained and contained in the control information request transmitted by the device control determiner 11, and the mapping data creating instruction containing the data managing device group ID set obtained from the device grouper 14, and receives the mapping data from the information collective obtainer 13. The device data mapper 12 allocates the element of the mapping data obtained from the information collective obtainer 13 to the facility device contained in the data managing device group, and replies, as a mapped group control information set, to the device control determiner 11.
The communicator 17 communicates with each air conditioner through the communication network 2 in accordance with the control information inquiry. More specifically, the communicator 17 receives the control information in accordance with the control information inquiry from each air conditioner. The communicator 17 interprets a command when communicating with the air conditioner through the communication network 2, and converts an instruction to the air conditioner into a command. When the device ID and the control information kind are transmitted, the communicator 17 receives the control information of the specified device upon inquiry to the air conditioner.
The communicator 17 transmits a control instruction to each of the multiple facility devices. More specifically, when receiving the control instruction containing the device ID and the control information kind from the control content determiner 11, the communicator 17 transmits, to the air conditioner, the control instruction to control that air conditioner corresponding to the device ID.
Next, an explanation will be given of an operation of the air conditioner control device according to this embodiment.
First, as illustrated in
Next, the device grouper 14 receives, from the device data mapper 12, the data managing device group creating instruction based on the control information request output by the device control determiner 11, and creates the data managing device group (step S2).
Subsequently, the control device 1 maps the control information of a different device onto the created data managing device group (step S3). Hence, the control information of a given device can be obtained as if it is the control information of the different device.
More specifically, the device grouper 14 creates the data possessing device group for each device in the data managing device group (step S31). Next, the information collective obtainer 13 obtains the device information of the data possessing device group, and creates mapping data (step S32). Subsequently, the device data mapper 12 maps the mapping data onto the data managing device group to create mapped group control information (step S32).
Next, the control device 1 determines whether or not mapping to all data managing device group has completed (step S4). When the mapping has not completed yet (step S4; No), the control device 1 repeats the steps S31→S32→S33. When the mapping has completed (step S4; Yes), the device control determiner 11 decides the content of control based on the mapped group control information (step S5). The control device 1 ends the process after the execution of the step S5.
A detail of the mapping operation of the control device will be explained with reference to
In the following explanation, a case in which the suctioning temperatures of the indoor units 5a, 5b, 5c, and 5d in the system of the outdoor unit 4a are obtained as data of the remote controllers 6a, 6b, and 6c in the same system in accordance with a control algorithm will be taken into consideration.
Moreover,
First, the device control determiner 11 transmits the control information request to the device data mapper 12 (step S101). As illustrated in
The reference device ID is the ID of the device that will be a reference point of a connection route when the data managing device group is created. The grouping connection kind is a connection relationship number indicating the connection relationship between the reference device and the data managing device group. The mapping connection kind is a connection relationship number indicating the connection relationship between the data managing device group and the data possessing device group. The control information ID is an ID indicating a kind of control information which is obtained from the data possessing device group.
As explained above, when the suctioning temperatures of the indoor units 5a, 5b, 5c, and 5d in the system of the outdoor unit 4a are obtained as data of the remote controllers 6a, 6b, and 6c in the same system, the reference device is the outdoor unit 4a, the data managing device group is the closest remote controller, the mapping connection kind is the closest indoor unit, and the control information ID is the suctioning temperature. That is, in this case, as illustrated in
The device data mapper 12 that has received the control information request transmits the data managing device group creating instruction to the device grouper 14 to obtain the data managing device group (step S102). The data managing device group creating instruction includes, in the received control information request, the reference device ID and the grouping connection kind.
The device grouper 14 that has received the data managing device group creating instruction transmits a connection route inquiry to the connection route database 15 to obtain the connection route from the reference device to the data managing device group (step S201). Like the data managing device group creating instruction, the connection route inquiry includes the reference device ID and the grouping connection kind.
The connection route database 15 that has received the connection route inquiry transmits a reference device attribute inquiry to the connection relationship manager 16 to obtain the attribute of the reference device (step S202).
The connection relationship manager 16 searches the reference device attribute corresponding to the received reference device ID from the device attribute database 23, and transmits a reference device attribute response that is a search result to the connection route database 15 (step S203). In this case, as illustrated in
Next, the connection route database 15 that has received the reference device attribute response from the connection relationship manager 16 searches the connection route corresponding to the obtained reference device attribute and the grouping connection kind, and replies a grouping connection route that is a search result to the device grouper 14 (step S204). As illustrated in
Subsequently, the device grouper 14 creates a data managing device group while inquiring the connection destination of the device to the connection relationship manager 16 through the grouping connection route (step S2).
First, the device grouper 14 transmits a connection destination device ID inquiry to the connection relationship manager 16 (step S205). In this inquiry, the device with the first attribute in the grouping connection route is inquired among the devices connected with the reference device. The connection relationship manager 16 that has received the connection destination device ID inquiry creates a first data managing device group, and transmits the created group information to the device grouper 14 (step S206). In this case, the device group created through the process of creating the data managing device group will be referred to as a first data managing device group. In this case, as illustrated in
Next, the device grouper 14 and the connection relationship manager 16 executes the processes in the steps S205 and S206 to the first data managing device group, thereby creating a second data managing device group. Thus, the steps S205 and S206 are repeated by the number of elements of the attribute array of the connection route. The processes in the steps S205 and S206 are executed on all elements of the attribute array of the connection route to create the second data managing device group. In this case, as illustrated in
The created data managing device group may contain a redundant element. In such a case, one redundant element is left, but the other elements are eliminated from the array. In this case, when remote controllers connected to respective ones in the indoor unit group {5a, 5b, 5c, 5d} are obtained, such a remote controller group becomes {6a, 6b, 6b, 6c}. In such a case, the device grouper 14 eliminates a redundant element 6b, and changes the remote controller group to be {6a, 6b, 6c}.
Eventually, the device grouper 14 transmits the data managing device group ID set to the device data mapper 12 (step S208).
Next, the device data mapper 12 creates a data possessing device group for each device in the received data managing device group, obtains control information, and maps such information onto the data managing device group (step S3).
First, the device data mapper 12 transmits a mapping data creating instruction for the first device in the data managing device group to the information collective obtainer 13 (step S301). The mapping data is control information for the data possessing device group corresponding to each device in the data managing device group. The first mapping data creating instruction contains the device ID of the first device in the data managing device group, the mapping connection kind, and the control information ID. In this case, the device ID=6a, the mapping connection kind=2. the closest remote controller, and the control information ID=suctioning temperature.
Subsequently, the information collective obtainer 13 transmits a data possessing device group creating instruction to the device grouper 14 (step S302). The data possessing device group creating instruction contains the device ID in the mapping data creating instruction and the mapping connection kind. In this case, the device ID=6a, and the mapping connection kind=2. the closest remote controller.
Next, the device grouper 14 creates a data possessing device group (step S31) through the same scheme as that of the data managing device group (step S2), and transmits the created group to the information collective obtainer 13 (step S304). In this case, a data possessing device group G1 to the indoor unit 6a is {5a}.
Thereafter, the information collective obtainer 13 transmits a control information inquiry to the communicator 17 to obtain control information on each device in the received data possessing device group (step S305). In response to this inquiry, the communicator 17 inquires the control information to the facility device, obtains the control information, and transmits the control information as a reply to the information collective obtainer 13 (step S306). The control information and the device ID correspond to each other one on one, and thus the number of data of reply of control information to one control information inquiry is one.
Subsequently, the information collective obtainer 13 that has obtained device data of all devices in the data possessing device group collects up the device data in an array, thereby creating mapping data (step S32). The information collective obtainer 13 transmits the mapping data to the device data mapper 12 (step S308). In this case, as illustrated in
Next, the device data mapper 12 that has received the mapping data maps the mapping data onto the device in the data managing device group, thereby creating mapped group control information (step S33). Note that mapping means an allocation of information on a device set to another device.
An explanation will now be given of an example case in which the number of elements in the mapping data is equal to or greater than two. When the mapping data has an array including equal to or greater than two elements, the device data mapper 12 obtains an average of the numeric values of all elements in the mapping data. In this case, as illustrated in
The device data mapper 12 repeats the process in the step S3 by the number of devices in the data managing device group, and creates mapped group control information. As illustrated in
Next, the device data mapper 12 transmits the mapped group control information created by aforementioned processes, to the device control determiner 11 (step S401).
The device control determiner 11 that has received the mapped group control information decides the control content for the device through, for example, a numerical calculation based on the obtained mapped group control information. The following is an example of algorithm utilizing the obtained mapped group control information.
The obtained mapped group control information is data including the suctioning temperature of the indoor unit mapped on the remote controller. The device control determiner 11 obtains a difference from data on the set temperature of the remote controller, takes the maximum value of the difference to calculate a necessary power of the air conditioner at this time, and decides the frequency of the outdoor unit that is the reference device.
Subsequently, the device control determiner 11 transmits the device control instruction decided based on the control algorithm to the communicator 17. The communicator 17 converts the control instruction into a command for controlling the air conditioner, and transmits such a command to the air conditioner. Hence, the air conditioner is operated.
As explained above in detail, according to this embodiment, the group of facility devices is automatically created based on the condition of the facility device in the possessing device group possessing control information to be obtained, the kind of the control information to be obtained, and the like, in accordance with the control algorithm on the basis of the connection relationship of the facility devices. According to this scheme, it becomes unnecessary to manually set a group, but grouping of the devices in a format suitable for the control algorithm can be automatically and flexibly carried out. As a result, description and setting of the control algorithm corresponding to a situation more properly (for example, better comforts and energy-saving performance) are facilitated.
In addition, according to this embodiment, the reference device and the connection relationship therewith are specified to trace the connection between the devices at the system's end, thereby automatically creating a device group. Accordingly, even if the device ID of the air conditioner is assigned irregularly or the device ID is spatially infrequent, a device group can be specified with a certain amount of work. Still further, in comparison with a case in which a device group is manually set, incompletion of the setting and an error thereof can be avoided.
Moreover, when the control algorithm of the air conditioner is set, a comparative calculation of information of two different device groups is applied in some cases. Information on respective device groups has difference in the number of elements in an array and the meaning of each element. However, according to this embodiment, information on one device group is reformed as information on another device group, and thus two kinds of information can be handled as information having a consistency in the number of elements and meaning. As a result, it becomes sufficient if a numerical calculation in the control algorithm is set as a calculation for respective simple arrays, and thus the setting for the control algorithm becomes simple and facilitated.
Furthermore, when the number of elements in the mapping data (the number of control information) is equal to or greater than two, an average is obtained in this embodiment, but a representative value, such as a maximum value, a minimum value, or an intermediate value, or, a calculated value based on a predetermined calculation may be utilized. In addition, when the control information of one device is mapped on equal to or greater than two devices, a piece of data may be copied and allocated to multiple devices, or divided into multiple pieces and then allocated to the multiple devices. When an appropriate numerical value to be allocated is selected, the amount of description in the setting for the control algorithm can be reduced, thereby reducing the work time.
Note that the registered content in the connection route database 15 is steady in this embodiment, but information on the connection route of an arbitrary connection relationship through an external input like a PC may be added or modified. In this case, information input to the connection route database 15 is a combination of a connection relationship number, a reference device attribute, and a connection route attribute array. Hence, a necessary connection route for setting the control algorithm in accordance with a site where the air conditioner is utilized can be added as needed, enabling a flexible setting for the control algorithm.
In addition, according to this embodiment, the control device 1 stores and retains the connection information of all devices and the device kinds thereof in the connection destination database 24 and the device attribute database 23. However, an inquiry to the facility device can be made as needed to obtain such information, or a result of an inquiry may be stored in the connection destination database 24 and the device attribute database 23, and every time information not stored becomes necessary, an inquiry for such information may be made to the facility device.
When, as the mapping connection kind, {0. local device} is specified, no mapping of data may be performed, control information on a data managing device group may be obtained through the information collective obtainer 13, and the obtained information may be transmitted to the device control determiner 11. When such data becomes necessary, the device control determiner 11 may be directly obtain the control information on the device from the information collective obtainer 13 not through the device data mapper 12.
According to this embodiment, the device grouper 14 automatically performs device grouping based on the connection relationship of the devices. However, a database that can obtain a connection route based on the reference device and the connection relationship with other facility devices may be created manually.
According to this embodiment, basically, the facility devices are grouped based on the connection relationship over the communication network 2, but the facility devices may be grouped based on a connection relationship through a refrigerant pipe or a power line.
Next, an explanation will be given of a second embodiment of the present disclosure.
According to this embodiment, however, no device data mapper 12 is provided. A control information request from the device control determiner 11 is transmitted to the information collective obtainer 13, and a group control information set from the information collective obtainer 13 is transmitted to the device control determiner 11. That is, according to this embodiment, no data managing device group is created, but only the data possessing device group is created.
The control device 1 of this embodiment further includes a numerical operator 19, and a data reformer 18.
The numerical operator 19 performs a numerical operation in accordance with a numerical operation instruction received from the device control determiner 11. The numerical operation instruction contains control information on two different device groups, a connection relationship between the two grouped devices, and an operation instruction. The numerical operator 19 performs a numerical operation based on the two different control information and the operation instruction, and replies an operation result to the device control determiner 11.
The data reformer 18 receives a data reforming instruction from the numerical operator 19. The data reforming instruction contains, in the numerical operation instruction, control information on two different device groups, two device groups, and a connection relationship between the two grouped devices (connection relationship kind). The data reformer 18 allocates the control information on the one device to another device based on those pieces of information using the device grouper 14, thereby reforming the two control information as the same device group control information.
The numerical operator 19 performs a numerical operation using the control information set formed by the data reformer 18.
In this case, it is presumed that like the control device 1 of the first embodiment, the device control determiner 11 possesses mapping data of control information for the two different device groups transmitted from the information collective obtainer 13, and a device ID set indicating the data possessing device group of such control information.
In addition, it is presumed that like the first embodiment, the air conditioning system 100 employs the configuration illustrated in
As illustrated in
Next, the numerical operator 19 that has received the numerical operation instruction determines whether or not the first data possessing device group and the second data possessing device group are the same (step S12). When the two device groups are the same group (step S12; Yes), the two control information are already in the same format, and thus the control device 1 progresses the process to step S15.
When the two device groups are different groups (step S12; No), the numerical operator 19 transmits a data reforming instruction to the data reformer 18 (step S13). The data reforming instruction contains, in the data contained in the numerical operation instruction, the control information D1, D2, the first and second data possessing device groups G1, G2, and the connection relationship (connection relationship kind) from the data possessing device group G2 to the data possessing device group G1.
Next, the data reformer 18 performs a data reforming process (step S14). The data reforming process is a process of reforming the second control information D2 that is data in the format for the data possessing device group G2 into reformed control information set that is data in the format for the data possessing device group G1.
The data reformer 18 transmits, to the device grouper 14, the connected device group creating instruction for the first device in the second data possessing device group G2 to the device grouper 14 (step S802). In this case, the connected device group indicates the device ID set satisfying a connection relationship with a specified reference device. The connected device group creating instruction contains the reference device ID and the connection relationship. In this case, the reference device ID=6a, and the connection relationship=2. the closest indoor unit.
The procedure of creating the device ID set satisfying the connection relationship by the device grouper 14 is the same as that of the operation (see step S2) of the first embodiment. In this case, as illustrated in
Subsequently, the data reformer 18 that has received the connected device group G3 determines whether or not the first data possessing device group G1 contains the first device in the connected device group (step S803). When the first device is contained (step S803; Yes), the data reformer 18 stores data in the reformed-data storing array (step S804). In this case, the first data of the second control information D2 is stored in the prepared reformed data storing array D3. At this time, it is presumed that the location in the array where the data is stored is the same location as the array order in the first data possessing device group G1 of the searched device. In this case, the first device 5a in the connected device group G3 is the first element in the first data possessing device group G1. Therefore, the data reformer 18 stores the first element of the second control information D2 that is 24 in the first location in the reformed-data storing array.
Conversely, when the first device is not contained (step S803; No), or after executing the process of the step S804, the data reformer 18 determines (step S805) whether or not the process is performed on all devices in the data possessing device group. In this way, the steps S802→S803 (→S804) are performed on all devices in the second data possessing device group G2.
In this case, when the connected device group contains multiple devices in the step S804, the corresponding second control information D2 is stored for the multiple elements in the reformed-data storing array. For example, a connected device group G4 of the second device 6b in the second data possessing device group G2 is {5b, 5c}. In this case, the second element of the second control information D2 that is 23 is stored in the second and third elements of the reformed-data storing array.
When the process on all devices in the data possessing device group completes (step S805; Yes), the data reformer 18 determines whether or not all elements of the reformed-data storing array are filled with data (step S806). When all elements are not filled with the data (step S806; No), an operation is not executable with the reformed data, and thus the data reformer 18 returns an error signal to the numerical operator 19.
When all elements are filled with data (step S806; Yes), the data reformer 18 determines whether or not multiple data are allocated to one element in the reformed-data storing array (step S807). When multiple data are allocated (step S807; Yes), the data reformer 18 obtains an average of the pieces of data allocated to the same array order, and updates the content of the reformed-data storing array (step S808).
When the multiple data are not allocated (step S807; No), or after executing the process of the step S808, the data reformer 18 transmits, as reformed control information set D3, data stored in the reformed-data storing array to the numerical operator 19 (step S809), in this case, as illustrated in
Returning to
Subsequently, the numerical operator 19 transmits the operation result D4 to the device control determiner 11 (step S16). The device control determiner 11 decides the content of control based on the obtained operation result D4. The device control determiner 11 transmits the device control instruction based on the decided control content to the communicator 17. The communicator 17 transmits a command obtained upon conversion on the control content to the air conditioner, thereby operating the air conditioner.
As explained above, according to this second embodiment, when an operation process is performed on the control information of two different device groups, information for the one device group is reformed in the format for another device group. The term format means a number of elements in an array and a layout of respective elements. When the formats of the two control information are unified, operations, such as addition, subtraction, and comparison, can be described as an operation process between simple group information.
Next, an explanation will be given of a third embodiment of the present disclosure.
A device group utilizer 22 receives and utilizes the device group created by the device grouper 14. The device grouping utilizer 22 corresponds to the information collective obtainer 13, the device data mapper 12, and the data reformer 18 of the first and second embodiments.
The installation relationship manager 20 manages information on relationships between multiple facility devices and the installation locations thereof.
The device grouper 14 inquires the equipment relationship manager 25 about the facility devices satisfying a condition of grouping, and groups the facility devices based on the condition of grouping related to an installation and based on the search route read from the installation relationship database 21.
Next, an explanation will be given of an operation of the control device 1 according to this embodiment.
In this embodiment, an explanation will be given of a case in which the device group utilizer 22 transmits a group creating instruction such that “create an indoor unit group installed in the same installation room as the indoor unit 5b” to the device grouper 14.
First, the device group utilizer 22 transmits a device group creating instruction to the device grouper 14 (step S21). The device group creating instruction contains the reference device ID and the relationship kind. The relationship kind indicates either one of the connection relationship or the installation relationship. In this case, the reference device ID=5b, and the relationship kind={100. indoor unit in the same installation room}. That is, the relationship kind indicates the installation relationship.
The device grouper 14 that has received the device group creating instruction determines whether or not the relationship kind in the device group creating instruction is the installation relationship kind (connection relationship kind) (step S22). In this embodiment, when the relationship kind number is 0 to 99, it indicates the connection relationship kind, and when the relationship kind number is equal to or over 100, it indicates the installation relationship kind. In this case, the relationship kind=100, and thus it is determined that the relationship kind indicates the installation relationship kind.
When the relationship kind is not the installation relationship kind (step S22; No), the device grouper 14 creates the device group satisfying the specified connection relationship from the reference device through the same operations (operations indicated by the steps S205, S206, and S207 in
When the relationship kind is the installation relationship kind (step S22; Yes), the device grouper 14 performs an installation related device group creating process (step S50) as explained below.
First, the device grouper 14 obtains an installation relationship search route from the installation relationship database 21 (step S24). More specifically, first, the device grouper 14 transmits an installation relationship search route inquiry to the installation relationship database 21. The installation relationship search route inquiry contains the installation relationship number (see
Subsequently, the device grouper 14 creates the installation related device group while inquiring the installation location manager 20 about the installation location information using the installation relationship search route.
More specifically, the device grouper 14 determines whether or not the element of the installation relationship search route is the installation location kind (device attribute) (step S25).
When the element of the installation relationship search route is the installation location kind (step S25; Yes), the device grouper 14 searches the device in the same installation location, and creates an installation related device quasi-group (step S26). More specifically, the device grouper 14 transmits an installation related device ID inquiry to the installation relationship manager 20. The installation related device ID inquiry contains the reference device ID and the installation relationship search route. The installation relationship manager 20 that has received the installation related device ID inquiry searches the installation location database 25, and sends back an installation related device ID set that is a device ID set of devices in the same installation location as that of the reference device. The device grouper 14 that has received the installation related device ID set creates an installation related device quasi-group.
In this case, the installation related device quasi-group is a device group that will be intermediate data created during a process of creating an installation related device quasi-group through a search route. When an installation related device ID inquiry is transmitted to the reference device, the installation related device ID set replied by the installation relationship manager 20 becomes the installation related device quasi-group. When the installation related device ID inquiry is made to each device in the installation related device quasi-group, the installation related device ID set for all devices is reformed into an array, and a redundancy is eliminated, which will be the installation related device quasi-group.
When the element of the installation relationship search route is not the installation location kind but is the device attribute (step S25; No), the device grouper 14 extracts the element of the specified device attribute (step S27). More specifically, the device grouper 14 transmits the device attribute inquiry to the installation relationship manager 20 for each element of the installation related device quasi-group. The device attribute inquiry contains the device ID. The installation relationship manager 20 that has received the device attribute inquiry searches the device attribute database 23, and replies the device attribute corresponding to the device ID. Only when the device attribute received from the received installation relationship manager 20 is consistent with the device attribute of the element in the installation relationship search route, the device grouper 14 leaves such an element in the installation related device quasi-group, and eliminates the others.
After executing the step S26 or step S27, the device grouper 14 determines whether or not the installation relationship search route is traced to the end (step S28). When the installation relationship search route is not traced to the end (step S28; No), the device grouper 14 returns the process to the step S25.
Thereafter, the device grouper 14 repeatedly performs the process in the step S26 or the step S27 on all elements in the array of the installation relationship search route. The installation related device quasi-group obtained after the installation relationship is traced to the end becomes the installation related device group.
In this case, the first element {installation room ID} of the installation relationship search route is the installation location kind, and thus the devices in the same installation room as the reference device {5b} are searched from the installation location database 25. As a result, the installation related device quasi-group becomes {5b, 5c, 6b}. Next, the second element {indoor unit ID in the room} is the device attribute, and thus only the indoor unit is extracted from the installed device quasi-group, and the installation related device quasi-group becomes {5b, 5c}. This becomes the final installation related device group.
When it is determined that the installation relationship search route is traced to the end (step S28; Yes), or after executing the step S23, the device grouper 14 transmits the group device ID set of the created installation related device group to the device group utilizer 22 (step S29).
As explained above, the device grouper 14 searches, when the element of the search route read from the installation relationship database 21 indicates an installation location, the facility device in that installation location, and creates the installation related device quasi-group. Next, the device grouper 14 leaves, when the element of the search route read from the installation relationship database 21 indicates the attribute of the facility device, only the element matching such an attribute in the installation related device quasi-group. Still further, the device grouper 14 groups the facility device contained in the installation related device quasi-group at a time point at which the search route is traced to the end.
Moreover, the device grouper 14 performs, when the received group creating instruction indicates a grouping based on the connection relationship of the facility devices, grouping based on the connection relationship of the facility devices. Conversely, when the group creating instruction indicates a grouping based on the relationship of the installation locations of the facility devices, the device grouper 14 performs grouping based on the installation relationship of the facility devices.
As explained above, according to this third embodiment, a device group is created based on, in addition to the connection relationship through a refrigerant pipe, a network, and a power line, information on the installation location. According to this scheme, the way of unification of the devices when the device group is created can have various options, and thus a flexible control algorithm can be set up.
In addition, in the case of building tenants like an office, the segmentation of rooms and the layout thereof are relatively frequently changed. However, it becomes possible to cope with such a change by only correcting a database collecting information of the installation locations at that time, thus easy to cope with a layout change.
As to the installation location database 25, the installation relationship database 21, and the installation location database 25, data created manually may be input in advance, or data may be set changeable through an external input using, for example, a personal computer (PC). The respective aforementioned databases have the registered contents updatable through an external device as explained above.
Still further, according to the respective aforementioned embodiments, no diverging controller or no central managing controller is provided, but those may be provided. In this case, the diverging controller or the central managing controller may be included objects controlled by the control device 1.
In the respective aforementioned embodiments, the control-target facility devices are air conditioners, but the present disclosure is not limited to this case, and the control target may be other facility devices, such as a lighting device and home electronics.
The program executed in the aforementioned embodiments may be stored in a computer-readable non-transitory recording medium, such as a flexible disk, a CD-ROM (Compact Disc Read-Only Memory), a DVD (Digital Versatile Disc), or an MO (Magneto-Optical Disc), distributed and installed to configure a system executing the above-explained threads.
Moreover, the program may be stored in a disk device or the like of a predetermined server device over a communication network like the Internet, and may be downloaded in a manner superimposed on, for example, carrier waves.
When the above-explained functions are realized in a manner shared by an OS (Operating System) or realized by a cooperative operation by the OS and an application, only portions other than the OS may be stored in a medium and distributed, or may be downloaded, for example.
The present disclosure can permit various embodiments and modifications thereof without departing from the broadest scope and spirit of the present disclosure. The above-explained embodiments are to explain the present disclosure, and are not intended to limit the present disclosure. That is, the scope and spirit of the present disclosure are indicated by the appended claims rather than the embodiments, Various modifications carried out within the scope of the appended claims and the equivalent range thereto should be within the scope and spirit of the present disclosure.
When the present disclosure is applied, it becomes possible to easily and flexibly set the control algorithm for air conditioners. That is, the present disclosure is useful as a control device that controls air conditioners and a control system including the same. When, for example, the present disclosure is applied, a work time and a setting error can be reduced when the air conditioning control algorithm is changed to an algorithm with an excellent energy saving performance, or when a control method is changed in association with a floor layout change in a building.
| Filing Document | Filing Date | Country | Kind | 371c Date |
|---|---|---|---|---|
| PCT/JP2012/056549 | 3/14/2012 | WO | 00 | 9/11/2014 |
| Publishing Document | Publishing Date | Country | Kind |
|---|---|---|---|
| WO2013/136465 | 9/19/2013 | WO | A |
| Number | Name | Date | Kind |
|---|---|---|---|
| 6085238 | Yuasa | Jul 2000 | A |
| 7321316 | Hancock | Jan 2008 | B2 |
| 8681754 | Ishii | Mar 2014 | B2 |
| 20030070534 | Ookubo | Apr 2003 | A1 |
| 20090080394 | Ishii | Mar 2009 | A1 |
| 20100324962 | Nesler et al. | Dec 2010 | A1 |
| 20110137853 | Mackay | Jun 2011 | A1 |
| Number | Date | Country |
|---|---|---|
| 1953469 | Aug 2008 | EP |
| 06-042800 | Feb 1994 | JP |
| 2003-122345 | Apr 2003 | JP |
| 2003-185234 | Jul 2003 | JP |
| 2007-322104 | Dec 2007 | JP |
| 2008-281241 | Nov 2008 | JP |
| 2009-008341 | Jan 2009 | JP |
| 2009-299951 | Dec 2009 | JP |
| Entry |
|---|
| Extended European Search Report issued Jan. 12, 2016 in the corresponding EP application No. 12871044.9. |
| International Search Report of the International Searching Authority mailed Jun. 5, 2012 for the corresponding international application No. PCT/JP2012/056549 (with English translation). |
| Number | Date | Country | |
|---|---|---|---|
| 20150120003 A1 | Apr 2015 | US |
