Public · Vehicle telemetry
Signal Broker
A vehicle-network development stack that gives CAN, LIN and related buses an explicit service boundary and makes live traffic available for interactive study in the browser.
- Niche
- Vehicle-network development and telemetry
- Core stack
- Elixir · gRPC · gRPC-Web · Vue
- Interfaces
- CAN/LIN · WebSocket · browser charts
- Role
- Open-source extension and interface design
The study
Vehicle buses contain rich technical information, while their native interfaces are optimized for low-level communication.
Signal Broker presents bus access through gRPC so application tools can work with a stable service boundary. The browser client brings the same traffic into an inspection surface built around selection, comparison and change over time.
System structure
The project treats vehicle signals as shared technical data that can support several forms of analysis.
gRPC gives applications in different languages a common contract for bus access and decoded signals.
The bus-facing server and presentation tools evolve as separate layers connected by explicit interfaces.
Live frames and signals can be selected, inspected and charted through an ordinary web client.
SocketCAN and virtual CAN give hardware-connected work and repeatable offline study the same conceptual model.
Product and interaction design
The browser interface is designed as an engineering instrument for observing relationships in live traffic.
A session begins by connecting to the broker, choosing frames or decoded signals and watching their behavior over time. The interface keeps the underlying data visible while adding enough structure for comparison and interpretation.
The service boundary also supports focused clients. WebSocket access suits lightweight JavaScript integrations, while gRPC provides the richer typed API for engineering tools.
Development approach
The design work centers on making machine behavior visible enough to form better questions about it.
Experiments begin with virtual CAN or recorded traffic, where filters, charts and interaction ideas can be compared quickly. Useful abstractions then become part of the typed gRPC boundary, giving exploratory work a clear path into the shared system model.
The working cycle is observe → isolate a signal → prototype an explanation → verify against representative traffic. Simulated buses, explicit transport contracts and visual inspection provide complementary forms of evidence.