Boardview Software: ZXW, WuXinJi, OpenBoardView & AI

A boardview file is a geometry-and-connectivity map of a printed circuit board. It records where every component and test pad sits in physical x-y coordinates, on which side of the board, and — critically — which pads belong to the same electrical net. When you load it in a viewer and click a component pin, the software instantly highlights every other pad on that net, including the ones hidden under shields or on the opposite side. That single feature is what makes a no-power or short-to-ground diagnosis tractable: you find a shorted rail, click it, and the viewer shows you every component sitting on that rail as a suspect list.

Boardview files come in many formats because they originated from different CAD and reverse-engineering toolchains. You will encounter extensions like .brd (the OpenBoardView family and its dialects), .fz, .bdv, .bv, .bvr, .cad, .cst, .f2b, .gr, .tvw and the modern KiCad .kicad_pcb. A boardview is not a schematic, though. It tells you what connects to what physically; it does not tell you that a given net is the PP1V8 rail feeding the PMIC, or that a particular IC is the Tristar or Tigris charging controller. For that electrical meaning you need the schematic — which is why serious technicians keep both open side by side.

ZXW, also sold as ZXW Tool or ZXWteam Dongle, is the tool most iPhone and Android board techs reach for first. Its strength is that it pairs a clean boardview with high-quality, hand-traced schematic diagrams for a huge library of Apple and Android boards. Click a component and ZXW jumps you straight to its location on the board and its place in the schematic, with voltage annotations on the rails. For tracing a backlight boost fault, a charging-IC issue, or a dead PMIC rail, that tight schematic-to-board linkage saves enormous time.

ZXW is a paid, subscription-style product tied to a hardware dongle or account licence. In the Indian market it typically lands in an approximate range of around 6,000 to 12,000 rupees per year (market-survey estimate, verify current pricing before purchase). It remains a viewer-and-reference tool: it shows you the board and the schematic beautifully, but the diagnosis — reading the symptom, forming a hypothesis, deciding what to probe — is all you.

WuXinJi, often written Wu Xin Ji and sold via the WuXinJi Dongle, is the other heavyweight schematic-and-boardview platform. Many technicians run both ZXW and WuXinJi because their board libraries and schematic coverage don't perfectly overlap — one will have a clean diagram for a board the other is missing. WuXinJi is particularly valued for the depth of its schematic collection across iPhone, iPad and a wide spread of Android boards.

Like ZXW it is a licensed, dongle-based product, with Indian market pricing in a roughly similar approximate band (around 6,000 to 13,000 rupees per year as a market-survey range; confirm before buying). And like ZXW, it is fundamentally a reference and navigation tool. It is superb at answering 'where is this and what is it connected to?' It does not answer 'given these symptoms, which part is most likely dead and what should I measure next?'

OpenBoardView is a free, open-source boardview viewer. It reads the common .brd and related formats and gives you the core capability — click a pad, see the net, flip the board, search by component reference. It carries no schematic library of its own and no diagnostic logic; it is a clean, fast, no-cost way to open a boardview file you already have. For a technician on a budget, or for quickly checking connectivity on a board you've reverse-engineered, it is genuinely useful and widely used.

FlexBV is a polished commercial boardview viewer that many professionals prefer for its speed, multi-format support and ability to overlay schematic images alongside the board. It is a paid licence, generally a one-time or per-version purchase rather than an annual subscription. Both OpenBoardView and FlexBV are, by design, viewers: they render the board and let you navigate it. The reasoning stays with the technician.

Every tool above is passive. ZXW, WuXinJi, OpenBoardView and FlexBV all show you the board and, in the case of the first two, the schematic. None of them reason. None of them know that the board in front of you boots a particular rail first, or that killing one specific IC would block the power-up at a specific phase, or that the three symptoms you just described point at one part rather than another. They are maps. You are still the navigator, the detective and the memory.

That gap is where a new, AI-native generation of tools is emerging. The idea is simple to state and hard to build: instead of a viewer you read, build a tool that ingests the same schematic and boardview files, constructs an electrical model of the board, and then reasons over that model with you — pointing at components on the board, simulating faults, and narrowing a symptom down to the next thing you should probe. The clearest public example of this approach is Wrench Board.

Wrench Board is a source-available diagnostic workbench for board-level repair, built by a working microsoldering technician under the Repair Valley name (the same workshop also goes by Repairmind). It is powered by Anthropic's Claude Opus 4.8 model. It placed 2nd in Anthropic's 'Build with Opus 4.7' hackathon, announced April 2026. It is source-available, not open source — an important distinction — and free for personal use and for independent repair professionals servicing their own clients.

A short, honest note before we go further, because this is an editorial piece: iTweak did not build Wrench Board, did not enter the hackathon, and is not affiliated with Anthropic or Repair Valley. We cover it because it represents where board-repair tooling is heading, and because we ourselves run AI-assisted diagnostics in our own workshop. We are describing a public tool, not selling it.

What makes Wrench Board different from a viewer is that it reads both the schematic PDF and the boardview file, builds a queryable electrical model of that exact board, and then runs a diagnostic agent that drives a 3D rendering of the board visually while you keep the iron in your hand. It is device-agnostic: feed it a schematic and a boardview and it works the same on an iPhone or MacBook logic board, an Android board, a console motherboard, a laptop or a single-board computer. Anything with a schematic and a boardview is fair game. It reads 16 boardview formats by extension, including the OpenBoardView .brd family and KiCad .kicad_pcb.

