An automatic generation method for automation equipment signal detection and control

Abstract

The application discloses an automatic generation method for signal detection and control of automation equipment, and has the technical scheme as follows: S1, a user describes all signals, signal relationship and default value according to specific rules based on actual signals of the user's equipment; S2, the system loads a signal configuration file when starting; S3, a signal tree of the corresponding equipment is automatically generated by analysis; S4, a business processing module maintains the signal tree and signal data reported by the equipment; S5, the equipment control software sends a signal reading request; S6, a request processing module checks the user's request authority; S7, the signal specified by the user is inquired; and S8, the equipment reports data of various sensors, and the business processing module maintains the information, so that the signal description method for the automation equipment is flexible, simple and highly expandable, and can support or extend the signal definition of all automation equipment.

Description

Technical Field

[0001] This invention relates to the field of automation equipment technology, and in particular to an automatic generation method for signal detection and control in automation equipment. Background Technology

[0002] Current access to automated equipment is based on direct access to PLCs or equipment motion control cards. Therefore, the equipment control software is heavily reliant on a specific brand of motion control card and its accompanying software package. This technology has the following disadvantages:

[0003] 1. There is no unified definition and access rules for device signals. Different control programs for different devices use different signal access methods, resulting in slow product iteration and poor backward compatibility.

[0004] 2. When equipment developers choose different sensors and motion control cards, their equipment control software needs to be adapted and modified, resulting in poor product maintainability and long development cycles.

[0005] 3. There is no effective abstract definition of the signals of automated equipment, and there is no effective abstract definition of the dependencies between signals, making the control software programming complex and difficult to maintain;

[0006] 4. Updating signal equipment requires redeploying and upgrading the control software, making maintenance difficult.

[0007] The monitoring and control of existing automated equipment are all operated and controlled through sensors (including position sensors, speed sensors, temperature sensors, vision sensors, etc.) and controllers (including valve control, cylinder control, motion control, temperature control, etc.) deployed in various links. Adaptation processing is required for different types of equipment, different models of the same type of equipment, different types of sensors, and different brands of the same type of sensors.

[0008] To ensure software development efficiency, platforms providing control boards and data acquisition boards abstract and encapsulate these sensors, providing various access interfaces to read and manipulate the corresponding sensor results. The sensors operated at the application layer are logical devices; the business logic is unaware of the specific physical devices. This hardware board + adaptable driver + API interface architecture has the following disadvantages:

[0009] 1. There is no unified data access model for device attributes, sensors, and controllers. Different devices and sensor types may require calling different data access interfaces;

[0010] 2. Different board vendors often provide different API interfaces, and equipment manufacturers have to update their business software when switching platforms;

[0011] 3. The interface has limited versatility and high complexity, requiring the selection of different API interfaces for different device types.

[0012] 4. Strong coupling between business processing and hardware boards: For different device types, it is often necessary to upgrade and update the software packages to adapt to the hardware boards. Summary of the Invention

[0013] In view of the problems mentioned in the background art, the purpose of this invention is to provide an automatic generation method for signal detection and control of automated equipment, so as to solve the problems mentioned in the background art.

[0014] The above-mentioned technical objective of the present invention is achieved through the following technical solution:

[0015] An automatic signal generation method for automated equipment detection and control includes the following steps:

[0016] S1. Users describe all signal information, relationships between signals, and default values ​​according to specific rules based on the actual signals of their devices;

[0017] S2. When the system starts up, it loads the signal configuration file;

[0018] S3. Automatically generate the signal tree for the corresponding device through parsing;

[0019] S4. The business processing module maintains this signal tree and the signal data reported by the device.

[0020] S5. The device control software sends a signal read request.

[0021] S6. The request processing module verifies the user's request permissions to ensure that the user has the access rights corresponding to the signal.

[0022] S7. Query according to the signal specified by the user;

[0023] S8. The equipment reports data from various sensors, and the business processing module maintains its information.

[0024] S9. Return the signal result according to the user's request;

[0025] S10, The user sends a specified signal control command;

[0026] S11. The business processing module processes control commands and sends them to the corresponding Actuator of the device according to the mapping relationship.

[0027] Preferably, in S1, various different configuration file types or self-defined file types may be used to define device signals.

[0028] Preferably, the configuration file definition replaces the keyword "Name" description, and the signals use different "Name" descriptions.

[0029] Preferably, the signal access interface in S7 is defined based on different programming languages, including JS, JAVA, VC++, and C.

[0030] Preferably, in step S2, when the system starts up, the corresponding device signal data structure is generated by automatically loading and parsing the configuration file describing the signal relationship, and the specified signal can be accessed through the provided API interface.

[0031] Preferably, the access to the signal includes: signal subscription, signal unsubscription, signal reading, signal operation, and signal acquisition.

