-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
No device found. The unit switches itself off after a few minutes idle; press its button or replug it. Check the cable is a data cable. On Linux make sure the udev rule is installed and the unit was replugged after installing it.
Linux: "access denied" or permission errors. The udev rule is not active for this plug‑in. Re‑run the two udevadm commands from Installation and replug the unit.
Android: no permission dialog / "permission denied". Unplug and replug the unit and accept the dialog. If the unit's screen never lights, the phone is not supplying enough power over OTG; keep the AAA battery in or use a powered OTG hub.
macOS: "cannot be opened because the developer cannot be verified". The build is not notarized. System Settings → Privacy & Security → Open Anyway (older macOS: right‑click → Open), once.
The app says the device is busy. Another program holds the unit: Peak's own app, or a browser tab running a WebUSB client. Close it.
A test times out. The unit does not talk over USB while it runs a test (about 3–4 s). The app waits up to 15 s; if it still times out, replug the unit.
A sweep produced a flat line. For a diode, check the anode/cathode selection matches the pinout on the Identify tab; a sweep run backwards traces a reverse‑bias line. For FET families, an out‑of‑range Vgs/Vds combination ends a trace early by design.
Something looks wrong with a reading. Open Log (terminal icon in the header) to see every USB exchange with timing and errors, and export it as a .dcalog capture to attach to a bug report.
Where is my data? See Data and backup.