hi object problem with saitek controllers

Jun 29, 2006 at 6:35pm

hi object problem with saitek controllers

I’ve tried using a Saitek P3000 wireless gamepad and
a Saitek Cyborg Wireless Evo joystick with the [hi]
object, but I’m having a few issues.

Firstly, only one device gets recognised when generating
a menu of available devices (if both are plugged in).

Secondly, when a device is recognised, it doesn’t seem
to recognise any of its elements.

When getting device info, this is printed to the Max window:

hi: focussing on Saitek Cyborg Evo Wireless
hi 2004.02.16. bugs? bbn@saoul.ca
1 devices
Saitek Cyborg Evo Wireless
0 elements

Any suggestions would be gratefully appreciated…

#26632
Jun 29, 2006 at 7:07pm

What OS & s/w versions? I have a Saitek wireless
gamepad working just fine here on OS 10.4.6 and
Max/MSP 4.5.7
cheers
Roger

#79923
Jun 29, 2006 at 7:30pm

Hi,

I’ve had similar problems with the [hi]-object. I even went out and bought a new, hugely expensive ps2 converter, since my old one didn’t work at all. Now max can only see one controller connected, even though I connect two. I am on the latest version of max with XP pro.

#79924
Jun 29, 2006 at 8:35pm

Maybe you could try my (maybe not so obsolete) [hidin] object that I
wrote back in the days when Max came without the [hi] object. You can
find the Windows version here:

http://www.akustische-kunst.org/maxmsp/dev/hidin-1.0beta8.zip

Maybe it uses a different API to connect to your HID devices and turns
out different results…

Olaf

#79925
Jun 30, 2006 at 2:36am

Ok I can use either controller if it’s connected by itself.
I simply forgot to send the message enabling periodic polling (every 10ms). Silly me.

However [hi] still can’t see more than one controller at a time
when two are plugged in.

I’m running Windows XP Pro SP2 & latest version of Max.

When I get a chance over the weekend I’ll try the older object as suggested and report back.

Thanks for the help so far.

#79926
Jun 30, 2006 at 2:59am

I just downloaded Olaf’s [hidin] external and gave it a try.

Whereas with the [hi] object I only got one device appearing in the devices list, with [hidin] I get 4:

Unsupported Device
Unsupported Device
Unknown (Device #3)
Cyborg evo Wireless

When I disconnect the p3000 and get the list of connected devices again, the unknown device disappears from the list.

Also with the [hidin] object, no controller data is coming out of the left outlet whatsoever, regardless of which controller is connected.

With the [hi] object, I do get controller data but as I mentioned earlier, only one device is usable when two are connected.

One more thing, the [hi] object doesn’t report the number of elements on the device connected, whereas the [hidin] object does. (22 for the Cyborg evo Wireless and 23 for the p3000).

FWIW, I’m also using the latest Saitek drivers.

#79927
Jun 30, 2006 at 9:57am

> I’ve tried using a Saitek P3000 wireless gamepad and
> a Saitek Cyborg Wireless Evo joystick with the [hi]
> object, but I’m having a few issues.

I’ve used a P-880 joystick and an X-52 flight control system without
problems. (OS X 10.4.x.)

> hi: focussing on Saitek Cyborg Evo Wireless
> hi 2004.02.16. bugs? bbn@saoul.ca

Hmm – are you sure you’re not using an old, pre-release version of [hi]?

– N.

nick rothwell — composition, systems, performance — http://
http://www.cassiel.com

#79928
Jul 3, 2006 at 1:00pm

Quote: nick rothwell / cassiel wrote on Fri, 30 June 2006 10:57
—————————————————-
> > hi: focussing on Saitek Cyborg Evo Wireless
> > hi 2004.02.16. bugs? bbn@saoul.ca
>
> Hmm – are you sure you’re not using an old, pre-release version of [hi]?

Just checked this and I was using an old version of [hi]. After remedying this (using the newest version, dated 2006.01.04) I still get the same problems…

hi 2006.01.04. bugs? bbn@saoul.ca
1 devices Saitek P3000 Wireless Pad
0 elements

#79929
Jul 3, 2006 at 10:01pm

Thanks for your comments – the windows version of the hi object will
support multiple devices soon.

Ben

#79930
Jul 5, 2006 at 3:44pm

Thanks Ben!

#79931

You must be logged in to reply to this topic.