[0032] Preferably, the system includes a hardware abstraction layer, a configuration file management unit, an init processing module, a business main processing module, and a request processing module.

[0033] In summary, the present invention has the following main beneficial effects:

[0034] I. The signal description method for automated equipment is flexible, simple, and highly scalable, and supports signal definitions for all automated equipment by default or through extensions.

[0035] Second, the universal signal access interface improves the programming efficiency of automated equipment control software and reduces the requirements for software personnel.

[0036] Third, the decoupling of hardware and software facilitates the long-term evolution of equipment control software;

[0037] IV. Supports the ability to remotely access devices (Industry 4.0, smart equipment) and provides a secure access channel. Attached Figure Description

[0038] Figure 1 This is one of the processing flowcharts of the present invention;

[0039] Figure 2 This is a general data model diagram of the automated equipment of the present invention;

[0040] Figure 3 This is the second processing flowchart of the present invention;

[0041] Figure 4 This is a structural block diagram of the prior art in this invention. Detailed Implementation

[0042] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0043] Example 1

[0044] refer to Figures 1 to 4 An automatic signal generation method for automated equipment detection and control includes the following steps:

[0045] S1. Users describe all signal information, relationships between signals, and default values ​​according to specific rules based on the actual signals of their devices;

[0046] S2. When the system starts up, it loads the signal configuration file;

[0047] S3. Automatically generate the signal tree for the corresponding device through parsing;

[0048] S4. The business processing module maintains this signal tree and the signal data reported by the device.

[0049] S5. The device control software sends a signal read request.

[0050] S6. The request processing module verifies the user's request permissions to ensure that the user has the access rights corresponding to the signal.

[0051] S7. Query according to the signal specified by the user;

[0052] S8. The equipment reports data from various sensors, and the business processing module maintains its information.

[0053] S9. Return the signal result according to the user's request;

[0054] S10, The user sends a specified signal control command;

[0055] S11. The business processing module processes control commands and sends them to the corresponding Actuator of the device according to the mapping relationship.

[0056] In S1, various different configuration file types or user-defined file types may be used to define device signals.

[0057] In this case, the configuration file definition changes the keyword "Name" description, and signals use different "Name" descriptions.

[0058] In S7, the signal access interface is defined based on different programming languages, including JS, JAVA, VC++, and C.

[0059] In S2, when the system starts up, the corresponding device signal data structure is generated by automatically loading and parsing the configuration file describing the signal relationship. The specified signal can be accessed through the provided API interface.

[0060] Signal access includes: signal subscription, signal unsubscription, signal reading, signal operation, and signal acquisition.

[0061] The system includes a hardware abstraction layer, a configuration file management unit, an init processing module, a business main processing module, and a request processing module.

[0062] The present invention has the following main advantages:

[0063] I. The signal description method for automated equipment is flexible, simple, and highly scalable, and supports signal definitions for all automated equipment by default or through extensions.

[0064] Second, the universal signal access interface improves the programming efficiency of automated equipment control software and reduces the requirements for software personnel.

[0065] Third, the decoupling of hardware and software facilitates the long-term evolution of equipment control software;

[0066] IV. Supports the ability to remotely access devices (Industry 4.0, smart equipment) and provides a secure access channel.

[0067] Example 2

[0068] refer to Figures 1 to 4 This invention discloses an automatic generation method for signal detection and control of automated equipment. By providing a series of general methods for describing and accessing automated equipment signals, it achieves the goal of rapid definition and access of automated equipment signals.

[0069] It provides a general data description method and rules for signals from automated equipment, making signal definition and access more flexible;

[0070] A method for describing signal relationships is provided, making the operation of automated equipment more convenient (simplified programming);

[0071] A method for automatically generating signal trees for automated equipment is provided;

[0072] This provides a universal method for accessing signals, which makes it easier for software engineers to access device status, control devices, and perform other operations without having to worry about differences in devices or signals.

[0073] This invention first defines a general data model for automated equipment:

[0074] SignalNode: "Signal Node", read-only, defined as a node in the device data model, containing only information about the relationships between signals;

[0075] Attribute: A read-only property whose content remains unchanged.

[0076] Sensor: A "sensor" type, read-only, the content of which is subject to change;

[0077] Actuator: "Controller" type, read / write;

[0078] Stream: A "resource" type, read-only, primarily used for data streaming.

[0079] Define the rules for describing the data model, and describe and modify them through configuration files (such as .yaml, .dat, .txt, .xls, and other text files):

[0080] Basic rules:

[0081] Addressnodes:

[0082] Parentnodes:

[0083] NodeEntry:

[0084] Type

[0085] Description

[0086] DataEntry:

[0087] DataTypes:

[0088] DataUnitTypes:

[0089] Sensor & Actuator

[0090] Attributes

[0091] EnumerateddataEntries;

[0092] Include rules:

[0093] Indicates which spec definition files are included;

