Method and device for realizing CC-Link protocol data transmission based on AutBus and storage medium

Abstract

The invention discloses a method and equipment for realizing CC-Link protocol data transmission based on an AutBus bus and a storage medium, relates to the technical field of communication, and is applied to an AutBus converter, one side of the AutBus converter is connected with CC-Link equipment, and the other side of the AutBus converter is connected with other AutBus converters through the AutBus bus. The method comprises the following steps: receiving a CC-Link message sent by a source CC-Link device, and determining a target address corresponding to a target CC-Link device according to the CC-Link message; taking the target address and the CC-Link message as data contents, and filling a PAYLOAD field of the AutBus message with the data contents; according to the technical scheme, the AutBus message is sent to the AutBus, the original CC-Link equipment does not need to be dismantled and replaced, and equipment waste is avoided.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method, device and storage medium for implementing CC-Link protocol data transmission based on the AutBus bus. Background Technology

[0002] CC-Link (Control & Communication Link) and AutBus (Autonomous Bus) are two different industrial fieldbus protocols. In a CC-Link network, the hardware interfaces and communication firmware of CC-Link devices already in use are designed according to the CC-Link specification. If you want to introduce AutBus or replace the existing CC-Link network with AutBus, you need to remove and replace these CC-Link devices with devices designed according to the AutBus specification. However, this replacement method means discarding hardware that is still working properly, which wastes a lot of equipment resources.

[0003] The above content is only used to help understand the technical solution of this application and does not represent an admission that the above content is prior art. Summary of the Invention

[0004] The main objective of this application is to provide a method, device, and storage medium for implementing CC-Link protocol data transmission based on the AutBus bus, aiming to solve the technical problem of reducing equipment waste from replacing CC-Link and AutBus bus networks.

[0005] To achieve the above objectives, this application proposes a method for implementing CC-Link protocol data transmission based on the AutBus bus, applied to an AutBus converter. One side of the AutBus converter is connected to a CC-Link device, and the other side is connected to other AutBus converters via the AutBus bus. The method for implementing CC-Link protocol data transmission based on the AutBus bus includes the following steps: Receive the CC-Link message sent by the source CC-Link device, and determine the target address corresponding to the target CC-Link device based on the CC-Link message; The target address and the CC-Link message are used as data content and filled into the PAYLOAD field of the AutBus message; The AutBus message is sent to the AutBus bus.

[0006] In one embodiment, before the step of sending the AutBus message to the AutBus bus, the method further includes: Based on the target address, determine the target identifier corresponding to the target AutBus converter in the local address mapping table; The target identifier is used as data content and filled into the PAYLOAD field of the AutBus message.

[0007] In one embodiment, before the step of sending the AutBus message to the AutBus bus, the method further includes: A preset character is filled into the TYPE field of the AutBus message. The preset character is used to indicate that the CC-Link message is included in the AutBus message.

[0008] In one embodiment, the method further includes: When the AutBus converter receives the AutBus message transmitted via the AutBus bus, it obtains the target address and the CC-Link message from the PAYLOAD field; Based on the target address, a match is performed in the local address mapping table; If the target address exists in the address mapping table, the CC-Link message is sent to the target CC-Link device according to the target address.

[0009] In one embodiment, after the step of matching the target address in the local address mapping table, the method further includes: If the target address does not exist in the local address mapping table, the CC-Link message is discarded.

[0010] In one embodiment, the method further includes: When the AutBus converter receives the AutBus message transmitted via the AutBus bus, it obtains the target address, the CC-Link message, and the target identifier from the PAYLOAD field. If the target identifier matches the identifier of the AutBus converter, the CC-Link message is sent to the target CC-Link device according to the target address.

[0011] In one embodiment, before the step of receiving a CC-Link message sent by the source CC-Link device and determining the target address corresponding to the target CC-Link device based on the CC-Link message, the method further includes: When the AutBus converter detects the access of the CC-Link device, it associates the address of the CC-Link device with the identifier of the AutBus converter and stores it in a local address mapping table.

