Virtual hardware control bus architecture and virtual hardware control bus system

Abstract

The application discloses a virtual hardware control bus architecture and a virtual hardware control bus system, and belongs to the technical field of automation control. The architecture comprises: a hardware parent class, the hardware parent class comprising an execution interface, the execution interface being used for receiving a hardware action instruction and feeding back hardware feedback information based on the hardware action instruction, the hardware action instruction comprising a hardware number, a hardware name, action information and action parameters of a hardware device performing an action, and the hardware feedback information comprising an action result, feedback data and abnormal information of the hardware device performing the action corresponding to the hardware action instruction; at least one hardware type, the hardware type being inherited from the hardware parent class, each hardware type being used for connecting a hardware device, the hardware type being used for analyzing the hardware action instruction, driving the hardware device to perform the action, and feeding back the hardware feedback information to the execution interface. The architecture improves the reuse degree and reduces the development cost through the universal design and the standardized software calling.

Description

TECHNICAL FIELD

[0001] The present application belongs to the field of automation control technology, and particularly relates to a virtual hardware control bus architecture and a virtual hardware control bus system. BACKGROUND

[0002] With the continuous development of the automation industry, a large number of automation control hardware components have begun to be controlled by software on an industrial computer instead of digital operation of an electronic system (PLC). Different hardware components are controlled through their respective drivers or software interfaces. Even the same type of hardware device has different interfaces, and the differences between interfaces of different types of devices are even greater. In actual project delivery, software is matched according to the hardware selection of the project.

[0003] The design of the industrial computer lacks generalization design and technical level design. When the automation process is controlled, the selected hardware needs to be aligned to perform application development of the specified Application Programming Interface (API). The process design is not reusable, especially in scenarios where the automation control process is similar, but the selected hardware is different. Hardware API adaptation is often required.

[0004] Currently, the development cost caused by software adaptation of automation control hardware is large, and the inability to reuse is a problem that needs to be solved in the automation control process. SUMMARY

[0005] The present application aims to at least solve one of the technical problems existing in the prior art. To this end, the present application provides a virtual hardware control bus architecture and a virtual hardware control bus system, which can standardize the calling of control software, improve the degree of reuse, and reduce the development cost.

[0006] In a first aspect, the present application provides a virtual hardware control bus architecture, which comprises:

[0007] a hardware parent class, the hardware parent class comprising an execution interface, the execution interface being configured to receive a hardware action instruction and feed back hardware feedback information based on the hardware action instruction, the hardware action instruction comprising a hardware number, a hardware name, action information, and action parameters of a hardware device performing an action, and the hardware feedback information comprising an action result, feedback data, and exception information of the hardware device performing the action corresponding to the hardware action instruction;

[0008] at least one hardware type, the hardware type being inherited from the hardware parent class, each hardware type being configured to connect one hardware device, the hardware type being configured to parse the hardware action instruction, drive the hardware device to perform an action, and feed back the hardware feedback information to the execution interface;

[0009] The hardware type is used to inherit the base class of the hardware type based on the hardware manufacturer model, and based on the base class and the hardware manufacturer model, call the hardware manufacturer application programming interface to drive the hardware device to perform an action.

[0010] According to the virtual hardware control bus architecture of this application, through the execution interface of the hardware parent class and the universal design of the hardware type, the calling of the upper-level process flow control part software is standardized, the degree of reuse is improved, and the development cost is reduced.

[0011] According to one embodiment of the present application, the basic information of the hardware parent class includes a hardware number, a hardware name, and a hardware type.

[0012] According to one embodiment of the present application, the transmission data format of the execution interface is JSON format.

[0013] According to one embodiment of the present application, the hardware type is used to parse the action information and action parameters of the hardware action instruction, and when it is determined that the action information and action parameters of the hardware action instruction match the hardware device connected to the hardware type, the hardware device is driven to perform the action.

[0014] In a second aspect, the present application provides a virtual hardware control bus system, the system comprising:

[0015] At least two virtual hardware control bus architectures as described in the first aspect, wherein the at least two virtual hardware control bus architectures are connected in series, and among the at least two virtual hardware control bus architectures, one virtual hardware control bus architecture is a server, and the remaining virtual hardware control bus architectures are clients, and the server is used to control the client.

[0016] According to the virtual hardware control bus system of the present application, the system is built through the virtual hardware control bus architecture, controlled by the server, and the calling interface on the software side is unified. For the device control network of multiple industrial computers, a wider range of universal design is achieved, which effectively improves the system's reuse level and reduces development costs.

