Skip to Navigation

5.3 - Errorcodes

Comments

#1

Submitted by Sean (not verified) on Tue, 2011-12-13 11:44.

A shame there isn't an enum/#define for all these errors in labjackusb.h.

#2

Submitted by LabJack Support on Tue, 2011-12-13 18:41.

The Exodriver and its header are meant for generic USB communications, and not the best place for the low-level function interface's error codes.  A more appropriate spot for these would be the u6/u3/ue9.h helper headers, or some other separate header.

#3

Submitted by Anonymous (not verified) on Mon, 2010-09-20 16:11.

After installing the newest version of the U3 driver (along with validating the libusb library, etc per the installation directions) we attempted to run a low-level program to make the LED blink. When the we executed the module we recieved the following error script:

LJUSB_DoTransfer warning:  got endpoint = 2, however this is not a known endpoint.  Please verify you are using the header file provided in usr/local/include/labjackusb.h and not an older header file.

libusb error:LIBUSB_ERROR_IO

However when you review the header file you see that there are actually three endpoints specified.  We have an older version of the program installed on another tower and the program still works fine on that machine.

The loss of functionality is directly realted to the new install.

We have also recently updated this machine to Fedora 13, where the working machine is still running Fedora 11.  Any insight/help would be greatly appreciated.

 

 

 

#4

Submitted by LabJack Support on Mon, 2010-09-20 16:25.

If you are using Python, then you will also have to update LabJackPython to the latest version.

We made sweeping changes to the Exodriver, and part of those changes involved changing the endpoint values to their USB endpoints. The error you saw is caused when LabJackPython tries to use the old endpoints on the new Exodriver.

Please contact us directly if you continue to have issues.