Device: SpaceNavigator PE
System: Windows 7 Professional, SP1
Hardware: Intel Core i7-2820QM CPU @ 2.30 GHz, 8 GB RAM, 64-bit OS
Software: Pro/ENGINEER WildFire 4.0, date code M130
I used to run a Magellan SpaceMouse Plus (serial port) on Windows XP (same Pro/E program) with 3DxWare drivers. Had no problems with it, even customized the input to switch the roll and spin axes to match how I was used to using it on old Catia V4 programs.
My work recently upgraded my computer to the current system (described at top) and it doesn't recognize the serial-port SpaceMouse anymore. I upgraded to a Navigator (though, really, I consider this a downgrade since I lost 9 buttons) and it functions ok. Running the Puzzle app in the 3D Mouse Home program shows no issues. However, when I run Pro/E again, the manipulation is jumpy and delayed. Worse, the delay is apparently so pronounced that the view will continue to rotate or pan even after I have let go of the SpaceMouse!
Anyone else have this problem and can recommend a fix?
SpaceNavigator use is jumpy in Pro/E WF4, on Win7 64-bit
Moderator: Moderators
Hello adipesh -
When a model drifts onscreen or moves when you are no longer touching the Space Navigator's cap, the unwanted movement is caused by mis-calibration. To correct it, open the 3Dconnexion ControlPanel and press the Calibrate button. Make sure your Space Navigator is on a flat surface and nothing is touching the cap. You will not see an on-screen confirmation that the process has taken place, but it does re-zero the sensors.
Due to the sensitive nature of the optical sensors, a slight compression of the cap during shipping can cause mis-calibration. As the cap moves back to the original relaxed position the sensor detects this movement and sends the data to the application causing the unwanted movement.You try the Jet Demo to test the behavior of the SpaceNavigator outside of your applications. [Start-AllPrograms-3Dconnexion-Demos-JetDemo] It can be easier to judge calibration results here than in the Puzzle Demo.
With the delay you are seeing in Pro/E, is your document being opened from your local PC or over the network? Do you see this behavior if you open a new document and create a small model ?
The driver release version is shown in the 3Dconnexion Properties window under Help-About.Are you using the current Release 3.15.2 ?
Does the 3Dconnexion Properties window open each time you open a Pro/E document ?
----------------------
Barbara
When a model drifts onscreen or moves when you are no longer touching the Space Navigator's cap, the unwanted movement is caused by mis-calibration. To correct it, open the 3Dconnexion ControlPanel and press the Calibrate button. Make sure your Space Navigator is on a flat surface and nothing is touching the cap. You will not see an on-screen confirmation that the process has taken place, but it does re-zero the sensors.
Due to the sensitive nature of the optical sensors, a slight compression of the cap during shipping can cause mis-calibration. As the cap moves back to the original relaxed position the sensor detects this movement and sends the data to the application causing the unwanted movement.You try the Jet Demo to test the behavior of the SpaceNavigator outside of your applications. [Start-AllPrograms-3Dconnexion-Demos-JetDemo] It can be easier to judge calibration results here than in the Puzzle Demo.
With the delay you are seeing in Pro/E, is your document being opened from your local PC or over the network? Do you see this behavior if you open a new document and create a small model ?
The driver release version is shown in the 3Dconnexion Properties window under Help-About.Are you using the current Release 3.15.2 ?
Does the 3Dconnexion Properties window open each time you open a Pro/E document ?
----------------------
Barbara
[quote="Barbara"]Hello adipesh -
When a model drifts onscreen or moves when you are no longer touching the Space Navigator's cap, the unwanted movement is caused by mis-calibration. To correct it, open the 3Dconnexion ControlPanel and press the Calibrate button. Make sure your Space Navigator is on a flat surface and nothing is touching the cap. You will not see an on-screen confirmation that the process has taken place, but it does re-zero the sensors.
Due to the sensitive nature of the optical sensors, a slight compression of the cap during shipping can cause mis-calibration. As the cap moves back to the original relaxed position the sensor detects this movement and sends the data to the application causing the unwanted movement.You try the Jet Demo to test the behavior of the SpaceNavigator outside of your applications. [Start-AllPrograms-3Dconnexion-Demos-JetDemo] It can be easier to judge calibration results here than in the Puzzle Demo.
[/quote]
Thanks, but I'm not having a case where it's drifting in one direction all the time. It's following the movements I input into the mouse, just taking longer to react to it than it should so that it continues after I let go. Like, if I move it in random circles, it'll keep going in those random circles.
[quote="Barbara"]
With the delay you are seeing in Pro/E, is your document being opened from your local PC or over the network? Do you see this behavior if you open a new document and create a small model ?
The driver release version is shown in the 3Dconnexion Properties window under Help-About.Are you using the current Release 3.15.2 ?
Does the 3Dconnexion Properties window open each time you open a Pro/E document ?
----------------------
Barbara[/quote]
I am working on network models... I'll try pulling up local models next time. The software is all local though, and I never had this problem with my old spacemouse plus.
The properties window does not pop up on its own. I have to open it.
When a model drifts onscreen or moves when you are no longer touching the Space Navigator's cap, the unwanted movement is caused by mis-calibration. To correct it, open the 3Dconnexion ControlPanel and press the Calibrate button. Make sure your Space Navigator is on a flat surface and nothing is touching the cap. You will not see an on-screen confirmation that the process has taken place, but it does re-zero the sensors.
Due to the sensitive nature of the optical sensors, a slight compression of the cap during shipping can cause mis-calibration. As the cap moves back to the original relaxed position the sensor detects this movement and sends the data to the application causing the unwanted movement.You try the Jet Demo to test the behavior of the SpaceNavigator outside of your applications. [Start-AllPrograms-3Dconnexion-Demos-JetDemo] It can be easier to judge calibration results here than in the Puzzle Demo.
[/quote]
Thanks, but I'm not having a case where it's drifting in one direction all the time. It's following the movements I input into the mouse, just taking longer to react to it than it should so that it continues after I let go. Like, if I move it in random circles, it'll keep going in those random circles.
[quote="Barbara"]
With the delay you are seeing in Pro/E, is your document being opened from your local PC or over the network? Do you see this behavior if you open a new document and create a small model ?
The driver release version is shown in the 3Dconnexion Properties window under Help-About.Are you using the current Release 3.15.2 ?
Does the 3Dconnexion Properties window open each time you open a Pro/E document ?
----------------------
Barbara[/quote]
I am working on network models... I'll try pulling up local models next time. The software is all local though, and I never had this problem with my old spacemouse plus.
The properties window does not pop up on its own. I have to open it.
Hello adipesh -
The 3Dconnexion Properties window does not open up on its own - it is correct that you need to open it.
Is the SpaceNavigator plugged in to a USB port on the PC rather than to an extension, adapter or monitor ?
Is the USB port one that is being scanned by network or security software ? If it is, that can cause a delay.
Your IT department would need to create an exception for the 3Dconnexion executable 3dxsrv.exe.
The 3d navigation in Pro/E is part of the application. The 3Dconnexion add-in provides button mapping only in Pro/E. I asked about behavior outside of Pro/E such as in the Jet demo or in a different application only to determine whether the problem you are seeing is specific to Pro/E.
----------------
Barbara
The 3Dconnexion Properties window does not open up on its own - it is correct that you need to open it.
Is the SpaceNavigator plugged in to a USB port on the PC rather than to an extension, adapter or monitor ?
Is the USB port one that is being scanned by network or security software ? If it is, that can cause a delay.
Your IT department would need to create an exception for the 3Dconnexion executable 3dxsrv.exe.
The 3d navigation in Pro/E is part of the application. The 3Dconnexion add-in provides button mapping only in Pro/E. I asked about behavior outside of Pro/E such as in the Jet demo or in a different application only to determine whether the problem you are seeing is specific to Pro/E.
----------------
Barbara