Page Comparison

...

Functional Block Diagram: 

Modules:

1. lights_can:
   1. It's Its main responsibility is to solely receive can messages and raise events. 
   2. Is the only module that knows about whether software is at the front board or the back board.
   3. The only occasion where it sends a can message is a sync signal to the other board.
2. main: This module only contains a main loop where it gets the raised events from lights_can and passes them to the next three modules: strobe, simple_peripherals, and signals_fsm. Every module checks if it owns the event that is passed to it and processes it. If the event is not related to the module, the module ignores it.
3. simple_peripherals: Used for all the peripherals which have a simple on, or off state. These peripherals are: horn, headlights, and brake lights.
4. strobe: Uses a blinker object to blink the strobe light.
5. signals_fsm: Contains the FSM of the signals. Every often calls send_sync from lights_can to sync the two boards. Uses blinker for blinking the signals. 
6. blinker: Basically handles all the overhead related to using soft timers.
7. lights_gpio: 
   1. Is the only module that knows about all the addresses.
   2. Can be thought of the only part where the boards actually take action?!
   3. strobe, signals_fsm, and simple_peripherals all call its lights_gpio_set() function to change the state of the lights.

...