Postprocessor coolant off then on on same tool.

Postprocessor coolant off then on on same tool.

Anonymous
Not applicable
1,812 Views
7 Replies
Message 1 of 8

Postprocessor coolant off then on on same tool.

Anonymous
Not applicable

Has anyone else noticed that the postprocessor has changed... a lot.. well it has for me.. and now there are dumb things like... same tool different tool-paths, at the end of one tool-path it M09, and then at the beginning of the next (with same tool) it hit M8 again...

also i see vortex has some new ways of Leading into the material... still exploring that..

 

0 Likes
1,813 Views
7 Replies
Replies (7)
Message 2 of 8

instrumakr
Advocate
Advocate

Hi

 

I had the same problem at one time I my local contact to change the post

to turn the coolant on at the start of the new tool change and to cancel before

next tool change. It was quite irritating.

 

instrumakr

0 Likes
Message 3 of 8

Anonymous
Not applicable

I had some fun time last night and edited mine... made a backup first tho 🙂 ... now it runs as smooth as before 🙂 got rid of all those unnecessary comments in it too.. you can edit it all yourself if you have good G and M code knowledge.

 

0 Likes
Message 4 of 8

NanchenO
Collaborator
Collaborator

Yes, @Anonymous, that's the right way: first make a backup.

 

You can do almost what you want with PMPost and it is easy to use.

 

I'm just missing a clear documentation to see what has changed between the versions. I had for instance a perfectly working 5 axis postpro which is no longer usable with PM 2017: The 5 axis coordinates are simply wrong for my machine and no way to tweak the postpro to get the correct values !

 

For me, we should not have to modify our posts between the versions because they changed something in PMPost, unless they clearly describe what is supposed to be modifyed.

 

I have five postpros to keep alive and no time to completely retest them (2x 5axis) with all possible functions between the versions. It seems, that Autodesk has not yet noticed that a wrong result when posting could be very expansive on a machine.

 

Olivier

0 Likes
Message 5 of 8

Anonymous
Not applicable

I fully agree with you...I believe that Delcam used to take a lot more care of their products... Autodesk seems to just want to collect the cream with their purchase of Delcam... I hope they do put some more thought into the Post and yea crashing is not so cheap.. if only we could bill them every time its a post problem 🙂

 

In our company, apart from Powermill, one of my colleagues uses ArtCAM from Delcam (has the 2015 version) and the post is similar to it... at least what I've noticed. I program for 2 machines now.. even though I just heard that we bought a CNC lathe - Fanuc --- cant wait to test out the chaos in powermills turning and post processing 🙂

 

0 Likes
Message 6 of 8

NanchenO
Collaborator
Collaborator

We have a mill-turn machine and I would like to use PM 2017's new funtionalities and implement them in the postprocessor (useful for the company and very motivating for me).

 

Unfortunately, it also seems that the new turning functionalites are not ready to be used in production ! I was not able to program a single finishing toolpath: PM 2017 simply crashes every time !

 

As I already wrote in another post, Autodesk must really learn the difference between CAD where you can almost always find a workaround and get an acceptable result despite of bugs and CAM which simply MUST BE RELIABLE.

 

Olivier

0 Likes
Message 7 of 8

emilie.a
Autodesk
Autodesk

Hi Olivier,

We are currently aware of a bug that causes PowerMill to crash when turning is used with cutter compensation. We are actively working on this.

If you think the bug you're experiencing is a different one, I urge you to contact your support team. Turning is a brand new functionality in PowerMill and we are eager to get as much data as possible where customers are experiencing issues. The development team hasn't changed and we treat crashes and gouges in particular as very high priority bugs.

Thanks for your help,

Emilie

 



Emilie.A
Software Development Manager
Message 8 of 8

NanchenO
Collaborator
Collaborator

Hi Emilie,

 

Thank you for your answer. I made the test without cutter compensation and there is no crash.

 

Please treat this bug with highest priority, since finishing does only make sense with cutter compensation. That means that the function is not really usable for the moment.

 

Thank you !

 

Olivier

0 Likes