|
Re: Problem with Async VI Agent.vi staying alive
I left out the info about how it determines what is the top VI. As you noticed, since only one Start Comms is really allowed in a working app, that was selected as the element to use to ID the main hierarchy. As you noted, the FPGA ref can stay alive and be shared amongst many hierarchies, even ones that start and restart. We also noticed that interrupts act up on the third use and were not able to get to the bottom of it last year. We believe it is likely a deeper bug in the RIO driver.
Greg McKaskle
|