[0012] In one embodiment, before the step of receiving a CC-Link message sent by the source CC-Link device and determining the target address corresponding to the target CC-Link device based on the CC-Link message, the method further includes: When the AutBus converter detects the access of the CC-Link device, it associates the address of the CC-Link device with the identifier of the AutBus converter and stores it in the address mapping table; The address mapping table is synchronized to the other AutBus converters via the AutBus bus.

[0013] Furthermore, to achieve the above objectives, this application also proposes a device for implementing CC-Link protocol data transmission based on the AutBus bus. The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor. The computer program is configured to implement the steps of the method for implementing CC-Link protocol data transmission based on the AutBus bus as described above.

[0014] In addition, to achieve the above objectives, this application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the method for implementing CC-Link protocol data transmission based on the AutBus bus as described above.

[0015] This application provides a method for implementing CC-Link protocol data transmission based on the AutBus bus, applied to an AutBus converter. One side of the AutBus converter is connected to a CC-Link device, and the other side is connected to other AutBus converters via the AutBus bus. The method involves receiving a CC-Link message sent by a source CC-Link device and determining the target address corresponding to the target CC-Link device based on the CC-Link message; filling the PAYLOAD field of the AutBus message with the target address and the CC-Link message as data content; and then sending the AutBus message to the AutBus bus.

[0016] The above method uses an "AutBus converter" as an intermediate layer to completely encapsulate CC-Link messages into AutBus messages, allowing both buses to coexist on the same network. The hardware interface and communication firmware of the CC-Link device remain unchanged; simply connecting the AutBus converter to the CC-Link device maps CC-Link messages to AutBus messages. Existing CC-Link devices do not need to be removed or replaced, avoiding equipment waste. Attached Figure Description

[0017] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0018] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is a schematic diagram of the architecture provided in Embodiment 1 of the method for implementing CC-Link protocol data transmission based on the AutBus bus in this application; Figure 2 This is a flowchart illustrating a method for implementing CC-Link protocol data transmission based on the AutBus bus, as described in Embodiment 1 of this application. Figure 3 This is a schematic diagram of the frame format of the CC-Link protocol provided in Embodiment 1 of the method for implementing CC-Link protocol data transmission based on the AutBus bus in this application; Figure 4 This is a schematic diagram of the frame format of the AutBus protocol provided in Embodiment 1 of the method for implementing CC-Link protocol data transmission based on the AutBus bus in this application; Figure 5 This is a flowchart illustrating Embodiment 2 of the method for implementing CC-Link protocol data transmission based on the AutBus bus in this application; Figure 6 This is a flowchart illustrating Embodiment 3 of the method for implementing CC-Link protocol data transmission based on the AutBus bus in this application; Figure 7 This is a flowchart illustrating Embodiment 4 of the method for implementing CC-Link protocol data transmission based on the AutBus bus in this application; Figure 8 This is a schematic diagram of the interaction process provided in Embodiment 4 of the method for implementing CC-Link protocol data transmission based on the AutBus bus in this application; Figure 9 This is a schematic diagram of message changes provided for the method of implementing CC-Link protocol data transmission based on the AutBus bus in the embodiments of this application; Figure 10 This is a schematic diagram of the device structure of the hardware operating environment involved in the method of implementing CC-Link protocol data transmission based on the AutBus bus in the embodiments of this application.

[0020] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0021] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of this application and are not intended to limit this application.

[0022] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific embodiments. It should be noted that all actions involving the acquisition of signals, information, or data in this application are performed in accordance with the relevant data protection laws and regulations of the country where the application is located, and with authorization from the owner of the corresponding device.

[0023] CC-Link and AutBus are two different industrial fieldbus protocols. In a CC-Link network, the hardware interfaces and communication firmware of CC-Link devices already in use are designed according to the CC-Link specification. If you want to introduce AutBus or replace the existing CC-Link network with AutBus, you need to remove and replace these CC-Link devices with devices designed according to the AutBus specification. However, this replacement method means discarding hardware that is still working properly, which wastes a lot of equipment resources.

