CN117376438A - Data communication method and system for tightening controller - Google Patents
Data communication method and system for tightening controller Download PDFInfo
- Publication number
- CN117376438A CN117376438A CN202311430931.0A CN202311430931A CN117376438A CN 117376438 A CN117376438 A CN 117376438A CN 202311430931 A CN202311430931 A CN 202311430931A CN 117376438 A CN117376438 A CN 117376438A
- Authority
- CN
- China
- Prior art keywords
- target
- controller
- data
- tightening
- communication
- 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.)
- Pending
Links
- 238000004891 communication Methods 0.000 title claims abstract description 173
- 238000000034 method Methods 0.000 title claims abstract description 52
- 230000004044 response Effects 0.000 claims abstract description 50
- 238000007405 data analysis Methods 0.000 claims description 3
- 238000004519 manufacturing process Methods 0.000 description 19
- 238000007726 management method Methods 0.000 description 17
- 238000010586 diagram Methods 0.000 description 9
- 238000013480 data collection Methods 0.000 description 6
- 230000010354 integration Effects 0.000 description 6
- 238000012545 processing Methods 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 238000005457 optimization Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/08—Protocols for interworking; Protocol conversion
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Communication Control (AREA)
Abstract
The invention relates to the technical field of tightening controllers and discloses a data communication method and a system for tightening controllers, wherein the method is used for acquiring a connection response message fed back by a target controller through each tightening controller by supporting a first communication protocol, determining a target type corresponding to the target controller according to the connection response message, and matching to obtain a target driving package corresponding to the target type so as to carry out data communication with the target controller based on a second communication protocol loaded by the target driving package.
Description
Technical Field
The invention relates to the technical field of tightening controllers, in particular to a data communication method and system for a tightening controller.
Background
Along with the rapid development of technology and the continuous progress of production industry, the application field is continuously expanding, and the demand for precision control equipment is increasing, wherein a tightening controller is used as important precision control equipment, the precision control of connecting elements such as bolts, screws and threads is realized by the stability of the tightening controller, the production can be effectively detected and controlled by collecting the data of the controller, and the stability and the reliability of the connecting elements are ensured, so that the tightening controller is widely applied to various industries.
However, as the brands and models of the tightening controllers are continuously diversified, different brands, different models, and different types of tightening controllers may have differences in communication protocols and data formats, which makes it necessary to develop a specific data communication program for each tightening controller separately, which is not only heavy in workload, but also disadvantageous in data collection and integration, so that the management difficulty of the tightening controller is correspondingly increased, and the production efficiency requirement cannot be satisfied.
Disclosure of Invention
The following presents a simplified summary in order to provide a basic understanding of some aspects of the disclosed embodiments. This summary is not an extensive overview, and is intended to neither identify key/critical elements nor delineate the scope of such embodiments, but is intended as a prelude to the more detailed description that follows.
In view of the above-mentioned drawbacks of the prior art, the present invention discloses a data communication method and system for a tightening controller, so as to reduce the management difficulty of the tightening controller.
The invention discloses a data communication method for a tightening controller, wherein the tightening controller comprises a target controller which is applied to a user terminal, and the method comprises the following steps: transmitting a connection request to the target controller based on a first communication protocol to acquire a connection response message fed back by the target controller, wherein each tightening controller supports the first communication protocol; determining a target type corresponding to the target controller from the connection response message; matching from a preset communication driving library according to the target type to obtain a target driving package, wherein the communication driving library stores one or more communication driving packages corresponding to the controller types respectively; and loading the target driving packet so as to carry out data communication with the target controller based on a second communication protocol loaded by the target driving packet.
The invention discloses a data communication method for a tightening controller, wherein the tightening controller comprises a target controller and is applied to a server side, and the method comprises the following steps: transmitting a connection request to the target controller based on a first communication protocol to acquire a connection response message fed back by the target controller, wherein each tightening controller supports the first communication protocol; determining a target type corresponding to the target controller from the connection response message; matching from a preset communication driving library according to the target type to obtain a target driving package, wherein the communication driving library stores one or more communication driving packages corresponding to the controller types respectively; and loading the target driving packet so as to carry out data communication with the target controller based on a second communication protocol loaded by the target driving packet.
The invention discloses a data communication system for tightening a controller, comprising: one or more tightening controllers connected with a user terminal or a server, wherein the tightening controllers comprise a target controller; the user terminal or the server side is configured to send a connection request to the target controller based on a first communication protocol, so as to obtain a connection response message fed back by the target controller, where each tightening controller supports the first communication protocol; determining a target type corresponding to the target controller from the connection response message; matching from a preset communication driving library according to the target type to obtain a target driving package, wherein the communication driving library stores one or more communication driving packages corresponding to the controller types respectively; and loading the target driving packet so as to carry out data communication with the target controller based on a second communication protocol loaded by the target driving packet.
The invention has the beneficial effects that:
and acquiring a connection response message fed back by the target controller through each tightening controller supporting the first communication protocol, and determining a target type corresponding to the target controller according to the connection response message, so as to obtain a target driving packet corresponding to the target type in a matching way, and carrying out data communication with the target controller based on a second communication protocol loaded by the target driving packet. In this way, the connection response message of the target controller is obtained through the first communication protocol, and the type of the target controller is determined according to the connection response message, so that the data communication of the target controller is realized according to the target driving package matched with the target type, the data acquisition and integration of tightening controllers of different suppliers brands, models and types are realized through unified data communication protocols and standards, the complicated work of independently developing a data communication program for each tightening controller is avoided, the management difficulty of the tightening controllers is reduced, and the working efficiency is further improved.
Drawings
FIG. 1 is a schematic diagram of an application environment for implementing a data communication method in accordance with an embodiment of the present invention;
FIG. 2 is a flow chart of a method of data communication for tightening a controller in accordance with an embodiment of the present invention;
FIG. 3 is a schematic diagram of a graphical interface for receiving user configuration information in accordance with an embodiment of the present invention;
FIG. 4 is a flow chart of a method of data communication for tightening a controller in accordance with an embodiment of the present invention;
FIG. 5 is a flow chart of another method of data communication for tightening a controller in accordance with an embodiment of the present invention;
fig. 6 is a schematic diagram of a data communication system for tightening a controller in accordance with an embodiment of the present invention.
Detailed Description
Other advantages and effects of the present invention will become apparent to those skilled in the art from the following disclosure, which describes the embodiments of the present invention with reference to specific examples. The invention may be practiced or carried out in other embodiments that depart from the specific details, and the details of the present description may be modified or varied from the spirit and scope of the present invention. It should be noted that, without conflict, the following embodiments and sub-samples in the embodiments may be combined with each other.
It should be noted that the illustrations provided in the following embodiments merely illustrate the basic concept of the present invention by way of illustration, and only the components related to the present invention are shown in the drawings and are not drawn according to the number, shape and size of the components in actual implementation, and the form, number and proportion of the components in actual implementation may be arbitrarily changed, and the layout of the components may be more complicated.
In the following description, numerous details are set forth in order to provide a more thorough explanation of embodiments of the present invention, it will be apparent, however, to one skilled in the art that embodiments of the present invention may be practiced without these specific details, in other embodiments, well-known structures and devices are shown in block diagram form, rather than in detail, in order to avoid obscuring the embodiments of the present invention.
The terms first, second and the like in the description and in the claims of the embodiments of the disclosure and in the above-described figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate in order to describe embodiments of the present disclosure. Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion.
The term "plurality" means two or more, unless otherwise indicated.
In the embodiment of the present disclosure, the character "/" indicates that the front and rear objects are an or relationship. For example, A/B represents: a or B.
The term "and/or" is an associative relationship that describes an object, meaning that there may be three relationships. For example, a and/or B, represent: a or B, or, A and B.
Before describing embodiments of the present invention in further detail, the terms and terminology involved in the embodiments of the present invention will be described, and the terms and terminology involved in the embodiments of the present invention will be used in the following explanation.
The Open Protocol is a communication Protocol that discloses a standard that allows for the communication and exchange of data between different hardware, software, and systems. It is usually formulated by an open organization or standards body, and anyone can view its standard documents or participate in its development. This disclosed property makes the Open Protocol a common technical basis that can be used by different vendors and developers together to develop respective products and solutions.
The business system is mainly a software system for business such as enterprise production management, order processing, inventory management, purchase management and the like. These systems typically include the following functions: production planning: making a production plan including what products are produced, the number of products produced, the production time and the like; production scheduling: scheduling production according to a production plan, including scheduling of production lines, scheduling of production time, etc.; order processing: processing orders of clients, including order entry, auditing, shipping and the like; inventory management: managing the inventory of a warehouse, including warehousing, ex-warehouse, inventory and the like of commodities; purchasing management: managing purchasing business, including making purchasing plan, generating purchasing order, purchasing warehouse-in and so on; financial management: managing finance of enterprises, including bill input, auditing, payment and the like; the business systems of the production industry are typically customized according to the actual needs and business processes of the enterprise, and thus the business systems of each enterprise may be different. However, as the informatization degree of enterprises increases, more and more enterprises choose to use a general business system to meet the requirements of production management.
Referring to fig. 1, an embodiment of the present disclosure provides an application environment for implementing a data communication method for a tightening controller, where the tightening controller, a user terminal, and a server side communicate with each other through a network.
The tightening controller is used for collecting controller data.
The user terminal is configured to execute user instructions comprising at least a portion of: transmitting a connection request to a target controller based on a first communication protocol to acquire a connection response message fed back by the target controller; determining a target type corresponding to the target controller from the connection response message; matching from a preset communication driving library according to the target type to obtain a target driving package; the target drive package is loaded for data communication with the target controller based on a second communication protocol loaded by the target drive package.
The server side is used for acquiring the controller data sent to the user terminal by the tightening controller.
As shown in connection with fig. 2, an embodiment of the present disclosure provides a data communication method for tightening a controller, applied to a user terminal, the method including:
step S201, a connection request is sent to a target controller based on a first communication protocol to acquire a connection response message fed back by the target controller;
the tightening controller comprises a target controller;
wherein each tightening controller supports a first communication protocol;
step S202, determining a target type corresponding to a target controller from a connection response message;
step S203, matching is carried out from a preset communication driving library according to the target type, and a target driving package is obtained;
the communication driving library stores one or more communication driving packages corresponding to the types of the controllers respectively;
step S204, loading the target driving packet to perform data communication with the target controller based on the second communication protocol loaded by the target driving packet;
the second communication protocol only supports tightening controllers corresponding to the same target type.
By adopting the data communication method for the tightening controllers, which is provided by the embodiment of the disclosure, the connection response message fed back by the target controller is obtained through each tightening controller supporting the first communication protocol, and the target type corresponding to the target controller is determined according to the connection response message, so that the target driving packet corresponding to the target type is obtained by matching, and the data communication is performed with the target controller based on the second communication protocol loaded by the target driving packet. In this way, the connection response message of the target controller is obtained through the first communication protocol, and the type of the target controller is determined according to the connection response message, so that the data communication of the target controller is realized according to the target driving package matched with the target type, the data acquisition and integration of tightening controllers of different suppliers brands, models and types are realized through unified data communication protocols and standards, the complicated work of independently developing a data communication program for each tightening controller is avoided, the management difficulty of the tightening controllers is reduced, and the working efficiency is further improved.
Optionally, sending a connection request to the target controller based on the first communication protocol includes: acquiring user configuration information corresponding to a target controller, wherein the user configuration information comprises connection parameters and channel information; and sending a connection request supported by the first communication protocol to the target controller according to the connection parameters, and establishing a connection channel between the server side and the target controller according to the channel information.
With reference to fig. 3, a graphical interface corresponding to the user configuration information is displayed; receiving channel information input by a user through a graphical interface, wherein the channel information comprises a channel name and a drive name; and receiving connection parameters input by a user through a graphical interface, wherein the connection parameters comprise connection IP, connection ports, connection versions and the like.
In some embodiments, each tightening controller supports connection of user terminals through a first communication Protocol developed based on the Open Protocol and data transmission in the form of ASCII (American Standard Code for Information Interchange ) characters.
In some embodiments, the connection request is composed based on a Header Field (Header), a Data content Field (Data Field), and an End of Message Field (Message End), the meaning of the fields in the connection request are shown in table 1.
TABLE 1
Optionally, the connection response message includes at least one of: a network Cell field (Cell ID) for carrying an identifier of a Cell in which the target controller is located; a network Channel field (Channel ID) for carrying an identifier of a Channel where the target controller is located; a Name field (Controller Name) for carrying the Name of the target Controller; a vendor field (vendor code) for carrying vendor codes; a protocol version field (Open Protocol version) for carrying a protocol version of a preset communication protocol, wherein the first communication protocol and the second communication protocol are developed based on the preset communication protocol; a controller version field (Controller software version) for carrying a controller software version of the target controller; a tool version field (Tool software version) for carrying a tool software version of the target controller; a base unit Type field (RBU Type) for carrying a Type of remote base unit (RBU, remote Base Station Unit); a sequence number field (Controller Serial Number) for carrying a sequence number of the target controller; a System type field (System type) for carrying a System type of the target controller; a System subtype field (System subtype) for carrying the System subtype of the target controller.
In some embodiments, the connection response message is shown in table 2, and the user terminal sends a connection request "MID 0001 Application Communication Start" to the target controller, the message example is "00200001003 NUL", and the target controller feeds back the connection response message "MID 0002 Application Communication Start Acknowledge".
TABLE 2
Optionally, determining the target type corresponding to the target controller from the connection response message includes: extracting target parameters from the connection response message, wherein the target parameters comprise one or more of a provider field, a protocol version field, a tool version field, a system type field and a system subtype field; matching from a preset supplier library according to the target parameters to obtain supplier information corresponding to the target controller, wherein the supplier library comprises one or more supplier parameters corresponding to the supplier information; and determining the supplier information corresponding to the target controller as a target type.
In some embodiments, the vendor brands of the target controllers are comprehensively analyzed according to the correspondence between vendor information and vendor parameters matching the target types to which the target parameters correspond.
In some embodiments, the target type may be a controller model number or the like in addition to vendor information.
In this way, because the controller IDs (Identity document, identification numbers) of the tightening controllers are different, the controller IDs are matched with the communication driving packets one by one, and the same target type corresponds to a plurality of tightening controllers by taking the target types such as the brand of the suppliers of the controllers and the model of the controllers as the basis, thereby avoiding the establishment of the corresponding relation between each controller ID and the communication driving packet, reducing the workload and improving the working efficiency.
Optionally, the communication with the target controller is performed based on a second communication protocol loaded by the target drive packet by: acquiring a data acquisition instruction supported by a second communication protocol; transmitting a data acquisition instruction to the target controller based on a second communication protocol, wherein the data acquisition instruction is used for controlling the target controller to acquire controller data; controller data fed back by the target controller is received.
In some embodiments, based on the Opte Protocol, each vendor defines different communication protocols and data formats for data collection to obtain second communication protocols corresponding to different offered brands; and automatically switching the driving based on the target driving package so as to acquire data of the tightening controller by adopting different MID messages aiming at different manufacturers.
In some embodiments, for the data collection instructions to collect tightening curve data, the data collection instructions of vendor brand a include "MID 0900Trace Curve Data Message", the data collection instructions of vendor brand B include "MID 7409Last Tightening Curve Data Subscribe", the data collection instructions of vendor brand C include "MID 0060Last Tightening Result Data Subscribe" and the message protocol version field is "500".
Optionally, after the data communication with the target controller according to the second communication protocol loaded by the target drive packet, the method further includes: the user terminal is connected with a server terminal; acquiring a service data format supported by a server side, and extracting target data from the controller data according to a second communication protocol, wherein the target data comprises one or more of alarm data, tightening result data, tightening curve data and tool data; converting the target data into service data according to the service data format; and sending the service data to the server side in a mode of service system information.
In some embodiments, the server side includes a business system, wherein the business system includes one or more of an ERP (Enterprise Resource Planning ) system, an OA (Office Automation, office Automation) system, an EIP (Enterprise Information Platform, user centric) system, a PLM (Product Lifecycle Management ) system, and the like.
In this way, the data formats of the controllers corresponding to different controller types have larger difference, target data are extracted according to the second communication protocol, and the data of different tightening controllers are converted into a unified format according to the unified service data format, so that a user can conveniently respond to the service data in the unified format, and the service data are integrated with a service system of a server side.
Optionally, the service system message includes at least one of: an information field for carrying controller information of the target controller; an alarm field for carrying alarm data; a tightening result field for carrying tightening result data; the tightening curve field is used for bearing tightening curve data; and the tool data field is used for bearing tool data.
In some embodiments, a portion of the format of the business system message is shown in table 3.
Optionally, the method further comprises: storing acquired data, wherein the acquired data comprises one or more of controller data, target data, and business data; responding to a data query instruction, a data analysis instruction or a data backtracking instruction input by a user according to the stored acquired data.
Therefore, the controller data, the target data and the business data are stored, so that the controller data, the target data and the business data are used for subsequent unified monitoring and analysis, comprehensive data support is provided for users, and the controller data, the target data and the business data are used for backtracking, inquiring and analyzing the data, so that convenience is provided for the users in terms of production management and production optimization.
As shown in connection with fig. 4, an embodiment of the present disclosure provides a data communication method for tightening a controller, including:
step S401, a user terminal acquires user configuration information;
step S402, the user terminal sends a connection request to the target controller based on a first communication protocol;
step S403, the target controller sends a connection response message to the user terminal;
step S404, the user terminal determines the target type corresponding to the target controller from the connection response message;
step S405, the user terminal matches from a preset communication driving library according to the target type to obtain a target driving package;
step S406, the user terminal loads the target driving package;
step S407, the user terminal sends a data acquisition instruction to the target controller based on a second communication protocol;
step S408, the target controller collects controller data;
step S409, the target controller sends controller data to the user terminal;
step S410, the user terminal extracts target data from the controller data according to the second communication protocol;
the target data comprises one or more of alarm data, tightening result data, tightening curve data and tool data;
step S411, the user terminal converts the target data into service data according to the service data format;
step S412, the user terminal sends the service data to the server in the form of service system information;
step S413, the server responds to a data query instruction, a data analysis instruction or a data backtracking instruction input by a user according to the stored acquired data;
wherein the collected data includes one or more of controller data, target data, and business data.
By adopting the data communication method for tightening controllers provided by the embodiment of the disclosure, the tightening controllers support the first communication protocol to obtain the connection response message fed back by the target controller, and the target type corresponding to the target controller is determined according to the connection response message, so that the target driving packet corresponding to the target type is obtained by matching, and the data communication is performed with the target controller based on the second communication protocol loaded by the target driving packet, thereby having the following advantages:
firstly, realizing data acquisition and integration of tightening controllers of different vendor brands, models and types through unified data communication protocols and standards;
secondly, the complicated work of independently developing a data communication program for each tightening controller is avoided, the management difficulty of the tightening controllers is reduced, and the working efficiency is further improved;
thirdly, as the controller IDs of the tightening controllers are different, the controller IDs are matched with the communication driving package one by one, and the same target type corresponds to a plurality of tightening controllers by taking the target types such as the brand of a supplier of the controller, the model of the controller and the like as the basis, so that the establishment of the corresponding relation between each controller ID and the communication driving package is avoided, the workload is reduced, and the working efficiency is improved;
the data formats of the controllers corresponding to the fourth and different controller types have larger difference, target data are extracted according to the second communication protocol, and the data of different tightening controllers are converted into a unified format according to the unified service data format, so that a user can conveniently respond to the service data in the unified format, and the service data are integrated with a service system of a server side;
and fifthly, storing the controller data, the target data and the business data, wherein the controller data, the target data and the business data are used for subsequent unified monitoring and analysis, comprehensive data support is provided for users, and the controller data, the target data and the business data are used for backtracking, inquiring and analyzing the data, so that convenience is provided for the users to production management and production optimization in two aspects.
Referring to fig. 5, an embodiment of the disclosure provides a data communication method for a tightening controller, where the tightening controller includes a target controller, and the method is applied to a server, and includes:
step S501, a connection request is sent to a target controller based on a first communication protocol to acquire a connection response message fed back by the target controller;
wherein each tightening controller supports a first communication protocol;
step S502, determining a target type corresponding to the target controller from the connection response message;
step S503, matching is carried out from a preset communication driving library according to the target type to obtain a target driving package, wherein the communication driving library stores one or more communication driving packages corresponding to the controller types respectively;
in step S504, the target driving packet is loaded to perform data communication with the target controller based on the second communication protocol loaded by the target driving packet.
By adopting the data communication method for the tightening controllers, which is provided by the embodiment of the disclosure, the connection response message fed back by the target controller is obtained through each tightening controller supporting the first communication protocol, and the target type corresponding to the target controller is determined according to the connection response message, so that the target driving packet corresponding to the target type is obtained by matching, and the data communication is performed with the target controller based on the second communication protocol loaded by the target driving packet. In this way, the connection response message of the target controller is obtained through the first communication protocol, and the type of the target controller is determined according to the connection response message, so that the data communication of the target controller is realized according to the target driving package matched with the target type, the data acquisition and integration of tightening controllers of different suppliers brands, models and types are realized through unified data communication protocols and standards, the complicated work of independently developing a data communication program for each tightening controller is avoided, the management difficulty of the tightening controllers is reduced, and the working efficiency is further improved.
Optionally, after the data communication with the target controller according to the second communication protocol loaded by the target drive packet, the method further includes: the server side is provided with a service system; acquiring a service data format supported by a service system, and extracting target data from the controller data according to a second communication protocol, wherein the target data comprises one or more of alarm data, tightening result data, tightening curve data and tool data; converting the target data into service data according to the service data format; and sending the service data to the service system in a mode of service system information.
As shown in connection with fig. 6, an embodiment of the present disclosure provides a data communication system for a tightening controller, including a tightening controller 601, a user terminal 602, and a server side 603.
One or more tightening controllers 601 are connected to the user terminal or server side, wherein the tightening controllers comprise a target controller.
The user terminal 602 or the server 603 is configured to send a connection request to a target controller based on a first communication protocol, so as to obtain a connection response message fed back by the target controller, where each tightening controller supports the first communication protocol; determining a target type corresponding to the target controller from the connection response message; matching from a preset communication driving library according to the target type to obtain a target driving package, wherein the communication driving library stores one or more communication driving packages corresponding to the controller types respectively; the target drive package is loaded for data communication with the target controller based on a second communication protocol loaded by the target drive package.
By adopting the data communication system for tightening controllers provided by the embodiment of the disclosure, each tightening controller supports a first communication protocol to obtain a connection response message fed back by a target controller, and determines a target type corresponding to the target controller according to the connection response message, so as to obtain a target driving packet corresponding to the target type in a matching manner, and perform data communication with the target controller based on a second communication protocol loaded by the target driving packet. In this way, the connection response message of the target controller is obtained through the first communication protocol, and the type of the target controller is determined according to the connection response message, so that the data communication of the target controller is realized according to the target driving package matched with the target type, the data acquisition and integration of tightening controllers of different suppliers brands, models and types are realized through unified data communication protocols and standards, the complicated work of independently developing a data communication program for each tightening controller is avoided, the management difficulty of the tightening controllers is reduced, and the working efficiency is further improved.
The above description and the drawings illustrate embodiments of the disclosure sufficiently to enable those skilled in the art to practice them. Other embodiments may involve structural, logical, electrical, process, and other changes. The embodiments represent only possible variations. Individual components and functions are optional unless explicitly required, and the sequence of operations may vary. Portions and sub-samples of some embodiments may be included in or substituted for portions and sub-samples of other embodiments. Moreover, the terminology used in the present application is for the purpose of describing embodiments only and is not intended to limit the claims. As used in the description of the embodiments and the claims, the singular forms "a," "an," and "the" (the) are intended to include the plural forms as well, unless the context clearly indicates otherwise. Similarly, the term "and/or" as used in this application is meant to encompass any and all possible combinations of one or more of the associated listed. In addition, when used in this application, the terms "comprises," "comprising," and/or "includes," and variations thereof, mean the presence of the stated sub-sample, integer, step, operation, element, and/or component, but do not exclude the presence or addition of one or more other sub-samples, integers, steps, operations, elements, components, and/or groups of these. Without further limitation, an element defined by the phrase "comprising one …" does not exclude the presence of other like elements in a process, method or apparatus comprising such elements. In this context, each embodiment may be described with emphasis on the differences from the other embodiments, and the same similar parts between the various embodiments may be referred to each other. For the methods, products, etc. disclosed in the embodiments, if they correspond to the method sections disclosed in the embodiments, the description of the method sections may be referred to for relevance.
Those of skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. The skilled person may use different methods for each particular application to achieve the described functionality, but such implementation should not be considered to be beyond the scope of the embodiments of the present disclosure. It will be clearly understood by those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not described herein again.
In the embodiments disclosed herein, the disclosed methods, articles of manufacture (including but not limited to devices, apparatuses, etc.) may be practiced in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of elements may be merely a logical functional division, and there may be additional divisions in actual implementation, e.g., multiple elements or components may be combined or integrated into another system, or some sub-samples may be omitted, or not performed. In addition, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interface, device or unit indirect coupling or communication connection, which may be in electrical, mechanical or other form. The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to implement the present embodiment. In addition, each functional unit in the embodiments of the present disclosure may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. In the description corresponding to the flowcharts and block diagrams in the figures, operations or steps corresponding to different blocks may also occur in different orders than that disclosed in the description, and sometimes no specific order exists between different operations or steps. For example, two consecutive operations or steps may actually be performed substantially in parallel, they may sometimes be performed in reverse order, which may be dependent on the functions involved. Each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Claims (10)
1. A data communication method for a tightening controller, the tightening controller including a target controller applied to a user terminal, the method comprising:
transmitting a connection request to the target controller based on a first communication protocol to acquire a connection response message fed back by the target controller, wherein each tightening controller supports the first communication protocol;
determining a target type corresponding to the target controller from the connection response message;
matching from a preset communication driving library according to the target type to obtain a target driving package, wherein the communication driving library stores one or more communication driving packages corresponding to the controller types respectively;
and loading the target driving packet so as to carry out data communication with the target controller based on a second communication protocol loaded by the target driving packet.
2. The method of claim 1, wherein sending a connection request to the target controller based on a first communication protocol comprises:
acquiring user configuration information corresponding to the target controller, wherein the user configuration information comprises connection parameters and channel information;
and sending a connection request supported by the first communication protocol to the target controller according to the connection parameters, and establishing a connection channel between the server side and the target controller according to the channel information.
3. The method of claim 1, wherein the connection response message comprises at least one of:
a network cell field, configured to carry an identifier of a cell in which the target controller is located;
a network channel field, configured to carry an identifier of a channel where the target controller is located;
a name field for carrying the name of the target controller;
a vendor field for carrying a vendor code;
a protocol version field, configured to carry a protocol version of a preset communication protocol, where the first communication protocol and the second communication protocol are both developed based on the preset communication protocol;
a controller version field for carrying a controller software version of the target controller;
a tool version field for carrying a tool software version of the target controller;
a base station unit type field for carrying a type of remote base station unit;
a sequence number field, configured to carry a sequence number of the target controller;
a system type field for carrying a system type of the target controller;
and a system subtype field for carrying a system subtype of the target controller.
4. A method according to claim 3, wherein determining the target type corresponding to the target controller from the connection response message comprises:
extracting target parameters from the connection response message, wherein the target parameters comprise one or more of a provider field, a protocol version field, a tool version field, a system type field and a system subtype field;
matching from a preset supplier library according to the target parameters to obtain supplier information corresponding to the target controller, wherein the supplier library comprises one or more supplier parameters corresponding to the supplier information;
and determining the supplier information corresponding to the target controller as a target type.
5. The method of any of claims 1 to 4, wherein the communication with the target controller is based on a second communication protocol loaded by the target drive packet by:
acquiring a data acquisition instruction supported by the second communication protocol;
transmitting the data acquisition instruction to the target controller based on the second communication protocol, wherein the data acquisition instruction is used for controlling the target controller to acquire controller data;
and receiving the controller data fed back by the target controller.
6. The method of claim 5, wherein after data communication with the target controller according to the second communication protocol loaded by the target drive packet, the method further comprises:
the user terminal is connected with a server;
acquiring a service data format supported by the server side, and extracting target data from the controller data according to the second communication protocol, wherein the target data comprises one or more of alarm data, tightening result data, tightening curve data and tool data;
converting the target data into service data according to the service data format;
and sending the service data to the server side in a service system message mode.
7. The method of claim 6, wherein the business system message comprises at least one of:
an information field for carrying controller information of the target controller;
an alarm field for carrying the alarm data;
a tightening result field for carrying the tightening result data;
a tightening curve field for carrying the tightening curve data;
and the tool data field is used for bearing the tool data.
8. The method of claim 6, wherein the method further comprises:
storing acquired data, wherein the acquired data comprises one or more of controller data, target data, and business data;
responding to a data query instruction, a data analysis instruction or a data backtracking instruction input by a user according to the stored acquired data.
9. A data communication method for a tightening controller, wherein the tightening controller includes a target controller, and is applied to a server, the method comprising:
transmitting a connection request to the target controller based on a first communication protocol to acquire a connection response message fed back by the target controller, wherein each tightening controller supports the first communication protocol;
determining a target type corresponding to the target controller from the connection response message;
matching from a preset communication driving library according to the target type to obtain a target driving package, wherein the communication driving library stores one or more communication driving packages corresponding to the controller types respectively;
and loading the target driving packet so as to carry out data communication with the target controller based on a second communication protocol loaded by the target driving packet.
10. A data communication system for tightening a controller, comprising:
one or more tightening controllers connected with a user terminal or a server, wherein the tightening controllers comprise a target controller;
the user terminal or the server side is configured to send a connection request to the target controller based on a first communication protocol, so as to obtain a connection response message fed back by the target controller, where each tightening controller supports the first communication protocol; determining a target type corresponding to the target controller from the connection response message; matching from a preset communication driving library according to the target type to obtain a target driving package, wherein the communication driving library stores one or more communication driving packages corresponding to the controller types respectively; and loading the target driving packet so as to carry out data communication with the target controller based on a second communication protocol loaded by the target driving packet.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311430931.0A CN117376438A (en) | 2023-10-31 | 2023-10-31 | Data communication method and system for tightening controller |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311430931.0A CN117376438A (en) | 2023-10-31 | 2023-10-31 | Data communication method and system for tightening controller |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117376438A true CN117376438A (en) | 2024-01-09 |
Family
ID=89407498
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311430931.0A Pending CN117376438A (en) | 2023-10-31 | 2023-10-31 | Data communication method and system for tightening controller |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117376438A (en) |
-
2023
- 2023-10-31 CN CN202311430931.0A patent/CN117376438A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104636421A (en) | Industrial monitoring using cloud computing | |
| CN110688828A (en) | File processing method and device, file processing system and computer equipment | |
| CN111125518B (en) | Household appliance information recommendation system and method | |
| CN102682105A (en) | System and method for identifying and acquiring related web page information by using mobile terminal | |
| CN113505265B (en) | Data query method and device, electronic equipment, storage medium and program product | |
| CN107133233B (en) | Processing method and device for configuration data query | |
| CN107704357B (en) | Log generation method and device | |
| US20120072589A1 (en) | Information Processing Apparatus and Method of Operating the Same | |
| CN111324786A (en) | Method and device for processing consultation problem information | |
| CN108648064A (en) | The method and apparatus of the quick restocking of product information | |
| CN116069838A (en) | Data processing method, device, computer equipment and storage medium | |
| CN111753056A (en) | Information pushing method and device, computing equipment and computer readable storage medium | |
| CN117376438A (en) | Data communication method and system for tightening controller | |
| KR100974621B1 (en) | Radio frequency identification business-aware framework | |
| CN107679096B (en) | Method and device for sharing indexes among data marts | |
| EP3539075B1 (en) | Multi-factor routing system for exchanging business transactions | |
| CN112204527A (en) | Method and system for processing engineering data in a multi-engineering system environment | |
| JP4336251B2 (en) | Traceability system, trace information management method, trace information management program, and recording medium | |
| JP7035326B2 (en) | Server equipment, asset management systems, control methods, and programs | |
| CN106649678B (en) | Data processing method and system | |
| EP3660763A1 (en) | Highly scalable event brokering and audit traceability system | |
| CN112070391A (en) | Workshop production task management system, method and device | |
| CN102567388B (en) | Device and method for data update | |
| CN105701187B (en) | Process integrated service device and the method for realizing system combination using it | |
| JP2017004139A (en) | Format conversion management device and format conversion management method |
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 |