UNIT 4: ELECTRICAL CAD LAB - COMPREHENSIVE NOTES

4.1 Advanced Schematic Design & Symbol Management

4.1.1 Working with Advanced Symbol Libraries (IEC, ANSI, JIC standards)

• Key Standards:

  • IEC (International Electrotechnical Commission): Circular symbols, minimal text. Common in Europe/global. e.g., Relay coil is a circle.

  • ANSI (American National Standards Institute): Rectangular/squared symbols with internal logic. Common in North America. e.g., Relay coil is a rectangle.

  • JIC (Japanese Industrial Standards): Similar to ANSI but with specific variations.

• Selection: Library choice is project-specific and must be consistent throughout a project.

• > [!TIP] Exams often ask to identify/differentiate IEC vs. ANSI symbols for common devices (relays, contacts, motors).

4.1.2 Creating and Modifying Custom Symbols

• Process:

  1. Duplicate an existing similar symbol.

  2. Edit graphic elements (lines, arcs) in symbol editor.

  3. Define pin numbers and locations (critical for connectivity).

  4. Add attribute fields (e.g., >Part Number<, >Description<).

  5. Save to a custom library (never edit default libraries).

• Attributes: Text fields enclosed in <> that pull data from the component database (e.g., >Catalog<).

4.1.3 Intelligent Components: Adding and Managing Component Data

