I am tring to comine the manager sample with the interface sample kit. The problem I am running into is the manager sample does not implement the CPhidgetInterfaceKitHandle IFK.

If I try to create and open the connection using the code from the sample kit it states the connection is already open. I belive this is the result of CPhidgetManager_getAttachedDevices call in the manager sample.

If this opened the interface kit how do I get the CPhidgetInterfaceKitHandle ? If not how do I open the connection?

the call to CPhidgetInterfaceKit_getOutputCount allways returns 0 outputs
an example of the code:

You can't just use the devices reported by the Manager directly - you need to open them first. You should check the return code of your function calls.

You need to create a new CPhidgetInterfaceKitHandle and then call open on it with the serial number reported by the Manager.

-Patrick

Patrick,
I have simliar problem. I create, open and wait for open, but nothing returned on call for num-anything. Receive return code 5.
Code snippet below.
Regards,
Alan

CPhidgetHandle phid; //value from PhidgetManager attach event
int ifSerial; //value from PhidgetManager attach event
CPhidgetInterfaceKitHandle PhidgetInterfaceKit;
int numInputs = 0;
int rc = 0;

CPhidgetInterfaceKit_create(&PhidgetInterfaceKit);
CPhidget_open(phid, ifSerial);
CPhidget_waitForAttachment(phid, 200);
rc = CPhidgetInterfaceKit_getInputCount(PhidgetInterfaceKit, &numInputs);

// getInputCount returns rc = 5 and numInputs unchanged

I would increase the waitForAttachment timeout - 200ms may be too low - also, check the return value from waitForAttachement.

-Patrick

I have tried setting to 0, 2, 2,000 and 20,000 and 200,000.
rc is alwyas zero.
Doesn't appear to actually wait, but comes back almost immediately, well at least is quicker than the fifth to half second that us humans can noticably perceive. Although, is UP UNTIL the time specified. i.e. if connected sooner, CPhidget_waitForAttachment will return immediately, or do I have that wrong?

...or.... is actually connecting, but something else is going on and CPhidget_waitForAttachment's error handlingcode falls into this return code. i.e. bug in CPhidget_waitForAttachment error handling.

Alan.

If I execute Manager_simple and InterfaceKit_simple, they work fine with regard to reading numInputs or numOutputs. Both with VC++ 2101 Express and RAD Studio C++ (what Embarcadero now calls the acquired Borland C++). Problem I have highlighted occurs when attempting to use the above in conjunction. A typical scenario for developing a solution that will dynamically detect, open and work with, say, an InterfaceKit of any serial number. Examples, assume that developer will write a program for one specific serial number.

Your 1st port says that rc==5 - that means 'not attached', but now you are saying that it's returning -0 - which means 'ok' - so numInputs should be getting updated.

-Patrick

rc = 0 for CPhidget_waitForAttachment (you had suggested I check that, and I responded without being specific. Apologies).
rc = 5 for subsequent CPhidgetInterfaceKit_getInputCount.

Regards,
Alan

You have two different handles - 'phid' and 'PhidgetInterfaceKit' - so, even if you call open on phid - you are trying to get the outputCount on PhidgetInterfaceKit - which has not been opened.

It should be:
-Patrick

I had code with incorrect casting. I had been playing with other alternatives. However, I now took Manager-simple project and put code into the display_devices routine in Manager-simple.c (using Visual C++ 2010 Express). Compiles fine and executes, but not getting return code 0 for the waitForAttachment. My additions are in red.

//Display the properties of the attached phidget(s) to the screen. We will be displaying the name, serial number and version of the attached device(s).
int display_devices(CPhidgetManagerHandle MAN)
{
int serialNo, version, numDevices, i, numInputs, rc;
const char* ptr;
CPhidgetHandle *devices;
CPhidget_DeviceClass cls;
CPhidgetInterfaceKitHandle PhidgetInterfaceKit;
CPhidgetManager_getAttachedDevices (MAN, &devices, &numDevices);

printf("|- # -|- Type -|- Serial No. -|- Version -|\n");
printf("|-------|----------------------------------|--------------|------------|\n");


for(i = 0; i < numDevices; i++)
{
CPhidget_getDeviceType(devices[i], &ptr);
CPhidget_getSerialNumber(devices[i], &serialNo);
CPhidget_getDeviceVersion(devices[i], &version);
CPhidget_getDeviceClass(devices[i], &cls);
printf("|- %3d -|- %30s -|- %10d -|- %8d -|\n", i, ptr, serialNo, version);
printf("|-------|----------------------------------|--------------|------------|\n");

if (cls = PHIDCLASS_INTERFACEKIT) {
CPhidgetInterfaceKit_create(&PhidgetInterfaceKit);
CPhidget_open((CPhidgetHandle)PhidgetInterfaceKit, serialNo);
rc = CPhidget_waitForAttachment((CPhidgetHandle)PhidgetInterfaceKit, 2000);
printf("Wait return code: ");
printf("%10d\n",rc);
if (rc == 0) {
rc = CPhidgetInterfaceKit_getInputCount(PhidgetInterfaceKit, &numInputs);
printf("numInputs return code: ");
printf("%10d\n",rc);
}
CPhidgetManager_freeAttachedDevicesArray(devices);

return 0;
}

Hi,

This will not work because display_devices is called from within the manager attach and detach handlers.

The thread that handled opening you InterfaceKit is the same as the thread that sends out attach and detach events - since this thread is busy in an attach event, your interfacekit will never become attached, no matter how long the waitForAttachment timeout is.

If you want to create/open devices from within manager attach events - this is fine, but you can't use waitForAttachment, you should instead set up an attach event for the new interfacekit - this will get run after the manager attach event returns.

Alternatively, you could stop using manager attach/detach events and just call display_devices from a loop in you main thread (with a short sleep between calls).

-Patrick

Thanks. That was helpful.
Would be useful to have C++ example that detects a phidget from the manager attach event and subsequently works with the attached phidget. I have this working in VB using the secondary attach solution you described (i.e. separate threads). Was recently looking at porting to C++ using example code (which are very useful), and putting prototype together. When I get a C++ prototype working I can send you a Detect-and-Use-simple (Microsoft and Borland).

Regards,
Alan Dyer

Had gotten this working. Did not get around to replying for a while.
Thanks for the great support.