I’m not certain the new path pilot version is to blame here but I’m having an issue with probing.
I use the xoomSpeed post processor thanks to its probing support (Fusion 360) to update work co-ordinates after I power up the machine. Even though it’s an MX machine I get 1-3 thousands offset after power on.
Basically I have 12 parts in a fixture each with its own WCS. The probing routing hits all the parts and updates these locations. This has worked perfectly until I updated path pilot. (I do have the most recent release installed)
I’m using Fusion 360 probing routing which starts with moving the probe over the part and it plunges (Z) then starts it’s probing routing.
When the routing switches from it’s fast move to probing I get a “Unexpected Contact with part error”.
I’ve slowed the machine to as slow as I can move it and the error still occurs at the same spot. I raised the distance from the part where it makes that transition and the error follows the new location.
The pathpilot console built in probing routinga run with ZERO issues. Watching the led on screen never shows the probe actually tripping.
As a final test I physically removed the probe from the machine (still plugged in) just not in the spindle and the error still occurs same place.
This feels to me like a variable isn’t initialized correctly and the instant the probing routing looks for a signal it’s getting tripped.
Normally in these types of situations having the wrong type of probe selected would be a suspect, but since you are able to do rapid moves and the standard probing routines work fine that would be ruled out. I would recommend reaching out to David Loomes, maybe there is an error in his macros or his post or some other weird thing going on.
Eric
I run my 1100mx the same way with multiple parts and different WCS with in-process probing using David’s post
running parts right now
no problems at all
Ed
kinda strange - I’m betting it’s something simple though
Out of curiousity, have you tried reverting to an earlier pp version to see if the issue persists or goes away?
As a separate thought, since the error only occurs with the Fusion posted code, and follows the location of the feedrate change, do you have some kind of tolerance built into the probing routine in fusion? I haven’t used it myself so I don’t know if that’s even an option but if, perhaps, you gave it a very small (or maybe zero, or negative?) tolerance between where it’s expected to make contact, and where that contact actually happens, that might be causing the fault.
Well still chasing this down. When the machine is turned on from cold shutdown the probing routing works for the first part probed then the error trips on the second part.
Resetting the program and running it again will cause the error every-time after that.
I’m also getting an warning I’m trying to understand now when importing my fusion code… I’m not sure if they’re related but they might be.
The Z for each WCS is set once in the work offset page in pathpilot. The base of jig that’s holding the stock isn’t variable like the length of my stock so I use it as my datum for Z in this first step.
The jig clamps can move the stock around a little bit usually +/- .004 " or so and I use the X/Y probing routing to lock down the center of the stock to correct for that.
Eric
Maybe run a test on a sample program and insert a Z probe routine before the X Y routine to see what happens
just for trouble shooting - if that works - maybe David can work around it
Ed
** Switching from a “partial circular boss” probe routine in fusion to a full circular boss took care of the warning messages **
The XY circular boss probing function is working properly. Using the “XY circular partial boss” option is not working and causes the unexpected contact error and associated warning messages.