[0024] In view of the above problems, this application proposes a method for implementing CC-Link protocol data transmission based on the AutBus bus, applied to an AutBus converter. One side of the AutBus converter is connected to a CC-Link device, and the other side is connected to other AutBus converters via the AutBus bus. The method involves receiving a CC-Link message sent by a source CC-Link device and determining the target address corresponding to the target CC-Link device based on the CC-Link message; filling the PAYLOAD field of the AutBus message with the target address and the CC-Link message as data content; and sending the AutBus message to the AutBus bus.

[0025] The above method uses an "AutBus converter" as an intermediate layer to completely encapsulate CC-Link messages into AutBus messages, allowing both buses to coexist on the same network. The hardware interface and communication firmware of the CC-Link device remain unchanged; simply connecting the AutBus converter to the CC-Link device maps CC-Link messages to AutBus messages. Existing CC-Link devices do not need to be removed or replaced, avoiding equipment waste.

[0026] It should be noted that the executing entity in this embodiment can be a computing service device with data processing, network communication, and program execution functions, such as a tablet computer or personal computer, or an electronic device or AutBus converter capable of performing the above functions. The following description uses an AutBus converter as an example to illustrate this embodiment and the subsequent embodiments.

[0027] Based on this, the first embodiment of this application provides a method for implementing CC-Link protocol data transmission based on the AutBus bus, applied to an AutBus converter. One side of the AutBus converter is connected to a CC-Link device, and the other side is connected to other AutBus converters via the AutBus bus. Figure 1 As shown, Figure 1 There is an AutBus bus, which is connected to AutBus converters 1, 2, 3, 4, and 5 respectively. AutBus converter 1 is connected to CC-Link device A, AutBus converter 2 to CC-Link device B, AutBus converter 3 to CC-Link devices C and D, and AutBus converter 4 to CC-Link device E. In this embodiment, CC-Link devices refer to field devices that only support the CC-Link protocol in the CC-Link network, including remote I / O modules, frequency converters, and CC-Link interface PLC (Programmable Logic Controller) slave units.

[0028] Reference Figure 2 In this embodiment, the method for implementing CC-Link protocol data transmission based on the AutBus bus includes steps S10 to S30: Step S10: Receive the CC-Link message sent by the source CC-Link device, and determine the target address corresponding to the target CC-Link device based on the CC-Link message.

[0029] It should be noted that the AutBus converter is a bridging device with a "dual protocol interface" used to achieve data forwarding and protocol encapsulation / decapsulation between the CC-Link device side and the AutBus bus side. One end is a CC-Link physical interface for connecting to existing CC-Link devices, and the other end is an AutBus physical interface for connecting to the AutBus bus.

[0030] For example, refer to Figure 3 , Figure 3This diagram illustrates the frame format of the CC-Link protocol. A CC-Link frame includes the following fields: preamble, SD (Start Delimiter), DLC (Data Link Control Byte), Data Field, CRC (Cyclic Redundancy Check), and ED (End Delimiter). The DLC further includes a frame type field, an address information field, and a control information field. The address information field specifies the address of the target CC-Link device and / or the address of the source CC-Link device. The source CC-Link device refers to the CC-Link device that sent the CC-Link message. In this implementation, the address of the target CC-Link device is stored in the address information field of the CC-Link frame.

[0031] When the AutBus converter receives a CC-Link message from the source CC-Link device, it obtains the target address of the target CC-Link device from the DLC of the CC-Link message.

[0032] Step S20: The target address and the CC-Link message are used as data content and filled into the PAYLOAD field of the AutBus message.

[0033] It should be noted that, referring to Figure 4 , Figure 4 This is a schematic diagram of the AutBus protocol frame format. An AutBus message includes the following fields: TYPE field, Fragment_no field, LENGTH field, PAYLOAD field, and CRC field. The TYPE field indicates the frame type; the Fragment_no field indicates the AutBus message fragment sequence number; the LENGTH field indicates the number of bits in the payload data PAYLOAD field of the AutBus message; and the PAYLOAD field indicates the valid data carried by the AutBus message.

[0034] For example, the "Dst_NodeID", "D_DLC", "S_DLC", "LENGTH", and "CC-Link Message" subfields can be set in the PAYLOAD field of the AutBus frame; these are used to store the target identifier of the target AutBus converter, the target address of the target CC-Link device, the source address of the source CC-Link device, the length n of the CC-Link message, and the CC-Link message itself, respectively. See the table below:

