Multi-axis integrated drive and control servo module, system, and control method based on EtherCAT bus

The multi-axis drive and control integrated servo module, which is integrated through the EtherCAT bus, realizes the internal closed-loop processing of motion control data and motor feedback, solves the delay and deviation problems in multi-axis synchronous control, and improves the system's synchronization and response speed.

CN122697906BActive Publication Date: 2026-11-17SHENZHEN DUOHE ELECTRIC CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202611122412.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2026-07-28
Publication Date
2026-11-17
Estimated Expiration
2046-07-28

AI Technical Summary

Technical Problem

In existing multi-axis motion control systems, the transmission delay of external communication links, the difference in internal processing delay of servo drivers, and the deviation in PWM update timing affect the multi-axis synchronization effect. Furthermore, the separation of the controller and the driver leads to the dispersion of motor feedback data, making it difficult to achieve real-time and accurate synchronous control.

Method used

A multi-axis drive and control integrated servo module based on EtherCAT bus is adopted. Through the integration of bus core, control core, shared memory unit and drive core, internal closed-loop processing of motion control data and motor feedback is realized. The PWM update of power drive stage is synchronously triggered by EtherCAT distributed clock to compensate for synchronization deviation.

Benefits of technology

It improves the real-time performance and consistency of multi-axis synchronous drive, reduces the interaction path between control and feedback variables, shortens response time, and enhances the system's synchronization and fault response capabilities.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122697906B_ABST
    Figure CN122697906B_ABST
Patent Text Reader

Abstract

The embodiments of this application relate to the fields of industrial automation and motion control technology; in particular, a multi-axis integrated drive and control servo module, system, and control method based on the EtherCAT bus. The system includes a bus core, a control core, a shared memory unit, and a drive core. The bus core connects to the EtherCAT bus to receive motion control data and sends it to the control core. The control core determines the axis drive control quantity to be written into the first shared data area based on the motion control data, and the drive core reads the axis drive control quantity and updates the PWM output. The second shared data area stores motor feedback quantities, and the control core updates the axis drive control quantities based on the motion control data and the motor feedback quantities. The bus core outputs a synchronous trigger signal based on the EtherCAT distributed clock, enabling each power drive stage to synchronously update the PWM, shortening the data interaction path between the control side and the drive side, and bringing bus synchronization down to the drive-level PWM update, thereby improving the real-time performance and consistency of multi-axis synchronous drive.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments of this application relate to the fields of industrial automation and motion control technology; in particular, multi-axis integrated drive and control servo modules, systems, and control methods based on EtherCAT bus. Background Technology

[0002] Multi-axis motion control systems are widely used in robots, CNC machine tools, electronic assembly equipment, semiconductor processing equipment, and automated production lines. In these scenarios, multiple motor axes need to perform position, speed, torque, or current control according to a unified trajectory planning result. The synchronization between the motor axes directly affects the end-point trajectory accuracy, machining quality, equipment operating stability, and mechanical structure lifespan.

[0003] Existing multi-axis motion control systems typically employ a hierarchical architecture consisting of a host computer or PLC, independent motion controllers, and multiple servo drives. The motion controller calculates the control quantities for each axis based on motion commands sent from the host computer or PLC, and then transmits these control quantities to the individual servo drives via an EtherCAT bus or other communication interface. Each servo drive then drives its corresponding motor based on the received control quantities. While this architecture facilitates expansion of the number of axes, the control calculations, drive execution, and feedback acquisition are distributed across different devices, and the controller and drives rely on external communication links to transmit control and feedback quantities.

[0004] In multi-axis high-precision synchronization scenarios, transmission delays in external communication links, differences in internal processing delays of each servo driver, PWM update timing deviations of different power drive stages, and inconsistent feedback data return paths can all affect the multi-axis synchronization effect. For applications such as gantry dual-drive, robot multi-joint interpolation, electronic cams, and high-speed assembly, even if the host motion command has a synchronized clock at the communication level, if the synchronization constraints are not further applied to the actual PWM update timing of each servo module's power drive stage, multiple motor axes may still experience output phase differences, leading to trajectory deviations, mechanical torsion, vibration, or wear.

[0005] Furthermore, in traditional systems where the controller and driver are separate, motor feedback, power stage temperature, current status, safety shutdown status, and alarm information are scattered across multiple devices, making it difficult for the control side to obtain timely, in-depth operational data from the drive side. In the event of overcurrent, overtemperature, collision, runaway, or safety communication anomalies, the system requires additional safety relays, safety PLCs, or independent diagnostic equipment for protection and fault location, increasing wiring complexity, equipment size, and maintenance costs.

[0006] Therefore, there is a need for an integrated drive and control servo module that can serve as a basic building block of a multi-axis servo system. This module should enable each servo module to complete motion control data reception, axis drive control quantity generation, power drive level PWM update, and motor feedback closed-loop update, and enable multiple servo modules to achieve drive-level synchronization under the EtherCAT distributed clock reference. Summary of the Invention

[0007] This application aims to solve the problem of how to further reduce the actual motion state deviation between different motor axes in a distributed multi-axis system composed of multiple single-axis drive and control integrated servo modules, while maintaining a unified PWM update time.