[0017] According to one embodiment of the present application, the client is used to connect to the server at startup, and after confirming the connection with the server, report the client's hardware list to the server. The client's hardware list includes the hardware number and hardware name of the hardware device connected to the client. The server is used to receive the client's hardware list and build a hardware list of the virtual hardware control bus system.

[0018] According to an embodiment of the present application, the client comprises a first client, the first client is configured to drive the target hardware device to perform the action in case that it is determined that the target hardware device corresponding to the hardware action instruction exists in the hardware list of the first client.

[0019] According to an embodiment of the present application, the first client is configured to invoke a hardware vendor application programming interface based on the hardware action instruction, and drive the target hardware device to perform the action.

[0020] According to an embodiment of the present application, the client further comprises a second client, the first client is configured to send the hardware control instruction to the server in case that it is determined that the target hardware device does not exist in the hardware list of the first client, the server is configured to forward the hardware action instruction to the second client based on the hardware list of the virtual hardware control bus system, so that the second client drives the target hardware device to perform the action.

[0021] According to an embodiment of the present application, the second client is configured to feed back hardware feedback information based on the hardware action instruction to the server after driving the target hardware device to perform the action, and the server is configured to forward the hardware feedback information to the first client.

[0022] Additional aspects and advantages of the present application will be made apparent from the following description of embodiments of the present application, which will be described in the following description of embodiments of the present application, which will be described in the following description of embodiments of the present application. BRIEF DESCRIPTION OF DRAWINGS

[0023] The above and / or additional aspects and advantages of the present application will become apparent and be readily understood from the following description of embodiments, taken in conjunction with the accompanying drawings in which:

[0024] Figure 1 is a structure diagram of a virtual hardware control bus architecture in an industrial computer provided by an embodiment of the present application;

[0025] Figure 2 is a structure diagram of a virtual hardware control bus system in a plurality of industrial computers provided by an embodiment of the present application. DETAILED DESCRIPTION

[0026] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all of the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art belong to the scope of protection of the present application.

[0027] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first", "second", etc. are generally of a kind and do not limit the number of objects, for example, the first object can be one or more. In addition, "and / or" in the specification and claims indicates at least one of the connected objects, and the character " / " generally indicates that the objects before and after are in an "or" relationship.

[0028] In the related art, the design of the industrial computer lacks general design and technical level design. When the automation process is controlled, the selected hardware needs to be aligned to develop the application of the Application Programming Interface (API). The process design is not reusable, especially in the scenario where the automation control process is similar, but the selected hardware is different. In this case, the hardware API needs to be adapted.

[0029] Currently, the development cost caused by the adaptation of the software of the automation control hardware is large, and the inability to reuse is a problem that needs to be solved in the automation control process.

[0030] The virtual hardware control bus architecture and the virtual hardware control bus system provided by the embodiments of the present application will be described in detail below in combination with the drawings and specific embodiments and their application scenarios.

[0031] The virtual hardware control bus architecture provided by the embodiments of the present application can be arranged in an industrial computer, and a virtual hardware control bus is constructed in the industrial computer to control the hardware devices connected to the industrial computer.

[0032] The virtual hardware control bus architecture provided by the embodiments of the present application includes a hardware parent class and at least one hardware type.

[0033] The virtual hardware control bus architecture can include a plurality of hardware types, each of which inherits from the hardware parent class, and each of which is used to connect a hardware device.

[0034] In actual execution, when a new hardware device is added to the virtual hardware control bus architecture, a corresponding hardware type is added for the new hardware device, and the hardware type is set to inherit from the hardware parent class.

[0035] In this embodiment, the hardware parent class includes an execution interface, which is used to receive a hardware action instruction and feedback hardware feedback information based on the hardware action instruction.

[0036] The hardware action instruction includes a hardware number, a hardware name, action information, and action parameters of a hardware device that performs an action.

[0037] In actual execution, when it is required to control a hardware device to perform an action, the industrial computer can issue a corresponding hardware action instruction, which is received by the execution interface of the hardware parent class in the virtual hardware control bus architecture, and is forwarded to the hardware type corresponding to the hardware action instruction.

[0038] The execution interface of the hardware parent class receives the hardware action instruction, can analyze the hardware number, hardware name, and other information in the hardware action instruction, determine the hardware type corresponding to the hardware action instruction, and forward the hardware action instruction to the hardware type.

