CS-Lab Support Forum for CNC Community

Help to run this brand-new forum and stay with us.
Ask your questions, we are here to help!

ForumCSMIO/IP controllers and Software - discussion forum: CSMIO/IP with simCNC softwarehow does G53 work?

You need to log in to create posts and topics.

how does G53 work?

#1 · 9 November 2024, 10:23

Hello, how does G53 work in simcnc?
Unfortunately, I didn't find any further information in the documentaries.
The following situation:
(see sketch) I have several identical parts that are to be milled in a vice with a stop. This means that the zero point remains the same, including the rotation. To clamp the parts, I need to move to a parking position on my fixed portal so that I have free access. Then I should just press start again to mill the next part. Unfortunately, this doesn't work because the rotation is not canceled when I move to the parking position with G53. If I set a G69 before, it works, but that can't be the solution because then I have to re-measure each part.
Is this intended in simcnc or is it a bug?
Shouldn't G53 temporarily cancel all zero point shifts and rotations?

Uploaded files:

#2 · 12 November 2024, 08:26

Currently, the solution is that the G68 command rotates the entire coordinate system (program and machine)

In order for it to achieve its goal, it is enough that after the machining is done, you cancel the rotation of the coordinate system:

G21

G0 X0 Y0 z0

G68 R45

G1 X10 F3000

Y10

G69

G53 G0 X0 Y0

M30

This way when you run gcode again, the machine will repeat exactly what it did the first time.

#3 · 12 November 2024, 11:15

Are you serious? Sorry, but that can't be the solution that when I have measured my raw part/workpiece I have to write the rotation value into my gCode by hand so that I don't lose the value or so that it doesn't crash when I move to the tool changer in the program???
Will you adjust the G53 command in the next update? Okay as a temporary solution but definitely not a permanent solution...

#4 · 13 November 2024, 07:55

As I wrote, this is how it is currently resolved, which does not exclude that we will not change it. It's already in our system for software developers.

carbonkid has reacted to this post.

#5 · 13 November 2024, 12:44

Ah okay, then maybe I misunderstood. Then it's good that you're already aware of it. It's a safety-related issue and it would be great if you could change it with the next update.