The option TEMPLATE_SOLIDPART and TEMPLATE_DESIGNASM are used to for the start parts. I've never tried adding it more than once.
START_MODEL_DIR provides a directory for start parts and assemblies. Not sure how they work together.
↧
Re: is there a function that can create a relation in all parts?
↧
Re: is there a function that can create a relation in all parts?
i changed the start model directory and my start parts have many more than just "model_by" and "description". but thats all that shows up in that dialog box.... hmmm there must be a way to add more to that list
↧
↧
Re: is there a function that can create a relation in all parts?
The parameters that show up in that list are the ones that are designated. If you would like more to show up in that list, designate them in the start part.
↧
Re: Removing hidden welds in drawing sections?
This is in third angle projection; the welds ringed in red should be hidden, however I want to keep the welds which SHOULD be visible, rather than hiding them all.
In the end, prior to pdf-ing it, I hid the welds in the model and manually drew in the weld fillet in the right hand view where they should be visible. A bit of a dirty work around, and not something I should have to do!
↧
Re: is there a function that can create a relation in all parts?
Okay, there are multiple things at play here.
First, if you want to add additional parameters to the 'out of the box' start parts, you will need to manually open those cad models, add the parameter, and then save them back to the same directory. There are located in the <loadpoint>\templates directory. Most people don't bother with this but instead build their own templates, store them somewhere else, and then point Creo to these folders/models instead (as Steve mentioned).
Second, if you create a parameter and you want it to automatically show up in the list when create a new part from it, you have to designate it. Simply check the box next to the parameter in the designate column.
↧
↧
Re: How to stamp Creo Drawings
Thanks a alot mahesh...solves my purpose..!!
↧
Re: Removing hidden welds in drawing sections?
Antonius Dirriwachter wrote:
Oh, by hidden do you mean hidden line font? I thought we could do that. I will have another look.
I mean that the welds on the rear side of the workpiece, which the viewer has no line of sight to, should not be seen.
The welds on the front, or viewed side on, which which the viewer does have line of sight to should obviously remain visible.
↧
Re: Removing hidden welds in drawing sections?
Okay, I'm back to using layers then.
↧
Re: Removing hidden welds in drawing sections?
Fair enough, although it seems utterly daft that a function which is so easy to toggle in a general or projection view becomes such a pain in the backside as soon as you turn the view into a section!
↧
↧
Re: How to stamp Creo Drawings
Not in particular - I only know that there has to be an Application that is responsible for displaying the filetype. I would guess that the Application needs an OLE interface as well. There was some paint program that was useful as a target, but I don't recall the name off hand. Also it looks like transparency may not be available using OLE - http://support.microsoft.com/kb/123151 I don't know enough about WMF or DiB to know if they support it, but I'm pretty sure the default BMP does not.
That's why I was leaning towards using Adobe as a place to add the stamp. They seem to handle graphics better than anyone. Though not enough to entice me to sign up for their subscription-only professional Creative Suite. There are other PDF integrators, but I haven't needed to look at them for a while.
Also, it looks like the original poster changed his basis for an acceptable answer, and is going with a drawing symbol. Not unheard of and it works, so that's good.
↧
Re: Removing hidden welds in drawing sections?
You realize, per typical drafting standards, that welds are not depicted anyway? Just the weld symbol. It would be a nightmare amount of work to draw those things so the industry doesn't show welds at all. All that is needed is the label. PTC should rightfully say, don't show them at all on drawings.
I think there is a toggle to turn the weld quilts off and just have a line for the weld symbol. The terms 'Solid' and 'Light; show up in http://help.ptc.com/creo_hc/creo30_pma_hc/usascii/index.html#page/pma/welding/About_Conver_Welding_Geom_Types.html but it doesn't explain the difference. Another place calls them 'surface' and 'light.'
↧
Re: Removing hidden welds in drawing sections?
Did you ever create a section in the assembly with Model & Quilts selected? That's what is supposed to trim out the Quilts that aren't supposed to be seen.
↧
Re: How to get Windchill Part Name and Part Number in Creo Model?
Your question provides a good opportunity to share what I have found out on this topic, and the problems that we have run into. I hope some of this information is helpful. I would be interested to know if other users share any of these views.
On p214-217 of the “Using Creo® with Windchill®” (v10.0 M030, January 2012) manual PTC provide a table of the Preferences related to system attribute mapping and file properties (aka CAD parameters), which lists the following attributes:
PTC_WM_ITERATION
PTC_WM_LIFECYCLE_STATE
PTC_WM_LIFECYCLE
PTC_WM_NAME (currently omitted from our Pro/E files)
PTC_WM_NUMBER (currently omitted from our Pro/E files)
PTC_WM_LAST_CHANGE_NOTE (currently omitted from our Pro/E files)
PTC_WM_CREATED_BY
PTC_WM_CREATED_ON
PTC_WM_IS_DRAWING (currently omitted from our Pro/E files)
PTC_WM_MODIFIED_BY
PTC_WM_MODIFIED_ON
PTC_WM_ORGANIZATION_ID (we get PTC_ORGANIZATION_ID instead)
PTC_WM_PART_NAME (currently omitted from our Pro/E files)
PTC_WM_PART_NUMBER (currently omitted from our Pro/E files)
PTC_WM_PART_REVISION_FOR_DRAWING (currently omitted from our Pro/E files)
PTC_WM_PART_STATE_FOR_DRAWING (currently omitted from our Pro/E files)
PTC_WM_REVISION
We have not changed any of the OOTB preferences for attribute mapping yet in our v10.0 M020 test server, and we assume this is the reason that we only see 9 of the 17 Attributes listed above being added to our Pro/E Wildfire4 files immediately upon Save to Workspace, even though WTParts are being created and associated automatically with the CAD Docs. A similar (but not identical) list of 9 default attributes is shown on the old TAN 118262 https://www.ptc.com/appserver/cs/view/solution.jsp?n=118262. Wouldn't it be nice if PTC kept all TPIs/TANs up to date ?
In addition we see the following 4 extra Windchill system attributes (Parameters) being added automatically in our Pro/E files :
PTC_MODIFIED (listed as Yes/No but drawings display it as True/False)
PTC_WM_LOCATION (the path to Windchill context and folder)
PTC_WM_TEAM
PTC_WM_VERSION (= PTC_WM_REVISION. PTC_WM_ITERATION)
In our test setup we still make use of the “old” PROI_VERSION parameter to display on drawings instead of PTC_WM_ITERATION, as it very usefully shows the +sign (like you see in the Windows title bar) as soon as the file is modified in session (and we have also set the config.pro option dm_emulate_ilink_sys_paramters = yes). The +sign is also shown correctly in the WGM, but for some reason PTC have stopped appending it to PTC_WM_ITERATION and instead suggest we make use of PTC_MODIFIED to indicate if a file has been modified locally and not yet checked-in. Unfortunately this change will require some customisation work to re-instate the original behaviour on our Pro/E drawings if the PROI parameters are ever dropped by PTC in future (eg. to translate the True/False values into “+” / <blank>).
The absence of PTC_WM_NAME seems to be causing us no trouble (yet) as we have set up CAD Doc numbering and naming to use the filename with and without extension respectively, and we have a company convention to give filenames to Pro/E drawings that are the same as their related model (apart from the filename extension, so they are listed adjacent if they both exist), hence we can still use the Pro/E drawing filename parameter &drg_name to display what we’ve set as the model (file)name on the drawing.
On p 55-60 of the “Windchill® Workgroup Manager for SolidWorks® Administrator's and User's Guide” (v10.0, June 2011) it lists the Windchill Default System Attributes as follows :
PTC_WM_REVISION
PTC_WM_PART_NAME (currently omitted from our SW files)
PTC_WM_PART_NUMBER (currently omitted from our SW files)
PTC_WM_NUMBER
PTC_WM_NAME
PTC_WM_ORGANIZATION_ID
PTC_WM_ITERATION
PTC_WM_LIFECYCLE
PTC_WM_LIFECYCLE_STATE
The subsequent section in that manual describes how these can be mapped to non-default File Properties (aka CAD Parameter) in Preference Management. We have not done this yet, and we assume this is the reason that we only see 7 of the 9 Attributes listed above being added to our SolidWorks files immediately upon Save to Workspace, even though WTParts are being created and associated automatically with the CAD Docs.
What I still cannot understand is why PTC chose to provide a much shorter list of Windchill system attributes to the 3rd party CAD applications via the Workgroup Manager. The WGM clearly has the ability to add and populate SolidWorks File Properties with some Windchill system attributes immediately upon a Save to workspace (which is great), but why is the list so limited, and why can’t we add the other ‘standard ones’ via some Preferences ? In particular we want to be able to have these Windchill attributes made available to 3rd party CAD files, without having to resort to customisation :
PTC_WM_CREATED_BY
PTC_WM_CREATED_ON
PTC_WM_MODIFIED_BY
PTC_WM_MODIFIED_ON
PTC_MODIFIED
I've posted this suggestion in the Ideas section (aka enhancement requests) - if you agree, please vote on it
It appear that My Idea was a broken link or hidden from public view (??), so now the URL is appended in the editing comment below !!
You can also try a Search for Idea number 1148.
Whilst that difference between 3rd party WGM’s and the Pro/E WGM might be overcome by customising the DefaultModeledAttributeDelegate.java file, a further difference in behaviour really undermines the credibility of PTC’s claim that “all the WGM’s work in the same way”. In the 3rd party WGM, the value of PTC_WM_ITERATION is bumped up to the next value in the series immediately upon modification of a file, in anticipation of the next check-in !
This makes it much more difficult to distinguish between any prints of work-in-progress drawings and any not-yet-checked-in future version that is almost certainly going to be different – as both will display the same Version number ! I understand we can display Lifecycle states on drawings, and perhaps with some customisation we can also show if the file(s) are checked in or out – but these approaches to solving the problem are a very poor substitute for not having the same attributes and attribute behaviour as we get with Pro/E files. When challenged about this PTC typically say they cannot do as much with 3rd party CAD application API’s (which I accept), but the description given above indicates that they could provide much more similarity between Pro/E and 3rd party CAD application with the existing WGM functionality, if they really wanted to.
On p63-64 of the same manual PTC describe Customizing Existing Windchill Attributes. They say “To create more authoring application parameters, Windchill provides a server-side delegate that can be used to customize the system parameters added to the CAD file upon download.” – and they give a list of reserved Windchill attributes (that relate to the associated WTParts) that the delegate can provide as follows :
SP_WM_PART_REV
SP_WM_PART_ITERATION
SP_WM_PROJECT
SP_WM_VIEW
SP_WM_PART_LIFECYCLE
SP_WM_PART_TYPE
SP_WM_PART_LC_STATE
In addition to these 7 reserved attributes, the sample delegate file also includes these 4 attributes, which you might be able to use or replace :
WT_CADDOC_NUMBER
WT_ASSOCIATED_PART_NUMBER
WT_ASSOCIATED_PART_NAME
ECN_NUMBER
We are only just starting to experiment with customising the ‘download delegate’. If we can get it to work as we want, then I will update this posting.
Message was edited by: Nick Drought - added reference to TAN 118262
Message was edited by: Nick Drought (trying to fix broken URL)
↧
↧
Re: Removing hidden welds in drawing sections?
Doesn't that just section the quilts the cross section cuts through, and the quilts in front of the cross section?
I'll give that another try.
↧
Re: Removing hidden welds in drawing sections?
I asked, because I have done a lot of sections with quilts in them using the Model and Quilts option and it always came out OK. Maybe Simon used it and it didn't work for some reason, but I didn't see that he says so one way or the other.
↧
Re: hai
thanks to all for replaying
↧
Re: Repeat Region Issues
There is a known issue where paginated tables become garbled. It has been resolved in Creo Parametric 2.0 M130. Your issue sounds like it may be related. See SPR 2221135 and article CS170301.
↧
↧
Re: Default Tree Column Configuration
Thanks so much Martin!
↧
Re: Importing DXF files into Isodraw 7.3 M030 not working
Heather,
can you upload some DXF example ?
Martin Hanak
↧
Re: Importing DXF files into Isodraw 7.3 M030 not working
Here is the file I am on about. I have given it a new name and still does not work
↧