[0008] This application provides a multi-axis integrated drive and control servo module based on EtherCAT bus. The servo module includes a bus core, a control core, a shared memory unit, and a drive core. The bus core connects to the EtherCAT bus to receive motion control data and sends it to the control core. The shared memory unit includes a first shared data area and a second shared data area. The drive core includes a power drive stage, each corresponding to a motor axis. The control core determines the axis drive control quantity to be written into the first shared data area based on the motion control data. The drive core reads the axis drive control quantity from the first shared data area and updates the PWM output of the power drive stage according to the axis drive control quantity. The second shared data area obtains and stores the electrical... The control core reads the motor feedback from the second shared data area and updates the axis drive control quantity written to the first shared data area based on the motion control data and the motor feedback. The bus core outputs a synchronization trigger signal to the drive core according to the EtherCAT distributed clock, and the power drive stage performs PWM update at the update time corresponding to the synchronization trigger signal. The bus core also receives synchronization status data from other servo modules. The control core determines the position deviation or synchronization deviation between the corresponding motor axis of this servo module and the corresponding motor axis of other servo modules based on the synchronization status data and the motor feedback, and updates the axis drive control quantity written to the first shared data area based on the position deviation or synchronization deviation.

[0009] Through the above scheme, each servo module can function as an integrated drive and control unit for a motor axis. Motion control data enters the control core via the bus core. The axis drive control quantity determined by the control core is no longer sent to the independent driver via an external bus, but is instead written into the first shared data area located between the control core and the drive core. The drive core reads the axis drive control quantity from the first shared data area and directly updates the PWM output of its power drive stage. The motor feedback quantity collected by the drive side is written into the second shared data area and read by the control core to continue updating the axis drive control quantity. Thus, a bidirectional data closed loop is established between the control side and the drive side within the servo module, shortening the interaction path between control quantity and feedback quantity. Simultaneously, the bus core outputs a synchronization trigger signal to the drive core according to the EtherCAT distributed clock, associating the PWM update time of the power drive stage with the bus synchronization reference. When multiple servo modules form a multi-axis system via EtherCAT bus, the power drive stage of each servo module can update the PWM output under the same distributed clock reference. It also enables a single servo module to compensate for the axis drive control quantity of its own module while driving the motor axis of its own module, in combination with the synchronization status of other servo modules. This is suitable for multi-axis synchronous applications such as gantry dual drive and robot multi-joint collaboration.

[0010] In some implementations, the first and second shared data areas are configured in a dual-port memory, and the control core and driver core access the dual-port memory through internal parallel data interfaces. This scheme enables the control core and driver core to access shared data in parallel, reducing the waiting time between control input writing and feedback input reading, which is beneficial for improving the servo closed-loop update speed.

[0011] In some implementations, the bus core is configured with a programmable logic device (PLD) integrating EtherCAT slave functionality. This PLD outputs a synchronization trigger signal based on the EtherCAT distributed clock, which is then transmitted to the PWM update terminal of the power drive stage via a hardware synchronization line. This approach avoids the synchronization signal remaining only at the communication protocol layer, ensuring that the PWM update terminal of the power drive stage is directly constrained by the distributed clock, thus improving the synchronization of drive outputs between modules.

[0012] In some implementations, the PWM update terminal of the power drive stage is equipped with a synchronous calibration circuit. This circuit calibrates the PWM update timing of the power drive stage based on a synchronous trigger signal. This solution can compensate for the update time difference between different servo modules caused by differences in line length, device response, or internal processing paths, making the actual drive output of multiple motor axes more consistent.

[0013] In some implementations, the control core acquires bus periodic jitter characteristics and mechanical periodic disturbance characteristics between the EtherCAT instruction cycle corresponding to the motion control data and the PWM update time of the power drive stage. Based on these characteristics, it compensates and updates the axis drive control quantities written to the first shared data area. This scheme can perform feedforward compensation for periodic disturbances before the drive stage output, reducing the impact of bus periodic jitter, gear meshing disturbances, or load cycle changes on motor axis following accuracy and multi-axis synchronization accuracy.

[0014] In some implementations, the power driver stage is configured with a hardware safety shutdown branch. This branch receives an EtherCAT safety communication timeout signal or an external safety input signal and cuts off the power transistor drive signal of the power driver stage based on the EtherCAT safety communication timeout signal or the external safety input signal. This solution can directly cut off the power drive output when safety communication fails or the external safety link is disconnected, shortening the safety response path.

[0015] In some implementations, the bus core is configured with a safety status mapping area. This area stores at least one of the following: safety shutdown trigger state, power drive stage over-temperature state, and power drive stage over-current state. It also maps at least one of these states to EtherCAT safety communication data. This solution enables the servo module's safety and fault states to be uploaded via EtherCAT safety communication data, facilitating unified monitoring by the upper-level safety control system.

[0016] This application also provides a multi-axis integrated drive and control servo system based on EtherCAT bus. The system includes at least two of the above-mentioned servo modules; each servo module corresponds to a motor axis, and the servo modules are connected via EtherCAT bus; the bus core of each servo module outputs a corresponding synchronous trigger signal based on the same EtherCAT distributed clock, so that the power drive stage of each servo module performs PWM update at the update time of the corresponding synchronous trigger signal.

[0017] Through the above system, multiple servo modules can drive multiple motor axes respectively. Each servo module completes the drive control and feedback closed loop of its own axis. At the same time, the EtherCAT distributed clock keeps the PWM update time of the drive level consistent, thereby improving the real-time performance and consistency of multi-axis synchronous drive.

