Why standalone: laptops in moving cars are a distraction and a projectile. The Openport's onboard logging turns the cable into a black-box recorder — plug it in, drive, review at your desk. It's also the way to catch the gremlin that only appears on Thursday mornings: leave it plugged in for a week.
Step 1 — Format a quality microSD card (modest capacity is fine; logs are small text files) and insert it into the Openport's card slot.
Step 2 — The cable reads its logging configuration from a file on the card (the Tactrix documentation covers the current filename and format). The config defines which parameters to sample — the community shares known-good standalone configs for common Subaru models, which is the sane starting point rather than writing one from scratch.
Step 3 — Start from a shared config for your generation and trim it to the same core health list you use in RomRaider Logger: RPM, load, boost, AF ratio, corrections, knock parameters, DAM, temps. Copy it to the card, safely eject.
Step 4 — Plug the Openport into the OBD port and start the car. The cable's LED behavior tells you it's logging (the documentation decodes the blink patterns). It logs every drive automatically from now on — no interaction needed.
Step 5 — For track use: tuck and secure the cable and any dongle clear of the driver's feet. Zip-tie discipline near pedals is a safety item, not tidiness.
Step 6 — After driving, pull the card and open the logs on your laptop. The files import into the same analysis flow as laptop logs — spreadsheets, or log-viewing tools the community favors, which graph knock events against RPM and load in a couple of clicks.
Step 7 — Card hygiene: archive log files off the card monthly into your Logs folder and clear it. A card that fills up silently stops recording — and it will choose the interesting day to do it.
Tuning changes engine behavior. Numbers here are typical, not guaranteed — your fuel, climate, and hardware matter, and a professional calibration for your specific car always beats a generic map.