Close
0%
0%

Scottina

A pocket-sized front panel for the diagnostic tools you already use

Similar projects worth following
A pocket-sized touchscreen front panel for the bench diagnostic tools you already use — a Pi 5 + 3.5" screen that boots straight to a tap-driven tile grid, strips each tool down to the two controls and two numbers you actually watch, and skips the other 90%. Diagnostics only — not a Flipper, not a Marauder, not a wardriving toy.

The gap I'm closing

Bench diagnostics live at two extremes. Either you're squinting at a terminal over SSH on a headless box, or you're hauling a laptop to the bench to open a full-size GUI. Headless is too little. The full interface is far too much.

Here's what I kept noticing: for any single diagnostic question, I'm pressing about two buttons of that tool and watching about two numbers come back. The other 90% of the interface is just in the way. I don't need the ribbon menus, the config panels, the twelve tabs. I need to plug a thing in, glance at a 3.5" screen, and get my answer.

Scottina is that middle ground. It doesn't invent new tools — it gives the ones you already trust a front panel sized to the one question you're asking.

Read more »

  • 1 × Raspberry Pi 5 Runs Kali. The whole panel is a Python app rendering to the framebuffer — the Pi 5's headroom is what makes SDR decode and live CAN counters feel instant instead of laggy.
  • 1 × 3.5" ILI9486 SPI touchscreen, 480×320, ADS7846 resistive touch The panel Scottina is built around. Driven by the piscreen DRM overlay, rendered straight to /dev/fb0, touch read from evdev. No X server anywhere in the stack.
  • 1 × Cheapo Pi Case off Amazon This one comes with a screen already: https://amzn.to/3R4uJzr
  • 1 × microSD card, 32GB+ Kali install. A10/U3-class or better — the panel is I/O-sensitive at boot.
  • 1 × USB-C power supply, 27W PD Pi 5 wants the official 5V/5A brick. Underpowering a Pi 5 with dongles attached produces the worst class of bug: intermittent and blamed on your code.

View all 9 components

  • Who said I need all these buttons in my face?

    Scottsky3 hours ago 0 comments

    Starting the logs where the project started: with the thing that annoyed me enough to build hardware.

    The problem, stated plainly

    Every diagnostic session I run lands in one of two bad places.

    Place one: SSH into a headless box and squint at a terminal. Fine if you already know the exact command and the exact flag. Miserable when you're standing at a bench with one hand on a probe.

    Place two: carry a laptop to the bench, open the full GUI, and navigate a tool built for someone doing everything, when you are doing one thing.

    The observation that turned into a project: for any single diagnostic question, I use roughly two controls and watch roughly two numbers. Consistently. Across CAN, I2C, serial, Wi-Fi, SDR. The tools aren't wrong — they're general-purpose, and general-purpose means the 90% you're not using is between you and the 10% you are.

    Read more »

View project log

  • 1
    Step 1 — Gather the hardware

    Full list with notes is in the Components section. The minimum to get a working panel: Pi 5, the 3.5" ILI9486 screen, a 27W USB-C supply, an active cooler, and a decent microSD. The ALFA, CAN dongle, and SDR are all optional — their tiles simply don't appear until they're plugged in.

    Do not skimp on the power supply. An underpowered Pi 5 with dongles attached produces intermittent faults you will spend a day blaming on software.

  • 2
    Step 2 — Flash Kali and get in over SSH

    Write the Kali Raspberry Pi image to the microSD, enable SSH, and boot the Pi with a network cable and no screen attached. Everything from here is done over SSH — the panel isn't alive yet.

    Update before you touch anything else:

    sudo apt update && sudo apt full-upgrade -y
  • 3
    Step 3 — Bring up the panel

    This is the step that eats afternoons, so it's deliberately minimal. Two lines in /boot/firmware/config.txt:

    dtparam=spi=on
    dtoverlay=piscreen,drm,rotate=90

    Reboot. That's the entire display configuration.

    rotate is the only display setting that requires a reboot — pick 90 or 270 depending on which way up your case holds the panel. Touch orientation is handled in software, so you never come back to this file to fix taps landing in the wrong place.

    Verify the framebuffer exists:

    ls -l /dev/fb0
    cat /sys/class/graphics/fb0/name

    You should see the ILI9486 DRM framebuffer. If /dev/fb0 is missing, stop here — nothing downstream will work.

View all 10 instructions

Enjoy this project?

Share

Discussions

Similar Projects

Does this project spark your interest?

Become a member to follow this project and never miss any updates