ARBoard
IT EN
Book a demo (opens in a new tab)
Book a demo (opens in a new tab)
IT EN

Software for PCB diagnosis, repair and rework. Repair faster.
Make fewer mistakes.

ARBoard is the software that puts everything a repair technician needs to work on a circuit board on their PC:

  • 2D and 3D board layout
  • Schematics and design data
  • Test reports
  • Component datasheets
  • Failure history
  • Repair procedures

And there’s ARBerto, the local AI assistant: it answers questions, searches past repairs and points to where to intervene on the board.

Book a demo (opens in a new tab) How it works
Interactive 3D presentation

Lot L2639 · Ethernet functional test

3 of 24 boards failed

Follow the full case
  • 100% on-premise
  • AI included
  • No telemetry
ARBoard at work

A board fails its test: here’s what the technician sees.

  1. Import the test report

    AI reads PDFs, Excel files and AOI, ICT and flying probe exports, linking each fault to its component.

  2. Find the suspect components

    The fault map colors them on the board in 2D and 3D, so the technician can see where to start.

  3. Ask ARBerto

    “How did we fix this before?” The assistant searches past repairs and documents, answers and points to the spot on the board.

  4. Record the repair

    One click opens a Work Order: every action has an author and timestamp. At closing, the report is ready and the case stays in the history.

ARBoard screenshot: the Y1 crystal and its nets highlighted on the layout, with ARBerto on the right answering from the repair history.
ARBerto searches past repairs and highlights Y1 on the board. Actual screenshot, demonstration scenario for lot L2639.
Follow the full case, step by step What you need to get started
The value

What changes for the team.

  • Less time searching

    Board, documents and history in one place. The AI finds the answer and shows it on the board.

    In the case: steps 1–4

  • Collaboration in context

    The expert joins the session, sees the same board and points to the spot, even from another department.

    In the case: step 5

  • Experience that stays

    Every repair feeds the history, for the next shift and for whoever joins the company tomorrow.

    In the case: step 7

Every repair leaves experience. And the knowledge stays yours: ARBoard and its AI colleague run 100% locally, inside the company.

AI-assisted PCB repair and rework

Installation and security

You start from a single file.
And everything stays in-house.

To get started

  • Board data a single ODB++, IPC-2581 or Gerber file

  • Workstations standard PCs on the company network

Optional, if available

  • 3D model STEP file

  • Bill of materials Excel or CSV

  • Documentation manuals, schematics and datasheets in PDF

  • History the reports you already have, imported with AI

100% on-premise, AI included

ARBoard runs entirely on your servers: application, database and AI models. No data leaves the company network.

  • Air-gap ready
  • Zero data egress
  • No telemetry
  • Self-hosted
Explore ARBoard on-premise Interactive presentation
Why ARBoard exists

Board production is automated.
Repair still isn’t.

Production

Automated

failed
test

Repair

Manual

  • On the line

    Thousands of coordinated operations, repeated precisely by machines.

  • At the bench

    If a board fails the test, it goes back to the bench: measurements, tools, hands and decisions.

  • The challenge

    Understanding that fault, on that board. It takes information and experience, right away.

The problem

The information needed for repair exists.
But it is scattered.

  • Test reports

    One format for each test station, to be linked back by hand to components and positions.

    Where they live: On the test station

  • Design data

    Layouts, schematics, BOMs and datasheets in different tools, designed for the people who design.

    Where they live: In CAD tools

  • Procedures

    Instructions in scattered documents, or only in someone’s head.

    Where they live: In folders and documents

  • Previous cases

    The same fault has already been solved. But by whom, and how?

    Where they live: In colleagues’ memories

The result: time spent searching instead of repairing, avoidable errors, and experience that is lost at every shift change or when someone leaves the company.

The answer

ARBoard brings the work together around the board.

