thanks, guys thanks for the support
appreciate for your help
appreciate for your help
↧
Re: multiple cad file converter
↧
Reuse Library Assembly Clone
Hello,
I've put an assembly which consists of parts and subassemblies under Reuse Library and made a KRX file of the top assembly.
When I try to clone it, the parts and assemblies are made unique but the parts under the subassemblies are still referenced to the library parts.
I would like to make a a completely unique clone that is stand alone from the original file.
I'm new to NX and would appreciate guidance.
Thank you
↧
↧
Re: Populating title block with Material and Weight
Thanks, so this is what I am going to propose we import:
{ Dataset type="UGMASTER"
"DB_PART_NAME" : Item.object_name /write_once /description="Part Name"
"DB_PART_DESC" : Item.object_desc /write_once /description="Part Description"
{ Item type="CGR4_Item"
"site" : Item.cgr4_Site /description="site"
"Year" : Item.cgr4_Year /description="Year"
"SectionComplex" : Item.cgr4_SectionComplex /master=iman /description="cgr4_SectionComplex_toNX"
"MeasuredWeight" : ItemRevision.cgr4_MeasuredWeight /master=iman /description="Measured Weight"
"Materialdetail" : ItemRevision.cgr4_Materialdetail /master=iman /description="Material Detail"
"IPN" : Item.cgr4_IPN /description="Internal Part Number"
"CarType" : Item.cgr4_CarType /description="Car Type"
"NX_Material" : ItemRevision.cgr4_Material /master=cad /description="Material"
}
}
{ Dataset type="UGPART"
# (hard-wired) DB_DATASET_ID : "Part File ID"
# (hard-wired) DB_DATASET_REV : "Part File Rev"
"DB_DWG_TEMPLATE_NX_Mass" : ItemRevision.GRM(IMAN_specification,UGMASTER).NR(UGPART-MASSPR).mass /master=iman /description="Mass (lbm)"
"DB_DWG_TEMPLATE_NX_Weight" : ItemRevision.GRM(IMAN_specification,UGMASTER).NR(UGPART-MASSPR).weight /master=iman /description="Weight (lbf)"
"DB_DWG_TEMPLATE_NX_Area" : ItemRevision.GRM(IMAN_specification,UGMASTER).NR(UGPART-MASSPR).area /master=iman /description="Area (in^2)"
"DB_DWG_TEMPLATE_NX_Volume" : ItemRevision.GRM(IMAN_specification,UGMASTER).NR(UGPART-MASSPR).volume /master=iman /description="Volume (in^3)"
"DB_DWG_TEMPLATE_NX_Density" : ItemRevision.GRM(IMAN_specification,UGMASTER).NR(UGPART-MASSPR).density /master=iman /description="Density (lb/in^3)"
}
↧
Re: Problem with hole callout
Have you achieved to place the dimension with feature parameter in the part attached? I cant, for me, it only shows the diameter but not the thread size.
↧
Export step with assembly structure and only visible parts
Hallo all
I need a solution to export step file with only visible parts on assembly, and i need an assembly structure.
Thanks for help
↧
↧
Re: Losing constraints after moving parts on different level
Have you filed ERs?
↧
Balloon in drawing of parts from assembly
Hello.
I have an assembly. Then I create drawing for that assembly with part list and auto ballon.
Then I create next sheet and I this sheet I make drawing from one part of the assembly. In this drawing I create ballon and here is my problem. What I need to do to get a number this part from part list in this ballon automaticly (associatively) ?
↧
Re: Balloon in drawing of parts from assembly
Did you run update, on the parts list? that should do it.
↧
Re: Losing constraints after moving parts on different level
Regards, Ben
↧
↧
Re: Balloon in drawing of parts from assembly
"and I this sheet I make drawing from one part of the assembly"
How did you create a drawing of this one part? If you added a view from the component part file, this will result in a "drafting component" that will not be recognized by the parts list. In other words, you will not be able to add an automatic balloon to this drawing view if it is a drafting component.
↧
Re: Losing constraints after moving parts on different level
Hi
thank you because I was revising my ER or PR and I didn't found it. Anyway, I searched with this number but I did't find. Can you give me my PR linked to the master ER 5889853 ?
Open :-)... it's easier to win to the lottery ..
↧
Re: Losing constraints after moving parts on different level
↧
Re: Re-attach constraints with errors
Hi
This has already been requested, per ER 6426242: "Ability to map constraints when replacing components".
Regards, Ben
↧
↧
Re: Losing constraints after moving parts on different level
This is why I consider that NX doesn’t take assembly constrains seriously. NX old timers I came across don’t care of about any constrains. They just build the assembly in space and the associative parametric functions are very remote. They avoid, scared or unaware of smart models and assemblies.
I think the constrains demand is coming from new users who migrated from other software and I’m not sure if NX could hear them.
Some of my basic ERs: (Yes they are so basic requirments)
↧
Re: Re-attach constraints with errors
Hi
I didn't open this ER, then I'm not sure at 100% if my request is equal to this ER. Anyway, I will request to be added.
↧
Re: Losing constraints after moving parts on different level
Hi
thank you to share yours ER. I asked to be added to yours.
↧
Re: Losing constraints after moving parts on different level
BenBroad wrote:@cubalibre00, perhaps PR 8252156?
Hi
the PR is a bit different, but always related to constraints.
↧
↧
Re: Problem with hole callout
Hi
in your case I don't have problem using 'Hole callout'.
↧
Re: Problem with hole callout
Hi
I suspect it has something to do with dimensioning an inch thread in a millimeter part file. If I convert the unit of the part to inch (using the ug_convert_part utility) I have no problem using the 'Feature Parameters' command to insert the callouts (using the ansi template), otherwise, like you I only see the diameter values. Here's the result having converted the unit:
I am also able to add the callouts using the Radial Dimension command, with the Method set to "Hole Callout" (without having to change the unit of the file):
Files attached.
Regards, Ben
↧
Re: Re-attach constraints with errors
The ER is one of our more detailed ones and requests a split screen, similar to other mapping techniques, such that the user can see how the constraints were originally applied on one screen and allow the constraints to be reapplied in the adjacent screen.
↧