IO control system based on AUTBUS

Abstract

The invention discloses an IO control system based on an AUTBUS, and belongs to the technical field of computers. The system comprises a controller, an AUTBUS bus, at least one low-speed communication node and at least one high-speed IO module, the controller, each low-speed communication node and each high-speed IO module are connected with the AUTBUS bus; data is transmitted between the low-speed communication node and the controller through an AUTBUS bus; and data is transmitted between the high-speed IO module and the controller through an AUTBUS bus. According to the IO control system based on the AUTBUS, under the condition that the low-speed communication node and the high-speed IO module with different communication rates can be flexibly connected to any position of the AUTBUS, the low-speed communication node and the high-speed IO module transmit data to the controller through the AUTBUS.

Description

Technical Field

[0001] The present application belongs to the field of computer technology, and in particular to an IO control system based on an AUTBUS bus. Background Art

[0002] In industrial control scenarios, in large PLC systems or measurement and control devices, serial buses are generally used to exchange data between central processing modules and IO modules. Common serial buses are divided into two types based on communication rates: one is a low-speed bus with a communication rate below 20Mbps, such as 485, 422, CAN, profibus, etc., and the other is a high-speed bus with a communication rate above 20Mbps, such as ethercat, profinet, etc.

[0003] In actual scenarios, in order to comprehensively consider the needs and costs, when the control system needs to be compatible with the high-speed bus and the low-speed bus, a coupler is usually added to the end of the high-speed bus, and then the low-speed bus is connected through the coupler. This method makes it impossible to flexibly set the position of the low-speed bus in the scenario of compatibility between the high-speed bus and the low-speed bus. Summary of the invention

[0004] The present application aims to solve at least one of the technical problems existing in the prior art. To this end, the present application proposes an IO control system based on the AUTBUS bus, which can realize that low-speed communication nodes and high-speed IO modules with different communication rates can be flexibly connected to any position of the AUTBUS bus, and both the low-speed communication nodes and the high-speed IO modules transmit data with the controller through the AUTBUS bus.

[0005] In a first aspect, the present application provides an IO control system based on an AUTBUS bus, the system comprising:

[0006] A controller, an AUTBUS bus, at least one low-speed communication node and at least one high-speed IO module;

[0007] The controller, each low-speed communication node and each high-speed IO module are connected to the AUTBUS bus;

[0008] Data is transmitted between the low-speed communication node and the controller via the AUTBUS bus;

[0009] Data is transmitted between the high-speed IO module and the controller via the AUTBUS bus.

[0010] According to the AUTBUS bus-based IO control system of the present application, by connecting both the low-speed communication nodes and the high-speed IO modules to the AUTBUS bus, it is possible to flexibly connect the low-speed communication nodes and the high-speed IO modules with different communication rates to any position of the AUTBUS bus, and both the low-speed communication nodes and the high-speed IO modules transmit data with the controller through the AUTBUS bus.

[0011] According to one embodiment of the present application, the low-speed communication node is a low-speed IO module.

[0012] According to one embodiment of the present application, the low-speed communication node is an AUTBUS coupler, and the IO control system based on the AUTBUS bus also includes multiple low-speed IO modules; the AUTBUS coupler is connected to the multiple low-speed IO modules via a low-speed bus.

[0013] According to one embodiment of the present application, the AUTBUS coupler is used to parse out the target low-speed IO module according to the target board address carried by the protocol data unit of the AUTBUS request message after receiving the AUTBUS request message sent by the controller, encapsulate the function code and the target board address into a low-speed bus message and send it to the target low-speed IO module, and the target low-speed IO module executes the request command of the controller according to the function code; the function code is carried by the protocol data unit; the AUTBUS request message carries the device ID of the AUTBUS coupler.

[0014] According to one embodiment of the present application, the AUTBUS coupler is used to receive field data collected by the low-speed IO module from the low-speed bus, and encapsulate the field data, the target board address and the device ID of the AUTBUS coupler into an AUTBUS response message and send it to the controller.

[0015] According to one embodiment of the present application, the AUTBUS coupler is used to assign a corresponding board address to each low-speed IO module and report it to the controller.

