Multi-adapter compatible library file module, calling method, and device

Abstract

To greatly improve development efficiency of an application program.SOLUTION: Abstraction of an adapter in an upper-layer APP is implemented by: building a library file module for each manufacturer; obtaining, by an application program, message information of a device by using the library file module; and disconnecting the device after obtaining the message information. The upper-layer APP exports generic API interfaces, creates a library file for an adapter of each manufacturer, and implements an API interface of the upper-layer APP by calling an API of the adapter of the manufacturer. The APP does not need to know any details of the adapter of the manufacturer, but only loads the library file to be able to use a function of the adapter.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention belongs to the field of adapter compatibility technology, and specifically relates to a multi-adapter compatibility library file module, a calling method, and a device.

Background Art

[0002] In the application of automotive tools, it is often necessary to use one or several types of equipment of existing various manufacturers simultaneously or alternately. The general method is to develop a single upper-level APP (application program) and support the APIs of Manufacturer A, Manufacturer B, and Manufacturer C at the same time, and arrange the mapping method so that this APP can communicate freely with the hardware of these three manufacturers. In this design, the following problems occur: When designing the APP, it is necessary to understand the API representation forms and calling methods of Manufacturer A, Manufacturer B, and Manufacturer C at the same time, and the APP includes the API calling algorithms of these three manufacturers, which improves the development difficulty and workload of the APP itself. The architecture of the APP cannot support dynamically adding new manufacturers. For example, for the devices of emerging manufacturers D and E, their APIs have clear representation forms different from those of Manufacturer A, Manufacturer B, and Manufacturer C. The architecture of the APP itself has the characteristics of being difficult to expand and lacking flexibility.

[0003] When the APP needs to support new manufacturers, such as the devices of manufacturers D and E, the implementation logic of the APP must be modified, and the API calling algorithms of manufacturers D and E are introduced into the conventional framework. This changes the APP. During the change, the workload of the software increases, and at the same time, defects may be introduced, affecting the calling of the APIs of the supported manufacturers.

[0004] Therefore, based on the above technical issues, it is necessary to design a new multi-adapter compatible library file module, calling method, and device. [Overview of the project]

[0005] The object of the present invention is to provide a multi-adapter compatible library file module, a calling method, and a device.

[0006] To solve the above technical problems, the present invention provides a multi-adapter compatible library file module, which includes: These include a submodule for reading the serial number, a submodule for reading the number of channels, a submodule for reading the channel type, a submodule for reading the channel baud rate, a submodule for writing the channel baud rate, a connection submodule, a message transmission submodule, a message reception submodule, and a disconnection submodule. Furthermore, the submodule that reads the serial number is suitable for reading the device API from the library file and returning the device's serial number to the application program. The submodule that reads the above channel count is suitable for reading the device API from a library file and returning the physical channel count of the device to the application program. The submodule that reads the above channel type is suitable for reading the device API from a library file and returning the type of a specific channel on the device to the application program. The submodule for reading the baud rate of the above channel is suitable for reading the above device API from the above library file and returning the baud rate of a specific channel to the above application program. The submodule for writing the baud rate of the above channel is suitable for calling the above device API from the above library file and writing the baud rate provided to the APP to the above device. The above connection submodule is suitable for establishing a connection between the above application and the above device by calling the above device API from the above library file. The above message sending submodule is suitable for calling the above device API from the above library file and writing the messages that need to be sent, which are given to the above APP, to the above device. The above message receiving submodule is suitable for calling the above device API from the above library file and returning the above messages read by the above device from all channels to the above application program. The above disconnection submodule is suitable for disconnecting the above device from the above application program by calling the above device API from the above library file.

[0007] In a second aspect, the present invention further provides a multi-adapter compatible calling method, which includes: We will build library file modules for each manufacturer. The application program obtains the device's message information using the above library file module, and After obtaining the above message information, disconnect from the above device.

