Robot Driver Interface definition

[formal]

No description provided.

[formal]

1. I think that we should use SPI rather than I2C.
2. We probably need an abstract definition of the requests & responses, but we also need a detailed description of the bits communicated over SPI.
3. The protocol will be asymmetric, i.e., the request (commands) will come from the Edison and the responses (results) from the Arduino.

This protocol will be implemented by #41 and #42.

[conor-f]

1. I agree that we should use SPI.
2. I will begin by creating an abstract definition in the coming days then later in the sprint I will flesh out details of the actual communication. I feel like this is the best option as the abstract can then be used by the team and I can work out the lower level technical details which are more likely to go wrong.
3. Yes.

[formal]

See #54.