WCS Probing not accurate!!

WCS Probing not accurate!!

mikeNCNTL
Advocate Advocate
1,057 Views
11 Replies
Message 1 of 12

WCS Probing not accurate!!

mikeNCNTL
Advocate
Advocate

Hello Fusion people

 

I am having a heck of a time with the WCS probing  working all of a sudden

 

If I use the Renishaw macro directly, or call it from the Haas, I get one value. 

 

If I use the WCS probing cycle built into Fusion and probe to update WCS, I get a value that averages .01" different. 

 

This obviously makes for bad parts. 

 

Probe speed is set to 4.0156in, which matches what Renishaw is using as default. 

 

I am splitting across Y in this case to get my WCS.

 

0 Likes
Accepted solutions (1)
1,058 Views
11 Replies
Replies (11)
Message 2 of 12

DarthBane55
Advisor
Advisor

The WCS probing cycle from Fusion is calling the Renishaw macro.  Are you using something else?  I doubt it has anything to do with Fusion because if it touches 2 points in Y axis to find the middle, it's entirely handled inside the probing macro (Renishaw).  Are you probing in the exact same location with the various methods you tried?

0 Likes
Message 3 of 12

mikeNCNTL
Advocate
Advocate
The probing is happening withing a few .001 of the exact same location.
The part(s) have been indicated to ensure they are flat / perpendicular etc.
0 Likes
Message 4 of 12

DarthBane55
Advisor
Advisor

ok, but the code is calling a Renishaw macro right?

Actually, do you mind posting here the 2 versions, the one you did by hand, and the code from Fusion?

0 Likes
Message 5 of 12

mikeNCNTL
Advocate
Advocate
It is calling a macro, I will go look and see if it is calling something different shortly

0 Likes
Message 6 of 12

seth.madore
Community Manager
Community Manager

Can you share your Fusion file here?
File > Export > Save to local folder, return to thread and attach the .f3d file in your reply


Seth Madore
Customer Advocacy Manager - Manufacturing


0 Likes
Message 7 of 12

programming2C78B
Advisor
Advisor

Keep in mind if you are doing a wall or Z height, that the offset in your heights tab can effect it. 

IE if you probe Z on the face, but have it programmed for -.1 by accident, it will tell the machine your top of part is actually -.100 from where it really is. 

Please click "Accept Solution" if what I wrote solved your issue!
0 Likes
Message 8 of 12

mikeNCNTL
Advocate
Advocate

Seth, I can send you the file directly. I can't post it out in the wild. 

 

I can't see is the subprogram running when using fusion is the same as what runs when I probe vis VPS on the haas. 

 

There is not an offset to height set in fusion. This is just finding center of a feature machined in a previous operation. 

 

 

 

0 Likes
Message 9 of 12

mikeNCNTL
Advocate
Advocate

Here is more info. Showing where the part is being probed, and the machine coordinate results of fusion vs Haas

G58 is probed with Haas. G59 is updated by Fusion. G154P1 is what is used to position probing in fusion. Y axis is whats screwed up.  There are reference flats cut in op 1 to probe on. This is not probing the cylinder. The flats are not tapered to one another. They are parallel. 

mikeNCNTL_0-1680270532713.png

mikeNCNTL_1-1680270692654.png

mikeNCNTL_2-1680270744921.png

mikeNCNTL_3-1680270765282.png

mikeNCNTL_4-1680270921390.png

 

 

 

0 Likes
Message 10 of 12

seth.madore
Community Manager
Community Manager

@mikeNCNTL drop me an email with a LINK to the Fusion file (not the file itself, just the link). Right click on the file in your Data Panel and select "Share Link". Copy that link and email it to me:

seth DOT madore AT autodesk DOT com


Seth Madore
Customer Advocacy Manager - Manufacturing


0 Likes
Message 11 of 12

seth.madore
Community Manager
Community Manager
Accepted solution

Your datum point is off location, it's not at zero:

2023-03-31_14h23_02.png

2023-03-31_14h23_33.png

2023-03-31_14h24_04.png


Seth Madore
Customer Advocacy Manager - Manufacturing


0 Likes
Message 12 of 12

mikeNCNTL
Advocate
Advocate

😤😫Giant Face Palm 😞

0 Likes