[0008] Furthermore, the methods for building library file modules for each of the above manufacturers include the following: The above library file module includes a submodule for reading the serial number, a submodule for reading the number of channels, a submodule for reading the channel type, a submodule for reading the channel baud rate, a submodule for writing the channel baud rate, a connection submodule, a message transmission submodule, a message reception submodule, and a disconnection submodule. The submodule that reads the above serial number is suitable for reading the device API from the above library file and returning the serial number of the above device to the above application program. The submodule that reads the above number of channels is suitable for reading the above device API from the above library file and returning the above number of physical channels of the above device to the above application program. The submodule that reads the above channel type is suitable for reading the above device API from the above library file and returning the type of a specific channel for the above device to the above application program. The submodule for reading the baud rate of the above channel is suitable for reading the above device API from the above library file and returning the baud rate of a specific channel to the above application program. The submodule for writing the baud rate of the above channel is suitable for calling the above device API from the above library file and writing the above baud rate provided to the APP to the device. The above connection submodule is suitable for establishing a connection between the above application and the above device by calling the above device API from the above library file. The above message sending submodule is suitable for calling the above device API from the above library file and writing the messages that need to be sent, which are given to the above APP, to the above device. The above message receiving submodule is suitable for calling the above device API from the above library file and returning the above messages read by the above device from all channels to the above application program. The above disconnection submodule is suitable for disconnecting the above device from the above application program by calling the above device API from the above library file.

[0009] Furthermore, the method by which the above application program obtains message information from the above device using the above library file module includes the following: The above application program obtains the above message information from the above device using the above library file module corresponding to the above manufacturer, that is, The functions of the submodule that reads the serial number, the submodule that reads the number of channels, the submodule that reads the channel type, the submodule that reads the baud rate of the channel, the submodule that writes the baud rate of the channel, the connection submodule, the message transmission submodule, and the message reception submodule are implemented in sequence to obtain the message information.

[0010] Furthermore, methods for disconnecting the connection with the above device after obtaining the above message information include the following: After obtaining the above message information, the above disconnection submodule will disconnect the connection between the application program and the above device.

[0011] In a third aspect, the present invention further provides a multi-adapter compatible calling system, which includes: This is a library file module, and it constructs the above-mentioned library file modules for each manufacturer. A module for acquiring message information, wherein the application program acquires the above message information from the device using the above library file module, and This is a disconnection submodule that disconnects the connection to the device after obtaining the above message information.

[0012] In a fourth aspect, the present invention further provides a multi-adapter compatible device, which includes: A control module, and a plurality of interface modules electrically connected to the control module. The above interface module is suitable for connecting to an adapter. The control module described above is suitable for receiving message information transmitted from the device via the adapter described above.

[0013] In a fifth aspect, the present invention further provides a multi - adapter compatible system, including the following: A multi - adapter compatible device and a host computer. The above - mentioned host computer is suitable for receiving message information transmitted from the above - mentioned multi - adapter compatible device and analyzing the message information.

[0014] The effects of the present invention are as follows. The present invention realizes the abstraction of the adapter in the upper - layer APP by constructing the library file module of each manufacturer, enabling the application program to obtain the message information of the device through the library file module, and disconnecting the connection of the device after obtaining the message information. The upper - layer APP derives a general API interface and creates a library file for the adapters of each manufacturer. By calling the API of the manufacturer adapter, the API interface of the upper - layer APP is realized. The APP does not need to know the details of any of the manufacturer adapters and can use the functions of the adapter only by loading the library file. It can support the adapters of all manufacturers in the market and, at the same time, support the adapters of any new manufacturer by increasing the library file, greatly improving the development efficiency of the application program.

[0015] Other features and advantages of the present invention are described in the following specification, and some are apparent from the specification or can be understood by implementing the present invention. The objectives and other advantages of the present invention are realized and achieved by the structure specifically pointed out in the specification and drawings.

[0016] To make the above - mentioned objectives, features, and advantages of the present invention clearer, the following provides preferred embodiments and will be described in detail in conjunction with the accompanying drawings.

Brief Description of the Drawings

[0017] To more clearly explain the specific embodiments of the present invention or the technical solutions in the prior art, the following briefly describes the drawings that need to be used in the description of the specific embodiments or the prior art. The drawings in the following description are some embodiments of the present invention, and it is obvious that those skilled in the art can obtain other drawings from these drawings without creative effort.

[0018] [Figure 1] Figure 1 is a flowchart of a calling method for multi - adapter compatibility according to the present invention. [Figure 2] Figure 2 is a schematic diagram of the principle of a calling method for multi - adapter compatibility according to the present invention. [Figure 3] Figure 3 is a block diagram of the principle of a calling system for multi - adapter compatibility according to the present invention.

Embodiments for Carrying out the Invention

