Device cannot be opened [Solved]

Post your question or observations here.

Moderator: DevRuss

Post Reply
Ross balmer
Apprentice
Posts: 3
Joined: Thu Feb 13, 2020 3:19 am

Device cannot be opened [Solved]

Post by Ross balmer » Fri Feb 14, 2020 9:03 pm

Hi. I just recently bought ControlMyJoystick this week and it was working fine. However, because of some other issues with my machine, I decided to reinstall Windows. Since the reinstall, which used the latest versions of ControlMyJoystick (5.3.45.89) and 3DxWare (10 10.6.5), I keep getting the message "Device cannot be opened", which is strange because CMJ shows the device is working properly on the Input/3DxWare tab, where the axis values change as I move the mouse.

Is there anything I can do about this? Is it something I have done in the install? I would really appreciate any help since this is obviously a very fine piece of software when I can get it working.

Many thanks,
Ross Balmer

User avatar
DevRuss
Journeyman
Posts: 101
Joined: Wed Mar 27, 2019 6:59 am

Re: Device cannot be opened

Post by DevRuss » Tue Feb 18, 2020 9:31 am

Please post the text from the log tab here and I will take a look. Which 3dconnexion device are you using? Not sure if the message is referring to another device, such as the microphone or a joystick. Does the 3dconnexion controller seem to work ok in CMJ even though this message is displayed in the log?
Russ - Tetherscript Developer

Whiten01se
Posts: 2
Joined: Sun Feb 23, 2020 10:22 pm

Re: Device cannot be opened

Post by Whiten01se » Sun Feb 23, 2020 10:25 pm

Yeah i'm running into the exact same issue since today.

What happened: I got my Kensington SlimBlade trackball (wonderful addition to the 3dx). However, it appears that if i use the actual Kensington driver for the device, i get the "cannot be opened" error from CMJ. If i replace the driver with a generic mouse driver (and lose functionality, like button assignments) it will then again work with CMJ (meaning CMJ won't crash).

I'd request this to be looked into with some urgency. Thank you. :)

Ross balmer
Apprentice
Posts: 3
Joined: Thu Feb 13, 2020 3:19 am

Re: Device cannot be opened

Post by Ross balmer » Tue Feb 25, 2020 11:20 pm

I am using a 3d SpaceMouse. It worked just fine before I reinstalled Windows. Now I can't get it to work. CMJ is still detecting the device. When I try to bind an output to Elite Dangerous (or anything) the values of all the axes are set to -1000.
cmj1.jpg

User avatar
DevRuss
Journeyman
Posts: 101
Joined: Wed Mar 27, 2019 6:59 am

Re: Device cannot be opened

Post by DevRuss » Fri Feb 28, 2020 12:11 am

Hi Ross,

Are you using a Kensington device, or using a Kensington driver for any devices on that system? This is the third instance of this error that I have heard this week. The other two were Kensington device driver related.
Russ - Tetherscript Developer

Ross balmer
Apprentice
Posts: 3
Joined: Thu Feb 13, 2020 3:19 am

Re: Device cannot be opened

Post by Ross balmer » Fri Feb 28, 2020 1:39 pm

Yup, I am using a Kengsington Orbit. It's the Kensington driver alright. That's annoying, but not as bad as ControlMyJoystick not working.

It must be worse for Whiten01se with the SlimBlade button assignments feature not working. I am looking into this, maybe it will help?

http://www.highrez.co.uk/downloads/XMou ... ontrol.htm

I have heard Kensington software is a bit flaky. It's a shame because the hardware is great. Hope you manage get to the bottom of this.

Thanks for the help!

Ross

User avatar
DevRuss
Journeyman
Posts: 101
Joined: Wed Mar 27, 2019 6:59 am

Re: Device cannot be opened

Post by DevRuss » Mon Mar 02, 2020 7:46 pm

@Rossbalmer Many thanks for the Kensington device info. We are looking at the code now, not sure on when a fix will come out.
Russ - Tetherscript Developer

User avatar
DevRuss
Journeyman
Posts: 101
Joined: Wed Mar 27, 2019 6:59 am

Re: Device cannot be opened

Post by DevRuss » Mon Jun 01, 2020 11:06 pm

We are working on the fix for this. The error that caused the crash *may* have been fixed in the new patch. We can’t duplicate this error here.

Note: This patch is available for the registered and trial version available on the tetherscript website. It won’t work on the Steam version.

Instructions
Replace the v5.3.45.89 controlmyjoystick.exe with the following v5.4.17.19 executable which contains a possible fix for the 'Device cannot be opened' and 'Device cannot be identified' bug. This is only the executable only. If this fixes the problem, we'll release the full installer. The new executable will work with your existing product key and also extends the trial period.

https://tetherscript.s3-us-west-2.amazo ... e_only.zip

Please let me know if this fixes the problem or not.
Russ - Tetherscript Developer

User avatar
DevRuss
Journeyman
Posts: 101
Joined: Wed Mar 27, 2019 6:59 am

Re: Device cannot be opened

Post by DevRuss » Thu Jun 04, 2020 3:12 am

This issue is resolved in 5.4.17.79.
Russ - Tetherscript Developer

Whiten01se
Posts: 2
Joined: Sun Feb 23, 2020 10:22 pm

Re: Device cannot be opened [Solved]

Post by Whiten01se » Thu Jun 11, 2020 9:30 pm

Awesome work! Thanks a lot. Confirmed resolved.

I'm curious, what was the solution?

User avatar
DevRuss
Journeyman
Posts: 101
Joined: Wed Mar 27, 2019 6:59 am

Re: Device cannot be opened [Solved]

Post by DevRuss » Fri Jun 12, 2020 3:51 am

It was a silly bug - i had left a component out on the Delphi form for communicating with a beta Wheel driver, but had not hooked up the error handling for it. This component should have not been there for the release. Major slappage of forehead when I saw that.
Russ - Tetherscript Developer

Post Reply