Plasma/Mesa Guru's
04 Apr 2011 12:30 #8474
by BigJohnT
Replied by BigJohnT on topic Re:Plasma/Mesa Guru's
One thing at a time. The wait for torch arc ok is done in g code. I call my touchoff file before starting cutting.
touchoff.ngc
The M66 line waits for 5 seconds for the Arc Ok then it runs anyway... I've been to lazy to make it abort.
This is my X trim file that I use to cut off a sheet in the X axis.
x-trim.ngc
When I get out to the shop I'll take a look at mine but I'm using the 5i20 so they are the same but different.
Which THCAD card are you using?
I hope Peter happens by and can comment on the connections to your 7i37TA
Are you sending the output of the THCAD to an encoder input on the 7i37TA?
John
touchoff.ngc
o<touchoff> sub
(#1 pierce height, #2 pierce delay, #3 cut height)
F10
G38.2 Z-1.75 (Probe to find the surface)
G91
G1 Z0.070 (Raise up to Z0)
G90
G92 Z0 (Set Z0)
G1 Z#1
M3 S1
M66 P0 L1 Q5 (Wait for Arc OK from Torch)
G4 P#2 (Pause for pierce delay)
F25
Z#3 (goto cut height)
o<touchoff> endsub
M2The M66 line waits for 5 seconds for the Arc Ok then it runs anyway... I've been to lazy to make it abort.
This is my X trim file that I use to cut off a sheet in the X axis.
x-trim.ngc
G20 (Units: Inches)
G40 (Cancel Cutter Comp)
G90 (Absolute Mode)
G64 P0.005 (Continuous mode + path tolerance)
G92 X0 Y0
o<touchoff> call [0.100] [0] [0.08] (Touchoff and start cutting)
F135
G1 X48.125
M5 (Torch Off)
G0 Z0.500
X0.000
G92.1 (Cancel offsets and set to zero)
G0 Z0
M2When I get out to the shop I'll take a look at mine but I'm using the 5i20 so they are the same but different.
Which THCAD card are you using?
I hope Peter happens by and can comment on the connections to your 7i37TA
Are you sending the output of the THCAD to an encoder input on the 7i37TA?
John
Please Log in or Create an account to join the conversation.
04 Apr 2011 13:31 #8477
by BigJohnT
Replied by BigJohnT on topic Re:Plasma/Mesa Guru's
The relevant portions of my plasma.hal file
John
# Torch Height Control
loadrt thc
addf thc servo-thread
...
# Touch Off
net torch-probe motion.probe-input <= parport.0.pin-13-in-not
# Set up the Encoder for the THC
setp hm2_5i20.0.encoder.00.counter-mode 1
net thc-vel-in hm2_5i20.0.encoder.00.velocity => thc.encoder-vel
setp thc.scale-offset 119000
setp thc.vel-scale 0.00037866834
# this might need to be increased
setp thc.correction-vel 0.0001
# spindle on starts the arc
net spindle-on motion.spindle-on => parport.0.pin-16-out
net spindle-on thc.torch-on
# starts the motion when the plasma arc has transfered to the work
net start-motion-input thc.arc-ok <= motion.digital-in-00 <= parport.0.pin-15-in
John
Please Log in or Create an account to join the conversation.
04 Apr 2011 14:47 #8487
by PCW
Replied by PCW on topic Re:Plasma/Mesa Guru's
A 7I37 will not work as a THCAD receiver, the 7I37 is too slow. The THCAD outputs frequencies from about 100 KHz to 1 MHz, but the 7I37 opto coupled inputs will not reliably read frequencies above a few KHz.. You _may_ be able to get it to work by setting the frequency divide option on the THCAD all the way up (/128 i think) but a better option would be to connect the THCAD to a 7I42TA (single ended, just FO+), or a differential receiver (spare encoder input on a 7I33 or 7I48 or RS-422 interface of some kind: 7I34,7I47,7I47S, 7I52, 7I52S.
Please Log in or Create an account to join the conversation.
04 Apr 2011 17:48 #8509
by austin.mn
Replied by austin.mn on topic Re:Plasma/Mesa Guru's
How do I change the encoder #0, pin A (input) , that is where I want the FO+ to go, I think.
I will need to put that on the 7i42TA which is on P4 of the 5i20.
Next.... I completely don't seem to get subroutines. Do I make the subroutine as a seperate file? what do I do with it. I tried making a file labeled touchoff.ngc and put your subroutine info in it, then put that into the same folder as the xtrim gcode file and I just get an error message "error on line 6 can't open <touchoff>
I tried to go through and read the subroutine wiki, but I couldn't make heads or tails of it.
I will need to put that on the 7i42TA which is on P4 of the 5i20.
Next.... I completely don't seem to get subroutines. Do I make the subroutine as a seperate file? what do I do with it. I tried making a file labeled touchoff.ngc and put your subroutine info in it, then put that into the same folder as the xtrim gcode file and I just get an error message "error on line 6 can't open <touchoff>
I tried to go through and read the subroutine wiki, but I couldn't make heads or tails of it.
Please Log in or Create an account to join the conversation.
04 Apr 2011 18:14 #8513
by andypugh
Replied by andypugh on topic Re:Plasma/Mesa Guru's
austin.mn wrote:
You should have a file called touchoff.ngc in your PROGRAM_PREFIX directory.
The file needs to contain:
O100<touchoff> SUB
{G-code here}
O100<touchoff> ENDSUB
M2
What do you mean by "change"? The pin allocations on the headers are set by the Mesa firmware, if that is what you mean. It is not easy to change them. What is currently plugged in to the header which contains the encoder pin you want?How do I change the encoder #0, pin A (input) , that is where I want the FO+ to go, I think.
Yes. It needs to have the same name as you are going to call it with, and it needs to be in the folder pointed to by the PROGRAM_PREFIX setting in your INI file. It also needs to contain a sub and an endsub.Next.... I completely don't seem to get subroutines. Do I make the subroutine as a seperate file?
what do I do with it. I tried making a file labeled touchoff.ngc and put your subroutine info in it, then put that into the same folder as the xtrim gcode file and I just get an error message "error on line 6 can't open <touchoff>
You should have a file called touchoff.ngc in your PROGRAM_PREFIX directory.
The file needs to contain:
O100<touchoff> SUB
{G-code here}
O100<touchoff> ENDSUB
M2
Please Log in or Create an account to join the conversation.
04 Apr 2011 18:17 #8514
by austin.mn
Replied by austin.mn on topic Re:Plasma/Mesa Guru's
forget about the subroutine issue. I just needed to change the folder that the ini file was pointing to. changed that to point to the correct folder and it seems to work.
I ran your xtrim file and it goes for the probe, I hit the momentary switch on my desk and then a few seconds later it takes off to start cutting.doesn't it need an arc ok signal before it will proceed to start traveling?
I ran your xtrim file and it goes for the probe, I hit the momentary switch on my desk and then a few seconds later it takes off to start cutting.doesn't it need an arc ok signal before it will proceed to start traveling?
Please Log in or Create an account to join the conversation.
04 Apr 2011 18:17 #8515
by BigJohnT
Replied by BigJohnT on topic Re:Plasma/Mesa Guru's
Please Log in or Create an account to join the conversation.
04 Apr 2011 18:19 #8516
by austin.mn
Replied by austin.mn on topic Re:Plasma/Mesa Guru's
can we just rename the pin that emc is looking for and use a gpio pin on the 7i42?
Please Log in or Create an account to join the conversation.
04 Apr 2011 18:20 #8517
by BigJohnT
Replied by BigJohnT on topic Re:Plasma/Mesa Guru's
As I stated in a previous reply it waits 5 seconds then goes. If it ain't lit off in 5 seconds I hit the stop button. The function of the M66 is to take off as soon as the arc ok comes in to reduce wear and tear on consumables just sitting still with the torch on is bad for the nozzle. You could make it wait longer if you like.
www.linuxcnc.org/docview/html/gcode_main...ec:M66-Input-Control
John
www.linuxcnc.org/docview/html/gcode_main...ec:M66-Input-Control
John
Please Log in or Create an account to join the conversation.
04 Apr 2011 20:06 #8527
by PCW
Replied by PCW on topic Re:Plasma/Mesa Guru's
What daughter cards do you current have connected? (and on which 5I20 connectors) It may be possibly to route the frequency output through on those. Also I can make a custom bitfile with the encoders moved around if thats the issue.
Please Log in or Create an account to join the conversation.
Time to create page: 0.221 seconds