[0018] This application also provides a multi-axis integrated drive and control servo control method based on EtherCAT bus. This method is applied to a multi-axis integrated drive and control servo system including at least two servo modules, each servo module corresponding to one motor axis. The method includes: Each servo module's bus core connects to the EtherCAT bus to receive motion control data and send it to the corresponding control core; The control core determines the shaft drive control quantity of the corresponding motor shaft based on the motion control data and writes the shaft drive control quantity into the first shared data area; The corresponding driver core reads the axis drive control quantity from the first shared data area and updates the PWM output of the corresponding power drive stage according to the axis drive control quantity; The second shared data area obtains and stores the motor feedback quantity corresponding to the motor shaft from the drive core; The control core reads the motor feedback quantity in the second shared data area and updates the shaft drive control quantity written in the first shared data area according to the motion control data and the motor feedback quantity; The bus core also receives synchronization status data from other servo modules. The control core determines the positional or synchronization deviation between the motor axis corresponding to this servo module and the motor axis corresponding to other servo modules based on the synchronization status data and the motor feedback, and updates the axis drive control quantity written to the first shared data area based on the positional or synchronization deviation. The bus core outputs a synchronous trigger signal to the driver core according to the EtherCAT distributed clock, so that the corresponding power driver stage performs PWM update at the update time corresponding to the synchronous trigger signal.

[0019] This method corresponds to the data flow and synchronization control logic of the servo module and the servo system, enabling each servo module to complete its own axis drive closed loop, and enabling the power drive stage of multiple servo modules to perform PWM updates under a unified clock reference. Attached Figure Description

[0020] Figure 1 This is a general block diagram of the servo module provided in the embodiments of this application; Figure 2 This is a schematic diagram of a multi-axis synchronization mechanism provided in an embodiment of this application; Figure 3 This is a schematic diagram of the internal shared storage structure provided in an embodiment of this application; Figure 4 This is a schematic diagram of the hardware security shutdown and secure communication process provided in the embodiments of this application; Figure 5 A flowchart of the control method provided in the embodiments of this application.

[0021] Explanation of reference numerals in the attached figures: 10. Multi-axis integrated drive and control servo system; 100. Servo module; 110. Bus core; 111. Programmable logic device with integrated EtherCAT slave function; 120. Control core; 130. Shared memory unit; 131. First shared data area; 132. Second shared data area; 140. Drive core; 141. Power drive stage; 142. PWM update terminal; 143. Hardware safety shutdown branch; 144. Synchronization calibration circuit; 150. Motor shaft; 151. Motor; 152. Encoder; 160. EtherCAT bus; 170. Non-volatile memory; 180. Safety status mapping area; 190. External safety input terminal; 200. Upper controller. Detailed Implementation

[0022] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.

[0023] The terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0024] In this document, references to embodiments indicate that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a mutually exclusive, independent, or alternative embodiment. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0025] The technical solution of this application will be described below with reference to the accompanying drawings. The following embodiments are used to illustrate the cooperation relationship between various technical features in the servo module, servo system, and control method, and do not limit the specific chip model, memory type, power device type, or control algorithm form of each component. Under the condition of satisfying the same data flow relationship and synchronous update relationship, the control core can be implemented using an FPGA, SoC, multi-core processor, digital signal processor, or a combination thereof; the drive core can be implemented using an intelligent power module, discrete power device drive circuit, or other power stage structure capable of outputting PWM drive signals; the bus core is implemented using a programmable logic device with integrated EtherCAT slave function. It should be noted that existing common EtherCAT slave controllers only receive or send data from their own slaves and do not parse information from other slaves. Therefore, the bus core in the following embodiments uses a programmable logic device with integrated EtherCAT slave function to realize its function of parsing data from other axes that require synchronization.

[0026] EtherCAT is a real-time communication bus based on industrial Ethernet, which can periodically transmit process data between a master station and multiple slave stations. EtherCAT distributed clock refers to multiple slave stations performing local time calibration based on a unified clock reference, enabling different slave stations to perform synchronous actions at predetermined times. In this application, the EtherCAT distributed clock not only serves as a communication synchronization basis but is also further converted into a synchronization trigger signal acting on the drive core, allowing the power drive stage to update the PWM output under the same clock reference. PWM stands for Pulse Width Modulation. The power drive stage controls the on / off state of the power transistor by updating the PWM duty cycle, phase, or switching state, thereby outputting voltage or current corresponding to the shaft drive control quantity to the motor 151.

[0027] like Figure 1 As shown, in the first embodiment, the servo module 100 includes a bus core 110, a control core 120, a shared memory unit 130, and a drive core 140. The servo module 100 is an axis control unit in the multi-axis integrated servo system 10. Each servo module 100 corresponds to a motor axis 150 and drives a motor 151 through its power drive stage 141. Multiple servo modules 100 are connected via an EtherCAT bus 160 to form the multi-axis integrated servo system 10.

[0028] Bus core 110 connects to EtherCAT bus 160, receives motion control data from EtherCAT bus 160, and sends the motion control data to control core 120. The motion control data may include target position, target speed, target torque, interpolation segment parameters, electronic gear parameters, synchronous motion commands, start / stop commands, operating mode commands, or other data related to the motion of motor shaft 150 sent by the host controller 200. Motion control data is the external input source for control core 120 to determine the shaft drive control quantities. Bus core 110 can also receive synchronization status data from other servo modules 100 via EtherCAT bus 160, or upload its own synchronization status data to other servo modules 100.

