After some delays in sourcing components and setting up a good test procedure, we now have the PhoneDrone Android/RC interface board in production and available for purchase ($99).
If you've been wanting to experiment with connecting Android phones or tablets to the world of RC vehicles, this is the board for you. It's the only Android ADK board on the market designed to work with RC equipment, and it can interface with APM (1 or 2) via serial, too.
From the product listing:
"The board has 8 channels of RC in and out, with PWM-to-PPM conversion and multiplexing between RC and Android control. You just plug the Android's phone USB connector into the board and you have two-way communications with RC gear and any other board, such as APM.
That means that you can switch between RC control and Android control or mix the two. An example would be "fly/drive by wire". You steer your vehicle via RC, but an Android phone does the actual control using its onboard IMU. On a car, that would allow every turn to be a high-speed controlled drift, for instance (we may show something like that at Maker Faire).
Or, with a UAV, you might have the Android phone doing high-level image processing and object tracking, sending mission commands to an autopilot board such as APM. You might also want to use the phone's long-distance wireless instead of an Xbee for two-way telemetry.
This can either replace APM if you've got equivalent code running on Android, or compliment it with the Android device doing image processing or long-distance wireless comms.
SPECIFICATIONS:
- 8 Input&output PWMs
- Native USB host master (MAX3421)
- Native USB slave (Atmega32-au)
- Arduino Compatible
- Atmega2560 as main controller
- Atmega32-u2 as FTDI substitute and PPM encoder
- Three spare serial ports to communicate with other boards (including APM)
- Build-in 5V-2A switched power regulator (input range 6V - 36V)
- Build-in 3.3V LDO power regulator
- Android TM compatible...
- All Atmega2560 pins exposed.
- High quality PCB is ROHS/lead free, Gold immersed.
- Dimensions: 4" x 1.6"...
Comments
well they ever make a tutorials to explain how to use it or codes
eFuse strikes again...
ADK requires Android 2.3.4 & after nearly a year of waiting, Motorola only recently graced me with Android 2.3.3...
Unless the new Google ownership is interested in righting past wrongs, it looks like I'm gonna need a different development phone. Guess which brand name I won't be buying it from?
Motorola has permanently lost this customer.
-If you are looking for a phone to watch youtube, feel free to buy their products.
-If you want a phone which isn't artificially obsolete the day after you buy it & allows you to keep pace with changing technology, I'd encourage you to run as far and fast away from Motorola as possible.
Who knows? APM Ground Control station may someday be released as an Android app.
Imagine the feeling when you find out the phone you bought less than 1 month ago won't run it because it requires a kernel version +0.0.1 higher than Motorola has decided to let you have.
For the next 2 years your shiny new phone is a bitter reminder of the miserable customer service you received when you called asking for information.
Warn friends & family:
"Motorola: the brand of disappointment and helplessness."
Buyer's remorse? Despair is more like it.
This is cool:
http://tech.slashdot.org/story/11/12/14/1655245/atlantic-crossing-b...
http://en.wikipedia.org/wiki/Automatic_Packet_Reporting_System
I forgot to mention but there's a certain amount of danger in using 3g for RC control as demonstrated by driving down the highway steaming youtube. Line of sight is easier at altitude but sacrificing baud rate for the durability of voice communication might inspire me to use the voice network for this application. It would take a lot of testing to quantify the trade-offs.
"Can you hear me now?"
Robincfey,
Do you mean using the phone as a wireless camera or as a wireless camera + RC Rx/Tx?
The first sounds like an easy Android Market problem to solve.
IE:https://market.android.com/details?id=com.skymobius.vtok&hl=en
The second would be finding an open source video chat app.
IE:http://coenraets.org/blog/2010/07/video-chat-for-android-in-30-line...
http://www.pcworld.com/businesscenter/article/229165/google_release...
I would approach the problem of RC control by exploring tunneling it through video audio or one of the standard internet communication channels like SSH, or maybe GPRS?
http://en.wikipedia.org/wiki/General_Packet_Radio_Service#Services_...
If you can achieve a good degree of autonomy then just feeding GPS waypoints through the google chat API would probably be the next thing I would explore.
I generally try to avoid re-inventing the wheel as much as possible.
Successful code upload to board. I'm satisfied it's working. Now it's all app development.
Here are some examples I just found:
http://www.cellbots.com/
http://code.google.com/p/cellbots/source/browse/#svn%2Ftrunk%2Fandr...
If anyone else is having problems with FTDI I think I figured out how to get the board to recognize on Windows 7.
I searched the web and it was recommended I either create a key called "RunOnce" under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce or delete it and recreate it if I already had one.
The forum topic I found recommended a reboot which I neglected to do which may have fixed things, but I forgot that step and looked for alternatives.
I uninstalled the Atmega 2560 under my device manager and then when I plugged the board back in, I right-clicked, updated driver, and instead of browsing my computer, I told it to "Search automatically for updated driver software".
This failed but gave me the "Have Disk" option. I navigated to the "Drivers" folder of my "Arduino" folder and then used the Arduino Mega ADK R3.inf file under "Communications Ports".
I hope this helps someone. I'm sorry if the details are vague. I'm having to go off of memory on this for fear of breaking something trying to get back to all the screens.
My Arduino IDE now recognizes the board as a Com Port so I think it was successful. I'll update with progress.
demo video please...
when well a demo video of this product come out
-
1
-
2
of 2 Next