how to clear Altium Designer Short-Circuit violation between polygon and via on power plane

By Sai Kiran Pandrala · Last verified: 2026-06-01 · Source: controls-community forums (r/PLC, r/Robotics, r/CNC, r/Fanuc, r/KUKA, r/Cognex, r/labview), OEM service bulletins and changelogs, OEM service manuals, in-controller diagnostic help

When how to clear Altium Designer Short-Circuit violation between polygon and via on power plane hits you on PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026 mid-shift, the first instinct is to cycle power on the controller or hit the master reset. Most of the time you do not have to. The steps below are what a maintenance engineer would do at the cell panel before escalating to the OEM hotline - I keep a fault-history notebook per machine so the working state and parameter set are always reproducible.

What how to clear altium designer short-circuit violation between polygon and via on power plane actually involves on PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026

On PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026 the first three tools that earn their keep are Eagle ULP DRC report scripts, Gerber viewer (Gerbv, KiCad Gerber Viewer) for fab-side cross-check, Altium Designer Messages panel and PCB Rules and Constraints Editor. Each of these surfaces a different layer of the fault - keep at least the first one in your fault-history notebook so the next time this happens you do not start cold.

For verification on PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026, the methods that survive contact with a real second-shift production workload are run KiCad Inspect > Design Rules Checker and export the JSON report and PADS Verify > Connectivity / Clearance / Plane after each route session. Anything less than that and you are shipping on vibes.

Authoritative sources for PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026 that I cross-reference before committing to a fix: ipc.org/standards (IPC-2221, IPC-7351), sw.siemens.com/en-US/product/pads-professional, kicad.org/help/documentation. OEM marketing brochures and trade-press writeups are signal, not ground truth.

The rest of this page is the structured fix path. Start with diagnose, then remediation, then the automation options so you do not have to do this by hand the next time it surfaces. Verify and safety sections at the end are the discipline that keeps the fix from regressing the next time you open the cabinet.

Diagnose first, fix second

Fifth: replay the failing run against a second axis or a second controller on the same PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026 cell. The point is to isolate "this drive" from "this controller" from "the whole cell." If a teammate identical sister-machine works but yours does not, the failure is local to the parameter set or the encoder cable. If the same program faults on every controller in the same cell, you have a cell-wide config change or an OEM-side firmware quirk. Pin the controller firmware version explicitly while you do this: the controller About panel, the firmware hash in the parameter dump, or the system version returned by a SCPI *IDN? query. The version pin is what isolates "the OEM update broke us" from "this machine is on an older firmware than the rest of the cell."

Start by capturing the exact failure signal in writing before you change a single thing on your PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026 setup. On the controller HMI that is the alarm code, the alarm message text, the timestamp, the controller hour-meter, and the part-count when the alarm hit. On the OEM diagnostic interface that is the fault-history dump (Fanuc alarm history, KUKA KSS log, Cognex In-Sight event log) plus the running program block number at the moment of fault. Photograph the HMI screen with the alarm panel open. Do not paraphrase. Most OEM service workflows will not even route the warranty case without the controller serial number, the alarm history dump, and the fault timestamp - the field service engineer pastes the alarm code straight into the OEM diagnostic tool and the first response is "we see the fault, here is what the controller logged."

Second pass: open the PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026 controller diagnostic panel and read the alarm history or fault stack for the failing window. Most modern industrial controllers surface a fault trail (the controller alarm history, the OEM diagnostic interface, the fab MES event log, the cell controller PLC fault table). The alarm history tells you whether the fault was a real condition, a teammate changing a parameter or DI mapping in the same minute, or an OEM-side firmware quirk. Many SRVO or AXIS faults trace to a parameter-level change pushed in the same engineering session in the previous hour - the fault trail makes that obvious without guesswork.

Field notes from real PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026 callouts

Last week on a graveyard shift I chased a phantom PCB Design and EDA Error Codes alarm for two hours before remembering ODB++ inspection in fab CAM tool would have isolated the bad channel in five minutes. For Electronics jobs I keep a battered field notebook of "what bit me on PCB Design and EDA Error Codes and how I cleared it", writing it down the first time has saved me a dozen overnight returns.

