Attached is the latest config options from PTC for Creo 2.0 M100.

Attached is the latest IDD from PTC.

Currently, Creo Simulate does not have CFD capability, but FloEFD can be integrated with PTC products as shown on Page 7 in the attached file.

Creo 2.0 - Hardware Notes.

Parametric, Direct, Layout, Schematics, Options Modeler, Simulate

Table of Content

Last updated: April 10, 2014

 Platform Support

 System Requirements

 Graphics Information

 Certified and Supported Graphics Cards

 Desktop Virtualization Environment Support

 Supported Peripherals and Accessories

 Supported MCAD Systems

 Supported Finite Element Solvers

 Platform Support for Data Exchange

When preparing to go from ProE WF4 to Creo 3 a PTC rep said that there were hundreds (I think he said over 400) enhancements going from WF4 to Creo 2 'while no features have been removed' (paraphrased).  For those who are using Creo2, we all know that is simply not true.

Purpose of this Document is to provide a one-stop-place to get the following

1. Make information available to others so they can account for specific losses in functionality
2. Give sanity to people who have been looking in vain for features that have been removed,
3. Perhaps people know workarounds, or simply new ways to do the same thing that they can share.
4. Increase awareness with PTC that they will bring back features that perhaps were overlooked during the upgrade.

Anyone has permission to modify this document.  Please Add/modify/or cross out anything below this line and discuss everything else below the thread:

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Functionality Removed:

1. Tabs for open objects
   1. Tabs for open objects in Creo (like was in ProE)
   2. Use Tabs for open models/drawings in Creo (like in ProE, IE, Firefox, Chrome, FoxIt pdf viewer, etc)?
2. Show Erase Model Annotations
   • You can show only model annotaions that have been DELETED.
   • You cannot show model dimensions that have been ERASED.
   • The erased dimensions get burred in the dwg tree forcing the user to go through the model tree to verify all necessary dims are shown rather than just use the show/erase dialog as it was in ProE WF.
   • Add a Search for Drawing Dimensions

Creo Simulate Help Center in multiple languages available here: http://help.ptc.com/creo_hc/creo30_sim_hc/usascii/

Flatten Quilt and Flatten-Quilt Deformation features are probably something most of us avoid due to the apparent limitations in several of the commands.

If you really need to map something with some semblance of accurately onto a 3D surface, this is the way to do it.

I have "offset" a PTC logo onto a spherical surface before and it wasn't as nice as I'd have liked (find the baseball).

I think in this sample part, I finally nailed it.  And the logo turns out to be quite robust for the offset feature used here.

I was surprised to find that if you can flatten a quilt, you can pretty much map anything 3D onto it.  Maybe not straight forward in every event, but there is a lot to be explored.  One thing I did note in Creo 2.0 is that when you highlight the flattened quilt, the Offset Feature does not present itself (remains grayed out).  However, if you pick the unflattened quilt, which does highlight the offset feature, you can change the target reference to the flattened quilt so you can proceed to manipulate this flattened surface.

You can map almost everything including solids, offsets, and curves.  Examples in the attached file include a trimming edges (curves) and two offsets to make the eye... and the rounds prior to reforming the surface.  The PTC logo was deformed onto the surface and projected back to the offset feature sketch.  This is how you get a true mapping with offset features on a 3D surface.

In the attached sample (Creo 2.0 parametric full version), you will find the use of boundary blends; offsets, and flatten-quilt deformations.  Although the target surfaces seem spherical, I had trouble flattening surfaces actually defined from revolved arcs.  However, the boundary blends seems to have no trouble flattening.

Here is a quick tour of what you will find in the attached file:

Attention:You will need to update your browsers Flash Player plugin to see videos on this site.

Update your Flash Player here. Its free and fast.

Inspired by user requests, it has become clear that people want to add 3D text onto surfaces already developed.  They want their text to be easily managed (as in using the editor) and not just projected edges into a sketch.

This video uses a Designated Area feature to let you make a more dynamic sketch that can be wrapped onto an extrusion not necessarily round.

Spinal Bend is a very powerful feature as it can bend along a profile, but it tends to distort features unless you use perimeter control. 

Spinal Bend does not lend itself to "centering" the object to be wrapped.  This video addresses this.

Spinal Bend on solids affect -all- solids in a model; and it truncates any solid outside the "select region".  This video addresses this by wrapping a quilt instead.

In the video I chose to "engrave" a relief, but you can extrude also.  I just wanted to add the variation by adding a frame.

The attached file was generated in the video.  Feel free to play with it.  It is Creo 2.0 Parametric full version.

Remember to set the YouTube quality up to 1280x720 for a clear image.

Enjoy!

Since Creo Parametric comes by default without fastener or standard parts library most of us had to download/make those by our self. Major problem is that you have to download different part for different standard and size so in the end you end up with huge pile of files. And every time you start new assembly you have to add those parts in given folder or use link to library via search.pro/config.pro. Last few years I`ve made lets say "compressed" fastener library made up of only 3 files/parts. Basicly you have screw,nut and washer part and each one is actualy one big family of parts.

So now you can just copy these 3 in working folder and you are done.

Supported standards and dimensions of fasteners are given in PDF file.

All fasteners are given with cosmetic thread by default but real thread can be turned on by unsuppresing "NAVOJ"(Bolt) or "FIZICKI NAVOJ"(Nut) in model tree.

Unfortunately I was too lazy to translate features or parameters from Serbian to English but then again I would have to do it every time I update these parts and enlarge family tables. Also versions of these fasteners I use myself have more standards(Luftnormen for example) in them  but i can`t give those.

Hope you find these usefull...

More standards have been added and some corrections of mistakes found in prior version.

6.7.2014 Update

I enlarged library last time for Creo 2.0 version. On 3.0 fasteners come by default so its a bit redundant except for maybe illustrations because of 3D thread.

In the past, it has been a bother to make proper involute gear teeth on the fly.

I have therefore resorted to "perfect mesh" cylindrical teeth in my gear sets for CAD purposes.

For some reason, these are not practical in the real world, but in CAD, they are easy to manage.

...until I tried a bevel gear, that is.

Rather than get into a long conversation about how the geometry is defined, I opted to provide the model and let you take a look for yourself.

Please post comments as questions arise and I will reply in the comments below.

The attached ZIP file has the appropriate assembly, part model, animation file, and mechanism file.

click on the small image to start the animation

Enjoy.

I finally got this...  Obviously math is -not- my strong suit.

"Unwrapping a string from a cylinder..."

The sketch will show you the basis of the formula.  The curve equation is stand-alone from the sketch.

Creo 2.0 attached

YouTube link

Attention:You will need to update your browsers Flash Player plugin to see videos on this site.

Update your Flash Player here. Its free and fast.

Since Creo Parametric comes by default without fastener or standard parts library most of us had to download/make those by our self. Major problem is that you have to download different part for different standard and size so in the end you end up with huge pile of files. And every time you start new assembly you have to add those parts in given folder or use link to library via search.pro/config.pro. Last few years I`ve made lets say "compressed" fastener library made up of only 3 files/parts. Basicly you have screw,nut and washer part and each one is actualy one big family of parts.

So now you can just copy these 3 in working folder and you are done.

Supported standards and dimensions of fasteners are given in PDF file.

All fasteners are given with cosmetic thread by default but real thread can be turned on by unsuppresing "NAVOJ"(Bolt) or "FIZICKI NAVOJ"(Nut) in model tree.

Unfortunately I was too lazy to translate features or parameters from Serbian to English but then again I would have to do it every time I update these parts and enlarge family tables. Also versions of these fasteners I use myself have more standards(Luftnormen for example) in them  but i can`t give those.

Hope you find these usefull...

More standards have been added and some corrections of mistakes found in prior version.

6.7.2014 Update

I enlarged library last time for Creo 2.0 version. On 3.0 fasteners come by default so its a bit redundant except for maybe illustrations because of 3D thread.

Creates note test that, when pasted, gives Session ID for those items in the given range of IDs.

