Quote:
|
For the record, the acquire or create semaphore reference VI is not the fastest thing
|
Are you talking about the actual semaphore VIs in the palette? If so, the issue may be more closely related to leaking the refnums. All I/O handles in LV are shadowed so that aborting or completing will do the close/free operations. And if you leak, that is a lot of resources to shadow. If you probe the refnum and see a unique one each time, you definitely need to close it.
If it is the WPILib Get VIs, which is it you are commenting on.
Greg McKaskle