Intermittently not working under Wildfire 3.0

dak · Post by **dak** » Tue May 22, 2007 5:13 pm

Seems to be completely random as I haven't been able to consistently repeat the problem, it's only happened a couple of times. When in Wildfire the controller will just stop responding. My old 4000 use to do the same and the work around to get it responding again was to open another part. This workaround doesn't work with the SpacePilot though...it will just start working again for no apparent reason.

agoenczi · Post by **agoenczi** » Wed May 23, 2007 12:13 am

Hi dak

The first thing I would like to ask to do is a calibration of the device. You have only to click to the button called "Calibrate" in the driver GUI.

If it doesn't help, please let me know.

dak · Post by **dak** » Thu May 31, 2007 8:36 am

Currently not working under WF3.0. Clicking on the Calibrate button does nothing when it's not working.

I'm sure if I restart Wildfire it will start working again. Just annoying to have to reopen the assemblies I'm working on.

agoenczi · Post by **agoenczi** » Sun Jun 03, 2007 11:48 pm

Hi dak,

Which is the release of 3DxSoftware you are working with?

I would like to propose you to remove completely 3DxSoftware (as described here). Finally download the newest 3DxSoftware v3.3.6 (currently available on our driver download page and test your application (Wildfire 3.0) again. This way you eliminate for sure any possible influence of former 3DxSoftware settings.

Fred · Post by **Fred** » Mon Jun 04, 2007 3:42 am

Dak,

Try making a firewall exception rule if you are using win XP.
click start
Control panel
Network connections
right click local area connections
choose properties
choose advanced
settings
exceptions
add program
browse to:
C:\Program Files\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare\
select 3dxsrv.exe
click save

Post by **jwick** » Wed Jun 06, 2007 5:40 am

dak,

Does it stop working after you open the part preview window?

dak · Post by **dak** » Thu Jun 07, 2007 9:02 am

agoenczi wrote:Hi dak,

Which is the release of 3DxSoftware you are working with?

I would like to propose you to remove completely 3DxSoftware (as described here). Finally download the newest 3DxSoftware v3.3.6 (currently available on our driver download page and test your application (Wildfire 3.0) again. This way you eliminate for sure any possible influence of former 3DxSoftware settings.

Thanks agoenczi. I will try this and report back. Current versions

Post by **jwick** » Thu Jun 07, 2007 10:49 am

dak,

Next time it stops working in Pro/E, see if it works in one of the 3Dx demos. If it doesn't, it is probably a hardware or O/S problem. If it works in a demo, it is probably a software problem. There was a problem in the past in which Pro/E would register the wrong window with the driver and then would ignore the events going to that window.

Let us know.

Jim
3Dx Software Development

dak · Post by **dak** » Fri Jun 29, 2007 9:52 am

Ok, it stopped working again in Pro/E. I tried opening another part but still did nothing. The LCD was displaying Pro/ENGINEER Part 1, but the controller had no effect. So I minimized Pro and opened up a part in SolidWorks 2007 and the controller worked fine and displayed SolidWorks in the LCD. So I then closed SolidWorks and maximized Pro/E and still no response. The LCD display no longer read Pro/ENGINEER, instead it read Any Application. So I restarted Pro/E and the controller works fine.

More of a nuisance than anything.

3Dconnexion Forum