Hi,

It is possible to create twisted  and revolved sheet body in nx cad8.5? 

Hi,

Can we save any component as mirror part?

Hi,

 whats  the  Difference between convert to sheet metal and sheet metal from solid body  this option in nx 8.5 

HI,

 can we use spline  create the sheet metal by contour flange tool?

I cant launch wave browser. The error Can't initialize the Java VM appear

NX 10.0.3.5

EXCEPTION:Error code  3600021 in line 635 of D:\workdir\reference\NX1003_5\src\nxjavaldr\no\ind\java_loader.cxx
+++ Can't initialize the Java VM


 EXCEPTION: Error code  3600005 in line 1917 of D:\workdir\reference\NX1003_5\src\syss\no\ind\lmldr.c
+++ Failed to load D:\Siemens\NX10\nxassembly\NxBrowser\server.jar

The installed jre version is 1.7.25

I set the parameters for  JRE:

set UGII_JAVA_HOME=C:\Java\jre7
set UGII_JVM_LIBRARY_DIR=%UGII_JAVA_HOME%\bin\server

But it not resolved error. NX is running in managed mode from TC 10.1.5 wich use  the same  jre 1.7.25

May be NX need one specific  jre version? I tried jre8 but   it also not resolved error.

Additionally I set JVM  options  like a -Xms=1024m -Xmx=1024m but without result

Dear All,

Is it possible to make a table with standard couterbore holes in order to simply place these as feature in a model?

I find it strange and a pity that this is not standard integrated in the hole comment. Now I every time have to look up and change these values manually.

Regards, Michel

Hi,

I imported a STL with two Bodies and try to do an Edge-Blend or Face-Blend but cannot do this. The edge and faces are not selectable. Does someone know if this is possible and, if yes, what I need to do?

Thanks,

Martin

All,

My first post asking for help since joining the forum.

We are using NX11.0.1mp05, TC 10.1.5

I am looking at some issues where we are trying to lower the load times of our large assemblies, we have many assemblies that take up to an hour to load and use. We have big machines with lots of ram, super fast networks and I have spent a lot of time fine tuning where I can. We were running NX8.5 until recently with data in various flavours of lightweight quality.

So we upgraded to NX11.0.1mp01 and I refiled the complete database and force rebuilt all the lightweights to the quality that I wanted. Now some months down the line I am happy to be able to spend some time looking at using lightweights. I remember when this function came out and there was the Insignia dataset that you could play with. 4 hours to load normally and about 6 mins with lightweights. That was in NX native.

But I am getting almost no performance increase, I have tried various timings of a test assembly.

1.Reboot the computer

Start TC

Start NX

Load options in NX set to

• Partial loading on
• Load structure only off
• Lightweight data off
• Load interpart data off
• Allow substitutions on
• Ref sets As Saved

Load the assembly from the TC Navigator. Now the data is in my local cache

2. Reboot the machine

Start TC

Start NX

Load options in NX set to

• Partial loading on
• Load structure only off
• Lightweight data off
• Load interpart data off
• Allow substitutions on
• Ref sets As Saved

Load the assembly from the TC Navigator, record the time

3. Reboot the machine

Start TC

Start NX

Load options in NX set to

• Partial loading on
• Load structure only off
• Lightweight data on
• Load interpart data off
• Allow substitutions on
• Ref sets As Saved

Load the assembly from the TC Navigator, record the time

Compare the times and see that it is approximately 6 minutes whether I use lightweights or not.

I and a few others have tried lightweights on many assembies with no success at all in saving any significant amount of load time. Memory usage is a lot lower and the manipulation, zoom etc is nice and fast with the lightweights. Can you suggest areas where I could explore the load time?

Thanks

Andy

