Space Navigator PE does not work with Solid Edge V19
Moderator: Moderators
-
- Posts: 4
- Joined: Fri Jan 26, 2007 2:21 am
Space Navigator PE does not work with Solid Edge V19
My new Navigator PE causes Solid Edge 19 to freeze.
I have the most uptodate drivers for the PE - I checked this through the update wizard.
I am uptodate with Windows XP.(SP2)
I have the PE plugged into a USB2 slot.
The symptoms seem the same as thos experianced by other users in other CAD applications.
I have tried the following.
Start a 3D new mode - software freezes.
Open and existing 3D model - software starts but after 1 or 2 minutes freezes.
I even tried to uninstall the PE software but there is a residual element that causes the CAD software to crash.
Probably a registry entry.
SOlid Edge was previosly working faultlessly on this machine.
Please help.
I have the most uptodate drivers for the PE - I checked this through the update wizard.
I am uptodate with Windows XP.(SP2)
I have the PE plugged into a USB2 slot.
The symptoms seem the same as thos experianced by other users in other CAD applications.
I have tried the following.
Start a 3D new mode - software freezes.
Open and existing 3D model - software starts but after 1 or 2 minutes freezes.
I even tried to uninstall the PE software but there is a residual element that causes the CAD software to crash.
Probably a registry entry.
SOlid Edge was previosly working faultlessly on this machine.
Please help.
-
- Posts: 49
- Joined: Mon Dec 04, 2006 2:39 pm
- Location: Rochester, MI.
- Contact:
Soli edge and navigator still not working
Ken,
Yes I do have a firewall but this does not interfere with the navigator working with any other application
Inventor, 3ds max, I-deas AND NX, AliasStudio and Rhino
tony
Yes I do have a firewall but this does not interfere with the navigator working with any other application
Inventor, 3ds max, I-deas AND NX, AliasStudio and Rhino
tony
Robert,
What Ken is referring too is Create a Firewall exception rule.
If you are just running Windows Xp firewall here are the instructions.
click start,
Control panel
Network Connections
Right click on Local area connection
Choose properties
Select Advanced
Settings
Exceptions
Check the list to see if a 3dxsrv.exe file is listed
if it is check the box.
If not choose
add program
the file path is
C:/program files/3dconnexion/3dconnexion 3dxware/ 3dxware/3dxsrv.exe
If you are using any other type of firewall the app should have a similar step.
What Ken is referring too is Create a Firewall exception rule.
If you are just running Windows Xp firewall here are the instructions.
click start,
Control panel
Network Connections
Right click on Local area connection
Choose properties
Select Advanced
Settings
Exceptions
Check the list to see if a 3dxsrv.exe file is listed
if it is check the box.
If not choose
add program
the file path is
C:/program files/3dconnexion/3dconnexion 3dxware/ 3dxware/3dxsrv.exe
If you are using any other type of firewall the app should have a similar step.
-
- Posts: 4
- Joined: Fri Jan 26, 2007 2:21 am
SE19 not working - not affected by firewall settings
Fred,
Thanks for the clarification.
I made exceptions in my firewall software as you suggested and this made no difference.
Is there anybody out there using the navigator SE with Solid Edge 19, I think it would be helpful to compare logfiles,
I have noticed that there are several requests for buttons 1-21 i.e.
________________________________________________
8:59:21.796: UdUi:HandleSyncGet: rec'd SI_SYNC_ITEM_BUTTON_ASSIGNMENT request for button 1
8:59:21.796: UdCtlTransSendSync: AppName=3Dconnexion Interface, sync->opCode=3, sync->itemCode=6
8:59:21.812: mwmtrans:UdTransSendSync: sending SI_SYNC_OP_SET.SI_SYNC_ITEM_BUTTON_ASSIGNMENT: item=6, hashCode=0x225, i=1, n=0
______________________________________________
this goes right through to button 21 like this
______________________________________________
8:59:22.312: UdUi:HandleSyncGet: rec'd SI_SYNC_ITEM_BUTTON_ASSIGNMENT request for button 21
8:59:22.312: UdCtlTransSendSync: AppName=3Dconnexion Interface, sync->opCode=3, sync->itemCode=6
8:59:22.328: mwmtrans:UdTransSendSync: sending SI_SYNC_OP_SET.SI_SYNC_ITEM_BUTTON_ASSIGNMENT: item=6, hashCode=0x225, i=21, n=-1
_______________________________________________-
The next few lines report back that an unexpected number of buttons was encountered and then the software freezes, the end of the log is shown below but some of the termination maessgaes may be related to me shutting down Solid Edge through the task manager.
_______________________________________________________
8:59:22.343: Udui:HandleSyncSet: Set ButtonAssignment: 2 to -26006
8:59:22.343: Udui:HandleSyncSet: Set ButtonAssignment: 1 to -26006
9:2:43.609: Udui:HandleSyncSet item: SI_SYNC_ITEM_INFO_LINE, duration=-1, string=Solid Edge Assembly 0
9:2:43.625: Udui:HandleSyncSet: Set ButtonAssignment: 2 to 40
9:2:43.640: Udui:HandleSyncSet: ButtonName: 1 is Fit View
9:2:43.640: UdUiApp::RebuildOneButtonList: Unexpected Button Number
9:2:43.656: UdUiApp::RebuildOneButtonList: Unexpected Button Number
9:2:43.671: Udui:HandleSyncSet: Set ButtonAssignment: 1 to 0
9:6:13.203: UdUi:TlReadConfigFile: Reading file: C:\Documents and Settings\robertac\Application Data\3Dconnexion\3DxWare\profiles\user03.scg
9:6:13.234: UdUi:TlReadConfigFile: Reading file: C:\Documents and Settings\robertac\Application Data\3Dconnexion\3DxWare\profiles\user03.scg
9:6:13.281: UdCtl: Closed application 3Dconnexion Interface on protocol 0.
9:6:13.296: kbdtrans: UdTransClose request made
9:6:13.296: UdCtl: Closed application 3Dconnexion Interface on protocol 50.
9:6:13.312: UdCtl: Closed application 3Dconnexion Interface on protocol 10.
9:18:19.406: UdCtl: Shutting down on 2/17/2007 at 9:18:19.
9:18:19.421: UdTermFocusHook: Error uninstalling hook
9:18:19.421: UdUi->TermDLL: UI DLL About to uninitialize.
9:18:19.453: UdUi->TermDLL: TermDLL Complete
9:18:19.468: UdCtl: UI layer termination completed.
9:18:19.468: kbdtrans: 3DxWare Keyboard transport layer terminated
9:18:19.484: kbdtrans: 3DxWare Keyboard transport layer terminated
9:18:19.500: pxytrans: Proxy transport layer terminated
9:18:19.500: pxytrans: Proxy transport layer terminated
9:18:19.515: s80trans: SpaceWare 8.0 transport layer terminated
9:18:19.515: s80trans: SpaceWare 8.0 transport layer terminated
9:18:19.531: UdCtl: Transport layer termination completed.
9:18:19.531: UdDev: Closing SpaceNavigator on port USB
9:18:24.906: UdCtl: Device layer termination completed.
9:18:24.906: UdCtl: Received WM_DESTROY, shutting down.
9:18:24.921: UdCtl: Termination successful.
9:18:24.937: UdCtl: Shutdown successful.
_________________________________________________________
I compared this to the logfile generated when using UGS I-DEAS 12 (which works perfectly with the navigator - the application element of the log file looks like this.
__________________________________________________________
9:35:53.640: UdArbitrate: New Target: hWnd: 0x11061a, Class Name: I-DEAS Graphics Child, AppName (SiOpen): Unknown, ExeName: ideast.exe
9:35:53.640: UdCtl: Open accepted on protocol 10 for application: Unknown(ideast.exe)
9:35:53.656: mwmtranslog - AppStarts Event Called
9:35:53.656: mwmtranslog - App requested beep
9:35:59.671: UdUi:TlReadConfigFile: Reading file: C:\Documents and Settings\robertac\Application Data\3Dconnexion\3DxWare\profiles\user03.scg
9:35:59.687: UdUi:TlReadConfigFile: Reading file: C:\Documents and Settings\robertac\Application Data\3Dconnexion\3DxWare\profiles\user03.scg
9:35:59.750: UdCtl: Closed application Unknown on protocol 0.
9:35:59.750: kbdtrans: UdTransClose request made
9:35:59.750: UdCtl: Closed application Unknown on protocol 50.
9:35:59.781: UdCtl: Closed application Unknown on protocol 10.
9:36:7.125: mwmtranslog - App sends us its handle under command event
9:36:7.125: UdCtl: Protocol 10 request to open connection for hwnd 0x12061a.
9:36:7.140: UdCtl: App transport list: 9:36:7.140: 50 9:36:7.156: 10 9:36:7.156:
9:36:7.171: UdUi:TlReadConfigFile: Reading file: C:\Documents and Settings\robertac\Application Data\3Dconnexion\3DxWare\profiles\user05.scg
9:36:7.187: UdUi:TlReadConfigFile: Reading file: C:\Documents and Settings\robertac\Application Data\3Dconnexion\3DxWare\profiles\user05.scg
9:36:7.250: UdArbitrate: New Target: hWnd: 0x12061a, Class Name: I-DEAS Graphics Child, AppName (SiOpen): Unknown, ExeName: geomod.exe
9:36:7.250: UdCtl: Open accepted on protocol 10 for application: Unknown(geomod.exe)
9:36:7.265: mwmtranslog - AppStarts Event Called
9:36:7.265: mwmtranslog - App requested beep
9:36:58.781: kbtrans:UdTransSendEvent: Using macroMechanism = 0
9:37:0.203: kbtrans:UdTransSendEvent: Using macroMechanism = 0
9:37:34.265: UdUi:TlReadConfigFile: Reading file: C:\Documents and Settings\robertac\Application Data\3Dconnexion\3DxWare\profiles\user05.scg
9:37:34.296: UdUi->Save: Wrote Config File 9:37:34.296: C:\Documents and Settings\robertac\Application Data\3Dconnexion\3DxWare\profiles\user05.scg9:37:34.312:
9:37:37.875: kbtrans:UdTransSendEvent: Using macroMechanism = 0
9:37:40.109: kbtrans:UdTransSendEvent: Using macroMechanism = 0
9:37:44.328: kbtrans:UdTransSendEvent: Using macroMechanism = 0
9:38:24.343: kbtrans:UdTransSendEvent: Using macroMechanism = 0
9:38:33.734: kbtrans:UdTransSendEvent: Using macroMechanism = 0
9:40:30.031: UdUi:TlReadConfigFile: Reading file: C:\Documents and Settings\robertac\Application Data\3Dconnexion\3DxWare\profiles\user03.scg
9:40:30.062: UdUi:TlReadConfigFile: Reading file: C:\Documents and Settings\robertac\Application Data\3Dconnexion\3DxWare\profiles\user03.scg
9:40:30.109: UdCtl: Closed application Unknown on protocol 0.
9:40:30.125: kbdtrans: UdTransClose request made
9:40:30.125: UdCtl: Closed application Unknown on protocol 50.
9:40:30.140: UdCtl: Closed application Unknown on protocol 10.
__________________________________________________________
This represents the following steps
Start driver,
start application
model a 3d part using navigator for pan, zoom and rotate, and also assign button fuctions to navigator.
Then exit the application.
The problem I face now is that after the dirver is installed for the navigator Solid edge will not work on that machine again whether the driver is load or not.
_________________________________________
My machine is an AMD 2800+ on an Asus motherboard with 1.25GB Ram
and a quadro 750xl graphics card.
Op system is win XP with service pack 2,
Virus software McAfee with firewall.
All device drivers are up to date and windows patches are current.
The same problem occured with Soild Edge 18 AND Solid edge 19.
ALL other 3D applications used work without any glitches with the navigator,
This include:
UGS I-DEAS12
UGS NX3 and NX4
Aurodesk inventor
Autodesk Alias Studio
Rhinoceros 3.0
I teach 3D CAD to a wide range of students and regularly get asked for advice on hardware ( which is why I have persevered with this for so long) I'm pretty sure that most of my students would have disposed of this device by now particularly if it messes with their application running.
Please Help
Regards,
Tony
Autodesk 3D Studio MAx 8.0
Thanks for the clarification.
I made exceptions in my firewall software as you suggested and this made no difference.
Is there anybody out there using the navigator SE with Solid Edge 19, I think it would be helpful to compare logfiles,
I have noticed that there are several requests for buttons 1-21 i.e.
________________________________________________
8:59:21.796: UdUi:HandleSyncGet: rec'd SI_SYNC_ITEM_BUTTON_ASSIGNMENT request for button 1
8:59:21.796: UdCtlTransSendSync: AppName=3Dconnexion Interface, sync->opCode=3, sync->itemCode=6
8:59:21.812: mwmtrans:UdTransSendSync: sending SI_SYNC_OP_SET.SI_SYNC_ITEM_BUTTON_ASSIGNMENT: item=6, hashCode=0x225, i=1, n=0
______________________________________________
this goes right through to button 21 like this
______________________________________________
8:59:22.312: UdUi:HandleSyncGet: rec'd SI_SYNC_ITEM_BUTTON_ASSIGNMENT request for button 21
8:59:22.312: UdCtlTransSendSync: AppName=3Dconnexion Interface, sync->opCode=3, sync->itemCode=6
8:59:22.328: mwmtrans:UdTransSendSync: sending SI_SYNC_OP_SET.SI_SYNC_ITEM_BUTTON_ASSIGNMENT: item=6, hashCode=0x225, i=21, n=-1
_______________________________________________-
The next few lines report back that an unexpected number of buttons was encountered and then the software freezes, the end of the log is shown below but some of the termination maessgaes may be related to me shutting down Solid Edge through the task manager.
_______________________________________________________
8:59:22.343: Udui:HandleSyncSet: Set ButtonAssignment: 2 to -26006
8:59:22.343: Udui:HandleSyncSet: Set ButtonAssignment: 1 to -26006
9:2:43.609: Udui:HandleSyncSet item: SI_SYNC_ITEM_INFO_LINE, duration=-1, string=Solid Edge Assembly 0
9:2:43.625: Udui:HandleSyncSet: Set ButtonAssignment: 2 to 40
9:2:43.640: Udui:HandleSyncSet: ButtonName: 1 is Fit View
9:2:43.640: UdUiApp::RebuildOneButtonList: Unexpected Button Number
9:2:43.656: UdUiApp::RebuildOneButtonList: Unexpected Button Number
9:2:43.671: Udui:HandleSyncSet: Set ButtonAssignment: 1 to 0
9:6:13.203: UdUi:TlReadConfigFile: Reading file: C:\Documents and Settings\robertac\Application Data\3Dconnexion\3DxWare\profiles\user03.scg
9:6:13.234: UdUi:TlReadConfigFile: Reading file: C:\Documents and Settings\robertac\Application Data\3Dconnexion\3DxWare\profiles\user03.scg
9:6:13.281: UdCtl: Closed application 3Dconnexion Interface on protocol 0.
9:6:13.296: kbdtrans: UdTransClose request made
9:6:13.296: UdCtl: Closed application 3Dconnexion Interface on protocol 50.
9:6:13.312: UdCtl: Closed application 3Dconnexion Interface on protocol 10.
9:18:19.406: UdCtl: Shutting down on 2/17/2007 at 9:18:19.
9:18:19.421: UdTermFocusHook: Error uninstalling hook
9:18:19.421: UdUi->TermDLL: UI DLL About to uninitialize.
9:18:19.453: UdUi->TermDLL: TermDLL Complete
9:18:19.468: UdCtl: UI layer termination completed.
9:18:19.468: kbdtrans: 3DxWare Keyboard transport layer terminated
9:18:19.484: kbdtrans: 3DxWare Keyboard transport layer terminated
9:18:19.500: pxytrans: Proxy transport layer terminated
9:18:19.500: pxytrans: Proxy transport layer terminated
9:18:19.515: s80trans: SpaceWare 8.0 transport layer terminated
9:18:19.515: s80trans: SpaceWare 8.0 transport layer terminated
9:18:19.531: UdCtl: Transport layer termination completed.
9:18:19.531: UdDev: Closing SpaceNavigator on port USB
9:18:24.906: UdCtl: Device layer termination completed.
9:18:24.906: UdCtl: Received WM_DESTROY, shutting down.
9:18:24.921: UdCtl: Termination successful.
9:18:24.937: UdCtl: Shutdown successful.
_________________________________________________________
I compared this to the logfile generated when using UGS I-DEAS 12 (which works perfectly with the navigator - the application element of the log file looks like this.
__________________________________________________________
9:35:53.640: UdArbitrate: New Target: hWnd: 0x11061a, Class Name: I-DEAS Graphics Child, AppName (SiOpen): Unknown, ExeName: ideast.exe
9:35:53.640: UdCtl: Open accepted on protocol 10 for application: Unknown(ideast.exe)
9:35:53.656: mwmtranslog - AppStarts Event Called
9:35:53.656: mwmtranslog - App requested beep
9:35:59.671: UdUi:TlReadConfigFile: Reading file: C:\Documents and Settings\robertac\Application Data\3Dconnexion\3DxWare\profiles\user03.scg
9:35:59.687: UdUi:TlReadConfigFile: Reading file: C:\Documents and Settings\robertac\Application Data\3Dconnexion\3DxWare\profiles\user03.scg
9:35:59.750: UdCtl: Closed application Unknown on protocol 0.
9:35:59.750: kbdtrans: UdTransClose request made
9:35:59.750: UdCtl: Closed application Unknown on protocol 50.
9:35:59.781: UdCtl: Closed application Unknown on protocol 10.
9:36:7.125: mwmtranslog - App sends us its handle under command event
9:36:7.125: UdCtl: Protocol 10 request to open connection for hwnd 0x12061a.
9:36:7.140: UdCtl: App transport list: 9:36:7.140: 50 9:36:7.156: 10 9:36:7.156:
9:36:7.171: UdUi:TlReadConfigFile: Reading file: C:\Documents and Settings\robertac\Application Data\3Dconnexion\3DxWare\profiles\user05.scg
9:36:7.187: UdUi:TlReadConfigFile: Reading file: C:\Documents and Settings\robertac\Application Data\3Dconnexion\3DxWare\profiles\user05.scg
9:36:7.250: UdArbitrate: New Target: hWnd: 0x12061a, Class Name: I-DEAS Graphics Child, AppName (SiOpen): Unknown, ExeName: geomod.exe
9:36:7.250: UdCtl: Open accepted on protocol 10 for application: Unknown(geomod.exe)
9:36:7.265: mwmtranslog - AppStarts Event Called
9:36:7.265: mwmtranslog - App requested beep
9:36:58.781: kbtrans:UdTransSendEvent: Using macroMechanism = 0
9:37:0.203: kbtrans:UdTransSendEvent: Using macroMechanism = 0
9:37:34.265: UdUi:TlReadConfigFile: Reading file: C:\Documents and Settings\robertac\Application Data\3Dconnexion\3DxWare\profiles\user05.scg
9:37:34.296: UdUi->Save: Wrote Config File 9:37:34.296: C:\Documents and Settings\robertac\Application Data\3Dconnexion\3DxWare\profiles\user05.scg9:37:34.312:
9:37:37.875: kbtrans:UdTransSendEvent: Using macroMechanism = 0
9:37:40.109: kbtrans:UdTransSendEvent: Using macroMechanism = 0
9:37:44.328: kbtrans:UdTransSendEvent: Using macroMechanism = 0
9:38:24.343: kbtrans:UdTransSendEvent: Using macroMechanism = 0
9:38:33.734: kbtrans:UdTransSendEvent: Using macroMechanism = 0
9:40:30.031: UdUi:TlReadConfigFile: Reading file: C:\Documents and Settings\robertac\Application Data\3Dconnexion\3DxWare\profiles\user03.scg
9:40:30.062: UdUi:TlReadConfigFile: Reading file: C:\Documents and Settings\robertac\Application Data\3Dconnexion\3DxWare\profiles\user03.scg
9:40:30.109: UdCtl: Closed application Unknown on protocol 0.
9:40:30.125: kbdtrans: UdTransClose request made
9:40:30.125: UdCtl: Closed application Unknown on protocol 50.
9:40:30.140: UdCtl: Closed application Unknown on protocol 10.
__________________________________________________________
This represents the following steps
Start driver,
start application
model a 3d part using navigator for pan, zoom and rotate, and also assign button fuctions to navigator.
Then exit the application.
The problem I face now is that after the dirver is installed for the navigator Solid edge will not work on that machine again whether the driver is load or not.
_________________________________________
My machine is an AMD 2800+ on an Asus motherboard with 1.25GB Ram
and a quadro 750xl graphics card.
Op system is win XP with service pack 2,
Virus software McAfee with firewall.
All device drivers are up to date and windows patches are current.
The same problem occured with Soild Edge 18 AND Solid edge 19.
ALL other 3D applications used work without any glitches with the navigator,
This include:
UGS I-DEAS12
UGS NX3 and NX4
Aurodesk inventor
Autodesk Alias Studio
Rhinoceros 3.0
I teach 3D CAD to a wide range of students and regularly get asked for advice on hardware ( which is why I have persevered with this for so long) I'm pretty sure that most of my students would have disposed of this device by now particularly if it messes with their application running.
Please Help
Regards,
Tony
Autodesk 3D Studio MAx 8.0
Hi robertac,
If you open the "About Solid Edge" panel , you will see a list of the "modules" that are available (or "licensed") for use. "Classic" is one of the most common licenses issued for commercial use.What do you mean 'Classic'
We need to know exactly what is the designation of the license. Some Solid Edge licenses have reduced API (add-in) functionality.This is an educational license.
-
- Posts: 4
- Joined: Fri Jan 26, 2007 2:21 am
Hi tony_roberts,
Do note that, as mentioned previously, some Solid Edge licenses limit the functionality (API) available for add-ins which may prevent the use of 3Dconnexion devices.
Thanks. This is what we wanted to know. We only have tested our solution with a "Solid Edge Academic" license. We have requested for a "Solid Edge Academic University" license and, as soon as we have tested it, we will post the results here.The Licence simply says Solid Edge Academic University.
Do note that, as mentioned previously, some Solid Edge licenses limit the functionality (API) available for add-ins which may prevent the use of 3Dconnexion devices.
Hi tony_roberts,
We have received an "academic" license (shown as the module "Solid Edge Academic University" on the application about box) and tested our add-in successfully on SE V19.
We used a system with a similar specification to what we believe you have: Windows XP SP2, Solid Edge V19 (v. 19.00.0066), 3DxSoftware v. 3.1.8, SpaceNavigator.
We have received an "academic" license (shown as the module "Solid Edge Academic University" on the application about box) and tested our add-in successfully on SE V19.
We used a system with a similar specification to what we believe you have: Windows XP SP2, Solid Edge V19 (v. 19.00.0066), 3DxSoftware v. 3.1.8, SpaceNavigator.