Control Labview VI from TestStand

[Ray.R]

THis was a slightly confusing thread... 

Do Cet & Akie work together on this?  😉

[Akie]

Yes...We share the same computer.

[Thoric]

That vi is so shocking I just spilt my drink

I shudder at the thought of ever having to work with it...

[Akie]

I also felt confused when I first saw that vi...anyway,we don't have time to edit that vi,so I only do some sequences to call that vi.

[Thoric]

Well, Akie, feel free to point those that created the vi at this forum thread - it might enlighten them a little bit.

[Akie]

Well...They have already finished thier intern last year when I started to take over the proj.My mentor said they did not know anything about Labview at that time,so they sent their VI to somewhere and got a lot of help...I am not very sure whether they have NI accounts,but I believe they don't.

Anyway,an intern is just a way to gain AUs for them.Maybe they are not major in such things, and we cannot expect too much,as long as their VI can run,it is considered as no problem...

[Thoric]

---

...they sent their VI to somewhere and got a lot of help...

---

This was created with help !?

With vi's written in this way, there is far too much room for human error to creep in - if just one of those many repetitive process blocks hasn't been wired up correctly then one of your outputs will be erroneous, but you may never 'see' it. Personally, for my own peace of mind, I'd be wanting to re-write most of that just to be throughly sure that it does work as expected.

Good luck with it! 

[Akie]

Thank you for being willing to spend time on that,I will also try to study more on LabView VIs to fix problems.

[Ray.R]

---

Akie wrote:

as long as their VI can run,it is considered as no problem

---

An important lesson in any programming language..

Being able to build & execute a software (making it run), is not an indication that it is doing what is supposed to do.  Writing a software that simply does what it is supposed to do may not handle exceptions that will be encountered (errors, out of bound values, you-name-it, etc...)

Therefore, a software that runs is far from being without problems..  😉