Interactive browser of every signal that crosses the 120-pin MCS DIM connector between a Motor Control DIM card (the MCU board) and a motor-control baseboard โ€” built for MPLAB Device Blocks developers wiring a Simulink model to a given DIM + baseboard.

Open the viewer

๐Ÿ–ฅ๏ธ Open in full window

How to read a pin card

Each of the 120 DIM pins is one card, grouped into colour-coded category sections (PWM, ANA, QEI, HAL, FLT, PFC, DBG, COM, LED, BTN, XPRO1, XPRO2, PWR, NC, โ€ฆ). The section header names and colours the category, so there is no separate on-page legend.

Card areaMeaning
LeftThe pin’s active function + bare port (e.g. PWM1H / RB14), with the remaining multiplexed functions in grey
Right (top)Baseboard signal on that DIM pin (e.g. M1_PWM_AH)
Right (mid)DIM:NNN โ€” the DIM edge-connector pin, and (for expansion pins) XPRO1:7 the Xplained-Pro connector pin
Right (bottom)MCU:N โ€” the MCU package pin behind it

A first “DIM” section summarises the board itself, not connector pins: the MCU identity (part, order code, package, Flash / RAM / speed / VDD), the on-DIM 8 MHz clock (an active oscillator on OSCI/CLKI โ€” External Clock mode, not a 2-pin crystal), the general-purpose LED LD2, and the ICSP/J2 programming pins (MCLR / PGD / PGC).

Useful interactions

  • Search box (top sub-bar) โ€” filter cards by signal, pin, function or port. Supports wildcards: * = any text, ? = any single character (e.g. PWM*H, M1_I?). Next to it the chip characteristics (Flash / RAM / speed / VDD) and the pin-count stats.
  • Hover any pin card to see the full pin signature (all PPS / AD / CVD / CMP tags) plus its alternate routings and any DNP-rework note.
  • Sort within category โ€” by Function, DIM pin, MCU pin, or Connector pin (XPRO1 then XPRO2).
  • Show alternate (0 ฮฉ) routings โ€” reveals secondary routes; an alternate flagged rework is DNP and needs a board modification (move/add 0 ฮฉ resistors, often to switch to an external op-amp) before it can be used.
  • Highlight motor-control-essential โ€” frames the PWM / current / voltage / Hall / QEI / fault (plus LED & button) signals and dims the rest, for sanity-checking a control-loop wiring.
  • The DIM and Baseboard dropdowns each carry a โ†— link to the Microchip product page; the selected view is encoded in the URL (the address-bar link is shareable).
  • mchp-board-dim-mapping skill โ€” full methodology for maintaining the spreadsheet and adding new DIMs. (In-repo at .pi/skills/mchp-board-dim-mapping/SKILL.md; not served by Hugo.)
  • Motor Control Guide โ€” high-level overview of the MCHP motor-control ecosystem.
  • Block Reference โ†’ PWM HS FEP โ€” the PWM block that drives the inverter pins visible in this viewer.
  • Microchip Motor Control landing page โ€” product-level information and development kits.

Data-source details

The embedded data is assembled from four authoritative inputs:

  1. Motor Control DIM-Pin Mapping.xlsx โ€” the Pin-DIM, DIM-Pin, and Alternates tabs
  2. MCS DIM Info Sheets on Confluence (space MCU16APP) โ€” for DNP / alternate-path remarks
  3. Per-chip datasheets โ€” for the pin-name signatures shown on hover
  4. MCHP_ChipDef.mat โ€” for cross-checking that every MCU pin mentioned actually exists on the target silicon

The extraction pipeline lives at Claude_Sandbox/boards/ in the repository; regeneration is a manual step (not part of build.sh) because it reads Confluence directly.

Known limitations

  • Date-stamped snapshot. A commit to the spreadsheet or the Confluence sheets after 2026-06-16 will not automatically propagate here; the tool must be regenerated.
  • Single baseboard pair only. Only MCLV-48V-300W and MCHV-230VAC-1.5kW are bundled today. Adding a new baseboard means extending the generator, not just dropping a new JSON.
  • Read-only. There is no “export schematic” button โ€” this is a lookup tool, not a CAD integration.
  • Browser-only. Works in any modern desktop browser (Chrome, Edge, Firefox, Safari). Not tested on mobile; the 120-row grid is hard to read on a narrow screen.

Feedback

Found a discrepancy with the spreadsheet or with silicon? Either:

  • File a Jira ticket on the internal MCU16APP project, or
  • Edit the spreadsheet first, then regenerate the viewer via Claude_Sandbox/boards/build_viewer.py.

Do not edit the embedded data directly in index.html โ€” the fix will be lost on next regenerate.