[0094] This rule indicates that the specified signal tree is being reused. Customization of the same signal can be achieved by using this rule (overriding the definition of the default signal).

[0095] Association rules:

[0096] "Association" indicates that this signal is related to other signals;

[0097] “Condition”: Access to a signal is performed when a specified condition is met;

[0098] "Seq": Sequential execution, executing a series of signal access operations sequentially.

[0099] “Parallel”: Parallel execution, triggering multiple specified signals simultaneously based on conditions;

[0100] "Wait": Wait for the specified time before performing the signal access operation;

[0101] Other features: Signal access rules can be defined to simplify application-level programming complexity;

[0102] Upon system startup, the configuration file describing the above signal relationships is automatically loaded and parsed to generate the corresponding device signal data structure. The provided API interface allows access to specific signals.

[0103] Signal subscription (specified signal, specified list of signals);

[0104] Subscribe to a signal (specified signal, specified list of signals, all signals);

[0105] Signal read(specified signal, specified list of signals);

[0106] Signal operations (specify signal, specified list of signals);

[0107] Supports signal acquisition (returns all signals supported by the current device, which can be used as input for specified signal access).

[0108] The typical processing flow for this solution is as follows:

[0109] S1. Users describe all signal information, relationships between signals, and default values ​​according to specific rules based on the actual signals of their devices;

[0110] S2. When the system starts up, it loads the signal configuration file;

[0111] S3. Automatically generate the signal tree for the corresponding device through parsing;

[0112] S4. The business processing module maintains this signal tree and the signal data reported by the device.

[0113] S5. The device control software sends a signal read request.

[0114] S6. The request processing module verifies the user's request permissions to ensure that the user has the access rights corresponding to the signal.

[0115] S7. Query according to the signal specified by the user;

[0116] S8. The equipment reports data from various sensors, and the business processing module maintains its information.

[0117] S9. Return the signal result according to the user's request;

[0118] S10, The user sends a specified signal control command;

[0119] S11. The business processing module processes control commands and sends them to the corresponding Actuator of the device according to the mapping relationship.

[0120] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. An automatic generation method for signal detection and control of automated equipment, characterized in that: Includes the following steps: S1. Users describe all signal information, relationships between signals, and default values ​​according to specific rules based on the actual signals of their devices. S2. When the system starts, load the signal configuration file; S3. Automatically generate the signal tree for the corresponding device through parsing; S4, the business processing module maintains this signal tree, as well as the signal data reported by the device; S5, The device control software sends a signal read request; S6. The request processing module verifies the user's request permissions to ensure that the user has the corresponding access permissions. S7. Perform a query according to the signal specified by the user; S8. The equipment reports data from various sensors, and the business processing module maintains its information. S9. Return the signal result according to the user's request; S10, The user sends a specified signal control command; S11. The business processing module processes control commands and sends them to the corresponding Actuator of the device according to the mapping relationship. First, define a general data model for automated equipment: SignalNode: "Signal Node", read-only, defined as a node in the device data model, containing only information about the relationship between signals; Attribute: "property", read-only, and its content remains unchanged; Sensor: This is a read-only sensor type; its contents are subject to change. Actuator: "Controller" type, read / write; Stream: "Resource" type, read-only, mainly for data stream patterns; Define the rules for describing the data model, and describe and modify them through configuration files: Basic rules: Addressnodes: Parentnodes: NodeEntry: Type Description DataEntry: DataTypes: DataUnitTypes: Sensor & Actuator Attributes EnumerateddataEntries; Include rules: Indicates which spec definition files are included; This rule indicates that the specified signal tree is being reused, and can be used to customize the same signal. Association rules: "Association" indicates that this signal is related to other signals; "Condition": Executes access to a signal when the specified condition is met; "Seq": Sequential execution, executing a series of signal access operations sequentially. "Parallel": Executes in parallel, triggering multiple specified signals simultaneously based on conditions; "Wait": Wait for the specified time before performing the signal access operation; Other features: Signal access rules can be defined to simplify application-level programming complexity; Upon system startup, the configuration file describing the above signal relationships is automatically loaded and parsed to generate the corresponding device signal data structure. The provided API interface allows access to specific signals. Signal subscription; Subscribe to the signal; Signal reading; signal operations; Supports signal acquisition; In S1, various different configuration file types and user-defined file types are used to define device signals; The configuration file definition changes the keyword "Name" description, and the signals use different "Name" descriptions; In S2, when the system starts up, the corresponding device signal data structure is generated by automatically loading and parsing the configuration file describing the signal relationship, and the specified signal can be accessed through the provided API interface; The access to the signal includes: signal subscription, signal unsubscription, signal reading, signal operation, and support for signal acquisition; The system includes a hardware abstraction layer, a configuration file management unit, an init processing module, a business main processing module, and a request processing module.

Images