[0035] For example, when the AutBus converter receives a CC-Link message sent by the source CC-Link device and determines the target address corresponding to the target CC-Link device based on the CC-Link message, it fills the source address of the source CC-Link device into the "S_DLC" subfield, fills the target address into the "D_DLC" subfield, fills the CC-Link message into the "CC-Link Message" subfield, and fills the length of the CC-Link message into the "LENGTH" subfield. Other subfields can be left empty by default.

[0036] Step S30: Send the AutBus message to the AutBus bus.

[0037] After encapsulating the CC-Link message into an AutBus message in step S20, the AutBus message is sent to the AutBus bus and then transmitted to the target CC-Link device via the AutBus bus.

[0038] In this embodiment, the source CC-Link device address, target CC-Link device address, and other CC-Link device address information are explicitly carried in the AutBus message, and the entire CC-Link message is placed in the PAYLOAD field. This allows the use of the existing AutBus message format. Only the entire CC-Link message needs to be written into the PAYLOAD field to realize CC-Link protocol data transmission without modifying the CC-Link device hardware, thus avoiding waste.

[0039] Understandably, traditional protocol conversion methods typically involve peeling away the original frame structure layer by layer from the software protocol stack and then reconstructing a new frame according to the target protocol rules. This requires multiple steps, including field parsing, cross-protocol address mapping table lookups, and double CRC checks, resulting in low real-time performance and high software computing power requirements. This application, however, preserves the original CC-Link message structure, avoiding the latency and compatibility issues caused by content parsing. It achieves cross-protocol routing by embedding a Layer 3 addressing label within the PAYLOAD field of the AutBus frame, utilizing the AutBus converter hardware component to compensate for the real-time shortcomings of the software protocol stack conversion method.

[0040] Based on the first embodiment of this application, in the second embodiment of this application, the content that is the same as or similar to that in the first embodiment can be referred to the above description, and will not be repeated hereafter. On this basis, refer to Figure 5 The method for implementing CC-Link protocol data transmission based on the AutBus bus further includes steps S40 to S60: Step S40: When the AutBus converter receives the AutBus message transmitted via the AutBus bus, it obtains the target address and the CC-Link message from the PAYLOAD field.

[0041] Step S50: Based on the target address, perform a match in the local address mapping table.

[0042] Step S60: If the target address exists in the address mapping table, then the CC-Link message is sent to the target CC-Link device according to the target address.

[0043] When the AutBus converter receives an AutBus message transmitted via the AutBus bus, it decapsulates the AutBus message and obtains the target address and the complete CC-Link message from the PAYLOAD field.

[0044] Understandably, when the AutBus converter receives a CC-Link message from a source CC-Link device, it retrieves the target address of the target CC-Link device from the DLC (Destination Location Code) of the CC-Link message. Therefore, when the AutBus converter encapsulates the CC-Link message into an AutBus message, it can fill the target address of the target CC-Link device into the PAYLOAD field, specifically the "D_DLC" subfield. This way, when the AutBus converter receives an AutBus message, it can directly read the target address from the PAYLOAD field of the AutBus message.

[0045] After obtaining the target address, the AutBus converter can look up its local address mapping table. This table contains the mapping relationship between the AutBus converter's own identifier and the addresses of each CC-Link device connected to the AutBus converter. If an address matching the target address exists in the address mapping table, a CC-Link message is sent to the target CC-Link device corresponding to that target address.

[0046] Optionally, if the target address does not exist in the local address mapping table, the CC-Link message is discarded.

[0047] For example, after obtaining the target address, the AutBus converter determines the identifier of the AutBus converter associated with the address of the target CC-Link device by looking up the local address mapping table. If the target address does not exist in the address mapping table, the CC-Link packet is discarded.

[0048] by Figure 1Taking the illustrated architecture as an example, when AutBus converter 1 receives a CC-Link message sent by CC-Link device A with CC-Link device E as the target CC-Link device, AutBus converter 1 encapsulates the CC-Link message into an AutBus message and sends it to AutBus converters 2, 3, 4, and 5. AutBus converters 2, 3, and 4, after determining through their local address mapping tables that they are not connected to CC-Link device E, discard the received AutBus message. AutBus converter 5, after determining through its local address mapping table that it is connected to CC-Link device E, decapsulates the AutBus message and forwards the CC-Link message to CC-Link device E.