[0029] The control core 120 is responsible for motion control data parsing, trajectory calculation, servo closed-loop update, and synchronization compensation processing. Based on the motion control data, the control core 120 determines the axis drive control quantity for the corresponding motor axis 150 and writes it into the first shared data area 131 of the shared storage unit 130. The axis drive control quantity is the data upon which the drive core 140 generates or updates the PWM output, and can be a position setpoint, speed setpoint, torque setpoint, current setpoint, PWM comparison value, compensation control quantity, or a combination of the above. For example, in position control mode, the axis drive control quantity may include the position loop output and the speed setpoint; in torque control mode, the axis drive control quantity may include the torque setpoint or the current setpoint; in current loop direct control mode, the axis drive control quantity may include the current loop control result used to determine the PWM duty cycle.

[0030] The shared storage unit 130 includes a first shared data area 131 and a second shared data area 132. The first shared data area 131 is for data transfer from the control core 120 to the drive core 140, and mainly stores axis drive control quantities; the second shared data area 132 is for data transfer from the drive core 140 to the control core 120, and mainly stores motor feedback quantities. By having the first shared data area 131 and the second shared data area 132 handle data transfer in two directions respectively, cross-over between control data and feedback data in the same cache area can be avoided, facilitating data access by the control core 120 and the drive core 140 according to a defined read / write direction.

[0031] The drive core 140 includes a power drive stage 141. The power drive stage 141 corresponds to a motor shaft 150 and controls the motor 151's operation via a power transistor drive signal. The drive core 140 reads the shaft drive control quantity from the first shared data area 131 and updates the PWM output of the power drive stage 141 according to the shaft drive control quantity. The power drive stage 141 drives the motor 151 according to the PWM output, causing the motor 151 to run according to the target trajectory, target speed, or target torque corresponding to the motion control data.

[0032] The second shared data area 132 acquires and stores the motor feedback quantities of the motor shaft 150 from the drive core 140. The motor feedback quantities may include encoder position feedback, motor speed feedback, current feedback, bus voltage feedback, power stage temperature feedback, position error feedback, alarm status, or operating status. The encoder 152 can collect position data from the motor 151 or the load side, the current sampling circuit can collect motor phase current or bus current, and the temperature detection circuit can collect the temperature of power devices or motor windings. After the drive core 140 writes the above feedback data into the second shared data area 132, the control core 120 reads the motor feedback quantities from the second shared data area 132 and updates the shaft drive control quantities written to the first shared data area 131 based on the motion control data and the motor feedback quantities.

[0033] Through the aforementioned data flow, a single servo module 100 internally forms a workflow of motion control data input—axis drive control quantity writing—PWM output update—motor feedback quantity write-back—axis drive control quantity update again. The control core 120 and drive core 140 complete internal data interaction through a shared storage unit 130, which reduces external communication link transmission delay and protocol conversion delay. After multiple servo modules 100 are connected into a system, each servo module 100 completes its own axis closed-loop control and synchronously updates the PWM output of the power drive stage 141 under the EtherCAT distributed clock reference.

[0034] like Figure 3 As shown, the first shared data area 131 can be configured with a control quantity storage area, a cycle number area, a data validity flag area, and a verification area. The second shared data area 132 can be configured with a feedback quantity storage area, a sampling timestamp area, a feedback validity flag area, and a status area. The control core 120 writes the axis drive control quantity into the first shared data area 131 according to the control cycle, and the drive core 140 reads the corresponding data according to the PWM update cycle. The drive core 140 writes the motor feedback quantity into the second shared data area 132 according to the sampling cycle, and the control core 120 reads the corresponding data according to the servo closed-loop cycle. The data validity flag indicates whether the corresponding data has been completely written, the cycle number distinguishes data from different control cycles, and the verification area identifies data transmission or access anomalies. This data organization method avoids the control core 120 reading incompletely updated feedback data and also prevents the drive core 140 from reading mixed control data across cycles.

[0035] In some embodiments, the shared memory unit 130 employs a dual-port memory. The dual-port memory has two independent access ports, and the control core 120 and driver core 140 access the dual-port memory through their respective internal parallel data interfaces. When using a dual-port memory, the operations of the control core 120 writing to the first shared data area 131 and reading from the second shared data area 132 can be performed in parallel with the operations of the driver core 140 reading from the first shared data area 131 and writing to the second shared data area 132, thereby reducing access conflicts. The internal parallel data interface can be an on-chip parallel bus, an FPGA internal bus, a processor local bus, or other low-latency parallel access interfaces. Compared to transmitting control and feedback quantities between the controller and independent drivers via external communication protocols, the above-described shared memory structure shortens the data path, which is beneficial for improving the servo closed-loop update speed.

[0036] like Figure 2 As shown, in the second embodiment, the multi-axis integrated drive and control servo system includes at least two servo modules 100. Each servo module 100 corresponds to a motor shaft 150 and is connected via an EtherCAT bus 160. The bus core 110 of each servo module 100 outputs a corresponding synchronous trigger signal based on the same EtherCAT distributed clock, enabling the power drive stage 141 of each servo module 100 to perform PWM updates at the update time of the corresponding synchronous trigger signal.

[0037] In this system, the host controller 200 can act as an EtherCAT master, and multiple servo modules 100 can act as EtherCAT slaves. The host controller 200 periodically sends motion control data to each servo module 100, and each servo module 100 controls its own motor shaft 150 according to the corresponding motion control data. The EtherCAT distributed clock provides a unified time reference for each servo module 100. The bus core 110 of each servo module 100 generates a synchronization trigger signal for its own module according to this time reference. When the synchronization trigger signal arrives, the drive core 140 loads the prepared PWM output data, so that the power drive stage 141 of its own module takes effect at a predetermined update time.

