Axis off position
- cndewitt
- Offline
- New Member
Less
More
- Posts: 4
- Thank you received: 0
23 Mar 2022 13:07 #238097
by cndewitt
Axis off position was created by cndewitt
I'm having an issue with my setup keeping in position. I noticed that when I move in slower G1 moves, everything seems to be ok. I can setup an indicator, move off of it and down the lathe and then come back to that position and it holds on the indicator. But when I introduced rapid moves, that went away.
1. I did some research and decided to lower the Max_Velocity, Default_Accelertaion and Max_Acceleration. This initially fixed my problem, although my motors are capable of much higher velocity and acceleration. At this point, I could take long (15") moves down the lathe in a slow G1 move and then Rapid G0 back to the original position and it would hold every time. I looped it so that it moved this way 40 times, and the indictor was never off position.
2. I then started running actual programs, that included long and short moves, both rapid and slow. Now we are seeing this issue again. One time I might see the original position off by .054", and then I can reset it and run the same exact program and see the position off by .032" the next time. It's always off, but it's never consistent with how much it is off.
3. I go back to step 1 and do the long moves down and back and everything works as it should.
My guess is that it has something to do with the ramp up and ramp down of the acceleration, but I'm not sure where to start on fixing this issue. Any help would be greatly appreciated.
1. I did some research and decided to lower the Max_Velocity, Default_Accelertaion and Max_Acceleration. This initially fixed my problem, although my motors are capable of much higher velocity and acceleration. At this point, I could take long (15") moves down the lathe in a slow G1 move and then Rapid G0 back to the original position and it would hold every time. I looped it so that it moved this way 40 times, and the indictor was never off position.
2. I then started running actual programs, that included long and short moves, both rapid and slow. Now we are seeing this issue again. One time I might see the original position off by .054", and then I can reset it and run the same exact program and see the position off by .032" the next time. It's always off, but it's never consistent with how much it is off.
3. I go back to step 1 and do the long moves down and back and everything works as it should.
My guess is that it has something to do with the ramp up and ramp down of the acceleration, but I'm not sure where to start on fixing this issue. Any help would be greatly appreciated.
Please Log in or Create an account to join the conversation.
- tommylight
- Away
- Moderator
Less
More
- Posts: 19479
- Thank you received: 6532
23 Mar 2022 13:30 #238100
by tommylight
Replied by tommylight on topic Axis off position
What version of LinuxCNC?
What drives? What current are they set to?
What motors and how they are attached to the machine?
Do you get latency warnings while using LinuxCNC?
What power supply?
What wiring from PC to drives?
In the mean time, set the step time and step space to at least 5000 in the ini file. I would try 15000 just to be sure.
What drives? What current are they set to?
What motors and how they are attached to the machine?
Do you get latency warnings while using LinuxCNC?
What power supply?
What wiring from PC to drives?
In the mean time, set the step time and step space to at least 5000 in the ini file. I would try 15000 just to be sure.
Please Log in or Create an account to join the conversation.
- cndewitt
- Offline
- New Member
Less
More
- Posts: 4
- Thank you received: 0
23 Mar 2022 13:50 #238104
by cndewitt
Replied by cndewitt on topic Axis off position
LinuxCNC 2.7.15
Pico Systems PWM Servo Amplifier
Servo Motors are original to the machine. The machine is a LeBlond Regal 24 servo shift that originally was controlled with the GE Mark Century Tape Drive/ NC system. Motors were originally fitted with resolvers that I used with the Pico System resolver converters. I thought the resolvers might be what was causing the issue so I replaced them with encoders. Same problem, so obviously not the resolvers.
No latency warning from LinuxCNC.
Power supply is also original to the machine. Control Systems Research, Inc. Model 675, 60 VDC output.
Running the Pico System Universal PWM controller between the PC and the drives.
Pico Systems PWM Servo Amplifier
Servo Motors are original to the machine. The machine is a LeBlond Regal 24 servo shift that originally was controlled with the GE Mark Century Tape Drive/ NC system. Motors were originally fitted with resolvers that I used with the Pico System resolver converters. I thought the resolvers might be what was causing the issue so I replaced them with encoders. Same problem, so obviously not the resolvers.
No latency warning from LinuxCNC.
Power supply is also original to the machine. Control Systems Research, Inc. Model 675, 60 VDC output.
Running the Pico System Universal PWM controller between the PC and the drives.
Please Log in or Create an account to join the conversation.
- scotth
- Away
- Elite Member
Less
More
- Posts: 220
- Thank you received: 52
23 Mar 2022 23:04 #238174
by scotth
Replied by scotth on topic Axis off position
I assume the encoders are mounted on the motor. If you have the same problem with the encoders and resolvers, then look for mechanical loss in the couplings or screw mounts or bearings. If the loop is closed and following error is returning to zero, then it almost has to be mechanical.
Please Log in or Create an account to join the conversation.
- andypugh
- Offline
- Moderator
Less
More
- Posts: 23170
- Thank you received: 4860
24 Mar 2022 21:17 #238272
by andypugh
I would definitely be looking for a slipping coupling somewhere.
Replied by andypugh on topic Axis off position
_Especially_ with Resolvers, which are absolute devices (though less so when converted to quadrature by the Pico boards)I assume the encoders are mounted on the motor. If you have the same problem with the encoders and resolvers, then look for mechanical loss in the couplings or screw mounts or bearings. If the loop is closed and following error is returning to zero, then it almost has to be mechanical.
I would definitely be looking for a slipping coupling somewhere.
Please Log in or Create an account to join the conversation.
Time to create page: 0.054 seconds