asynchrous testing

[sharanu.dambal@geind.ge.com]

Hi ,

I am building automated Burn-in test tool for product . I have created the work cell for each device . The work cell contains the information like start test,time stamp  ,end time ..etc .  Each work cell will have to under go different test steps (Test1 ,Test2.....etc). The  requirement is ,test run should be asynchronous,meaning when test running for Work cell 1 ,the other two work cell testing  need to be ideal. When ever the test completes for the work cell 1 , testing for the work cell2 should start and so on . As per the front panel ,access for all the work cell should be available for the user . Please find the attachment for the VI written for user to initiates the test for all the work cell . Please help what are the tools i need to used to get the work cell test sequencing .

Regards,

Sharanu

[altenbach]

You code has serious dataflow problems and cannot work in its current state. For example, any of the inner loops can never be stopped because the stop control is outside the loop.

I don't uderstand why you even need a "stop burn-in" button. Without seeing the "burn in stop sub.vi" I cannot tell for sure.

Your use of event structures is also incorrect. There is no way to tell what boolean the case structure gets when the event triggers, but most likely it will get a stale value.

---

sharanu.dambal@geind.ge.com wrote:

The  requirement is ,test run should be asynchronous,meaning when test running for Work cell 1 ,the other two work cell testing  need to be ideal. When ever the test completes for the work cell 1 , testing for the work cell2 should start and so on . As per the front panel ,access for all the work cell should be available for the user .

---

I don't uderstand what "ideal" mean in this context. Can you explain?

Maybe you can explain in more details what this program is supposed to do. What is a "work cell"? How long is a "burn-in". Do you need the capability to stop an ongoing burn-in test? What should happen if an error occurs.

[sharanu.dambal@geind.ge.com]

Hi,

Thanks for your response . The following is the brief description of the Automated Burn -in Tool

1. This tool is cable of testing Multiple number of boards(PWA/PCB) during Burn-in process

2.  Burn-In duration would be 16 hours

3. Work cell is associated with board placed on the fixture ( Fixture1 will have board1 and it associated with work cell1 on the front panel)

4. User needs to enter the serial number of the board and enter the serial number and click the start button to initiate the testing

5. Each board will be tested once in hours , hence each board will be tested for 16 times during 16 hours burn-in

6. Once the burn in is over the test status and the burn in status will be displayed on the front panel

7. Board(PWA/PCB) communicated with PC through RS232.

8. Serial port is multiplexed for all the all the boards that under goes for burn in testing ,hence any given point of time only one board (respective work cell) will be getting tested.

Hope the above mentioned will be help you provide the solution

Thanks

Sharanu

[Matt_S.]

Hi Sharanu,

Altenbach was correct in what he said. There are many data flow problems in your application. You'll never be able to stop the inner loops, because your stop buttons are outside of the loop.

there are other issues as well. It looks as though you've not had a lot of experience with LabVIEW. You might want to consider taking the LabVIEW Basics class. They will cover many things that it appears you need a bit of help with.

If you need help on this application immediately, consider an alliance member.

Alliance Page

Regards,

Matt S.

[sharanu.dambal@geind.ge.com]

Yes .... I have started using Lab view  the first time but have done many project using Lab window CVI .

The VI i have enclosed is just for the front panel where user to select  work cell and to enter the required information. I just would like to what are suitable tools that can be used to achieve the requirement mentioned above .The tools could be event handing ,while loop , timed loop etc . Would like know to which is the suitable method for building the tool.

Regards,

Sharanu

[sharanu.dambal@geind.ge.com]

Hi

Please find the attachment for the sub Vi. As per the front panel section goes it works ok

Regards,

Sharanu

[Matt_S.]

If you're just running this test 16 times with 1 hour delays between each run, you could use a for loop instead of a while loop. Just wire a 16 to the "N" input on the top left of the for loop, and add a 1 hour "Wait". Then inside that for loop you do your testing. You can take a time stamp before you run the for loop, and one after you run the for loop. That would let you see the start and finish times.

-Matt S.