Enormous C-Axis "unwind" on program start <Resolved>
Posted: Fri Jun 27, 2025 8:42 pm
I have an Avid 4x4 router with the Acorn based EX controller and Clearpath SDSK servo motors. A while ago I built a C-Axis add-on to use the machine as a tangential knife fabric cutter (documented here: viewtopic.php?t=11460). In short there is an additional clearpath servo that indexes the de-energized spindle via a timing belt to orient a spring loaded rotary knife. The homing macro was modified to spin the C-axis servo until a ferrous sensor flag trips a non-contact prox switch. This sets the C-axis machine coordinate to 0.00 degrees on completion.
The problem I am having is at the start of a program on initial machine start up. The way I have the fusion 360 post configured is to initially command a G0C0 move which, mysteriously, starts an enormous "unwind" of the C-axis to the tune of 65000 degrees. This isn't necessarily a "problem" per-se but the 30 seconds of spinning the rotary axis before the program starts is pretty silly and annoying. When the program actually starts after this ridiculous display everything seems to run perfectly fine. The same thing happens if I command any other angle via MDI right after machine start up. Calling M151/C also has no effect on this behavior.
My guess is there is some kind of parameter I have configured incorrectly here but I can't figure out what that is. I have attached a fresh report file for perusal.
The problem I am having is at the start of a program on initial machine start up. The way I have the fusion 360 post configured is to initially command a G0C0 move which, mysteriously, starts an enormous "unwind" of the C-axis to the tune of 65000 degrees. This isn't necessarily a "problem" per-se but the 30 seconds of spinning the rotary axis before the program starts is pretty silly and annoying. When the program actually starts after this ridiculous display everything seems to run perfectly fine. The same thing happens if I command any other angle via MDI right after machine start up. Calling M151/C also has no effect on this behavior.
My guess is there is some kind of parameter I have configured incorrectly here but I can't figure out what that is. I have attached a fresh report file for perusal.