开云体育

Derek:

Somethings lagging the GUI , thats for sure. Can't think of what though.

Art
www.artofcnc.ca

Yes, video could be the culprit. The screen switch should be very

fast at

this point. Mine are pretty much instant. I can't find a problem

which would

explain it except a lagging GUI. Is this at 25Khz?

Art
www.artofcnc.ca

it happens at 25khz and 35khz

Derek:

Yes, video could be the culprit. The screen switch should be very fast at
this point. Mine are pretty much instant. I can't find a problem which would
explain it except a lagging GUI. Is this at 25Khz?

Art
www.artofcnc.ca

--- In mach1mach2cnc@..., "morgtod" <todmorg@h...> wrote:

Tom -
I also forgot to mention, I also used the thc on& off to keep the
torch from hunting during the pierce dwell time. On thinner metal

it

doesn't make much differance, but on .375 an thicker the torch

would

dive towards the surface during the pierce dwell time and glops of
molten metal would stick to the torch head. In other words, I m03,
dwell, thcon and this gives a very smooth entry , even on very

short

cuts in thick metal. I'll change if you have a better way! :)
Todd

I seldom cut anything over .250 and mostly 10Ga. I normally do a
pierce at about .190 and the next command is a G00Z.135 to drive the
head into the cut. There is a certain amount of head oscillation
hunting for the perfect height but it never gets out of the critical
zone. It quickly adjusts as the cut starts.

I can see on thicker material where the hunting might be an issue.
The fix of the G28.1 will allow us to program when and where we re-
reference the Z axis. The only time I need to do it on my table is
when I am at the extremes of the material. I cut 2' X 2' or 2' X 3'
squares and I have a set of magnets setup to position the material
and hold it while I clamp it down with a bunch of hand squeeze clamps
(like large aligator clips). Even 10Ga will curl from stress relief
and uneven heating so the clamps keep everything fairly flat. I use
my CAM software to break the cuts down into logical groups and I try
to cut from the center out and somewhat even them out over the entire
design.

I was concerned about Art making program changes since my version
seems to be doing the auto Z axis reset on an M05. I have not
installed the last 5 or 6 RC's since none of them addressed any THC
issues.

TOM C

Derek
Here s what you do to fix your problem,
right click on "my computer" icon
left click on properties,
click on Advanced,
click on settings,
Then check on "adjust for best performance".
Let me know how it goes
Arturo

Hi Art
Well I turned off every thing I could and still have the same
problem. I'm thinking it's a video problem. I noticed that changing
from tab to tab on the GUI the screen changes are very slow.

Any thoughts on this?

Derek

Guys,
One of the plus's of using WinXP for Mach2 is that you can easily use
the USB PenDrives or USB Compact FlashDrives to replace floppies,
Just plug them in and WinXP knows what to do.
I develop Gcode on a laptop that doesnt have a floppy drive. Got
tired of burning CDs to transfer NC files, so a friend told me about
his PenDrive. On Ebay you can get them for anywhere from $15 on up
starting a 8meg to 128meg or more. I got a compact flash USB adapter
for a 128meg card I had laying around. Makes it easy to tranfer files
to the mill and plasma cutter.
-Lee

--- In mach1mach2cnc@..., Art <fenerty@a...> wrote:

No worries, I do not intend to require any change in code, I was

just

confused, because the unit was not rationalizing the DRO's when you

went to
snip-

Hi Art-
I found that if I do a oem124 between each thc on and off things
work just right. If you could tell me how to do this from a macro we
wouldn't have to change the program at all and risk causing problems
for others. A side note- rc10 overwrites my settings and macros also,
maybe its a win2k thing?

Tom -
I also forgot to mention, I also used the thc on& off to keep the
torch from hunting during the pierce dwell time. On thinner metal it
doesn't make much differance, but on .375 an thicker the torch would
dive towards the surface during the pierce dwell time and glops of
molten metal would stick to the torch head. In other words, I m03,
dwell, thcon and this gives a very smooth entry , even on very short
cuts in thick metal. I'll change if you have a better way! :)
Todd

Now BOTH of you have me confused. First to Todd: Why are you
turning the THC off and on during the moves? The THC

only "listens"

to UP and DOWN commands when the torch output is active (M03) AND

the

sync. Honestly, I don't run G28.1 in code since I only zero at the
beginning of a cut. I normally break my designs into 4 or 5

separate

g-code files that cut logical groups of vectors. I return to 0,0,1
at the end of each and can just load and go for the next cut or
decide to do a reference on X and Y or all three. Some of my

designs

have hundreds of individual cuts and the added G28.1 for Z each

time

would be a real waste of time.

snip-
Hi Tom-
The reason for the thcon and off was an atempt to make g28.1 work
correctly. I need the g28.1 on each pierce because the metal I use
has all been handled by forktruck, causing a a crown in the center.
With the speed of my table a G28.1 takes less than one second and
insures proper pierce height and no blowback into the torch. turning
the thc on and off did not help or hinder the g28.1 thing.
Todd

