Comment by Radoslaw Kornicki on January 16, 2012 at 3:34pm

Roman, as to the use of IOIO, well it blo#~ !!! I have trashed it after just few minutes of playing with it. Since then I have re-done it all, this is my board and my code implementations on booth the board level and the tablet software. Plus I don't contol the servos with it, the board is the host in the system and it is intended to be a transmitter controller with a tablet interface. The hardware is designed to serve such purose.

Comment by Squalish on January 16, 2012 at 4:52pm

If you used one of the new color epaper displays, that would solve a major problem with autopilot groundstations - the awkwardness of a laptop in full sun on rough terrain. You would need to make sure it's comfortable in the hands, though.

Comment by joe on January 16, 2012 at 9:29pm

Aside from the enclosure and sticks - this seems similar to another project mentioned at diydrones:

http://code.google.com/p/copter-gcs/

http://www.diydrones.com/profiles/blogs/coptergcs-now-supports-mavlink

Unfortunately, I don't think copter-gcs works over usb (?), just bluetooth - but it might be a start for someone that does not want to wait until this is released. I planned to try it on a tablet some time next month. Haven't thought about how to interface sticks though. PS3 controller...?

The pressure sensor reference in this project is an interesting idea

Comment by Roman on January 16, 2012 at 11:48pm

Hello,

I used a custom IOIO board that take power from the tablet and not the opposite (but you can still power it with a battery).

If you look carefully at my blury video, you can see that this is not the IOIO that is driving the servos, the IOIO send a ppm signal to a hobbyking salvaged transmitter.

I had the same idea, to have the tab be a configurator and let the board be the brain, but I didn't implemented it yet.

Let me know if I can be of any help.

Comment by avionics on January 17, 2012 at 12:48am

very very nice design.

Comment by Bart on January 17, 2012 at 4:54pm

@joe

Connecting through USB was attempted (and almost entirely implemented) in a private branch of copter-gcs. However, the tested (unmodded) android phones/tablets didn't support USB/Serial comminication, so the options was let go to avoid major hassles with support.

@radoslaw Nice work! How did you get the MAVLink information parsed in android?

Comment by Pauli Seppinen on January 19, 2012 at 11:37am

Nice work. I have had also similar ideas. My approach is a little bit more embedded. It is based on mbed controller, 4D touch screen, xbee and mavlink. Currently I have only the basic MAVLINK messages working with GCS and tested with modified UDB 4 in HIL sim with Xplane.  Also in uplink the mode control is working in simulation. the downside of this approach is that it is not so suitable for online map, but x,y map is implemented. the good thing is that mbed API is fast development environment and adding features using mavlink API is relatively simple. I'll post something when the time is right

Comment by Maciej on January 19, 2012 at 5:48pm

sweeeeeeeet!!!! I want one! I have a tablet and ardupilot...!!

Comment by Radoslaw Kornicki on January 19, 2012 at 7:20pm

@Bart, The micro is parsing all info to a format that I've thought to be best for the tablet communication. I'm passing information as hex numbers and then decode them again on the tablet.

Comment by Nick Mann on January 20, 2012 at 1:11pm

Rad, your initiative is amazing.  You could raise more funds the same way these guys did. You've clearly got a lot of intense interest and support.

Comment

• ‹ Previous
• 1
• 2
• 3
• 4
• 5
• Next ›
• Page