cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Summary: WF2.0 to WF3.0 upgrade (Pro/Man) recommendations

Highlighted
Newbie

Summary: WF2.0 to WF3.0 upgrade (Pro/Man) recommendations

Hello all,

I have received several responses to my query. Most recommend WF3 M080,
certainly nothing earlier than M070.

The most significant "gotcha" is apparently the new Tool Manager which
requires some elbow grease to configure initially.

The responses are presented here for your enjoyment. My original
posting is appended.

Thanks to everyone who responded,

Dave Ford
CNC Programming
G.W. Lisk Co.
Clifton Springs, NY 14513
(315) 462-4381

**************
We went to WF3 a few months ago. We're on M080 presently, M070 had some
issues that went away with M080.
"Make Datum" was restored in M040 (I think). Between M40 and M060, you
couldn't subroutine properly. Put is in a real bind, we programmed in
M040/50/60 but if we had a program with individual subs we had to
generate CL data on another machine running M030.
Play Path is a hell of a lot smoother. with solid tools, not jerky. If
you have a lot of cut data, be prepared to have to convert it to the new
XML format. There's a 'whats new' document on the splash page that
details the updates to NC.

**************
We found a issue with the old tooling parameter files. The new Tool
Manager did not always play nice with them and would do a Pro/Exit. We
changed all of them into xml files to fix it. We also had to do some
clean up to our solid models of tool assemblies. We had some issues with
parameters that were not showing up. The models that we had problems
with were created a long time ago in version 14 and were not correct.
They did work before but we had to clean them up to get them to work
properly with the new Tooling Manager. We are planning to release build
M070 to production as soon as it works into Design Engineering's
schedule. We did try to go to WF2 build M250 but found an issue with
patterned subroutines that caused strange rotation output for our mills.
There is an SPR filed for the problem.

**************
Be sure to load the latest build of WF3 M080. Earlier builds had
numerous bug issues with CLDATA. Issues such as leadin / leadout and
where cutter compensation was being turned on. Also GPOST was updated in
later builds. So be sure to review the g-code files for different
output.

**************
am looking at this as well. So far I have come up with: If you store the
tool feed/speed with tool you may have issues, as all this in now stored
in one xml file rather than separate files. You should look at how to
convert this before moving forward.

**************
[Original Request]

Hello all,

We are using Pro/Man for Turning, Milling, and Mill/Turn machines and
preparing to move from WF2.0 (M180) to WF3.0.

I have used PTC's Update Advisor and did not see any red flags.

We are looking for advice on the following:
1) What is a stable date code from a manufacturing perspective?
2) What open issues or "gotchas" should we look out for?
3) Has the early WF3.0 issue of extraneous (NC sequence related) datum
planes in the model tree been resolved?
4) What new functionality should we be on the lookout for?

Thanks in advance for any advice offered. I will post a summary.

Regards,

Dave Ford
CNC Programming
G.W. Lisk Co.
Clifton Springs, NY 14513
(315) 462-4381