labjack / exodriver Goto Github PK

Hello,

I'm using the u3.c file to work with the U3 device.
I'm using a lot the eDI and eDO functions with ConfigIO = 1
The state (I or O) isn't change a lot of time but can change, that's why I use ConfigIO = 1.

In certain case (eg. when I use a lot of time eDI in a row, the card crashes and I can read:
libusb error: LIBUSB_ERROR_OVERFLOW
ehFeedback error : response buffer is too small
libusb error: LIBUSB_ERROR_PIPE
ehConfigIO error : read failed
libusb error: LIBUSB_ERROR_PIPE
ehConfigIO error : read failed
libusb error: LIBUSB_ERROR_PIPE
ehConfigIO error : read failed
libusb error: LIBUSB_ERROR_PIPE
ehConfigIO error : read failed
[...]

Do you have an idea ? Thanks!

PS: I've a 35ms delay (minimum) betweek each read.

Thanks! Bye :D

It looks from commit 0106af0 like the 2.7.0 release is prepared, but no corresponding tag has been added. The tag is useful because a versioned zip download link will be available.

The build fails on the latest macOS release. The error is:

$ make -f Makefile DESTINATION=/usr/local/Cellar/exodriver/2.5.3/lib HEADER_DESTINATION=/usr/local/Cellar/exodriver/2.5.3/include install
clang -fPIC -g -Wall  -c labjackusb.c
libtool -dynamic -o liblabjackusb.dylib -install_name liblabjackusb.dylib -current_version 2.5.3 -compatibility_version 2.5.3 labjackusb.o -lusb-1.0 -lc
ld: file not found: 
fatal error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: internal link edit command failed
make: *** [liblabjackusb.dylib] Error 1

Hi, downstream users like Homebrew on OS X use repo Tags to allow us to update, currently your version is 2.5.2 but the last tag was 2.5.1, could you tag the next release to allow us to update. Thanks!

The ill-named t4 branch adds untested T4 support. @davelopez01, please test before merging, of course.

Also, we should probably just add T5 support now, so we only have to increment the version once. Do you agree, @davelopez01?

Hello,

Sorry but it's about : #6

I really need it now and I can't do it by myself =/ I'm not at my ease with low-level...
I want to read the Output state of a digital output.

In fact, I want to act like a Voltmeter on the FIO.

Thanks.

Hello,

I developped an automation program with your driver (thanks)
I've just a little problem.

At the start of my software, I set eDO for port 8 & 9 to Low.
On an Event, I read the value of 8 & 9 (eDI) and I set (eDO) to the contrary. After a while, I set 8 & 9 with previous read states.

Ex:
Starting.. 8 & 9 = Low (by eDO)
Event
Reading 8 & 9 ( => previousState = Low )
Setting 8 & 9 to High
Wait a bit
Setting back 8 & 9 to previousState = Low.

That's work. Right.

But now, when I want to do this :
Starting.. 8 & 9 = HIGH (by eDO)
Event
Reading 8 & 9 ( => previousState = Low ) <=== PROBLEM. It should be High!
Setting 8 & 9 to High
Wait a bit
Setting back 8 & 9 to Low.

Do you see what I mean ? ^^ It's a bit stange x) Or maybe I'm a noob. Do you have any idea on How to do the trick ?

Thanks for all !

(You're credited into the program^^)

The last tag is from 2014, with quite a few commits since. Would it make sense to create a new tagged release?

Thanks!

Hi,
I'm using exodrive from Matlab and got a warning when I load labjackusb and labjackusb.h :
Warning: The data type 'voidPtrPtrPtr' used by function LJUSB_OpenAllDevicesOfProductId does not exist.

Everything else works perfect (I'm not using that function really), but I think maybe is useful that I report this.

Best,
Fernando Chaure

The install script breaks when executed from within gnome terminal because of a call to "logname" which was broken by a recent change detailed here:
https://bugzilla.gnome.org/show_bug.cgi?id=747046#c10

The install script works fine if executed from within xterm.

It might make sense to revert f9f89f1 ?

Hi, the V2.5 tag was set 6 moths or so ago, and you've tagged no new release. Without a tag, downstream repo's like homebrew cannot update their ports of exodriver (unless explicitly using HEAD). Can you tag a release if the changes you made are useful, and probably you need to tag as V2.51 even though your previous version is 2.05 -- some typo I assume...