[0016] According to one embodiment of the present application, the AUTBUS coupler periodically polls the low-speed IO module and receives field data collected by the low-speed IO module from the low-speed bus.

[0017] According to one embodiment of the present application, the controller allocates communication resources to the high-speed IO module, the low-speed IO module and the AUTBUS coupler connected to the AUTBUS bus.

[0018] According to one embodiment of the present application, the IO control system based on the AUTBUS bus also includes a non-AUTBUS bus power supply device and an AUTBUS bus power supply device.

[0019] According to one embodiment of the present application, the AUTBUS bus is a ring bus.

[0020] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0022] Figure 1 It is a structural diagram of an IO control system based on AUTBUS bus provided in an embodiment of the present application;

[0023] Figure 2 It is a structural schematic diagram of a controller in an IO control system based on an AUTBUS bus provided in an embodiment of the present application;

[0024] Figure 3 It is a structural diagram of another AUTBUS bus-based IO control system provided in an embodiment of the present application;

[0025] Figure 4A This is a schematic diagram of a linear networking structure of an IO control system based on an AUTBUS bus provided in an embodiment of the present application;

[0026] Figure 4B This is another linear networking structure diagram of an IO control system based on an AUTBUS bus provided in an embodiment of the present application;

[0027] Figure 5A This is a schematic diagram of a ring network of an IO control system based on an AUTBUS bus provided in an embodiment of the present application;

[0028] Figure 5B This is another AUTBUS bus-based IO control system ring networking schematic diagram provided in an embodiment of the present application;

[0029] Figure 6 It is a flow chart of an IO data interaction method based on AUTBUS bus provided in an embodiment of the present application;

[0030] Figure 7 This is a schematic diagram of an application example structure of an AUTBUS bus-based IO control system provided in an embodiment of the present application;

[0031] Figure 8 It is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0032] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments in the present application belong to the scope of protection of this application.

[0033] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0034] The following is a detailed description of the AUTBUS bus-based IO control system, electronic device and readable storage medium provided in the embodiments of the present application through specific embodiments and their application scenarios in conjunction with the accompanying drawings.

[0035] The terminal includes, but is not limited to, a portable communication device such as a mobile phone or tablet computer having a touch-sensitive surface (e.g., a touch screen display and / or a touch pad). It should also be understood that in some embodiments, the terminal may not be a portable communication device, but a desktop computer having a touch-sensitive surface (e.g., a touch screen display and / or a touch pad).

[0036] In the following various embodiments, a terminal including a display and a touch-sensitive surface is described. However, it should be understood that the terminal may include one or more other physical user interface devices such as a physical keyboard, a mouse and a joystick.

[0037] like Figure 1 As shown, the IO control system based on the AUTBUS bus includes: a controller 110, an AUTBUS bus 120, at least one low-speed communication node 13i (i is a positive integer) and at least one high-speed IO module 14h (h is a positive integer); the controller 110, each low-speed communication node 13i and each high-speed IO module 14h are connected to the AUTBUS bus 120; data is transmitted between the low-speed communication node 13i and the controller 110 through the AUTBUS bus 120; data is transmitted between the high-speed IO module 14h and the controller 110 through the AUTBUS bus 120.

[0038] In actual implementation, the controller may include a programmable logic controller, which may be an industrial control PLC; the controller may use a high-performance CPU and provide a bus interface for the AUTBUS bus. Figure 2 As shown, the high-performance CPU (e.g., 2K1000) in the controller communicates with the Ethernet controller (e.g., WX1860) through PCIE. When the Ethernet controller includes two electrical ports, it is connected to the PHY (e.g., KD3002) through the MDI interface, and the PHY communicates with the KY3001 through the RGMII interface, thereby realizing that the bus interface is connected to the AUTBUS bus and communicates externally through the AUTBUS bus. The controller can determine the target bandwidth of the low-speed communication node and the high-speed IO module.

[0039] In actual implementation, the low-speed communication node may include a low-speed bus (such as 485, 422, CAN, profibus and other buses with communication rates below 20Mbps), and the high-speed IO module may include a high-speed bus (such as ethercat, profinet and other buses with communication rates above 20Mbps).

