Hello, does anyone have advice on how to diagnose the "unable to reference parent objects that are either expressed or modeled away" warning that pops up sometimes, especially as they relate to sketches?
I know they're not necessarily "errors", but they are annoying and I can't find a way to properly diagnose them.
I'm using NX 9, but I had the same issue in NX 8 and I'm sure it applies to other versions of NX.
Mike
Does anyone know if there is a way to show all the named reference sets available within a complete top assembly structure from the first assembly down to the last lowest detail?
So basically show me a list of each part/assembly and then list the reference sets within each of those.
Also is there a way to do that same thing for Arrangements?
Thanks!
I generally tell the user, to think back to what they changed, that could make a face, or some other entity, not exist anymore. Example, a sketch of a square, that is now a triangle...well that side that is no longer there, created some geometry previously.
Stuff like that.
Well, it's a labor intensive solution, but there is always "view dependent edit".
If it was Teamcenter, I'd blame a corrupt cache, but you don't say you use Teamcenter.
I believe load options are logged in the syslog, so it isn't that.
I am *assuming* both users/computers have full read access to the folders/files.
Could be the registry or user.mtx or... is corrupt?
With the user who has problems logged on:
- Exit all NX sessions
- Using regedit, rename the key HKEY_CURRENT_USER\Software\Unigraphics Solutions\NX\(your version)
to something else
- find where the user has their user.mtx file (typically C:\Users\(username)\AppData\Local\Siemens\(your version) - rename that folder as well
- Then try restarting NX & opening the assembly
Another option is see if the "bad" user's "temp" folder(s) have lots of files (100s or 1000s) - try deleting all of the files/folders in their temp folders (NOTE: have the user log off, then log back on, and DO NOT start any applications. Clean up the folder using DOS commands so it keeps going when it encounters files it can't delete. You really should NOT delete temp files while applications are running) I have seen cases where cleaning up temp folders clears a problem.
Hope one (or more) suggestions helps...
How old are these model files? Have they ever been saved since you moved to NX 8.5? I ask because when NX opens a file saved on an older version, it 'converts' it to the new format behind the scenes. If these files are several versions old, you might consider using the 'refile_part' utility to bring them up to the NX 8.5 format; especially if you are using lightweight representations in the assembly.
Also, consider using 'ug_inspect' to scan for file corruption and use the 'examine geometry' command to look for any corrupt geometry within the part.
Ben -
Our IT guy in charge of Office installations is getting me confused.
He says your version (16.0.7070.2026).of Excel 2016 is the "Office 365" version.
The version of Excel 2016 we are installing (with the latest updates from MS) is the "normal" version and is 16.0.4405.1000
So are we OK? Or is MS just 2665 versions behind in releasing patches?
A more confused than normal...Ken
Hello all,
Amature question here. I'm new to my employer and this community as well.
I am working on some issues some of my colleagues have been reporting inside of NX, and noticed we have not participated in downloading any of the "Maintenance Packs" provided by Siemens. I have a few questions, hopefully some of you are able to spread some knowledg on.
We are currently operating on version 9.0.0.19 (We are 48 patches behind)
1. Are the maintenance packs necessary? What are some of your experiences with fucntionality of maintenance packs and do you recommend I update?
2. Do the maintenance packs need to be applied sequentially? (Since we have no patch, will I need to apply them one at a time in order, or can I jump to the latest version)
Any input is appreciated! Thanks!
-Jake
Hi Jake, welcome to the community.
Maintenance Packs (MP) are smaller patches installed on top of Maintenance Releases (MR). There have been 3 MR's for NX9, the newest one being NX9.0.3. The newest MR includes all fixes that were issued with the previous MR's. The newest MP for NX9.0.3 will include all the previous MP fixes for NX9.0.3.
You need to install the MR before the MP.
To bring your version of NX9 up to the newest versions of MR and MP you only need to install the most recently released versions. Thus:
Maintenance Release NX9.0.3
Maintenance Pack NX9.0.3 mp13
Are the maintenance packs necessary? What are some of your experiences with functionality of maintenance packs and do you recommend I update?
Are you experiencing problems with the software? If you are, it's likely they've been fixed in a newer MR or MP.
Regards, Ben
If you are using Teamcenter you can show a column for the transformation matrix. This will show you if a transformation has been applied, but it might be tricky to calculate the actual distance.
Well, if you use the view break method, here is a procedure that will let you "name" the centerline, and then use that name as a selection object in the Linear Dimension dialog box. That way you can hide the centerline (because it is outside the bounds of the view) but still use it to create dimensions.
Create a named centerline, and then hide it:
Now you have a named centerline that you can use to create linear dimensions.
One other MR / MP difference.
MRs are (if I understand correctly) much more "tested" before release than MPs.
So (on occasion) an MP will fix problem A but cause a new problem B.
Therefore, MRs are pretty safe to apply, but you might want to have a strategy to back out MPs (note there is no "easy" way to do that. After installinga base release, e.g. NX9, I make a copy of the entire install folder. Then, if needed, I can copy that (again) and install the MR & MP I want to go "back" to)
Excellent!
Thanks for clearing this up, I couldn't have asked for a better response!
Now I just need to figure out how to go about updating all of our machines system wide!
Best,
Jake
A Maintenance Release is a significant and quality release. Updates to the technical documentation are included, along with enhancements that would not appear in the base release (or MP's). MP's are interim fixes, to be installed while you wait for the next MR. The time between each NX9 MR's was approximately 3 months, whereas MP's were typically quicker. Also, MR NX9.0.3 is the last MR for NX9, so installing an NX9.0.3 MP is the only way to correct fixes for that MR.
Another consideration is End of Maintenance:
http://solutions.industrysoftware.automation.siemens.com/view.php?si=sfb-nx-8110
"End of Maintenance dates for NX Release versions ... represent when Siemens PLM Software will discontinue MP (Maintenance Pack) support and customer specific patches (HF). No further updates or fixes will be issued for the corresponding NX version after these dates."
Regards, Ben
Does anyone have a recommended process/method for installing these updates across an entire environment? (roughly 20 workstations)
also,
Timeframe, downtime, etc..
A software deployment tool would be the best solution to update many systems, there are some freely available like http://wpkg.org
I would at least install the latest MR, so you advance to NX 9.0.3 after that, I would use it for some weeks and see if there are still some issues left.
!!! If NX 9.0.3 is working without problems for you, don't install any MP !!!
If you encounter issues, that you can not easily work-around, check the read-me of the latest MP for the latest MP that contains the fix and apply just that. For example MP9 is the latest MP available, your issue is fixed in MP6 => install MP6 and check if there are any new issues.
If you have multiple issues and one is fixed in MP4, another in MP6 and the last in MP7 => install MP7, since it also included the previous fixes, and check if there are any new issues.
Installing of a MR or MP is usually taking about half an hour without SSD drive and 15 minutes on an SSD drive.
I write install/update scripts for our users to run. You can even make it automatic if you add some logic to a launch script to check for updates before starting the program. I did a presentation on this at the 2016 PLM World conference. Link: http://www.plmworld.org/p/do/sd/topic=1033&sid=7401
In the Move Component window, go to Copy ->Mode -> “Manual Copy” then click “Create Copy”.
Select moving constrains to move the component. With the Settings and other selections, you could have the original component to remain at the original location. Measure and then undo or delete unwanted component.