Phidgets Forums

Howdy,

Am having some difficulty getting Max/MSP to recognize a 0/16/16 on Mac OS 10.13.2
The Phidget package installed is ver. 2.1.8.201 (also installed is Phidget22)
and Max is ver. 7.3.3

The interface is showing up in the System Preferences Phidget utility
and the PhidgetInterfaceKit object is recognized by Max
but there is no communication.

Has anyone else run into this issue?
Please advise

Cheers!

When the Phidget shows up in the system preferences utility, are you able to access it and control its inputs and outputs?

When you try to access it in Max/MSP, do you still have it open in the Phidget utility? Because a Phidget can only be open in one program at a time unless it has been opened remotely in each program.

In the Phidgets utility, yes, the inputs and outputs are responsive.
The utility has not been open when using Max

Can you clarify what isn't working in Max/MSP? Is the open call timing out, or are you able to open the Phidget but can't get inputs and set outputs?

Sure, using the help patch, the Phidget isn't recognized. getSerial doesn't return anything in the console and inputs and outputs are not registering after trying to start communication. The device doesn't seem to open. The led on the board lights up when triggering an input but Max isn't seeing it.

…and when trying the PhidgetDigitalOutput object help file, getDeviceSerialNumber returns -1.
when triggered, the setState message returns a device not attached error

macOS is 10.13.2
Java is version 8 update 151

I’ve had no problems in the past using phidgets w/Max. Is this something OS specific?


cheers

Do you get the same results when you use our sample code for DigitalOutput or DigitalInput?

yup, the phidget remains unrecognized when trying the help files for DigitalOutput and DigitalInput

Hi,

perhaps, I have similar problem. I am using Phidget 1046RTD. It is well recognized on my MacBook with iOS 10.13, but when I open bridges, it shows "Attached: nothing".

I tried the same phidget on iMac with iOS 10.9 and works fine without issue.

Any hint how to solve it?

Thanks,Miroslav.

It looks like this may be a compatibility issue. I've let our Max/MSP developer know about it.