[0049] Based on the above, in a feasible implementation, before the step of the AutBus converter receiving the CC-Link message sent by the source CC-Link device and determining the target address corresponding to the target CC-Link device according to the CC-Link message, the method further includes: when the AutBus converter detects the access of the CC-Link device, associating the address of the CC-Link device with the identifier of the AutBus converter and storing it in a local address mapping table.

[0050] For example, with Figure 1 Taking the illustrated architecture as an example, if CC-Link device A is connected to AutBus converter 1, then the address mapping table inside AutBus converter 1 will associate and store the identifier of AutBus converter 1 with the address of CC-Link device A. If CC-Link devices C and D are connected to AutBus converter 3, then the address mapping table inside AutBus converter 3 will associate and store the identifier of AutBus converter 3 with the addresses of CC-Link devices C and D. Each AutBus converter connected to the AutBus bus only records the address of the CC-Link device it is connected to.

[0051] Based on the first embodiment of this application, in the third embodiment of this application, the content that is the same as or similar to the first embodiment can be referred to the above description, and will not be repeated hereafter. On this basis, refer to Figure 6 Before step S30, the method for implementing CC-Link protocol data transmission based on the AutBus bus further includes steps S70 to S80: Step S70: Determine the target identifier corresponding to the target AutBus converter in the local address mapping table based on the target address.

[0052] Optionally, in this embodiment, when the AutBus converter detects a CC-Link device access, it associates the CC-Link device's address with the AutBus converter's identifier and stores it in a local address mapping table. Then, the address mapping table is synchronized to other AutBus converters via the AutBus bus.

[0053] For example, with Figure 1 Taking the architecture shown as an example, when each CC-Link device follows... Figure 1 After the architecture shown is connected to the AutBus converter, AutBus converter 1 is associated with the address of CC-Link device A, AutBus converter 2 with the address of CC-Link device B, AutBus converter 3 with the addresses of CC-Link devices C and D, and AutBus converter 4 with the address of CC-Link device E. After synchronization, each AutBus converter will store an address mapping table as shown in the table below:

[0054] Through the above steps of synchronizing the address mapping table, as soon as a CC-Link device connects to an AutBus converter, the address of the CC-Link device and the identifier of the corresponding AutBus converter are written into the address mapping table and broadcast to all AutBus converters on the AutBus bus. Thus, when any AutBus converter receives a CC-Link message from a CC-Link device, it can directly determine the target AutBus converter based on the destination address of the CC-Link message and its local address mapping table. It then sends the AutBus message encapsulated with the CC-Link message to the target AutBus converter, which in turn forwards the CC-Link message to the target CC-Link device, thereby enabling the transmission of CC-Link messages between different CC-Link devices.

[0055] Step S80: The target identifier is used as data content and filled into the PAYLOAD field of the AutBus message.

[0056] Optionally, the target identifier can be populated into the "Dst_NodeID" subfield of the AutBus message.

[0057] Understandably, in this embodiment, all AutBus converters maintain the same address mapping table locally. Once an AutBus converter detects a new CC-Link device accessing the network, it must synchronize the entry "AutBus converter identifier ↔ CC-Link device address" to all AutBus converters via the AutBus bus. Only after synchronization is complete can other AutBus converters accurately encapsulate CC-Link messages destined for the target CC-Link device into unidirectional AutBus messages, directly reaching the unique target AutBus converter. The advantage of this method is that the same AutBus device only appears once on the AutBus bus line, resulting in high bandwidth utilization, a unique forwarding path, a fixed number of hops, and precise end-to-end latency calculation. However, the cost is that each change in the AutBus network topology requires a synchronization process.

