How maddisagar/raw_can works
Project type and purpose
• This is a full-stack telemetry dashboard built with Next.js (React) that visualizes real-time CAN-bus data, decoded via an Arduino/JavaScript pipeline.
• The README confirms it's a Next.js application, bootstrapped with create-next-app, serving up a front-end on port 3000.
File structure
Top-level entries:
• components/ – dozens of React UI pieces (charts, gauges, status cards), plus CAN decoding scripts (canDecoder.js, dbc files, Arduino C++ code).
• src/app/ – the Next.js App Router directory (layout.tsx, page.tsx, CSS).
• Configuration files – next.config.mjs, tsconfig.json, jsconfig.json, postcss.config.mjs, eslint.config.mjs.
• package.json, package-lock.json – lists Next.js, React, WebSocket libraries, charting utilities.
Patterns & clues:
• components/data-context.js – React Context for passing live data.
• components/websocketurl.js – likely holds the URL for a live WebSocket server.
• Arduino code and DBC files indicate a hardware ingestion pipeline.
README for additional insights
• It's a Next.js front-end only. No backend code here, so the real-time data must come from an external service (e.g., a Node.js WebSocket server you deploy separately, or from the Arduino via serial-to-WebSocket bridge).
• Deployment target is Vercel, but the real-time pipeline is external.