04-16-2006 08:09 AM
One more thing...
You did not say if this 5 second delay was causing a problem. In most cases I will code expecting delays that large or larger if devloping in Windows.
Ben
04-17-2006 12:04 AM
04-17-2006 08:48 AM
Ben -
Thanks for your comments. The 5 second delay is abig deal to us, as each test sequence calls on the order of 500 VIs and takes approximately 2 seconds. When one of those VIs comsunes 5 seconds instead of 5 milliseconds, we notice. In previous versions of our application that did not use this kind of central LV2-style data management, we did not have this problem. Our application is used on the production line, where timing is critical.
I will try to put together a version of my LV2 global that you can hack around with. I'll need to slim it down quite a bit to simplify the problem, and then make sure that it's repeatable with that code.
On a side note: I did implement something like you described by changing the way the caller and the LV2 interact, with very good results. This will suffice as a workaround for now.
thanks again, Scott
04-17-2006 08:50 AM
Scott wrote;
"
On a side note: I did implement something like you described by changing the way the caller and the LV2 interact, with very good results. This will suffice as a workaround for now.
"
Excellent!
Thank you very much for the update.
Ben
11-13-2008 03:45 PM - edited 11-13-2008 03:46 PM