Pike is a model rocket project that does not aim any military purpose. It is created as a hobby project and it will remain like that.
Mission of the Pike Rocket is to have computer guided cruising and landing after a successful launch.
Note: To render diagrams in this page, you may consider installing the mercat chrome extension.
- Engine Control
- Software Design of Sub-System
- E-Match ignition
- Ignition test of one engine
- Ignition test of clustered engines
- Burnout detection
- Hardware Design
- Assembly of Engine Section
- Ground Test
- Deployment
- Ignition of ejection charge
TODO: Roadmap will be updated later.
System of the rocket consists of several sub-systems that are explained below. As of today (01/08/2021) CANBUS is selected as a main communication channel between all sub-systems. Reason of this choice is supported with the white paper by Renesas Electronics.
Main system design is based on creating a distributed processing power for each function in the system itself.
System states are described in the table below.
Table 1. System States| State Name | Description |
|---|---|
| IDLE_STATE | The system shall read and report voltage and current information of peripherals and itself. But shall not take any action. |
| READY_STATE | The system shall initialize all the subsystems and check all modules. |
| LAUNCH_STATE | The system shall initiate engine firing if there is no error in modules. |
| RISING_STATE | The system shall check the sensors to be able to detect state events. |
| DESCEND_STATE | The system shall deploy the first parachute and keep track of altitude and acceleration to take an action for state change. |
| DEPLOYMENT_STATE | The system shall deploy the second parachute. |
| LANDING_STATE | The system shall keep track of altitude and acceleration. |
| TOUCHDOWN_STATE | The system shall check all the peripherals and shutdown. |
| MISSION_ABORT_STATE | The system shall take an action according to previous state. |
Note that in each state system will report status of each sub-system using telemetry.
stateDiagram-v2
[*] --> IDLE_STATE
IDLE_STATE --> [*]
IDLE_STATE --> READY_STATE
READY_STATE --> IDLE_STATE
READY_STATE --> [*]
READY_STATE --> LAUNCH_STATE
LAUNCH_STATE --> RISING_STATE
RISING_STATE --> DESCEND_STATE
DESCEND_STATE --> DEPLOYMENT_STATE
DEPLOYMENT_STATE --> LANDING_STATE
LANDING_STATE --> TOUCHDOWN_STATE
TOUCHDOWN_STATE --> [*]
TOUCHDOWN_STATE --> MISSION_ABORT
LANDING_STATE --> MISSION_ABORT
DEPLOYMENT_STATE --> MISSION_ABORT
DESCEND_STATE --> MISSION_ABORT
RISING_STATE --> MISSION_ABORT
LAUNCH_STATE --> MISSION_ABORT
READY_STATE --> MISSION_ABORT
IDLE_STATE --> MISSION_ABORT
MISSION_ABORT --> [*]
Engine Control subsystem is responsible for firing the engine, controlling current status and informing the mission control subsystem.
Table 2. Engine Control States| Sub-System State Name | Description | System State Name |
|---|---|---|
| IDLE_STATE | The sub-system shall check voltage status and continuity of ignition systems. But shall not take any action other than reporting. | IDLE_STATE |
| READY_STATE | The sub-system shall prepare itself for ignition. | READY_STATE |
| IGNITION_STATE | The sub-system shall start ignition. | LAUNCH_STATE |
| PROPULSION_STATE | The sub-system shall check burnout detection sensors and control the stability. | RISING_STATE |
| BURNOUT_STATE | The sub-system shall inform mission control about the detection of burnout. | RISING_STATE |
stateDiagram-v2
[*] --> IDLE_STATE
IDLE_STATE --> [*]
IDLE_STATE --> READY_STATE
READY_STATE --> IDLE_STATE
READY_STATE --> [*]
READY_STATE --> IGNITION_STATE
IGNITION_STATE --> PROPULSION_STATE
PROPULSION_STATE --> BURNOUT_STATE
BURNOUT_STATE --> [*]
sequenceDiagram
Mission Control -) Engine Control: Check the engine status
alt OK
activate Engine Control
Engine Control --) Mission Control: Engines are ready to go!
deactivate Engine Control
Mission Control -) Telemetry: Engines are ok!
activate Telemetry
Mission Control -) Engine Control: Start the ignition!
activate Engine Control
Engine Control --) Mission Control: Ignition is started.
Note over Telemetry: Telemetry module will report <br> all data to ground system.
Mission Control -) Telemetry: Ignition started!
Engine Control -) Mission Control: Burnout!
deactivate Engine Control
Mission Control -) Telemetry: Engines are burnout!
else NOT OK
activate Engine Control
Engine Control --) Mission Control: Engines are not ok!
deactivate Engine Control
Mission Control -) Telemetry: Engines are not ok! Rocket is not ready!
Mission Control -) Engine Control: Abort!
end
TODO: Not decided yet
TODO: Not decided yet
TODO: Not decided yet
TODO: Not decided yet