PowerMill 2020

PowerMill 2020

claire.louise.davies
Autodesk Autodesk
8,654 Views
46 Replies
Message 1 of 47

PowerMill 2020

claire.louise.davies
Autodesk
Autodesk

PowerMill 2020 was released today. Over the next few weeks, you will see PowerMill 2020 availability in your account. Please check your Autodesk Account or Autodesk Desktop App to see when your entitlement is available for download. 

 

In the meantime, you can review the Help and Release Notes to see what is being delivered in PowerMill 2020.

 

Thank you!


Claire-Louise Davies
Senior Manager, SQA

8,655 Views
46 Replies
Replies (46)
Message 21 of 47

M_Hennig
Collaborator
Collaborator

Collision checking after toolpath calculation is considerably slower.

Message 22 of 47

zfreitas
Advocate
Advocate

Congratulations to all development team in releasing this version where users can experience more calculation speed in parallel with some new features.

Best regards,
Jose Carlos Freitas
----------------
Tech Support Engineer
NORCAM
Message 23 of 47

zfreitas
Advocate
Advocate

Hello

 

In few words, where you will see huge improovments in speed.

-Constz

-3dOffset

 

-Any toolpath with huge amount of linking, like those inside complex boundaries (ex: rest boundary)

 

Speed is now (on a large project) slightly better than Powermill 2016. There are toolpaths that are slower to calculate (ex:raster) and quicker (constz & 3doffset) compared to 2016.

 

Best regards,
Jose Carlos Freitas
----------------
Tech Support Engineer
NORCAM
Message 24 of 47

lokesh.kalia
Autodesk
Autodesk

Hi @M_Hennig .  Please could you send us a PM 2019 project that demonstrates the significant deterioration in collision checking that you have seen in PM 2020 - either via the forum/direct message me, or via Salesforce. Apologies if you've already done so. Thanks.

 

Hi @Anonymous .Just to clarify Ben's comments earlier, he was referring to our ongoing efforts to make automatic collision avoidance faster. This is not because of a decrease in speed relative to PM 2019. Rather, it is simply because we know that using automatic collision avoidance adds to the time taken to calculate toolpaths  (albeit that it saves time post-calculation correcting these collisions). We are exploring ways to reduce this additional time.



Lokesh Kalia
Senior Manager, Software Development
Message 25 of 47

M_Hennig
Collaborator
Collaborator

I will create a support ticket on the site right now. It's a little hard to work "backwards" and go from 2020 to 2019. But I do have an example in my project. By the way, this is after calculation collision checking. In PM 2019 the toolpath was 18 seconds, in PM 2020, it was 4 minutes 55 seconds. 

Message 26 of 47

glen_h
Advocate
Advocate

@5axes 

Nice table. Thanks for taking the time to benchmark 2019 vs 2020.

I'm curious though, are those time savings in seconds or minutes?

 

Glen

Big thanks to all who contribute!
My opinions are my own and are not intended to reflect yours.
0 Likes
Message 27 of 47

Benjamin.Br
Autodesk
Autodesk

The fix for the problem where PowerMill 2020 closes unexpectedly when using Toolpath Edit tab > Edit panel > Move Start Points is now available in the PowerMill 2020.0.1 update. Details on the update, including a link to the full list of issues fixed, are available in this post: https://forums.autodesk.com/t5/powermill-forum/autodesk-powermill-2020-0-1-update-is-now-available-f....



Benjamin Brereton
Director, Engineering
0 Likes
Message 28 of 47

Anonymous
Not applicable

Just confirmed using PM2020 with automatic collision avoidance and a stock model for Model Rest Area Clearance toolpath is ridiculously, excruciatingly slow. 

Message 29 of 47

glen_h
Advocate
Advocate

@Anonymous 

 

I haven't started using 2019 for all the bugs, let alone 2020.

 

However all of the bragging by Autodesk about increases in computational speeds is intriguing.

 

Previous poster in this thread shows a chart, however it seems that only seconds are being saved in calculation time in many instances.

 

