G33.1 synchronized tapping problem
- spumco
- Offline
- Platinum Member
Less
More
- Posts: 1870
- Thank you received: 749
26 Jan 2025 02:59 #319865
by spumco
Replied by spumco on topic G33.1 synchronized tapping problem
Thanks for the troubleshooting suggestion.
Yes, same behavior, but much less Z-distance during the initial 'dive' than when using MDI.
Approximate position the Z-axis rapids to before synchronization while running a program:
G33.1 Z-0.5 K0.05 $0
(Starting at Z0.500")
Still don't think this behavior is right.
Yes, same behavior, but much less Z-distance during the initial 'dive' than when using MDI.
Approximate position the Z-axis rapids to before synchronization while running a program:
G33.1 Z-0.5 K0.05 $0
(Starting at Z0.500")
- 60rpm: 0.440"
- rapid dist: 0.060"
- 100rpm: 0.390"
- rapid dist: 0.110"
- 200rpm: 0.370"
- rapid dist: 0.130"
- 400rpm: 0.300"
- rapid dist: 0.200"
- 750rpm: 0.140"
- rapid dist: 0.360"
- 1000rpm: -0.125"
- rapid dist: 0.625"
Still don't think this behavior is right.
Please Log in or Create an account to join the conversation.
- spumco
- Offline
- Platinum Member
Less
More
- Posts: 1870
- Thank you received: 749
26 Jan 2025 03:13 #319867
by spumco
Replied by spumco on topic G33.1 synchronized tapping problem
Changing the Z-axis accel only slightly affected the rapid distance, if at all.
The earlier tests were done with MAX_VEL = 4, and MAX_ACCEL = 175.
Dropping down to MAX_ACCEL = 2 resulted in approximately the same pre-synch rapid distance at all speeds.
Much less violent rapids, of course.
The earlier tests were done with MAX_VEL = 4, and MAX_ACCEL = 175.
Dropping down to MAX_ACCEL = 2 resulted in approximately the same pre-synch rapid distance at all speeds.
Much less violent rapids, of course.
Please Log in or Create an account to join the conversation.
Time to create page: 0.051 seconds