[0038] This synchronization mechanism enables the distributed clock of the communication layer to further influence the PWM update terminal 142 of the power drive stage 141. For multi-axis systems, even if the internal processing time of each servo module 100 for receiving motion control data differs, as long as each power drive stage 141 loads a new PWM output at the update time corresponding to the synchronization trigger signal, the phase deviation of the drive output between different motor axes 150 can be reduced.

[0039] In some embodiments, a programmable logic device 111 with integrated EtherCAT slave functionality is configured in the bus core 110. The programmable logic device 111 with integrated EtherCAT slave functionality outputs a synchronization trigger signal according to the EtherCAT distributed clock. The synchronization trigger signal is transmitted to the PWM update terminal 142 of the power drive stage 141 via a hardware synchronization line. The PWM update terminal 142 is the interface for the power drive stage 141 to receive update triggers. After receiving the synchronization trigger signal, the power drive stage 141 loads the prepared PWM duty cycle, phase, or switching control data into the PWM output register, making the power transistor drive signal effective at the update time.

[0040] In some embodiments, the PWM update terminal 142 of the power drive stage 141 is configured with a synchronization calibration circuit 144. The synchronization calibration circuit 144 may include a programmable delay unit, a phase adjustment unit, a latch, a counter, or a timestamp comparison unit. The synchronization calibration circuit 144 calibrates the PWM update time of the power drive stage 141 according to the synchronization trigger signal. For example, during the initialization phase, the system can measure the response delay between receiving the synchronization trigger signal and the actual change in the PWM output of each servo module 100, and write this response delay into the calibration parameter area. During operation, the synchronization calibration circuit 144 triggers the PWM update of the power drive stage 141 earlier or later according to the calibration parameters, keeping the actual update time difference between different servo modules 100 within a preset range. This scheme can compensate for line propagation delay, power drive chip response differences, and logic path differences, further improving multi-axis drive synchronization.

[0041] In the third embodiment, the control core 120 acquires bus periodic jitter characteristics and mechanical periodic disturbance characteristics between the EtherCAT command cycle corresponding to the motion control data and the PWM update time of the power drive stage 141, and compensates and updates the axis drive control quantity written to the first shared data area 131 based on the bus periodic jitter characteristics and mechanical periodic disturbance characteristics. The EtherCAT command cycle refers to the cycle in which the master station periodically sends motion control data, and the PWM update time is the time when the power drive stage 141 loads the new PWM output. In high-speed servo control, the bus command cycle is usually greater than or equal to multiple PWM update cycles. Therefore, between two bus commands, the control core 120 can use existing feedback data and disturbance characteristics to compensate the axis drive control quantity.

[0042] The periodic jitter characteristics of the bus can be determined based on the arrival time, timestamp deviation, or deviation of the synchronization trigger signal relative to the data reception time of motion control data within multiple bus cycles. The mechanical periodic disturbance characteristics can be determined based on position errors, speed fluctuations, current fluctuations, or vibration information in the motor feedback. For example, in gear drives, lead screw drives, or synchronous belt drives, gear meshing errors, lead screw periodic errors, or belt drive elasticity changes may manifest as periodic position errors or current fluctuations. Control core 120 can perform frequency domain analysis on the position error sequence, current fluctuation sequence, or speed fluctuation sequence over a period of time, extract the disturbance frequency and amplitude corresponding to the mechanical structure cycle, and superimpose compensation control quantities onto the shaft drive control quantity in subsequent control cycles. Frequency domain analysis can be implemented using fast Fourier transform, or by moving average, harmonic estimation, lookup table compensation, or adaptive filtering.

[0043] This embodiment further addresses the impact of periodic bus jitter and mechanical periodic disturbances on motor shaft following accuracy and multi-axis synchronization accuracy. Since the shaft drive control quantity has been compensated for in conjunction with disturbance characteristics before being written into the first shared data area 131, the control quantity read by the drive core 140 can offset part of the periodic error in advance, making the motor drive corresponding to the PWM output closer to the desired trajectory.

[0044] In the fourth embodiment, the bus core 110 also receives synchronization status data from other servo modules 100. The control core 120 determines the position deviation or synchronization deviation between the motor shaft 150 corresponding to this servo module 100 and the motor shaft 150 corresponding to other servo modules 100 based on the synchronization status data and the motor feedback amount of this module, and updates the axis drive control amount written to the first shared data area 131 based on the position deviation or synchronization deviation.

[0045] Specifically, the master station needs to configure which axes the axis should synchronize with before control, so that the bus core can extract the synchronization status data of other slave stations from the EtherCAT frame. After configuration, once the master station has completed the control algorithm calculation for each axis, it packages the target position, target speed, target torque, and synchronization control flags of all synchronized axes into an EtherCAT datagram and broadcasts it to all slave stations within one communication cycle. After receiving the data frame, each bus core automatically performs frame parsing, address matching, and FMMU mapping through hardware, and writes the corresponding process data into the control core.

[0046] For example, in a dual-drive gantry application, the multi-axis drive-control integrated servo system may include two servo modules 100. One servo module 100 drives the left motor of the gantry beam, and the other servo module 100 drives the right motor of the gantry beam. The two servo modules 100 exchange synchronization status data via an EtherCAT bus 160. The synchronization status data may include position count values, speed status, synchronization timestamps, deviation status, or running status. The control core 120 of each servo module 100 can determine the position deviation or synchronization deviation between the two motor shafts 150 based on the feedback from its own motor and the synchronization status data of the other servo module 100. When the left motor shaft lags behind the right motor shaft, the control core 120 of the left servo module 100 can increase the compensation control amount in the axis drive control amount of its own module; when the left motor shaft leads the right motor shaft, the control core 120 of the left servo module 100 can decrease the axis drive control amount of its own module or adjust the speed setpoint. In this way, the deviation of the gantry structure, beam torsion, and mechanical wear can be reduced.