Before I sign the work order on a PCB Design and EDA Error Codes job I run `Altium Designer Tools > Design Rule Check with all categories enabled` and tape a printout of the result into the panel, auditors love it and night-shift loves it more. Vendor portals like kicad.org/help/documentation are a starting point for Electronics questions, never the final word. The integrator forums are where the ugly edge cases actually get diagnosed. The Electronics side of PCB Design and EDA Error Codes evolves slowly on paper and fast in firmware, a vendor manual from two years ago is almost guaranteed to miss the new alarm codes.

Tools I actually reach for

For most PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026 faults I start with ODB++ inspection in fab CAM tool, fall back to OrCAD Allegro Constraint Manager, IPC-2581 export verifier, Altium Designer Messages panel and PCB Rules and Constraints Editor, Gerber viewer (Gerbv, KiCad Gerber Viewer) for fab-side cross-check when ODB++ inspection in fab CAM tool cannot surface the answer, and keep Altium Designer Violation Display with Highlight Net handy for the cases where neither answers. That ordering is not academic - it matches the layers of the fault as they tend to surface, so the cheapest signal lands first and the heavier tooling only comes out when the simpler answer does not hold up. My muscle-memory shortcut for this is to run the first tool while the alarm screen is still open, not after I have already cycled controller power.

Verification I run before I call it fixed

Before I mark a PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026 fault resolved, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheaper checks gate the more expensive ones.

OrCAD PCB Editor Tools > Update DRC then Setup > Constraints recheck

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

compare net count between schematic netlist and PCB netlist for parity

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

Altium Designer Tools > Design Rule Check with all categories enabled

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

regenerate copper pour fills before final DRC pass

Only when every line above runs clean do I close the loop and update my fault-history notebook with the timestamps.

Where I check first when the docs disagree

When two sources contradict each other on a PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026 detail, the disambiguation order I lean on is stable. I usually check kicad.org/help/documentation for the ground-truth view on this part of PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026. I usually check cadence.com/en_US/home/support/orcad for the ground-truth view on this part of PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026. I usually check autodesk.com/products/eagle for the ground-truth view on this part of PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026. OEM marketing brochures and trade-press writeups are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim.

Solution-focused remediation path

For PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026 cells where duty-cycle limits or thermal envelopes are suspect, read the in-controller hints honestly. "Servo overcurrent" usually means you hit the peak current envelope of the drive during accel. "Motor overload" is the sustained-thermal signal on the motor winding. "Drive overheat" is the heatsink thermistor signal. Each is telling you the exact same thing in a PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026-specific dialect. Apply duty-cycle dwell for repeated-cycle programs (insert a 500ms dwell between high-load moves), reduce the rapid feedrate, and chunk a long cycle into smaller passes. Decision point: if you are hitting the thermal limit sustained rather than in bursts, the cell is undersized for the workpiece - upgrade the drive amperage rating or request a thermal margin review from the OEM with a written duty-cycle analysis; without it, dial back the throughput at the cell. Replay the failing program against a fresh test workpiece at half the feedrate to confirm the new safe envelope before pushing to the production cell.

Before any destructive step on a PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026 cell, slow down and stage rollback. Snapshot the current firmware revision, the current parameter set (PARAM PUNCH OUT, KUKA archive, Cognex job export), the current ladder and HMI screens, the current I/O mapping, and the current member-roster of teach pendants registered to the cell to a notes entry first. Capture the failing photo, the PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026 alarm history dump, and the timestamp window. Photograph the cell from two angles: the controller HMI showing the alarm, and the cabinet showing the drive status LEDs. Then do the destructive step (clear a parameter, swap a drive, remove a teach pendant, restore a backup) inside a maintenance mode or a sister cell first, never the production cell directly. Capture the firmware revision, the safety-PLC permissions, the connected-pendant list, the cell operator roster, and the relevant fieldbus log snapshot to your notes before the destructive step. Decision point: if the cell is under an OEM service contract, the cheapest correct path is almost always to open the OEM hotline in parallel with the rollback - the OEM service engineer can confirm whether an OEM-side firmware push is responsible while you are still staging the change, which avoids a needless parameter edit if the fix is in the next firmware revision.

