I had a play with your job file using the post processor you supplied.
I generated the gcode file and got the same as the gcode file you supplied, where the probing code has mysteriously been omitted at the line you mentioned.
I did a "Save As" on your job file and deleted your drawing then imported a drawing with 5 separate shapes. Used the same tool and generated the gcode but this time all 5 sets of probing code appeared in the gcode.
Seems to me like a coding bug in the post processor so I had a look.
The only thing I can see that appears wrong is at line 129 in the post processor file where it says this:
firstRef = refDistance >=0
I've done a little coding, and to me that statement is incorrect. The ">=" means "is greater than or equal to" and is normal used as a conditional check on a variable. However in this case it appears to be used incorrectly and I'm guessing this is "confusing" the post processor.
I think Les himself (Sheetcam creator) or the company that supplied your equipment, needs to look further into this to confirm whether I'm correct about this.
Sorry I can't be much more use than this.
The only other alternative is to use a different plasma post processor that will work with your equipment, but again if it's a custom designed system maybe you need to ask the manufacturer.
EDIT:
Had a bit more play with things. In the post processor at line 17 there is this code:
Code: Select all
--this is the distance between each torch reference in MILLIMETRES
--set it to -1 if you never want to reference
refDistance = 200
I changed that bottom line to:
refDistance = 1
When I generated the code after doing that, the probing was included.
So if you make the same modification in your post processor, hopefully your problem will be fixed.
Overall I think the post processor is not written correctly because if the torch is not doing the probing/reference moves before some pierces, then the gcode should be bringing the torch down to pierce height, and NOT firing the torch at Safe-Z height.
I looks like the post processor has simply been written to omit the referencing code if the torch has not moved at least the refDistance, but it's not as simple as that as you have found out.
I did more tests. I set refDistance at 3000 and had 4 objects only about 200mm apart. Therefore after the first reference/probe, there should not have been any more on the other 3 objects. However, the 2nd object did not have probing code, the 3rd object did have probing code, then the 4th object did not have probing code.
I set the refDistance back to 1 and all objects had the probing code.
Sorry to say it but the post processor seems to be written wrong and it has bugs in it.
Was this a cheap table ?