[0039] The hardware number of the hardware device can refer to a hardware ID, a hardware serial number, etc., and each hardware device has a unique hardware number.

[0040] The hardware type receives the hardware action instruction, is used to analyze the hardware action instruction, drive the hardware device to perform an action, and feed back hardware feedback information to the execution interface.

[0041] In this embodiment, the hardware type is used to inherit the base class of the hardware type based on the hardware manufacturer model, and call the hardware manufacturer application programming interface based on the base class and the hardware manufacturer model to drive the hardware device to perform an action.

[0042] In each hardware type, the base class of the hardware type component is inherited according to different hardware manufacturer models, and the application programming interface (API) of each hardware manufacturer is called based on the inherited base class to realize the driving of the hardware device to perform an action.

[0043] It should be noted that the driving of the hardware device to perform an action by each hardware type can be independently completed, and the hardware type does not perceive the external process design part when calling the hardware manufacturer application programming interface based on the base class to realize the driving.

[0044] In this embodiment, the hardware type analyzes the hardware action instruction, determines the hardware number, hardware name, action information, and action parameters of the hardware device corresponding to the hardware action instruction, calls the hardware manufacturer application programming interface based on the base class according to the action information and the action parameters, and drives the hardware device to perform a corresponding action.

[0045] The hardware type drives the hardware device to perform an action, and feeds back hardware feedback information related to the action of the hardware device to the execution interface of the hardware parent class.

[0046] The hardware feedback information includes an action result of the hardware device performing the action corresponding to the hardware action instruction, feedback data, and abnormal information.

[0047] For example, the hardware type drives the hardware device to perform the action, and the action result in the hardware feedback information fed back to the execution interface of the hardware parent class is that the hardware device completes the action corresponding to the hardware action instruction, the feedback data is data generated when the hardware device performs the action corresponding to the hardware action instruction, and the abnormal information is whether an abnormality occurs when the hardware device performs the action corresponding to the hardware action instruction.

[0048] In the embodiment of the application, a virtual hardware control bus is constructed in the industrial computer through the hardware parent class and the hardware type, and the virtual hardware control bus is directly called in an application by using an application programming interface in application transmission, the virtual hardware control bus constructed effectively abstracts all hardware devices, and unifies the calling interface (that is, the execution interface) on the software side, so that the selection difference on the hardware level does not affect the development of the upper-layer business.

[0049] A specific embodiment is introduced below.

[0050] As shown in FIG. 1, the process flow control process of the industrial computer is driven by a hardware unified calling interface, which is an execution interface of a hardware parent class in a virtual hardware control bus architecture of the industrial computer. Figure 1 The industrial computer is connected with three hardware devices, that is, a motor, a vacuum component, and a pressure sensor, and the three hardware devices correspond to three abstract interfaces, that is, a motor abstract interface, a vacuum abstract interface, and a pressure sensor abstract interface.

[0051] In the virtual hardware control bus architecture of the industrial computer, each hardware device corresponds to a hardware type, and the hardware type calls an application programming interface of a hardware manufacturer based on a corresponding base class and a hardware manufacturer model to drive the hardware device to perform an action.

[0052] The motor abstract interface is connected with a brand A motor, a brand B motor, and a brand C motor, and the brand A motor, the brand B motor, and the brand C motor correspond to three different hardware types.

[0053] When the brand A motor is driven to perform an action, the hardware type corresponding to the brand A motor calls the application programming interface of the hardware manufacturer A based on the corresponding base class and the hardware manufacturer model A to drive the brand A motor to perform the action.

[0054] When the brand D motor or the vacuum component needs to be added, a corresponding hardware type is established, the hardware type is inherited from the hardware parent class, and the hardware type calls the application programming interface of the hardware manufacturer to drive the hardware device to perform the action.

[0055]

[0056] ​According to the virtual hardware control bus architecture provided in the embodiment of the present application, through the execution interface of the hardware parent class and the universal design of the hardware type, the calling of the upper-level process flow control part software is standardized, the degree of reuse is improved, and the development cost is reduced.

[0057] In some embodiments, the basic information of the hardware parent class includes a hardware number, a hardware name, and a hardware type.

[0058] In this embodiment, the basic information of the hardware parent class is used to represent information such as the hardware number, hardware name, and hardware type of the hardware device connected to the hardware type included in the virtual hardware control bus architecture.