[0019] To make the objectives, technical solutions and advantages of the embodiments of the present invention clearer, the following clearly and completely describes the technical solutions of the present invention in connection with the accompanying drawings. However, it is obvious that the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative labor fall within the protection scope of the present invention.

[0020] Example 1 This embodiment 1 provides a multi-adapter compatible library file module, which may include, but is not limited to, submodules for reading serial numbers, reading channel numbers, reading channel types, reading channel baud rates, writing channel baud rates, connection submodules, message transmission submodules, message reception submodules, and disconnection submodules. The library file module enables an API interface for higher-layer APPs (application programs) by calling the manufacturer adapter APIs. The APP does not need to know any details of the manufacturer adapters and can use the adapter functions simply by loading the library file. The APP does not require any modifications after development is complete and can support adapters from all manufacturers on the market, and can also support any new manufacturer's adapters by simultaneously adding library files, significantly improving the development efficiency of the application program. This reduces the workload and the possibility of errors.

[0021] In this embodiment, each time the APP loads a library file module, it invokes a series of specific callback functions (submodules of the corresponding functions) into that library file module. These callback functions are invoked in real time during APP execution. The type and number of callback functions depend on the functionality of the APP. The submodule functions and number in a library file module have different implementations for different manufacturers, and furthermore, the same manufacturer may have library file modules with the same functionality but different implementation methods by different developers. The submodule for reading the serial number is suitable for reading the device API from the library file and returning the device's serial number to the application program. The submodule for reading the number of channels is suitable for reading the device API from the library file and returning the physical number of channels of the device to the application program. The submodule for reading the channel type is suitable for reading the device API from the library file and returning the type of a specific channel of the device (such as a CAN channel, LIN channel, or Ethernet channel) to the application program. The submodule for reading the baud rate of a channel is suitable for reading the device API from the library file and returning the baud rate of a specific channel to the application program. The submodule for writing the baud rate of the above channel is suitable for calling the device API from the library file and writing the baud rate given to the APP to the device. The connection submodule is suitable for establishing a connection between the APP and the device by calling the device API from the library file. The message sending submodule is suitable for calling the device API from the library file and writing the message that needs to be sent given to the APP to the device. The message receiving submodule is suitable for calling the device API from the library file and returning the messages that the device has read from all channels to the application program.The above disconnection submodule is suitable for disconnecting a device from an application program by calling the device API from a library file.

[0022] Example 2 Figure 1 is a flowchart of the multi-adapter compatible calling method according to the present invention. As shown in Figure 1, building upon the foundation of Embodiment 1, Embodiment 2 further provides a multi-adapter compatible calling method, which includes constructing library file modules for each manufacturer, allowing the application program to obtain device message information via the library file modules, and disconnecting the device connection after obtaining the message information. The design process of the multi-adapter upper-layer software (the execution process of the multi-adapter compatible calling method) is hardware-independent, eliminating the need to know the existence of any particular manufacturer in advance during the design process. This allows for the development and completion of a software platform that is generally applicable to all adapters, and further enables manufacturers to independently complete device support. The upper-layer software architecture constructed with the multi-adapter compatible calling method has clear and flexible interfaces, allowing different types of automotive adapters to be called by loading library files (library file modules), and can also accommodate newly emerging automotive adapters. The entire process does not require modification of the APP, thereby expanding the connectivity capabilities of the APP as a software platform and unifying compatibility methods in the automotive adapter field.

[0023] In this embodiment, the library file module can be constructed using the library file module from Embodiment 1 to create a library file module corresponding to a manufacturer.

[0024] In this embodiment, the multi-adapter compatibility calling method is bottom-up, obtaining the characteristics of the device API, creating an interface program, which implements the interface functions required by the upper layer of the multi-adapter software, and finally loading and executing it in the multi-adapter software. The bottom-up method makes the upper-layer software hardware-independent, eliminating the need for modifications once development is complete, thereby realizing a software platform, and allowing new adapters produced by new manufacturers to always be added to the same software platform.