When you give Wrench Board a schematic PDF, it parses the schematic page by page using Opus 4.8 vision, extracting reference designators, component values, topology and typed edges (what powers what, what enables what, what decouples what). It then compiles that into an ElectricalGraph: it classifies nets into power rails versus logic versus connector, derives which components depend on which rails, and infers the boot sequence — the order the rails come up at power-on — by topological sort. This is what lets the tool say something like '+3V3 standby comes up first from U14, then the main rail, then the CPU module', and trace a dead board back along that chain, instead of guessing from generic knowledge.

Two deterministic engines sit on top of that model, and neither calls a language model at runtime — which is what makes their output auditable and repeatable. The forward simulator takes a fault you propose (a component plus a failure mode such as dead or shorted) and computes the consequences across the boot sequence: which rails sag, which parts degrade, and at which boot phase the board gets blocked. It is a behavioral simulator, not a SPICE analog model. The canonical example is 'kill U12, board blocks at Phase 2.' The reverse hypothesizer does the inverse: you give it a partial observation (the 3V3 rail is dead, U14 is alive, the CPU never wakes) and it enumerates the component faults that would explain it, scores them, and — when several suspects tie — tells you the single measurement that best splits them. In other words, it tells you exactly what to probe next to narrow it down fastest.

Because a microsoldering diagnosis lives or dies on what your probe is touching right now, Wrench Board can see the actual board on demand. You plug a USB microscope or webcam into the bench; when the agent needs a fresh visual on a suspect chip, it requests a still frame, which you have already framed and focused. To be precise about what this is: it is technician-initiated capture on your optics and your cue, not autonomous machine vision roaming the board on its own. Captures are saved under the repair so a whole session can be replayed later.

The flagship safety feature is a two-layer guarantee against invented part names. First, the lookup tools physically cannot fabricate — ask for an unknown component and the tool returns 'not found' with closest matches rather than making one up. Second, before any agent reply reaches your screen, a server-side sanitizer scans it for reference-designator-shaped tokens (like U7, C29, Q3100) and validates each against the actually-parsed board; anything it can't verify gets visibly flagged rather than slipping through as fact. The sanitizer is deliberately careful, so it doesn't false-flag bus or protocol names like USB3, DDR4 and PCIE4 or Apple model numbers like A2337. For a technician, that is the difference between a tool you can trust on a refdes and a chatbot that confidently invents one.

Wrench Board has a genuine layered memory, not just a chat history. When you confirm a root cause, the agent saves a durable field report for that device — the at-fault part, the reported symptom, the failure mechanism and your notes. The next diagnostic session on the same device can recall those reports, so the more real repairs a workshop does on a given board, the smarter the tool gets on that specific board. Again, to be precise: this is recall of confirmed field reports, plus a nightly tuning loop that adjusts the deterministic engine against a frozen, human-curated benchmark of real scenarios — keeping a change only if measured accuracy improves, and reverting it otherwise. It is not training or fine-tuning the underlying Claude model on customer data.

On timing, set expectations honestly. A focused knowledge pack for a device lands in roughly two minutes. A full pack that ingests a dense schematic — think a board-heavy Apple Mac schematic — can take 15 minutes or more, and you can close the page because it keeps building in the background. The live diagnostic agent is also tier-selectable: a deep tier on Opus 4.8 for hard causal chains, a balanced tier on Sonnet for routine work, and a fast tier on Haiku for quick lookups.

Here is how the established tools and the AI-native approach line up. INR figures are approximate market-survey ranges only — confirm current pricing with each vendor before you buy.

iTweak is an ISO 9001:2015 certified independent Apple and Android repair business based in Marathahalli, Bangalore, with branches in Mumbai and Chennai. We have been repairing since 2010 and doing board-level micro-soldering since 2012 — PMIC and charging-IC replacement, backlight boost repair, BGA reballing, NAND work, water-damage recovery with ultrasonic and IPA cleaning, and short-detection on dead boards. We pair that bench experience with AI-assisted diagnostics in our own workflow, alongside the established boardview and schematic tools every serious shop relies on.

Every repair runs through our 80-point diagnostic, comes with up to a one-year warranty, free pan-India insured pickup, a see-the-fault-before-you-pay policy, a digital invoice, and a money-back guarantee on misdiagnosis. If your phone or MacBook motherboard has a fault that needs component-level work, that combination of trained technicians, proper tooling and honest diagnostics is what gets it fixed rather than written off.

Quick answers to the questions technicians and customers ask most about boardview software and AI-assisted board repair.

• Is a boardview the same as a schematic? No. A boardview maps the physical board — pad locations and which pads share a net. A schematic explains what each net does electrically. ZXW and WuXinJi bundle both; OpenBoardView and FlexBV are boardview viewers only.
• Which is better, ZXW or WuXinJi? Most working technicians use both, because their board and schematic libraries don't fully overlap. If you can only pick one, choose the one with better coverage for the boards you repair most.
• Is OpenBoardView good enough on its own? For opening and navigating a .brd file you already have, yes — it is free and fast. But it has no schematic library and no diagnostic logic, so you still need a schematic source and your own expertise.
• Is Wrench Board open source? No. It is source-available, built by a working microsoldering technician under the Repair Valley name, and free for personal use and for independent repair pros servicing their own clients. It placed 2nd in Anthropic's 'Build with Opus 4.7' hackathon and is powered by Claude Opus 4.8. iTweak is not affiliated with it.
• Does Wrench Board replace the technician? No. It pilots the board visually, simulates faults and suggests the next probe point, but it captures images only when you frame and request them, and it is built so the human keeps the iron and makes the call.
• Can I get my motherboard repaired at iTweak even if it's a complex board fault? Yes. We do board-level micro-soldering on iPhone, Android and MacBook motherboards, backed by an 80-point diagnostic, up to a one-year warranty, and money-back on misdiagnosis.