Data pull

Get your data off the board over the USB cable: the SD card, the alert log in the board's own flash, and captures as .pcap for Wireshark. The card never leaves the case.

What am I looking at?

What's on the board

Alert log, in the board's own memory

One line for every alert the board beeped for: when, what kind (camera, drone, tracker…), which rule matched, signal strength and the device's radio address. Every board has it, card or not. It keeps the last 100,000 alerts; after that each new one overwrites the oldest. It only records while Log alerts on the board is on (app: Settings → Recording, or Record on the Sweep screen). It never records a location.

On the SD card, if one is fitted

  • Session logs (LOG00107.CSV): a copy of the alert log, one file per power-on, named by its power-on number. It adds the device name, Wi-Fi network, channel and maker, which the board's memory has no room for.
  • Captures (CAP00003.SSC): every Wi-Fi frame and Bluetooth advert heard during a Site Survey capture. Saved here as a .pcap for Wireshark (Wi-Fi only; the Bluetooth part stays in the original).

The board never deletes anything from the card, so files pile up. It only lists its newest 64 session logs and 64 captures; older ones are still on the card but don't show here. python pull.py --wipe clears the card after copying everything off.

What you get

  • alerts.txt: the alert log, readable. Counts per kind at the top, then every alert, oldest first, in your local time.
  • report.html: the same alerts as a page you can sort and filter. Opens in any browser, offline.
  • CAP*.pcap: a capture, ready for Wireshark.
  • raw/ (in Downloads: names with -raw-): the originals, untouched: the alert log as a spreadsheet (alert-log.csv), the session logs and the capture files. Keep them if you want everything.

Words you'll see

  • Power-on / boot: the board counts every time it gets power. Session logs and the boot column use that number.
  • boot 83 +1:15:14: the board didn't know the date that power-on (no phone connected, no clock fitted), so the time is given as 1 h 15 min 14 s after power-on 83.
  • dBm: signal strength. Around −30 is right beside you; −90 is far off or faint.
  • MAC: a device's radio address. Phones and trackers often change theirs every few minutes, so one device can show up as several.

Nothing on this page leaves your computer.

Nothing leaves this machine

This page is one file with no libraries, no analytics and no CDN. Its security policy (connect-src 'none') has the browser block any network request it tries, so it can only talk to the cable. Files are written only where you choose to save them.

Don't want to trust a hosted page at all? Save this page (Ctrl+S) and open your copy offline, or skip the browser and use pull.py: one readable Python file, needs only pyserial. python pull.py --wipe also clears the card once every file has copied intact.

1 · Plug in the board

Desktop Chrome, Edge or Opera. Close the SignalSweep app first: only one program can hold the port.

2 · Pick and save

Not connected.

A folder keeps it tidy: pick one (Documents is fine) and a new SignalSweep-<date> folder lands inside it. What you get:

Already have a capture?

Turn a .sscap from the phone, or a .SSC from the card, into a .pcap. No board needed.

Data on the phone

The app saves captures and session logs to the phone's Documents folder as signalsweep-*. Plug the phone into the PC, pick File transfer, and copy them. Or run python pull.py --phone --no-board with adb.

Saved pins and photo finds are encrypted in the app and stay that way. Export them from the app with your PIN (Survey → export).