Multiple WCS Probing Post Issue - Haas

Multiple WCS Probing Post Issue - Haas

Anonymous
2,951 Views
22 Replies
Message 1 of 23

Multiple WCS Probing Post Issue - Haas

Anonymous
Not applicable

I wanted to post this to bring it to peoples attention as it had me puzzled for a bit until I actually paid attention to what was going on. Hopefully it can be corrected in a future update, I have not looked at modifying the Haas post for my use here, but hopefully this helps someone else running into this problem.

 

With that said there is also the possibility I have something setup wrong and this is my mistake, but I have looked at it a couple times and I don't see any way to correct settings in fusion to correct this issue

 

To try and make a long story short, I have a pallet of parts and due to variations in the parts I need to probe the height and location of each one. To do this I have Fusion setup to use multiple WCS and each part has a series of probing routines setup to update the WCS for each of the 8 parts on the pallet individually.

I proved out the code running only a single part, everything went well and the work offsets updated correctly so I assumed all was good.

 

I check the box in the setup to use multiple WCS, posted the code and ran a pallet  Each part probed like I expected them to so I assumed all was well and I ran the program through. Once done, it was clear there was an issue as several of the parts looked like the Work offset was not set correctly. So I ran the program through the probing again paying attention to the individual work offsets this time. What was happening was every time it probed the next part, it would only update the first work offset rather than update the work offset for the part it was probing.

 

So I started looking through the code and found the following.

 

Each time the probing is called up, it changes the individual work offset correctly, but where is specifies which work offset to update (SXXX.XX) it for some reason defaults back to the original work offset.

 

The simple fix obviously is to manually edit the post, it would be nice if this was done automatically. If anyone else has had luck with this then maybe I have screwed something up, some help would be great. If its just the post and the fact that the probing is pretty new, hopefully Autodesk can add this to the roadmap of things to work out in a future update.

 

 

%
O30001 (DM1-8 Finish Machining )
(Using high feed G1 F500. instead of G0.)
(T1 D=0.125 CR=0. - ZMIN=-0.34 - flat end mill)
(T2 D=0.06 CR=0. - ZMIN=-0.34 - flat end mill)
(T3 D=0.5 CR=0. - ZMIN=-0.25 - slot mill)
(T4 D=0.25 CR=0. TAPER=45deg - ZMIN=-0.025 - chamfer mill)
(T20 D=0.2362 CR=0.1181 - ZMIN=-0.3362 - probe)
G90 G94 G17
G20
G53 G0 Z0.

(Top Surface Probe Part 1)
T20 M6
(Haas Renishaw Work Probe)
G154 P1
G0 X1.0652 Y-1.4725
G43 Z0.6 H20
G65 P9832
G65 P9810 Z0.1 F39.37
G65 P9811 Z0. Q0.1 S154.01
G65 P9810 Z0.6
G65 P9833
G1 X1.0652 Y-1.4725 F500.
G53 G0 Z-10.

(Top Surface Probe Part 2)
G154 P2
G0 X1.0652 Y-1.4725
G43 Z0.6 H20
G65 P9832
G65 P9810 Z0.1 F39.37
G65 P9811 Z0. Q0.1 S154.01
G65 P9810 Z0.6
G65 P9833
G1 X1.0652 Y-1.4725 F500.
G53 G0 Z-10.

(Top Surface Probe Part 3)
G154 P3
G0 X1.0652 Y-1.4725
G43 Z0.6 H20
G65 P9832
G65 P9810 Z0.1 F39.37
G65 P9811 Z0. Q0.1 S154.01
G65 P9810 Z0.6
G65 P9833
G1 X1.0652 Y-1.4725 F500.
G53 G0 Z-10.

 

An additional request for probing while I am requesting things, and maybe this is already planned, would be to let us specify the exact probing location. For instance, right now when probing a single surface, the probe defaults to the center of that surface. In my case on this part, there are obstructions that prevent this from being possible. The quick work around was to model in dummy probe locations that confined the probe to a specific area. It would be great if you could also pick a point or feature to further define the probing location and would make it much easier to setup.

