Skip to main content

Filter by idea status

Filter by product

6851 Ideas

CablingArchived

I have been tasked with creating cabling harnesses for a next generation space telescope for NASA at Goddard Space Flight Center.  Our traditional method of harness manufacture is to build a mock up structure, run all the cables on the mock up, and then transfer the harnessing to the actual spacecraft.  With this method we have to do an immense amount of guesswork and add in a lot of extra room to make sure that everything will fit.    As of right now there are many many areas for improvement within the cabling module and Creo itself that I would like to submit for submission.   There is currently no method for making changes to a cable short of deleting it and rerouting it manually.  NOTHING updates parametrically.  This is a massive departure from the way that Creo works and markets itself.  Please change this.   If I run a cable and then have to change the spool or diameter - Delete and Rerun If I run a cable and need to change the end location - Delete and Rerun If the Connector moves, the cable will not reroute properly - It will keep the old route and then "add" another section from the old location to the new location - Delete and Rerun   I would also like to be able to calculate the mass of a cable.   In the photos attached you will see that I created a straight 1,000 mm cable run in order to test the mass calculating capabilits of Creo, I then calculated using Excel what the mass of the cable should be if density is calculated by unit length or unit volume.  I couldn’t obtain results that are in line with what Creo provides.    I then looked around and found different values for density that were reported by Creo, both in the cabling module and the standard module.  I went back and calculated the mass of the cable with the many densities that I found within the module.  I couldn’t get any results that match my own calculations.    Why are there so many different densities?  Shouldn’t it be something that is set once? Is mass something that Creo can actually calculate?  Even in the standard Creo module I oftentimes have to “trick” Creo into giving me a correct mass or have to calculate it myself.  I’ve spoken with many designers here and have been told to not have too much confidence in Creo’s mass reporting function and to always double check or calculate the results yourself. Is there anyone at PTC that knows the cabling module that I can speak with?   I have provided video to PTC showing them these issues.  Please see PTC Technical Support Case #14610212  

Fix the bug in the handling of Search Radii that the programmers says is the way it was intended.Archived

If the Selection Radii are changed from within a design that uses inch units, it causes a rapid spiral to them becoming zero whenever any changes to any of the options are made.    In spite of the statement “Radius dimensions are shown in screen units that do not depend on sheet units and the zoom factor” PTC customer service has verified with the programming team that they actually are metric units. If you look at them with a design sheet open that has inch units, they will be 1/25.4 of the radii you see without any sheets open. If you change the values while in the sheet, the numerical value of the inch dimension will be transferred into the default value without converting it back to millimeters. The next time you open a design, the program reads the numerical value as millimeters and divides it by 25.4 to “convert” it to inches, making it. If you change ANY option (not just the Selection radii), this process happens each time: assuming that the numerical inch values is millimeters and saving it as the option, thus dividing it by 25.4 each time.   The programming team has told the support team that this is working as designed and that you should never change the radii with a design sheet open.   It does appear that closing all design sheets and setting the radii will end the spiral, but this sounds like something was overlooked in the programming (going back several revisions) to not convert the inch units back to millimeters if it is changed with a design sheet open.   I suspect that most people have never seen this because there is little to no need to change the values. I have seen it happen because the values have mysteriously changed, causing issues selecting items with a design sheet open. The typical reaction at that point is to fix it (with the design still open) so that you can continue with your work. That causes the death spiral to get going. The real fix (and expected according to the programming staff) is to save your work and close the design, set the Selection Radii, and then reopen your work.

Sheet metal feature hierachyArchived

In an effort to standardize our sheet metal parts, I have been searching for a bulletproof model structure to accurately and consistently measure the flat state for blank sizes. Our standard practice has always been develop the part model through adding features, unbend, measure, bendback, and an unbend or flat_pattern which is suppressed. (UMBF for short) We then create a family table instance for the flat state that will be used in deliverables, (a drawing for forming operations and flat pattern geometry for export to CAM software)    The issue with this practice is the measurement can be incorrect if features are placed after the "UMBF", the measurement feature references fail or do not regen, or are not oriented correctly to reflect the true OAL and OAW .    The flat state includes measurements, (SMT_FLAT_PATTERN_LENGTH & SMT_FLAT_PATTERN_WIDTH), but can also be incorrect if the flat state is suppressed as the FLAT_PATTERN feature is inherently forced to the end of the model tree.   In the attached files, I added a "Bend Back" feature to keep the SMT_FLAT_PATTERN measurements "live", but the Bend Back failed when it was forced ahead of the FLAT_PATTERN. I re-arranged the features thru  PRO_PROGRAM by cutting and pasting the failed Bend Back feature to the end of the feature list. My family table instance needed for drawings and CAM is created by using the "Create Instance" command under the :Flat Pattern" drop down. I modify the resulting family table instance by removing the default FLAT_PATTERN feature from the table and adding the "Bend Back", which is toggled to a "N" value for the instance.   The relations set the inside bend radius and "material" parameter based on the SMT_THICKNESS as well as evaluate and convert the SMT_FLAT_PATTERN measurements to text strings for use in parameters.   For roughly 6-8 months, I have been using this practice for my sheet metal parts without issue. Parts created in this manner seem more robust than any other modeling techniques I have tried to date. Any Sheet metal feature can be added or removed without the FLAT_PATTERN and resulting measurements failing.   As this has been created in Creo 3.0, I do not know if this functionality has been added in later releases. Feedback of any type is welcome and encouraged as I would like to present this as a company standard practice.