开云体育

Just jumping into this thread because it very topical - can anyone
recommend a msximum speed for my plasma cutting table - I'm in the
midst of assembling the electronics and designing the table.

By the "book" 16 gauge steel should be cut at 330 ipm (verse 3/8" at
35 ipm) and 1/16" aluminum at 550 ipm - this sounds extremely fast -
I was initially going to design for a max speed of 200 ipm - now
I've moved it up to 300 - 350 ipm.

I'm anxious to hear others' experiences - any suggestions.

Bob Jacoby
Florida




--- In mach1mach2cnc@..., Scot Cameron <scotxl@y...>
wrote:

Hi Tom,Thank you,I will play around with the settings
,I plan to lift the torch between cuts but have the
head floating,this will do for now as i learn more and
the THC kit becomes available,when you say contouring
is this constant contouring,if i want sharp pointsand
corners should i turn constant contouring off.
regards
Scot

--- caudlet <thom@t...> wrote:

--- In mach1mach2cnc@..., "scot"
<scotxl@y...> wrote:

Hi,I have just got my plasma machine running,I am

looking for some

help on cutting ramp speeds
Should i keep the ramp speed to the minimum the

motors can handle
so

the require cut speed is acheived quicker.
Thanks in advance
Scot
Uk

I don't think any changes in acceleration or
deceleration are needed
for torch cutting. Just set your machine for the
best performance.
Slower ramps means the machine will run smoother
(less jerkyness)
which is good for torch work. A plasma is not
exactly a precision
cutting machine and the flame trails behind the tip
to an extent. The
biggest challenge is to get consistant piercing and
constant torch
height above the material (unless you are using a
drag tip).

The most important thing is to have the conturing
feature enabled
to make the curves and shapes you cut nice and
smooth. I use between
70 and 80 IPM on 11Ga steel. I cut some 1/4" stock
the other day and
I got good results at 40IPM. This is with a 55A
torch and the Torch
Height Control running.

Tom C

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software

Hi Tom,Thank you,I will play around with the settings
,I plan to lift the torch between cuts but have the
head floating,this will do for now as i learn more and
the THC kit becomes available,when you say contouring
is this constant contouring,if i want sharp pointsand
corners should i turn constant contouring off.
regards
Scot

--- caudlet <thom@...> wrote:

--- In mach1mach2cnc@..., "scot"
<scotxl@y...> wrote:

Hi,I have just got my plasma machine running,I am

looking for some

help on cutting ramp speeds
Should i keep the ramp speed to the minimum the

motors can handle
so

the require cut speed is acheived quicker.
Thanks in advance
Scot
Uk

I don't think any changes in acceleration or
deceleration are needed
for torch cutting. Just set your machine for the
best performance.
Slower ramps means the machine will run smoother
(less jerkyness)
which is good for torch work. A plasma is not
exactly a precision
cutting machine and the flame trails behind the tip
to an extent. The
biggest challenge is to get consistant piercing and
constant torch
height above the material (unless you are using a
drag tip).

The most important thing is to have the conturing
feature enabled
to make the curves and shapes you cut nice and
smooth. I use between
70 and 80 IPM on 11Ga steel. I cut some 1/4" stock
the other day and
I got good results at 40IPM. This is with a 55A
torch and the Torch
Height Control running.

Tom C

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software

--- In mach1mach2cnc@..., "scot" <scotxl@y...> wrote:

Hi,I have just got my plasma machine running,I am looking for some
help on cutting ramp speeds
Should i keep the ramp speed to the minimum the motors can handle

so

the require cut speed is acheived quicker.
Thanks in advance
Scot
Uk

I don't think any changes in acceleration or deceleration are needed
for torch cutting. Just set your machine for the best performance.
Slower ramps means the machine will run smoother (less jerkyness)
which is good for torch work. A plasma is not exactly a precision
cutting machine and the flame trails behind the tip to an extent. The
biggest challenge is to get consistant piercing and constant torch
height above the material (unless you are using a drag tip).

The most important thing is to have the conturing feature enabled
to make the curves and shapes you cut nice and smooth. I use between
70 and 80 IPM on 11Ga steel. I cut some 1/4" stock the other day and
I got good results at 40IPM. This is with a 55A torch and the Torch
Height Control running.

