---
title: Troubleshooting
description: Fix common setup, calibration, and tracking problems.
---

Most detection problems come back to the physical setup. Check these in order.

## Nothing is being detected

- **Look at each camera feed.** The whole board must be visible.
- **Check the lighting.** Heavy shadows or glare hide darts.
- **Re-run calibration.** Any movement of the board or a camera invalidates it.
- **Make sure the board itself is secure.** A board that wobbles will miss throws.

## Wrong segment being scored

- Usually calibration. Re-run it and test with a few throws.
- If only clustered darts are wrong, the cameras need better angles, or another camera.

## Cameras not showing up

- Check the operating system can see the camera.
- Try another USB port, ideally on a different controller.
- Several cameras on one USB bus can run out of bandwidth, so spread them across ports.

## The camera says it is in use

Only one program can usually read a camera at a time. If another app — or a service that
starts at boot — is holding the camera, dartpilot cannot open it. The camera tile names the
program when the operating system reports it.

- **Close other camera apps.** Quit anything that might use a camera, including video
  call and streaming tools.
- **Check startup services.** On a Raspberry Pi or Linux board, a camera service may still
  be running after you close its window:

  ```bash
  fuser -v /dev/video*
  ```

  Stop the program it names, and disable it if it starts automatically.
- **Check permissions.** On macOS and Windows, allow camera access for dartpilot in system
  settings if access was denied.
- **Retry.** dartpilot keeps trying in the background, and the board shows a **Retry
  cameras** button. When the other program releases the camera, the feed comes back
  without a restart.

## The board shows as offline

- Check the board is really running: the desktop app is open, or the headless
  service is up.
- Open **Boards** in the web app to see which of your boards are online.
- Give it a moment. A board that has just started takes a little while to appear.
- Still offline? Restart the board and read its logs: the journal on Linux
  (`journalctl --user -u dartpilot`), or
  `~/Library/Logs/dartpilot/dartpilot.out.log` on macOS.

## Still not working?

Check the [FAQ](/faq) or [contact us](/legal/contact).