Author Topic: Custom NC pierce code not injected  (Read 418 times)

0 Members and 1 Guest are viewing this topic.

Offline JL-wshvacTopic starter

  • Full Member
  • ***
  • Posts: 71
  • Country: hk
  • Gender: Male
Custom NC pierce code not injected
« on: Apr 02, 2025, 23:13:36 PM »
Hi All,

I am wondering why the "pierce" code in my NC file is not injecting the same way as defined? In my tool the pierce defined should have 4 words but they are never being referenced in the NC file. Instead it only refers the "tool ON" and "tool OFF" instead. What did I do wrong?


Offline CAMeleon

  • Active Member
  • **
  • Posts: 36
  • Country: us
  • Gender: Male
Re: Custom NC pierce code not injected
« Reply #1 on: Apr 03, 2025, 14:10:25 PM »
Some controllers require a move/coordinate after your pierce call out. You might try manually adding the G00 above the Pierce all out in your SS.
Do you have pierce size in your tool setup? If so what is the value?
Garrett Tice

Offline JL-wshvacTopic starter

  • Full Member
  • ***
  • Posts: 71
  • Country: hk
  • Gender: Male
Re: Custom NC pierce code not injected
« Reply #2 on: Apr 03, 2025, 19:22:28 PM »
Hello Garrett,

Thank you for your information. Just to re-cap, I am trying to configure a custom NC setup and the current situation is the "pierce" action defined in the tool is not injected into the NC file at all. The NC codes of the specified pierce points in the opus will always use the "tool on" and "tool off" command for the NC code generation. I have confirmed this by replacing the "tool on" tool off" into different words just to differentiate between the action commands.

 As for the current pierce setting please refer to the attached images.


Offline CAMeleon

  • Active Member
  • **
  • Posts: 36
  • Country: us
  • Gender: Male
Re: Custom NC pierce code not injected
« Reply #3 on: Apr 10, 2025, 16:07:39 PM »
What is the size of the hole in your part? With a .050 pierce size, if the holes are .051, they will not pierce, they will burn.
Any hole with a value less than the pierce size entered will qualify for the pierce.
That is what I would first test. Make pierce size 1" for testing, put in a 1/2" hole, and see if your code changes.
Garrett Tice

Offline Darren Young

  • Premier Member
  • *****
  • Posts: 2128
  • Country: us
  • Gender: Male
    • BIM There Done That.
Re: Custom NC pierce code not injected
« Reply #4 on: Apr 16, 2025, 16:59:41 PM »
Haven't played with this for a long time.. but at one time... the Pierce section of the Custom NC didn't work in CAMduct at all. Literally would never be called. 

Sent it a support ticket for it over half a decade ago. Wouldn't surprise me if they never fixed it.

So unless someone has an example where their Pierce section of a Custom post IS called... I'd consider it broke.

That custom post UI is so buggy and limited, hardly anybody uses it unless they absolutely have to. And considering there's one one company that now that will produce a custom VPL, more and more are trying to use the Custom UI  as it can take months to even get a call with the Arkance folks. And then, they're a minimum of 3 months to produce a post, Given what I've heard and after talking with them, I have a hard time recommending them.

Offline Dave M

  • Full Member
  • ***
  • Posts: 99
  • Country: au
  • Gender: Male
    • DaveM AEC Consulting
Re: Custom NC pierce code not injected
« Reply #5 on: Apr 21, 2025, 11:54:37 AM »
Hi All,

I am wondering why the "pierce" code in my NC file is not injecting the same way as defined? In my tool the pierce defined should have 4 words but they are never being referenced in the NC file. Instead it only refers the "tool ON" and "tool OFF" instead. What did I do wrong?

If you are using the D6 PP with the Hypertherm Tool Options selected you should only see the Tool On / Tool Off followed by a G00 (move to next point) in your code. Providing you have a pierce size nominated in your tool config (I usually place this in the Globals section not details for materials then you should see a X (cross) in your path for each pierce.
The odd thing I see in your code is the feed rate as technically there is no 'feed' involved.