Help

Troubleshooting

Use this page when something blocks setup or a debug session. If a check below doesn’t unblock you, include the project type, operating system, Symbiote version (if relevant), and the visible error message when you contact support.

Scope not detected

Work through these in order:

  • Confirm Symbiote is installed and paired with the web app.
  • Confirm the device is a PicoScope 2204A. Manual measurement entry still works without supported hardware.
  • Install PicoScope 7 or the required PicoSDK components for your OS.
  • Connect the scope directly over USB. Skip hubs while you’re chasing detection issues.
  • Open PicoScope 7 once and confirm it sees the device, then quit it so it releases the device before Symbiote tries to connect.
  • On Apple Silicon Macs, if your scope driver needs Rosetta, install it with softwareupdate --install-rosetta and restart Symbiote.

KiCad import fails or the schematic doesn’t render

Most KiCad import problems are project-folder structure issues.

  • From New Project → Import Project, select the folder containing the .kicad_pro and related .kicad_sch files.
  • If the selected folder contains several nested .kicad_pro roots, select the narrower project folder unless you want several boards.
  • Keep sibling sheets, libraries, library tables, and project settings inside the selected folder.

If the import succeeds but the schematic looks incomplete, save the project with a supported KiCad version and import the complete folder again.

Altium import fails

Second Silicon expects an Altium project folder, not a standalone file or ZIP archive.

  • Include the .PrjPcb project file.
  • Include the related .SchDoc files and any project-side library references.
  • Don’t upload a single .SchDoc or .PcbDoc — single-file Altium imports aren’t supported.
  • Select the folder that contains one project root. Folders with zero or several .PrjPcb roots are rejected.

Agent responses are slow or time out

Slow responses usually come from a large context, provider latency, or a network issue.

  • Start a new thread if the current one has a long history or many attached files.
  • Remove irrelevant firmware attachments or schematic selections before asking a new question.
  • Pin a faster model from the composer.
  • Check corporate proxy, VPN, or firewall rules if requests fail consistently.

BYOK key rejected

When a provider key doesn’t work:

  • Confirm the key belongs to the provider field where you pasted it.
  • Confirm your provider account has access to the model you selected.
  • Check account balance, billing status, and usage limits with the provider.
  • Rotate the key in the provider console and paste the new one under Settings → API Keys.
  • Enable at least one model from that provider under Settings → Models.