This note discusses how to integrate the payload into the satellite bus, also how we can set up a development environment. (Some figures from the NanoAvionics M6P Software and Hardware ICDs).
CubeSat bus overview
The figure below shows how the M6P CubeSat bus generally is organized. In our case, we do not have the propulsion unit.
Our payload should be connected to the Payload Controller (PC) through the CAN-bus.
Communication network and software architecture
The communication between ground and satellite, as well as between sub-systems is made possible through the use of CubeSat Space Protocol (CSP)
This means that the our payload processor must implement CSP in order to be able to connect and communicate with the rest of the satellite. This also implies the use of CAN-bus interface for all communication. An option might be that payload data (images) might be transmitted over a RS422-interface, as a streaming interface (see below).