The torch late after pierce

[Chennasami]

Hi
I am new . I have a problem with cut quality
the torch is diving at the start of cutting (after pierce). Is late 2 or 3s
I use the parameters indicated in the catalog hypertherm
( When i use height pierce = height cut no problem no late )
Help me to improve cut quality
Sorry for googletraduction English...

[acourtjester]

Are you using a Torch Height Control

[Chennasami]

Yes . I use THC proma

[Chennasami]

Hi
I am new . I have a problem with cut quality
the torch is diving at the start of cutting (after pierce). Is late 2 or 3s
I use the parameters indicated in the catalog hypertherm
( When i use height pierce = height cut no problem no late )
Help me to improve cut quality
Sorry for googletraduction English...

[acourtjester]

Ok you need a post processor that will delay the time where the THC starts to check the arc voltage. This allows the arc to stabilize at the cutting height before the THC starts to sample the arc voltage. If the THC samples the arc to soon it will cause the THC to dive, you need about 1 second of cutting time before the THC samples it.

[Greolt]

It sounds to that the OP may mean that the pierce delay is longer than intended "Is late 2 or 3s"

He is using a translator.

If so this can be caused by a number of different things.

The THC may have a setting to delay before issuing a "Ark OK"
The gcode produced by the CAM may introduce a longer than desired delay.
The control software may have a delay setting. I use UCCNC and it has its own delay setting.

[Chennasami]

I use sheetcam

[robertspark]

Are you using mach3/4/uccnc/linuxcnc/planetcnc/????

[Chennasami]

Are you using mach3/4/uccnc/linuxcnc/planetcnc/????

I use Mach3
When i use hypertherm parameters .

[robertspark]

Screenshot attached

[robertspark]

you may also be suffering from synchronous and non-synchronous G and M codes within Mach3

most gocodes are non-synchronous (i.e. they require motion to stop before they are implented) and then motion contines afterwards.

eg:

Code: Select all

N01 M3
N02 G01 X100 F1200
N03 M5
N04 G1 X200

At the end of line N2, motion will slow down to implement M5 and then speed up for N04

where as

Code: Select all

N01 M3
N02 G01 X100 F1200
N03 G1 X200

there is no slow down between N02 and N03

in Mach3 only M11 and M10 are synchronous motion and do not require a machine to slow down.

Code: Select all

N01 M3 M11
N02 G01 X100 F1200
N03 M10
N04 G1 X200
N05 M5

there will be no slow down between N02 and N04

So it is recommended that you use M11/M10 to turn the THC on and off within Mach3 but you need a motion controller (or parallel port) which CAN use M11 / M10 to turn off the "laser" output in sync with motion.

UCCNC has all of these built in and more synchronous motion codes