[0047] For example, in multi-joint robot applications, a multi-axis drive-control integrated servo system may include six servo modules 100, each driving a joint motor. The host controller 200 sends motion control data for the corresponding joint to each servo module 100 via an EtherCAT bus 160. Each servo module 100 updates its axis drive control quantity based on feedback from its joint motor and synchronously updates the PWM output under a distributed clock reference. For joints requiring coordinated motion, each servo module 100 can exchange synchronization status data via the EtherCAT bus 160, enabling the control core 120 to correct its axis drive control quantity based on the synchronization relationship between joints, thereby improving end-effector trajectory consistency.

[0048] In the fifth embodiment, as Figure 4 As shown, the power drive stage 141 is equipped with a hardware safety shutdown branch 143. The hardware safety shutdown branch 143 receives an EtherCAT safety communication timeout signal or an external safety input signal, and cuts off the power transistor drive signal of the power drive stage 141 according to the EtherCAT safety communication timeout signal or the external safety input signal. The external safety input signal can come from an emergency stop switch, safety door switch, light curtain, safety relay, or other safety input device, and the external safety input terminal 190 can serve as the access terminal for the corresponding safety signal. The EtherCAT safety communication timeout signal can be generated when the bus core 110 fails to receive valid safety communication data within a preset time.

[0049] The hardware safety shutdown branch 143 may include dual-channel safety logic, an isolated drive shutdown circuit, a gate drive disable circuit, or a power transistor drive enable control circuit. The dual-channel safety logic can detect the status of the two safety input channels separately. Only when both channels are in a safety-enabled state will the power drive stage 141 allow the output of the power transistor drive signal. When either safety input channel is disconnected, EtherCAT safety communication times out, or a safety fault is detected, the hardware safety shutdown branch 143 cuts off the power transistor drive signal, causing the motor 151 to lose its active output torque. Because this safety shutdown path acts directly on the power drive stage 141 and does not depend on the software calculation results of the control core 120, it can improve the determinism of the safety response.

[0050] Bus core 110 can be configured with a safety status mapping area 180. The safety status mapping area 180 stores at least one of the following (180-1, 180-2, 180-3…180-N): safety shutdown trigger state, power drive stage over-temperature state, and power drive stage over-current state. It also maps at least one of these states to EtherCAT safety communication data. The EtherCAT safety communication data can be carried using the Fail Safe over EtherCAT protocol. Fail Safe over EtherCAT is a communication mechanism used to transmit safety-related data over an EtherCAT network. It can transmit safety status information to the safety master station or upper-level safety controller in the form of safety messages. Through the safety status mapping area 180, the system can upload the hardware safety status and power fault status of the servo module 100 via bus core 110, enabling the upper-level system to promptly obtain the cause of the safety shutdown, the location of the over-temperature, or the path of the over-current, facilitating fault location and safety recovery.

[0051] Preferably, the servo module 100 can also be configured with a non-volatile memory 170. The non-volatile memory 170 can record at least one of the following during the operation of the motor shaft 150: current feedback, temperature feedback, vibration feedback, position error feedback, alarm events, and safety shutdown events. The control core 120 can generate maintenance warning information based on the historical operating data recorded in the non-volatile memory 170 and upload it through the bus core 110. For example, when the current feedback of a certain servo module 100 under the same load conditions continues to increase, or the position error feedback continues to increase within the same operating segment, the control core 120 can determine that the motor shaft 150 corresponding to the servo module 100 has a trend of bearing wear, increased mechanical resistance, or changing transmission clearance, and generate maintenance warning information. This scheme is beneficial for providing early maintenance reminders before equipment downtime occurs, but it is not a necessary condition for realizing integrated drive and control synchronous drive, and can be used as an extension configuration for intelligent diagnostic functions.

[0052] like Figure 5 As shown in the sixth embodiment, a multi-axis drive-control integrated servo control method based on EtherCAT bus is provided. Figure 5 It can be drawn as a flowchart, including the steps: S101. The bus core of each servo module is connected to the EtherCAT bus to receive motion control data and send it to the corresponding control core; S102. The control core determines the shaft drive control quantity of the corresponding motor shaft based on the motion control data, and writes the shaft drive control quantity into the first shared data area; S103. The corresponding driver core reads the axis drive control quantity in the first shared data area and updates the PWM output of the corresponding power drive stage according to the axis drive control quantity; S104. The second shared data area obtains and stores the motor feedback quantity corresponding to the motor shaft from the drive core; S105. The control core reads the motor feedback quantity in the second shared data area and updates the shaft drive control quantity written in the first shared data area according to the motion control data and the motor feedback quantity; S106. The bus core also receives synchronization status data from other servo modules. The control core determines the position deviation or synchronization deviation between the motor shaft corresponding to this servo module and the motor shaft corresponding to other servo modules based on the synchronization status data and the motor feedback amount, and updates the shaft drive control amount written to the first shared data area based on the position deviation or synchronization deviation. S107. The bus core outputs a synchronous trigger signal to the driver core according to the EtherCAT distributed clock, so that the corresponding power driver stage performs PWM update at the update time corresponding to the synchronous trigger signal.