[0059] In actual implementation, the basic information of the hardware parent class includes a hardware number, a hardware name, and a hardware type. The basic information of the hardware parent class corresponds to a hardware list of hardware devices in the virtual hardware control bus architecture.

[0060] The hardware number of a hardware device can refer to a hardware ID, hardware serial number, etc. Each hardware device has a unique hardware number. The hardware name is the name of each hardware device, and the hardware name can be modified. The hardware type is the type of the hardware device. Hardware devices can be classified according to the hardware type.

[0061] For example, Figure 1 As shown, in the virtual hardware control bus architecture, the hardware types are divided into motors, vacuum components and pressure sensors. The motor abstract interface connects brand A motor, brand B motor and brand C motor. Brand A motor, brand B motor and brand C motor are hardware names, and brand A motor, brand B motor and brand C motor have their own unique hardware numbers.

[0062] In this embodiment, when hardware devices are added or removed from the virtual hardware control bus architecture, the basic information of the hardware parent class changes accordingly. The hardware parent class can analyze and determine the hardware type corresponding to the hardware action instruction based on the basic information.

[0063] In some embodiments, the transmission data format of the execution interface is in JSON format.

[0064] Among them, JSON (JavaScript Object Notation) is a lightweight data exchange format based on a subset of ECMAScript (the js specification developed by the European Computer Manufacturers Association). It uses a text format that is completely independent of the programming language to store and represent data. It is easy for people to read and write, and it is also easy for machines to parse and generate, and effectively improve network transmission efficiency.

[0065] In this embodiment, the data transmitted by the execution interface includes hardware action instructions and hardware feedback information, and the data format of the hardware action instructions and the hardware feedback information is JSON format.

[0066] The following describes a specific embodiment by taking a vacuum component as an example.

[0067] The hardware component that performs the action is A-side feeding vacuum, and the hardware action instruction received by the execution interface can be as follows:

[0068] [{

[0069] "hardwareId":"vacuum2_3",

[0070] "hardwareName":"A-side feeding vacuum",

[0071] "actionName":"Vacuum Breaking",

[0072] "actionTime":"2021-11-23 13:03:22",

[0073] "actionParam"

[0074] [{

[0075] "paramName":"timeout",

[0076] "paramValue":"60",

[0077] },

[0078] {

[0079] "paramName":"retryTime",

[0080] "paramValue":"3",

[0081] }]

[0082] }]

[0083] According to the hardware action instruction, the hardware type drives the hardware device A-side feeding vacuum to perform the action, and feeds back hardware feedback information related to the action of the hardware device to the execution interface of the hardware parent class. The hardware feedback information can be as follows:

[0084] [{

[0085] "hardwareId":"vacuum2_3",

[0086] "hardwareName": "A face loading vacuum",

[0087] "actionName": "Vacuum Breaking",

[0088] "actionTime": "2021-11-23 13:03:22",

[0089] "actionResult": "succeed",

[0090] "failReason": "",

[0091] "actionData"

[0092] [{

[0093] "paramName": "duration",

[0094] "paramValue": "1.5",

[0095] }]

[0096] }]

[0097] In this embodiment, the data transmitted by the execution interface includes hardware action instructions and hardware feedback information in JSON format, which is easy for machine parsing and generation, and can effectively improve the network transmission efficiency.

[0098] In some embodiments, the hardware type is used to parse the action information and action parameters of the hardware action instruction, and in the case where the action information and action parameters of the hardware action instruction are matched with the hardware device connected to the hardware type, the hardware device is driven to perform the action.

[0099] In the virtual hardware control bus architecture, each hardware type inherits from the hardware parent class, and each hardware type can abstract the standard action of the hardware device connected thereto and can be mapped to the action description of the execution interface of the hardware parent.

[0100] The hardware type confirms whether the hardware action instruction includes the necessary operation parameters by parsing the action information and action parameters of the hardware action instruction, i.e., determines whether the action information and action parameters of the hardware action instruction are matched with the hardware device connected to the hardware type.

[0101] The hardware type parses the action information and action parameters of the hardware action instruction, confirms that the hardware action instruction includes the necessary operation parameters, calls the hardware manufacturer application programming interface, and drives the hardware device to perform the corresponding action.

[0102] Taking a vacuum component as an example.

[0103] The vacuum components can perform vacuum suction and vacuum breaking actions.

