Every Shape past First fails to start(Solved) pierce delay

CrossFire ® PRO
1

I am using sheetcam with my crossfire Pro. I have a series of shapes. It cuts the first one fine, then on every subsequent shape, it goes down to touch the metal and then errors out. It says something about pierce delay being too short, (It never even seems to try to ignite the torch) but it asks if I want to retry, and then I choose “Generate” to modify the code from that line.

Then it works for that current shape and fails on the next. Lather rinse repeat. I am not sure what it could be. Is there something in the post that behaves differently from the first shape to the later shapes? I appreciate any insight the team here can provide.

Thanks,
Gumby

2

The pierce delay in your program is likely too short.

Try to increase the Pierce delay in the program to .5 seconds or more

5 Likes
3

Why does it work for the first cut?

4

The first pierce adds a millisecond to the delay. .5 or better, and try it. Also, make sure your plasma cutter is not on 4T. It should be on 2T

3 Likes
5

what is your PD set to now? I would start at .8 secs and work down .1 until is stops cutting consistently then add .1 to that and that’s your PD.

2 Likes
6

It will always work for the first cut, even if you set the delay to zero. I don’t know why, but Firecontrol makes the first delay longer than the rest.

The minimum recommended delay is .5 second, regardless of the plasma manufacturers recommendations.

3 Likes
7

Thank you everyone. I will try to find where to make that change.

I’ll follow up to close the thread if it works.

Cheers

8

Yes, I found the setting in the tool options and set it to .5 It actually seems long now for the thin material I am cutting, but I can experiment from here. Thank you again for the responses. Consider this thread done.

Happy New Year!
Gumby

2 Likes
9

Did it work, or did you just find the post-processor section?

1 Like
10

I’ve been able to go down to .4 reliably on thinner material. I tried .3, but it would throw an occasional error.

4 Likes
11

Yes, Problem solved. Thanks.

1 Like