WCS To Be Updated isn't necessarily correct

[vworpi]

I've just realised that the April update to improve probing usabilty has introduced some confusion.

WCS to be updated now contains a text field that refers to the setups WCS offset. 

If you drop a probe operation into a folder and change the folders Override WCS Offset to something different to the setup, the program is posted out with the offset to be updated changed. This is good, this is how it worked before.

However, the WCS to be updated in the probe cycle never changes from the setup WCS offset number.

[Richard.stubley]

Hi @vworpi,

I've just checked this out and you are completely correct. I'll raise a ticket and push to get this fixed. Thank you for reporting it!

[vworpi]

Is there any scope for this to be user set-able in the toolpath dialog, rather than at a folder level? I'll often probe a G54 but cast the value to G55 so I can compare the initial work offset with the current actual value, then throw the job back to the pallet changer if it's been loaded too far out of position.

[Richard.stubley]

Hmm, I see the workflow you are trying to achieve.

The issue if you change it in the Probe WCS dialog is then should it change the milling toolpaths too....

Have you tried using Override Driving WCS to Keep a static datum and then using the out of position check to do that tolerance check for you.
https://www.youtube.com/watch?v=X4qCU0X1pWM&t=222s&ab_channel=AutodeskFusion360

[vworpi]

I do need to update my post processors to use tolerance, but no, I'm not trying to update any offsets or check a position.

I have 48 parts on a fixture, 24 of part A, 24 of part B. Both parts use the same tooling, but can be ordered by our customer in different quantities. I've modified our existing program so each part is run or skipped depending on a couple of variables. 

The probing comes into play at the start of the program. I probe the first components of parts A & B, store the new values to G55 & G56, subtract those offsets from the initial G54 and store the results in #100 & #101. If the components are present, #100/#101 has a small deviation and the part runs. If the component is not loaded when probed, the comparison has a large deviation (we trigger on the fixture instead of the part) and the part is skipped.

Original datum is maintained throughout, G55 & G56 just used for macro comparison.