Heidenhain iTNC530 C-Axis Acceleration Issue

[Neil22B]

I'm hitting a snag with a new grinding application on our Heidenhain iTNC530 controlled machine, and I'm hoping someone here has some insights. We're getting an overload error on the C-Axis (rotary table) specifically when accelerating with a fully loaded table, even though the weight is well within the manufacturer's specs for the machine. If I manually slow down the acceleration or reduce the feedrate significantly, it goes away, but that's not a sustainable solution for production.

My first thought was to reduce the acceleration parameter for the C-axis. I've been trying to adjust MP1060.0 but the weird thing is, I've tried dropping the value all the way down to 0.05 and I see absolutely no change in the C-axis's acceleration behavior or the overload issue. Then I tried adjusting the MP1060 value for our A-axis and that immediately had a noticeable effect. The A-axis clearly accelerated much slower.

I'm wondering why the MP1060.x isn't making a difference for the C-axis. Is there another parameter I should be looking at for rotary axis acceleration limits? Any help or pointers would be greatly appreciated!

 

[GreenFlagMan]

I'm hitting a snag with a new grinding application on our Heidenhain iTNC530 controlled machine, and I'm hoping someone here has some insights. We're getting an overload error on the C-Axis (rotary table) specifically when accelerating with a fully loaded table, even though the weight is well within the manufacturer's specs for the machine. If I manually slow down the acceleration or reduce the feedrate significantly, it goes away, but that's not a sustainable solution for production.

My first thought was to reduce the acceleration parameter for the C-axis. I've been trying to adjust MP1060.0 but the weird thing is, I've tried dropping the value all the way down to 0.05 and I see absolutely no change in the C-axis's acceleration behavior or the overload issue. Then I tried adjusting the MP1060 value for our A-axis and that immediately had a noticeable effect. The A-axis clearly accelerated much slower.

I'm wondering why the MP1060.x isn't making a difference for the C-axis. Is there another parameter I should be looking at for rotary axis acceleration limits? Any help or pointers would be greatly appreciated!

It's super weird that MP1060.0 works fine for A but does nothing for C. I've seen similar stuff on other machines.

My gut feeling is that something else is actually the bottleneck for your C-axis, and MP1060 isn't the active limiting factor. This could be bcs there's a problem with the actual C-axis drive's current limit/ torque limit, or a mechanical issue under load. you probably need to check them

 

[IVGrbn]

I'm hitting a snag with a new grinding application on our Heidenhain iTNC530 controlled machine, and I'm hoping someone here has some insights. We're getting an overload error on the C-Axis (rotary table) specifically when accelerating with a fully loaded table, even though the weight is well within the manufacturer's specs for the machine. If I manually slow down the acceleration or reduce the feedrate significantly, it goes away, but that's not a sustainable solution for production.

My first thought was to reduce the acceleration parameter for the C-axis. I've been trying to adjust MP1060.0 but the weird thing is, I've tried dropping the value all the way down to 0.05 and I see absolutely no change in the C-axis's acceleration behavior or the overload issue. Then I tried adjusting the MP1060 value for our A-axis and that immediately had a noticeable effect. The A-axis clearly accelerated much slower.

I'm wondering why the MP1060.x isn't making a difference for the C-axis. Is there another parameter I should be looking at for rotary axis acceleration limits? Any help or pointers would be greatly appreciated!

Sounds tricky but it seems you're on the right track to investigate acceleration parameters! For rotary axes on iTNC530, sometimes the acceleration limits are also influenced by parameters related to the jerk limit or even the drive controller settings themselves, rather than just the general acceleration parameter. Have you checked MP1070.0 (jerk limit for C-axis) or any of the drive-specific parameters (like those in the MP7xxx range) for the C-axis drive? It's possible there's an overriding limit coming from the drive or a more general dynamic parameter. Also, double-check your machine's specific documentation for any unique parameters related to rotary table dynamics, as some manufacturers implement their own overlays!

 

[noseyposey]

It sounds like MP1060 isnt actually controlling your C-axis acceleration, likely because that axis is set up differently, its accel limit is probably coming from the servo drive or another parameter, not the control. That would explain why the A-axis reacts but the C-axis doesnt. I'd check how the C-axis is defined in the machine parameters, look for any axis-coupling or rotary table settings, and dig into the drive's own torque/accel limits or inertia settings. The fix might be in the drive config, not in MP1060.

 

[_nano_]

Since it only happens when the machine's working hard, it might be how the servo drive is set up, not just the CNC control. The drive could be hitting its limits for current or acceleration before the iTNC settings even matter.