How can I activate a functional global without displaying a LabVIEW VI ??

[Noriyuki]

Hello. I'm using Teststand and have been got stuck on a problem now.

Whenever I communicate to a LabVIEW VI which is activated as a functional global,  I purposely displayed the LabVIEW VI on front pannel to make sure the data communication.

However once I released the check mark 'Show VI front pannel when called' , the data transmission including receiving vanished. As a matter of fact, always the numeric data resturns ' 0 '.

So the data communication must be transacted with a shift resgister function at each step in Teststand, so it always provides a command to the functional global VI for an e-num  item selector.

Therefore it looks the shift register function doesn't work at the point anymore in the functional global VI.

Otherwise as long as I suspend the VI as a display, checking on the box 'Show VI front pannel when called' , I exactly can make sure the data communication , receiving the command and returning the data.

Have you heard that kind of unusal problem before?

Do you think it happened due to data communication or just simply Teststand applicational error?

If it has some useful information, I try to fix them. 

Thank you.

Noriyuki

[Mathan]

duplicate post

[rolfk]

---

hirose wrote:

Hello. I'm using Teststand and have been got stuck on a problem now.

Whenever I communicate to a LabVIEW VI which is activated as a functional global,  I purposely displayed the LabVIEW VI on front pannel to make sure the data communication.

However once I released the check mark 'Show VI front pannel when called' , the data transmission including receiving vanished. As a matter of fact, always the numeric data resturns ' 0 '.

So the data communication must be transacted with a shift resgister function at each step in Teststand, so it always provides a command to the functional global VI for an e-num  item selector.

Therefore it looks the shift register function doesn't work at the point anymore in the functional global VI.

Otherwise as long as I suspend the VI as a display, checking on the box 'Show VI front pannel when called' , I exactly can make sure the data communication , receiving the command and returning the data.

Have you heard that kind of unusal problem before?

Do you think it happened due to data communication or just simply Teststand applicational error?

If it has some useful information, I try to fix them. 

Thank you.

Noriyuki

---

I'm not sure about the current versions of TestStand but in previous versions you had the possibility to preload certain test steps or initializer VIs. TestStand made sure to keep them in memory for the entire duration of the particular test sequence. You create such an initializer VI and call your init method in there and mark that step as preload. On loading the sequence or initializing it your step gets called and stays in memory for the entire duration. I would be surprised if TestStand doesn't support this anymore.

Rolf Kalbermatter

[Noriyuki]

Thank you very much for answering back and giving me the information.

So I wasn't  sure if my description worked or not but at least we are trying to that problem on your way.

The first thing we marked was how to know a VI is preloaded as the Initializer V.I.

Therefore we are trying to use and place an initial VI which used to be in a first step of a sequencall on the sequence step as the first memory reminder.

Do you think my approach is right?

So we thought it can be worked when the first step is put out if the step used to be in the sequencecall and used to be called throught it.

Otherwise we thought the VI actual load is assigned at each step and can be loaded one by one if without checking on 'show VI front panel when called'. And the VI is suspended and can be durable as long as being showed as the diplay .

If you would know something about the 'preload ' and a way of setting and suspend a VI, please provide us the useful information.

Similar approach would be welcomed sincerely.

Thank you.

Hirose