0 Likes
2,952 Views
22 Replies
Replies (22)
Message 2 of 23

LibertyMachine
Mentor
Mentor

The ability to select a certain point on the probing surface is being developed, and is currently available in Beta mode.

 

Would you be able to share the file you were working on, or a dummy file that reflects what you did and the results you got? I could make a file and and try to simulate your issue, but if my selections are different and I get better results, I/We couldn't help you with where you went wrong (if that is the case where the error is on your end and not Fusion's)


Seth Madore
Owner, Liberty Machine, Inc.
Good. Fast. Cheap. Pick two.
0 Likes
Message 3 of 23

LibertyMachine
Mentor
Mentor

I've been playing with this for a while this morning, using both the Fanuc and the Haas post, and I'm starting to think this is a bug. As the day progresses, I'll try to get into the post and see if something jumpps out at me as to why it's doing this. It most likely will require more trained eyes to discover the error

Going to tag a couple few post guys from Autodesk @bob.schultz @matthew.nichols @AchimN


Seth Madore
Owner, Liberty Machine, Inc.
Good. Fast. Cheap. Pick two.
Message 4 of 23

Anonymous
Not applicable

I could email it, don't want to post is as its not my part. Im thinking it is a bug somewhere, easy enough to fix by hand but kind of annoying.

 

Im going to make the change manually and make sure it runs on the machine.

 

 

0 Likes
Message 5 of 23

Steinwerks
Mentor
Mentor

@LibertyMachine wrote:

I've been playing with this for a while this morning, using both the Fanuc and the Haas post, and I'm starting to think this is a bug. As the day progresses, I'll try to get into the post and see if something jumpps out at me as to why it's doing this. It most likely will require more trained eyes to discover the error

Going to tag a couple few post guys from Autodesk @bob.schultz @matthew.nichols @AchimN


Bug confirmed for sure. The dump.cps is outputting this for every operation (I used four incremental offsets starting at 7):

 

onParameter('probe-output-work-offset', 7)

 

So it doesn't increment properly and then it hits this section:

 

var probeOutputWorkOffset = 1;

function onParameter(name, value) {
  if (name == "probe-output-work-offset") {
    probeOutputWorkOffset = (value > 0) ? value : 1;
  }
}

and probeOutputWorkOffset gets populated further on in the probing code.

 

This could be worked around I think but it wouldn't be pretty and it probably means that if the user wanted to override the WCS used for the probe AND use multiple work offsets it'd fail miserably.

Neal Stein

New to Fusion 360 CAM? Click here for an introduction to 2D Milling, here for 2D Turning.

Find me on:
Instagram and YouTube
Message 6 of 23

LibertyMachine
Mentor
Mentor

Thanks for digging into this sir. Been kinda busy all day with work. Now, to see how long it take for them to bring it into a patch/bug update


Seth Madore
Owner, Liberty Machine, Inc.
Good. Fast. Cheap. Pick two.
Message 7 of 23

Steinwerks
Mentor
Mentor

Just did a little testing in Inventor HSM: this is across the board, not just Fusion, and it doesn't matter if it's the G154 range or not, it won't output for multiple WCS offsets period. Just got a bunch of S1. when posting from G54 to G57.

 

@al.whatmough@fonsecr I think this is a big deal and it's going to scrap a lot of parts if it doesn't get fixed soon.

Neal Stein

New to Fusion 360 CAM? Click here for an introduction to 2D Milling, here for 2D Turning.

Find me on:
Instagram and YouTube
Message 8 of 23

Anonymous
Not applicable
Thanks for looking into this guys. Hopefully they get it corrected. Taught me not to trust the post quite as much so that's a positive I guess. Manual edits for now it is.
0 Likes
Message 9 of 23

AchimN
Community Manager
Community Manager

Thanks for your feedback, we will have a look into this.



Achim.N
Principal Technology Consultant
Message 10 of 23

