Reset variable value after each execution

[enzofurlan]

---

@billko  escreveu:

Sorry for not getting back to you.  Are you able to save it as previous?  I only have LV 2016.  😞

---

Yes, im attaching the lib too.

When run normally, "event index" should always return 89, but if you run it continuously, a crescent value is returned. And that s the behavior I am having on TestStand suite, each step that call this VI returns an incremented value.

[billko]

Thank you.  Let me chew on this.

[billko]

I know TestStand "pre-loads" your VIs.  I think it might be related to the fact that your Vi stays in memory, like it grabs the equivalent of a new reference each time because of that.  Some things point away from that conclusion, though, like it should work the same way if VI was open but not running.  I believe that "continuous run" is just the equivalent of clicking the run button as fast as possible.

If you're calling something "homegrown", it might be worth thinking about thread execution...

Of course there's always the possibility that the dll isn't quite working correctly.

Sorry, that's all I have.

[enzofurlan]

---

@billko  escreveu:

I know TestStand "pre-loads" your VIs.  I think it might be related to the fact that your Vi stays in memory, like it grabs the equivalent of a new reference each time because of that.  Some things point away from that conclusion, though, like it should work the same way if VI was open but not running.  I believe that "continuous run" is just the equivalent of clicking the run button as fast as possible.

If you're calling something "homegrown", it might be worth thinking about thread execution...

Of course there's always the possibility that the dll isn't quite working correctly.

Sorry, that's all I have.

---

It's alright billko, I really appreciate your effort. I ve found a way to overcome this problem in TestStand, I ll be posting here just for information, even though, I am pretty sure that this can be fixed on LV.

https://forums.ni.com/t5/NI-TestStand/Why-is-my-VI-still-running-after-my-teststand-sequence-has/td-...

if anyone could still help, i d be grateful.

[billko]

---

@enzofurlan wrote:

---

@billko  escreveu:

I know TestStand "pre-loads" your VIs.  I think it might be related to the fact that your Vi stays in memory, like it grabs the equivalent of a new reference each time because of that.  Some things point away from that conclusion, though, like it should work the same way if VI was open but not running.  I believe that "continuous run" is just the equivalent of clicking the run button as fast as possible.

If you're calling something "homegrown", it might be worth thinking about thread execution...

Of course there's always the possibility that the dll isn't quite working correctly.

Sorry, that's all I have.

---

It's alright billko, I really appreciate your effort. I ve found a way to overcome this problem in TestStand, I ll be posting here just for information, even though, I am pretty sure that this can be fixed on LV.

https://forums.ni.com/t5/NI-TestStand/Why-is-my-VI-still-running-after-my-teststand-sequence-has/td-...

if anyone could still help, i d be grateful.

---

Great!  I'm super-curious - and it could lead someone to a solution and not a workaround.  🙂

[enzofurlan]

Still couldn't find an answer inside labview suite, could someone help?