Tom C

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

I have not yet gotten to the point that I know
the divisions can be set via SPI, but if they
can I will allow for that.

Rutex don't seem to have made the RT990H chip datasheet available,
even though it is refered to as the source of the SPI info.

The RT990A chip datasheet has a full list of SPI register addresses
and flags but I don't know if it is the same as the RT990H

Hi,I have just got my plasma machine running,I am looking for some
help on cutting ramp speeds
Should i keep the ramp speed to the minimum the motors can handle so
the require cut speed is acheived quicker.
Thanks in advance
Scot
Uk

evening,

i was wondering if mach1 / 2 is able to be interfaced to
potentiometers for controlling feed rates and bounceless
switches for controlling jog increments as well as axis
selection. this would resemble a bostomatic type controller
for anyone who knows those machines.

by the way, if you read this art, its nice to hear you had a
great time, and arrived back safely.

thanks in advance

jeff

oops,
I meant for the second g28.1 to be another g28.1z1.
Todd

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

Hi,
The problem with the g28.1 is repeatable, Run your z axis to 2",
type g28.1z1 in the mdi, manually trip your home switch, type g28.1
in the mdi, manually trip your home switch, this time it will rapid
back to 2" on the z. I dont know if this is the original 2" or if

it

is 2" up from tripping the switch, but something don't seem right.
Todd

One more quick question:
Is there a way to pas a variable in to the Gcode?

Example:
M6START
tool = GetSelectedTool()
x = GetToolChangeStart( 0 )
y = GetToolChangeStart( 1 )
z = GetToolChangeStart( 2 )
a = GetToolChangeStart( 3 )
b = GetToolChangeStart( 4 )
c = GetToolChangeStart( 5 )



SetCurrentTool( tool )

code "G00 G53 Z-.1"
code " G00 G59 P255"

M6END
x = GetToolChangeStart( 0 )
y = GetToolChangeStart( 1 )
z = GetToolChangeStart( 2 )
a = GetToolChangeStart( 3 )
b = GetToolChangeStart( 4 )
c = GetToolChangeStart( 5 )

StraightTraverse x, y, a, b, c

code "G43 H (Tool) " ; I don't think this will work


And then I can set the tool change location as 255


Thank you
Brian

Hi,
The problem with the g28.1 is repeatable, Run your z axis to 2",
type g28.1z1 in the mdi, manually trip your home switch, type g28.1
in the mdi, manually trip your home switch, this time it will rapid
back to 2" on the z. I dont know if this is the original 2" or if it
is 2" up from tripping the switch, but something don't seem right.
Todd

Art and list-at-large:
I am experiencing a slow down in performance at 35kHz (and incredible slow
down at 45kHz) in Mach 2 as compared to 25kHz. Can someone tell me what is
happening and how to remedy the situation. Running a 1.3 GHz machine
dedicated to Mach2 - nothing else running, use of Gecko 201's, and only
rapids of about 10mm/sec.
Also a couple of possible bugs:
- upon M30 reset, rewind all axes ok except X that does not reset properly
- variable speed of incremental jog, sometimes slow, sometimes same speed
as continuous.
Thanks in advance.

Tom Hess

Hi,
When I load my second or more g-code file, the extrema is
incorrect, the only way I have found to correct it is to restart
mach2. Regenerating the screen does not help. Any ideas?
Thanks
Todd

Thanks John,
Your method works perfect. code ("F100G1X1Y3")
Todd

--- In mach1mach2cnc@..., "japrenticeuk" <john@c...>
wrote:

--- In mach1mach2cnc@..., "Lee Studley"
<indigo_red@q...> wrote:

Sorry, I didnt mean any offense, just needed to de-murkify my

self:-)

That's very useful, is it mentioned in the docs and I missed it? -

Lee

In regards to the question, "Can
I execute G-Code in a macro, yes, I believe the command is

GCode

("G0X0") for example, but I will have to look this up...

Lee

I am sure no offence has been taken.

The function to execute G-code is documented in manual revision A2 -