[0040] In actual implementation, the AUTBUS bus can adopt an orthogonal frequency division multiplexing communication mechanism, and each low-speed communication node obtains the data transmitted by the controller from the AUTBUS bus at a rate belonging to the first preset range, and the first preset range can be 20Mbps to 100Mbps. Each high-speed IO module obtains the data transmitted by the controller from the AUTBUS bus at a rate belonging to the second preset range, and the minimum value of the second preset range is greater than the maximum value of the first preset range. For example, the second preset range can be 1Mbps to 20Mbps. The rate at which the high-speed IO module obtains the data transmitted by the controller through the AUTBUS bus is lower than the rate at which the low-speed communication node obtains the data transmitted by the controller through the AUTBUS bus.

[0041] In some embodiments, the controller can act as a master station, and the low-speed communication nodes and high-speed IO modules can act as slave stations. The controller can acquire data transmitted by slave stations such as low-speed communication nodes and high-speed IO modules through the AUTBUS bus in the role of the master station.

[0042] In actual implementation, at least one low-speed communication node is connected to a position on the AUTBUS bus that is farther away than the distance between the controller and at least one high-speed IO module, so that at least one low-speed communication node with a transmission rate lower than that of the high-speed IO module is connected to a position farther away than the high-speed IO module.

[0043] In actual implementation, the position at which at least one high-speed IO module is connected to the AUTBUS bus is greater than the first target preset distance and less than or equal to the second target preset distance.

[0044] In some embodiments, the low-speed communication node can be an AUTBUS coupler and / or a first-class device, and the AUTBUS coupler can be a BK1250 coupler or any theoretically feasible coupler, which is not specifically limited in this application. The first-class device can be a low-speed IO module, and the low-speed IO module can include a low-speed IO bus. The low-speed IO module can forward data transmitted between the low-speed communication node and the controller via the AUTBUS bus based on a data transmission rate belonging to a first preset range.

[0045] In some embodiments, the controller can be used as a primary master station, and the high-speed IO module and the AUTBUS coupler connected to the low-speed bus can be used as primary slave stations. At the same time, the AUTBUS coupler can be used as a secondary master station, and multiple low-speed IO modules connected to the low-speed bus can be used as secondary slave stations. The AUTBUS coupler can play the role of a secondary master station, obtain the data transmitted by the low-speed IO module as a secondary slave station through the low-speed bus, and then the AUTBUS coupler, as a primary slave station, transmits the data to the controller as a primary master station through the AUTBUS bus.

[0046] In some embodiments, the AUTBUS bus may form a ring structure with the controller.

[0047] In actual implementation, the IO control system based on the AUTBUS bus can adopt a topological structure, and the controller, AUTBUS bus, low-speed communication node, high-speed IO module, AUTBUS coupler, low-speed IO module, second-class device and target data bus can be connected through a connector, and the connector can be a 2*10pin European connector with a durable structure and support blind insertion. The programmable logic controller, AUTBUS bus, low-speed communication node, high-speed IO module, AUTBUS coupler, low-speed IO module and low-speed bus can be directly fixed on the rack by screws, or installed on the rack by the back gauge.

[0048] In some embodiments, the controller may adopt a target communication protocol to perform data transmission with a low-speed communication node and a high-speed IO module via an AUTBUS bus, and the target communication protocol may be an AUTBUS PA protocol.

[0049] According to the AUTBUS bus-based IO control system of the present application, by connecting both the low-speed communication nodes and the high-speed IO modules to the AUTBUS bus, it is possible to flexibly connect the low-speed communication nodes and the high-speed IO modules with different communication rates to any position of the AUTBUS bus, and both the low-speed communication nodes and the high-speed IO modules transmit data with the controller through the AUTBUS bus.

[0050] In some embodiments, Figure 3 As shown, in an IO control system based on the AUTBUS bus, the distance between at least one low-speed communication node 33i (i is a positive integer) and the controller 310 is greater than the distance between at least one high-speed IO module 34h (h is a positive integer) and the controller 310.

