NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Ready to give up on this, I really need some assistance

Hi,

 

First of all, I have learned alot from the knowledge that the experts have given me on this forum for my current project I am working on. Thank You.

 

I have parallel model working great, it is stable, and quick. The final part of the puzzle is getting the "Test UUT" window the way I want it. I am really only trying to do one thing, and I have tried to figure out, but I can't.

 

I am using the parallel model for my test fixture that tests 5 units at a time. Rather than use the the okay button to start the test, I am using a button on my fixture at each station to start the test. The issue is that if I use the button on the fixture to start the unit, I don't get that "Running" indicator that I would if I pressed okay on the GUI.

 

I need to somehow tie the button push on the fixture to the "okay" push on GUI. I tried CVI to perhaps edit the model, but I cannot make heads or tails of what I should do. I have spent HOURS on this and I think I need a little help.

 

Thanks,

Ryan

0 Kudos
Message 1 of 4
(3,338 Views)

Hi Ryan

 

I am struggling to get a feel for how your application hangs together from you post.  Is the button on your text fixture implemented in hardware or software?  If it's hardware you have to configure the process model to detect when the button has been pressed (by polling a Digital IO Line for example).  Once the button press is detected you can allow the process model to continue as normal.  If you are detecting a hardware button push you can set the step that displays the GUI Panel with the OK button on it to skipped (commented out) so that the panel is never displayed. 

 

Here is something that occured to me when reading your post that may help your understanding (apologies in advance if I cover ground your familiar with).  The TestStand process model communicates with the Operator Interface using UI Messages.  Thread.PostUIMessageEx() will appear in your process model all over the place (assuming you are using a model that ships with TestStand).  Calls to Thread.PostUIMessageEx() help me alot when trying to work out what a process model is doing.

 

Hope Im not that far off the mark, let me know.

 

Regards

 

Steve

 

 

0 Kudos
Message 2 of 4
(3,310 Views)

Hi Steve,

 

Thanks for the response. I was in the process of moving so it took a while for me to respond. To answer your questions....

 

Is the button on your text fixture implemented in hardware or software?

Exactly, The buttons are controlled by polling a digital I/O line.

 

If it's hardware you have to configure the process model to detect when the button has been pressed (by polling a Digital IO Line for example).  Once the button press is detected you can allow the process model to continue as normal.  If you are detecting a hardware button push you can set the step that displays the GUI Panel with the OK button on it to skipped (commented out) so that the panel is never displayed. 

I have that part completed, everything runs fine. Pushing the button starts the sequence just fine...it can be started by pressing "Okay" or pushing the button. When I push the button I do not get that "Running" indicator on the screen like I would if I pushed "Okay". That is the issue.

 

Here is something that occured to me when reading your post that may help your understanding (apologies in advance if I cover ground your familiar with).  The TestStand process model communicates with the Operator Interface using UI Messages.  Thread.PostUIMessageEx() will appear in your process model all over the place (assuming you are using a model that ships with TestStand).  Calls to Thread.PostUIMessageEx() help me alot when trying to work out what a process model is doing.

This is a learning process for me, and I was playing with the Thread.PostUIMessageEx() but I wasn't having any luck. Perhaps I will give it another shot. Once again my goal seems simple (haha)...."To have the GUI say "Running" when the hardware button is pushed rather than just start running.

 

Hope Im not that far off the mark, let me know.

Thank you for the help, does this clarify it a little bit?

 


0 Kudos
Message 3 of 4
(3,275 Views)

Hi Ryan

 

Thanks for that, still struggling though I'm affraid.

 

Can you post your process model sequence (or a cutdown version if it is sensitive)?  I have TestStand 4.0 on my machine so if you could save as that version or earlier.

 

Regards

 

Steve 

Message Edited by Cheesey on 11-25-2009 08:12 AM
0 Kudos
Message 4 of 4
(3,273 Views)