Ever have windows that are always in the way or hide? The following AutoIt program is a basis for creating a custom solution to your problem. You can start it up and leave it running while using Pro/E or Creo or any other programs you like. It isn't very smart, but it doesn't do very much, except be convenient.

It has three functions, based on window name: Move a window to a certain spot, ask the window to close, and activate the window (which should bring it out of hiding)

It has a variable, $delay, that sets how fast it runs through a list you create of window titles. By default it is once per second.

It has the ability to select whether you mean windows with a specific name or those based on a partial name

It can either just do the action once for each time you run the winmover program or to keep at it

I think it is commented well enough; others may differ on that, so ask questions if you like.

ConsoleWrite is a diagnostic. Those lines can be taken out if you don't need them, but leave them in to see how it works. Comment them if there's a chance of needing them in the future.

The ";", semicolon, is a comment introducer. From there to the end of the line is a comment.

AutoIT is a zero-based array language. Dimension an array with 3 elements and they are numbered 0, 1, and 2.

Note that there can be many windows that meet a poor match choice. It's best not to use the window-close function until you have some practice doing this, particularly when using 'repeat'.

To test it, copy and run it from AutoIt or open the attached file**. Then open Notepad; it should move the window a bit. Then save the Notepad file as winmover_test.txt. The program should close it.

** The attached file can be edited with Notepad. The AU3 suffix tells the AutoIt customized SciTE editor the file type.

If you hammer on this program hard enough, there's a chance it will fail trying to move or close a window that you manage to close first. It does check to see if the window exists at the start of the loop, but if the program is slower than you are, you could beat it. Nothing bad happens. AutoIT will stop the program and give an error message. The program could be three or four times longer to make it more bullet-resistant. Do not use it where loss of life is a concern. Do not base your business on it. It is provided as-is for amusement and educational purposes. Do not attempt high-wire acts involving rabid wild animals or fire.

******************************Start of program, does not include this line***********************************

;Takes a list of window names

;and matching list of coordinates and options

;and waits for windows

$delay = 1000 ;the amount of time to wait for the next sweep

$entries = 3

$winactive = 1 ;flag in win_select_opts to indicate option applies only when active

$i = 0

dim $win_names[$entries]

dim $win_select_opts[$entries][3]

;first opt is title match -exact names or partial, always, or only active?

;second is if it applies only when active

;third is action: 1 = move, 2 = close, 3 = bring to front

dim $win_coords[$entries][2] ; X, Y

dim $win_repeat[$entries] ; Should the window action repeat?

dim $win_done[$entries] ; if true and win_repeat is false, then don't do it again.

;If you want to write a file open/close/validate interface, then go ahead

;Otherwise you'll just have to enter all the data here.

;Besides, you should know what the code does before you use it.

$entry = 0

$win_names[$entry] = "winmover_test.txt - Notepad"

$win_select_opts[$entry][0] = 3; match entire title

$win_select_opts[$entry][1] = $winactive; when active

$win_select_opts[$entry][2] = 2; close the window

$win_coords[$entry][0] = 300

$win_coords[$entry][1] = 500

$win_repeat[$entry] = True

$win_done[$entry] = False

$entry = 1

$win_names[$entry] = "winmover_test.txt - Notepad"

$win_select_opts[$entry][0] = 3; match entire title

$win_select_opts[$entry][1] = 0; active or not active

$win_select_opts[$entry][2] = 1; move the window

$win_coords[$entry][0] = 300

$win_coords[$entry][1] = 500

$win_repeat[$entry] = False

$win_done[$entry] = False

$entry = 2

$win_names[$entry] = "Notepad"

$win_select_opts[$entry][0] = 2; match part of the title

$win_select_opts[$entry][1] = 0; active or not active

$win_select_opts[$entry][2] = 1; move the window

$win_coords[$entry][0] = 300

$win_coords[$entry][1] = 100

$win_repeat[$entry] = true

$win_done[$entry] = False

