Extra Pin Found in Component Display Mode

Parent category: Violations Associated with Components

Default report mode:

Summary

This violation occurs if an extra pin has been detected in one of the display modes for a part.

Notification

If compiler errors and warnings are enabled for display on the schematic (enabled on the Schematic - Compiler page of the Preferences dialog) an offending object will display a colored squiggle beneath it. A notification is also displayed in the Messages panel in the following format:

Extra Pin <Identifier> in <DisplayMode> of part <PartName>

where:

• Identifier is used to identify the pin in question. When compiling a schematic library document, the identifier appears in the format PhysicalComponentName-PinDesignator (e.g. DIP14-15). When compiling the source schematic or project, the identifier appears in the format PartDesignator-PinDesignator (Inferred) (e.g. X1-1 (Inferred)).
• DisplayMode is the specific graphical representation mode for the part in which the extra pin has been found. A part has a Normal mode and can have up to 255 defined Alternate modes
• PartName is either the physical component name or the designator for the affected part, depending on whether you are compiling the schematic library document or source schematic sheet/project respectively.

Recommendation for Resolution

This violation typically arises when an alternate graphical mode is defined for a component and either:

• An extra pin has been added to the display that is not specified in the Normal display mode, or
• A pin has been specified with a different Designator and/or Name to a pin specified in the Normal display mode.

Not only must there be an identical number of pins between graphical display modes, the pins must be identical in both Designator and Name.

In the source schematic library, display the offending display mode for the component and delete the extra pin. This can be performed directly on the schematic sheet for a part that has been placed already, but you would typically tackle the problem from within the library, then push the change across (Tools » Update Schematics).