I have one NX license and am the only one that uses it.  NX is currently set up to use a floating license; however, I recently encountered an issue with it (while upgrading) that required almost 4 hours with tech support to resolve.  I'm now wondering whether a node locked license with a dongle would be a better (less error prone) way to go, especially since I'm the only one that uses NX.  I believe that is still an option. Any thoughts?  The issue still isn't fully resolved, but if this is a viable option, I may bring it up with my VAR. 

Thanks for any feedback on this!

Pat

hello,

I would like to hear users opinions about the way NX currently handles legacy parts,
I mean parts in which the material information was manually entered in the MATERIAL
attribute instead of being entered by means of the Assign Material command.

In NX9 these parts have the MATERIAL attribute deleted without any notice, something
very unfortunate as a piece of information is lost without any warning.
What's disappointing is that I didn't find mention of this behaviour in NX9 What's New
or Release Notes, so that change went completely unnoticed here when we migrated to NX9,
which is again unfortunate.

In NX11 an information window warns the user, which is better than NX9, yet the attribute
original content is still lost.

The only solution proposed by Siemens is to disable the automatic material attribute
creation/setting altogether, which doesn't make much sense as NX8.5 handled this case
better : the original attribute content is retained, it cannot be edited manually, yet
it is superseded by the Assign Material command.  This way the original information is
kept yet the material automation is still enabled.
Someone may argue that in NX8.5 if a material was assigned to solid which doesn't
match the attribute content then there is a discrepancy that cannot be fixed, and this
is the reason for the automatic re-sync between attribute and solid information that takes
place in NX9 and beyond (which causes the MATERIAL attribute in legacy parts to be deleted).
Yet, even in NX11 a discrepancy might occur as there are parts that contain multiple materials,
and in that case NX can prompt the user about what to do, so the very same could be done
if a discrepancy is found between attribute and solid information or if there is no solid
information at all, as in the case of legacy parts.

I have submitted an ER (9105047) to have this implemented in NX, and in the meantime I have found
out that an identical ER was submitted by Chrysler earlier and closed as custom hotfix for them.
I wonder why this has not been turned into an enhancement for the general public rather than a
custom fix, as the problem can affects many (me, for one).

I just upgraded to Windows 10 and NX12 is giving me fits with C++ Exceptions dialogs (see the log below).