[0051] In actual execution, among all the low-speed communication nodes included in the IO control system based on the AUTBUS bus, the distance between at least one low-speed communication node and the controller is greater than the distance between at least one high-speed IO module and the controller. In some embodiments, the IO control system based on the AUTBUS bus includes two low-speed communication nodes, namely, a low-speed communication node 331 and a low-speed communication node 332, and the IO control system based on the AUTBUS bus also includes a high-speed IO module 341 and a high-speed IO module 342, and the distance between at least one of the low-speed communication node 331 and the low-speed communication node 332 and the controller 310 is greater than the distance between at least one of the high-speed IO module 341 and the high-speed IO module 342 and the controller 310. For example, the distance between the low-speed communication node 332 and the controller 310 is greater than the distance between the high-speed IO module 341 and the controller 310. For another example, the distance between the low-speed communication node 332 and the controller 310 is greater than the distance between the high-speed IO module 341 and the controller 310, and the distance between the low-speed communication node 331 and the controller 310 is greater than the distance between the high-speed IO module 342 and the controller 310.

[0052] According to the AUTBUS bus-based IO control system of the embodiment of the present application, by making the distance between at least one low-speed communication node and the controller greater than the distance between at least one high-speed IO module and the controller, it is possible to achieve that low-speed communication nodes and high-speed IO modules with different communication rates can be flexibly connected to any position of the AUTBUS bus.

[0053] In some embodiments, the distance between at least one high-speed IO module and the controller is greater than 100 meters.

[0054] In actual implementation, the high-speed IO module can be connected to the AUTBUS bus, and the AUTBUS bus adopts an orthogonal frequency division multiplexing communication mechanism, so that at least one high-speed IO module can be connected to the AUTBUS bus at a position greater than 100 meters away from the controller, and obtains data transmitted by the controller from the AUTBUS bus at a rate within the second preset range. For example, the high-speed IO module is connected to the AUTBUS bus at a position 200 meters away from the controller.

[0055] According to the AUTBUS bus-based IO control system of the embodiment of the present application, by connecting at least one high-speed IO module to a position on the AUTBUS bus that is more than 100 meters away from the controller, the controller can communicate with the high-speed IO module that is more than 100 meters away through the AUTBUS bus.

[0056] In some embodiments, the low-speed communication node is an AUTBUS coupler and / or a low-speed IO module.

[0057] In actual implementation, when the low-speed communication node is an AUTBUS coupler, the AUTBUS coupler may include an AUTBUS bus chip, and the AUTBUS bus chip realizes the connection between the AUTBUS bus and the AUTBUS coupler.

[0058] In some embodiments, Figure 4A As shown, the low-speed communication node may be a low-speed IO module 431 , which forwards data transmitted between the low-speed communication node and the controller 410 via the AUTBUS bus 420 .

[0059] In some embodiments, Figure 4A As shown, the low-speed communication node 432 can also be composed of an AUTBUS coupler and a low-speed IO module, and the AUTBUS coupler and the low-speed IO module are connected via a low-speed bus. The AUTBUS coupler can be a BK1250 coupler or any theoretically feasible coupler, and this application does not make specific limitations on this.

[0060] like Figure 4B As shown, the controller, H_IO (high-speed IO module), L_IO_A module (low-speed IO module) and AUTBUS coupler are all equipped with AUTBUS bus chip KY3001, which are connected through AUTBUS bus to form a linear network. The AUTBUS coupler connects multiple L_IO_B modules (low-speed IO modules) through the 422 bus.

[0061] According to the AUTBUS bus-based IO control system of the embodiment of the present application, the low-speed communication node is an AUTBUS coupler and / or a low-speed IO module, so that the AUTBUS coupler and the low-speed IO module can be flexibly set at any position of the AUTBUS bus.

[0062] In some embodiments, when the low-speed communication node is an AUTBUS coupler, the IO control system based on the AUTBUS bus also includes multiple low-speed IO modules, and each AUTBUS coupler is connected to multiple low-speed IO modules through a low-speed bus; for each AUTBUS coupler, the data transmission between the low-speed IO module connected to the AUTBUS coupler and the controller is relayed through the AUTBUS coupler.