[0104] The hardware type parses the hardware action instruction to search for the "timeout" parameter. When confirming that the action information, action name, and action parameters are all satisfied, the vacuum component is driven to perform the vacuum suction action or the vacuum breaking action. After the action is completed, the hardware feedback information corresponding to the hardware action instruction is synchronously given.

[0105] The virtual hardware control bus architecture of the embodiment of the present application can build a virtual hardware control bus inside the industrial computer through the hardware parent class and hardware 5 types, and directly use the application programming interface to call all hardware devices.

[0106] It can effectively abstract the equipment, unify the calling interface of the software side, standardize the calling of the control software, improve the degree of reuse, and reduce development costs.

[0107] In related technologies, as the complexity of hardware equipment increases and the scale of hardware equipment becomes larger, there are multiple industrial control

[0108] The industrial computers are segmented to form a device control network. However, due to inconsistent hardware interfaces in this scenario, it is often necessary to build a communication solution between industrial computers, such as TCP, and then transmit notification signals in a customized manner. The corresponding industrial computers then parse the protocol signals and call different hardware interfaces.

[0109] In complex multi-industrial computer control networks, inconsistent hardware component interface designs and varying hardware requirements for different devices lead to customized communication message content based on the actual project selection, resulting in a low reuse rate.

[0110] 5 The embodiment of the present application also provides a virtual hardware control bus system that can be used in devices with multiple industrial computers.

[0111] Control applications in the network, ensure consistency in the calling interface on the software side, and provide universal and highly reliable hardware control functions.

[0112] The virtual hardware control bus system provided by the embodiment of the present application includes: at least two virtual hardware control bus architectures as described above.

[0113] In this embodiment, each virtual hardware control bus architecture corresponds to an industrial computer.

[0114] The equipment control network where the system is located includes at least two industrial computers.

[0115] The at least two virtual hardware control bus architectures are connected in series, and in actual implementation, the industrial personal computers corresponding to the virtual hardware control bus architectures can be connected in series through WCF (Windows Communication Foundation) technology.

[0116] The WCF provides a foundation for the.Net Framework, enabling it to write code that communicates between components, applications, and systems.

[0117] In this embodiment, the virtual hardware control bus system includes a plurality of virtual hardware control bus architectures, one of which is used as a server (Server) and the others are used as clients (Client), and the server is used to control the clients.

[0118] The device control network of the plurality of industrial personal computers in which the virtual hardware control bus system is located constitutes a Client-Server (C / S) structure, and the server and the clients interact with each other to control the clients.

[0119] The industrial personal computer of the virtual hardware control bus architecture as the server can be referred to as a master industrial personal computer, and the industrial personal computers of the virtual hardware control bus architectures as the clients can be referred to as slave industrial personal computers.

[0120] For example, the device control network in which the virtual hardware control bus system is located includes four industrial personal computers, of which the industrial personal computer A is the master industrial personal computer, and the other industrial personal computers B, C, and D are the slave industrial personal computers.

[0121] The following describes a specific embodiment.

[0122] As shown in Figure 2 , the master industrial personal computer Server includes a local hardware unified calling interface and a remote hardware unified calling interface, and the local hardware unified calling interface is the execution interface of the hardware parent class in the virtual hardware control bus architecture of the master industrial personal computer Server.

[0123] The master industrial personal computer Server is connected with three hardware devices, i.e., a motor, a vacuum component, and a pressure sensor, and corresponds to three abstract interfaces, i.e., a motor abstract interface, a vacuum abstract interface, and a pressure sensor abstract interface.

[0124] The motor abstract interface of the master industrial personal computer Server is connected with a brand A motor, a brand B motor, and a brand C motor, and the brand A motor, the brand B motor, and the brand C motor correspond to three different hardware types.

[0125] When the brand B motor is driven to perform an action, the hardware type corresponding to the brand B motor is based on the corresponding base class and hardware manufacturer model B, and the hardware manufacturer B application programming interface is called to drive the brand B motor to perform the action.

[0126] The remote hardware unified calling interface can interact with the slave industrial computer Client to control the slave industrial computer Client to drive the hardware devices connected thereto to perform actions.

[0127] According to the virtual hardware control bus system provided in the embodiments of the present application, the system is built through the virtual hardware control bus architecture, is controlled by a server, and has a unified software-side calling interface, so that a larger range of universal design is achieved for a device control network of multiple industrial computers, the reuse degree of the system is effectively improved, and the development cost is reduced.

