NX is "frozen". Stop button clicked but didn't work. E-sop? Emergency Stop Feature? 1

[ingallspw]

thread561-314412

In the above thread, someone stated a desire to have an emergency stop if you will...

I know there is a "Click Stop to interrupt this operation - Stop" dialog box that pops up but what I am looking on my screen, at this very second, is a grayed out Stop button because I clicked Stop but the arrow is still turning around the NX icon in the upper right but it's still crunching. Its been doing so for over an hour. Yeah... I'm gonna lose some work, so...

How about an E-Stop? I like that NX has a feature that recovers from errors and does not simply crash so maybe the e-stop could force "an error" and cause it to Recover from a serious error but say something nicer like, "Forced user interruption (not recommended). Reverting to recovered model"

Can I get a witness!? ;-)

NX 7.5.5.4
Windows 7

 

[ingallspw]

Or even if NX itself noticed an operation taking an ordinarily long time and then paused for 30 seconds or so to ask the user if they want to continue with the operation.

 

[CAD2015]

Long time ago, Unigraphics had a tool, named "Kill" sesion...........................

MZ7DYJ

 

[ewh]

You could go back to running it on UNIX, where you could easily stop the process without having to shut down the software. Ah, those were the days!



“Know the rules well, so you can break them effectively.”
-Dalai Lama XIV

 

[JohnRBaker]

In the old days, pre-solid modeling, you could always stop UG (except when opening and/or saving files) by holding down 'Ctrl+Shift+L'. After the introduction of Solid Modeling (using the Parasolid kernel) there were situations where this would no longer worked and eventually the keyboard sequence was replaced with the now familiar...

...which will only appear when you're actually able to abort the current NX operation.

Now if what you've described IS happening and can be reproduced, once you kill the NX session using, I assume, the 'Task Manager', save the log-file which will still be in the temp folder and contact GTAC and have them look at what was (or was NOT happening) when NX stopped responding.

Note that for the next version of NX (the one that's coming after NX 8.5) we've made some architectural changes which should allow a user to abort many more different NX operations, and hopefully in a more consistent and reliable manner.

John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Industry Sector
Cypress, CA
Siemens PLM:
UG/NX Museum:

To an Engineer, the glass is twice as big as it needs to be.

 

[ingallspw]

Note that for the next version of NX (the one that's coming after NX 8.5) we've made some architectural changes which should allow a user to abort many more different NX operations, and hopefully in a more consistent and reliable manner.

Sweet music to my ears!!!