I was wondering if you were able to compare the calculation time for this particular rest roughing with automatic collision avoidance toolpath with 2018, or 2019?

 

Big thanks to all who contribute!
My opinions are my own and are not intended to reflect yours.
0 Likes
Message 30 of 47

Anonymous
Not applicable

....and freezes out all other PM projects while it tries to calculate said rest area clearance toolpath.

0 Likes
Message 31 of 47

lokesh.kalia
Autodesk
Autodesk

Hi @Anonymous . Would it be possible to send us the project with the very slow calculation, please? We are investigating ways to improve the speed of automatic collision avoidance and it would be very useful for us to have this example and see whether our prototype solution improves the performance in this case. Thanks.



Lokesh Kalia
Senior Manager, Software Development
0 Likes
Message 32 of 47

Anonymous
Not applicable
Case ID: 15436027
0 Likes
Message 33 of 47

Anonymous
Not applicable

more than just the slowdown during the calculation of a Model Rest Area Clearance while using automatic verification with a stock model...which 99% of Tool and Mold shops will use, btw. While PowerMILL is chugging and trying to calculate this if you open a new empty  project and try to expand the Macro button (lower left corner) that empty project will stall out and freeze.

0 Likes
Message 34 of 47

zfreitas
Advocate
Advocate
Can you check your free RAM?
Best regards,
Jose Carlos Freitas
----------------
Tech Support Engineer
NORCAM
0 Likes
Message 35 of 47

lokesh.kalia
Autodesk
Autodesk

Thanks for the data @Anonymous . We'll take a look. - From the initial comment I had taken 'automatic collision avoidance' to refer to tool-tilting but from the subsequent comment and data, I think I had misunderstood and the reference was to 'automatic collision checking/verification'? (We really should name 'automatic collision avoidance' something like 'automatic tool-tilting', it would be so much clearer!)



Lokesh Kalia
Senior Manager, Software Development
Message 36 of 47

Anonymous
Not applicable

Steep & shallow should've never changed. I just updated from 2017 and I'm not happy with this tool path.  It made pretty good path, now it does not.  Hopefully it gets addressed soon.   

 

 


@M_Hennig wrote:

I like the "uphill" feature with corner finishing, but when doing steep and shallow stitch areas, they start on the bottom and go up.. That does not really work in the steel.. Maybe this was overlooked.?


 

0 Likes
Message 37 of 47

lokesh.kalia
Autodesk
Autodesk

Hi @Anonymous . Would it be possible to provide a project that demonstrates the deterioration in behaviour - ideally, one project saved in PowerMill 2017 and another saved in PowerMill 2020 that has both, with the problematic areas highlighted, e.g. by circling them via some user-defined boundaries. - I apologise for the trouble in doing so but this would be of great help in identifying the problem and tracking down what has caused the change. In trying to fix some customers' problems we can change/perturb the behaviour from that which was satisfactory on other customers' parts. - Feel free to send it via this forum or via your support agent/Salesforce, of course. Thanks.



Lokesh Kalia
Senior Manager, Software Development
Message 38 of 47

bgundrum
Advocate
Advocate

Is it just my setup or is opening the toolpath settings page more painful in 2020 again? It seems to take longer than the 2019.2.2.2019210 version that I was running.

 

On the other hand, below is a time comparison of 2018/2020

 

2020 BENCHMARK.PNG

Message 39 of 47

lokesh.kalia
Autodesk
Autodesk

Hi @bgundrum Thanks for that data. Please could you say the toolpath strategy each benchmark used, as I'd be interested to know, in your usage, where PowerMill has made the most, and least, improvement.

 

I'll pass on the suggestion that we take another look at the toolpath strategy form, as I agree that raising it is slower than it should be.



Lokesh Kalia
Senior Manager, Software Development
Message 40 of 47

bgundrum
Advocate
Advocate

@lokesh.kalia 

For this benchmark test, I ran a macro that I found on the forum a few years back. Below is a list of the toolpaths that are calculated in this macro. Attached is the macro itself and a word document that has the Echo commands from the macro.

 

toolpaths in benchmark test.png