Convert to 5 Axis MC2017

[Jim at Gentex]

All,

I have used the 'Convert to 5 Axis' toolpath quite a bit in previous versions.

 

In MC2017 it is not working correctly for me.

I can't post my file here, but I can describe it simply.

 

It is a dome shaped surface.

Normally I do a 2d radial surface toolpath, then use the 'Convert to 5 Axis' to add a fixed tilt value to the Z axis for a little extra clearance for the toolholder.

This method has always worked for me, and it is clean and simple.

 

Doing that same procedure in MC2017, it seems to be ignoring the tilt value and just stays vertical.

Backplot and Verify both show the tool staying vertical, and the posted code confirms all B0 values.

 

Is this a known issue, or am I just missing something in the parameters?

[gcode]

My first guess

do you have the tool holder check enabled  on  the collision page

 

to test if it's broken in MC2017

open an X9 file that ran properly and post it in MC2017

if it posts correctly, you've got something set wrong in your new file

[Jim at Gentex]

OK thanks G.

I'll give that a try.

[Jim at Gentex]

OK here's what I did...

I opened the file in X9 and did the radial and convert to 5 axis toolpaths from scratch.

Backplot, verify, and post all good.

 

Opened that X9 file in MC2017.

Backplot, verify, and post all good there too.

 

So why didn't the toolpaths work from scratch in 2017, but the X9 ones do?

Parameters all the same, but one works and the other does not.

 

Lastly, I closed 2017, reopened it, reopened the file, regenerated the toolpaths, and it is still all good.

I could swear the parameters are all the same, but I still have that one that is boogered up. (I saved that one under a different file name.)

 

So now I'm completely stumped.

[gcode]

OK here's what I did...

I opened the file in X9 and did the radial and convert to 5 axis toolpaths from scratch.

Backplot, verify, and post all good.

 

Opened that X9 file in MC2017.

Backplot, verify, and post all good there too.

 

So why didn't the toolpaths work from scratch in 2017, but the X9 ones do?

Parameters all the same, but one works and the other does not.

 

Lastly, I closed 2017, reopened it, reopened the file, regenerated the toolpaths, and it is still all good.

I could swear the parameters are all the same, but I still have that one that is boogered up. (I saved that one under a different file name.)

 

So now I'm completely stumped.

 

 

stock definition????

[Jim at Gentex]

stock definition????

 

Not used.

I stuck to all of the default settings just to see what would happen.

I have the job running now with the X9 posted code, but I would still like to know why 2017 crapped out to begin with.

 

I sent a zip2go file to my reseller to see what they can come up with.

Nobody usually works there on Saturday, so I will have to wait until Monday before they even look at it.

[jlw™]

I use it convert to 5 quite often. It's probably my goto 5ax path

[Jim at Gentex]

OK I've had a chat with the tech support guys at my reseller.

Turns out it was something simple I overlooked. 

 

I didn't have the 'Tool axis crosses tilt axis' box checked.

Apparently it was checked by default in the older versions which is why I probably just overlooked it.

I checked the box, regenerated, and it's all good. 

 

Sometimes it's the little things that are right there under our nose that we don't see.

 

I'm glad we got this resolved, but it does raise a separate issue.

This particular toolpath seemed to take a much longer time to process in MC2017 than it did in X9 with the same feedrates and stepover values.

When I click on the green checkmark from the parameters page, the program almost seems to lock up.

If not for the blinking light  showing activity on my hard drive, I wouldn't know it was doing anything.

Then after the parameters page finally disappears, the toolpath still shows dirty and I need to regen it.

That also seems to take about 3x longer than it did in X9.

 

Anyone else seeing that?

[jlw™]

Ditto that extra processing time compared to X9.  I'll usually get a few paths ready then click regen and do my running around the shop.  Most of the time I come back and then decide to go do some more floor walking till it gets done.

 

I also want to add ref points to it.

[huskermcdoogle]

Speaking of moduleworks paths...  Anyone else's take forever to load the dialog box when you press parameters,  this takes forever, I don't recall it ever taking so long in the past.