[0025] Figure 2 is a schematic diagram illustrating the principle of the multi-adapter compatible calling method according to the present invention. In this embodiment, the method for constructing the library file modules for each of the above manufacturers is as follows. The library file module may include, but is not limited to, a submodule for reading the serial number, a submodule for reading the number of channels, a submodule for reading the channel type, a submodule for reading the channel baud rate, a submodule for writing the channel baud rate, a connection submodule, a message transmission submodule, a message reception submodule, and a disconnection submodule. The submodule for reading the serial number is suitable for reading the device API from the library file and returning the device's serial number to the application program. The submodule for reading the number of channels is suitable for reading the device API from the library file and returning the number of physical channels of the device to the application program. The submodule for reading the channel type is suitable for reading the device API from the library file and returning the type of a specific channel of the device to the application program. The submodule for reading the channel baud rate is suitable for reading the device API from the library file and returning the baud rate of a specific channel to the application program. The submodule for writing the channel baud rate is suitable for calling the device API from the library file and writing the baud rate given to the APP to the device. The above connection submodule is suitable for establishing a connection between the app and the device by calling the device API from a library file. The above message sending submodule is suitable for calling the device API from a library file and writing the message that needs to be sent, provided by the app, to the device. The above message receiving submodule is suitable for calling the device API from a library file and returning the messages that the device has read from all channels to the application program. The above disconnection submodule is suitable for disconnecting the device from the application program by calling the device API from a library file.As shown in Figure 2, taking library file A as an example, its contents include submodules corresponding to various API calling algorithms of manufacturer A on the left and submodules corresponding to the callback function of the APP on the right, realizing the two main components and serving as the API interface between the external manufacturer's device and the APP.

[0026] As shown in Figure 2, in this embodiment, the application program obtains the device's message information using the library file module as follows: The application program obtains the device's message information using the library file module corresponding to the manufacturer, that is, it sequentially implements the functions of a submodule that reads the serial number, a submodule that reads the number of channels, a submodule that reads the channel type, a submodule that reads the channel's baud rate, a submodule that writes the channel's baud rate, a connection submodule, a message transmission submodule, and a message reception submodule, and obtains the message information.

[0027] In this embodiment, the method for disconnecting the device after obtaining the above message information includes the following: After obtaining the message information, the disconnection submodule is used to disconnect the connection between the application program and the device.

[0028] Example 3 Figure 3 is a principle block diagram of the multi-adapter compatible calling system according to the present invention. As shown in Figure 3, in addition to Example 2, Example 3 further provides a multi-adapter compatible calling system, which includes: It is a library file module, and it builds library file modules for each manufacturer. A module for acquiring message information, wherein the application program acquires the device's message information through a library file module, and This is a disconnection submodule that disconnects the device connection after obtaining message information.

[0029] Example 4 In addition to Example 3, Example 4 further provides a multi-adapter compatible device, which includes: A control module, and a plurality of interface modules electrically connected to the control module. The above interface module is suitable for connecting to an adapter. The control module described above is suitable for receiving message information sent from a device via an adapter. In this embodiment, the control module can integrate the functions of each module in the multi-adapter compatible calling system, and it can call various types of API calling algorithms and callback function functions of the corresponding manufacturers based on the APP.

[0030] Example 5 In addition to Embodiment 4, Embodiment 5 further provides a multi-adapter compatible system, which includes a multi-adapter compatible device and a host machine. The host machine is suitable for receiving message information transmitted from the multi-adapter compatible device and for analyzing the message information.

[0031] In this embodiment, the multi-adapter compatible device can be the multi-adapter compatible device described in Embodiment 4, and the host device can acquire message information transmitted from the device via the multi-adapter compatible device based on the functions and needs of the APP, and perform analysis processing on the message.

[0032] In summary, the present invention achieves adapter abstraction in a higher-layer application by constructing library file modules for each manufacturer, allowing the application program to obtain device message information through the library file modules, and disconnecting the device connection after obtaining the message information. The higher-layer application derives a general-purpose API interface and creates library files for each manufacturer's adapter. The API interface of the higher-layer application is realized by calling the manufacturer adapter's API. The application does not need to know the details of any of the manufacturer adapters and can use the adapter's functions simply by loading the library file. Not only can it support adapters from all manufacturers on the market, but it can also support any new manufacturer's adapter by simultaneously adding library files, significantly improving the development efficiency of the application program.

[0033] In some embodiments provided by this application, the disclosed devices and methods can, of course, be implemented in other ways. The embodiments of the devices described above are merely illustrative; for example, the flowcharts and block diagrams in the drawings illustrate the implementable architectures, functions, and operations of the devices, methods, and computer program products according to some embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, program segment, or part of code containing one or more executable instructions for performing a given logical function. In some alternative implementations, the functions represented in the blocks may occur in an order different from that shown in the drawings. For example, two consecutive blocks can actually be executed substantially in parallel, and sometimes in reverse order depending on the related functions. It should also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in a block diagram and / or flowchart, may be implemented in a dedicated hardware-based system that performs a given function or operation, or in a combination of dedicated hardware and computer instructions.