• Component Database/ Catalog: Central repository linking a symbol to real-world part data (Manufacturer, Part #, Ratings, Price).

• Assignment: In schematic, after placing a symbol, assign a catalog number from the database. All associated attributes (Description, Manufacturer) populate automatically.

• > [!TIP] This creates the intelligence for automatic Bill of Materials (BOM) generation.

4.1.4 Using Real-Time Cross-Referencing

• Purpose: Automatically tracks relationships between components.

• Key Types:

  • Coil/Contact Cross-Ref: Shows which coil a contact belongs to (and vice-versa). Format: CR1 coil, contacts show CR1:1, CR1:2.

  • Terminal Cross-Ref: Shows all wires connected to a terminal block point. Format: TB1-1 connects to TB1-1 on another page.

  • PLC I/O Cross-Ref: Links schematic tag (e.g., %I0.0) to physical slot/point in PLC configuration.

• Mechanism: Based on unique tag names and net labels.

4.1.5 Advanced Wiring and Net Labeling Strategies

• Net Label: Text assigned to a wire network. All wires with the same net label are electrically connected, even if not physically drawn together.

• Power Ports/Plane: Special symbols for global power nets (e.g., +24V, L1, N). Avoids drawing long power wires across multiple pages.

• Signal Conditioning: Use net labels like START_PB_SIG to clearly denote signal purpose vs. physical wire.

4.1.6 Hierarchical Design and Sub-drawing (Block) Usage

• Purpose: Manage complexity in large systems (e.g., a motor control center).

• Block (Sub-drawing): A separate schematic page representing a functional unit (e.g., "Motor Starter 1").

• Hierarchy:

  • Top-Level (Sheet): Shows blocks as single symbols with interface ports (inputs/outputs).

  • Child Sheet (Block): Contains the detailed internal wiring.

• Connectivity: Wires connect to ports on the block symbol, which map to nets inside the child sheet.

• > [!TIP] Enables modular design and reuse of standard circuits.

4.2 Panel Layout & Physical Design

4.2.1 Introduction to Panel Layout Workspace/Tools

• Separate workspace/environment from schematic. Focuses on physical component placement within an enclosure.

• Tools: Component browser (from schematic), routing tools (for wires/cables), dimensioning tools, 3D view.

4.2.2 Component Placement and Spacing Rules

• Clearance Rules: Minimum distances defined by:

  • Electrical Safety Standards (e.g., UL 508A, NFPA 79).

  • Heat Dissipation: Space between heat-generating devices (drives, transformers).

  • Maintenance Access: Space for wiring, tool access, component removal.

• Logical Grouping: Place related devices together (e.g., PLC rack with I/O modules, motor starters with overloads).

• > [!TIP] Design Rule Check (DRC) for panel layout can enforce these clearance rules automatically.

4.2.3 Creating and Using 3D Models/Footprints for Components

• Footprint (2D): Copper pattern and solder points for PCB design. Less relevant for panel layout.

• 3D Model (for Panel): Represents the physical envelope (height, width, depth) of the component. Crucial for:

  • Interference Checking: Detecting collisions between components or with enclosure walls.

  • Accurate Cable Routing.

• Models are typically sourced from manufacturer websites (STEP, SLDPRT formats) or CAD library.

4.2.4 Routing Wires and Cables in Panel

• Path Definition: Wires route along ducts, trays, or conduits inside the panel.

• Cable Bundles: Group multiple wires into a single cable assembly for routing.

• Spools/Wire Numbers: Assign wire numbers from a spool. Software tracks total length used per spool.

• Termination Points: Wire ends connect to component terminals or terminal blocks.

4.2.5 Dimensioning and Annotating Panel Drawings

• Overall Dimensions: Enclosure size, mounting hole locations.

• Component Locations: X-Y coordinates from a reference point (e.g., panel bottom-left).

• Annotations: Labels for wire numbers, cable IDs, component tags (from schematic), and drill charts for mounting holes.

4.2.6 Generating Bill of Materials (BOM) from Panel Layout

• BOM Content: List of all physically mounted components (including terminals, duct, power supplies).

• Source: Derived from placed components, not the schematic. May include quantities and locations (e.g., "Terminal Block, 10-position, Mounted on DIN rail, Left wall").

• > [!TIP] Panel BOM often includes hardware (screws, DIN rail) not present in schematic.

4.3 PLC (Programmable Logic Controller) Integration

4.3.1 Inserting and Configuring PLC Racks/Modules

• Place PLC rack symbol.

• Insert power supply and I/O modules into specific slots in the rack.

• Configure module type (e.g., 16-point discrete input, 8-point relay output).

4.3.2 PLC I/O Addressing and Tagging Conventions

• Address: Physical location in the PLC memory. Format is CPU-specific (e.g., Siemens: %I0.0, Allen-Bradley: I:0/0).

• Tag (Symbolic Name): Human-readable name (e.g., MOTOR_START_PB, PUMP_1_RUNNING).

• Link: The tag in the schematic is mapped to the PLC I/O address via the module slot/point.

• > [!TIP] Consistency in tag naming convention (e.g., [Device]_[Function]) is critical for readability and troubleshooting.

4.3.3 Generating PLC I/O Assignment Lists/Reports

• Report Content: Table listing:

  • PLC Address (e.g., %Q0.0)

  • Tag/Symbol Name (e.g., MOTOR_1_CONTACTOR)

  • Description (e.g., "Motor 1 Contactor Coil")

  • Schematic Page/Reference

• Purpose: Primary document for programmer and panel builder to wire field devices to correct PLC terminals.

4.3.4 Linking Schematic Logic to Physical PLC I/O Points

• Workflow:

  1. Place PLC input symbol (e.g., pushbutton) in schematic.

  2. Assign it a tag (e.g., START_PB).

  3. In PLC configuration, map the tag START_PB to a specific physical input point (e.g., Slot 0, Point 0 of Input Module).

  4. Software creates the link: Schematic START_PB net ↔ PLC %I0.0.

• Result: Wire from field device (pushbutton) connects to PLC terminal corresponding to %I0.0.

4.4 Reporting, Documentation & Data Extraction

4.4.1 Generating Standard Reports

• Component List (BOM): All parts used, with catalog data.

• Wire List: All wires in the project, with:

  • Wire Number

  • From Component/ Pin

  • To Component/ Pin

  • Wire Type/Gauge

  • Length (if routed)

• Terminal List: All terminal block points, with connected wire numbers on each side.

• Cable List: All multi-conductor cables, with core assignments.

4.4.2 Customizing Report Formats and Filters

• Filters: Exclude certain component types (e.g., "no fasteners"), include only specific pages.

• Columns: Select which attributes to display (Part #, Description, Manufacturer, Supplier, Cost).

• Sorting/Grouping: By location, function, or manufacturer.

4.4.3 Exporting Data to Excel/CSV for BOM Management

• Purpose: Import into ERP/MRP systems or external BOM management tools.

• Format: CSV (Comma Separated Values) is universal.

• > [!TIP] Ensure consistent part numbering (catalog numbers) before export to avoid duplicate entries in the ERP.

4.4.4 Creating Wire Connection Diagrams and Interconnection Diagrams

• Wire Connection Diagram (WCD): Shows all connections for a specific wire number across all sheets/pages.

• Interconnection Diagram (ICD): Shows terminal-to-terminal connections, often used for terminal block wiring. Can be a "one-line" representation of terminal block connections.

• Use Case: Essential for field wiring and troubleshooting.

4.4.5 Automatic Generation of Legends and Symbol Tables

• Legend: List of symbols used on a drawing sheet with their description.

• Symbol Table: Project-wide list of all unique symbols and their quantities.

• Automation: Generated directly from the schematic database.

4.5 Project Management & Collaboration Tools

4.5.1 Project Structure and File Organization

• Project File (.prj): Master file that references all drawings, libraries, and settings.

• Drawing Files (.dwg, .sch): Individual schematic or layout drawings.

• Library Files (.lib): Contain symbol and footprint definitions.

• Best Practice: Use a single project file for a complete system. Keep all files in a structured folder hierarchy.

4.5.2 Using Project-Wide Find and Replace

• Scope: Operates across all drawings in the project.

• Functions:

  • Find/Replace tag names (e.g., change all M1 to MOTOR_1).

  • Find/Replace descriptions or attribute values.

• > [!TIP] Extreme caution required. Use preview and understand global impact. Often requires project-wide reannotation after changes.

4.5.3 Managing Design Revisions and Drawing Sets

• Revision Cloud: Highlights changed areas on a drawing.

• Revision Table/Block: On drawing border, logs revision number, date, description, author.

• Drawing Set: A compiled PDF/plot of all relevant drawings for a release.

• Version Control: Use file naming (e.g., Project_Rev1.dwg) or dedicated PLM/ECAD-MRP systems.

4.5.4 Basic Principles of Design Collaboration

• External References (Xrefs): Attaching another drawing file as a non-editable reference.

• Use Case in Electrical CAD:

  • Referencing a piping & instrumentation diagram (P&ID) or civil/architectural layout as background for panel location.

  • Less common for pure electrical schematics (which are usually in one project).

• Overlay vs. Attachment: Overlay loads every time; Attachment is a one-time bind.

4.5.5 Introduction to Design Validation and Error Checking Tools

• ERC (Electrical Rule Check): Checks schematic for electrical errors.

  • Unconnected Pins: Power pins not connected to a power source.

  • Duplicate Tags: Two components with same tag.

  • Unconnected Wires: Wires with no net label or connection.

• DRC (Design Rule Check): Checks PCB/panel layout for physical violations (clearance, short circuits).

• > [!TIP] Always run ERC/DRC before generating final reports or releasing drawings.

4.6 Advanced Features & Industry Workflows

4.6.1 Introduction to Macro/Intelligent Symbol Usage for Standard Circuits

• Macro: A pre-built, parameterized sub-circuit (e.g., "Motor Starter with Seal-in").

• Intelligent Symbol: A single symbol that expands into multiple components/wires when placed.

• Benefit: Ensures consistency, reduces design time, and embeds best-practice logic.

• Parameters: User inputs (e.g., Contactor Size=30A, Overload Range=20-30A) to customize the macro.

4.6.2 Basic Scripting or Automation for Repetitive Tasks

• Purpose: Automate bulk operations (e.g., renumbering all wires, updating all title blocks).

• Common Languages/Tools:

  • LISP (AutoCAD-based CAD): For AutoCAD Electrical.

  • Built-in Macros/Recorders: Record a sequence of actions and replay.

  • API Access: For advanced integration with other software.

• > [!TIP] This is an advanced skill that greatly enhances productivity but requires programming knowledge.

4.6.3 Understanding the Link Between Schematic, Layout, and Reports

• Complete Project Flow:

  1. Schematic: Defines logical connectivity and component tags.

  2. Panel Layout: Uses component tags from schematic to place physical devices and route wires/cables.

  3. Reports: Extract data from both schematic (component list, wire list) and layout (cut list, wire lengths).

• Critical Link: Unique, consistent tagging across all domains is what makes this integration possible.

4.6.4 Preparing Drawings for Manufacturing and Assembly

• Fabrication Drawings: Detailed drawings for fabricating parts (e.g., panel drilling template, wire harness assembly).

• Wiring Diagrams: Simplified diagrams for electricians to make field connections. Often derived from interconnection diagrams.

• Assembly Instructions: Annotations on layout showing torque specs, wire tie locations, etc.

• Output: PDF/Plot files with all necessary dimensions, notes, and part numbers.

4.6.5 Overview of Electrical CAD Standards

• IEEE: Standard for graphic symbols (e.g., IEEE 315).

• NFPA 79 (Electrical Standard for Industrial Machinery): Defines safety requirements, wire routing, and documentation standards for machinery. Heavily referenced in North America.

• ISO 1219 (Fluid Power): Symbols for hydraulic/pneumatic components.

• IEC 61346 (Reference Designation): System for tagging (e.g., K for relays, Q for circuit breakers).

• Application: CAD software libraries are often pre-loaded with these standards. Project settings define which standard to use.

4.7 Troubleshooting & Best Practices

4.7.1 Common Schematic Errors and How to Resolve Them

• Unconnected Pins/Wires: Run ERC. Ensure all pins are connected to a net (use power ports for unused power inputs).

• Duplicate Tags: Run ERC. Use Project-Wide Find and Replace to renumber systematically.

• Missing Catalog Assignment: Component appears in BOM as "?" or "UNKNOWN". Assign a valid catalog number from the database.

• Orphaned Components: Components not connected to any net. Delete or connect.

4.7.2 Resolving Cross-Reference and Report Discrepancies

• Symptom: Cross-reference report shows a contact but no coil, or wire list shows a wire not in schematic.

• Cause: Usually inconsistent tagging or unconnected nets.

• Fix:

  1. Verify coil and contact have exact same base tag (e.g., CR1 vs CR1:1).

  2. Check for net label typos.

  3. Run ERC and fix all errors.

  4. Update all cross-references (menu command).

4.7.3 Best Practices for File Naming, Layer Management, and Drawing Organization

• File Naming: ProjectName_SheetNumber_Revision.dwg (e.g., PM_System_E101_R0.dwg).

• Layers (if used): Standardize layer names (e.g., POWER, CONTROL, PLC, NOTE). Use layers to control visibility/plotting.

• Drawing Organization:

  • Functional Grouping: Sheets grouped by system (Power, Control, PLC).

  • Logical Flow: From power source to load.

  • Title Block: Must contain Project Name, Sheet Number, Revision, Designer, Checker.

4.7.4 Tips for Efficient Design and Reducing Errors

1. Start with a Template: Pre-configured title block, layers, and settings.

2. Use Hierarchical Design for large projects.

3. Place Components First, Then Wire: Reduces wire crossing.

4. Use Net Labels Liberally: Improves readability and reduces wire clutter.

5. Assign Catalog Numbers As You Go: Don't leave it for the end.

6. Run ERC Frequently, not just at the end.

4.7.5 Backing Up and Archiving Electrical CAD Projects

• Backup: Frequent copies of the entire project folder to a separate drive/cloud. Use versioning.

• Archive: For a completed project, create a read-only package containing:

  • All drawing files.

  • All library files used.

  • All generated reports (PDF, Excel).

  • Note: Without the libraries, drawings may not open correctly.

• > [!TIP] Use the CAD software's "Package Project" or "Archive" utility, which collects all dependent files automatically.