fredvol
commented
4 years ago One option can be to use a I2C splitter: https://store.mrobotics.io/mRo-JST-GH-GPS-Port-to-I-C-Bus-Splitter-p/mro-jstgh-gps-i2c-split-mr.htm
an other one active ( for managing the 5V voltage) https://store.mrobotics.io/ProductDetails.asp?ProductCode=AUAV-I2C-HUB-MR
with this kind of keyboard: https://www.instructables.com/id/Arduino-Nano-I2C-Matrix-Keypad-With-PCF8574PCF8574/
also on the next step an small screen can be added to confirm the test pilot that the device is fully ready before taking off ( exemple: the GPS sattelite reception )
Idea: I think it could be very useful to be able to put some markers in the log. The idea is to ask the test pilot to push some buttom at the begining of the manoeuvre and at the end. The most important to be able at the end of the manoeuvre to discard the test ( collapse too small , or too big for exemple) for the analysis software to be able to ignore the datas:
There is 3 strategy :
Here the list of the different option to send data to the device:
Could be interesting to see where the air speed sensor should be plug.
Looks like the driver should be added in the source to be investigate