I'm in need of making a routine that shows on the screen the yield of tested boards. To improve the efficiency of my fixtures that would help me a lot.
Somebody already did something like that or have any idea to help me???
In this same routine could show me my top offenders of failures.
would you look at the attached picture to see if this is something that you want?
The screen capture shows the "first PASS yield" (FPY) for the product tested on the Agilent i3070 ICT system.
Below the FPY is a list of top hitters of probes related to failures detected. We believe that this would help the user identify if probes are causing the current failures due to false rejects.
I already knew this feature, but only a few of our machines that have this feature. Some are older software versions as Agilent Medalist i3070 05.40p.
Actually I was wanting the FPY appeared on the screen of the BT-BASIC and generate a txt file to make it registered this data. This would have to be done on the testplan. Ive started doing something similar, but I had some bugs during testing. So I asked if anyone had done something like that to be able to help me.
If you have or know to do it would be of great help!!
I have created some sample codes that you can use.
= sample FPY routines (just FPY). You can use this to try out the FPY tracking process/routines
= sample testplan with the FPY algorithms added into it to show you where the FPY statements can be placed within the testplan. The FPY routines are indicated by "!FPY" at the end of the line. The statements requiring testheads have been commented ("!ADR>"), so you can run this testplan on your development station.
= the FPY log file to store the current FPY results
Would you like to try it out to see if it works for you?
I'm using this routine to create the Daily yield file saving all files with the current day, but I am facing a problem that every day when upsets overnight the counter is not reset and is accumulating the previous day's value polluting the yield. Could you help me to make this file was reset every day at 00:00 hs.
I have updated the "fpy_track" and "testplan_fpy_nth" files to include some statements to reset the FPY count.
The assumption that I have made is that if the date changes since the last entry, the count would be reset. This would be true when the testing crosses midnight and/or when the test has not been executed for a few days.
It did not work!! I've validated in production line and it didn't work out this new routine that you sent me!
As the file is generated every time and from one day to the next the file continues to be raised this sum file with the previous day. I am not able to extract the data that way.
You would have some other idea to help me???
The sample testplan that I sent earlier will not work if you change the filename every midnight. This is because it relies on reading the file to reset the variables. I have added some code into the sample testplan to manage the change in the output file name and the use of a log directory. This will suit your needs.
I have sent your production testplan to you. The sample testplan is attached for your reference.
I am sending you a log file your email that shows the count being made strange. After 12:00 am is locked into two boards, and with it the rest of the day is the wrong account. Would you look at me?
I need even this script.
Another thing it stopped generating the file with the folder FPY with the amount of yield per day for my use is more important to generate a daily archive rather than be printing on the screen.