[0058] In Embodiment 2 described above, forced synchronization of the address mapping table is not required. The AutBus converter only records locally which CC-Link devices it directly connects to, and no longer actively pushes the "AutBus converter identifier ↔ CC-Link device address" entry to other AutBus converters. In this case, since the AutBus converter cannot determine the target AutBus converter, when it receives a CC-Link message, the source AutBus converter no longer looks up the table for precise one-way propagation, but directly broadcasts the encapsulated AutBus message to all other AutBus converters; the receiving AutBus converters each use their local tables for filtering—if the address of the target CC-Link device is found in the local address mapping table, it is decapsulated and forwarded; otherwise, it is discarded. Since the entries are no longer synchronized through the AutBus bus, any newly inserted CC-Link device can be immediately recognized by the local machine, and the CC-Link message sent by the newly inserted CC-Link can be encapsulated into an AutBus message and broadcast to the entire AutBus network. The initial communication delay is only limited by the delay of one broadcast, realizing plug-and-play functionality. However, this AutBus message will be copied N-1 times on the AutBus bus link (N is the number of AutBus converters), and the instantaneous bandwidth consumption will increase linearly with the network size. Therefore, the transmission method in the above embodiment two sacrifices bandwidth efficiency in exchange for simpler configuration and a faster plug-and-play experience.

[0059] Based on Embodiment 3 of this application, in the fourth embodiment of this application, the same or similar content as the above embodiments can be referred to the above description, and will not be repeated hereafter. Based on this, refer to... Figure 7The method for implementing CC-Link protocol data transmission based on the AutBus bus further includes steps S90~S100: Step S90: When the AutBus converter receives the AutBus message transmitted via the AutBus bus, it obtains the target address, the CC-Link message, and the target identifier from the PAYLOAD field.

[0060] Understandably, when an AutBus converter receives a CC-Link message from a source CC-Link device and encapsulates it into an AutBus message, it fills the target identifier of the target AutBus converter into the PAYLOAD field of the AutBus message. Therefore, when an AutBus converter receives an AutBus message transmitted via the AutBus bus, it can obtain the target identifier from the PAYLOAD field, specifically the "Dst_NodeID" subfield.

[0061] Step S100: If the target identifier matches the identifier of the AutBus converter, the CC-Link message is sent to the target CC-Link device according to the target address.

[0062] Optionally, if the target identifier does not match the identifier of the AutBus converter, or if the address of the target CC-Link device does not exist in the local address mapping table of the AutBus converter, the AutBus message will be discarded.

[0063] To better understand the solution presented in this embodiment, in conjunction with Figure 1 The architecture shown further illustrates this implementation.

[0064] Reference Figure 8CC-Link device A and CC-Link device C are connected to AutBus converter 1 and AutBus converter 3 respectively, and AutBus converter 1 and AutBus converter 3 have synchronized their address mapping tables. Assume CC-Link device A wants to send a CC-Link message to CC-Link device C. CC-Link device A first sends a CC-Link message to AutBus converter 1. AutBus converter 1 obtains the target address of CC-Link device C from the CC-Link message, finds the target identifier of the AutBus converter corresponding to the target address of CC-Link device C in the address mapping table (which is 3), encapsulates the CC-Link message into an AutBus message, writes the target address and target identifier of CC-Link device C into the PAYLOAD field, and sends the AutBus message to AutBus converter 3. After receiving the AutBus message, AutBus converter 3 obtains the destination identifier from the message. Once it confirms that the destination identifier matches its own identifier, it extracts the CC-Link message from the AutBus message and sends it to CC-Link device C according to the destination address. This enables the transmission of CC-Link data between CC-Link device A and CC-Link device C via the AutBus bus.

[0065] Based on the above embodiments, in the fifth embodiment of this application, the same or similar content as the above embodiments can be referred to the above description, and will not be repeated hereafter. In addition, before step S30, the method further includes: filling the TYPE field of the AutBus message with a preset character, wherein the preset character is used to indicate that the AutBus message includes a CC-Link message.

[0066] For example, the CC-Link message is used as the payload data PAYLOAD of the AutBus message and stored in the PAYLOAD field. At the same time, the TYPE field is set to a preset character such as "0x00" to tell the receiving AutBus converter that the AutBus message carries CC-Link protocol content.

