-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support UAVCAN v1.0 #42
Comments
Good morning @pavel-kirienko 👋 Naturally we are using the latest version of CC / @generationmake @per1234 |
We are aiming at early June. If you could lend us a hand here, it would be appreciated. Also, may you be interested in sharing the info about your project at the UAVCAN forum? |
Thank you for letting me know. Early June sounds good to me as we also need some time to get 107-Arduino-UAVCAN into usable shape. We've got experienced firmware engineers on the team so building and testing any sapog changes are well within our ability 😉 I'd love to share on the UAVCAN forum, which category do you think would be best suited and what exactly do you want me to share (focus on the Arduino UAVCAN abstraction or the whole project?). |
What I meant is that if your engineers could help us integrate libcanard v1 here instead of libuavcan v0, that would be great. But testing also helps.
This category works best: https://forum.uavcan.org/c/app (the libcanard subcategory is also probably acceptable depending on the scope of your post). I think we want the full context. |
Good morning 👋 I don't want to promise something we can't deliver (due to time constraints mostly) but we'll give it a try 🚀 |
Hey all, just wanted to mention that I'm interested in getting Sapog-compatible ESCs and migrating sapog to UAVCANv1 this summer (although I can't provide a timeline at this point). Trouble is actually getting sapog ESCs, since kotleta20 is semi-permanently out of stock due to chip shortages and Orel 20 is out of my budget. Perhaps I'll design a board. |
https://forum.uavcan.org/t/uavcan-2019-roadmap/666
The text was updated successfully, but these errors were encountered: