Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Add option to unit interpretation so that material properties are left intactArchived

CREO offers two schemes for altering model units: conversion and interpretation. Of these, the conversion option adjusts geometry and model material properties to stay self-consistent, while the interpretation option changes units for both without adjusting either. This means that the interpretation option will alter the material properties, which requires the user to set them up again.   This is especially problematic for organizations that set up models with a default material already assigned. Sometimes users may forget to change the units until they have already started modeling geometry, which requires them to use the unit interpretation option. Current workarounds consist of either using a manual scaling operation or resetting the material properties after unit interpretation. It should also be noted that this process tends to confuse new users, who generally don't expect this behavior.   It would be nice if CREO included a scheme that gave the option to conduct a unit interpretation for model geometry, and a unit conversion for all material parameters.   A specific use case for this scheme would be a user attempting to import a computer chip from a step file. The chip uses units of microns, but CREO imports it into a template using inches. The user would need to interpret the model into microns, and then convert the model to inches. As mentioned before, the current CREO unit change options would prevent the user from setting their material before the unit operations.

3D CABLE ASSY FLAT PATTERN MBD for downstream MAPSB 3D work instructionsArchived

  Today some 3D notes can be used with drawing simplified representations for cable assembly drawings centric fabrication. Would like to suggest harness manufacturing us simplified representations with 3D annotate flat to screen combined views. This would be used on our 3D harness manufacturing flat pattern model process "nail board". Windchill MPMLink author states use combined views for EBOM/MBOM assembly wtPart structure.      "Using simplified representations with combined views on harness cable assembly 3D Annotate functionality" This would allow us to use MBD assembly features designated control characteristic with our 3D flat patterns to support our harness MPMLink fabrication process planning 3D work instruction operation sequences. This uses Creo View / Illustrate    Would like to use annotation tab "flat to screen"; 3D annotations Reference Designation "Feature Name" and/or Ref_DES Dimensions " Designated control characteristics" MPMLink notes Reference Dimensions 3D Notes tolerance, text etc Cabling parameters Pro/E parameters Clamp locations 3D tables .tbl wire list, component list This would help support using Windchill wtParts MAPSB Manufacturing Associated Part Structure Browser with EBOM/MBOM flat pattern assembly visualization process planning. This could remove the drawing from our models using MPMLink process planning.    

Allow further feature types to be moved to the regeneration footerArchived

The regeneration footer concept is very interesting and useful, to have some kind of analysis features to be made only after the model is totally regenerated, like measuring the weight for instance.   Even though the concept is usefull, it could  still be improved, by allowing further feature types to be moved there. Currently, only this types of features could be moved to the regeneration footer:   "To Move Features to the Regeneration Footer You can move the features that are created by default in the active list (in the Model Tree above the Insert Here node) to the Regeneration Footer. These features include the Analysis features, Publish Geometry features, Reference feature, Annotation features."   Only simple features is not enough. I created a group to measure a solid body to always have an up-to-date bounding box dimension for a part. The problem is that the group cannot be moved to the regeneration box, even if uses mosly analysis features. But since i had to create CSYS to measure the external distance to the body, in each of the 3 axis X, Y, Z in both directions, the CSYS cannot be moved to the footer, so, if the group is stuck in the middle of the model tree, it will not have the final body dimensions as intended.   Even extrude features could and should be made possible to be moved to the regeneration feature, for instance, for engraving text on a part, and that regeneration footer extruded feature should / could be automatically supressed when mirroring parts, since we do not want mirrored text in a part. If we could move that engraving feature to the regeneration footer, we could guarantee that a mirrored part would automatically extrude the text correctly, and not in a mirrored direction.   Please see the attached images for clarification:  

Pro/Program incorrect behaviour should be fixedArchived

Currently all the relations and parameters values that we specify get edited out by Creo, converting EVERYTHING to uppercase after we try to use Pro/Program to implement "conditional features". (Suppressed based on parameter values).   Since we have lots of parameters that are String Values, mostly Restriced parameter values, that use a mixture of lower and uppercase letters, all the automation conditions get invalidated, whenever Pro/Program converts everything to uppercase. It should not alter the relation strings, or if it does, it should only convert keywords, like "if" to "IF", but should not touch any strings inside quotes.   If we have a string restricted parameter called "FixedSide" and use a relation:   If ParamA == "FixedSide"   .. Endif   and later Pro/program converts the relation string value to "FIXEDSIDE" like this   IF PARAMA == "FIXEDSIDE"   .. ENDIF   Then we have a problem, since the Restriced Sring Parameter was not converted, and continues to only allow the user to select "FixedSide" and not "FIXEDSIDE"... meaning, all the logic we tried to implement with Pro/Program gets invalidated.   Since there are parameters that we have to use in lowercase, or mixed, upper and lower case, Pro/Program should not convert the "Pro/Program" to all uppercase letters, invalidating most of the relations that deal with string values.    

Consider the possibility of Creating embedded drawings inside a partArchived

Having external file drawings as separate entities inside Creo philosophy is very useful, specially when dealing with large and complex parts and assemblies, where there is a need to eventually share work among several team members, besides allowing operning only the 2D drawing files, when someone will not look into the 3d geometry.   Having said that, there are CAD packages, namely VX, if my memory seves me well, that did allow each part or assembly to have embedded 2D drawings. For small parts and assemblies, or with simple 2D drawings, where the drawings are made by the same user, and there is no need to share work, there are also advantages to have the option of creating an inside part or assembly embedded drawing.   In our case, when trying to implement automation, designing "skeleton" start parts for later deriving 3D geometry to finalize the parts, using a multibody approach, where each body will define the size and positioning of later derived parts, it would be extremely usefull to be able to create inside the part, multiple embedded drawings, where each drawing would 2D detail each "Body" (as a future part), or to 2D detail the whole part, as a conceptual assembly. Since we can use "Save a Copy as" to save the 3D part with a different filename, and edit the bodies dimensions as another "conceptual assembly", it would be a lot easier to manage the associated simple 2D drawings if they were saved inside the part, instead of having to manage that association as external drawing files.   Currently (Creo 7), it's also not easy to detail individual bodies, unless we use layers to hide all the bodies except one. Even with external drawing files, the 2D environment should allow us to select each body (or group of bodies) to be associated with a general view, and it's associated projected views. Solidworks allows that easy selection of the body to be used to detail in 2D.

Multibody improvements in Flexible Modeling Body Move and Boolean operationsArchived

Flexible Modeling Body move operations should have the option to also automatically include "attached" datum axis or datum thread quilts. If that association "axis <---> hole surfaces" and "thread quilt <---> hole surfaces" already exists in Creo database, this should be straightforward to implement. If not, Creo database should be improved to internally keep that association when using the hole or thread hole command. Also, these axis and thread quilts should also be optionally automatically all included when using data sharing features, such as "Merge / Inheritance" or "Copy Geometry". When copying Geometry, if we select a body to copy, we should have the option to include all the body axis and threads, with the option to eventually exclude some unwanted ones.   Also, when doing boolean operation, such as body boolean cut or boolean intersect, in the resulting body geometry should only be included the datum axis and threads belonging to holes surfaces that do not "disapperar" or do not get consumed in the final body to avoid having dangling axis or thread quilts unattached to any solid geometry. Even if we try to manually hide them in a layer, they influence the bounding box of the part, and if new holes are added, we have to constantly have to manually add the new axis and quilts to hide them. It should not be too difficult to create an algorithm that checks if the hole surfaces of a tool body disappear or not after a boolean operation.  

volume roughingAcknowledged

1. Describe the ProblemHi,the tool path of volume roughing sometimes works from the outside to inside (correct) and other time as opposed to or alternate.in these two videos I use the same volume roughing sequence, the only difference is the size of the volume extrusion.First video the tool path is correct. (function() { var wrapper = document.getElementById('lia-vid-6363736141112w658h540r271'); var videoEl = wrapper ? wrapper.querySelector('video-js') : null; if (videoEl) { if (window.videojs) { window.videojs(videoEl).ready(function() { this.on('loadedmetadata', function() { this.el().querySelectorAll('.vjs-load-progress div[data-start]').forEach(function(bar) { bar.setAttribute('role', 'presentation'); bar.setAttribute('aria-hidden', 'true'); }); }); }); } }})();(view in My Videos) (function() { var wrapper = document.getElementById('lia-vid-6363738470112w660h540r728'); var videoEl = wrapper ? wrapper.querySelector('video-js') : null; if (videoEl) { if (window.videojs) { window.videojs(videoEl).ready(function() { this.on('loadedmetadata', function() { this.el().querySelectorAll('.vjs-load-progress div[data-start]').forEach(function(bar) { bar.setAttribute('role', 'presentation'); bar.setAttribute('aria-hidden', 'true'); }); }); }); } }})();(view in My Videos)2. Are you using a workaround?I didn't find it3. What is the use case for your organization?The solution would be to define a direction for the toolpath. It must also respect the parameters CUT_TYPE = CLIMB, UPCUT or ZIG_ZAG.4. What impact does this problem currently have on your organization?All manufacturing, I have to use another sequence that takes longer.