- Posts: 12160
- Thank you received: 0
lathe moving in inverted direction while jogging direction is correct.
3 years 9 months ago #261933
by rodw
Replied by rodw on topic lathe moving in inverted direction while jogging direction is correct.
Not specific to lathes, but without touching off somewhere inside the machining envelope, there is insufficient room for the tool (eg to move the cutter to the surface) takes it out of bounds. This is where G54 touchoffs solve the problem. It is a breath of fresh air when you adopt a G54 strategy with touchoffs...
ref:
linuxcnc.org/docs/2.9/html/gcode/coordin...ha:coordinate-system
ref:
linuxcnc.org/docs/2.9/html/gcode/coordin...ha:coordinate-system
Please Log in to join the conversation.
- smc.collins
- Topic Author
- Offline
- Platinum Member
-
Less
More
- Posts: 721
- Thank you received: 0
3 years 9 months ago #261995
by smc.collins
Replied by smc.collins on topic lathe moving in inverted direction while jogging direction is correct.
for some reason g53 is being sent to 830 and 1150mm resepctively, for a unknown reason. I already have a email in with them about why this is ?
Please Log in to join the conversation.
3 years 9 months ago #262008
by JPL
Replied by JPL on topic lathe moving in inverted direction while jogging direction is correct.
You should have this or something similar in fusion 360:
From there you should be able to set 'safe retracts' to G53 or G28 (highlited blue line)
AND set the G53 X and Z home position
Attachment not found
From there you should be able to set 'safe retracts' to G53 or G28 (highlited blue line)
AND set the G53 X and Z home position
Please Log in to join the conversation.
- smc.collins
- Topic Author
- Offline
- Platinum Member
-
Less
More
- Posts: 721
- Thank you received: 0
3 years 9 months ago #262063
by smc.collins
Replied by smc.collins on topic lathe moving in inverted direction while jogging direction is correct.
yeah, I set them to zero and they still call out to max travel, I have a email in about it.
Please Log in to join the conversation.
Time to create page: 1.686 seconds
