- Posts: 2203
- Thank you received: 486
phillc54 wrote:
I didn't think it did and I have just tested it here and it works OK.Clive S wrote: If I understand correctly the array is saved to a different folder than the standard NGC one. I saved the file under a different name to the desktop and edited that, I then shut the PC down and restarted and checked that the G4P15 was in the file on the desktop and opened that file.
Does the PlasmaC purge the G4P15 from the code?
Please Log in or Create an account to join the conversation.
Clive S wrote:
phillc54 wrote:
I didn't think it did and I have just tested it here and it works OK.Clive S wrote: If I understand correctly the array is saved to a different folder than the standard NGC one. I saved the file under a different name to the desktop and edited that, I then shut the PC down and restarted and checked that the G4P15 was in the file on the desktop and opened that file.
Does the PlasmaC purge the G4P15 from the code?
Thanks for the feedback. I will go out and test again.
Please Log in or Create an account to join the conversation.
Yes, it only looks for spindle on signals and does it own thing.Clive S wrote: But I was using pierce only and it was that, that was getting rid of the G4
Please Log in or Create an account to join the conversation.
phillc54 wrote:
Yes, it only looks for spindle on signals and does it own thing.Clive S wrote: But I was using pierce only and it was that, that was getting rid of the G4
That also explains the G1 X 0.000001 you referred to before, LinuxCNC needs to have some motion otherwise it won't turn the torch on.
If you had saved the Pierce Only file then added the G4 codes in then loaded it and run it in Pierce and Cut mode it should work.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
phillc54 wrote: Have you tried a long Arc Fail timeout?
Please Log in or Create an account to join the conversation.