I just wanted to post a a little helper file for creating internal and external threads based on the Unified Thread Standard (UTS) which covers both English and Metric.

I must give high kudos' to Wikipedia.  I borrowed their images and tables for the attached Creo 2.0 full version parametric file.  You will also find a linked link in the site if you turn on annotation.

See the relations to drive the pitch and diameter you are interested in.  The file is set up for English but you can change it to metric units, if that is your primary usage.  Most everything that can be driven by relations has been.  Only 3 variables are needed... and TPI (thread per inch) is set to zero if you want to define the pitch directly for metric threads.  See the "IF" statement in Relations.

I did have some troubles along the way.  I split up the helical sweep because it -did- fail if I did it in one go although it did not overlap anywhere.  This was customer support's "works as expected" Pro|WorkAround© for helical sweeps that fail otherwise.  This made the file more robust for changing threads on the fly through relations.

Of course, I suggest you make a library part of the two sketches in the file and use them liberally.  Otherwise, the file is a nice quick reference for many thread features.  And if you link into Wikipedia, you will find even more excellent information about this standard.

http://en.wikipedia.org/wiki/Unified_Thread_Standard

http://en.wikipedia.org/wiki/ISO_metric_screw_thread

Here are some of the highlight images from the file... turn off planes and CS' and turn on Annotation, Axes, and Points. 

The images should be saved in the file so no external reference issues should exist.

These are the actual "thread cutters"...

This is the structure of the file...

And I love intelligent parametric sketches...  yes, I have the rounding turned off on purpose.

If you find a serious bug, let me know.  Otherwise, enjoy!

Please Refer: Suggested Technique for Creating Table.pnt files and Setting Default Pens.

REFER ATTACHED PDF

Pro/ENGINEER entities are assigned pens based on the default system colour corresponding to entity type. When entities are plotted, the system uses the line width and line font associated with a particular colour. For example, all entities that appear in Pro/ENGINEER in white are plotted to pen #1, and have the same line width and thickness.

I have currently inherited an assy using a skeleton. Pub Geoms have been created at the skeleton level.

The technique used here was to us copy geoms to pull in the pub geoms from the skeleton into the individual parts...

I would like to find All the refs for a particular feature in the skeleton, this includes any of the parts that may be referencing

this feature via the Pub Geom... So far I have not found a way thru the reference viewer to do so... This includes attempting to do

so from the skeleton itself, and also by trying to work bottom up by invoking the ref viewer at the piece part level.

I cannot seem to get it to break down past the Pub geom in any meaningful way... Ideally I would like to generate a list of parts

and which features in that part.... Any suggestions...

This is a document so please edit it and add, correct, &/or clarify how you see fit.  Then we can all use this as a point of reference when dealing with Repeat Regions/BOM programming.  If you don't want to edit it but still want to contribute, then just leave a comment.  Thanks!

List of System Parameters and Model Parameters used in model/drawing (Document - CS133915):

https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS133915&art_lang=en&posno=10&q=repeat%20region%20symbols&sourc…

List of Operators:

Pro/ENGINEER, Creo Elements/Pro and Creo Parametric

This is one means to create a wound spring.

It uses two graphs: One called Radius and the other called Turns. Pictures of typical graphs are attached. Graphs are a kind of Datum feature.

The centerline of the spring is a datum curve driven by equation using a cylindrical coordinate system. Since I happened to chose an X extent from 0 to 16 in the graphs, the number 16 is used in the relations for the equation. You may choose a different length. You don't have to use the entire graph extent. "t" in the equations is a Pro/E supplied variable that is evaluated over the range of 0 to 1. Unless you want kinks in the spring, keep all transitions between entities in the graph tangent.

r =evalgraph("radius",t*16)

theta = 360*evalgraph("turns",t*16)

z=16*t

Notice that the turns graph changes from 0 to 10 along a straight line. Some other curves are possible, though Pro/E may balk at the next step, creating a solid. Adjustments to accuracy may be required.

The solid (or surface if you like) is created using a variable section sweep. Pick the curve, then select Insert/Variable Section Sweep; sketch the section and it should work.

Notice that the ends of the spring are perpendicular to the centerline allowing addition of straight sections, hooks, and other attachments.

Check the  spring pictures available by changing the graphs.

If you need flat segments or reversals, add a graph for the 'z' component.

When you want to add a part to an assembly, you can browse for it or fill in this part's name.

The problem with this is that you must know what you are looking for. In my experience in many cases its easier to place the name of a part to the clipboard when it's still open and use this when adding this part to an assembly etc.

When you want to create a simple mapkey which copies the name of a part/asm you have open, you are going to fail because for some reason this doesnt work.

I overcome the "copy name" problem by creating a mapkey which does the following:

first create a log-file which contains the name of the current part in the working directory.

Then a batch file with DOS script copies this name to memory and then the log-file is deleted.

Im sure you can do this even more efficient with Pro/Toolkit but I'm not familiar with and I dont know why PTC does not just program these mapkeys themselves.

Do the following steps:

1.

find the path of your working directory (in this case I used "C:\working-directory") and open config.pro with notepad (right mouseclick --> open with..)

2.

paste the following lines in config.pro, replace "C:\working-directory\" with your own path and save.

mapkey cc ~ Command `ProCmdInfoAuditTrail` ;#FILE;\

mapkey(continued) @SYSTEMC:\\working-directory\\clipboard.bat;\

mapkey(continued) @SYSTEMdel C:\\working-directory\\modiflist.inf.*;

3.

paste clipboard.bat in your working directory. Open clipboard.bat with notepad (right mouseclick --> EDIT) and replace "C:\working-directory\" with your own path and save.

4. restart CREO 2.0. The mapkey is activated by pressing "cc" or you can add an Icon that activates the mapkey.

Works like a charm on my system, but I cant guarantee that is works on other machines.

Have you ever needed to create a presentation where you wanted to show fluid flow ?

Here is an interesting technique using mechanism to create a fluid flow simulation.

The idea is simple enough; create a basic "swirl" geometry...

This is a simple helical sweep following whatever shape you want the fluid to follow.  In my case, a simple conic.

Save a copy of your "vane" using the Mirror Part option.

I used an assembly to pattern the single vain. 

For some reason, patterning failed within the part file, so to simplify the overhead I made this assembly and one like it with the mirrored vane.

In the next-level assembly, both the original and the mirror version are assembled on top of each other.

In the Mechanism application, you can use either a motor or a gear connection to rotate these assemblies in opposite directions.

I also applied a glass appearance.  This makes for a profound effect when you use the Shade with Reflections for your annotation.

Just remember that transparency can add a huge overhead to your graphics processing.  The above image has transparency disabled in Options.

Here is the mechanism animation comparing use of lower quality graphics in Shaded mode and HQ settings and Shaded with Reflection selected:

Flow rates are easily managed with Mechanism and volumes can be simulated with the initial geometry.

Remember to use HD setting in YouTube.

Enjoy!

The key to designing better products is operating in an environment where innovation is seamlessly integrated into the design process. The PTC Creo Design Exploration Extension, brand new in PTC Creo 3.0, provides innovative users like you with a dedicated environment to easily and efficiently evaluate new ideas and the impact of design changes. It eliminates the need to manually manage multiple versions of data and allows you to move seamlessly back and forth between these design alternatives during development and review. In today’s post we will discuss how to explore new design concepts, build check point trees, and use the notification center in PTC Creo Design Exploration Extension (DEX).  Moshe Baum, CAD Product Manager, explains more here:

To begin a DEX session, use the file menu to open the ManageSession menu. Hover over DesignExplorationSession and click Start. Name your Design Exploration session and click OK to begin exploring the model and investigating new design ideas. Be sure to create a name that is easily understood at first glance.

For this example, the DEX session is named train_seats_concept_design.

In our model, the arms of a chair are mounted to the back, but they need to be mounted to the base. Within the DEX session, you can freely explore how to change this and save the new design concept as a checkpoint. Simply select the part or assembly that you want to change and click Activate. Use the features in the toolbar to update the model as needed. Click AddCheckpoint and update the CheckpointProperties to save your changes. As you continue to explore more design concepts within the DEX environment, you can build a checkpoint tree, including branches off of individual concepts. This allows you to effortlessly move between check points, eliminating the manual effort typically required.

Create a name for your Checkpoint that is easily understood at first glance, like Original_with_Recline.

Within the DEX environment, you also have access to the full capabilities of PTC Creo Parametric. In this case, using Freestyle to quickly develop freeform surfaces, we can easily change the head supports on the seat and create a new checkpoint. To further develop this concept, we can modify the legs to meet the requirements of the design and save this as a new checkpoint branching off the existing one. Once the final concept is chosen, the checkpoint can be brought forward as the new version of the model. To do so, click the assembly in the Model Tree, hover over Check In, and click Auto to confirm the new version of the model.

Here, we used Freestyle to quickly reshape the headrest on the seat.

Another area where DEX provides significant advantage is in understanding and viewing proposed design changes in a top down design environment. In this case, we are updating a passenger train assembly with a new chair design, then accommodating a customer driven change. You can navigate a sub-assembly in your model for a closer look. When combined with PTC Windchill, PTC Creo Parametric will notify you when newer versions of parts and assemblies are available. To open the NotificationCenter, click the yellow flag at the bottom right hand of your screen and click the notification. The Notification Center provides you with easy to use tools to identify and update changing parts and assemblies in the assembly. Select the models that you want to update to the latest PDM version and click the Update icon as shown in the image. Click Yes in the next dialogue box to update the objects in your work space and session.

In this example, the First Class Seat Assembly and Back require updates.

Our passenger car design also requires an update to accommodate a more streamlined shape. After locating the part in the ModelTree and making the update, we can see that this top level change has a significant effect on the existing assemblies and parts. Typically, to review these changes, you need to accept them and regenerate the entire model without any visibility into the impact. DEX provides a more efficient visual alternative to this workflow. By returning to the notification center at the bottom right of the screen, we can see how our changes impact the model.

Here, you can see that there are now three Outdated Components/Features.

In this case, the top down design change has an unplanned impact on the chair design that must be resolved – specifically the leg geometry. In addition to the NotificationCenter, you are provided with warning icons in the ModelTree next to affected features. Using the new update control, only available with DEX, you can visualize the impact of the changes on your design. Select the parts and assemblies with yellow warning triangles, hover over UpdateControl, and click ShowDifferences. Outdated and changed geometry can now be viewed simultaneously. To make viewing the changes easier, you can click Isolate in the tool bar and select the Outdated or Changed to make things more apparent.

Now you can easily visualize the impact of your design changes.

Using a DEX session, you can further explore the impact of a top down design change on the model without accepting the modifications as final. By doing this, you not only ensure an uninterrupted workflow, you also eliminate the need to create manual backup copies of the data. To start a DEX session, click Explore Update in the toolbar and use the Start a Design Exploration Session dialogue box to name your session. Once in the session, you are able to resolve the changes and move the design forward or determine that the new changes will not work with your design. To move the design forward, click the check mark icon with a plus sign next to the Checkpoint Tree and OK.

Quickly and easily evaluate modifications without creating back-up copies or accepting the changes as final.

To complete the process, you can store your entire DEX session in a lightweight file format. This saves significant time, eliminating the need to load each design version and manage multiple PTC Creo Parametric instances just to review alternative designs. Entire DEX session data can be captured in a single file that can be accessed by other users to review different design alternatives. To access a DEX session that was created by other user – first download its file to the work space, then open it from the File menu. Select Manage Session, Design Exploration Session, click Open, and select the file. To browse different concepts – select desired checkpoint and click Activate.

You can easily locate and activate new design concepts from any of your Model Trees.

To learn more about design exploration in PTC Creo Design Exploration Extension, check out our video tutorial (“PTC Creo Design Exploration Extension Synopsis Demo Video”).

Stay tuned to our “Did You Know” blog series as we cover all of the exciting, new enhancements in PTC Creo 3.0.

For more in-depth product feature explanations, visit our Tech Tips area.

Have some ideas about what PTC Creo product features you’d like to learn more about? Send me a message or leave a comment below and we’ll write up the best ideas from the community. Thanks for reading, looking forward to all of your feedback!

In case you missed it, see what’s new and check out our recent Did You Know posts covering PTC Creo 3.0 enhancements:

1. Fast Facts! Quick Tips for Using PTC Creo - Mechanism Part 1
2. Did You Know? PTC Creo 3.0 Enhancements: Tangency Propagation in PTC Creo Flexible Modeling Extension
3. Did You Know? PTC Creo Advanced Assembly Extension: Concurrent Engineering

Today’s “Fast Facts!” post focuses on creating analyses and measures. This content is intended to provide users with easy-to-use, actionable tips and tricks for how to use PTC Creo more effectively. These tips come from Steve Meyers and Evan Winter, two PTC Creo experts in our training group.

1. Creating Analyses An analysis lets you define conditions for servo motors that move the assembly.   First, select an Analysis type: Position– This option verifies the validity of the mechanism based on defined motors. Kinematic– Use this option to analyze the motion of bodies as a result of defined motor profiles. Dynamic– With this option you can incorporate forces to analyze reactions at connections (e.g. the Normal load on a pin due to gravity and Mass Properties). Next, choose Motors and define the start/end times.

2. Creating Measures A measure allows you to get dynamic information on a component as a result of the Analysis definition (Speed, position, acceleration, etc.). You can also use previously defined analyses to get measurement graphs and values.   To create measurements, click the icon shaped like a new page. Open the measure to give it a new Name and Type. The options include: position, velocity, acceleration, etc. After defining the measurement, click OK or Apply.

Stayed tuned as we cover more PTC Creo commands, features, and shortcuts designed to help you use the product faster!

For more in-depth product feature explanations, visit our Tech Tips area.

Have some ideas about what you’d like to learn more about? Send me a message or leave a comment below and we’ll write up the best ideas from the community. Thanks for reading, looking forward to all of your feedback!

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 just wanted to post a a little helper file for creating internal and external threads based on the Unified Thread Standard (UTS) which covers both English and Metric.

I must give high kudos' to Wikipedia.  I borrowed their images and tables for the attached Creo 2.0 full version parametric file.  You will also find a linked link in the site if you turn on annotation.

See the relations to drive the pitch and diameter you are interested in.  The file is set up for English but you can change it to metric units, if that is your primary usage.  Most everything that can be driven by relations has been.  Only 3 variables are needed... and TPI (thread per inch) is set to zero if you want to define the pitch directly for metric threads.  See the "IF" statement in Relations.

I did have some troubles along the way.  I split up the helical sweep because it -did- fail if I did it in one go although it did not overlap anywhere.  This was customer support's "works as expected" Pro|WorkAround© for helical sweeps that fail otherwise.  This made the file more robust for changing threads on the fly through relations.

Of course, I suggest you make a library part of the two sketches in the file and use them liberally.  Otherwise, the file is a nice quick reference for many thread features.  And if you link into Wikipedia, you will find even more excellent information about this standard.

http://en.wikipedia.org/wiki/Unified_Thread_Standard

http://en.wikipedia.org/wiki/ISO_metric_screw_thread

Here are some of the highlight images from the file... turn off planes and CS' and turn on Annotation, Axes, and Points. 

The images should be saved in the file so no external reference issues should exist.

These are the actual "thread cutters"...

This is the structure of the file...

And I love intelligent parametric sketches...  yes, I have the rounding turned off on purpose.

If you find a serious bug, let me know.  Otherwise, enjoy!