Re: [Libphidget-devel] libphidget newbie post...

[Tom B. <tb...@ba...>]

sorry, missed some items that may be relevent... linux "dmesg" shows the
following:

usb.c: usbdevfs driver claimed interface caa63380
usb.c: ignoring set_interface for dev 9, iface 0, alt 0
usb.c: usbdevfs driver claimed interface caa63380
usb.c: ignoring set_interface for dev 9, iface 0, alt 0
usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_BULK failed dev 9 ep 0x81 len 7 ret -110

I'm using the ik_example example ...
note that the 1083 serial # is the same one reported by the linux 
kernel...

   usb.c: USB device number 7 default language ID 0x409
   Manufacturer: Phidgets Inc.
   Product: PhidgetInterfaceKit
   SerialNumber: 01083


   [root@home /home/tbrown/libusb/libphidget/src/examples]# strace -o tmpx -s
   500 ./ik_example
   ik_example: code examples of how to communicate with interface kits
   Version 1.1
   *** DEBUG *** : phidgetInit
   *** DEBUG *** : _clearDeviceTypes
   *** DEBUG *** : _registerDeviceType
   *** DEBUG *** : _registerDeviceType
   *** DEBUG *** : _registerDeviceType
   *** DEBUG *** : _registerDeviceType
   *** DEBUG *** : _registerDeviceType
   *** DEBUG *** : _registerDeviceType
   *** DEBUG *** : _registerDeviceType
   *** DEBUG *** : _registerDeviceType
   *** DEBUG *** : _registerDeviceType
   *** DEBUG *** : _registerDeviceType
   *** DEBUG *** : _registerDeviceType
   *** DEBUG *** : phidgetEvents
   *** DEBUG *** : _checkForSoftPhidgets
   *** DEBUG *** : Going thru all USB Busses
   *** DEBUG *** : Going thru each device on that bus
   *** DEBUG *** : _findDevice
   *** DEBUG *** : Is this device a phidget? - no
   *** DEBUG *** : _findDevice
   *** DEBUG *** : Is this device a phidget? - yes
   *** DEBUG *** :         getting serial old fashioned way

   *** DEBUG *** : Get Serial
   *** DEBUG *** : _getSerial
   *** DEBUG *** :         usb_open

   b0 Buffer:12
   *** DEBUG *** : _addDevice
   *** DEBUG *** : _findDevice
   *** DEBUG *** : Is this device a phidget? - no
   *** DEBUG *** : _findDevice
   *** DEBUG *** : Is this device a phidget? - no
   *** DEBUG *** : Going thru each device on that bus
   *** DEBUG *** : _findDevice
   *** DEBUG *** : Is this device a phidget? - no
   *** DEBUG *** : _findDevice
   *** DEBUG *** : Is this device a phidget? - no
   *** DEBUG *** : Going thru phidgets
   *** DEBUG *** : _stateAttached
   *** DEBUG *** : phidgetGetPhidgets
   Interface Kit Controller found: 1083
   Found interfacekit
   *** DEBUG *** : phidgetGetPhidgets
   *** DEBUG *** : phidgetOpen
   done 'CInterfaceKit'...
   built analog in 
   *** DEBUG *** : phidgetRead
   whoa! usb_bulk_read() returned -1 bytes when we expected 7
   Change:2.036505
   Change:2.506664
   Change:2.017647
   Change:-1.999806
   called kit.update()
   helper.h#127 const X &error (const X &) [with X = const phidget_type *]
   Exception:libphidget error >> Error reading bulk data from a phidget
   CPhidget.cc#45 int CPhidget::classType () Exception:libphidget error >>
   Error reading bulk data from a phidget
   *** DEBUG *** : phidgetClose
   exception:libphidget error >> Error reading bulk data from a phidget
   *** DEBUG *** : phidgetDeinit
   *** DEBUG *** : _clearDeviceTypes
   *** DEBUG *** : clearDevices


On Thu, 26 Jun 2003, Tom Brown wrote:

> 
> sorry for being impatient and not waiting a few days to see if there is
> any traffic on this list, but the sourceforge archives indicate zero
> traffic since september... 
> 
> I see Jack on the commit list is working on an 'LP_8WAY_SERVO' I'm trying
> to get the 888 interface kit up and running... anyhow, is anyone around
> 
> I'm making slow progress... the DBG statements had to be defined and
> re-ordered to make my C compiler happy. --no-verify had to be deleted from
> a line in ./configure to get configure to run... I've added ( ||
> interfacekit = 888) to a bunch of the 488 code and I'm now at the point
> where the code is trying to query the inputs on the device but I'm getting
> USB timeouts and I'm now substantially over my head (it has found and
> identified the device, so the USB layer would seem to be ok... it's
> probably just some 488 specific stuff in the command? Unfortunately I
> don't have any docs on the commands being sent in the USB datastream?
> [you here/hear Chester?]) ... will keep slugging at it...
> 
> -Tom