Skip to content

Module Index

The CAN-Gateway firmware is easier to understand when you read it by responsibility instead of by file name. Each module page below explains one part of the board in plain language and links to the source files that matter.

NOTE

This tree is board-specific. It is meant to explain how the CAN-Gateway behaves at runtime, not to serve as a reusable driver reference for other projects.

Module groups

Communication

The communication layer turns board state into CAN traffic and turns selected incoming frames into commands. Start here if you want to understand what the board sends, what it accepts, and how the CAN driver is wired into the hardware.

Data processing

This is the sensor pipeline: raw ADC samples are gathered, filtered, scaled, and turned into usable values for the rest of the board.

Sensors I/O

The sensors layer binds each physical input to a driver object and handles the board-specific split between front and rear gateway behavior.

FSM and control flow

The state machine decides when the board is idle, processing, outputting data, entering bootloader, or staying in fault handling.

TIP

If you are looking for a specific path through the board, read the FSM page first and then jump into the owning module. That usually shows the runtime order faster than reading source files top to bottom.

Released under the MIT License.