[0053] This method is applied to a multi-axis integrated drive and control servo system including at least two servo modules 100, each servo module 100 corresponding to a motor axis 150.

[0054] Combination Figure 1-5 As shown, specifically, in step S101, each servo module 100 receives motion control data via its bus core 110 connected to the EtherCAT bus 160 and sends it to the corresponding control core 120. The motion control data can come from the EtherCAT master station, or from a host computer, PLC, or motion controller connected to the EtherCAT master station. This step allows external motion commands to enter each servo module 100.

[0055] In step S102, the control core 120 determines the shaft drive control quantity of the corresponding motor shaft 150 based on the motion control data and writes the shaft drive control quantity into the first shared data area 131. The control core 120 can calculate the shaft drive control quantity of the corresponding motor shaft 150 of this module based on the target position, target speed, trajectory segment parameters or synchronous motion commands in the motion control data, combined with the servo control algorithm.

[0056] In step S103, the axis drive control quantity in the first shared data area 131 is read by the corresponding drive core 140, and the PWM output of the corresponding power drive stage 141 is updated according to the axis drive control quantity. The drive core 140 can read the corresponding axis drive control quantity in each PWM control cycle and convert it into the PWM duty cycle, phase or switching control data of the power drive stage 141.

[0057] In step S104, the motor feedback quantity corresponding to the motor shaft 150 is obtained from the drive core 140 and stored through the second shared data area 132. The drive core 140 can obtain the motor feedback quantity from the encoder 152, the current sampling circuit, the temperature sampling circuit, or the fault detection circuit, and write the motor feedback quantity into the second shared data area 132.

[0058] In step S105, the control core 120 reads the motor feedback quantity from the second shared data area 132 and updates the axis drive control quantity written to the first shared data area 131 based on the motion control data and the motor feedback quantity. This step enables the control core 120 to perform closed-loop correction based on the current motion target and actual motor feedback. For example, the control core 120 can calculate the position error based on the target position and encoder position feedback, the speed error based on the target speed and speed feedback, and the current error based on the target current and current feedback, and then update the axis drive control quantity based on the above errors. For multi-axis synchronous scenarios, the control core 120 can also compensate and update the axis drive control quantity of this module based on the synchronization status data from other servo modules 100.

[0059] In step S106, the bus core 110 also receives synchronization status data from other servo modules. The control core determines the position deviation or synchronization deviation between the motor shaft corresponding to this servo module and the motor shaft corresponding to other servo modules based on the synchronization status data and the motor feedback amount, and updates the shaft drive control amount written to the first shared data area based on the position deviation or synchronization deviation.

[0060] In step S107, the bus core 110 outputs a synchronization trigger signal to the driver core 140 according to the EtherCAT distributed clock, causing the corresponding power driver stage 141 to perform PWM update at the update time corresponding to the synchronization trigger signal. This step can be executed in parallel with step S103, or it can be used as a trigger condition for PWM loading. The driver core 140 prepares the PWM output data to be updated before the synchronization trigger signal arrives, and loads it when the synchronization trigger signal arrives, so that the PWM update time of the power driver stages 141 of multiple servo modules 100 is constrained by the same EtherCAT distributed clock reference.

[0061] In the above method, steps S101 to S107 can be executed cyclically. In each cycle, motion control data enters the control core 120 via the bus core 110. The control core 120 updates the axis drive control quantity, and the drive core 140 drives the motor 151 according to the axis drive control quantity. The motor feedback quantity returns to the control core 120 via the second shared data area 132, and the control core 120 then performs closed-loop correction based on the motor feedback quantity. The synchronous trigger signal constrains the PWM update time of the power drive stage 141 in each cycle, ensuring that the multiple motor axes 150 corresponding to the multiple servo modules 100 maintain synchronous output.

[0062] In practical applications, the control cycle, feedback sampling cycle, PWM update cycle, and EtherCAT communication cycle can be the same or different. For example, the EtherCAT communication cycle can be 250 microseconds, 500 microseconds, or 1 millisecond, the PWM update cycle can be several microseconds to tens of microseconds, and the control core 120 can perform one or more closed-loop updates within one EtherCAT communication cycle. The above cycle values ​​are only examples; the actual values ​​can be determined based on the motor type, power rating, control accuracy, and processor performance.

[0063] As can be seen from the above embodiments, the technical solution of this application uses a servo module 100 as the basic drive and control unit of a multi-axis servo system. Each servo module 100 corresponds to a motor axis 150, and bidirectional data interaction between the control core 120 and the drive core 140 is realized within the servo module 10 through a shared storage unit 130. Multiple servo modules 100 form a multi-axis integrated drive and control servo system 10 through an EtherCAT bus 160, and synchronously update the PWM output of the power drive stage 141 under the same EtherCAT distributed clock reference. This solution can reduce the communication delay and feedback data fragmentation problem between the controller and independent drivers in the traditional hierarchical architecture, and improve the real-time performance and consistency of multi-axis synchronous drive. Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0064] Those skilled in the art will readily understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. Those skilled in the art will also readily understand that the various embodiments of this application have different focuses, and for the sake of convenience and brevity, the same or similar parts may not be repeated in different embodiments. Therefore, parts not described or not described in detail in one embodiment can be referred to the descriptions in other embodiments.

[0065] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0066] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0067] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0068] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially as a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted through the computer-readable storage medium. The computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital versatile discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0069] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This program can be stored in a computer-readable storage medium, and when executed, it can include the processes described in the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