The NVidia drivers were updated to the latest WIndows 10 ones on both an NVIDIA M3000M and a Titan XP (http://www.nvidia.com/download/driverResults.aspx/86510/ )   Running on either card gives the same problem.

What do you all think?  Do I need to backtrack on Nvidia drivers or is it something else?

*** EXCEPTION: Severe error  69 in line 210 of o:\ugnx120\ip27\src\syss\no\ind\Error_Severe.cxx at Fri Mar  9 13:28:47 2018 Eastern Standard Time
+++ C++ std::exception caught: Unknown exception
[ 1] 7FFB8133CA57                                                              (libsyss) 
[ 2] 7FFB8133C73B                                                              (libsyss) 
[ 3] 7FFB8133D03C                                                              (libsyss) 
[ 4] 7FFB8133D1BC                                                              (libsyss) 
[ 5] 7FFB8288906B                                                              (libdisp) 
[ 6] 7FFBBAA7C1E0                                                              (VCRUNTIME140) 
[ 7] 7FFBBAA72D03                                                              (VCRUNTIME140) 
[ 8] 7FFBCE3E9603                                                              (ntdll) 
[ 9] 7FFB82544F3F                                                              (libdisp) 
[10] 7FFB825445A6                                                              (libdisp) 
[11] 7FFB82544CD6                                                              (libdisp) 
[12] 7FFB825F588A                                                              (libdisp) 
[13] 7FFB826AA952                                                              (libdisp) 
[14] 7FFB826AA22A                                                              (libdisp) 
[15] 7FFB826A9F0C                                                              (libdisp) 
[16] 7FFB70E241D6                                                              (liblwksint) 
[17] 7FFB70E2519A                                                              (liblwksint) 
[18] 7FFB70E260F1                                                              (liblwksint) 
[19] 7FFB818E67D3                                                              (libugui) 
[20] 7FFB818EDC87                                                              (libugui) 
[21] 7FFB818F28D0                                                              (libugui) 
[22] 7FFB818E56F2                                                              (libugui) 
[23] 7FFB818F76C5                                                              (libugui) 
[24] 7FFB818F7F6A                                                              (libugui) 
[25] 7FFB818F4FF6                                                              (libugui) 
[26] 7FFB818E2FE9                                                              (libugui) 
[27] 7FFB81B9CF45                                                              (libugui) 
[28] 7FFB81D1A6FB                                                              (libugui) 
[29] 0000010084FD                                                              (windowsui) 
[30] 00000100D35D                                                              (windowsui) 
[31] 000001009CC0                                                              (windowsui) 
[32] 7FFB8D5301BA                                                              (mfc140u) 
[33] 7FFB8D52FCCE                                                              (mfc140u) 
[34] 7FFB8D52CF6C                                                              (mfc140u) 
[35] 7FFB8D52D344                                                              (mfc140u) 
[36] 7FFB8D3BD471                                                              (mfc140u) 
[37] 7FFBCDDBBC50                                                              (USER32) 
[38] 7FFBCDDBB80B                                                              (USER32) 
[39] 7FFB8B0A911E                                                              (OPENGL32) 
[40] 7FFBCDDBBC50                                                              (USER32) 
[41] 7FFBCDDBB5CF                                                              (USER32) 
[42] 7FFB8D514442                                                              (mfc140u) 
[43] 000000FA3320                                                              (windowsui) 
[44] 000000FA3934                                                              (windowsui) 
[45] 000000FA6513                                                              (windowsui) 
[46] 7FFB818D5B30                                                              (libugui) 
[47] 7FFB81BE4BB7                                                              (libugui) 
[48] 7FFB81B2B6F1                                                              (libugui) 
[49] 7FFBB71E4AA5                                                              (libuginitint) 
[50] 00014000719F                                                              (ugraf) 
[51] 000140003975                                                              (ugraf) 
[52] 00014000B502                                                              (ugraf) 
[53] 7FFBCDD12774                                                              (KERNEL32) 
[54] 7FFBCE3B0D51                                                              (ntdll) >>>> Severe error  69 caught in file "o:\ugnx120\ip27\src\disp\no\ind\Display_FlushApi.cxx" at line number 244>>>> Severe error  69 caught in file "o:\ugnx120\ip27\src\disp\no\ind\dssv2_view_ops.c" at line number 1242>>>> Severe error  69 caught in file "o:\ugnx120\ip27\src\disp\no\ind\dss_view_ops.c" at line number 1066>>>> Severe error  69 caught in file "o:\ugnx120\ip27\src\ugui\no\ind\git.c" at line number 9350>>>> Severe error  69 caught in file "o:\ugnx120\ip27\src\ugui\no\ind\git.c" at line number 7458>>>> Severe error  69 caught in file "SurfaceWnd.cpp" at line number 873&MACRO SUB_SELECT 2>>>> Severe error  69 caught in file "o:\ugnx120\ip27\src\ugui\no\ind\uigblfunc.c" at line number 440>>>> Severe error  69 caught in file "o:\ugnx120\ip27\src\uginitint\no\ind\clink.c" at line number 693&MACRO MESSAGE_BOX -2, Standard C++ exception caught. See system log for details
APP_EXITED_APPLICATION_ENVIRONMENT_CALLBACK_ID UG_APP_GATEWAY.

When working in within an Assembly the Selection Intent is set "Within Work Part Only" as a default.  I have to change it every time to "Entire Assembly".  I know some might like this setting and have reasons for it, but I don't.  I looked through Customer Defaults and could not find any setting related to this.  Am I missing it?  Tried using Command Finder and that did not help.  I asked this question 3 years ago, but was told by Siemens there was no setting I could change.  Please help or could Siemens add a place in Customer Defaults to change it?  I attached a sreen shot showing what I am talking about.  Thank you. 

Is there a setting somewhere where the gap for the dimension adjusts when you hang/stack GD&T below the dimension value?

I can adjust the gap, but it does it equally on both sides.

If add the GD&T the old school way by text it'll drop the line for me, but than I'm using the older way of formating GD&T.

Thanks!

Hi every one,
After activate GC toolkit for gear modeling, i noticed that when i have to thread a solid body into the Thread feature dialog box i can´t find Metric form anymore.

I tried with GB193 form and this contains dimensions equals to ISO metric thread, in any case a would like to find a way to restablish metric thread and that it is available for use it.
Note that the file thd_metric.dat (see attached file) where the parameter for threads are taken apparently was modified after apply GC tool kit, so i took a look to the content of this file (oppened with notepad) and i found that metric parameters are still there, but those are not available for use them, and I found that other parameters also exist, (e.g. GB193, GJB3.4, GJB3.2, etc.).
I thought I can solve this impasse replacing the existing file by the original file, but i don´t have one (the original file).
Please i hope for help.

By the way, after applying GC toolkit all my templates (i.e. model, assy., drawing and sheet templates) were not available for use them for default, so i locate the folder "english" at the rout (C / ProgramFiles / Siemens / NX10/LOCALIZATION / prc / english; and i delete all the contain of this folder (previously made a copy), reestart NX and resolved business.

Thanks in advance.

Josejavier17
Design Engineer
NX10

Hello

How to rename part, part revision and model all in one in NX11+TC11 ?

I now do it like this:

1. In part main TC11 MB3 -> Edit properties -> Name...

2. In part revision TC11 MB3 -> Edit properties -> Name...

3. In 3D part itself TC11 MB3 -> Edit properties -> Name...

I have to change the name in 3 seperate places.

Is there a way to change all at once ?

I finally have the material attribute working here, but now the issue of a part file having multiple local materials, and the wrong one being the primary, has arisen.

As many of you know, if you create a wave link, the material of the parent body of the wave link, will become a local material in the file the link was created.  If you create a few wave linked bodies for reference, and then create the actual part geometry, and forget to explicitly assign it a material, the part file will make one of the wave related materials the primary.  Then, we end up with the wrong material populating the drawing file, and boom, we have a part made of the wrong material.  This would be bad    

Anotehr issue, is when you have multiple local materials, you will get prompted to select one during part load, and if its an assembly, with a lot of parts, the user may not know what part it is refering to, and click ok, inadvertantly changing something they shouldn't.  In the past, I have seen parts get made with the wrong material due to this.

Also running Part Cleanup, with the "Delete All Materials" toggled on, does not delete materials, at least in my testing.  I will contact GTAC on this one.

So, how do other companies deal with making sure there is only 1 material, within the NX part file?  I know there are attributes for MaterialMultipleAssigned, MaterialMissingAssignments, and MaterialPreferred.  Is there any way to use those to help the situation?  Of simply create a limit of one local material per NX model?

I'm sure large companies have a checking system, but this industry does not have that luxury, time and manpower is crucial with very short timelines.  Automating, and making things 'idiot proof' (for lack of a better term) are crucial.

hello everyone

anyone knows if its possible in the xls of the reuseable part, make inter_part expressions like in moldwizard ?

before parameters: placing the "Inter_Part" then in values: the name of part, path and the variable to pass

I'm using NX 12 with SAMCEF solver for 2D FEM problem. When I try to open the solution I get this Error and i don't understand why and how to solve it or where to go to change the file extension.

Once I click "OK" I get this msg:

Thx for your help.

Hi everyone,

I have problem with detecting and removing superimposition of objects in NX assembly. There is any easy tool to investigate it? I hope you'll find some solution.

best regards 

lukipap

Recently updates our material xml file, so we occasionally get this message:

Once I get around to updating them, or get a minion, do the family members have to be updated too, or just the master?