[0063] In actual implementation, when the low-speed communication node is an AUTBUS coupler, the IO control system based on the AUTBUS bus may also include multiple low-speed IO modules. The AUTBUS coupler is connected to multiple low-speed IO modules via a low-speed bus, and the low-speed IO module may transmit communication data to the AUTBUS coupler via the low-speed bus, and the low-speed bus may be a 422 or 485 bus communication.

[0064] In actual implementation, when the low-speed communication node is an AUTBUS coupler, the distance between the AUTBUS coupler and the AUTBUS controller is greater than the distance between at least one high-speed IO module and the controller.

[0065] According to the AUTBUS bus-based IO control system of the embodiment of the present application, when the low-speed communication node is an AUTBUS coupler, the AUTBUS bus-based IO control system also includes multiple low-speed IO modules; each AUTBUS coupler is connected to the multiple low-speed IO modules through a low-speed bus, so that the AUTBUS bus-based IO control system can expand multiple communication nodes through the AUTBUS coupler.

[0066] In some embodiments, after receiving the AUTBUS request message sent by the controller, the AUTBUS coupler can parse out the target low-speed IO module according to the board address carried by the protocol data unit of the AUTBUS request message, encapsulate the function code and the board address into a low-speed bus message and send it to the target low-speed IO module. The target low-speed IO module executes the request command of the controller according to the function code; the function code is carried by the protocol data unit; the AUTBUS request message carries the device ID of the AUTBUS coupler.

[0067] In actual execution, the controller may send an AUTBUS request message through the AUTBUS bus to request the low-speed communication node and / or high-speed IO module to perform communication data transmission for the AUTBUS request message. The AUTBUS request message may include the address of the low-speed communication node and / or high-speed IO module receiving the AUTBUS request message and service data, etc.

[0068] In actual execution, the function code can be used to represent the request instruction of the controller, such as obtaining temperature data, obtaining humidity data, executing download operations, etc.

[0069] In some embodiments, during the process of the controller sending an AUTBUS request message to a target low-speed IO module among multiple low-speed IO modules, the controller sends the AUTBUS request message to the AUTBUS bus. After receiving the AUTBUS request message sent by the controller, the AUTBUS coupler parses the target low-speed IO module (the receiving object of the AUTBUS request message) according to the target board address carried by the protocol data unit of the AUTBUS request message. The AUTBUS coupler encapsulates the function code and the target board address into a low-speed bus message, and sends it to the target low-speed IO module based on the target board address. The target low-speed IO module executes the request command of the controller according to the function code.

[0070] In some embodiments, when the low-speed communication node is an AUTBUS coupler and multiple low-speed IO modules, and the multiple low-speed IO modules are connected to the AUTBUS coupler through a low-speed bus, the controller can send an AUTBUS request message to a target low-speed IO module among the multiple low-speed IO modules based on the target board address of the target low-speed IO module. The AUTBUS request message can include the device ID and protocol data unit of the AUTBUS coupler, and the protocol data unit can include the target board address and function code of the target low-speed IO module. After the controller sends the AUTBUS request message to the AUTBUS bus, the AUTBUS coupler obtains the AUTBUS request message based on the device ID of the AUTBUS coupler and parses the AUTBUS request message to obtain the target board address of the target low-speed IO module. The AUTBUS coupler encapsulates the function code and the target board address into a low-speed bus message based on the target board address of the target low-speed IO module, and sends the low-speed bus message to the target low-speed IO module based on the low-speed protocol.

[0071] In some embodiments, when the low-speed communication node is an AUTBUS coupler, the AUTBUS coupler can be used to receive field data collected by the low-speed IO module from the low-speed bus, and encapsulate the field data, the target board address and the device ID of the AUTBUS coupler into an AUTBUS response message and send it to the controller.

[0072] In some embodiments, after the target low-speed IO module sends the collected field data and the target board address of the target low-speed IO module to the AUTBUS coupler through the low-speed bus, the AUTBUS coupler encapsulates the field data, the target board address and the device ID of the AUTBUS coupler into an AUTBUS response message, and sends the AUTBUS response message including the field data, the target board address and the device ID of the AUTBUS coupler to the controller through the AUTBUS bus.

[0073] In some embodiments, the controller and the AUTBUS coupler may transmit AUTBUS request messages and AUTBUS response messages via the AUTBUS protocol. The structure of the AUTBUS protocol may be as follows:

[0074] Table 1 is the AUTBUS request message

[0075]

[0076] Table 2 is the protocol data unit in Table 1

[0077]

[0078] Table 3 is the AUTBUS response message

[0079]

[0080] Table 4 is the response protocol data unit in Table 3

[0081]

[0082] In some embodiments, the AUTBUS coupler may assign a corresponding board address to each low-speed IO module.

[0083] In actual implementation, the AUTBUS coupler can obtain the type of each low-speed IO module connected to the low-speed bus through the low-speed bus, and assign a corresponding board address to each low-speed IO module. The AUTBUS coupler can also send the board address assigned to each low-speed IO module to the controller through the AUTBUS bus.

[0084] In some embodiments, the AUTBUS coupler may periodically poll the low-speed IO module and receive field data collected by the low-speed IO module from the low-speed bus.

[0085] In actual implementation, the AUTBUS coupler can perform board address allocation and field data reception with each of the multiple low-speed IO modules based on the low-speed protocol. The structure of the low-speed IO protocol used by the AUTBUS coupler is shown in the following tables:

[0086] Table 5 shows the low-speed IO protocol structure used by the AUTBUS coupler

[0087]

[0088] Table 6 shows the meaning of the board address in Table 5

[0089]

[0090] Table 7 Target node type

[0091]

[0092]

[0093] Table 8 is the function code in Table 5

[0094]

[0095]

[0096] In some embodiments, the controller may allocate communication resources to the high-speed IO module, the low-speed IO module, and the AUTBUS coupler connected to the AUTBUS bus.

[0097] In actual execution, the controller can obtain communication resources corresponding to the high-speed IO module, low-speed IO module and AUTBUS coupler connected to the AUTBUS bus, such as the target bandwidth, by communicating with the user terminal. The user terminal can be a visual electronic device. The communication resources obtained by the controller through communication with the user terminal can be input by the target user.

[0098] In some embodiments, the AUTBUS bus-based IO control system further includes non-AUTBUS bus-powered devices and AUTBUS bus-powered devices.

[0099] In some embodiments, the AUTBUS bus may be a ring bus. Figure 5AAs shown, the AUTBUS bus 520 is a ring data bus, and the low-speed communication node 531, the low-speed communication node 532, the low-speed communication node 533 and the high-speed IO module 541 are connected to the AUTBUS bus 520. The AUTBUS bus 520 adopts an orthogonal frequency division multiplexing communication mechanism; the low-speed communication node 531, the low-speed communication node 532, and the low-speed communication node 533 obtain the data transmitted from the controller 510 to the AUTBUS bus 520 at a rate belonging to the first preset range from the AUTBUS bus 520; the high-speed IO module 541 obtains the data transmitted from the controller 510 to the AUTBUS bus 520 from the AUTBUS bus 520 at a rate belonging to the second preset range; the minimum value of the second preset range is greater than the maximum value of the first preset range. The distance between the low-speed communication node 332, the low-speed communication node 533 and the controller 510 is greater than the distance between the high-speed IO module 541 and the controller 510. The distance between the high-speed IO module 541 and the controller 510 is greater than 100 meters. The low-speed communication node 533 may include an AUTBUS coupler and a low-speed IO module. The AUTBUS coupler and the low-speed IO module may be connected via a low-speed bus.

[0100] like Figure 5B As shown, the controller, H_IO (high-speed IO module), L_IO_A module (low-speed IO module) and AUTBUS coupler are all equipped with AUTBUS bus chip KY3001, which are connected through AUTBUS bus to form a ring network. The AUTBUS coupler connects multiple L_IO_B modules (low-speed IO modules) through the 422 bus.

[0101] The embodiment of the present application also provides a data interaction method. The execution subject of the data interaction method can be an electronic device or a functional module or functional entity in the electronic device that can implement the data interaction method. The electronic devices mentioned in the embodiment of the present application include but are not limited to mobile phones, tablet computers, computers, cameras and wearable devices, etc. The data interaction method provided in the embodiment of the present application is explained below using the electronic device as an example of the execution subject.

