Creo2 - build code

Forum|Forum|11 years ago
May 14, 2014
14 replies
3902 views

Hi all - I found a reason to leave Creo2 M070 and want to update.

Should I go M090 or M100?

I run without PDM - but I don't run with scissors or a lollypop in my mouth.

Thanks

B

BobMonat

1-Visitor

M110 is supposed to be available today.

Is the list of fixes between builds still available? If so, where is it?

Thanks,
Bob

Bob Monat
Jerand Technical Services, Inc.
bob@jerand.com
www.jerand.com
1-317-875-6087

On Wed, May 14, 2014 at 2:48 PM, Nathan Rollins
<->wrote:

> Hi all – I found a reason to leave Creo2 M070 and want to update…
>
>
>
> Should I go M090 or M100?
>
>
>
> I run without PDM – but I don’t run with scissors or a lollypop in my
> mouth…
>
>
>
> Thanks
>

B

BrianToussaint

19-Tanzanite

Under eSupport Tools on your PTC support page.

[cid:image001.png@01CF6F89.7DF86FF0]

Brian Toussaint
Systems Administrator

Hoshizaki America, Inc.
“A Superior Degree Of Reliability”
618 Hwy. 74 S., Peachtree City, GA 30269

D

DeanLong

1-Visitor

Brian,

Use caution jumping above M080. I have recently found out that my HP with on-board grahics will not work above M080 without OpenGL disabled. If you are using an approved hardware configuration then you are fine. Just make sure before the jump up.

D

davehaigh

13-Aquamarine

You should go with m110

PTC strongly discourages using Creo Parametric 2.0 M110 with older datecodes. It is important to move all users at once, to avoid models being modified again in older datecodes by other users.

Document - CS150760

Document Information
Type

Article

Date Created

12-Nov-2013 13:04:12 EST

Date Last Updated

10-Mar-2014 12:27:34 EDT

Document Details
Title

Defect in handling of unitized expressions of angular values in PTC Creo Parametric 2.0

Description

• Defect in handling of unitized expressions of angular values
• A dimension driving a coordinate system shows an incorrect value, when a UDF containing relations is placed.
• In Wildfire 4.0 the value is correct, but in Creo Parametric 2.0 a different value is displayed

Applies To

• Creo Parametric 2.0 datecodes: F000 - M100

Cause

• Defect in handling of unitized expressions of angular values in PTC Creo Parametric 2.0 F000 - M100
• The System of Units in PTC Creo Parametric is defined by three primary basic units: length, mass/force, and time. There are two more quantity types included in a System Unit definition: temperature and angle. Inside Creo, all standard System Units contain radian as the basic unit for angular values. However, angular measurements in Creo models are reported in degrees. These contradictions cause inaccurate support of angular values in Relations and Parameters.

Resolution

• SPR 2201931 has been filed with PTC R&D
• Corrected in Creo Parametric 2.0 M110
• PTC strongly discourages using Creo Parametric 2.0 M110 with older datecodes. It is important to move all users at once, to avoid models being modified again in older datecodes by other users.

SPR Information
Product

Creo Parametric, Direct, and Layout

Module

FEATURE OPERATIONS

Reported Release

Creo 2.0

Reported Datecode

M090

Affected Platform

All

Resolution Status

Release

Status

Datecode

Creo 3.0

Evaluating

-

Creo 2.0

Planned

M110

Related Documents
Type

Number

Status

Description

SPR

2201931<">https://www.ptc.com/appserver/cs/view/spr.jsp?n=2201931>

Open

The dimension 'PROFILE_ANGLE' in coordinate system 'BACKUP_CTR_TIP' shows up as
-128.69 instead of -2.25, when UDF is placed. In Wildfire 4.0 the value can be seen
as -2.25, but Creo Parametric 2.0 displays a different value.

David Haigh

B

BrianKrieger

10-Marble

I would say go to M100*. Our tests show that M100 is faster than M070 (didn't test against m090, though) when disconnected from PDMLink. When connected, though, our guy's tests showed slower performance. M100 does solve a few things, though, like Model Check misinformation and some drawing exits. As mentioned, though, the upgrade advisor is a nice tool.

We run PDMLink, so I guess we're running with a lollipop in our hands and scissors........oh, never mind...........

BK

* - That said, M110 is due tomorrow, so if there hasn't been testing, this one might be slated instead to circumvent the "try in the latest build" scenario when something does go wrong.

D

dmartin

11-Garnet

Windchill users, be aware that your Windchill cache is not supported if jumping more than one maintenance build code. We are in the process of moving from M030 to M090 and just found that out. Recommended practice is to upload or check in all new or modified objects from all workspaces prior to upgrade. Our internal MCAD AE discovered this when one of our users had some weird workspace behavior after upgrading.

David R. Martin II

Senior CAD Application Specialist

Amazon

D

davehaigh

13-Aquamarine

I'm not sure that's a hard and fast rule.

M030 had lots of issues with Windchill and the cache, most of that stuff was fixed by m050/m060.

I can totally believe you would have issues updating from that version.

David Haigh

T

TomU

23-Emerald IV

We recently jumped from CEP5 M120 to M220 with no issues. The only thing we noticed is that the first time you launched Pro/e, it would take between 10 and 15 minutes to start up. There seemed to be some type of cache update or backup taking place in the background. After that initial startup delay, everything was fine. Users did not check-in, upload, or anything prior to the jump. FWIW.

Tom U.

B

BillRyan

16-Pearl

Go to M110 if you are connected to Windchill and depend on Creo calling for the objects on the fly. For some reason, M110 is able to utilize 100% of the network which has given us a 20% improvement in opening files(initial testing). Thank you PTC!

[cid:image001.png@01CF737D.CA1D2E50]

S

ScottPearson

1-Visitor