Troubleshooting
Step-by-step fixes for specific issues you might encounter while using Protoboard.
Specific problems, specific fixes. Each scenario below describes what you're seeing, why it happens, and how to resolve it.
Validation shows no results
What you see: You open Board Review (shield icon) and run DRC, but the results panel is empty: no errors, no warnings, nothing.
Why it happens: DRC only validates harnesses, the connections between parts. If your board has parts but no harnesses, there's nothing for the DRC to check.
How to fix it:
Part not found in the library
What you see: You search the Parts Bin for a specific component and it doesn't appear in the results.
Why it happens: The parts library is growing but doesn't include every component yet. The search may also not match your exact query phrasing.
How to fix it:
The Parts Bin uses AI-powered semantic search. Try:
The manufacturer name plus part number (e.g., "Adafruit BME280")
A descriptive phrase (e.g., "I2C temperature humidity sensor")
A shorter version of the name (e.g., "BME280" instead of "Bosch BME280 Environmental Sensor")
A category search (e.g., "motor driver" or "boost regulator")
If the part genuinely isn't in the library, create a blank part and define its interfaces and resources manually. This lets you continue designing while the library catches up. See the Breadboard from Blank Parts tutorial for a walkthrough.
Open ProtoBot and ask: "Find me a 3.3V I2C accelerometer." ProtoBot can search the library using different strategies and may find parts that a simple text search missed.
ProtoBot not responding
What you see: You send a message to ProtoBot and nothing happens: no response, no loading indicator, or a generic error message.
Why it happens: Several possible causes: exhausted energy balance, model availability issues, or network connectivity problems.
How to fix it:
Harness shows red but parts seem compatible
What you see: You created a harness between two parts that should work together, but the DRC shows INCOMPATIBLE or NOT_CONFIGURED (red).
Why it happens: The harness exists, but the interface link inside it may be misconfigured: wrong interfaces paired, missing function links, or unallocated resources.
How to fix it:
Save failed
What you see: You get an error when trying to save your board, or changes don't seem to persist.
Why it happens: Usually a network issue. Protoboard syncs to the cloud, so saving requires a stable internet connection.
How to fix it:
Verify you have internet access. Try loading another website. If your connection is unstable, wait for it to stabilize and try saving again.
If the normal save keeps failing, try exporting your board as a local file (if available). This creates a backup you can re-import later.
Protoboard autosaves drafts periodically. If your session ended unexpectedly, check for autosaved drafts when you next open the board. Your most recent changes may already be preserved.
Canvas is blank after opening a board
What you see: You open a board that previously had parts, but the canvas is empty.
Why it happens: The board file may have failed to load properly, or there may be a sync issue between the local cache and the server.
How to fix it:
ProtoBot gives an irrelevant or wrong suggestion
What you see: ProtoBot suggests a fix or action that doesn't match what you're trying to do.
Why it happens: AI quality depends on the model you've selected and the context you've provided. Lighter models may misunderstand complex requests.
How to fix it:
Open the model selector in the ProtoBot panel and choose a heavier model. More capable models handle nuanced design questions better, though they consume more energy per interaction.
Be specific in your prompts. Instead of "fix my board," try:
"The I2C harness between the Arduino Uno and the BME280 shows PARTIALLY_CONFIGURED. I think it needs pin allocation. Can you assign A4 to SDA and A5 to SCL?"
The more context you give, the better ProtoBot can help.
Instead of asking ProtoBot to do everything at once, break complex tasks into individual steps:
"Place an Arduino Uno Rev3 on the canvas"
"Place a BME280 sensor next to it"
"Create an I2C harness between them"
"Allocate I2C pins on the Arduino"
This gives ProtoBot less room to misinterpret your intent.
BOM shows missing prices or supplier data
What you see: Some parts in the BOM panel have no pricing or supplier information.
Why it happens: Not all parts have supplier data linked yet, especially newer or less common components. Blank (custom) parts won't have supplier data unless you add it manually.
How to fix it:
I accidentally deleted a part or harness
What you see: A part or harness you needed is gone from the canvas.
Why it happens: Accidental deletion, usually via the Delete key or a context menu action.
How to fix it:
Undo: Press Ctrl+Z (or Cmd+Z on Mac) to undo the deletion. Protoboard supports multiple undo levels.
Autosave: If you've made many changes since the deletion, check whether an autosaved draft from before the deletion is available.
Re-add: If undo doesn't work, re-add the part from the Parts Bin and recreate the harness. Your other connections won't be affected.
Still stuck?
If none of these scenarios match your issue:
Check Known Limitations: the issue might be a known constraint
Ask ProtoBot: describe the problem in natural language and see if it can help
Use the feedback button: report the issue with screenshots and reproduction steps
Check the FAQ: your question may be answered there
Related pages
FAQ: General questions about Protoboard
Known Limitations: Current constraints and expected behavior
Common DRC Failures: Learn to diagnose DRC failures
Fixing Errors: Step-by-step error resolution workflow
Last updated