Why do I not see a 'busy' indicator in the operator interface?

[Neumannium]

Hi all,

Ok, probably a stupid question, but here goes.

I can run my tests (mostly VIs) in the teststand LV operator interface without problem. In fact, they run quite well. The problem is, when the user initially hits the 'single pass' button to begin testing, there is about a 20-30 second delay before the actual VI front panel appears, ready for testing. During this time, there is no signal that the operator interface is doing anything. No hourglass, no indicator whatsoever. The problem is that several users have continued to click the 'single pass' button, which causes more than one instance of the VI to open, and slows the testing down, and confuses the operator.

When I play with the LV operator in
terface on MY pc (not the test pc) I DO see an hourglass when I press the 'single pass' button.

Does anyone know where it went on my test machine? The test machine is a Win98. I'm using TS v2.0.1 and LV v6.1

Not a big deal, but would be nice to fix another user complaint!

Thanks in advance,

Dave Neumann

[Nick_Storton]

Hi Dave,

Could you say if you get an hourglass on any application as it could be that the mouse setup in control panel is not set to give an hourglass when the PC is busy.

Regards,

Nick

[Neumannium]

Nick,

Yes, the cursor turns into an hourglass in other operations. In fact, it turns into an hourglass when I open the Testexec.exe file.

When I try this on my PC, I see a hourglass in a small window (looks like a labview panel), the cursor doesn't change. I don't see this labview panel on the test machine.

Hope that clears it up a bit.

Thanks,

Dave

[Nick_Storton]

Hi Dave,
The busy indicator is indeed a LabVIEW vi it is called:- TestStand - Busy Indicator.vi and it resides in the following location:- C:\TestStand\OperatorInterfaces\NI\LV\Common VIs.I think you probably need to ensure that this vi is copied onto your test machine in the same directory as the vi's that are called by the runtime operator interface.

hope this helps,

Nick

[Neumannium]

Nick,

Thanks for your help.

In the 'testexec' folder there is only a testexec.llb file. I've copied this and examined it and found the 'Busy Indicator.vi' in the library.

I assume these are the vi's used by testexec when it opens the operator interface, but for some reason that vi is not being properly used.

Thanks again for your help,

Dave

[Nick_Storton]

Hi Dave,
Are you using the shipping LV user interface or is it a modified version? Also are you using a compiled version on the test machine or is the user interface running in the LV ADE? Do you see the busy indicator just before and just after the login dialog? I have been able to replicate the problem you describe by moving the busy vi to a different location.

regards,
Nick

[Neumannium]

Nick,

I'm using the shipped version of the operator interface -- I haven't made any alterations to it at all.

I compiled the test engine in Teststand and then used the setup.exe and .cab files to install it on the test machine. When I did the compile, I included the 'common vi' folder (where the busy indicator vi is located on my development machine).

Any other questions, let me know.

Thanks again for your help.

Dave

[Nick_Storton]

Hi Dave,
Could you check to see if you have TestStand - Show Busy Indicator.vi in your testexec.llb. This is the vi that calls the busy indicator vi within the operator interface.

Regards,
Nick

[Neumannium]

Nick,

Yes, Teststand - Show Busy Indicator.vi is in the testexec.llb file.

Thanks again,

Dave