[0102] like Figure 6 As shown, the IO data interaction method based on the AUTBUS bus includes step 610, step 620 and step 630.

[0103] Step 610: The controller sends an AUTBUS request message to the AUTBUS coupler via the AUTBUS bus. The AUTBUS request message includes a protocol data unit and a device ID of the AUTBUS coupler. The protocol data unit includes a target board address of a target low-speed IO module.

[0104] In actual implementation, the data interaction method can be applied to the above-mentioned AUTBUS bus-based IO control system. The AUTBUS bus-based IO control system may include a controller, an AUTBUS bus, an AUTBUS coupler and a low-speed IO module; the controller may be a programmable logic controller, and the programmable logic controller may be an industrial control PLC; the controller and the target node are connected to the AUTBUS bus; the AUTBUS bus adopts an orthogonal frequency division multiplexing communication mechanism.

[0105] In actual implementation, the protocol data unit of the AUTBUS request message also includes a function code.

[0106] In actual implementation, the AUTBUS coupler may include an AUTBUS bus chip, and the AUTBUS coupler is connected to the AUTBUS bus via the AUTBUS bus chip.

[0107] In actual execution, after the controller sends the AUTBUS request message to the AUTBUS bus, the AUTBUS coupler can obtain the AUTBUS request message based on the device ID of the AUTBUS coupler.

[0108] In actual execution, the controller may send the AUTBUS request message to the AUTBUS bus via the AUTBUS protocol. The structure of the AUTBUS protocol is described in the above embodiment.

[0109] Step 620, the AUTBUS coupler parses the AUTBUS request message to obtain the target board address of the target low-speed IO module, encapsulates the function code and the target board address into a low-speed bus message, and sends the low-speed bus message to the target low-speed IO module based on the low-speed protocol. The target low-speed IO module executes the request command of the controller according to the function code.

[0110] In actual execution, the protocol data unit of the AUTBUS request message carries the target board address and function code of the target low-speed IO module. The AUTBUS coupler parses the AUTBUS request message to obtain the target board address of the target low-speed IO module.

[0111] In actual implementation, the AUTBUS coupler can perform board address allocation and field data reception with each of the multiple low-speed IO modules based on the low-speed protocol. The structure of the low-speed protocol is described in the above embodiment.

[0112] Step 630: The AUTBUS coupler receives the field data collected by the target low-speed IO module through the low-speed bus, and encapsulates the field data, the target board address and the device ID of the AUTBUS coupler into an AUTBUS response message and sends it to the controller.

[0113] In actual execution, the low-speed IO module sends the collected field data and the board address of the low-speed IO module to the AUTBUS coupler through the low-speed bus. The AUTBUS coupler encapsulates the field data, the target board address and the device ID of the AUTBUS coupler into an AUTBUS response message and sends it to the controller through the AUTBUS bus.

[0114] In actual implementation, the low speed bus may be a 422 or 485 bus communication.

[0115] In actual implementation, each low-speed IO module can transmit the collected field data to the AUTBUS coupler through the low-speed bus based on the corresponding target bandwidth, so that the AUTBUS coupler transmits the field data to the controller through the AUTBUS bus. The low-speed IO module can transmit the communication data to the low-speed bus through the uart port of the MCU.

[0116] In order to better understand the AUTBUS bus-based IO control system provided in the embodiment of the present application, it is further explained below through application examples. It should be understood that the following discussion is only exemplary.

[0117] In some embodiments, Figure 7 As shown, the AUTBUS bus-based IO control system includes a controller 710 (e.g., a high-performance server), an AUTBUS bus 720, a low-speed communication node 731, and a high-speed IO module 741. The low-speed communication node 731 may include an AUTBUS coupler and a low-speed IO module. Figure 7 The system shown also includes: KYWT series RS485 low-speed IO module (connected to the temperature and humidity meter), KYYZ series high-speed IO module (connected to the driver of the stepper motor motion kit) and IO expansion module and KYIO series coupler module (connected to the non-driver module in the stepper motor motion kit).