When the PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026 controller returns intermittent alarms, cycle delays, or "something went wrong" under normal load, suspect the OEM firmware or a wiring intermittent before blaming the cell. Subscribe to the PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026 OEM service bulletin RSS or hotline notification so an open bulletin lights up your inbox or Teams automatically. Cross-check the OEM Trust Center or maintenance portal for any planned firmware push covering your machine series. Listen to the OEM controls-community forum and r/pcb - many regressions land there 15 to 30 minutes before the formal bulletin update. Decision point: if no bulletin is open but multiple teammates in the same plant are seeing the same alarm, fail over to a sister cell (if a sister machine exists) or to a backup parameter set (if the saved archive is current) and file an OEM service ticket with the alarm history dump, the controller serial number, and the timestamp window; major OEMs all accept the controller serial number as the primary trace key. Photograph the faulting cell with the HMI and the firmware version visible before the failover - that photo is what the OEM field service engineer asks for first on any alarm or cycle-time complaint.

Automate this fix so you do not do it twice

Automate PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026 parameter + I/O mapping snapshots via OEM utility or API

On the PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026, regular parameter and I/O snapshots catch silent parameter drift, recipe edits, and stale safety-PLC permissions well before the cell starts faulting in prod. Pair OEM health checks (the OEM diagnostic SDK, the controller users API, the fieldbus device listing) with a license-validity check so both OEM-side and cell-side issues land in one folder. Run the scheduled task on a control-plane logger PC (a hardened IPC at the cell, a GitHub Actions runner against the cell-controller VPN, a small Linux box at the line) under a tightly scoped service account that mirrors the maintenance role.

# List cell operator roster + safety-PLC roles
curl -H "Authorization: Bearer $CONTROLLER_TOKEN" \ https://controller.plant.local/api/v1/operators \ > pcb-operators.json
# List active fieldbus drops + their last-link-up timestamp
curl -H "Authorization: Bearer $CONTROLLER_TOKEN" \ https://controller.plant.local/api/v1/fieldbus_drops \ > pcb-fieldbus.json
# Validate the maintenance license token itself
curl -H "Authorization: Bearer $CONTROLLER_TOKEN" \ https://controller.plant.local/api/v1/me \ > pcb-me.json

Fleet maintenance-license + OEM token rotation via OEM admin

Rotating a maintenance access token on one PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026 controller by hand is fine; rotating across a fleet of cells is how you end up with twelve different tokens, four expired ones, and an unknown blast radius across the plant. Drive rotation through the PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026 OEM admin SDK or REST under a service account with the rotation scope only, store the new token in a plant-wide password manager (1Password, Bitwarden, OEM secrets manager) with versioning enabled, and roll the consumer scripts one cell at a time with a health check between each. Pin the API version explicitly during rotation so a coincident OEM firmware push does not look like a rotation failure.

# Rotate the controller maintenance token (regenerate via the OEM utility, capture in 1Password)
op item create --vault Plant --category "API Credential" \ --title "pcb controller token 2026-06-01" \ password="$NEW_CONTROLLER_TOKEN" notes="Rotated $(date -Iseconds)"
# Capture the old token as deprecated so cutover is reversible
op item create --vault Plant --category "API Credential" \ --title "pcb controller token OLD 2026-06-01" \ password="$OLD_CONTROLLER_TOKEN" notes="Old token marked deprecated"

Codify the firmware revision pin and rollback as a single notes entry

Once a stable firmware revision is identified for the PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026, write the revision string, the build hash, and the parameter set state to a fault-history notebook entry with the date in the title. Reproducible rollback is then a single OEM utility load plus a parameter restore. Pin the parameter set state explicitly so an OEM-side default change does not silently shift behavior under you. Stage the notebook entry next to a checklist that lists the failing photo, the PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026 alarm history dump (if any), and the OEM case number; the second time the cell faults at 9 a.m. you do not want to be rediscovering which firmware revision was actually green.