[0067] For example, refer to Figure 9 , Figure 9 This application provides a schematic diagram illustrating message changes in a method for implementing CC-Link protocol data transmission based on the AutBus bus, as described in the embodiments of this application. Specifically: Suppose CC-Link device A wants to send a CC-Link message to CC-Link device C. CC-Link device A will send the CC-Link message as a CC-Link data packet to AutBus converter 1. AutBus converter 1 will write the CC-Link data packet into its generated AutBus data packet (i.e., an AutBus message). Then, the AutBus data packet carrying the CC-Link data packet will be transmitted via the AutBus bus to AutBus converter 3. AutBus converter 3 will extract the CC-Link data packet from the AutBus data packet and send it to CC-Link device C.

[0068] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the method of implementing CC-Link protocol data transmission based on the AutBus bus. Any simple modifications based on this technical concept are within the protection scope of this application.

[0069] This application provides a device for implementing CC-Link protocol data transmission based on the AutBus bus. The device for implementing CC-Link protocol data transmission based on the AutBus bus includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the method for implementing CC-Link protocol data transmission based on the AutBus bus in the above embodiment 1.

[0070] The following is for reference. Figure 10 This document illustrates a schematic diagram of a device suitable for implementing CC-Link protocol data transmission based on the AutBus bus in the embodiments of this application. The device for implementing CC-Link protocol data transmission based on the AutBus bus in the embodiments of this application may include, but is not limited to, mobile terminals such as laptops, digital broadcast receivers, personal digital assistants (PDAs), tablet computers (PADs), portable media players (PMPs), and in-vehicle terminals (e.g., in-vehicle navigation terminals), as well as fixed terminals such as digital TVs and desktop computers. Figure 10 The device shown that implements CC-Link protocol data transmission based on the AutBus bus is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments in this application.

[0071] like Figure 10As shown, a device implementing CC-Link protocol data transmission based on the AutBus bus may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 1002 or a program loaded from storage device 1003 into random access memory (RAM) 1004. The random access memory 1004 also stores various programs and data required for the operation of the device implementing CC-Link protocol data transmission based on the AutBus bus. The processing unit 1001, ROM 1002, and RAM 1004 are interconnected via bus 1005. Input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to I / O interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. Communication device 1009 allows devices implementing CC-Link protocol data transmission based on the AutBus bus to communicate wirelessly or wiredly with other devices to exchange data. Although devices implementing CC-Link protocol data transmission based on the AutBus bus with various systems are shown in the figure, it should be understood that it is not required to implement or have all of the systems shown. More or fewer systems may be implemented alternatively.

[0072] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from read-only memory 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0073] The device for implementing CC-Link protocol data transmission based on the AutBus bus provided in this application, employing the method for implementing CC-Link protocol data transmission based on the AutBus bus in the above embodiments, can solve the technical problem of reducing equipment waste from replacing CC-Link and AutBus bus networks. Compared with the prior art, the beneficial effects of the device for implementing CC-Link protocol data transmission based on the AutBus bus provided in this application are the same as the beneficial effects of the method for implementing CC-Link protocol data transmission based on the AutBus bus provided in the above embodiments, and other technical features in this device for implementing CC-Link protocol data transmission based on the AutBus bus are the same as those disclosed in the method of the previous embodiment, and will not be repeated here.

[0074] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0075] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0076] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, which are used to execute the method for implementing CC-Link protocol data transmission based on the AutBus bus in the above embodiments.

[0077] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or flash memory, optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, radio frequency (RF), etc., or any suitable combination thereof.

[0078] The aforementioned computer-readable storage medium may be included in a device that implements CC-Link protocol data transmission based on the AutBus bus; or it may exist independently and not be assembled into a device that implements CC-Link protocol data transmission based on the AutBus bus.

[0079] The aforementioned computer-readable storage medium carries one or more programs that, when executed by a device implementing CC-Link protocol data transmission based on the AutBus bus, enable the device to write computer program code for performing the operations of this application in one or more programming languages ​​or a combination thereof. These programming languages ​​include object-oriented programming languages—such as Java, Smalltalk, and C++—and conventional procedural programming languages—such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, or as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0080] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0081] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0082] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described method for implementing CC-Link protocol data transmission based on the AutBus bus. This solves the technical problem of reducing equipment waste during CC-Link and AutBus bus network replacements. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the method for implementing CC-Link protocol data transmission based on the AutBus bus provided in the above embodiments, and will not be repeated here.

