Engine Control System
Objective:
Create two subsystems, where each subsystem executes on separate Micro Controller Units (MCU). One subsystem represents the Engine Management System (EMS) and the other the Engine Control Unit (ECU).The system is to emulate an Engine Control System
The EMS will send commands to the ECU, the ECU will acknowledge the command, the ECU reacts to the command, and the EMS will measure the reaction. This is a simple closed loop uncontrolled system, but it does help demonstrate a multi discipline system. The following figure lays out the basic flow of the system.
- To define CMD protocol, handshake and error messages.
- To define time domain interactions (when a command is received to when the actual freq. is changed)
- State machine to handle messages and errors, response synchronization
Behavior Requirements:
1. Inputs :
a. S1; start engine (default speed 10rpm) / stop Eng.
b. S2: each press increments speed by 10rpm (max 150 rpm)
c. S3: each press decrements speed by 10rpm (min 0 rpm)
d. Engine rpm input IC1(RD8)
e. Comm: your design
2. Outputs:
a. LED0 (D4) : engine state (stop=off, running=on)
b. LED1 (D5): error
c. LED3 (D6): blink per sec = error code (1/sec, 2/sec, 3/sec)
d. Engine rpm frequency output
e. Comm: your design
3. Errors
a. Limit breach: speed too fast: blink 1/sec
b. Limit breach: speed too slow: blink 2/sec
c. Unknown Command: blink 3/sec
i. This will require a breakpoint or
ii. Other fault injection
The intent is to control freq. (speed) 0 - 150 rpm, steps of 10rpm (hint nibble is 4 bits, 2**4-1 is 15. Steps of 10, = nibble * 10=rpm) or 2**8-1 or 0-255, RPM is the cycle of the state machine (state 1 to state 1).