sadly this is of little use to you as this revision also covers the
function key screen selection and XML profiles (as in Release
Candidate 7) but, as RC2.2 is still suggested for mainstream use, I
have not published it yet to avoid confusion!

The function as I have it is:
code (LPCTSTR block)
and will execute the commands in the string (VB script variable or
literal) that would be valid as an MDI line.
e.g. code ("F100G1X1Y3") in a macro will feed at 100 units per min
to 1,3

Thanks for your input I will definitely improve the explanations -
perhaps everyone should have somethink murky in their life

though ;=)

Best wishes

John Prentice

--- In mach1mach2cnc@..., "caudlet" <thom@t...> wrote:

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

wrote:

Hi,
Does the thc function alter the initial 0 z height, if I set my
0,0,0 and start the file my torch raise 1" rapids to the pierce

point

and the thc starts, when I call my next g0 z1 do I return to the
initial 1" or do I go 1" up from the present thc offset.
P.S. The THC control greatly improved the quality of my cuts,

this

is

really a cool hardware, software combo.
Todd

The THC simple keeps the Z updated with the actual height. If you
have it on and start cutting, let's say at .125 above the material
and the THC moves the head up and down during the cut, that

distance

is added or subtracted from the initial .125. It's basically like a
jog during the cut. Let's say the last position of the head prior

to

your M05 (torch off) was .187 then that is the number stored in the

Z

height register and on the DRO. A move to 1.00 would be absolute

so

if the read was at .187 it would move the difference. In the end

the

head should end up 1.00 above the zero point (I use the material
surface as Z zero).

One strangness that I have noticed (Art refuses to believe me) is
that PRIOR to running any g-code, a G28.1 X1Y1 reference move

rapids

to 1,1 and moves at reference speed to the home switchs and stops

at

0,0...just like when you hit the manual axis reference buttons.
After you have run a g-code program the same exact command results

in

a rapid run to 1,1 a slow run to home and a rapid back to 1,1 with
the DRO on 1.000X 1.000Y. It has something to do with table

offsets

I think, but I just wish it was the same all of the time. I do not
put in G28.1 in the code since the result can be different.

At this point I could not live without my THC. I am cutting a lot

of

steel and just the saving of tips makes it worth the price.

Tom C.

Hi Tom,
Thanks for the explanation on the offset function. You are correct
about the g28.1 functioning oddly, if I do a G28.1z1 my torch rapids
to 1", slowly lowers to the switch opening, and stops. The second
time I run it, it will referance the switch and then return to 1",
just like you explained it. This is keeping me from using the g28.1,
but I would like to use it to maintain accurate pierce height. Once
this small problem is cleared up I think it will be smooth sailing
with the thc. Is is fun to watch the torch glide over uneven metal
and just hover at 1/16", its just like magic!
Todd

Thank you that works GREAT and the G53 works too

Yup works fine on mine.. Save just the line

code "g0 g53 x6"

in a file called M60.m1s and call it from MDI with M60, the tool will move
to Machine coord X 6.

Thanks,
Art
www.artofcnc.ca

Actual code is without the paren's as in

code "G0X6"

This will execute a move to 6 in X, haven't tried G53 yet.

Thanks,
Art
www.artofcnc.ca

The function as I have it is:
code (LPCTSTR block)
and will execute the commands in the string (VB script variable or
literal) that would be valid as an MDI line.
e.g. code ("F100G1X1Y3") in a macro will feed at 100 units per min
to 1,3

I have been trying to get the g code to run in the macros as well and
have not been successful. I think I am doing it wrong ;o) … Is there
anyone having any luck getting it to work?? What I would like to do
is change the tool change macros (G00 G53 Z-.1).

Thank you
Brian

Will check it out...

Thanks,
Art
www.artofcnc.ca

Hi:

I have not yet gotten to the point that I know the divisions can be set via
SPI, but if they can I will allow for that.

Art
www.artofcnc.ca

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

I have decided to add a small SPI driver
section to the Mach2 driver for a graphical tuneup
for the RH990's.

Now that has made my day!. Excellent news Art. I presume that means
configuring the drive via SPI will be available? (eg, setting the
encoder division ratio)