[0128] In some embodiments, the client is configured to connect to the server at startup, and after determining that the connection with the server is successful, report a hardware list of the client to the server, the hardware list of the client including hardware numbers and hardware names of hardware devices connected to the client, and the server is configured to receive the hardware list of the client and build a hardware list of the virtual hardware control bus system.

[0129] When the slave industrial computer where the client is located starts up, the client reports a hardware list of the client to the server according to the hardware devices connected to the client, the hardware list of the client including hardware numbers and hardware names of hardware devices connected to the client.

[0130] In actual execution, when each client starts up, the server starts to listen, the client actively connects to the server, and after the client confirms that the connection with the server is successful, each client reports hardware numbers and hardware names of hardware devices managed by the client, that is, reports a hardware list of the client to the server, and the server collects and manages the hardware list of the client to build a hardware list of the entire virtual hardware control bus system.

[0131] In the device control network of multiple industrial computers, the master industrial computer collects all hardware device components including hardware devices managed by the master industrial computer and the slave industrial computer according to a hardware configuration file when starting up in the virtual hardware control bus system, registers hardware numbers and hardware names of all hardware devices after confirming that the initialization calling of the hardware device components is successful, and builds a hardware list of the virtual hardware control bus system for facilitating cross-industrial computer calling.

[0132] The specific process of cross-industrial computer calling is described below.

[0133] In some embodiments, the client includes a first client, and the first client is configured to drive a target hardware device to perform an action in a case where the target hardware device corresponding to a hardware action instruction exists in a hardware list of the first client.

[0134] The first client corresponds to the virtual hardware control bus architecture of the slave industrial computer that issues hardware action instructions.

[0135] The first client parses the hardware action instruction and determines whether a target hardware device corresponding to the hardware action instruction exists in the hardware list of the first client.

[0136] When it is determined that the target hardware device corresponding to the hardware action instruction exists in the hardware list of the first client, that is, the target hardware device corresponding to the hardware action instruction is a hardware device managed by the first client, the first client directly drives the target hardware device to perform the action.

[0137] In some embodiments, the first client is used to call the hardware manufacturer's application programming interface based on the hardware action instruction to drive the target hardware device to perform the action.

[0138] In this embodiment, the hardware type of the first client parses the action information and action parameters of the hardware action instruction, confirms that the hardware action instruction includes necessary operation parameters, calls the hardware manufacturer's application programming interface, and drives the target hardware device to perform the corresponding action.

[0139] In some embodiments, the client also includes a second client, and the first client is used to send hardware control instructions to the server when it is determined that the target hardware device does not exist in the hardware list of the first client, and the server is used to forward the hardware action instructions to the second client based on the hardware list of the virtual hardware control bus system, so that the second client can drive the target hardware device to perform the action.

[0140] The target hardware device corresponding to the hardware action instruction is not a hardware device managed by the first client, but a hardware device managed by the second client.

[0141] In this embodiment, the first client sends the hardware control instruction to the server, and the server determines that the target hardware device is a hardware device managed by the second client based on the hardware list of the virtual hardware control bus system, and then forwards the hardware control instruction to the second client.

[0142] The second client receives the hardware control instruction, parses the action information and action parameters of the hardware action instruction, confirms that the hardware action instruction includes necessary operation parameters, calls the hardware manufacturer's application programming interface, and drives the target hardware device to perform the corresponding action.

[0143] In some embodiments, the second client is configured to feed back hardware feedback information based on the hardware action instruction to the server after driving the target hardware device to perform an action, and the server is configured to forward the hardware feedback information to the first client.

[0144] It can be understood that the first client is an action initiator, the second client is an action executor, the target hardware device corresponding to the hardware action instruction is not a hardware device managed by the first client, and after the second client drives the target hardware device to execute the action, the hardware feedback information needs to be fed back to the first client, the action initiator, for analysis and confirmation.

[0145] A specific embodiment will be introduced below.

[0146] In the device control network of multiple industrial computers, when any one industrial computer needs to control an action of a hardware device, it will first confirm whether the hardware device exists in its own hardware list. If it exists, it will call the hardware manufacturer's application programming interface to directly control the action of the hardware device.

[0147] If it is not in its own hardware list, the JSON content of the called hardware control instruction will be directly sent to the master industrial computer Server, which will query the hardware list in the device control network to confirm which industrial computer the operating hardware is on, and then forward it.

