• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Allegro X Capture CIS
  3. Parameters/.param component fails physical DRC, results...

Stats

  • State Not Answered
  • Replies 1
  • Subscribers 42
  • Views 1946
  • Members are here 0
More Content

Parameters/.param component fails physical DRC, results in error. Cannot convert to PCB

SS202408303624
SS202408303624 10 months ago

I'm running Orcad 23.1. I'm new to Orcad, and more used to LTSpice, so a lot of the quirks of this software often confuse me.

I have a "parameters" (SPECIAL.olb/PARAM) component in my circuit, to set global parameters that i use throughout the circuit. I want to make a PCB from my schematic, however, this requires the circuit to pass design rule checking.
.
For some reason, i get a physical DRC error related to the "parameters" component, which has referece set to '1', with the description "WARNING(ORCAP-36050): No pins are present in 1. Ignoring this component in the netlist.".

Why is this an error, when the description suggests it's a warning?

If i try to waive the error, it just re-appears when i do the DRC again.

A parameters header shouldn't need to have any pins, right? It's should just translate to ".param Something=..., AnotherThing=..." in PSpice, and have no effect on the PCB side of things, right? I'm very confused.

I can't find any documentation online about this.

I found a (possibly) related post from someone using orcad 17.4, where they claim the version 17.4 is broken, and that this error never occured in the prior version 17.2 (link: community.cadence.com/.../17-4-design-sync-parts-without-footprint). Downgrading to version 17.2 solved it for them. If this is a bug, why is such an essential feature still not fixed in version 23.1? Coming from LTSpice, i use .param all the time.

I've tried setting the parameters "FOOTPRINT_IGNORE", "NETLIST_IGNORE", "DRC_IGNORE" all to TRUE (i've tried all of them one-by-one and all together), and it still gives the same error. The "PSpiceOnly" property is also set to TRUE, like it is by default.

Some claim this error can be mitigated by explicitly setting the "Ignored" pin property to TRUE for all pins, but this component doesn't have any pins, so how does that make any sense? Should i make a dangling/dummy pin just to suppress the error? How can i do that if the component has no 'part'?

I can simulate the circuit without problem, by the way, and it behaves just like it should.

This is my session log:

```

ERROR(ORCAP-2213): Checking Physical Rules
WARNING(ORCAP-36050): No pins are present in 1. Ignoring this component in netlist. /1:  MAIN, PAGE1  (8.10, 0.40)

INFO(ORCAP-2211): Check High Speed Properties Syntax

INFO(ORCAP-2212): Check Power Ground Mismatch

Reporting Unused Refdes in multiple part packages
Part                           Quantity                           Reference
-----------------------------------------------------------------------------------------

```

  • Cancel
  • Sign in to reply
  • rg13
    0 rg13 10 months ago

    It's an already known subject and a Cadence Change Request (CCR) is in place for this. RnD may consider it while planning for future releases.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information