PCB diagnosis, repair and rework in a single workspace: the board, the information, the people and the experience.

  • The board

    Components, nets and layout from an ODB++, IPC-2581 or Gerber file. A 3D model from STEP and an exploded layer view.

  • The information

    Schematics, manuals, datasheets and test reports, linked to the components they refer to.

  • The people

    Technicians and experts in the same session, on the same board, with chat and assistance requests.

  • Experience

    Failure history, procedures and recorded repairs, available to whoever comes next.

And an AI colleague, ARBerto, working on all of this. 100% local.

Explore the ARBoard platform for PCB repair

The narrated presentation

Watch ARBoard in action.

From circuit board to resolved fault: a demonstration case shows how data, people and an AI colleague work together. Everything stays on-premise, AI included.

English narration11 minutes

Explore the interactive presentation
Watch on YouTube (opens in a new tab)

A concrete case

Lot L2639: three boards fail the Ethernet test.

September 29. End-of-line testing of the CX-200 control unit reports 3 boards out of 24 that fail the Ethernet functional test. We need to find out why, repair them and get them back on the line.

The cast

  • LucaRepair technician, at the bench
  • GiuliaExpert, in another department
  • ARBertoARBoard’s AI colleague

The seven steps

  1. The report enters ARBoard the AI reads it and updates the history
  2. Where to look the fault map points to the suspects
  3. Asking the AI colleague “how did we solve this the other times?”
  4. Exploring the board connections, 3D and inner layers
  5. A second opinion the expert joins the session
  6. Recording the repair every action, with author and time
  7. Report and memory the case becomes experience for everyone

Demonstration scenario. All screens are captured from the ARBoard software.

Skip the story

Step 1 · The test report

The report enters ARBoard, and the AI turns it into data.

ARBoard screen: the file Collaudo_FT02_Lotto_L2639.txt dropped into the ARBerto assistant, the Ethernet 10/100 functional test failures assigned to Y1, U2 and J3, and the fault map on the board. Open the full-resolution image
  1. Zoom into detail 1 of step 1

    1. Luca drags the test station report into the assistant: ARBerto recognizes the test and assigns each failure to the right component (Y1, U2, J3).

  2. Zoom into detail 2 of step 1 (1 of 2) Zoom into detail 2 of step 1 (2 of 2)

    2. The history and the fault map on the board update themselves: no copy and paste, and every import can be undone.

Step 2 · Where to look

The fault map shows where to start.

Fault map on the board: U2, Y1 and J3 colored orange; on the right, the Y1 test log with the September 29, 2026 failure and the repair procedure recorded on July 30, 2026. Open the full-resolution image
  1. Zoom into detail 1 of step 2

    1. ARBoard counts how many times each component has made the Ethernet test fail.

  2. Zoom into detail 2 of step 2

    2. On the board, the components are colored accordingly: the PHY U2, the crystal Y1 and the connector J3 stand out.

  3. Zoom into detail 3 of step 2

    3. On Y1, next to the failure just imported, is the procedure used last time: five steps, down to the load capacitors.

Step 3 · The AI colleague

ARBerto answers from the history, and shows the answer on the board.

ARBerto answers Luca’s question with the procedure already used and highlights the crystal Y1 and its nets on the board. Open the full-resolution image
  1. Zoom into detail 1 of step 3

    1. Luca asks, by voice or in writing: “How did we solve this the other times?”

  2. Zoom into detail 2 of step 3

    2. ARBerto checks the history and brings back the procedure already used.

  3. Zoom into detail 3 of step 3

    3. Meanwhile it highlights Y1 and its nets on the board.

Step 4 · Exploring the board

Components and connections, without searching through documents.

U2, the Ethernet PHY, selected: its pins and connected nets highlighted, each in its own color; on the right, the component’s net list. Open the full-resolution image
  1. Zoom into detail 1 of step 4

    1. Luca selects U2, the Ethernet PHY: its pins and every connected net light up, each in its own color.

  2. Zoom into detail 2 of step 4

    2. On the right, the component’s nets: each one leads to the other connected components, so you can decide where to measure.

