I've done the basics, getting the various IDE's running and proving the concept of outputting APM sensor readings as ROS topics.
What I'm seeking now is input from the community as to what we want this integration to provide. Any suggestions and/or requests would be most welcome!
Comments
Well, I've hit a snag - maybe one of you folks can help with a suggestion. I have my Mega 2560 board, and just received my "ArduPilotMega IMU Shield/OilPan Rev-H" - and the pins don't come close to matching. Board sizes are different as well, so I don't see how these two can mate, even though the DIY store links them.
Any suggestions? Is the store simply linking together the wrong two things?
Ralph: I can't speak to the ubuntu board - sounds like Garry is familiar with options.
I'm still puzzled why there isn't a uSD card socket on the system. A Class 10, 8GByte card would resolve most size issues and consume very little power. It's simple to write a driver that would allow people to "swap" functions into the main cache for speed. Is there some reason this isn't available - or did I miss the option somewhere?
My only real concern has been to find the right integration point. Putting ROS interface code at the individual sensor level seemed icky. I'm not familiar enough with AMP to know, but I gather people generally agree that this MAVLink interface is the best place. I can certainly look at it to assess any issues.
Or I can turn this topic over to you, if you want to do it. No issues with me...I'm still digging thru code to learn what's where.
Chris Anderson posted about ROS-MAVLink-ArduPilot Mega integration and linked to the ROS package back in March, so people might want to take a look at that:
http://diydrones.com/profiles/blogs/willow-garage-announces-ros
Ralph Castain, I am also interested in publishing new waypoints to an APM using ROS. I guess my full wish list for ROS integration would be a) read/write APM waypoints using ROS b) have APM publish current state, including next waypoint c) send data from another GPS to the APM through ROS and d) send heading+alt+airspeed from another source into the APM through ROS. I'm guessing (a) and (b) can already be handled through ROS<->MAVLink package?
Sorry for lowering the awesomeness of the joke, I got it too...
One of the coolest things about ROS is the Microsoft kinect support so it can be used for SLAM (Simultaneous localization and mapping) for indoor use. Does anybody know what UC Berkley uses for there quads to interface with there motion capture system? I think it may be ROS as I'm pretty sure the use pelican quads.
This is indeed the WillowGarage ROS. I'll take a look at these use-cases and get back to you on degree of difficulty. Sending heading, speed, and other sensor-related data from APM to ROS is pretty easy. I haven't studied going the reverse direction yet.
I'll also take a look at Player and Pelican - those terms are new to me :-)
One thing everyone is using ROS is for hooking in collision avoidance routines... and computer vision stuff (hmmm, there's got to be something to do with FPV and ROS)...
I was thinking of doing this but never got around to it...It would be neat to replicate AscTec Pelican drone node so you could use it as a drop in replacement for the quad. It then would be compatible with the code that MIT & Stanford use for there aerial quad kinect SLAM. It would also be much cheaper than a <$10,000 AscTec system
-
1
-
2
-
3
of 3 Next