-
I suddenly started having issues talking to my USB device from Java, and after trying a ton of stuff, I looked at the propertys of libusbjava.dll in system32. it said something about being blocked and had a button to unblock it. a little notice would have been nice. i think this is what got me back on track, but i tried a ton of stuff so it could have been something else.
good luck...
2009-10-25 22:30:40 UTC by james
-
You can try to increase the timeout to a high value ( e.g. 10 seconds). If the situation is the same it's probably a device error. Without more detail of the device it's difficult to say what the problem is.
Note that a reset of the device invalidates the device handle and the device must be reopened.
2009-09-17 21:19:07 UTC by spandi
-
Hi
The DLL is calling libusb-win32 functions synchronously. So the question is if libusb-win32 is thread safe --- not the wrapper.
I'm also not a DLL expert but [msdn][1] states: 1. Synchronize access to all global variables - 2. Link only with libraries that are thread safe
The global variables in the DLL are: 1. Bus structure retrieved by usb\_get_busses() - 2. References to Java...
2009-09-17 21:11:15 UTC by spandi
-
I am having a similar problem. I also get a reap timeout error. My send data works and read data works sometimes, and once it starts working, it works until I click reset. I don't know if this means there is a timing issue or the in endpoint is not configured properly. Below are the details of my in endpoint:
Usb_Endpoint_Descriptor
blenght: 0x7
bDescriptorType: 0x5
bEndpointAddress...
2009-09-16 14:44:58 UTC by abidbodal
-
Hi,
i tested the dll extensively under windows and i found a major problem.
I had to drive 3 printers from 3 software instances, each software instance had is own folder with jars and dll,
I found that running the 3 instances togheter gives a lot of problems in opening the device (busy) and several other communication problems that render the library unusable.
To solve the problem i had...
2009-09-08 10:21:28 UTC by marcopar
-
Hello, I've made some progress and the problem was that some telegrams needed to be sent previously in order that the device could be able to send some data to the PC by USB. That was the reason why timeout exception appeared.
Thank you very much.
2009-07-27 13:02:36 UTC by celia82
-
A timeout exception can have the following reasons:
1. The device doesn't send any data
2. The device wants to send data but the timeout is too short
Most likely (1) is the problem.
How it works technically: The timeout parameter passed to the function ch.ntb.usb.Device.readInterrupt(int, byte[], int, int, boolean) specifies the amount of time the function call will wait for data to be...
2009-07-18 14:11:37 UTC by spandi
-
Hello,
I´m using libusb in Linux and libusb-win32 in Windows in order to read and write telegrams between a KNX network and my PC through a KNX device (ABB i.bus EIB/KNX USB/S1.1) with USB connection.
Firstly I made the changes that are necessary in both OS so that the device is considered as a device controlled by libusb or libusb-win32.
When I execute the java wrapper a timeout error...
2009-07-13 09:25:49 UTC by celia82
-
Hi,
OK thanks, My problem was that I just clicked on the download link on the page:
http://sourceforge.net/project/showfiles.php?group_id=188245
This just gives you the jar, hence my problem.
This link gets you the dll as well:
https://sourceforge.net/project/showfiles.php?group_id=188245&package_id=220085
Cheers.
2009-06-15 06:05:40 UTC by jonesst99
-
In the release notes there was a reference to the snapshot 20081220 because the dll hasn't change since then. That was maybe not obvious, so I moved the dll to the latest release and added a reference to the release notes of snapshot 20081220.
Just go to the download page again and click on the latest snapshot.
To compile it yourself you need MinGW and Apache ant. That should be it...
2009-06-12 18:04:13 UTC by spandi
