Tormach Post Processor WCS Probing Support

[Anonymous]

Hello Team

I have recently purchased a Passive probe for my PCNC770 and attempted to perform a WCS Probing routine in CAM on a XY Circular Hole.  Unfortunately when posting out this code the file posts with a XXXXX.nc.failed extension and further investigation reveals that the post is failing at the point of the WCS Code.  (See attached Screen Grab).

I may very well be doing something wrong in my CAM operations so would appreciate any guidance.

Thanks in advance!

Grant

[Anonymous]

If WCS probing is unsupported for the Tormach Post Processor is there anybody here that knows how to code this in.  Your assistance would be much appreciated.

I have attached a copy of the current Tormach Post Processor that I am using, if that helps?

Cheers

Grant

[RyanWeber]

I've been looking forward to the WCS probing on the Tormach post processor since fusion added the probing feature.  I'm surprised I have not heard more request on the forums, seem like being able to set up probing routines in the CAM would significantly save time and add versatility to what is currently available in pathpilot.    

[xNerdius.MaximusX]

Hi All,

I also have this same issue. With PathPilot on Tormach, I am unable to generate probing Gcode from the post-processor to auto find work coordinates. 

Is there a workaround with a generic post processor?

I also have access to a Tromach PCNC 440 and passive probe but would like to employ in process inspection. 

Would be very advantageous to add this functionality. Is this functionality that Autodesk would have to incorporate or Tormach would have to incorporate?

-MTL

[brettedwards_be]

hey guys i would like something  as well and i have some helpful stuff. path pilot uses some crazy probing code thats not G code !  with the manual in the probing area you can fined a lot of what you may need   has any one edited a post processor ? download link for path pilot .pdf

o<probe_pocket> sub

(probe to find center of circular or rectangular pocket)

#<x_start> = #5420 (Current X Location)
#<y_start> = #5421 (Current Y Location)

#<x_max> = [#<_ini[AXIS_0]MAX_LIMIT> - #5221 - .001] (5221 = G54 X Offset)
#<x_min> = [#<_ini[AXIS_0]MIN_LIMIT> - #5221 + .001]
#<y_max> = [#<_ini[AXIS_1]MAX_LIMIT> - #5222 - .001] (5222 = G54 Y Offset)
#<y_min> = [#<_ini[AXIS_1]MIN_LIMIT> - #5222 + .001]

#<feed_rate> = #1

F #<feed_rate>
G38.3 X #<x_max> (rough probe +X side of hole)
F [#<feed_rate>/30]
G38.5 X #<x_start> (finish probe)
#<x_plus>=#5061 (save results)
G0 X #<x_start> (return to start)

F #<feed_rate>
G38.3 X #<x_min> (probe -X side of hole)
F [#<feed_rate>/30]
G38.5 X #<x_start>
#<x_minus>=#5061 (save results)
G0 X #<x_start>
#<x_center> = [[#<x_plus>+#<x_minus>]/2]
G0 X #<x_center> (go to middle)

F #<feed_rate>
G38.3 Y #<y_max> (probe +Y side of hole)
F [#<feed_rate>/30]
G38.5 Y #<y_start>
#<y_plus>=#5062 (save results)
G0 Y #<y_start> (return to start)

F #<feed_rate>
G38.3 Y #<y_min> (probe -Y side of hole)
F [#<feed_rate>/30]
G38.5 Y #<y_start>
#<y_minus>=#5062 (save results)
G0 Y #<y_start>
#<y_center> = [[#<y_plus>+#<y_minus>]/2]
G0 Y #<y_center> (go to middle)

G10 L20 P1 X 0 Y 0 (set current location to zero)

F #<feed_rate> (restore original feed rate)

o<probe_pocket> endsub
M2

[xNerdius.MaximusX]

From what I recall, the # signifies a parametric variable that some sort of pre-processor converts into the actual gcode. 

If you look at gcode generated in pathpilot for conventional operations, it does the same thing. 

-M-

[SithechCustoms]

I recently converted a Renishaw MP-11, which is active, for Tormach use.  It would be awesome if we could probe from Fusion for sure.  Alright, so that's like 4 or 5 of us...don't hold our breath lol.

---

@Anonymous wrote:

Hello Team

I have recently purchased a Passive probe for my PCNC770 and attempted to perform a WCS Probing routine in CAM on a XY Circular Hole.  Unfortunately when posting out this code the file posts with a XXXXX.nc.failed extension and further investigation reveals that the post is failing at the point of the WCS Code.  (See attached Screen Grab).

I may very well be doing something wrong in my CAM operations so would appreciate any guidance.

Thanks in advance!

Grant

---

[Anonymous]

have any of you found more info on this?

[brettedwards_be]

i was told if you buy the new pathpilot they will give you a post that has probing in it don't know if that is true or not 

[Anonymous]

David Looms from XoomSpeed has successfully created probing routines for PathPilot (Big shout out and thanks to David!)  I have been using it with success for the past 6 months.  Here is the link to all the information and files:  

http://xoomspeed.com/CNC/FusionAutoProbing.htm

Kind regards

Grant

[Muzzerboy]

From my understanding, David Loomes' excellent post processor mods for PathPilot / LinuxCNC implement the "WCS probing" functions - these simply reset the WCS origin or axis to the probed position, so won't do much by way of part inspection. You need to have your WCS origin suitably positioned in the CAM setup at the point where you plan to do the probing and it simply corrects any error.

Note that the "in process / part inspection probing" is a paid-for extra in Fusion ("extension"). The associated credits are f expensive and have a short life. 

I don't know if David or anyone else is planning to go the next stage and attempt to implement the part inspection features in a PathPilot post but I doubt it, given the eye-watering cost of the Fusion extension (without which the feature is not available) vs the typical user base for Tormach machines.

[davidGLA8P]

Hi gents,

These days the post processor and the probing macros needed to support it are pre-installed in PathPilot.

Have a look in the files tab.  There's a folder called 'Fusion probing' or something similar that contains the post processor and some instructions on how to use it.  There's also a video I did at https://youtu.be/lMLcEQuZhDk that shows it all in action.

All the WCS probing routines are covered except those that deal with axis rotation.  The main reason they're missing is that PathPilot doesn't have UI functions to turn it off again, so you'd be stuck with your axes rotated forever more!

Adding the geometry and surface probing options isn't really on.  I can't justify paying all that money to Autodesk to enhance software I give away for free so that anyone who wants to use it can pay Autodesk another pile of money for the privilege.  Really not a very good business model that!