Punch Press Gcode
05 Jun 2017 14:30 #94094
by AElmasry
Replied by AElmasry on topic Punch Press Gcode
Is this the right place to ask my question? If not someone help please to find the appropriate section of this forum
Please Log in or Create an account to join the conversation.
05 Jun 2017 15:00 #94097
by andypugh
Replied by andypugh on topic Punch Press Gcode
It seems as good a place as any.
But I was away from LinuxCNC machines all weekend.
But I was away from LinuxCNC machines all weekend.
Please Log in or Create an account to join the conversation.
05 Jun 2017 18:02 #94114
by AElmasry
Replied by AElmasry on topic Punch Press Gcode
Thanks andypugh
Waiting for you to get back
Waiting for you to get back
Please Log in or Create an account to join the conversation.
05 Jun 2017 20:06 #94122
by andypugh
Replied by andypugh on topic Punch Press Gcode
I think that the trick is to include "modalgroup=1" in the REMAP line. Removing it certainly prevents remapping from working, despite the system stating that it will use the default of 1.
If you want to put the g11.ngc file in the config directory (which is where I think it belongs) then you should use:
You don't currently seem to be using the XY parameters. When you want to, you will need something like this to deal with the fact that X and Y are both optional;
I got in a bit of a tangle trying to see if G11 / g11 made a difference, and ended up with files of both names in both places,
But I figured that you would prefer to have the answer than have me spend an hour or so going through all possibilities.
REMAP = G11 modalgroup=1 argspec=xy ngc=G11If you want to put the g11.ngc file in the config directory (which is where I think it belongs) then you should use:
[RS274NGC]
SUBROUTINE_PATH = ./
REMAP = g11 modalgroup=1 argspec=xy ngc=g11You don't currently seem to be using the XY parameters. When you want to, you will need something like this to deal with the fact that X and Y are both optional;
O<g11> sub
(DEBUG, #<x> #<y>)
O100 IF [exists[#<x>]]
O101 IF [exists[#<y>]]
G1 X #<x> Y #<y>
O101 ELSE
G1 X #<x>
O101 ENDIF
O100 ELSEIF [exists[#<y>]]
G1 Y #<y>
O100 ENDIF
M64 P1
M66 P0 L3 Q100
M64 P1
O<g11> endsubI got in a bit of a tangle trying to see if G11 / g11 made a difference, and ended up with files of both names in both places,
But I figured that you would prefer to have the answer than have me spend an hour or so going through all possibilities.
The following user(s) said Thank You: AElmasry
Please Log in or Create an account to join the conversation.
05 Jun 2017 20:52 #94126
by AElmasry
Replied by AElmasry on topic Punch Press Gcode
Thanks andypugh 
I'll try and get back to you
I'll try and get back to you
Please Log in or Create an account to join the conversation.
06 Jun 2017 14:23 - 06 Jun 2017 14:24 #94165
by AElmasry
Replied by AElmasry on topic Punch Press Gcode
It show an error:
EOF in file (current executed ngc file)
Seeking o-word: o<g11> from line:0
I added your code before my gcode program and it worked very well.
Is this the right way to remap g11, put it's code inside every ngc file?
Note: it worked only with G11 not g11 in the REMAP =G11
EOF in file (current executed ngc file)
Seeking o-word: o<g11> from line:0
I added your code before my gcode program and it worked very well.
Is this the right way to remap g11, put it's code inside every ngc file?
Note: it worked only with G11 not g11 in the REMAP =G11
Last edit: 06 Jun 2017 14:24 by AElmasry.
Please Log in or Create an account to join the conversation.
06 Jun 2017 14:38 #94171
by andypugh
No, you should be able to put g11.ngc in the config directory, and then g11 is a new G-code.
Replied by andypugh on topic Punch Press Gcode
I added your code before my gcode program and it worked very well.
Is this the right way to remap g11, put it's code inside every ngc file?
No, you should be able to put g11.ngc in the config directory, and then g11 is a new G-code.
Please Log in or Create an account to join the conversation.
06 Jun 2017 15:03 #94174
by AElmasry
Replied by AElmasry on topic Punch Press Gcode
Ok, I'll check whats wrong.
I have another problem that sometimes the interpreter execuete next line before reach the desired position
For example
G11 x1500 y500
M64 p0 ( for punching)
Some times i get the punch at x1499 y500
Or x1500 y 499
How can i hold g1 or g11 till get exact position or not exceeding specific error ( 0.1 mm)
I have another problem that sometimes the interpreter execuete next line before reach the desired position
For example
G11 x1500 y500
M64 p0 ( for punching)
Some times i get the punch at x1499 y500
Or x1500 y 499
How can i hold g1 or g11 till get exact position or not exceeding specific error ( 0.1 mm)
Please Log in or Create an account to join the conversation.
- Todd Zuercher
-
- Offline
- Platinum Member
-
Less
More
- Posts: 5007
- Thank you received: 1441
06 Jun 2017 15:55 #94180
by Todd Zuercher
Replied by Todd Zuercher on topic Punch Press Gcode
Don't know if this is the answer, but is the machine set for G61.1 mode or the default G64 mode (or G61)?
Please Log in or Create an account to join the conversation.
- Todd Zuercher
-
- Offline
- Platinum Member
-
Less
More
- Posts: 5007
- Thank you received: 1441
06 Jun 2017 15:57 #94181
by Todd Zuercher
Replied by Todd Zuercher on topic Punch Press Gcode
Also if it is a servo, is the dro set to actual or commanded postion?
Please Log in or Create an account to join the conversation.
Time to create page: 0.107 seconds