Recently active
In ProManf when a NC sequence is clicked in the model tree the NC sequence is not highlighted on the screen. When there are numerous NC sequence it can become confusing to distinguish the different operations. It would be nice to be able to click on an NC operation in the model tree and the operation will highlight on the model as well.
1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.We design metal stamping die designs 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.While designing, we have several templates, that we add to our designs as sub assemblies. To proper fit those templates, we need to relate to skeleton's planes, axis, surfaces, for that, we need to create copies and replace the references, to the new created copies.4. What is the use case for your organization?Our proposal, is to add those templates, like we add UDF, same methodology, it will speed up the whole process.5. What business value would your suggestion represent for your organization?Most of projects (not only in our organization, or only metal stamping tools), are created by using lot of templates. So if the whole process of inser
Even though I am a little dejected by having about 20 of my ideas "archived" this week, we'll still try to improve the product. IDEA: Connector datasheets provide a pitch value between conductors/contacts for flat ribbons. However, you can't enter that value into the 'thick' field in the spool. Instead, you need to run some crazy calculation to generate that value. Really? https://www.ptc.com/en/support/article/CS263593 If the 'thick' value in the spool doesn't correlate to anything 'physical' then why not just have the value mean the conductor thickness. All we need to do is put in the pitch value and that's it.
If you ask 95% of users that they want to export a paginated table to a CSV file, they will tell you they want it all, not just one paginated segment. this should be the default option. (or at least give us a config to allow us to save the full table as if it is unpaginated i.e. without headers and footers)
Add a configuration setting to control whether or not tooltips (e.g. the small white pop-up boxes) which contain entity/feature information are displayed when the cursor hovers over those types of elements in the graphics area for assemblies, drawings, parts, etc. That new setting should work independently of any other settings for preselection highlighting. A desired outcome is to disable tooltips in the graphics area while retaining preselection highlighting. Displaying entity/feature information elsewhere in the GUI such as the message area/log is acceptable.
1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.My company is a Manufacturing Company, I am a "Project Optimization Engineer PLM" but for you I am a Windchill Administrator and Customizer. My stakeholders are the Windchill and CAD users, many departments of the company.2. What product and version are you currently running?8.13. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.I would like to export pvz informations in other formats to use in third part software. Wrl at this moment don't have attributes.4. What is the use case for your organization?View point 35. What business value would your suggestion represent for your organization?I could integrate Windchill information with creo view and the third part software (custom IOT that can read wrl)
Hello,we would like to use the piping and cabling axtension, but found out that it is really cumbersome to get it to work.We can barely check in a cabling assembly into Windchill.That seems to be due to having modelcheck gatekeeper enabled. That is the only way for us to keep up the quality of our cad models.But it seems necessary to run Modelcheck in another special recursive mode to get it working at all for cabling assemblies. On the opposite we have set up gatekeeper to require Modelcheck regenerate explicit since that is the only mode that catches all errors.Please make the piping and cabling assembly module work well with modelcheck gatekeeper, regardless of its configuration.many thanks
Hello,I want to make a sugestion for the ModelCheck.When i start the ModelCheck, the resulted report gives me detailed list that shows the restrictions and then you can highlight the problematic features. This is very good application and you can save a lot of time, otherwise you have to check every feature one by one.But on the other hand when you decide to go deeper for the failed feature and want to detailed investigation you can highligh, but first you have to try to find the highlighted features. In my opinion this is not user friendly and users are loosing time to find the highligted geometry in complex parts, My suggestion is to add zoom functionality for the failed features, highlight is not eneough. Strange thing is when you make a geometry check it is automatically zooming in for the failed features, so can't you bring and merge this functionality for the ModelCheck results ?Thanks and Best Regards,Serkan ACAROGLUI
Dear Creo Team, let's add a new check for Modelcheck: do the threads of schrew and tapped hole fit together? This check would return an error when detecting screws of M5 built into holes with internal M4 threads, for example. That would make validating designs much faster and easier, especially on changes. In this case, often the change task is done by another person that did not first create the assembly, and all screws and internal threads need to be checked manually. Manual checks take time and are prone to errors. greetings
Please create a function in Pro/TOOLKIT similar to ProOutputFileWrite, but for piping info (ProPipingOutputFileWrite?). The fuction should allow all "info types" (General, Length, BOM, Bend Machine, etc).
Current set of default piping components/fittings located at <creo_load_directory>/text/piping_data/fittinglib/ are valid for Spec-Driven Piping only. These fitting parts are missing datum points witch would enable their use in manual piping. Secondly these fittings have naming conflict in instances. PTC See tech support case: C12412047, C12457308.
Dear Sir, When I am adding screws automatically through IFX, the generated bolt nut is having interferences becuase bolt is modelled on major dia and nut is modelled on minor dia. I have an assemblies where I have more than thousand parts including screws and nuts. When I am adding screws through IFX and doing global interference check, the result is always filled with screw interferences, therefore it is difficult to identify real intereferences. Why dont PTC make the library model nut part with hole major dia and put the cosmetic thread as internal minor dia. I think in this method there would not be any interferences in library part. Regards, Jayanta Sarkar
I opened a case with tech support as explained below:1) create an ecad board design in creo2) create a extruded cut inside the pcb geometry3) export the board into idx file format4) import the idx file in an ECAD SW (Zuken, Cadence, ecc.)5) verify that exported hole is imported as board outline instead ecad holeThis is a big pain if you have an ECAD-MCAD collaboration, because every time an idx file is exchanged between the mechanical and electronic engineer, they have to manually adjust the result of the export.This is the answer i got from second level TS:"Hello Mr TOSIN,I am in charge of this request regarding the export of cuts as holes from Creo Parametric for ECAD part or assembly.SPR 2221054 was reported for such issue and here is the R&D information:“Exporting cuts as holes (using the config option ecad_export_cuts_as_holes set to yes) works in the following manner:For each board cut, it collects its geometry from the board (only what intersects board geometry), and only if
There is an issue regarding schedule for fittings in Specification driven piping.1. Changing Pipe SIZE - OK.Example for a 90 Bend fitting .ptd file:"SCH_RATE" "SIZE" "NSIZE" "BSIZE" "END_TYPE" "NEND_TYPE" "FITT_MODEL_NAME" "WEIGHT""40" "2" "" "" "BW" "" "N004E0504-P281""80" "6" "" "" "BW" "" "N004E0801-P281"This .ptd file works fine and when you change the pipe size from 2 to 6 in the 3D model, then the fitting (90 Bend) is automatically replaced from fitting file N004E0504-P281 to N004E0801-P2812. Changing Pipe SCH_RATE but having same pipe SIZE - NOT OKThis behavior should also work if you only change the SCH_RATE but have same pipe size.Example is a Sweepoflange (Olet fitting):"SCH_RATE" "SIZE" "NSIZE" "BSIZE" "END_TYPE" "NEND_TYPE" "FITT_MODEL_NAME" "WEIGHT""140" "2" "12" "BW" "FLGR" "N021B1104-P888""120" "2" "16" "BW" "FLGR" "N021B1303-P888"SCH_RATE is basically the wall thickness of pipe&fittings. The example doesn't work properly in the 3D model, when you switch
There should be functionality that allows a user to show an annotation or BOM balloon for bundles (or wires/cables) in Pro/Cabling. You can show reference designators on a drawing but there is no automated way to add a note (annotation/balloon) to a bundle on a drawing.
Currently each help segment is just that, a stand-alone segment that if followed directly would not lead to success. The About Configuring ModelCHECK is a good start, as is the ModelCHECK Overview. But it just seems you have to read a bunch of different articles to get the full picture of how it all goes together. Perhaps there is a better way to describe the use of ModelCHECK that doesn't require taking a course.PTC Did this way back in 2001 it looks like at this link: http://support.ptc.com/carezone/tutorials/files/modelcheck. Perhaps a simple updating and expansion of that document would meet this need, and include it with the documentation set or link to it in the help.
Sustainability of the size of adjusted datum plane to an edge even after removing the original edge with cut or solidify.After removing solid, it would be nice to keep the size of a Daum plane adjusted to an edge.Warning message: Reference of datum outline (id 27333) is no longer in geometry; using default.
Hi,ModelCheck can rename features in the modeltree with "PRT_DATUM_RENAME / ASM_DATUM_RENAME", he can also rename layers with "PRT_LAYER_MOVE / ASM_LAYER_MOVE" command.In my company, old models have orientations in German. In our new templates, we did put them in english.However, It would be a good thing to implement a feature that allows to rename the orientations with ModelCheck. This way old models can be entirely "cleaned" with modelcheck out-of the box possibilites.Thanks.
The CREO View ECAD Compare utility is really strong when viewing what's changed in a design. It would be even more powerful to communicate to 3rd parties what's changed between a known version and the latest. The problem is that there is not a good way to generate a human-readable file that really tells you what's changed. Ideally, you would need to take all the changes from a ECAD Compare session, show the graphical A vs. B from CREO View and a quick explanation. We are currently doing this manually by viewing all the changes and take screenshots to build a document that can be shared. It would be great to press a button like "Create Comparison Report as PDF". Then, you can share the PDF with all the changes found through CREO Compare with whoever you want or need to.
In its current form, if a user is inserting a fitting in non-spec-driven piping, a window appears to allow the user to select their desired entry-ports and orientation points. However, this window does not show any of the datums if the model is saved with its layers turned off. Therefore, if the layers are hidden for that model, there is no way for a user to select those coordinate systems or points. Even a CTRL+F does not show results on a first try (a hidden work-around is to force it to find the coordinate systems by manually changing the "look-in", and simply re-selecting the model in the pop-up window.Please change this window to include a model tree and layer tree. This would probably be the easiest way to solve the hidden-layer issue.
Manufacturing: Why has the 3-axis-trajectory no tool kerf ?We have began to program with PTC-Manufacturing in the year 1997.In this time the custom trajectory was the only way to program. I don't know exactly, but I think in Wildfire 1 or 2 came the new 3-axis-trajectory.First we didn't use this way to program, but now we are using Creo2 and we won't use the custom trajectory anymore.The new 3-axis-trajectory became in the meantime a very good tool.But we are missing the tool kerf so much.Please make it possible that we get the tool kerf in the new 3-axis-trajectory.Thank you, Bernd
The symbol_spell check definition from the Creo 2 ModelCheck help says:"Checks drawing symbol for spelling mistakes. If any are found, you can highlight them or highlight an correct them. Also, you can add the word to the dictionary so that ModelCHECK accepts it as correct."Looking on PTC's site document CS191447 says:The check option SYMBOL_SPELL works only for symbols with a variable textPTC's own help files says nothing about it only working for variable text.Even though this check should be considered a bug according to PTC's help files I would like the symbol_spell check to check ALL words in a symbol. It shouldn't matter if it's variable text or not.
Currently in Creo 3.0 you are able to set the color of a manufacturing volume (mold volume/mill volume) in wireframe mode only. While in shaded mode, the volume is blue regardless of the color you set it to.***Give the user the ability to color the manufacturing volume in both shaded and wireframe mode.****
We would like to have a configuration option in ModelCHECK for checking of all family table instances when the generic is checked and when an instance is found in an assembly. This has to be a complete check including all checks that ModelCHECK is set up to preform. DETAILED DESCRIPTION:This is applicable for the following two use cases: 1. When running ModelCHECK on a generic part. A complete check on all family table instances should be preformed. 2. When running ModelCHECK on an assembly containing a part instance. A complete check on the parts generic and all family table instances should be preformed.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.