QCad CAM
08 Nov 2013 04:47 #40644
by Sterling
That's weird. 
I tested it here first, honest. I don't know what could be the problem. My first thought would be something got corrupted between saving it, coping it to the flash drive then uploading...? (maybe I can download it and take a look-see...)
Anyway, I figured out a way to get what I needed acomplished and I've got the center pocket where I want. (Hooray!) So now it's time to tweak the paths and edges!
As always, many thanks for you help!! I hope to make some decent progress now in the next couple days (depends on how link it takes me to 'tweak' the hand-written code.)
I tested it here first, honest. I don't know what could be the problem. My first thought would be something got corrupted between saving it, coping it to the flash drive then uploading...? (maybe I can download it and take a look-see...)Anyway, I figured out a way to get what I needed acomplished and I've got the center pocket where I want. (Hooray!) So now it's time to tweak the paths and edges!
As always, many thanks for you help!! I hope to make some decent progress now in the next couple days (depends on how link it takes me to 'tweak' the hand-written code.)
Please Log in or Create an account to join the conversation.
09 Nov 2013 00:43 #40674
by BigJohnT
The following user(s) said Thank You: Sterling
Please Log in or Create an account to join the conversation.
09 Nov 2013 21:07 #40687
by BigJohnT
I assume this is for a plasma torch. I use a subroutine to touch off and fire the torch and pass the pierce height, pierce delay, cut height to the subroutine when I call it.
Doing a short test in QCad I drew the lead in then the shape then the lead out and QCad correctly followed the path. It would be a simple thing to add to the start a call to a subroutine I think.
JT
<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)
<touchoff> endsub
M2Doing a short test in QCad I drew the lead in then the shape then the lead out and QCad correctly followed the path. It would be a simple thing to add to the start a call to a subroutine I think.
JT
Please Log in or Create an account to join the conversation.
16 Nov 2013 06:06 #40845
by emcPT
I made this in 2006 (mach3), and still running.
I use a sensor with an offset in Y axis where it probes where the plate is, then it moves the cutting head to the same spot where the height was measured and apply a determined offset (normally depends on the material to cut).
It can be seen on the video how it behaves.
Also using QCad, with a small program that I wrote where the code is structured and includes the piercing, delay, delay between parts and so on.
I made this in 2006 (mach3), and still running.
I use a sensor with an offset in Y axis where it probes where the plate is, then it moves the cutting head to the same spot where the height was measured and apply a determined offset (normally depends on the material to cut).
It can be seen on the video how it behaves.
Also using QCad, with a small program that I wrote where the code is structured and includes the piercing, delay, delay between parts and so on.
Please Log in or Create an account to join the conversation.
16 Nov 2013 22:06 - 16 Nov 2013 22:10 #40865
by BigJohnT
I see on the QCad forum a guy has created a configuration that uses layer names for options and had tool diameter offset.
I'm working on a Plasma configuration at the moment.
Also you can change the order of entities to suit your cutter path in the property editor. While this works for drawings with a few entities it would be too hard if you have a drawing with a bunch of lines. If you draw your shape in QCad the entities are numbered as you draw them so you can have lead in and lead out and crossing paths.
JT
I'm working on a Plasma configuration at the moment.
Also you can change the order of entities to suit your cutter path in the property editor. While this works for drawings with a few entities it would be too hard if you have a drawing with a bunch of lines. If you draw your shape in QCad the entities are numbered as you draw them so you can have lead in and lead out and crossing paths.
JT
Last edit: 16 Nov 2013 22:10 by BigJohnT.
Please Log in or Create an account to join the conversation.
Moderators: Skullworks
Time to create page: 0.090 seconds