[0083] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the method for implementing CC-Link protocol data transmission based on the AutBus bus as described above.

[0084] The computer program product provided in this application can solve the technical problem of reducing equipment waste during replacement of CC-Link and AutBus bus networks. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as those of the method for implementing CC-Link protocol data transmission based on AutBus bus provided in the above embodiments, and will not be repeated here.

[0085] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.

Claims

1. A method for implementing CC-Link protocol data transmission based on the AutBus bus, characterized in that, Applied to an AutBus converter, wherein one side of the AutBus converter is connected to a CC-Link device and the other side is connected to other AutBus converters via an AutBus bus, the method for implementing CC-Link protocol data transmission based on the AutBus bus includes the following steps: Receive the CC-Link message sent by the source CC-Link device, and determine the target address corresponding to the target CC-Link device based on the CC-Link message; The target address and the CC-Link message are used as data content and filled into the PAYLOAD field of the AutBus message; The AutBus message is sent to the AutBus bus.

2. The method for implementing CC-Link protocol data transmission based on the AutBus bus as described in claim 1, characterized in that, Before the step of sending the AutBus message to the AutBus bus, the method further includes: Based on the target address, determine the target identifier corresponding to the target AutBus converter in the local address mapping table; The target identifier is used as data content and filled into the PAYLOAD field of the AutBus message.

3. The method for implementing CC-Link protocol data transmission based on the AutBus bus as described in claim 1 or 2, characterized in that, Before the step of sending the AutBus message to the AutBus bus, the method further includes: A preset character is filled into the TYPE field of the AutBus message. The preset character is used to indicate that the CC-Link message is included in the AutBus message.

4. The method for implementing CC-Link protocol data transmission based on the AutBus bus as described in claim 1, characterized in that, The method further includes: When the AutBus converter receives the AutBus message transmitted via the AutBus bus, it obtains the target address and the CC-Link message from the PAYLOAD field; Based on the target address, a match is performed in the local address mapping table; If the target address exists in the address mapping table, the CC-Link message is sent to the target CC-Link device according to the target address.

5. The method for implementing CC-Link protocol data transmission based on the AutBus bus as described in claim 4, characterized in that, After the step of matching the target address in the local address mapping table, the method further includes: If the target address does not exist in the local address mapping table, the CC-Link message is discarded.

6. The method for implementing CC-Link protocol data transmission based on the AutBus bus as described in claim 3, characterized in that, The method further includes: When the AutBus converter receives the AutBus message transmitted via the AutBus bus, it obtains the target address, the CC-Link message, and the target identifier from the PAYLOAD field. If the target identifier matches the identifier of the AutBus converter, the CC-Link message is sent to the target CC-Link device according to the target address.

7. The method for implementing CC-Link protocol data transmission based on the AutBus bus as described in claim 4 or 5, characterized in that, Before the step of receiving the CC-Link message sent by the source CC-Link device and determining the target address corresponding to the target CC-Link device based on the CC-Link message, the method further includes: When the AutBus converter detects the access of the CC-Link device, it associates the address of the CC-Link device with the identifier of the AutBus converter and stores it in a local address mapping table.

8. The method for implementing CC-Link protocol data transmission based on the AutBus bus as described in claim 2, characterized in that, Before the step of receiving the CC-Link message sent by the source CC-Link device and determining the target address corresponding to the target CC-Link device based on the CC-Link message, the method further includes: When the AutBus converter detects the access of the CC-Link device, it associates the address of the CC-Link device with the identifier of the AutBus converter and stores it in the address mapping table; The address mapping table is synchronized to the other AutBus converters via the AutBus bus.

9. A device for implementing CC-Link protocol data transmission based on the AutBus bus, characterized in that, The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the method for implementing CC-Link protocol data transmission based on the AutBus bus as described in any one of claims 1 to 8.

10. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, it implements the steps of the method for implementing CC-Link protocol data transmission based on the AutBus bus as described in any one of claims 1 to 8.

Images