07-13-2016 08:01 AM
I tried to develop the following simulation: Concurrently run two SignalExpress projects with similar steps, but different configurations defined.
However, what actually happened was: The first *.seproj runs as expected. However, when I run the second *.seproj file, it uses the configuration of the first project, rather than its own.
File and folder (in bold) setup:
Steps taken:
Is this behavior correct? I expected the re-entrant nature of the VIs (developed from a SignalExpress template) would ensure that different INI files would be read.
Thank you.
Solved! Go to Solution.
07-14-2016 06:30 PM
Hi Dhakkan,
Can I ask how you obtain the VI path? The Current VI's Path Function behaves a little different than you might expect when inside a built application as detailed here:
http://zone.ni.com/reference/en-XX/help/371361E-01/glang/current_vis_path/
If you try running Project2 instead, does the behavior reverse itself?
07-14-2016 11:32 PM
Hello Dale,
Thanks for your response.
I should have noted this earlier... When the scenario is reversed, i.e. Project2 starts before Project1; then Project2.ini path is displayed in both dialogs. So, the situation is reproducible in reverse as well.
"Current VI's Path" function is being used to re-construct the INI file path. I am using 'Strip Path' function to remove "VILibrary.llb" from the path as well. The situation described in the link you provided is similar. At the next interval sometime today, I'll trim up the whole thing into a simple set of code modules and attach it in my next post.
07-18-2016 12:00 PM
Alright thanks I'll look out for that. I haven't had much succes trying to replicate what you are seeing unfortunately.
07-19-2016 08:40 AM
Hello Dale,
Here's an extremely simple version that appears to reproduce the issue in my computer. Environment details:
Steps taken to create the attached ZIP file:
Now execute as stated in the opening post (and vice versa).
NOTE: In my environment, as long as SignalExpress was never 'removed' from computer memory, the second seproj file will always show the path to the first folder even if the first seproj has stopped executing and closed! That is,
The reverse is also true.
Thanks for any insight you may be able to provide.
07-20-2016 04:06 PM
Thanks for the information!
I found that the issue goes away if you give the VIs different names. Would this be a viable workaround? The issue seems to be that SignalExpress will just use the first VI of a particular name without check that it's the 'right' VI.
07-21-2016 12:48 PM
Hi Dale,
That's a very viable workaround. Thanks! for the tip.
That still leaves me to wonder why a 'reentrant' VI would work as demonstrated. It would be great to know if our observations indicate whether the software working as designed or not.
Regards,
Vishak
07-21-2016 05:20 PM
I'm not entriely sure what causes this to happen. I believe that LabVIEW also has issues if you try to load two VIs of the same name at the same time unless they are placed in seperate projects.