# Fault-history notebook template (pcb)
Date: 2026-06-01
Controller: pcb
Working firmware: 30iB-Plus 02.20 (Build hash: a1b2c3d)
Cell: Line 4 Cell B
Machine serial: SN-pcb-12345
Failing photo: ~/notes/pcb-2026-06-01.jpg
OEM case: OEM-pcb-12345
Rollback path: load previous firmware from OEM utility, master OFF, restore parameter archive, power up

Common pitfalls and what to watch for

The deepest trap with PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026 cells is treating a recurring class of alarm as a one-off incident. A drive overheat or a vision-trigger miss burst gets papered over with a power-cycle or a parameter reset, the cell runs for two weeks, and the exact same signature returns because the root cause was never identified. Codify every case in a fault-history notebook per machine, save the working firmware revision (the About panel) in the same note, and write the exact parameter set, I/O mapping, and fieldbus drop list into a checklist. After any major firmware update on PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026 review the parameter set and the I/O mapping explicitly, since OEMs silently change defaults or add new safety interlocks between major releases.

The second half of this pitfall is confirming the fix on a single cell when the cell is part of a fleet. If you and three teammates run the same PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026 controller on the same production line, an OEM-side firmware push tends to bite a whole batch within the same shift. Verify on every cell that runs the failing recipe, log the result and the firmware revision per attempt, and only then declare the class closed.

Verify the fix worked

• Reproduce the original faulting cycle against PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026 on the same cell AND a sister cell with the same recipe. If the alarm or fault code still surfaces on any cell, you have not fixed it.
• Watch for 24 to 48 hours via the PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026 controller alarm history + the fieldbus log + your fault-history notebook. Cached fault states and stale fieldbus link state mask slow-burn drift and intermittent fieldbus issues.
• Smoke-test under realistic load: replay the cycle against a test workpiece for at least 30 minutes at your normal production feedrate, log success / alarm and the timestamp per attempt to a notes file.
• Capture the new state in a fault-history notebook entry so the next time this happens you do not rediscover it. Note firmware revision + parameter set + I/O mapping + failing photo + verbatim alarm string + fix applied. Push to a plant-wide maintenance wiki if your plant uses one.
• If the fix involved a maintenance-token rotation or a parameter set change, commit the new token to your password manager and photograph the parameter dump for archival.

Safety, rollback, blast radius

• Test in a PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026 maintenance mode or on a sister cell first before any change that touches the production cell. Snapshot the firmware revision, the parameter set, the I/O mapping, and the safety-PLC permissions before changing anything.
• Apply the principle of least surprise when granting teach-pendant access or safety-PLC permissions. Review the operator roster against the people who actually need access - extra teach pendants are extra blast radius.
• Use idempotent cycles where the PCB Design and EDA Error Codes, KiCad DRC, Altium, Eagle, OrCAD, Mentor PADS, 2026 controller supports it (the OEM cycle-id de-dupe, external id keys on MES records) so a re-run cycle does not double-count parts or duplicate scrap records.
• Know your rollback path. Firmware rollback is a one-line OEM utility load; a maintenance-token rotation is reversible if you kept the old token in the password manager during cutover; a parameter set change is reversible only if you saved the previous archive.
• For cell-wide or plant-wide changes, line up a maintenance window with production scheduling before pushing through the OEM utility.

FAQ

Related fixes

Related guides worth a look while you sort this one out:

• how to fix Altium Designer Clearance Constraint violation between pad and polygon
• how to debug Altium Designer Hole Size Constraint violation for via-in-pad design
• how to clear OrCAD PCB Editor DRC Spacing Violation between SMD and BGA
• how to fix KiCad DRC clearance violation between via and copper pour on inner layer
• how to debug OrCAD Allegro shape void priority error on split power plane
• how to fix Altium Designer Un-Routed Net error after re-importing schematic changes