[0118] The IO control system based on the AUTBUS bus in the embodiment of the present application can be an electronic device, or a component in the electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or other devices other than the terminal. Exemplarily, the electronic device can be a mobile phone, a tablet computer, a laptop computer, a PDA, a vehicle-mounted electronic device, a mobile Internet device (Mobile Internet Device, MID), an augmented reality (augmented reality, AR) / virtual reality (virtual reality, VR) device, a robot, a wearable device, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a netbook or a personal digital assistant (personal digital assistant, PDA), etc., and can also be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc., and the embodiment of the present application is not specifically limited.

[0119] The AUTBUS bus-based IO control system in the embodiment of the present application may be a device having an operating system. The operating system may be a Microsoft (Windows) operating system, an Android (Android) operating system, an IOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.

[0120] In some embodiments, Figure 8 As shown, an embodiment of the present application also provides an electronic device 800, including a processor 801, a memory 802, and a computer program stored in the memory 802 and executable on the processor 801. When the program is executed by the processor 801, each process of the above-mentioned data interaction method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be described here.

[0121] It should be noted that the electronic devices in the embodiments of the present application include the mobile electronic devices and non-mobile electronic devices mentioned above.

[0122] An embodiment of the present application also provides a non-transitory computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the various processes of the above-mentioned data interaction method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0123] The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk.

[0124] An embodiment of the present application also provides a computer program product, including a computer program, which implements the above-mentioned data interaction method when executed by a processor.

[0125] The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk.

[0126] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned data interaction method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0127] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0128] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0129] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM / RAM, a disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0130] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

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

[0132] Although the embodiments of the present application have been shown and described, those skilled in the art will appreciate that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present application, and that the scope of the present application is defined by the claims and their equivalents.

Claims

1. An IO control system based on AUTBUS bus, characterized in that: include: A controller, an AUTBUS bus, at least one low-speed communication node and at least one high-speed IO module; The controller, each of the low-speed communication nodes and each of the high-speed IO modules are connected to the AUTBUS bus; The low-speed communication node transmits data to the controller via the AUTBUS bus; The high-speed IO module and the controller transmit data via the AUTBUS bus.

2. The AUTBUS bus-based IO control system according to claim 1, characterized in that: The low-speed communication node is a low-speed IO module.

3. The IO control system based on AUTBUS bus according to claim 1 is characterized in that: The low-speed communication node is an AUTBUS coupler, and the AUTBUS bus-based IO control system further includes a plurality of low-speed IO modules; the AUTBUS coupler is connected to the plurality of low-speed IO modules via a low-speed bus.

4. The AUTBUS bus-based IO control system according to claim 3, characterized in that: The AUTBUS coupler is used to parse out a target low-speed IO module according to the target board address carried in the protocol data unit of the AUTBUS request message after receiving the AUTBUS request message sent by the controller, encapsulate the function code and the target board address into a low-speed bus message and send it to the target low-speed IO module, and the target low-speed IO module executes the request command of the controller according to the function code; the function code is carried by the protocol data unit; the AUTBUS request message carries the device ID of the AUTBUS coupler.

5. The AUTBUS bus-based IO control system according to claim 4, characterized in that: The AUTBUS coupler is used to receive the field data collected by the low-speed IO module from the low-speed bus, and encapsulate the field data, the target board address and the device ID of the AUTBUS coupler into an AUTBUS response message and send it to the controller.

6. The AUTBUS bus-based IO control system according to claim 3, characterized in that: The AUTBUS coupler is used to allocate a corresponding board address to each of the low-speed IO modules and report the address to the controller.

7. The AUTBUS bus-based IO control system according to claim 5, characterized in that: The AUTBUS coupler periodically polls the low-speed IO module and receives field data collected by the low-speed IO module from the low-speed bus.

8. The AUTBUS bus-based IO control system according to claim 5, characterized in that: The controller allocates communication resources to the high-speed IO module, the low-speed IO module and the AUTBUS coupler connected to the AUTBUS bus.

9. The AUTBUS bus-based IO control system according to claim 5, characterized in that: It also includes non-AUTBUS bus powered devices and AUTBUS bus powered devices.

10. The AUTBUS bus-based IO control system according to any one of claims 1 to 5, characterized in that: The AUTBUS bus is a ring bus.

Images