As web developers, we rarely get to play with raw automotive hardware. But when I started messing around with my Tesla's CAN bus network to monitor FSD performance metrics, I realized the software ecosystem for tracking these hardware mods was non-existent. Most enthusiasts rely on static PDFs or outdated forum wikis.
To fix this, I built FSD CAN Mod Tracker (fsdcanmod.com). I wanted it to be incredibly lightweight, responsive on mobile (crucial when you're working inside a car), and highly structured.
The Tech Stack
I chose SvelteKit for the frontend because of its lightning-fast load times and reactivity. The app parses and displays complex telemetry mappings, configuration profiles, and hardware compatibility lists. Tailwind CSS handled the dashboard layouts, keeping the visual hierarchy clean and highly readable under direct sunlight (again, testing inside a vehicle makes you appreciate high-contrast UIs).
Architectural Challenges
The trickiest part was designing a flexible schema for tracking dynamic CAN signals across different Tesla hardware versions (Intel Atom vs. AMD Ryzen chipsets, HW3 vs. HW4). The dashboard must dynamically filter and map compatibility profiles without hitting heavy database bottlenecks. I implemented an optimized client-side filtering system that keeps interactions snappy even with hundreds of data points.
Check it out and let me know how I can improve the telemetry parsing pipeline!