Claims

1. A multi-axis drive control integrated servo module based on EtherCAT bus, characterized in that, It includes a bus core, a control core, a shared memory unit, and a driver core; The bus core connects to the EtherCAT bus to receive motion control data and sends it to the control core; The shared storage unit includes a first shared data area and a second shared data area; The drive core includes a power drive stage, and the power drive stage corresponds to a motor shaft; The control core determines the axis drive control quantity to be written into the first shared data area based on the motion control data, and the drive core reads the axis drive control quantity in the first shared data area and updates the PWM output of the power drive stage based on the axis drive control quantity. The second shared data area obtains and stores the motor feedback amount of the motor shaft from the drive core. The control core reads the motor feedback amount in the second shared data area and updates the shaft drive control amount written in the first shared data area according to the motion control data and the motor feedback amount. The bus core outputs a synchronous trigger signal to the driver core according to the EtherCAT distributed clock, and the power driver stage performs PWM update at the update time corresponding to the synchronous trigger signal. The bus core also receives synchronization status data from other servo modules. The control core determines the positional deviation or synchronization deviation between the motor axis corresponding to this servo module and the motor axis corresponding to other servo modules based on the synchronization status data and the motor feedback, and updates the axis drive control quantity written to the first shared data area based on the positional deviation or synchronization deviation.

2. The multi-axis drive and control integrated servo module based on EtherCAT bus as described in claim 1, characterized in that, In the shared storage unit, the first shared data area and the second shared data area are configured in a dual-port memory, and the control core and the driver core access the dual-port memory through internal parallel data interfaces, respectively.

3. The multi-axis drive and control integrated servo module based on EtherCAT bus as described in claim 1, characterized in that, The bus core is configured with a programmable logic device that integrates EtherCAT slave functionality. The programmable logic device that integrates EtherCAT slave functionality outputs a synchronization trigger signal according to the EtherCAT distributed clock. The synchronization trigger signal is transmitted to the PWM update terminal of the power drive stage via a hardware synchronization line.

4. The multi-axis drive and control integrated servo module based on EtherCAT bus as described in claim 3, characterized in that, The PWM update terminal of the power drive stage is equipped with a synchronous calibration circuit, which calibrates the PWM update time of the power drive stage according to the synchronous trigger signal.

5. The multi-axis drive and control integrated servo module based on EtherCAT bus as described in claim 1, characterized in that, The control core acquires bus periodic jitter characteristics and mechanical periodic disturbance characteristics between the EtherCAT instruction cycle corresponding to the motion control data and the PWM update time of the power drive stage, and compensates and updates the axis drive control quantity written to the first shared data area based on the bus periodic jitter characteristics and the mechanical periodic disturbance characteristics.

6. The multi-axis drive and control integrated servo module based on EtherCAT bus as described in claim 1, characterized in that, The power drive stage is configured with a hardware safety shutdown branch, which receives an EtherCAT safety communication timeout signal or an external safety input signal, and cuts off the power transistor drive signal of the power drive stage according to the EtherCAT safety communication timeout signal or the external safety input signal.

7. The multi-axis drive and control integrated servo module based on EtherCAT bus as described in claim 6, characterized in that, The bus core is configured with a safety state mapping area, which stores at least one of the safety shutdown trigger state, power drive stage over-temperature state, and power drive stage over-current state, and maps at least one of the safety shutdown trigger state, the power drive stage over-temperature state, and the power drive stage over-current state to EtherCAT safety communication data.

8. A multi-axis integrated drive and control servo system based on EtherCAT bus, characterized in that, Includes at least two multi-axis integrated drive and control servo modules based on the EtherCAT bus as described in any one of claims 1 to 7; Each of the aforementioned servo modules corresponds to a motor shaft, and the servo modules are connected via an EtherCAT bus; The bus core of each servo module outputs a corresponding synchronous trigger signal based on the same EtherCAT distributed clock, so that the power drive stage of each servo module performs PWM update at the update time of the corresponding synchronous trigger signal.

9. A multi-axis drive-control integrated servo control method based on EtherCAT bus, characterized in that, The method, applied to a multi-axis integrated drive and control servo system comprising at least two servo modules, each servo module corresponding to a motor axis, includes: Each servo module's bus core is connected to the EtherCAT bus to receive motion control data and send it to the corresponding control core; The control core determines the shaft drive control quantity of the corresponding motor shaft based on the motion control data, and writes the shaft drive control quantity into the first shared data area; The corresponding driver core reads the axis drive control quantity from the first shared data area and updates the PWM output of the corresponding power drive stage according to the axis drive control quantity; The second shared data area obtains and stores the motor feedback quantity corresponding to the motor shaft from the drive core; The control core reads the motor feedback quantity in the second shared data area and updates the shaft drive control quantity written in the first shared data area according to the motion control data and the motor feedback quantity. The bus core also receives synchronization status data from other servo modules. The control core determines the positional deviation or synchronization deviation between the motor axis corresponding to this servo module and the motor axis corresponding to other servo modules based on the synchronization status data and the motor feedback, and updates the axis drive control quantity written to the first shared data area based on the positional deviation or synchronization deviation. The bus core outputs a synchronization trigger signal to the driver core according to the EtherCAT distributed clock, so that the corresponding power driver stage performs PWM update at the update time corresponding to the synchronization trigger signal.

Citation Information

Patent Citations

  • High-precision driving and control integrated servo system

    CN121541570A

  • Multi-Servo control system

    KR1020170045940A