4000 FLX

Questions and answers about 3Dconnexion devices on Windows.

Moderator: Moderators

Post Reply
danmk1984
Posts: 8
Joined: Thu Nov 01, 2007 6:57 am

4000 FLX

Post by danmk1984 »

I know its an old model, but I have just invested in a new machine and was hoping to continue to use my old Spaceball 4000. However I'm having the same problem as posted by Thermocad in May... And although the problem was solved for him, I still have it!

"no 3d motion controller could be detected"

I've followed all the suggestions on the topic, and still no joy. Even specifying the com port as suggested hasn't helped.

Can anyone help?

Thanks
Peter
Moderator
Moderator
Posts: 34
Joined: Tue Dec 05, 2006 5:23 am

Post by Peter »

danmk1984,
You are correct, the SB4000 serial device has not been manufactured for a number of years. While there is still a driver available from www.3dconnexion.com (v2.8.2).....the SB4000 is considered legacy hardware and it is not possible to keep the driver updated.
However, here are several things to look at:
Be certain that the serial cable is connected directly to the serial port on the PC....remember that no adapters of any type can be used.
Test the SB4000 on another PC if possible. It could be that the problem is with the device itself.

Peter
danmk1984
Posts: 8
Joined: Thu Nov 01, 2007 6:57 am

Post by danmk1984 »

Peter

I've got the latest driver from 3D connexion, and I was using the spaceball fine on my last machine, which is why I was hoping to use it again on my new machine. The com port is working fine with no adaptors, and I even get two beeps when the machine is switched on or if I try to run the driver. But every time the controller can't be found.

Is there a way I can tell the machine that the device is there?
jwick
Moderator
Moderator
Posts: 3331
Joined: Wed Dec 20, 2006 2:25 pm
Location: USA
Contact:

Post by jwick »

What's the difference between the old machine and the new machine? x64 / Vista / etc.
danmk1984
Posts: 8
Joined: Thu Nov 01, 2007 6:57 am

Post by danmk1984 »

There is a new motherboard obviously, but it runs the same version of windows.

there is no changes that i can think would effect it. The com port is working, and the ball beeps when the driver is started.

I'm running windows XP and solid edge version 19
jwick
Moderator
Moderator
Posts: 3331
Joined: Wed Dec 20, 2006 2:25 pm
Location: USA
Contact:

Post by jwick »

Your serial port may not be providing enough current to fully power the device. It may be able to beep, but not be able to respond.

Let's find out what the driver thinks. Turn the driver log file on. I think with this old driver you have to pass -log on the command line to 3DxSrv.exe. It should create a 3DxWare.log file in the driver's directory.

Post the first 20-30 lines of that file (it should be quite short)

Jim
3Dx Software Development
danmk1984
Posts: 8
Joined: Thu Nov 01, 2007 6:57 am

Post by danmk1984 »

I've copied the full log file in below.