while 1=1

    for $i = 0 to $entries-1

        Opt("WinTitleMatchMode", $win_select_opts[$i][0])

        ;See help for more advanced match type 4

        ;1 = Match the title from the start (default)

        ;2 = Match any substring in the title

        ;3 = Exact title match

ConsoleWrite($win_names[$i]&@crlf)

        if (false = $win_repeat[$i] and true = $win_done[$i]) then

            ;this action is not supposed to repeat, and have already done this once.

ConsoleWrite("Skipped"&@crlf)

            ContinueLoop

        EndIf

        if WinExists($win_names[$i]) then

ConsoleWrite("Found it " & $i &" "&WinGetTitle($win_names[$i]) &@crlf)

            if $win_select_opts[$i][1] = $winactive Then ; only if the window is active

                if WinActive($win_names[$i]) Then

Consolewrite("It must be active and is"&@crlf)

                    Select

                        case 1 = $win_select_opts[$i][2] ; Move the window

                            WinMove($win_names[$i],"",$win_coords[$i][0],$win_coords[$i][1])

                        case 2 = $win_select_opts[$i][2] ; Close the window

                            WinClose($win_names[$i])

                        case 3 = $win_select_opts[$i][2] ;Bring window to front

                            WinActivate($win_names[$i])

                    endselect

                endif

            else ;don't care if window is active

Consolewrite("It's not active"&@crlf)

                Select

                    case 1 = $win_select_opts[$i][2] ; Move the window

                        WinMove($win_names[$i],"",$win_coords[$i][0],$win_coords[$i][1])

ConsoleWrite("Tried to move the window"&@crlf)

                    case 2 = $win_select_opts[$i][2] ; Close the window

                        WinClose($win_names[$i])

                    case 3 = $win_select_opts[$i][2] ;Bring window to front

                        WinActivate($win_names[$i])

                endselect

            endif

            if (false = $win_repeat[$i]) then

                $win_done[$i] = true

            EndIf

        endif

    Next

    sleep($delay)

wend

Edit 07/25/2014: Please see the linked thread for information on Wrap issues using some equation curves.  Another equation curve approximation error

A not so quick video on the technique of creating springs without fussing with the helical sweep and multiple pitch setting.

I found it difficult to create a good representation of a closed end spring, and also the closed and ground version.

This video shows how to make a closed and ground spring and how to quickly tweak it to the exact shape you want to show.

There are several techniques throughout this video, so don't miss the little detail...

• How to define the initial sketch finding the core diameter vs the known ID or OD.
• How to manage the known parameter.  In this case, the OD, height, and the wire dia. were all known's.
• Using the Coordinate system in the Wrap Section.  You might even opt for sketching in the section starting at the bottom of the cylinder.
• Using Pi*D*No. of Turns to manage the overall swap.
• Remembering to save the hidden layers.
• Tweaking the Wrap Section to maximize accuracy.



Of course, if you make a lot of springs, you want to use more relations to automate this process somewhat.

Hope you find this video useful.  Please -like- this document if you do.

Attention:You will need to update your browsers Flash Player plugin to see videos on this site.

Update your Flash Player here. Its free and fast.

I want make the 2d dimension show as below, how to set up the config file let the basic dimension like this?

working with CREO2M120 / M110

regenerate the model  you get the erroro message internal datum 11113 is unattached from feat 10541

With the inclusion of the welding module we have found that there is no editing possible for the OOTB weld symbols to remove the sequence note from the symbol tail. When we contacted tech support with a case we were told this was intended functionality. The actual squence numbers assigned could vary from the actual production process and many times do.

Prior to the Weld module our weld symbols were 2D symbols on the drawing. Now that we are trying to use the application to have welds in the model we have had to put the model weld annotation features on a layer to hide then duplicate the effort by adding the 2D symbols to the drawing.

We did consider creating the custom weld symbol but that would require regular maintenance and testing with every Creo upgrade.

We would request that Creo product management take the initiative here and edit the ootb symbol to add the sequence as variable text.

Here is a collection of known keyboard accelerators (hotkeys) for Creo Parametric 3.0

This document was generated from the following discussion: Creo 3.0 Keyboard Accelerators (Hotkeys)