Arduino Code Structure

There are some challenges building up the code structure that will run on the Arduino:

1. Create an exchangeable interface that offers all methods, which are required to communicate with the hardware and environment.
   The benefit from this is, that the interface can be chosen depending on the sensors and if the flight is real or simulated.
   
   
2. Make sure that within a single tick some sensor value is not measured multiple times just because it is requested on several occasions.
   This is important because every measurement takes time and consumes power. For that reason the above-mentioned interface should serve a resetTick function to know when a new tick hast begun. 
   
   
3. Perform the implementation of the SCCharts-generated code as simple as possible.
   The Arduino code provides a setup method and a loop method, which are equivalent to the reset function and the tick function in SCCharts. Though KIELER can easily create some Arduino code out of any SCChart, important host code is missing:
   • At the very beginning of the Arduino code some dependencies like libraries and the interface need to be included.
   • Before every new tick the interface must be notified.
     
     

Basic Arduino sketch

The main routine

#include "CompInterface.h"
#include "CollisionAvoidance.h"
CompInterface comp;
void setup() {
  reset();
}
void loop() {
  comp.resetTick();
  tick();
}