KerimY
Alumni
Alumni

thanks for feedback.

Please insert "currentSection" before workoffset into this two lines in onCyclePoint.

We will update it soon.

 

function onCyclePoint(x, y, z) {
var probeWorkOffsetCode;
if (isProbeOperation()) {
setCurrentPosition(new Vector(x, y, z));

var workOffset = probeOutputWorkOffset ? probeOutputWorkOffset : currentWorkOffset;
if (workOffset > 99) {
error(localize("Work offset is out of range."));
return;
} else if (workOffset > 6) {
probeWorkOffsetCode = "154." + probe154Format.format(currentSection.workOffset - 6);
} else {
probeWorkOffsetCode = currentSection.workOffset + "."; // G54->G59
}
}

 

Please let me know if the issue has solved.

---

KerimY
Software Engineer
Message 11 of 23

fonsecr
Autodesk
Autodesk

Thanks all,

 

Opened ticket CAM-5754 for this one. Fixed in next release.

 


René Fonseca
Software Architect

Message 12 of 23

NYC_CNC
Advocate
Advocate

a BIG thanks.  We just got a new machine (HAAS) and are running twin, dual-station vices (4 workpieces) and wanted to use the multiple WCS offsets" with our Renishaw probe via Fusion 360 probing CAM routines.  It didn't work (per this bug) but we made the QUICK change to post per processor and IT WORKS!  SUCH A WIN!!!  THANK You!  It's great to have this running today!!!

0 Likes
Message 13 of 23

fonsecr
Autodesk
Autodesk

No problem. But once the December release of Fusion is out you should revert the post change. Dont think changing the post will workaround the problem in general.

 


René Fonseca
Software Architect

0 Likes
Message 14 of 23

Steinwerks
Mentor
Mentor

As best I can tell the workaround won't result in letting the override work either, it only allows the probe code to output for the current work offset.

 

@fonsecr is this correct?

Neal Stein

New to Fusion 360 CAM? Click here for an introduction to 2D Milling, here for 2D Turning.

Find me on:
Instagram and YouTube
0 Likes
Message 15 of 23

fonsecr
Autodesk
Autodesk

Yes, correct the multiple work offset increment value set in the Setup would need to be handled also.

 


René Fonseca
Software Architect

0 Likes
Message 16 of 23

EricbIMM
Explorer
Explorer

Hello,

has there been any progress on this? we are running into the same exact issue now 3 years later. Thanks Eric 

Message 17 of 23

GeorgeRoberts
Autodesk
Autodesk

Good Morning,

 

Sorry to hear you're still having issues. I can't reproduce this problem here anymore, the parameter 'probe-output-work-offset' seems to be getting updated correctly in the latest release of Fusion.

 

Could you share a copy of your post processor and a file which you're having the issue on?

 

 

-

George Roberts

Manufacturing Product manager
If you'd like to provide feedback and discuss how you would like things to be in the future, Email Me and we can arrange a virtual meeting!
0 Likes
Message 18 of 23

Anonymous
Not applicable

I'm having the same problem as well, I just downloaded the latest post from the library (Haas UMC-750), I've tried it multiple different ways but it still only updates G54.

 

It actually seems to be doing something even stranger, even though the two holes that I'm probing are ~20mm apart in X, the two figures that it updates G54 with (pausing the program between the two holes and writing it down) are basically the same (within about 0.005mm) so it appears as if it's subtracting the distance between the two holes off the figure it's updating the offset with?

 

I've manually probed both holes and come up with a difference in X of 20.007mm.

 

%
O01001
(Using high feed G1 F5000. instead of G0.)
(Machine)
( vendor: Haas Automation)
( model: HAAS UMC-750)
(T40 D=6. CR=3. - ZMIN=-5.5 - probe)
N10 G90 G94 G17
N15 G21
N20 G53 G0 Z63.5

(Probe WCS2 2)
N25 T40 M6
(Renishaw OMP40-2 6mm x 50mm - Haas)
N30 G55
N35 G53 G0 Z63.5
N40 G53 G0 X-736.6 Y-203.2
N45 G0 B0. C0.
N50 G0 X0. Y0.
N55 G43 Z177.915 H40
N60 G65 P9832
N65 G65 P9810 Z-5.5 F3000.
N70 G65 P9814 D8.2 Q1. S1.
N75 G65 P9810 Z177.915
N80 G65 P9833
N85 G53 G0 Z63.5

(Probe WCS2 5)
N90 G56
N95 G0 B0. C0.
N100 G0 X20.009 Y-0.013
N105 G43 Z177.915 H40
N110 G65 P9832
N115 G65 P9810 Z-5.5 F3000.
N120 G65 P9814 D8.2 Q1. S1.
N125 G65 P9810 Z177.915
N130 G65 P9833

N135 M5
N140 G53 G0 Z63.5
N145 G53 G0 X-736.6 Y-203.2
N150 G28 G91 C0.
N155 G90
N160 G0 B0. C0.
N165 M30

%

0 Likes
Message 19 of 23

GeorgeRoberts
Autodesk
Autodesk

Thank you for the reply. Please can you share a copy of the file you're using here? I can't seem to replicate this here

-

George Roberts

Manufacturing Product manager
If you'd like to provide feedback and discuss how you would like things to be in the future, Email Me and we can arrange a virtual meeting!
0 Likes
Message 20 of 23

Anonymous
Not applicable

@GeorgeRoberts 

FYI, still does not work with

description = "HAAS (pre-NGC)";

$Revision: 42746 c0171a78ac3084c1218477b31e4ff27d64e56706 $
$Date: 2020-04-23 05:29:32 $
FORKID {241E0993-8BE0-463b-8888-47968B9D7F9F}

 

All offsets are being written but they are all getting approximately the same coordinate locations.

 

I have tried it multiple different ways (individual setups, nested folders, etc.) but they always end up with the same values being written to all of the offsets even though the probe is moving to the new correct location when measuring.

 

Here is an example of the code output:

 

%
O05000 (PROBE AT G57, 58, 59, 154.P1)
(T100 D=0.2362 CR=0.1181 - ZMIN=5.8108 - PROBE)
G90 G94 G17
G20
G53 G0 Z0.

(PROBE G57 STARTING AT G55)
T100 M6
(RENISHAW OMP40-2 6MM RUBY/CERAMIC STEM)
G55
G0 X-4. Y-4.5313
G43 Z10.047 H100
G65 P9832
G65 P9810 Z7.047 F50.
G65 P9814 D5.635 Z5.8108 Q0.5 R0.5 M4. S4.
G65 P9810 Z7.047
G0 Z10.047
G65 P9833
G53 G0 Z0.

(PROBE G58 STARTING AT G57)
G57
G0 X4. Y-4.5313
G43 Z10.047 H100
G65 P9832
G65 P9810 Z7.047 F50.
G65 P9814 D5.635 Z5.8108 Q0.5 R0.5 M4. S5.
G65 P9810 Z7.047
G0 Z10.047
G65 P9833
G53 G0 Z0.

(PROBE G59 STARTING AT G58)
G58
G0 X4. Y4.5313
G43 Z10.047 H100
G65 P9832
G65 P9810 Z7.047 F50.
G65 P9814 D5.635 Z5.8108 Q0.5 R0.5 M4. S6.
G65 P9810 Z7.047
G0 Z10.047
G65 P9833
G53 G0 Z0.

(PROBE G154.P1 G110 STARTING AT G59)
G59
G0 X-4. Y4.5313
G43 Z10.047 H100
G65 P9832
G65 P9810 Z7.047 F50.
G65 P9814 D5.635 Z5.8108 Q0.5 R0.5 M4. S154.01
G65 P9810 Z7.047
G0 Z10.047
G65 P9833

M5
G53 G0 Z0.
X-4.
G53 G0 Y0.
M30

%

 

0 Likes