CN112084127A - Distributed controller and distributed autonomous system - Google Patents
Distributed controller and distributed autonomous system Download PDFInfo
- Publication number
- CN112084127A CN112084127A CN202010854824.0A CN202010854824A CN112084127A CN 112084127 A CN112084127 A CN 112084127A CN 202010854824 A CN202010854824 A CN 202010854824A CN 112084127 A CN112084127 A CN 112084127A
- Authority
- CN
- China
- Prior art keywords
- protocol
- hardware interface
- layer
- component
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 claims abstract description 25
- 238000012544 monitoring process Methods 0.000 claims abstract description 15
- 230000008569 process Effects 0.000 claims description 17
- 238000012545 processing Methods 0.000 claims description 4
- 230000004044 response Effects 0.000 claims description 4
- 239000000126 substance Substances 0.000 claims description 3
- 230000001960 triggered effect Effects 0.000 claims description 3
- 239000010410 layer Substances 0.000 description 64
- 238000010438 heat treatment Methods 0.000 description 17
- 238000009423 ventilation Methods 0.000 description 16
- 230000006870 function Effects 0.000 description 15
- 238000010586 diagram Methods 0.000 description 7
- 238000004891 communication Methods 0.000 description 6
- 230000005540 biological transmission Effects 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 3
- 239000000463 material Substances 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 239000002346 layers by function Substances 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/42—Bus transfer protocol, e.g. handshake; Synchronisation
- G06F13/4204—Bus transfer protocol, e.g. handshake; Synchronisation on a parallel bus
- G06F13/4221—Bus transfer protocol, e.g. handshake; Synchronisation on a parallel bus being an input/output bus, e.g. ISA bus, EISA bus, PCI bus, SCSI bus
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/382—Information transfer, e.g. on bus using universal interface adapter
- G06F13/387—Information transfer, e.g. on bus using universal interface adapter for adaptation of different data processing systems to different peripheral devices, e.g. protocol converters for incompatible systems, open system
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
Abstract
The application relates to a distributed controller and a distributed automatic control system, and belongs to the technical field of controllers. The hardware interface layer is used for configuring an enabling hardware interface and sending an Inode identifier to the protocol component layer; the protocol component layer is used for configuring a protocol template component for the enabled hardware interface, acquiring data corresponding to the enabled hardware interface through the Inode identifier and analyzing the data by utilizing the corresponding protocol template component; the point location logic layer is used for receiving the analysis data sent by the protocol component layer and the corresponding protocol template component and storing the analysis data and the corresponding protocol template component in a database; and marking the data bits of the corresponding analysis data according to the protocol template component to obtain a unique identifier corresponding to each functional point, and monitoring by utilizing various logic components based on the unique identifier. By the method and the device, the problem that monitoring management is hindered by bottom-layer heterogeneous system differences is solved.
Description
Technical Field
The application belongs to the technical field of controllers, and particularly relates to a distributed controller and a distributed automatic control system.
Background
The intelligent building automatic control system carries all intelligent subsystems, most of the automatic control systems adopt a centralized control management architecture, an upper computer uniformly and centrally manages all the subsystems, all subsystem equipment is vertically integrated longitudinally, and is integrated and accessed to the upper computer through various open standard protocols, so that the following problems exist, and when the equipment interfaces are incompatible, the equipment interfaces are additionally converted and accessed to the upper computer through a protocol conversion gateway; data is managed in a unified and centralized mode, and when an upper computer is down, the whole system is easy to crash and data is easy to lose; the linkage logic data of the subsystems must be processed by an upper computer, and the performance requirement of the upper computer is high; when new function requirements are added, the original structure is greatly changed, and the normal operation and maintenance of the building are influenced, so that various manufacturers propose respective schemes of distributed systems.
Building distributed autonomous systems on the market at present realize distributed system architecture with the regional management of building controller, but most of existing distributed controllers can only access to the system interface that originally sets up, for example building controller has an RS485 interface, and this RS485 interface only supports the access of inside original integrated protocol, for example supports Modbus RTU and DLT645 protocol, and this RS485 interface can be compatible to the equipment of opening these two protocols, but can't be compatible other protocols.
Disclosure of Invention
In order to overcome the problems in the related art at least to a certain extent, the application provides a distributed controller and a distributed automatic control system, which are beneficial to solving the problem that the monitoring management is hindered by the difference of a bottom heterogeneous system.
In order to achieve the purpose, the following technical scheme is adopted in the application:
in a first aspect,
the application provides a distributed controller, includes:
the hardware interface layer is configured with a plurality of drive library files which form corresponding relations with a plurality of hardware interfaces;
the protocol component layer is configured with a plurality of protocol template components;
the point location logic layer is configured with a database and a plurality of logic components;
wherein the content of the first and second substances,
the hardware interface layer is used for configuring an enabled hardware interface and sending an Inode identifier to the protocol component layer;
the protocol component layer is used for configuring a protocol template component for an enabled hardware interface, acquiring data corresponding to the enabled hardware interface through the Inode identifier and analyzing the data by using the corresponding protocol template component;
the point location logic layer is used for receiving the analysis data sent by the protocol component layer and the corresponding protocol template component and storing the analysis data and the corresponding protocol template component in the database; and marking the data bits of the corresponding analysis data according to the protocol template component to obtain a unique identifier corresponding to each functional point, and monitoring by utilizing various logic components based on the unique identifier.
Further, the hardware interface layer is configured to enable a hardware interface, including:
enabling the corresponding drive library file in response to an enabling request of a user for a specified hardware interface; and/or the presence of a gas in the gas,
and enabling the corresponding drive library file when detecting that the hardware interface forms electric connection.
Further, the protocol component layer is configured to configure a protocol template component for the enabled hardware interface, and includes:
responding to a protocol configuration request submitted by a user aiming at an enabled hardware interface, and configuring a protocol template component for the enabled hardware interface; and/or the presence of a gas in the gas,
and acquiring the protocol type information of the equipment connected with the enabled hardware interface through the Inode identifier, and configuring a protocol template component for the enabled hardware interface according to the acquired protocol type information.
Furthermore, the hardware interface layer is provided with a hardware interface library for storing various drive library files and carrying out unified call management on the various drive library files through a Daemon process;
the protocol component layer is provided with a protocol module library used for storing various protocol template components.
Further, the point location logic layer performs monitoring processing by using various logic components based on the unique identifier, including:
generating a corresponding service process according to the logic component, wherein the service process acquires point location data in the database through the unique identifier;
and carrying out logic judgment through the logic component according to the point location data, and issuing a corresponding control instruction to corresponding equipment through the unique identifier when a judgment condition is triggered.
Further, the issuing a corresponding control instruction to a corresponding device through the unique identifier includes:
and finding the protocol template component corresponding to the corresponding equipment through the unique identifier, and issuing the corresponding control instruction to the corresponding equipment through a corresponding hardware interface.
Further, the distributed controller further includes:
and the business service layer is configured with a plurality of platform protocol templates and is used for configuring corresponding platform protocol templates for the upper computer, responding to a data request of the upper computer and transmitting data in the database to the upper computer by using the configured platform protocol templates.
Further, the data in the database are transmitted to the upper computer by using the configured platform protocol template, and the method comprises the following steps:
and when the upper computer requests data through the unique identifier, acquiring corresponding point location data in the database according to the unique identifier, forming a new protocol frame according to a configured platform protocol template, and transmitting the point location data to the upper computer by using the new protocol frame.
In a second aspect of the present invention,
the application provides a distributed autonomous system, includes:
an upper computer; and
a plurality of the distributed controllers described in any one of the above, each connected to the upper computer.
Furthermore, the distributed automatic control system is a building distributed automatic control system.
This application adopts above technical scheme, possesses following beneficial effect at least:
through the function framework of the distributed controller, the driver library file and the protocol template component can be expanded and configured in the hardware interface layer and the protocol component layer, flexible configuration of the heterogeneous protocol template component can be achieved, different protocols of different subsystem equipment can be compatible, the unique identifier of each function point position can be obtained through the point position logic layer, monitoring and management can be conducted on the protocol heterogeneous subsystem equipment, and therefore the problem that monitoring and management are hindered by differences of a bottom heterogeneous system is facilitated to be solved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a functional architecture diagram of a distributed controller, shown in accordance with an exemplary embodiment;
FIG. 2 is a flow diagram illustrating a point location configuration in accordance with an exemplary embodiment;
FIG. 3 is a schematic diagram illustrating data bit markers under the heating and ventilation system Modbus protocol in accordance with an exemplary embodiment;
FIG. 4 is a schematic diagram of a distributed automation system in accordance with an exemplary embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail below. It is to be understood that the embodiments described are only a few embodiments of the present application and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the examples given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, fig. 1 is a schematic diagram illustrating a functional architecture of a distributed controller according to an exemplary embodiment, and as shown in fig. 1, the distributed controller 11 includes:
the hardware interface layer is configured with a plurality of drive library files which form corresponding relations with a plurality of hardware interfaces;
the protocol component layer is configured with a plurality of protocol template components;
the point location logic layer is configured with a database and a plurality of logic components;
wherein the content of the first and second substances,
the hardware interface layer is used for configuring an enabled hardware interface and sending an Inode identifier to the protocol component layer;
the protocol component layer is used for configuring a protocol template component for an enabled hardware interface, acquiring data corresponding to the enabled hardware interface through the Inode identifier, analyzing the data by using the corresponding protocol template component, and storing the analyzed data and the corresponding protocol template component in the database;
the point location logic layer is used for marking data bits of corresponding data according to a protocol template to obtain a unique identifier corresponding to each functional point location, and monitoring by utilizing various logic components based on the unique identifier.
As shown in fig. 1, the present application provides a new function hierarchy architecture of a distributed controller, which helps to make the internal logic implementation of the distributed controller more flexible and the function extension of each hierarchy more excellent. The functional layer levels are further explained below.
As shown in fig. 1, in an embodiment, the hardware interface layer has a hardware interface library for storing various drive library files, and performs unified call management on the various drive library files through a Daemon process; the protocol component layer is provided with a protocol module library used for storing various protocol template components.
The hardware interface layer CAN be configured with a hardware interface library to store various drive library files corresponding to various hardware interfaces, taking a building controller as an example, common hardware interfaces of a building are CAN, RS485, ethernet interfaces and the like, each hardware interface forms a corresponding drive library file, a user CAN add the corresponding drive library file in the hardware interface layer by himself, for example, the RS485 communication interface generates librs485.so, the CAN communication interface generates libcan. so, the ethernet communication interface libeth. so and the like, and CAN carry out unified calling management through a Daemon process, so that the drive library files are not interfered with each other, each drive library file CAN be equivalent to a plug-in, the hardware interface layer CAN realize plug-in type management through the Daemon process, so that the enabled hardware interface is realized, and the data transmission function of the related hardware interface is configured and completed.
The protocol component layer may be configured with a protocol template library to store various protocol template components (specifically as shown in fig. 1), so as to implement various heterogeneous protocol integration. In practical application, a user can write a protocol template component into a jar packet through a java language and perform corresponding calling, the user can add the corresponding jar packet in a protocol component layer, for example, the Modbus protocol is used for communication in a heating and ventilation system, the data can be analyzed by calling the corresponding Modbus. Similarly, each protocol template component can be equivalent to a plug-in, and plug-in management of each protocol template component can be realized through a protocol component layer, so that flexible configuration of heterogeneous protocol template components can be realized, and different protocols of different subsystems are compatible.
In one embodiment, the hardware interface layer is to configure an enabled hardware interface, including:
and enabling the corresponding drive library file in response to an enabling request of a user for the specified hardware interface.
Specifically, the user may complete configuring the hardware interface layer by operating the enabled corresponding drive library file on the upper computer according to a specific interface of the access device. For example, the heating and ventilation system adopts an RS485 interface, a user can perform configuration operation on an upper computer, an enable request is sent to the RS485 interface where the controller is connected with the heating and ventilation system, and the hardware interface layer enables a corresponding drive library file through Daemon to enable the hardware interface to become an enable hardware interface.
In another embodiment, the hardware interface layer is to configure an enabled hardware interface, including:
and enabling the corresponding drive library file when detecting that the hardware interface forms electric connection.
The scheme is that the hardware interface layer carries out automatic enabling configuration according to the accessed hardware interface. Specifically, for example, when the user accesses the RS485 interface of the heating and ventilation system to the controller, the hardware interface layer detects that the hardware interface forms an electrical connection, and thus, the hardware interface layer enables the driver library file corresponding to the hardware interface through the Daemon process, and the hardware interface becomes an enabled hardware interface.
After the hardware interface layer is configured with an enabled hardware interface, the hardware interface layer correspondingly sends an Inode identifier to the protocol component layer.
In one embodiment, the protocol component layer is configured to configure a protocol template component for an enabled hardware interface, comprising:
the protocol template component is configured for the enabled hardware interface in response to a protocol configuration request submitted by a user for the enabled hardware interface.
Specifically, for example, the heating and ventilation system uses a Modbus protocol for communication, and a user configures a protocol component layer through an upper computer according to the Modbus protocol adopted by the heating and ventilation system, operates on the upper computer, submits a protocol configuration request to an enabling hardware interface corresponding to the heating and ventilation system, and configures a Modbus protocol template component to the enabling hardware interface corresponding to the heating and ventilation system.
In another embodiment, the protocol component layer is configured to configure a protocol template component for an enabled hardware interface, comprising:
and acquiring the protocol type information of the equipment connected with the enabled hardware interface through the Inode identifier, and configuring a protocol template component for the enabled hardware interface according to the acquired protocol type information.
Specifically, after the hardware interface layer is configured with an enabled hardware interface, the hardware interface layer correspondingly sends an Inode identifier to the protocol component layer. Still taking the example of using the Modbus protocol to perform communication in the heating and ventilation system, the protocol component layer determines the enabled hardware interface corresponding to the heating and ventilation system by receiving the Inode identifier to obtain some information of the heating and ventilation system, where the information includes protocol type information of the heating and ventilation system, and the like.
Different system devices transmit data through different transmission protocols, for example, a heating and ventilation system transmits data by using a Modbus protocol, and after a protocol component layer configures corresponding protocol template components for different enabled hardware interfaces, the protocol component layer can further determine corresponding enabled hardware interfaces according to the Inode identifier and acquire the data transmitted by the corresponding system devices. And acquiring data corresponding to the enabled hardware interface through the Inode identifier, and analyzing the data by using a corresponding protocol template component, thereby being beneficial to solving the problem of data acquisition caused by the difference of a bottom heterogeneous system.
And the protocol component layer sends the analysis data and the corresponding protocol template component to the point location logic layer, and the point location logic layer stores the analysis data and the corresponding protocol template component in a database. In practical applications, as shown in fig. 1, the database may be a Redis database.
In a specific application, a user may perform point location configuration on the function points of each subsystem device through the upper computer, where each function point of each subsystem device is described by a point location, for example, the on/off function of an air conditioner internal unit in the heating and ventilation system is described as one function point location in the distributed controller 11. Referring to fig. 2, fig. 2 is a schematic flow chart illustrating point location configuration according to an exemplary embodiment, where the point location configuration of each function point is completed through a unique identifier corresponding to each function point. The point location logic layer obtains the unique identifier of each functional point location of each system device by using the stored analysis data and the corresponding protocol template component. Specifically, the point location logic layer performs data bit marking on corresponding data according to the protocol template to obtain a unique identifier corresponding to each functional point location, please refer to fig. 3, where fig. 3 is a schematic diagram illustrating data bit marking under the Modbus protocol of the heating and ventilation system according to an exemplary embodiment. And after the point location logic layer obtains the unique identifier of each functional point location of each system device, logic monitoring is carried out on each bottom layer heterogeneous system device according to the unique identifier, and edge side monitoring management is carried out on each system device.
In the method, the point location logic layer marks corresponding data according to the protocol template to obtain unique identifiers corresponding to the functional point locations, logic monitoring is performed on the bottom heterogeneous system devices according to the unique identifiers, the problem that monitoring management is hindered by differences of the bottom heterogeneous system devices can be solved, interconnection and intercommunication of subsystem data can be achieved, multi-service data are concurrently processed, and accordingly regional data autonomy is achieved.
In one embodiment, the point location logic layer performs monitoring processing using a variety of logic components based on the unique identifier, including:
generating a corresponding service process according to the logic component, wherein the service process acquires point location data in the database through the unique identifier;
and carrying out logic judgment through the logic component according to the point location data, and issuing a corresponding control instruction to corresponding equipment through the unique identifier when a judgment condition is triggered.
Further, the issuing a corresponding control instruction to a corresponding device through the unique identifier includes:
and finding the protocol template component corresponding to the corresponding equipment through the unique identifier, and issuing the corresponding control instruction to the corresponding equipment through a corresponding hardware interface.
Specifically, as shown in fig. 1, the point location logic layer stores various logic components, which can be managed by logic processes in a unified manner, taking a logic component as an example, when detecting that there exists a py logic file, a corresponding service process is generated, the service process acquires point data in the Redis database through a unique identifier, the monitored point location is logically determined through the py logic file, when the building controller acquires input condition trigger in the logic condition, for example, when detecting trigger information of an infrared detector in a corridor, the building controller performs relevant control according to configuration logic output conditions, for example, automatically turning on equipment in a certain room, such as electric lamps, air conditioners and the like, the building controller finds out relevant subsystem equipment protocol component template information through the unique identifier, and completes control through a corresponding hardware interface and sends the information to relevant subsystem equipment, the logic control of the subsystem can be realized on the edge side of the building controller without the logic judgment of an upper computer platform.
Referring to fig. 1, in an embodiment, the distributed controller 11 further includes:
the service layer is used for configuring corresponding platform protocol templates for the upper computer, responding to a data request of the upper computer and transmitting data in the database to the upper computer by using the configured platform protocol templates.
Specifically, the business service layer is configured with a plurality of platform protocol templates, plug-in management can be performed on each platform protocol template according to the transmission protocol type of the upper computer, and then flexible configuration of heterogeneous platform protocol templates can be realized to enable the platform protocol templates to be upwards compatible with a specific transmission protocol of the upper computer, so that data in the point logic layer database is uploaded to the upper computer through a unified protocol interface.
In one embodiment, the transmitting data in the database to the upper computer by using the configured platform protocol template includes:
and when the upper computer requests data through the unique identifier, acquiring corresponding point location data in the database according to the unique identifier, forming a new protocol frame according to a configured platform protocol template, and transmitting the point location data to the upper computer by using the new protocol frame.
Referring to fig. 4, fig. 4 is a schematic structural diagram illustrating a distributed automation system according to an exemplary embodiment, and as shown in fig. 4, the distributed automation system 1 includes:
an upper computer 12; and
the distributed controllers 11 are connected to the upper computer 12.
With regard to the distributed automation system 1 in the above embodiment, the specific implementation thereof has been described in detail in the above related embodiment, and will not be elaborated herein.
Further, the distributed autonomous system 1 may be a building distributed autonomous system 1.
Specifically, the upper computer 12 is connected to each distributed controller 11, and each distributed controller 11 is connected to each corresponding subsystem (for example, a heating and ventilating subsystem, a lighting subsystem, etc.)
The distributed autonomous system 1 can also be applied to management of plant equipment and the like.
It is understood that the same or similar parts in the above embodiments may be mutually referred to, and the same or similar parts in other embodiments may be referred to for the content which is not described in detail in some embodiments.
It should be noted that, in the description of the present application, the terms "first", "second", etc. are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. In addition, in the description of the present application, the meaning of "plurality" means at least two unless otherwise specified.
It will be understood that when an element is referred to as being "secured to" or "disposed on" another element, it can be directly on the other element or intervening elements may also be present; when an element is referred to as being "connected" to another element, it can be directly connected to the other element or intervening elements may also be present, and further, as used herein, connected may include wirelessly connected; the term "and/or" is used to include any and all combinations of one or more of the associated listed items.
Any process or method descriptions in flow charts or otherwise described herein may be understood as: represents modules, segments or portions of code which include one or more executable instructions for implementing specific logical functions or steps of a process, and the scope of the preferred embodiments of the present application includes other implementations in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the embodiments of the present application.
It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.
In addition, functional units in the embodiments of the present application may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium.
The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc.
In the description herein, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
Although embodiments of the present application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present application, and that variations, modifications, substitutions and alterations may be made to the above embodiments by those of ordinary skill in the art within the scope of the present application.
Claims (10)
1. A distributed controller, comprising:
the hardware interface layer is configured with a plurality of drive library files which form corresponding relations with a plurality of hardware interfaces;
the protocol component layer is configured with a plurality of protocol template components;
the point location logic layer is configured with a database and a plurality of logic components;
wherein the content of the first and second substances,
the hardware interface layer is used for configuring an enabled hardware interface and sending an Inode identifier to the protocol component layer;
the protocol component layer is used for configuring a protocol template component for an enabled hardware interface, acquiring data corresponding to the enabled hardware interface through the Inode identifier and analyzing the data by using the corresponding protocol template component;
the point location logic layer is used for receiving the analysis data sent by the protocol component layer and the corresponding protocol template component and storing the analysis data and the corresponding protocol template component in the database; and marking the data bits of the corresponding analysis data according to the protocol template component to obtain a unique identifier corresponding to each functional point, and monitoring by utilizing various logic components based on the unique identifier.
2. The distributed controller of claim 1, wherein the hardware interface layer is configured to enable a hardware interface, comprising:
enabling the corresponding drive library file in response to an enabling request of a user for a specified hardware interface; and/or the presence of a gas in the gas,
and enabling the corresponding drive library file when detecting that the hardware interface forms electric connection.
3. The distributed controller of claim 1, wherein the protocol component layer is configured to configure a protocol template component for an enabled hardware interface, comprising:
responding to a protocol configuration request submitted by a user aiming at an enabled hardware interface, and configuring a protocol template component for the enabled hardware interface; and/or the presence of a gas in the gas,
and acquiring the protocol type information of the equipment connected with the enabled hardware interface through the Inode identifier, and configuring a protocol template component for the enabled hardware interface according to the acquired protocol type information.
4. The distributed controller according to any one of claims 1 to 3,
the hardware interface layer is provided with a hardware interface library and is used for storing various drive library files and carrying out unified calling management on the various drive library files through a Daemon process;
the protocol component layer is provided with a protocol module library used for storing various protocol template components.
5. The distributed controller of claim 1, wherein the point location logic performs monitoring processing with a variety of logic components based on the unique identifier, including:
generating a corresponding service process according to the logic component, wherein the service process acquires point location data in the database through the unique identifier;
and carrying out logic judgment through the logic component according to the point location data, and issuing a corresponding control instruction to corresponding equipment through the unique identifier when a judgment condition is triggered.
6. The distributed controller according to claim 5, wherein said issuing a corresponding control instruction to a corresponding device through the unique identifier comprises:
and finding the protocol template component corresponding to the corresponding equipment through the unique identifier, and issuing the corresponding control instruction to the corresponding equipment through a corresponding hardware interface.
7. The distributed controller of claim 1, further comprising:
and the business service layer is configured with a plurality of platform protocol templates and is used for configuring corresponding platform protocol templates for the upper computer, responding to a data request of the upper computer and transmitting data in the database to the upper computer by using the configured platform protocol templates.
8. The distributed controller of claim 7, wherein said transmitting data in said database to said host computer using a configured platform protocol template comprises:
and when the upper computer requests data through the unique identifier, acquiring corresponding point location data in the database according to the unique identifier, forming a new protocol frame according to a configured platform protocol template, and transmitting the point location data to the upper computer by using the new protocol frame.
9. A distributed automation system, comprising:
an upper computer; and
a plurality of the distributed controllers of any one of claims 1-8, each connected to the upper computer.
10. The distributed automation system of claim 9 wherein the distributed automation system is a building distributed automation system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010854824.0A CN112084127B (en) | 2020-08-24 | 2020-08-24 | Distributed controller and distributed autonomous system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010854824.0A CN112084127B (en) | 2020-08-24 | 2020-08-24 | Distributed controller and distributed autonomous system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112084127A true CN112084127A (en) | 2020-12-15 |
| CN112084127B CN112084127B (en) | 2022-04-22 |
Family
ID=73728575
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010854824.0A Active CN112084127B (en) | 2020-08-24 | 2020-08-24 | Distributed controller and distributed autonomous system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112084127B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115037778A (en) * | 2022-05-25 | 2022-09-09 | 珠海格力电器股份有限公司 | Terminal equipment and building autonomous system |
| CN117408763A (en) * | 2023-12-15 | 2024-01-16 | 珠海格力电器股份有限公司 | Charging management method, system, equipment and storage medium for building control system |
Citations (25)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO1999053414A1 (en) * | 1998-03-27 | 1999-10-21 | Innovex Technologies, Inc. | Distributed architecture |
| US20090285233A1 (en) * | 2008-04-18 | 2009-11-19 | Arris | Multi-service phy box |
| CH701294A1 (en) * | 2009-06-18 | 2010-12-31 | Archimede Solutions Sarl | multi-protocol system monitoring and management of heterogeneous smart objects. |
| CN201845437U (en) * | 2010-08-06 | 2011-05-25 | 厦门市成利吉智能交通科技有限公司 | Multi-protocol traffic signal controller |
| CN102595365A (en) * | 2012-03-08 | 2012-07-18 | 北京神州数码思特奇信息技术股份有限公司 | Business component-based development method |
| CN103812953A (en) * | 2014-02-25 | 2014-05-21 | 中标软件有限公司 | Communication interface system of micro-control unit and ARM (advanced RISC (reduced instruction-set computer) machines) processor |
| CN104104674A (en) * | 2014-07-01 | 2014-10-15 | 广东艾科技术股份有限公司 | Multiprotocol distributed data acquisition control system of equipment sensor and method thereof |
| US20140371878A1 (en) * | 2013-06-13 | 2014-12-18 | Samsung Electronics Co., Ltd. | Communication apparatus and method of controlling the same |
| CN104239478A (en) * | 2014-09-04 | 2014-12-24 | 上海帝联信息科技股份有限公司 | File monitoring method and device |
| CN104462147A (en) * | 2013-09-25 | 2015-03-25 | 天津书生投资有限公司 | Storage method for document |
| US20160043549A1 (en) * | 2013-03-13 | 2016-02-11 | Prolucid Technologies Inc. | Distributed micro-grid controller |
| CN105607568A (en) * | 2015-12-22 | 2016-05-25 | 中国电子信息产业集团有限公司第六研究所 | Communication system of safety PLC multiple physical interfaces based on domestic SPARC CPU |
| CN106059833A (en) * | 2016-07-28 | 2016-10-26 | 武汉虹信技术服务有限责任公司 | Multi-protocol adaptation method and system applied to intelligent building platform |
| CN107222458A (en) * | 2017-04-17 | 2017-09-29 | 珠海格力电器股份有限公司 | A kind of data processing method and system of the BACnet protocol stacks of compatible Modbus agreements |
| CN108052086A (en) * | 2017-12-28 | 2018-05-18 | 珠海格力智能装备技术研究院有限公司 | Data collecting system |
| CN108616506A (en) * | 2018-03-23 | 2018-10-02 | 中国科学院软件研究所 | A kind of intelligent building real time data distributed integeration control method |
| CN208255662U (en) * | 2018-06-29 | 2018-12-18 | 浙江慧控科技有限公司 | A kind of distribution building automation device |
| CN109189031A (en) * | 2018-10-22 | 2019-01-11 | 暨南大学 | Dcs, method and application with layered framework |
| CN109634881A (en) * | 2018-11-16 | 2019-04-16 | 中国航空工业集团公司洛阳电光设备研究所 | A kind of gigabit Ethernet DMA data transfer design device based on FPGA |
| CN109906444A (en) * | 2016-09-05 | 2019-06-18 | Iot耐科特有限公司 | The equipment interface system and method for software definition |
| CN110036619A (en) * | 2016-12-27 | 2019-07-19 | 英特尔Ip公司 | Frame for IOT protocol-identifier and management |
| CN110362009A (en) * | 2019-07-15 | 2019-10-22 | 珠海格力电器股份有限公司 | Configuration logic generation method, device and the building system of building system |
| CN110401187A (en) * | 2019-07-17 | 2019-11-01 | 北京交通大学 | Temperature control load layering aggregation control method towards intelligent building |
| CN209605349U (en) * | 2019-01-21 | 2019-11-08 | 珠海格力电器股份有限公司 | A kind of group control system |
| CN210573263U (en) * | 2019-07-15 | 2020-05-19 | 珠海格力电器股份有限公司 | Building system |
-
2020
- 2020-08-24 CN CN202010854824.0A patent/CN112084127B/en active Active
Patent Citations (25)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO1999053414A1 (en) * | 1998-03-27 | 1999-10-21 | Innovex Technologies, Inc. | Distributed architecture |
| US20090285233A1 (en) * | 2008-04-18 | 2009-11-19 | Arris | Multi-service phy box |
| CH701294A1 (en) * | 2009-06-18 | 2010-12-31 | Archimede Solutions Sarl | multi-protocol system monitoring and management of heterogeneous smart objects. |
| CN201845437U (en) * | 2010-08-06 | 2011-05-25 | 厦门市成利吉智能交通科技有限公司 | Multi-protocol traffic signal controller |
| CN102595365A (en) * | 2012-03-08 | 2012-07-18 | 北京神州数码思特奇信息技术股份有限公司 | Business component-based development method |
| US20160043549A1 (en) * | 2013-03-13 | 2016-02-11 | Prolucid Technologies Inc. | Distributed micro-grid controller |
| US20140371878A1 (en) * | 2013-06-13 | 2014-12-18 | Samsung Electronics Co., Ltd. | Communication apparatus and method of controlling the same |
| CN104462147A (en) * | 2013-09-25 | 2015-03-25 | 天津书生投资有限公司 | Storage method for document |
| CN103812953A (en) * | 2014-02-25 | 2014-05-21 | 中标软件有限公司 | Communication interface system of micro-control unit and ARM (advanced RISC (reduced instruction-set computer) machines) processor |
| CN104104674A (en) * | 2014-07-01 | 2014-10-15 | 广东艾科技术股份有限公司 | Multiprotocol distributed data acquisition control system of equipment sensor and method thereof |
| CN104239478A (en) * | 2014-09-04 | 2014-12-24 | 上海帝联信息科技股份有限公司 | File monitoring method and device |
| CN105607568A (en) * | 2015-12-22 | 2016-05-25 | 中国电子信息产业集团有限公司第六研究所 | Communication system of safety PLC multiple physical interfaces based on domestic SPARC CPU |
| CN106059833A (en) * | 2016-07-28 | 2016-10-26 | 武汉虹信技术服务有限责任公司 | Multi-protocol adaptation method and system applied to intelligent building platform |
| CN109906444A (en) * | 2016-09-05 | 2019-06-18 | Iot耐科特有限公司 | The equipment interface system and method for software definition |
| CN110036619A (en) * | 2016-12-27 | 2019-07-19 | 英特尔Ip公司 | Frame for IOT protocol-identifier and management |
| CN107222458A (en) * | 2017-04-17 | 2017-09-29 | 珠海格力电器股份有限公司 | A kind of data processing method and system of the BACnet protocol stacks of compatible Modbus agreements |
| CN108052086A (en) * | 2017-12-28 | 2018-05-18 | 珠海格力智能装备技术研究院有限公司 | Data collecting system |
| CN108616506A (en) * | 2018-03-23 | 2018-10-02 | 中国科学院软件研究所 | A kind of intelligent building real time data distributed integeration control method |
| CN208255662U (en) * | 2018-06-29 | 2018-12-18 | 浙江慧控科技有限公司 | A kind of distribution building automation device |
| CN109189031A (en) * | 2018-10-22 | 2019-01-11 | 暨南大学 | Dcs, method and application with layered framework |
| CN109634881A (en) * | 2018-11-16 | 2019-04-16 | 中国航空工业集团公司洛阳电光设备研究所 | A kind of gigabit Ethernet DMA data transfer design device based on FPGA |
| CN209605349U (en) * | 2019-01-21 | 2019-11-08 | 珠海格力电器股份有限公司 | A kind of group control system |
| CN110362009A (en) * | 2019-07-15 | 2019-10-22 | 珠海格力电器股份有限公司 | Configuration logic generation method, device and the building system of building system |
| CN210573263U (en) * | 2019-07-15 | 2020-05-19 | 珠海格力电器股份有限公司 | Building system |
| CN110401187A (en) * | 2019-07-17 | 2019-11-01 | 北京交通大学 | Temperature control load layering aggregation control method towards intelligent building |
Non-Patent Citations (9)
| Title |
|---|
| 周法福: "200mm硅外延软件控制系统的设计与实现", 《中国优秀硕士学位论文全文数据库 (电子期刊)》 * |
| 姜婷婷等: "一种NMR谱仪控制台软件系统的多层架构设计", 《波谱学杂志》 * |
| 廉洁; 黄向华; 王偎蕲: "航空发动机控制软件组态软件的设计与实现", 《测控技术》 * |
| 张文佳: "基于Linux的嵌入式控制系统软件设计", 《中国优秀硕士学位论文全文数据库 (电子期刊)》 * |
| 李福荣; 李心科: "一种高可扩展的软件定义网络控制平面架构", 《信息技术》 * |
| 王海燕等: "CANopen在大功率风力发电机组控制器上的应用", 《微计算机信息》 * |
| 王瑞华,王普,尹金玉,张红: "基于TCPIP的楼宇自控网BACnet", 《测控技术》 * |
| 王跃宣等: "多层分布式先进控制软件及其应用", 《浙江大学学报(工学版)》 * |
| 田佩龙: "基于BIM与建筑自动化系统的设备运维期监控与管理", 《中国优秀硕士学位论文全文数据库 (电子期刊)》 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115037778A (en) * | 2022-05-25 | 2022-09-09 | 珠海格力电器股份有限公司 | Terminal equipment and building autonomous system |
| CN115037778B (en) * | 2022-05-25 | 2023-08-18 | 珠海格力电器股份有限公司 | Terminal equipment and building automatic control system |
| CN117408763A (en) * | 2023-12-15 | 2024-01-16 | 珠海格力电器股份有限公司 | Charging management method, system, equipment and storage medium for building control system |
| CN117408763B (en) * | 2023-12-15 | 2024-05-03 | 珠海格力电器股份有限公司 | Charging management method, system, equipment and storage medium for building control system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112084127B (en) | 2022-04-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106878459B (en) | Self-adaptive Internet of things intelligent gateway implementation method and equipment thereof | |
| CN108173874B (en) | Intelligent device management method, platform, system, medium and device | |
| US20190379733A1 (en) | Method and device for managing data in internet of things, computer device and readable medium | |
| CN112084127B (en) | Distributed controller and distributed autonomous system | |
| US20110071685A1 (en) | Creation and use of software defined building objects in building management systems and applications | |
| US20040039459A1 (en) | Universal device control | |
| JPH11501491A (en) | Method for initializing a wireless packet hopping network | |
| CN111727410B (en) | Discovery and control of intelligent building devices | |
| CN108616506B (en) | Intelligent building real-time data distributed integrated control method | |
| CN111880430A (en) | Control method and device for intelligent household equipment | |
| CN111064627A (en) | Plug-and-play management system for electric power internet of things terminal | |
| US8484323B2 (en) | Network system connected with multiple master devices and method for operating the same | |
| CN101241365A (en) | Method and apparatus for automatically recognizing a connection of a device to a building management system | |
| CN114584429A (en) | Industrial intelligent internet of things gateway | |
| JP2000269998A (en) | Setting method for decentralized system | |
| CN208873044U (en) | Automotive diagnostic installation and automotive diagnostic system | |
| US11212134B2 (en) | Building automation system providing for integration of subsystems | |
| CN104993583A (en) | Communication method of power distribution automation equipment | |
| CN110456705B (en) | Network control device capable of dynamically expanding interface and building automatic control system | |
| CN116074397A (en) | Data sharing system | |
| CN215576153U (en) | 485 intelligent home gateway system | |
| JP2005504482A (en) | Use of less specific modules when there is no specific control module | |
| CN105207811B (en) | Method and device for replacing non-AllJoyn equipment | |
| KR102168775B1 (en) | Method for quickly processing service-based information query via a network and a device for said method | |
| CN110019281B (en) | Identification method and device for broadcasting and television equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CB03 | Change of inventor or designer information |
Inventor after: Liu Hua Inventor after: Li Hongbo Inventor after: Mou Guixian Inventor after: Shen Weigang Inventor after: Kang Yutao Inventor after: Chen Chuhong Inventor after: Wei Hexuan Inventor before: Liu Hua Inventor before: Mou Guixian Inventor before: Shen Weigang Inventor before: Kang Yutao Inventor before: Chen Chuhong Inventor before: Wei Hexuan |
|
| CB03 | Change of inventor or designer information | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20231008 Address after: 400039 GREE Road, Kowloon District, Chongqing, No. 1 Patentee after: GREE ELECTRIC APPLIANCES (CHONGQING) Co.,Ltd. Patentee after: GREE ELECTRIC APPLIANCES Inc. OF ZHUHAI Patentee after: Gree Electrical Appliances (Luoyang) Co.,Ltd. Address before: 519000 Qianshan Golden Chicken West Road in Zhuhai, Guangdong Patentee before: GREE ELECTRIC APPLIANCES Inc. OF ZHUHAI |
|
| TR01 | Transfer of patent right |