AnsweredAssumed Answered

Put yield on the screen?

Question asked by leo_br on Mar 28, 2012
Latest reply on Jun 18, 2012 by leo_br

Like • Show 0 Likes0
Comment • 11

Hi,

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.

Thank you and I look forward to returning.

No one else has this question

Outcomes

11 Replies

adrianc Apr 20, 2012 12:41 PM
Mark Correct
Correct Answer
Hi Leo,
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.

rgds ... adrianc
Attachments
- Operator_FPY_a.bmp2.3 MB
Like • Show 0 Likes0
Actions
- leo_br @ adrianc on Mar 29, 2012 4:45 AM
  Mark Correct
  Correct Answer
  Hi, Adrianc
  
  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!!
  
  att, Leo
  Like • Show 0 Likes0
  Actions
  - adrianc @ leo_br on Mar 30, 2012 2:03 AM
    Mark Correct
    Correct Answer
    Hi Leo,
    I have created some sample codes that you can use.
    
    fpy_track
    = sample FPY routines (just FPY). You can use this to try out the FPY tracking process/routines
    
    testplan_fpy_nth
    = 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.
    
    first_pass_yield.txt
    = the FPY log file to store the current FPY results
    
    Would you like to try it out to see if it works for you?
    
    Tell me how it goes.
    Attachments
    FYP_Tracking.zip18.3 KB
    Like • Show 0 Likes0
    Actions
    - leo_br @ adrianc on Apr 2, 2012 6:26 AM
      Mark Correct
      Correct Answer
      Hello,
      
      Thank you Adrianc! Your file has helped me a lot.
      
      I did some updates to make it the way I wanted. If you want I send you what was changed.
      
      Thank you very much!
      Like • Show 0 Likes0
      Actions
      - ANDREL @ leo_br on Apr 11, 2012 5:15 AM
        Mark Correct
        Correct Answer
        +1, usefull code Adrianc, thx!.
        Like • Show 0 Likes0
        Actions
      - leo_br @ leo_br on May 11, 2012 9:39 AM
        Mark Correct
        Correct Answer
        Hi,
        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 would be grateful for the help ...
        Like • Show 0 Likes0
        Actions
        adrianc @ leo_br on May 13, 2012 10:14 PM
        Mark Correct
        Correct Answer
        Hi Leo,
        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.
        
        Hope this works for you.
        Attachments
        FPY_Tracking.zip19.2 KB
        Like • Show 0 Likes0
        Actions
        leo_br @ adrianc on May 17, 2012 7:33 AM
        Mark Correct
        Correct Answer
        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???
        Like • Show 0 Likes0
        Actions
        adrianc @ leo_br on May 17, 2012 6:50 PM
        Mark Correct
        Correct Answer
        Could you send me the testplan?
        It is quite difficult to debug without the testplan, because I do not know the flow of your testplan is.
        
        Note that I just added the codes marked in "!FPY1" so, the engineers should not need to modify the old code.
        
        my email: adrian_cheong@agilent.com
        Like • Show 0 Likes0
        Actions
        adrianc @ adrianc on May 23, 2012 12:30 AM
        Mark Correct
        Correct Answer
        Hi Leo,
        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.
        Attachments
        FPY_Tracking.zip2.7 KB
        Like • Show 0 Likes0
        Actions
        leo_br @ adrianc on Jun 18, 2012 5:27 AM
        Mark Correct
        Correct Answer
        Adrian,
        
        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.
        
        Leo
        Like • Show 0 Likes0
        Actions

Put yield on the screen?

Outcomes

Attachments

Attachments

Attachments

Attachments

Related Content

Recommended Content