Since the Viper MAV project is still somewhat in the design exploration phase we are only capable to assemble a tentative roadmap. However, a tentative roadmap is better than none, as it creates both a direction to follow and commitment to actually follow it.
-
107-Arduino-UAVCAN shall be extended to support all currently officially released UAVCAN profiles (public_regulated_data_types/uavcan and public_regulated_data_types/reg/drone). Since the message set for controlling ESCs is contained within reg/drone this is setting us up for being able to control UAVCAN v1 based ESCs. This would entail extending nunavut to automatically generate Arduino UAVCAN wrapper files as manually creating all those types would be a maintenance nightmare. Another possibility would be to leverage the code generation web-service under development.
-
Complete implementation of both UAVCAN on Arduino reference implementations UAVCAN-GNSS-Node and UAVCAN-ToF-Distance-Sensor-Node. During this process we expected to discover common functionality which could be extracted into a reusable Arduino library.
-
Complete implementation of 107-Arduino-BNO085 to fully support the already existing NavShieldBNO.
-
Extend 107-Arduino-TMF8801 with currrently missing features (such as GPIO control and daisy chaining of TMF8801 modules).
-
Eventually add kocherga based 2nd stage bootloader for software update via UAVCAN/CAN (uavcan forum thread).
If you feel that there’s something that’s currently not on the roadmap but should be - please feel free to reply to this post. Also, if there’s something you’d be interesting in doing than I’d love to hear about it (private message, forum post, email, …).