- Posts: 1630
- Thank you received: 595
Lathe macros - Facing bug?
- RotarySMP
- Topic Author
- Offline
- Platinum Member
-
Less
More
3 months 1 week ago #348055
by RotarySMP
Lathe macros - Facing bug? was created by RotarySMP
G'day all,
This is a question about Andy's lathe macros. I am getting a slight angle / coordinated facing angle although I set zero angle in the cut parameters.
Is this finger trouble on my part, or a possible bug?
Cheers,
Mark
This is a question about Andy's lathe macros. I am getting a slight angle / coordinated facing angle although I set zero angle in the cut parameters.
Is this finger trouble on my part, or a possible bug?
Cheers,
Mark
Please Log in or Create an account to join the conversation.
- andypugh
- Offline
- Moderator
-
Less
More
- Posts: 19311
- Thank you received: 4655
3 months 1 week ago #348071
by andypugh
Replied by andypugh on topic Lathe macros - Facing bug?
I don't know what is going on here.
Is it possible that you have modified the G-code to support angled facing?.
github.com/andypugh/LatheMacros/blob/Py3_GTK3/facing.ngc
Says that angled facing isn't supported, and there is no indication of the #6 input being used in the standard G-code.
Is it possible that you have modified the G-code to support angled facing?.
github.com/andypugh/LatheMacros/blob/Py3_GTK3/facing.ngc
Says that angled facing isn't supported, and there is no indication of the #6 input being used in the standard G-code.
The following user(s) said Thank You: RotarySMP
Please Log in or Create an account to join the conversation.
- RotarySMP
- Topic Author
- Offline
- Platinum Member
-
Less
More
- Posts: 1630
- Thank you received: 595
3 months 1 day ago #348342
by RotarySMP
Replied by RotarySMP on topic Lathe macros - Facing bug?
Hi Andy,
Sorry for the slow response. I dropped the ball on this as I was doing wood working .
This is the facing.ngc file I am using. I have not modified it at all. I just noticed I have both a "lathemacro.ini" and a "lathemacros.ini" (plural) in my machine directory. Could that be the issue?
Cheers,
Mark
Sorry for the slow response. I dropped the ball on this as I was doing wood working .
This is the facing.ngc file I am using. I have not modified it at all. I just noticed I have both a "lathemacro.ini" and a "lathemacros.ini" (plural) in my machine directory. Could that be the issue?
Cheers,
Mark
Please Log in or Create an account to join the conversation.
- Aciera
- Offline
- Administrator
-
Less
More
- Posts: 4819
- Thank you received: 2177
3 months 1 day ago - 3 months 1 day ago #348343
by Aciera
Replied by Aciera on topic Lathe macros - Facing bug?
I don't see anything in 'facing.ngc' that could cause a simultaneous move in X and Z.
Could you put a debug message inside of your 'facing.ngc' and run that macro again. Just to be sure that that is the actual file being executed (You should see a info message popup in the gmoccap gui).
Something like adding '(MSG, Executing facing.ngc)' to the start of the sub:
Could you put a debug message inside of your 'facing.ngc' and run that macro again. Just to be sure that that is the actual file being executed (You should see a info message popup in the gmoccap gui).
Something like adding '(MSG, Executing facing.ngc)' to the start of the sub:
Code:
;Facing
O<facing> sub
(MSG, Executing facing.ngc)
Last edit: 3 months 1 day ago by Aciera.
The following user(s) said Thank You: RotarySMP
Please Log in or Create an account to join the conversation.
- RotarySMP
- Topic Author
- Offline
- Platinum Member
-
Less
More
- Posts: 1630
- Thank you received: 595
3 months 1 day ago #348347
by RotarySMP
Replied by RotarySMP on topic Lathe macros - Facing bug?
Thanks. I added the message, which displayed, so that is the .ngc being loaded.
I had just run a facing cut which had a taper. Ran it after adding that msg, and had no taper. I will need to see what the error correlates with.
I had just run a facing cut which had a taper. Ran it after adding that msg, and had no taper. I will need to see what the error correlates with.
Please Log in or Create an account to join the conversation.
Time to create page: 0.061 seconds