03-18-2023 01:25 AM
"Test single stage.vi" calls single Task.vi of Zaber library using Start Async Call Node.
Profile performance and memory dialog shows:
- 5 (!!!) Task.vi and 4 looks as Task.vi:Instance:***
- 5 (!!!) "Test single stave.vi": one as "Test single stave.vi", two as "Test single stave.vi:Instance:***" and two "[Test single stave.vi]"
Why?
03-18-2023 12:47 PM
03-18-2023 12:49 PM
Task.vi is reentrant VI.
03-18-2023 12:53 PM
Ohh ... Test single stage. VI is also reentrant vi. It is top level vi and there isn't reason to make it as reentrant. I will place new Profile dialog later.
03-18-2023 07:30 PM
Test signal stage.vi is non-reentrant. No changes/
03-19-2023 12:33 PM
What's the question?
03-19-2023 10:02 PM
Why are there 5 lines "Test single stage.vi" and "Task.vi" instead of one line?
03-20-2023 02:05 AM
Hi Vasilich,
@Vasilich2004 wrote:
Why are there 5 lines "Test single stage.vi" and "Task.vi" instead of one line?
Now there's time to attach some code so we can examine the problem.
(It's quite hard to analyze from looking at some images of the profiling dialog…)
03-20-2023 05:18 AM
I'm assuming Task is Preallocated reentrant. If so, it'll create an instance for each placed in the code (or a few in a parallell loop). (qualified guess)
03-20-2023 06:01 AM - edited 03-20-2023 06:02 AM
@Vasilich2004 wrote:
Test signal stage.vi is non-reentrant. No changes/
Your profile window clearly proves otherwise! It may not be the VI itself set to be reentrant but the way you launch it in your program.
As others said: It's time to attach some code. Debugging images is always a pitta.