[0034] Furthermore, in each embodiment of the present invention, each functional module may be integrated to form a single independent part, each module may exist individually, or two or more modules may be integrated to form a single independent part.

[0035] The above functions can be implemented in the form of a software function module and, when sold or used as an independent product, can be stored on a computer-readable storage medium. Based on this understanding, the technical solutions of the present invention, in their essence or in parts that contribute to the prior art, or parts of such technical solutions, can be represented in the form of a software product. The computer software product is stored on a storage medium and contains a plurality of commands that cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present invention. The storage medium includes: various media capable of storing program code, such as U disks, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0036] Using the ideal embodiment of the present invention described above as a hint, those concerned can make a variety of changes and modifications within the scope of the technical concept of the present invention, as described above. The technical scope of the present invention is not limited to the contents of the specification, and its technical scope must be determined based on the claims.

Claims

1. A library file module for multi-adapter compatibility, A multi-adapter compatible library file module characterized by including a submodule for reading the serial number, a submodule for reading the number of channels, a submodule for reading the channel type, a submodule for reading the channel baud rate, a submodule for writing the channel baud rate, a connection submodule, a message transmission submodule, and a message reception submodule.

2. The aforementioned submodule for reading the serial number is suitable for reading the device API from a library file and returning the device's serial number to the application program. The submodule for reading the number of channels is suitable for reading the device API from the library file and returning the physical number of channels of the device to the application program. The submodule for reading the channel type is suitable for reading the device API from the library file and returning the type of a specific channel for the device to the application program. The submodule for reading the baud rate of the channel is suitable for reading the device API from the library file and returning the baud rate of a specific channel to the application program. The submodule for writing the channel baud rate is suitable for calling the device API from the library file and writing the baud rate provided by the APP to the device. The aforementioned connection submodule is suitable for realizing a connection between the APP and the device by calling the device API from the library file. The message sending submodule is suitable for calling the device API from the library file and writing the message to be sent, provided by the APP, to the device. The multi-adapter compatible library file module according to claim 1, characterized in that the message receiving submodule is suitable for calling the device API from the library file and returning the messages read by the device from all channels to the application program.

3. A calling method for multi-adapter compatibility, The application program obtains device message information through a library file module, This includes, after obtaining the message information, disconnecting the connection with the device. A multi-adapter compatible calling method characterized in that the library file module includes a submodule for reading a serial number, a submodule for reading the number of channels, a submodule for reading the channel type, a submodule for reading the channel baud rate, a submodule for writing the channel baud rate, a connection submodule, a message transmission submodule, and a message reception submodule.

4. The application program obtains the device's message information through the library file module, The application program includes obtaining device message information through a manufacturer-specific library file module, i.e., The multi-adapter compatible calling method according to claim 3, characterized in that it achieves the acquisition of message information by utilizing the functions of the submodule that reads the serial number, the submodule that reads the number of channels, the submodule that reads the channel type, the submodule that reads the baud rate of the channel, the submodule that writes the baud rate of the channel, the connection submodule, the message transmission submodule, and the message reception submodule.

5. The aforementioned library file module further includes a disconnection submodule, Disconnecting from the device after retrieving message information is possible. The multi-adapter compatible calling method according to claim 3 or 4, characterized in that, after obtaining message information, the disconnection submodule enables the disconnection of the connection between the application program and the device.

6. The aforementioned submodule for reading the serial number is suitable for reading the device API from a library file and returning the device's serial number to the application program. The submodule for reading the number of channels is suitable for reading the device API from the library file and returning the physical number of channels of the device to the application program. The submodule for reading the channel type is suitable for reading the device API from the library file and returning the type of a specific channel for the device to the application program. The submodule for reading the baud rate of the channel is suitable for reading the device API from the library file and returning the baud rate of a specific channel to the application program. The submodule for writing the channel baud rate is suitable for calling the device API from the library file and writing the baud rate provided by the APP to the device. The aforementioned connection submodule is suitable for realizing a connection between the APP and the device by calling the device API from the library file. The message sending submodule is suitable for calling the device API from the library file and writing the message to be sent, provided by the APP, to the device. The message receiving submodule is suitable for calling the device API from the library file and returning the messages read by the device from all channels to the application program. The multi-adapter compatible calling method according to claim 5, characterized in that the disconnection submodule is suitable for disconnecting the connection between the application program and the device by calling the device API from the library file.

