Home > Community > Forums > PCB Design > Testprep.log in 15.5

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: *

 Testprep.log in 15.5 

Last post Wed, Mar 15 2006 10:52 AM by archive. 2 replies.
Started by archive 15 Mar 2006 10:52 AM. Topic has 2 replies and 659 views
Page 1 of 1 (3 items)
Sort Posts:
  • Wed, Mar 15 2006 10:52 AM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,950
    Testprep.log in 15.5 Reply

    Greetings -

    It seems that the testprep.log file has changed its format in 15.5.  We have routines that parse this file, and they no longer function properly on files with this new format.  While I admit that I need to study the new format more, I was wondering whether there was a way of producing the old-style format so that our current external routines could still operate effectively.

    Thank you,

    - Phil


    Originally posted in cdnusers.org by phil_alberg
    • Post Points: 0
  • Wed, Mar 15 2006 11:20 AM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,950
    RE: Testprep.log in 15.5 Reply

    Hi Phil,

    The log file changed as a result of the enhancements made to testprep in 15.5 (probe type attributes, multiple via replacements). There are no options to revert to 15.2 format.

    Ed


    Originally posted in cdnusers.org by EdH
    • Post Points: 0
  • Wed, Mar 15 2006 11:24 AM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,950
    RE: Testprep.log in 15.5 Reply

    I believe I see what you are talking about.. The format is very close but has some additional lines in the output for each net that were not there before:
       Processing net XXX (X out of X)... and Net already probed as required..

    I tried to enable the allegro_old_report env variable but the testprep.log report still output the same.

    One suggestion is to do a slight modification to your code to only parse lines which contain an "@" sign  and this will give the same testpoint output as the previous testprep.log.


    Originally posted in cdnusers.org by mcatramb91
    • Post Points: 0
Page 1 of 1 (3 items)
Sort Posts:
Started by archive at 15 Mar 2006 10:52 AM. Topic has 2 replies.