Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Fix Secondary Dimension from being truncated in Dual Dimensions when display is reversed.Archived

Currently, the secondary dimension is truncated to be able to comply with not exceeding the value permitted by the primary dimension. The problem is that when the dimensions are displayed in reverse ("secondary [primary]"), the values are inherently incorrect.   To further elaborate, we model in SI Units as we work internationally. Bur our parts are fabricated in the US, so we draft with the primary dimensions displayed as Imperial.   For this example, drawing dimensions are shown as .XX +/-.xx [.Y +/-.y] where X is in inches and Y is in millimeters. A modeled dimension of 100 +/- 10 mm currently displays as: 3.9 +/-.3 [100 +/-10]              This is terribly incorrect, as the dimension above would require the displayed secondary dimension tolerance to be truncated to a max of 9 mm to fit within the bounds: * max bound of 109.42 mm = 3.954 + .354 in (this assumes 5 is alway rounded down) * min bound of at 89.05 mm = 3.860 - .354 in   But we want this tolerance to be 10, so the dimension should really display as:3.9 +/-.4 [100 +/-10] * max bound of 111.96 mm = 3.954 + .454 in (this assumes 5 is alway rounded down) * min bound of at 86.51 mm = 3.860 - .454 in NOTE: a tolerance of 11 mm is also acceptable in this range, but the primary displayed as secondary, should continue to be unaltered from it's rounded form.   As another example, a dimension of 110 +/- 11 mm should display as: 4.3 +/-.4 [110 +/-11] * max bound of 122.12 mm = 4.354 + .454 in (this assumes 5 is alway rounded down) * min bound of at 96.67 mm = 4.260 - .454 in   Ideally, an immediate fix - for all builds - would be to round the secondary dimension when it displays as primary dimension (versus truncating it) - this would make it only slightly incorrect, versus how terribly incorrect it is now.   A future build would adjust the secondary dimension displayed as a primary dimension/tolerance to create bounds around the rounded value of the true primary dimension displayed as secondary (essentially reversed from what is currently done to match the reverse display).

Situations in FEA simulation where ProMechModel gives incrrect imprintingAcknowledged

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.We (Novus Nexus) is technical partner to PTC. We developed CAE automation product-CAENexus as an addin/Auxiliary application over Creo using Pro/toolkit API. Our product has been used by some of our common customers using Creo. This issue has been originally reported by John Deere.  I am working as software developer and support engineer for CAENexus.2. What version of Creo Parametric are you currently running? Creo 7.03. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video. CAENexus creates simulation model (imprinted model) as ProToolkit's ProMechModel. The ProMechModel created using Pro/Toolkit API do not create expected imprint model in some geometric situation. To know about these situation in more detail, please find the presentation in attached zip file. 4. What is the use case for your organization? In CAENexus, we create non-manifold model (built over ProMechanica model) to do the meshing and next processes such as exporting FEA solver deck. It would be great if ProMechanica model gives correct imprint model. This will help us to merge the faces/edges/vertices at required locations.  If non-manifold model (built over promechanica model) is correct then meshing will have no failures.5. What business value would your suggestion represent for your organization?Currently if incorrect imprinting model exist (our non-manifold model is built over it) then Deere CAD engineers needs to do trial and error, find some workaround and do the changes so that meshingworks correctly. Again there is no specific method or recipe for it. It all depends on trial and error and fixing it. Hence it will be good if ProMechanica model gives expected imprinting model in the cases mentioned in the presetantion of attached zip file. 

[Eztol]TA item which sensitivity=0 isn’t shown on general reportAcknowledged

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.Chassis designer:use sheetmetal and solid in Creo Parametric & EZTol. 2. What version of Creo Parametric are you currently running?Creo 7.0.3 upgrade to Creo 7.0.83. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.We find some dimension items in Stackup table becomes to sensitivity=0 after we add draft angle and round edge.As the picture“sensitivity0_1003-1.jpg” shown, we can see the sensitivity of Hole83 is ½, and Asm shift Hole83-Shaft81 can be auto-shown in Stackup table.But if we modify the hole and add draft angle and add round edge feature as picture”sensitivity0_1003-2.jpg” shown.Because the plastic hole isn’t parallel with standoff outer diameter surface after to add draft angle and round edge. We have to select the edge on the hinge of the draft angle in the dimension loop.But we can see the sensitivity of Edge76 is 0, not ½.And Asm shift between Edge76 and Shaft77 can’t be auto-run.And these calculation results and Dims are different as below picture shown. After generate report, sensitivity=0 won’t shown on  generate report.We think this shall be a bug in Eztol. We hope PTC can solve this bug.4. What is the use case for your organization?We use Eztol to build TA stackup and generate TA report. But TA report is not only recorded and reviewed by designer, QA and Customers also have to check TA report. So how the TA generate report viewed impacts user experience. 5. What business value would your suggestion represent for your organization?We can push Customer to accept to use EZTol more easily. And we can improve RD efficiency. 

System Information (Information Window) does not list all locations for Configuration Files!Acknowledged

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.We design and manufacture high-end electronics. I am the CAD Manager / PTC SME. Stakeholders for this idea include our Creo user community. 2. What version of Creo Parametric are you currently running?8.0.6.03. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video. Reference Ticket: 16548299   Background: We had an issue with an auxiliary application running in Creo. We checked our protk.dat in the text folder and couldn't find where this was called. We checked the Information Window, by using File>Help>System Information and didn't see anything. The data shown there did not show any other protk.dat file except for the one in the text folder. After a lot of back we found the protk.dat within C:\ProgramData\PTC\Creo8\Plugins. This was news to us.    The Information Window / System Information should show the full list of configuration files loaded, regardless of location. This includes the ProgramData folder. Please have this fixed.4. What is the use case for your organization?Our admins, as well as PTC Support Engineers, utilize the Information Window to help debug and problem solve. If this information does not give us the accurate snapshot of the system, we can be mislead to the problem. It will take much longer to address the problem, which can cause engineering downtime. In addition, we won't be able to use the data shown, for fear that it isn't accurate. This would then be another facet of the tool that needs to be skipped due to it not being fully flushed out.   Thank you5. What business value would your suggestion represent for your organization?It enables us to use this portion of the tool, as it was designed. We can debug and help fix issues that are related to imported files. In addition, it allows PTC Support Engineers to properly diagnose our issues as well.   Thanks!