Step 5 · A second opinion

Need an expert opinion? The expert joins the session.

Luca’s assistance request, medium urgency: “Y1 not oscillating on two boards of lot L2639…”, with the “Prendi & Entra” (Claim & Join) button. Open the full-resolution image Built-in chat between Giulia and Luca over the shared board, with C21 selected by Giulia and highlighted. Open the full-resolution image

  1. 1. Luca asks for assistance, stating the urgency and the problem.

  2. 2. Giulia, in another department, receives the request: with “Claim & Join” she is in the same session, on the same board.

  3. Built-in chat between Giulia and Luca over the shared board, with C21 selected by Giulia and highlighted. Open the full-resolution image
    Zoom into detail 3 of step 5 (1 of 2) Zoom into detail 3 of step 5 (2 of 2)

    3. They talk in the built-in chat. When Giulia selects C21, it lights up on Luca’s screen too.

At the bench

Experience guides.
The technician verifies.

“Measure C21 before replacing Y1”

Giulia, expert

Then it’s back to hands and tools. Luca measures C21: on both boards, the value does not match the bill of materials. He replaces it, rechecks the 25 MHz clock and reruns the Ethernet test: passed. On the third board the problem is different: connector J3 has to be replaced.

Test result

Ethernet functional test

Passed

C21 replaced, clock restored

  • SN 007 passed
  • SN 013 passed
  • SN 021 waiting for connector J3

Step 6 · Recording the repair

The repair is recorded while the work happens.

Repair session (Work Order) “Lotto L2639 - Ethernet” open: C21 added to the Ethernet test failures, with the problem description and three repair instructions. Open the full-resolution image
  1. Zoom into detail 1 of step 6

    1. Luca opens a repair session (Work Order): from here every action is recorded, with author and time.

  2. Zoom into detail 2 of step 6

    2. He adds C21 to the Ethernet test failures…

  3. Zoom into detail 3 of step 6

    3. …with a description of the problem and the repair instructions, step by step.

Step 7 · The report

When the case closes, the report is already written.

Work Order confirmation: “Also worked on this: Giulia”, final notes “SN 007 and 013: C21 replaced, clock restored, Ethernet test OK. SN 021: J3 to be replaced.” and the option to save the session as a repair example (a “capsule” in the app). Open the full-resolution image AI summary of the confirmed Work Order, with the final notes and the action log of September 29, 2026. Open the full-resolution image Exported Work Order report: “Lotto L2639 - Ethernet KO (SN 007, 013, 021)”, operator Luca, participants Luca and Giulia. Open the full-resolution image

  1. 1. On confirmation, ARBoard records who worked on the case, Giulia included, and saves the session as a repair example.

  2. AI summary of the confirmed Work Order, with the final notes and the action log of September 29, 2026. Open the full-resolution image

    2. The AI summary writes itself, next to the notes and the action log.

  3. Exported Work Order report: “Lotto L2639 - Ethernet KO (SN 007, 013, 021)”, operator Luca, participants Luca and Giulia. Open the full-resolution image

    3. One-click export to Word, Excel or CSV: the document for quality or for the customer is ready.

The next crystal that fails to oscillate will start from here, and ARBerto will know.

The outcome

The board runs again.
The experience stays.

Two boards from lot L2639 go back on the line; the third waits for its connector. The work stays: in the session, in the report and in the component catalog. Anyone who runs into a crystal that won’t oscillate will find the same path and can weigh it against their own board.

Book a demo (opens in a new tab) The full repair workflow

Who supports ARBoard

Supported by

  • Politecnico di Torino
  • Fondazione Compagnia di San Paolo
  • ConceptionX

Assisted by

  • I3P, Politecnico di Torino incubator

The next story could be yours.

Let’s organize a demo: we’ll show you every feature, answer your questions and think together about how ARBoard can fit into your company’s work.

Book a demo (opens in a new tab) Write to us

Giorgio Insinga — CEOgiorgio@arboard.eu