No worries, I do not intend to require any change in code, I was just
confused, because the unit was not rationalizing the DRO's when you went to
move back up. All I did was add a "auto-rationalize" into the spindle off
routine ( which I thought was there, but I can't find it). This should not
affect anythign else,but should allow the G28.1 to work if it is called ta
any time. Though it will require a test to see if it messes anything up, on
my end it looks OK, but if it messes up I'll remove the fix the same day.

Art
www.artofcnc.ca

--- In mach1mach2cnc@..., "morgtod" <todmorg@h...> wrote:

--- In mach1mach2cnc@..., Art <fenerty@a...> wrote:

HI TorchHeads...

Hi-
I did not know there was a way to zero the thc after a cut! I

use

macros in place of the m03 m05's so I can inset a zero very easily

(

as long as you tell me how ). On a related subject, the plasma dxf
import it would be very nice if I could make it call my m40 instead
of the default m03 and m41 in place of m05. A header and footer
would also be sweet( I use a m42 for my header and m43 for the
footer ).

I have traced the THC code and as I don't use THC, I am a bit

confused as

to the flow. When are you turning it on and when is it turned off

in your

programs. I think I see the problem and its related to turning

off

the THC.

It must be turned off and zeroed after a cut when the torch is

turned off

with the M5. Should I have it do this automatically on M3 (turn

on

THC) and

on M5(turn off the THC)? This may solve the problem but I don't

want to

screw up your flow.

Can't find the 2nd problem with the G0 to G1 difference. ..yet

anyway.

Art
www.artofcnc.ca

Now BOTH of you have me confused. First to Todd: Why are you
turning the THC off and on during the moves? The THC only "listens"
to UP and DOWN commands when the torch output is active (M03) AND the
TORCH ON input is active (from arc good). Any other time and the
signals are ignored in MACH2. On a M05 the Z axis is supposed
to "true up" so that the DRO matches the absolute position of the
head. I turn my THC on when I load the first g-code and leave it on
until I shut down the program. In the even the torch runs off the
material then the fault circuit in the THC hardware shuts off UP and
DOWN signals to MACH2.

To Art: Please don't fix something that is not broken. I have cut
miles of steel in the last two months and the THC works just fine as
long as you run the code with a G00 like the sample I sent. The
G28.1 problem may be interconnected with the THC but if the logic
works as we originally designed it, M05 should true up the Z and zero
out the THC move register. While it would be nice to have the THC
hold (waiting for TORCH ON) to work under ALL conditions, changing
the logic in the M03 and M05 section could cause things to get out of
sync. Honestly, I don't run G28.1 in code since I only zero at the
beginning of a cut. I normally break my designs into 4 or 5 separate
g-code files that cut logical groups of vectors. I return to 0,0,1
at the end of each and can just load and go for the next cut or
decide to do a reference on X and Y or all three. Some of my designs
have hundreds of individual cuts and the added G28.1 for Z each time
would be a real waste of time.

Todd:

This weekend coming I think, or earlier, but I have a few things in the
works so I need to finish them.

Thanks,
Art
www.artofcnc.ca

Thanks!
Once we get past this last little obstacle, the thc software and
tom's control board will be working at 100%. Any Idea how long 'till
the next release so I can try it out?
Todd
--- In mach1mach2cnc@..., Art <fenerty@a...> wrote:

Thanks Todd:

I think I have it fixed. I failed to sync the engine after the THC

run, so

whatever the correction was, was being added to the further

trajectories. It

SHOULD be fix, but we'll see what your tests show.

Thanks,
Art
www.artofcnc.ca

Thanks Todd:

I think I have it fixed. I failed to sync the engine after the THC run, so
whatever the correction was, was being added to the further trajectories. It
SHOULD be fix, but we'll see what your tests show.

Thanks,
Art
www.artofcnc.ca

--- In mach1mach2cnc@..., Art <fenerty@a...> wrote:

HI TorchHeads...

Hi-
I did not know there was a way to zero the thc after a cut! I use
macros in place of the m03 m05's so I can inset a zero very easily (
as long as you tell me how ). On a related subject, the plasma dxf
import it would be very nice if I could make it call my m40 instead
of the default m03 and m41 in place of m05. A header and footer
would also be sweet( I use a m42 for my header and m43 for the
footer ).

I have traced the THC code and as I don't use THC, I am a bit

confused as

to the flow. When are you turning it on and when is it turned off

in your

programs. I think I see the problem and its related to turning off

the THC.

It must be turned off and zeroed after a cut when the torch is

turned off

with the M5. Should I have it do this automatically on M3 (turn on

THC) and

on M5(turn off the THC)? This may solve the problem but I don't

want to

screw up your flow.

Can't find the 2nd problem with the G0 to G1 difference. ..yet

anyway.

Art
www.artofcnc.ca

--- In mach1mach2cnc@..., Art <fenerty@a...> wrote:

Todd:

I'm curious about something. Are you using an M5 prior to the

g28.1?

Art
www.artofcnc.ca

Hi-
Yes, at each pierce point I run a macro that g28.1z.1, g0z.25, m03
( torch on) , dwells, and does a thcon(). At the end of each cut
thcoff() m05, g0z1.
Todd

HI TorchHeads...

I have traced the THC code and as I don't use THC, I am a bit confused as
to the flow. When are you turning it on and when is it turned off in your
programs. I think I see the problem and its related to turning off the THC.
It must be turned off and zeroed after a cut when the torch is turned off
with the M5. Should I have it do this automatically on M3 (turn on THC) and
on M5(turn off the THC)? This may solve the problem but I don't want to
screw up your flow.

Can't find the 2nd problem with the G0 to G1 difference. ..yet anyway.

Art
www.artofcnc.ca

Todd:

I'm curious about something. Are you using an M5 prior to the g28.1?

Art
www.artofcnc.ca

I'm running a cnc router with Mach2 on a Compaq 1520, works fine.

Frank Carpenter