Hi
but don't know how to do the PMI 2d notes in modeling space
Assuming your using the Ribbon UI...
Select the Application tab and make sure PMI is selected.
Select the PMI tab and select "Note" in the Annotation group.
Add your PMI note to your model.
Regards, Ben
This was always a "Good News/Bad News" issue with NX...
The "Good News" is that there are TEN ways to do everything in NX.
The "Bad News" is that NINE of them are perfectly valid.
Stephan --
The easy answer is yes. :-)
Is this close?
I was reluctant to use the ribbon when it was first announced because I am one of the old dogs that doesn't like change. I have used Unigraphics NX continuously since 1984 (33 years and counting). HOWEVER, after seeing how the ribbon can be customized to my needs, then I have loved it. I would hate to go back to the old toolbar UI.
I have had this same conversation with hundreds of NX users since we introduced the ribbon. Nearly all of them have loved the ribbon after I showed them how to modify to suit their needs. There have been one or two users who refuse to admit the new ribbon UI is better than the old, but the vast majority like it.
Thank you for your reply.
Yes, I figured that out too.
I would also like to know where I can find the description of functions available in the function manager? For example STEP(x,x0,h0,x1,h1), I would like to know the meaning of the variables I should put into the function.
Image may be NSFW.
Clik here to view.
We work directly for GM (Tier 1). Found they same problem with with another user here, when I looked at their settings. I didn't install it, so I'm assuming its a license issue or NX was installed incorrectly, see the attached for our licensing bundels
I was working with the program this morning, when suddenly the scroll zoom stopped working. I restarted the program and this error appeared on the screen. I could not solve it by looking at other posts. I attached my ".syslog" in case anyone could help me with it.
I have updated all drivers: motherboard, CPU, GPU etc ... and still not working
System
CPU: Intel i5-4690k
GPU: AMD R9 280X
Motherboard: MSI GD65
Ram: 32GB DDR3
With this type of error, it is best to contact GTAC (or your VAR) as soon as possible.
Hi
I removed your syslog from your post for security reasons.
I'm 99.99% sure it's your graphics driver:
+++ Invalid read from 0000000000000000
rsp: 5fbac0, rip: 7fff6ad896bf, rbp: 5fbb70
rsi: 5fbbd0, rdi: 0
rax: 1001403, rbx: 0, rcx: 0, rdx: 5fbb40
r8: 3, r9: 72cd580, r10: 141b00, r11: 5fbb40
r12: 0, r13: ffffffff910119b5, r14: 5fbb40, r15: e
[ 1] 7FFF6AD896BF (atig6txx)
[...]
[15] 7FFF9E6A8829 (libgraphics_driver)
Your session crashed before any graphics card information was recorded, however, from the above I can see it's an ATI card, but can't tell if it's supported. We have a hardware (graphics card) certification table here so you can see which cards are certified along with their current driver. If you're using a card that is certified, and its driver is the certified driver, consider downloading and installing a newer driver from either your workstation vendor or the graphics card vendor.
If you're still having problems, as
Regards, Ben
I re-read your posts and I wonder if this is related to the "Start in" path defined in your NX shortcut icon. Right click the icon you use when you start NX and choose Properties. On the Shortcut tab you'll find the "Start in" field, which by default is set to the UGII folder in your install path (E.g., "C:\Program Files\Siemens\NX 11.0\UGII\"). Change this to your D:/Family_parts directory and see if that makes any difference. If not, set it back to it's default value.
In my mind, the measuring tool for value input always gives associative results. In mose cases it works fine. But today I find that non-associative result is also possible.
This makes me greatly concerned about the use of measuring tool for value input. Your suggestion would be highly appreciated!
Image may be NSFW.
Clik here to view.
Clik here to view.
Clik here to view.
Clik here to view.
Clik here to view.
Clik here to view.
It seems that Measure within a command can't be associative. Maybe Siemens could consider adding this functionality. Thanks!
For sketch based features where the sketch is internal to the feature, as long as you define explicit dimensions within the sketch, the workflow should be almost the same as in SolidWorks. Look at the following movie:
Dear Ganesh,
Thanks for the reply, am posting a video which will explain you the requirement of mine.
this is the functionalty available in creo. Please let me know the process to do it in NX.
Regards
Manikanda
All the libraries you're looking for are part of MoldWizard and require a mold design license. If you don't have a MoldWizard license you won't have access to any of them. Your option then is to create your own library components or find a 3rd party solution.
Hi Ben,
Thx, that was exactly what I was looking for.
surfactant_pub --
Measurements are one of the areas I look after in NX.
To clarify, measurements within commands most definitely CAN be associative. :-) In fact, they are associative by default. Try similar mesaurements embedded within Extrude or Hole features, and you'll see what I mean.
With that said, there is certainly something odd going on in this specific command. The *first* time you (or I) attempt this offest for the second point, the Point command is creating this odd non-associative value. (I'm seeing what you saw.):
Image may be NSFW.
Clik here to view.
Interestingly, editing the second point and performing the measurement AGAIN actually results in an associtive offset:
Image may be NSFW.
Clik here to view.
Go figure. Given that I don't see that "double-pump" behavior in any other embedded measurement scenarios I've tested, I suspect an anomaly in the Point feature. Submitting an IR there would be very helpful.
I can tell from your Expressions dialog that you're in either NX 11 or NX 12. Out of curiosity, I went back to NX 10 and tested this, and was surprised to find the exact same behavior there -- namely, a non-associative result the FIRST time...
Image may be NSFW.
Clik here to view.
...and the associative result I would expect the second time around:
Image may be NSFW.
Clik here to view.
So this is clearly not a new anomaly. Again, an IR against the Point function would be helpful. (...and feel free to reference this thread in the IR.)
One last thing... Note that the measurements taken from *within* another feature are represented in the expressions dialog differently than measurements taken as their *own* feature. (In fact, they're architecturally slightly different under the hood as well.) Embedded measurements will show up with this black string [which is more susceptible to inadvertent editing] in the formula -- as shown above -- and standalone measurement features will use the blue "system" expression style. (...and as you can see from the NX 10 pictures, this has been true for quite a while.) If you're aiming to remove potential points of failure, creating standalone measurements ahead of time would be a slightly more robust way to construct this.
Thanks for the good observation!