Home > Community > Forums > PCB Design > netlist generation w/ Orcad 16.2 vs 16.3

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

 netlist generation w/ Orcad 16.2 vs 16.3  

Last post Thu, Jan 27 2011 9:34 PM by paragc. 4 replies.
Started by speedracer 30 May 2010 12:01 PM. Topic has 4 replies and 3616 views
Page 1 of 1 (5 items)
Sort Posts:
  • Sun, May 30 2010 12:01 PM

    • speedracer
    • Not Ranked
    • Joined on Fri, Sep 11 2009
    • san diego, CA
    • Posts 14
    • Points 265
    netlist generation w/ Orcad 16.2 vs 16.3 Reply

    Hello!  All,

    Has anyone had any problem generating Allegro netlist using Orcad 16.3 but o.k. with 16.2?  I've been getting <[ALG0082] Illegal character "*" found> w/ 16.3, but my CAD guy has no problem with his 16.2.

    I verified the allegro.cfg files in both versions.  They are the same.   Did Cadence put more check with 16.3 than 16.2?

    Thanks!

    S.R.

    • Post Points: 20
  • Mon, May 31 2010 6:10 AM

    • paragc
    • Top 500 Contributor
    • Joined on Fri, Dec 4 2009
    • Toronto, Ontario
    • Posts 23
    • Points 295
    Re: netlist generation w/ Orcad 16.2 vs 16.3 Reply
    Pl. refer to the section "List of Unsupported Capture-PCB Flow field values" to the "Using Capture with PCB Editor" chapter of the 16.3 Capture User Guide valid character set
    • Post Points: 20
  • Mon, May 31 2010 8:41 AM

    • speedracer
    • Not Ranked
    • Joined on Fri, Sep 11 2009
    • san diego, CA
    • Posts 14
    • Points 265
    Re: netlist generation w/ Orcad 16.2 vs 16.3 Reply

    yes, I can fix the problems by removing "*" from the pin names.  However, I am curious about the different outcomes from the two different versions of Orcad.

    Thanx!

    S.R.

    • Post Points: 20
  • Mon, May 31 2010 8:55 PM

    • paragc
    • Top 500 Contributor
    • Joined on Fri, Dec 4 2009
    • Toronto, Ontario
    • Posts 23
    • Points 295
    Re: netlist generation w/ Orcad 16.2 vs 16.3 Reply
    Yes - you are right. There are additional checks added in OrCAD Capture 16.3 to avoid failures at later stage.
    • Post Points: 5
  • Thu, Jan 27 2011 9:34 PM

    • paragc
    • Top 500 Contributor
    • Joined on Fri, Dec 4 2009
    • Toronto, Ontario
    • Posts 23
    • Points 295
    Re: netlist generation w/ Orcad 16.2 vs 16.3 Reply
    Based on large number of customer requests - The netlist flow was enhanced and restrictions on pin names were removed in 16.3 ISR. Only the following are treated as illegal - 1. Leading and trailing spaces 2. ‘!’ and ‘ ( single quote)
    • Post Points: 5
Page 1 of 1 (5 items)
Sort Posts:
Started by speedracer at 30 May 2010 12:01 PM. Topic has 4 replies.