[0148] After the corresponding industrial computer receives the execution requirement, it executes the action and feeds back to the master industrial computer Server, which forwards it to the action initiator.

[0149] In this embodiment, any node of the device control network of multiple industrial computers can operate the hardware devices under all nodes, and no longer perceives the industrial computer, model, and other contents of the specific hardware device, facilitating the implementation and reuse of the overall control process software.

[0150] The embodiments of the application are described above in combination with the drawings, but the application is not limited to the above specific implementation, and the above specific implementation is only illustrative, not restrictive, and those skilled in the art can make many forms under the inspiration of the application without departing from the scope of the application and the protection scope of the claims.

[0151] In the description of the present specification, the description of the terms "one embodiment", "some embodiments", "illustrative embodiment", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in combination with the embodiment or example are included in at least one embodiment or example of the present application. In the present specification, the illustrative description of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner.

[0152] While the embodiments of the application have been shown and described, it is to be understood that the embodiments can be varied, modified, substituted and changed by those skilled in the art without departing from the principles and spirit of the application, the scope of which is defined by the claims and their equivalents.

Claims

1. A virtual hardware control bus architecture, characterized in that: include: A hardware parent class, the hardware parent class including an execution interface, the execution interface being used to receive hardware action instructions and to feed back hardware feedback information based on the hardware action instructions, the hardware action instructions including the hardware number, hardware name, action information, and action parameters of the hardware device performing the action, and the hardware feedback information including the action result, feedback data, and exception information of the hardware device performing the action corresponding to the hardware action instruction; At least one hardware type, the hardware type inherits from the hardware parent class, each of the hardware types is used to connect to one of the hardware devices, the hardware type is used to parse the hardware action instruction, drive the hardware device to perform the action, and feed back the hardware feedback information to the execution interface; The hardware type is used to inherit the base class of the hardware type based on the hardware manufacturer model, and based on the base class and the hardware manufacturer model, call the hardware manufacturer application programming interface to drive the hardware device to perform an action; The basic information of the hardware parent class includes hardware number, hardware name and hardware type; When the hardware device is added or reduced in the virtual hardware control bus architecture, the basic information of the hardware parent class changes accordingly. The hardware parent class analyzes and determines the hardware type corresponding to the hardware action instruction based on the basic information.

2. The virtual hardware control bus architecture according to claim 1, wherein: The transmission data format of the execution interface is JSON format.

3. The virtual hardware control bus architecture according to claim 1 or 2, characterized in that: The hardware type is used to parse the action information and action parameters of the hardware action instruction, and drive the hardware device to perform an action when it is determined that the action information and action parameters of the hardware action instruction match the hardware device connected to the hardware type.

4. A virtual hardware control bus system, characterized in that: include: At least two virtual hardware control bus architectures according to any one of claims 1 to 3, wherein the at least two virtual hardware control bus architectures are connected in series, and among the at least two virtual hardware control bus architectures, one virtual hardware control bus architecture is a server and the other virtual hardware control bus architectures are clients, and the server is used to control the clients.

5. The virtual hardware control bus system according to claim 4, characterized in that: The client is used to connect to the server at startup, and after confirming the connection with the server, report the client's hardware list to the server. The client's hardware list includes the hardware number and hardware name of the hardware device connected to the client. The server is used to receive the client's hardware list and build a hardware list of the virtual hardware control bus system.

6. The virtual hardware control bus system according to claim 5, characterized in that: The client includes a first client, and the first client is used to drive the target hardware device to perform an action when it is determined that the target hardware device corresponding to the hardware action instruction exists in the hardware list of the first client.

7. The virtual hardware control bus system according to claim 6, characterized in that: The first client is used to call the hardware manufacturer's application programming interface based on the hardware action instruction to drive the target hardware device to perform an action.

8. The virtual hardware control bus system according to claim 6, wherein: The client also includes a second client, wherein the first client is used to send the hardware action instruction to the server when it is determined that the target hardware device does not exist in the hardware inventory of the first client, and the server is used to forward the hardware action instruction to the second client based on the hardware inventory of the virtual hardware control bus system, so that the second client drives the target hardware device to perform the action.

9. The virtual hardware control bus system according to claim 8, characterized in that: The second client is used to feed back hardware feedback information based on the hardware action instruction to the server after driving the target hardware device to perform an action, and the server is used to forward the hardware feedback information to the first client.

Images