Solar Sailing Software Architecture Mission Specific Board Prototyping

Solar Sailing Software Architecture

Mission Specific Board Prototyping ● MSB - MP 430 FR 5739 ● Ext. FRAM - MR 45 V 200 A - 2 MB Memory ● Communication To Flight Computer ○ ○ ○ SPI Slave(MSB) To SPI Master(FC) Detumbled Signal Data Transfer - Initialized By Software Interrupt ● Power Reset ○ ○ ○ Reinitialize SPI Interfaces, ADCs, Timers Power Reset Indicated By Internal FRAM Status Byte If Sail Was Deployed Already, Jump To Velocity Capture ● Communication To Memory And Sensors ○ SPI Master (MSB) To SPI Slave (Memory, Sensors)

Flight Computer Simulator ● Raspberry Pi ○ ○ ○ Serial communication with MSP 430 microcontroller Connect to Cube. Sat PC-104 bus Execute ADCS algorithm controller ■ Actuator Control ■ Feedback gyro data to algorithm ● Simulate mission timeline ○ ○ ○ Test ADCS control in expected tumble conditions Send deployment commands to MSB Collect deployment information from MSB ● Graphical interface for Cube. Sat electronics ○ ○ Provide user control for ADCS actuators Graph sensor data from MSB

Serial Interfaces - SPI - Serial Peripheral Interface ● SPI: Flight Computer to MSB ○ ○ Flight Computer is SPI Master - Initializes all data transfers and has overall control of MSB is SPI Slave - Interrupts normal operation based on commands from Flight Computer ● SPI: MSB to Memory and Sensor Peripherals ○ ○ MSB is SPI Master - Initializes all data transfers Memory and Sensors are Slaves - Respond to commands from MSB