by flomartel » Tue Sep 30, 2014 11:36 pm
Hi Max,
I didn't expect any less from Larry!
Thanks Steve and Max about suggesting the discovery board. Indeed great value... Considering the amount of changes I'll need to make to the code, I probably could use more feedback than values displayed through MavLink, but there's a good chance I'll start with MavLink initially as it will also allow me to learn more about it (essentially,even though there are other options out there, I plan on using MavLink anyways to retrieve telemetry information - needed by the collision avoidance algorithm - and to send commands to the autopilot).
I guess the choice of development tool is a matter of personal preference, and although I've used Eclipse before, it's been a while (never used SWD or programmed STM32F4s before though)... From a cursory search query, it looks like there is support for ST-LINK/V2 in Linux, but if I can just get by using Windows, then that's probably what I'll prefer. So, do you recommend the STM32F4Discovery with STM32F407VG processor model?
Great question about the M4 vs. the AQ6 w/DIMU. I don't know enough yet about the differences (essentially same source code?) to make a judgment call, so I'm tempted to turn the question back to you. I'm candidly struggling to find information about the hardware and interfaces besides a few pictures and diagrams lying around... So, which one do you think would be most suitable given what you know about my project? For reference, my project is a continuation of this one:
Also, I would like to know the state of development and possible pinout/user guide information about the PDB. It would greatly simplify my design requirements if I could run the collision avoidance code directly on the PDB's STM32F405. Now I feel like I'm overly demanding...
Random question: has there been any discussion about interfacing the ESC32v3 with other autopilots? I know that would require code changes on those autopilots, but I believe some could be convinced by some of its features...