Home > Community > Forums > Logic Design > Anyone ever import an ATE tester STDF fail log into Encounter Diagnostics?

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

 Anyone ever import an ATE tester STDF fail log into Encounter Diagnostics? 

Last post Thu, Jan 12 2012 4:18 PM by SteveJ. 0 replies.
Started by SteveJ 12 Jan 2012 04:18 PM. Topic has 0 replies and 2554 views
Page 1 of 1 (1 items)
Sort Posts:
  • Thu, Jan 12 2012 4:18 PM

    • SteveJ
    • Not Ranked
    • Joined on Thu, Jan 12 2012
    • Posts 1
    • Points 5
    Anyone ever import an ATE tester STDF fail log into Encounter Diagnostics? Reply

    STDF, an industry standard format and yet Encounter only supports Chip Pad Pattern (CPP) and it's own format generated output. The convert_failures_to_cpp.pl script seems too generic to be of much use and the instructions leave much to be desired as it doesn't line-up with standard output from a tester.

    Some of the documents on Cadence solutions seem to imply that Encounter Diagnostics in Volume mode will take in an SQL style database but once again user guide rather vague, more like you have to build that from CPP inputs for different die.

    • Post Points: 5
Page 1 of 1 (1 items)
Sort Posts:
Started by SteveJ at 12 Jan 2012 04:18 PM. Topic has 0 replies.