LabVIEW
Experience with ftd2xx.dll
Hi all,
as described in a different post I have been having problems that I think I've narrowed down to a dll that is used as a wrapper around another dll. The manufacturer of the hardware has suggested that I might make direct calls to the second dll, which is the ftd2xx.dll from FTDI the USB folks. I created this thread to get more eyeballs looking at it, the other one had gotten so long and had developed a low SNR at this point.
What I'm interested in is any experience with the ftd2xx.dll, whether anyone knows whether it is considered threadsafe (the examples at FTDI are LabVIEW 7.x and the calls to the dll are configured as "Run in UI thread"). I would hate to put a ton of effort in writing wrappers around this dll to replace the calls to the "wrapper dll" we have been using, only to find that my problem was at this level (a distinct possiblity).
Thanks!!
Still early, but a quick experiment, setting the calls to the dll to "Run in any thread" didn't crash so I will update everybody on Monday when I have wrapped and tested more functions. Still would like to hear from anyone with experience with this dll.
"Gone Sailing"
It appears that the ftd2xx.dll is threadsafe, I have been running a test (mentioned in this thread) overnight without apparent problems with my calls to the dll marked "run in any thread". It is running in a thread other than the UI's as indicated by the actual user interface not having the momentary "freeze-ups" it had with the original "run in UI thread" dll calls. I won't feel 100% about it until I have put these calls into the actual program and run it continuously for a few days, but I am at the 90% comfort range at this point, high for a pessimistic test engineer.
