Part alignment

[Jurgenvh1]

Hello all,

I have a problem with part alignment.

My goal is to probe along the Y axis and then update the WCS to rotate the table (Z-Axis) before milling. 

The only problem is that this type of product is serial work and they are all different. So I can't measure every single part and create different files for them like the way they describe in the tutorials. 

Is there a way to measure and update the WCS automatically within one single program?

The machine is a DMG MORI CMX70U (3+2) with siemens 840D sl control.

Thanks in advance!

[Richard.stubley]

Hi @Jurgenvh1,

Using the Part alignment Function inside of Fusion 360 needs the the application to calculate the alignment. So it does unfortunately need the results to be bought back in for calculation.

If you are only aligning the part along a line have you looked at Probe WCS?
This is less mathematically intensive so uses on machine macros, this can be done all within the same cycle so no need to bring the results back. 

[Jurgenvh1]

Hi @Richard.stubley 

Thanks for your reply. I tried the thing WCS probing operation you suggested, and with some extra programming I am getting this thing to work. The only things i need to get working now is that the rotation, even when e.g. G54 says -0.1 the C-axis gives me a +0.1 rotation?

And after a next WCS probing operation the rotation of the C-axis goes back to 0 while G54 says it's still -0.1.

I hope you can help me out with this too..

[Richard.stubley]

@Jurgenvh1,

This is an odd one.

So if you watch the machine C position throughout the cycle what happens? 
Id expect it to be at 0 while its doing the probing ops.
Then move to 0.1 after the probing ops.

The machine position is the better one to look at rather than G54 position. 
This will most likely never move from 0. As when the offset table gets updated to 0.1 and called again, although the actual machine will move the relative value will stay at 0.

[Jurgenvh1]

@Richard.stubley 

After the firts operation the c axis gets rotated, but when the next probe operation is performed the machine position goes to 0 indeed. 

So basically the machine displays 0 because it has not changed since the previous operations?

[Richard.stubley]

@Jurgenvh1,

Can you attach the code you are running please.

[Jurgenvh1]

@Richard.stubley 

Sorry for the late reply, but i can't attach the code because the main code is confidential.