Hi
Thanks a lot!!
The manual workaround would work. But this is something I would like to avoid.
I also was thinking of a journal, but I have no experience with that.
Do you know if a journal could automatically set all dimension that have a "0" at the second decimal place, the decimal places to 1?
Regards,
Thomas
Thank you very much!! :-)
Regards,
Thomas
Hi dodbrew,
NX has a customer default named 'Pack Components' which decides whether or not multiple instances of same part are need to be shown as packed/unpacked state in assembly navigator.
By default,it is always set to 'ON' so if you want to work in 'Unpacked' mode always,make this default-->OFF.
Thanks
Sachin
Hello All,
I am trying to pattern a feature using the pattern geometry feature but it misses a few of the steps. ie, the subtraction extrude and the punch.
I initially used the pattern feature but that had issues also, and I read on here that it was best to stay away from that if helped.
Anyone have any idea what I am doing wrong?
Thanks
Imports System
Imports NXOpen
Module NXJournal
Sub Main (ByVal args() As String)
Dim theSession As Session = Session.GetSession()
Dim workPart As Part
workPart = theSession.Parts.Work
Dim partDimensions() As Annotations.Dimension
partDimensions = workPart.Dimensions.ToArray
Dim lw As ListingWindow = theSession.ListingWindow
lw.open()
For Each partDimension As Annotations.Dimension In partDimensions
Dim test as string
test = partDimension.ComputedSize
Dim test1 as string
test1 = test.Substring(test.IndexOf("."c) + 1)
Dim test2 as double
test2 = "." & test1
if len(test1) > 8 then
if Not test1.ToString.Contains(".") And Not test1.ToString.Contains(",") And test2 < 1 then '''' when dim values are 10.000000000000001
Dim objects1(0) As NXOpen.DisplayableObject
objects1(0) = partDimension
Dim editSettingsBuilder1 As NXOpen.Annotations.EditSettingsBuilder = Nothing
editSettingsBuilder1 = workPart.SettingsManager.CreateAnnotationEditSettingsBuilder(objects1)
editSettingsBuilder1.AnnotationStyle.DimensionStyle.AngularDimensionValuePrecision = 1
editSettingsBuilder1.AnnotationStyle.DimensionStyle.DimensionValuePrecision = 1
Dim nXObject1 As NXOpen.NXObject = Nothing
nXObject1 = editSettingsBuilder1.Commit()
end if
end if
if Not test.ToString.Contains(".") And Not test.ToString.Contains(",") then '''' when dim values are 10, 50, 65
Dim objects1(0) As NXOpen.DisplayableObject
objects1(0) = partDimension
Dim editSettingsBuilder1 As NXOpen.Annotations.EditSettingsBuilder = Nothing
editSettingsBuilder1 = workPart.SettingsManager.CreateAnnotationEditSettingsBuilder(objects1)
editSettingsBuilder1.AnnotationStyle.DimensionStyle.AngularDimensionValuePrecision = 1
editSettingsBuilder1.AnnotationStyle.DimensionStyle.DimensionValuePrecision = 1
Dim nXObject1 As NXOpen.NXObject = Nothing
nXObject1 = editSettingsBuilder1.Commit()
end if
Next
lw.close()
End Sub
End Module
Hi
Thank you very much!!
I will try that!
Regards,
Thomas
Hi
Delete the faces of hole (extrude 11) instances at locations where linear pattern instances are getting created. And then try 'pattern face'. I think, it'll solve the issue.
Regards,
Amol
Hi Al50991 ,
I have checked the part file you have attached and found that the new pattern geometry created is actually a sheet body,I think that's the reason extrude-subtract failing and not gettting the desired result.
Thanks
Sachin
Hello,
I'm trying to work with Signals in Runtime Behavior.
If I define a Signal called "oeffnen" and try to refer to a Signal in PhysicsNavigator. But the Signal is not accepted.
The same with SignalAdapter works.
Did I define the Signal in Runtime Behavior wrong? (here the signal is binary)
Regards
Andreas
Is it still like this? Do we have any updates this year? Still we can't delete or replace open prt file from nx?
Hi
You'll find a file inside the download package (or/and just beside it if you do not want to download a lot of data just to browse the fixes). It'll be a .csv and a .html.
(I don't know if we've got the right to post the fixes list here..)
Best regards,
Frédéric.
Hi
I always post a link to the release letter which includes a table of fixes that each maintenance pack (MP) includes. MP9 will include the fixes from all previous MP's. Does that help?
Regards, Ben
When updating a feature it seems like the part file wants to go back up into the tree and work it was back down. i know I can turn off delay update but whats causing this. On large models it takes forever to update something.
Hey Thomas,
Thanks for your replay. I can understand NX budget constraints here I am trying to achieve only one thing which is replace prt file with updates, hence need to delete a file. I can add like to not delete file which is open. but, that is not what I need. My crieteria is to delete a file and add new one for that I need this function to be work. Deleting is working so I thought may be I can add now new one with same name but due to cache memory it is not allowing me to do so.
Hard to say the cause w/o data as it's usually highly dependent on the relationships between your features.
There are times where data is not cached and available, or something is marked modified, the system has to re-gen to be sure its up-to-date.
Something that can help some scenarios is having NX cache some Rollback data for you so it is always available and does not have to be re-gen-ed (unless changed).
In older NX releases, we allowed users to control this setting, found in Customer Defaults -> Gateway -> General -> Part -> Save Data for Feature Edit.
Make sure it's set to something other than "None".
The default for NX 11 should not "None", but some customers have chosen to over-rule that setting.
If newly set, the data will be cached the next time features get updated.
Related settings, once you have this cached Rollback data:
CD -> Modeling -> General -> Update ->(1) Load Rollback Data to NX on WP Change and (2) Load to Memory
There is enough benefit to using this data in NX that we removed the CD option to set to "None" starting in NX 12, so it can always be leveraged.
Hopefully this helps some of your cases.
Thanks Pat I will try this. Yeah i understand it bepends on the part. We are getting a lot of bad parts from our customer that would run Playback. I asume this is part of the problem.
Attached is what i have set. would this be correct. running 11
Hi
The last few cases that we [GTAC] had were closed as ER (ER 6608206) and are currently still open. At the time, attribute mapping was attempted and using occurrence notes, but both failed.
I did find the following, which I have not tested:
Alternate IDs are runtime properties on the Item/ItemRevision. These do not map to NX. This is also an issue because there can be multiple alternate IDs on an ItemRevision. Several Enhancement Requests (ER) have been submitted requesting this ability. As a workaround, if only one alternate id is used, the value can be mapped ONLY if the Teamcenter Display Rule is set to display the alternate ID as the ItemID, rather than the Teamcenter ItemID.
The mapping would be as follows:
{ Dataset type="UGMASTER"
# (hard-wired) DB_PART_NAME : "Part Name"
# (hard-wired) DB_PART_DESC : "Part Description"
ALT_ITEM_ID : Item.current_id /master=iman /description="Part Number"
ALT_REV_ID : ItemRevision.current_revision_id /master=iman /description="Part Revision"
}
{ Dataset type="UGPART"
# (hard-wired) DB_DATASET_REV : "Part File Rev"
# (hard-wired) DB_DATASET_ID : "Part File ID"
ALT_ITEM_ID : Item.current_id /master=iman /description="Part Number"
ALT_REV_ID : ItemRevision.current_revision_id /master=iman /description="Part Revision"
}
Please consider contacting GTAC to ask that you're added to the ER.
Regards, Ben
