CN111431784A - Universal MODBUS protocol data analysis method - Google Patents
Universal MODBUS protocol data analysis method Download PDFInfo
- Publication number
- CN111431784A CN111431784A CN202010315960.2A CN202010315960A CN111431784A CN 111431784 A CN111431784 A CN 111431784A CN 202010315960 A CN202010315960 A CN 202010315960A CN 111431784 A CN111431784 A CN 111431784A
- Authority
- CN
- China
- Prior art keywords
- data
- configuration
- definition
- protocol
- software
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- 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/22—Parsing or analysis of headers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L2012/40208—Bus networks characterized by the use of a particular bus standard
- H04L2012/40228—Modbus
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Communication Control (AREA)
Abstract
The invention discloses a universal MODBUS protocol data analysis method, in particular to the technical field of communication software development, wherein MODBUS acquisition software is accessed to slave station equipment by importing a data configuration file, and the method comprises the following specific steps: the method comprises the following steps: an MODBUS acquisition software developer acquires a slave station data definition table in advance and converts the definition table into a required configuration file format; step two: the collection software supports loading and importing a data definition configuration table, and the configuration table is used in the message analysis process; step three: and in the message analysis process, converting the original message data into interface visual data according to the data configuration information in the configuration table. The flexible MODBUS protocol configuration data method provided by the invention can meet the protocol data analysis requirement, can enable the acquisition software to be developed and shaped at one time on the premise of meeting the visual data, does not influence the acquisition software due to the change of the equipment data definition, and greatly reduces the software development cost.
Description
Technical Field
The embodiment of the invention relates to the technical field of communication software development, in particular to a universal MODBUS protocol data analysis method.
Background
The MODBUS protocol-based software development technology for communication includes three parts: interactive flow, message format and data definition. The interactive process and the message format are clearly defined in the standard protocol, the protocol implementation of different manufacturer equipment cannot be different, and the acquisition software is stable in adaptation to the interactive process and the message format. The data definition is open, different manufacturers and different devices may have independent data definitions, the data definition is a key of communication interaction, and the acquired original data cannot be correctly analyzed without the data definition, so that the data cannot be visualized. Key elements of the data definition include: data name, membership data block, data address, data amount (length), data type, data coefficient, byte order, word order. The MODBUS protocol does not define a data self-description scheme, so none of the above elements is embodied in the message data. For this reason, MODBUS acquisition software needs to provide a complete data definition table from the station device. During development, software re-or incremental development is required for each access to a new data-defining device protocol.
A large amount of equipment of industrial control industry have used MODBUS agreement to carry out data interaction, need resolve the agreement data into the visual data of interface after host computer software or desktop debugging software data acquisition, because equipment difference leads to agreement data definition diverse, this analysis conversion process needs software reduplication, accomplish the adaptation of new equipment data definition through the mode of upgrading software version, the human input cost is high, equipment inserts the development inefficiency
Disclosure of Invention
Therefore, the embodiment of the invention provides a universal MODBUS protocol data analysis method, provides a flexible MODBUS protocol data configuration method, achieves the protocol data analysis requirement, can enable the acquisition software to be developed and shaped at one time on the premise of meeting the visual data, does not influence the acquisition software due to the change of the equipment data definition, and greatly reduces the software development cost.
In order to achieve the above object, the embodiments of the present invention provide the following technical solutions: a general MODBUS protocol data analysis method is characterized in that MODBUS acquisition software is accessed to slave station equipment in a data configuration file importing mode, and the method specifically comprises the following steps:
the method comprises the following steps: an MODBUS acquisition software developer acquires a slave station data definition table in advance and converts the definition table into a required configuration file format;
step two: the collection software supports loading and importing a data definition configuration table, and the configuration table is used in the message analysis process;
step three: and in the message analysis process, converting the original message data into interface visual data according to the data configuration information in the configuration table.
Further, according to key elements in the MODBUS data definition, the configuration table definition method is as follows:
s1, each device has an independent data configuration based on the device granularity;
s2, the device configuration node includes the following attribute configuration items:
a. device Name: defining visual names for distinguishing different devices;
b. membership port PortName: associating a background communication channel;
c. device type DeviceType: for distinguishing device classes;
d. device address Addr: communication address definition;
s3, under each equipment configuration node, a plurality of data configuration nodes are provided;
s4, the data configuration node comprises the following configuration items:
a. data Name: defining a visual name for distinguishing different data;
b. a membership data block B L OCK for defining the data category and the protocol data block;
c. data address Addr: a data address required by the protocol;
d. data Size/length Size: the BIT number or register number occupied by the current data;
e. data coefficient Coef: multiple information participating in operation when shaping is converted into a floating point type;
f. protocol transmission type PrtcTYPE: types defined during data transmission;
g. data visualization type ShowType: the target type to be converted is displayed on a data interface;
h. data Unit: visualization fields, which do not participate in the conversion calculation process;
i. data Range: visualization fields, which do not participate in the conversion calculation process;
j. endian ByteOder: defining the sequence of multi-byte data in protocol transmission;
k. word order WordOder: defining the sequence of the multi-word data in protocol transmission;
l, interval time: defining a transmission interval between each data request;
m, timeout Time: defining an unresponsive timeout for each data request;
n, retransmission number ResendCount: the number of retransmissions after a timeout of the data request is defined.
Further, the protocol transmission types include:
a. signed shaping PT _ INT: the software is divided into 2, 4 and 8 bytes of data according to the data length;
b. unsigned shaping PT _ UINT: the software is divided into 2, 4 and 8 bytes of data according to the data length;
c. the floating point type PT _ F L OAT is characterized in that the software is divided into 4 and 8 bytes of data according to the data length;
d. byte stream PT _ BYTES: in combination with the data length, the software can define any length within the maximum length range allowed by the protocol;
e. BIT data PT _ BIT: accounting for only 1 Bit.
Further, the data visualization types include:
a. a floating point type ST _ F L OAT, wherein software definition is a high precision type to receive converted data, and display precision is determined by coefficients of data definition;
b. reshaping the 10-ary ST _ INT-DEC: presenting the visualized integer data in a 10-ary manner;
c. shaping 16-ary ST _ INT-HEX: rendering the visualization reshaping data in a 16-ary manner, e.g., 0X 0012;
d. byte stream ST _ BYTES: presenting the data in a byte stream;
e. character STRING ST _ STRING: presenting the data in a character string manner;
f. BIT data ST _ BIT: the data is presented in bits, with the presentation data being only 0 or 1.
Further, the definition and mapping relationship between the protocol transmission type and the data visualization type are as follows:
a. the signed shaping in the protocol transmission can be converted into visual floating point data, ST _ F L OAT (PT _ INT) Coef;
b. signed shaping in protocol transmission can be converted into visualized shaped decimal data: ST _ INT-DEC ═ formatted ("% d", PT _ INT);
c. signed shaping in protocol transmission can be converted into visualized shaped hexadecimal data: ST _ INT-HEX format ("0X% X", PT _ INT);
d. unsigned shaping in protocol transmission is as above;
e. the floating point type in the protocol transmission can be converted into visual floating point type data only, wherein ST _ F L OAT is PT _ F L OAT;
f. the byte stream in the protocol transmission can be converted into visualized byte stream data: ST _ STRING ═ STRING (PT _ BYTES);
g. the byte stream in the protocol transmission can be converted into visualized character string data: ST _ BYTES is PT _ BYTES;
h. bit data in a protocol transmission can only be converted into visualized bit data: ST _ BIT is PT _ BIT.
The embodiment of the invention has the following advantages:
the flexible MODBUS protocol configuration data method provided by the invention can meet the protocol data analysis requirement, can enable the acquisition software to be developed and shaped at one time on the premise of meeting the visual data, does not influence the acquisition software due to the change of the equipment data definition, and greatly reduces the software development cost.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below. It should be apparent that the drawings in the following description are merely exemplary, and that other embodiments can be derived from the drawings provided by those of ordinary skill in the art without inventive effort.
The structures, ratios, sizes, and the like shown in the present specification are only used for matching with the contents disclosed in the specification, so as to be understood and read by those skilled in the art, and are not used to limit the conditions that the present invention can be implemented, so that the present invention has no technical significance, and any structural modifications, changes in the ratio relationship, or adjustments of the sizes, without affecting the effects and the achievable by the present invention, should still fall within the range that the technical contents disclosed in the present invention can cover.
Fig. 1 is a flow chart of access provided by the present invention;
fig. 2 is a mapping relationship diagram of a protocol transmission type and a data visualization type provided by the present invention.
Detailed Description
The present invention is described in terms of particular embodiments, other advantages and features of the invention will become apparent to those skilled in the art from the following disclosure, and it is to be understood that the described embodiments are merely exemplary of the invention and that it is not intended to limit the invention to the particular embodiments disclosed. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example 1:
the invention provides a universal MODBUS protocol data analysis method.A MODBUS acquisition software accesses a slave station device by importing a data configuration file, and the method comprises the following specific steps:
the method comprises the following steps: the method comprises the following steps that MODBUS acquisition software developers obtain a slave station data definition table in advance, the definition table is converted into a required configuration file format, and according to key elements in MODBUS data definition, the configuration table definition method comprises the following steps:
s1, each device has an independent data configuration based on the device granularity;
s2, the device configuration node includes the following attribute configuration items:
a. device Name (Name): defining visual names for distinguishing different devices;
b. membership port (PortName): associating a background communication channel;
c. device type (DeviceType): for distinguishing device classes;
d. device address (Addr): communication address definition;
s3, under each equipment configuration node, a plurality of data configuration nodes are provided;
s4, the data configuration node comprises the following configuration items:
a. data Name (Name): defining a visual name for distinguishing different data;
b. a membership data block (B L OCK) defining the data category and belonging to the protocol data block;
c. data address (Addr): a data address required by the protocol;
d. data Size/length (Size): the BIT number or register number occupied by the current data;
e. data coefficient (Coef): multiple information participating in operation when shaping is converted into a floating point type;
f. protocol transmission type (PrtcTYPE): types defined during data transmission;
g. data visualization type (ShowType): the target type to be converted is displayed on a data interface;
h. data Unit (Unit): visualization fields, which do not participate in the conversion calculation process;
i. data Range (Range): visualization fields, which do not participate in the conversion calculation process;
j. endian (ByteOder): defining the sequence of multi-byte data in protocol transmission;
k. word order (wordmoder): defining the sequence of the multi-word data in protocol transmission;
l, interval time (IntervalTime): defining a transmission interval between each data request;
m, timeout Time (Time): defining an unresponsive timeout for each data request;
n, number of retransmissions (ResendCount): defining the retransmission times after the data request is overtime;
taking XM L format as an example:
step two: the collection software supports loading and importing a data definition configuration table, and the configuration table is used in the message analysis process;
step three: in the message analysis process, converting original message data into interface visual data according to data configuration information in a configuration table;
the protocol transmission types include:
a. signed shaping (PT _ INT): the software is divided into 2, 4 and 8 bytes of data according to the data length;
b. unsigned shaping (PT _ UINT): the software is divided into 2, 4 and 8 bytes of data according to the data length;
c. floating point (PT _ F L OAT) software is divided into 4 and 8 bytes of data according to the data length;
d. byte stream (PT _ BYTES): in combination with data length, the software can define an arbitrary length (within the maximum length allowed by the protocol);
e. BIT data (PT _ BIT): only 1 Bit;
the data visualization types include:
a. a floating point type (ST _ F L OAT) software definition for receiving the converted data in a high precision type, the display precision being determined by a coefficient of a data definition type;
b. shaping (10-ary) (ST _ INT-DEC): presenting the visualized integer data in a 10-ary manner;
c. shaping (16-ary) (ST _ INT-HEX): rendering the visualization reshaping data in a 16-ary manner, e.g., 0X 0012;
d. byte stream (ST _ BYTES): presenting data in a byte stream, e.g., 02851 A3F;
e. character STRING (ST _ STRING): presenting data in a string, such as "This is string";
f. BIT data (ST _ BIT): the data is presented in bits, with the presentation data being only 0 or 1.
The definition and mapping relationship between the protocol transmission type and the data visualization type are as follows:
a. the signed shaping in the protocol transmission can be converted into visual floating point data, ST _ F L OAT (PT _ INT) Coef;
b. signed shaping in protocol transmission can be converted into visualized shaped decimal data: ST _ INT-DEC ═ formatted ("% d", PT _ INT);
c. signed shaping in protocol transmission can be converted into visualized shaped hexadecimal data: ST _ INT-HEX format ("0X% X", PT _ INT);
d. unsigned shaping in protocol transmission is as above;
e. the floating point type in the protocol transmission can be converted into visual floating point type data only, wherein ST _ F L OAT is PT _ F L OAT;
f. the byte stream in the protocol transmission can be converted into visualized byte stream data: ST _ STRING ═ STRING (PT _ BYTES);
g. the byte stream in the protocol transmission can be converted into visualized character string data: ST _ BYTES is PT _ BYTES;
h. bit data in a protocol transmission can only be converted into visualized bit data: ST _ BIT is PT _ BIT.
Example 2:
1. different profile formats are used, rather than XM L L as mentioned in this disclosure being the only feasible solution for a profile;
2. the difference in configuration item names has no substantial difference in schema;
3. the granularity of the protocol transmission type and visualization type definitions is different, for example, the shaping region is divided into 2-byte shaping, 4-byte shaping and 8-byte shaping;
4. configuration information is imported using other loading methods, for example, the software itself provides configuration functions, and an external configuration file import process is not required.
Although the invention has been described in detail above with reference to a general description and specific examples, it will be apparent to one skilled in the art that modifications or improvements may be made thereto based on the invention. Accordingly, such modifications and improvements are intended to be within the scope of the invention as claimed.
Claims (5)
1. A universal MODBUS protocol data analysis method is characterized in that: the method comprises the following steps that MODBUS acquisition software is accessed to slave station equipment in a data configuration file importing mode:
the method comprises the following steps: an MODBUS acquisition software developer acquires a slave station data definition table in advance and converts the definition table into a required configuration file format;
step two: the collection software supports loading and importing a data definition configuration table, and the configuration table is used in the message analysis process;
step three: and in the message analysis process, converting the original message data into interface visual data according to the data configuration information in the configuration table.
2. The method of claim 1, wherein the method comprises the following steps: according to key elements in MODBUS data definition, a configuration table definition method comprises the following steps:
s1, each device has an independent data configuration based on the device granularity;
s2, the device configuration node includes the following attribute configuration items:
a. device Name: defining visual names for distinguishing different devices;
b. membership port PortName: associating a background communication channel;
c. device type DeviceType: for distinguishing device classes;
d. device address Addr: communication address definition;
s3, under each equipment configuration node, a plurality of data configuration nodes are provided;
s4, the data configuration node comprises the following configuration items:
a. data Name: defining a visual name for distinguishing different data;
b. a membership data block B L OCK for defining the data category and the protocol data block;
c. data address Addr: a data address required by the protocol;
d. data Size/length Size: the BIT number or register number occupied by the current data;
e. data coefficient Coef: multiple information participating in operation when shaping is converted into a floating point type;
f. protocol transmission type PrtcTYPE: types defined during data transmission;
g. data visualization type ShowType: the target type to be converted is displayed on a data interface;
h. data Unit: visualization fields, which do not participate in the conversion calculation process;
i. data Range: visualization fields, which do not participate in the conversion calculation process;
j. endian ByteOder: defining the sequence of multi-byte data in protocol transmission;
k. word order WordOder: defining the sequence of the multi-word data in protocol transmission;
l, interval time: defining a transmission interval between each data request;
m, timeout Time: defining an unresponsive timeout for each data request;
n, retransmission number ResendCount: the number of retransmissions after a timeout of the data request is defined.
3. The method of claim 1, wherein the method comprises the following steps: the protocol transmission types include:
a. signed shaping PT _ INT: the software is divided into 2, 4 and 8 bytes of data according to the data length;
b. unsigned shaping PT _ UINT: the software is divided into 2, 4 and 8 bytes of data according to the data length;
c. the floating point type PT _ F L OAT is characterized in that the software is divided into 4 and 8 bytes of data according to the data length;
d. byte stream PT _ BYTES: in combination with the data length, the software can define any length within the maximum length range allowed by the protocol;
e. BIT data PT _ BIT: accounting for only 1 Bit.
4. The method of claim 1, wherein the method comprises the following steps: the data visualization types include:
a. a floating point type ST _ F L OAT, wherein software definition is a high precision type to receive converted data, and display precision is determined by coefficients of data definition;
b. reshaping the 10-ary ST _ INT-DEC: presenting the visualized integer data in a 10-ary manner;
c. shaping 16-ary ST _ INT-HEX: rendering the visualization reshaping data in a 16-ary manner, e.g., 0X 0012;
d. byte stream ST _ BYTES: presenting the data in a byte stream;
e. character STRING ST _ STRING: presenting the data in a character string manner;
f. BIT data ST _ BIT: the data is presented in bits, with the presentation data being only 0 or 1.
5. The method of claim 1, wherein the method comprises the following steps: the definition and mapping relationship between the protocol transmission type and the data visualization type are as follows:
a. the signed shaping in the protocol transmission can be converted into visual floating point data, ST _ F L OAT (PT _ INT) Coef;
b. signed shaping in protocol transmission can be converted into visualized shaped decimal data: ST _ INT-DEC ═ formatted ("% d", PT _ INT);
c. signed shaping in protocol transmission can be converted into visualized shaped hexadecimal data: ST _ INT-HEX format ("0X% X", PT _ INT);
d. unsigned shaping in protocol transmission is as above;
e. the floating point type in the protocol transmission can be converted into visual floating point type data only, wherein ST _ F L OAT is PT _ F L OAT;
f. the byte stream in the protocol transmission can be converted into visualized byte stream data: ST _ STRING ═ STRING (PT _ BYTES);
g. the byte stream in the protocol transmission can be converted into visualized character string data: ST _ BYTES is PT _ BYTES;
h. bit data in a protocol transmission can only be converted into visualized bit data: ST _ BIT is PT _ BIT.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010315960.2A CN111431784A (en) | 2020-04-21 | 2020-04-21 | Universal MODBUS protocol data analysis method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010315960.2A CN111431784A (en) | 2020-04-21 | 2020-04-21 | Universal MODBUS protocol data analysis method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111431784A true CN111431784A (en) | 2020-07-17 |
Family
ID=71556523
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010315960.2A Pending CN111431784A (en) | 2020-04-21 | 2020-04-21 | Universal MODBUS protocol data analysis method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111431784A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112003837A (en) * | 2020-08-05 | 2020-11-27 | 深圳市中物互联技术发展有限公司 | Intelligent equipment adaptation method and device based on Modbus protocol and storage medium |
| CN115052051A (en) * | 2022-04-26 | 2022-09-13 | 深圳市云伽智能技术有限公司 | Information processing method, system, controller and terminal based on ICAP protocol |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103139025A (en) * | 2011-12-05 | 2013-06-05 | 艾默生网络能源系统北美公司 | Access method and access system of Modbus equipment |
| CN103792928A (en) * | 2014-02-24 | 2014-05-14 | 东南大学 | Industrial field data collecting and analyzing system based on Modbus |
| US20160350097A1 (en) * | 2015-06-01 | 2016-12-01 | Wipro Limited | Method for updating firmware and configuration file and a firmware-configuration file management system therefor |
| CN110502467A (en) * | 2019-07-25 | 2019-11-26 | 江苏诺蓝翌新能源科技有限公司 | A kind of general acquisition interface software systems based on serial ports modbus communication protocol |
-
2020
- 2020-04-21 CN CN202010315960.2A patent/CN111431784A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103139025A (en) * | 2011-12-05 | 2013-06-05 | 艾默生网络能源系统北美公司 | Access method and access system of Modbus equipment |
| CN103792928A (en) * | 2014-02-24 | 2014-05-14 | 东南大学 | Industrial field data collecting and analyzing system based on Modbus |
| US20160350097A1 (en) * | 2015-06-01 | 2016-12-01 | Wipro Limited | Method for updating firmware and configuration file and a firmware-configuration file management system therefor |
| CN110502467A (en) * | 2019-07-25 | 2019-11-26 | 江苏诺蓝翌新能源科技有限公司 | A kind of general acquisition interface software systems based on serial ports modbus communication protocol |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112003837A (en) * | 2020-08-05 | 2020-11-27 | 深圳市中物互联技术发展有限公司 | Intelligent equipment adaptation method and device based on Modbus protocol and storage medium |
| CN115052051A (en) * | 2022-04-26 | 2022-09-13 | 深圳市云伽智能技术有限公司 | Information processing method, system, controller and terminal based on ICAP protocol |
| CN115052051B (en) * | 2022-04-26 | 2023-11-17 | 深圳市云伽智能技术有限公司 | Information processing method, system, controller and terminal based on ICAP protocol |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6141767A (en) | Method of and apparatus for verifying reliability of contents within the configuration ROM of IEEE 1394-1995 devices | |
| JP5180190B2 (en) | Serialization of portable objects | |
| US7725606B2 (en) | Method and apparatus for two phase structured message to tagged message translation | |
| US7904803B2 (en) | Method and system for converting user interface source code of a legacy application to web pages | |
| US20040268306A1 (en) | Methods, systems and computer program products for language independent data communication and display | |
| CN111431784A (en) | Universal MODBUS protocol data analysis method | |
| JP2009535720A5 (en) | ||
| US7185101B2 (en) | Method, apparatus, and product for transmitting multibyte characters in a network | |
| CN113238936B (en) | Extensible universal embedded software communication interface testing method and device | |
| US6182202B1 (en) | Generating computer instructions having operand offset length fields for defining the length of variable length operand offsets | |
| US20050021870A1 (en) | Modular presentation device with network connection for use with PDA's and Smartphones | |
| CN113641700A (en) | Data processing method and device based on Spring boot frame | |
| US20100031204A1 (en) | Process-independent schema library | |
| Bruce et al. | Personal digital assistant (PDA) based I2C bus analysis | |
| CN112235316A (en) | Data communication method for instrument integration | |
| EP1298525A1 (en) | Interaction between computers with different object-oriented run-time environments | |
| US20090138796A1 (en) | System for Character Validation and Method Therefor | |
| CN115801922A (en) | Analytic rule generation method based on serial communication byte code protocol | |
| WO2018034509A1 (en) | Website creating method and system implemented in web browser | |
| CN115544061A (en) | Data query method, system, terminal and computer readable storage medium | |
| US6243765B1 (en) | Method and apparatus for data communication | |
| CN112416843A (en) | Backboard communication equipment, control method thereof and storage medium | |
| US6510215B1 (en) | Caller ID data-reporting mechanism for electronic devices and associated methods | |
| TW502195B (en) | Computer system using interface circuit to increase pins of general-purpose input/output port | |
| WO2024128344A1 (en) | Facility interworking and data visualization method using asset administration shell information model |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200717 |