06-06-2008 08:18 AM
Why not ?
Although i have not tried it...
06-06-2008 08:41 AM
06-06-2008 08:41 AM
The whole idea of a functional global is that it is a place to hold data in single known place in memory that can only be accessed by one process at a time. That helps prevent race conditions that can occur with other variables. If it's reentrant, you don't know where the data is because you don't have control over how many copies that NI creates.
06-06-2008 08:43 AM
06-06-2008 09:14 AM
Jeff,
I think I see what you're getting at. I'll agree that in the specific instance of using Open VI Reference with option 08 and using the Call By Reference Node that a reentrant functional global should work.
Anyone else reading this thread just needs to understand that all calls to the reentrant functional global are by reference only and not by calling it directly as a subvi on the block diagram.
06-06-2008 09:43 AM
06-06-2008 09:49 AM
06-06-2008 10:25 AM
06-06-2008 10:33 AM

The type gets wired to the top input of the Open.
Ben
06-06-2008 10:35 AM
Is the "preallocate memory" available in 8.5, since I cannot locate it in 8.2.1
May I know what is option 8.
What I assume is each thread will generate a new instance for FG by VI reference Open. Then wherever need to use the same FG, I just pass the reference to it, no matter inside or outside the port.
The new instance of FG should only be generated when I call it, but now seems cannot make it. So I am a bit confused.
If I use a vit and open it as a reference, will it generate another new copy when I use the same reference to run the FG.