7. A multi-adapter compatible device including a control module and a plurality of interface modules electrically connected to the control module, The control module integrates the functions of each module in the multi-adapter compatible calling system and is configured to call various types of API calling algorithms and callback function functions of the corresponding manufacturers based on the APP. The control module includes a submodule for reading the serial number, a submodule for reading the number of channels, a submodule for reading the channel type, a submodule for reading the channel baud rate, a submodule for writing the channel baud rate, a connection submodule, a message transmission submodule, a message reception submodule, and a disconnection submodule. The interface module is suitable for connecting to an adapter. The control module is a multi-adapter compatible device characterized by being suitable for receiving message information transmitted from a device via the adapter using the functions of a submodule for reading serial numbers, a submodule for reading the number of channels, a submodule for reading the channel type, a submodule for reading the channel baud rate, a submodule for writing the channel baud rate, a connection submodule, a message transmission submodule, and a message reception submodule.

8. The aforementioned submodule for reading the serial number is suitable for reading the device API from a library file and returning the device's serial number to the application program. The submodule for reading the number of channels is suitable for reading the device API from the library file and returning the physical number of channels of the device to the application program. The submodule for reading the channel type is suitable for reading the device API from the library file and returning the type of a specific channel for the device to the application program. The submodule for reading the baud rate of the channel is suitable for reading the device API from the library file and returning the baud rate of a specific channel to the application program. The submodule for writing the channel baud rate is suitable for calling the device API from the library file and writing the baud rate provided by the APP to the device. The aforementioned connection submodule is suitable for realizing a connection between the APP and the device by calling the device API from the library file. The message sending submodule is suitable for calling the device API from the library file and writing the message to be sent, provided by the APP, to the device. The message receiving submodule is suitable for calling the device API from the library file and returning the messages read by the device from all channels to the application program. The multi-adapter compatible device according to claim 7, characterized in that the disconnection submodule is suitable for disconnecting the connection between the application program and the device by calling the device API from the library file.

9. It is a multi-adapter compatible system, Includes the multi-adapter compatible device and host machine described in claim 7 or 8, The aforementioned higher-level device is a multi-adapter compatible system characterized by being suitable for receiving message information transmitted from the multi-adapter compatible device and for analyzing the message information.

10. A computer device comprising memory, a processor, and a computer program stored in the memory, wherein the processor executes the multi-adapter compatible calling method described in claim 3 by executing the computer program.

11. A computer-readable storage medium in which a computer program is stored, characterized in that when the computer program is executed by a processor, the multi-adapter compatible calling method of claim 3 is executed.

12. A computer-readable storage medium containing a computer program compatible with a multi-adapter compatible library file module, The multi-adapter compatible library file module is a computer-readable storage medium characterized by including a submodule for reading the serial number, a submodule for reading the number of channels, a submodule for reading the channel type, a submodule for reading the channel baud rate, a submodule for writing the channel baud rate, a connection submodule, a message transmission submodule, a message reception submodule, and a disconnection submodule.

13. The aforementioned submodule for reading the serial number is suitable for reading the device API from a library file and returning the device's serial number to the application program. The submodule for reading the number of channels is suitable for reading the device API from the library file and returning the physical number of channels of the device to the application program. The submodule for reading the channel type is suitable for reading the device API from the library file and returning the type of a specific channel for the device to the application program. The submodule for reading the baud rate of the channel is suitable for reading the device API from the library file and returning the baud rate of a specific channel to the application program. The submodule for writing the channel baud rate is suitable for calling the device API from the library file and writing the baud rate provided by the APP to the device. The aforementioned connection submodule is suitable for realizing a connection between the APP and the device by calling the device API from the library file. The message sending submodule is suitable for calling the device API from the library file and writing the message to be sent, provided by the APP, to the device. The message receiving submodule is suitable for calling the device API from the library file and returning the messages read by the device from all channels to the application program. The computer-readable storage medium according to claim 12, characterized in that the disconnection submodule is suitable for disconnecting the connection between the application program and the device by calling the device API from the library file.

14. A computer program product in which a computer program is stored, characterized in that when the computer program is executed by a processor, the multi-adapter compatible calling method described in claim 3 is executed.

Images