15:26:17.109: 3DxWare driver startup: 11/5/2007 15:26:17
15:26:17.109: 3DxWare Driver Version 5.9.2 : July 21, 2006
15:26:17.109: -quiet -- disabled
15:26:17.109: -shutdown -- disabled
15:26:17.109: -protocol -- none given. All protocols enabled.
15:26:17.109: -com -- Disabled, using spcware.ini file settings.
15:26:17.109: -dev -- Disabled, using spcware.ini settings.
15:26:17.109: -eps disabled sending each event.
15:26:17.109: -log enabled
15:26:17.109: -logLevel ffffffff
15:26:17.109: -logFile C:\Program Files\3Dconnexion\3Dconnexion 3DxWare\3DxWare.log
15:26:17.109: -searchWarnDlg not enabled
15:26:17.109: -showGUI not enabled
15:26:17.109: -hideGUI not enabled
15:26:17.109: UdCtl: Attempting to find (ID=2057) 'English' locale in EN_GB
15:26:17.109: UdCtl: Found resource DLL in C:\Program Files\3Dconnexion\3Dconnexion 3DxWare\en_us\3dxsrv.dll
15:26:17.109: UdCtl: initialization successful.
15:26:17.109: UdCtl: Attempting to load device DLL: C:\Program Files\3Dconnexion\3Dconnexion 3DxWare\UdDev\HIDDev.dll
15:26:17.125: UdDev: Attempting to open 3Dx-supported HID device on USB
15:26:17.140: UdDev: Attempting to open 3Dx-supported HID device on USB
15:26:17.140: UdDev: Attempting to open SpaceMouse-type device on port USB
15:26:17.140: UdDev: Attempting to open SpaceBall 2003 or 3003 device on port USB
15:26:17.140: UdDev: Attempting to open SpaceBall 4000 device on port USB
sb4000:UdComOpen: Error opening port: USB
15:26:17.218: UdDev: Attempting to open 3Dx-supported HID device on USB
15:26:17.218: UdDev: Attempting to open SpaceMouse-type device on port USB
15:26:17.218: UdDev: Attempting to open SpaceBall 2003 or 3003 device on port USB
15:26:17.218: UdDev: Attempting to open SpaceBall 4000 device on port USB
sb4000:UdComOpen: Error opening port: USB
15:26:17.218: UdDev: Attempting to open 3Dx-supported HID device on HID1
15:26:17.218: UdDev: Attempting to open SpaceMouse-type device on port HID1
15:26:17.218: UdDev: Attempting to open SpaceBall 2003 or 3003 device on port HID1
15:26:17.218: UdDev: Attempting to open SpaceBall 4000 device on port HID1
sb4000:UdComOpen: Error opening port: HID1
15:26:17.218: UdDev: Attempting to open 3Dx-supported HID device on COM1
15:26:17.218: UdDev: Attempting to open SpaceMouse-type device on port COM1
15:26:25.875: UdDev: Failed to get SpaceMouse firmware version - no device detected
15:26:25.953: UdDev: Attempting to open SpaceBall 2003 or 3003 device on port COM1
15:26:31.046: UdDev: Failed to get firmware version for 2003 or 3003 - no device detected
15:26:31.125: UdDev: Attempting to open SpaceBall 4000 device on port COM1
sb4000:UdComWrite: WriteFile failed, err = 0x3e5
sb4000:UdComWrite: WriteFile failed, err = 0x3e5
sb4000:UdComWrite: WriteFile failed, err = 0x3e5
sb4000:UdComWrite: WriteFile failed, err = 0x3e5
sb4000:UdComWrite: WriteFile failed, err = 0x3e5
sb4000:UdComWrite: WriteFile failed, err = 0x3e5
sb4000:UdComWrite: WriteFile failed, err = 0x3e5
sb4000:UdComWrite: WriteFile failed, err = 0x3e5
15:26:39.187: UdDev: Failed to get 4000 firmware version - no device detected
jwick
Moderator
Moderator
Posts: 3331
Joined: Wed Dec 20, 2006 2:25 pm
Location: USA
Contact:

Post by jwick »

What makes you think your COM port is working?

Try this:
1) Start HyperTerminal (Start->Accessories->Communications->HyperTerminal)
2) Choose any name
3) Choose COM1 (or whatever port your SB is connected to)
4) 9600, 8, none, 1, Xon/Xoff
5) Press a button on the SB. You should get firmware version and various @@-type characters in the terminal window. They overwrite each other.

Make sure your BIOS and/or your anti-virus software has not disabled the COM port.

Jim
3Dx Software Development
danmk1984
Posts: 8
Joined: Thu Nov 01, 2007 6:57 am

Post by danmk1984 »

I assumed because the COM port was shown in my hardware devices and I was getting beeping that it was fully functioning.

I've carried out you're last instruction and have had no joy, again only beeping. Does this mean there is a fault with the com port? Could I connect the old one from the old computer to make it work?

Thanks for your help on this

Dan
jwick
Moderator
Moderator
Posts: 3331
Joined: Wed Dec 20, 2006 2:25 pm
Location: USA
Contact:

Post by jwick »

I suspect it is a configuration issue. Check the BIOS to make sure the COM ports are enabled. Then check the antivirus software to make sure they aren't being disabled.
danmk1984
Posts: 8
Joined: Thu Nov 01, 2007 6:57 am

Post by danmk1984 »

I've just checked the BIOS and the Port isn't being disabled. The anti virus software has no control or restrictions. If it is a configuation issue, is there a way to set the COM port configuration other than the limited on/off that can be set in BIOS?
jwick
Moderator
Moderator
Posts: 3331
Joined: Wed Dec 20, 2006 2:25 pm
Location: USA
Contact:

Post by jwick »

Dunno. Every machine seems to be a bit different. You'll have to check with the PC supplier.

Please report back here what you find, so others can take advantage of your findings.
danmk1984
Posts: 8
Joined: Thu Nov 01, 2007 6:57 am

Post by danmk1984 »

ok, thank you for your help. a couple of the other guys in the office have been onto the PC supplier so this was the last place to get anywhere with it.

Dan
Post Reply