DroidPlanner (GCS) on Android tablet

I lucked out and just managed to get IceCreamSandwich 4.x installed on my old (circa 2012 with GingerBread 2.x) Chinese Android 7" tablet (iView 760TPC). It is dual-core with 512mb RAM, and supports USB Host Mode (for 3G cell dongles, etc.). The tablet came with a little OTG USB adapter cable that allows you to plug in normal-sized USB flash drives (while I don't use it much, it goes work). The tablet's native USB port is Mini (not Micro) so I can't use the OTG cable supplied with HK 3DR v2 Telemetry radios. Therefore, for now, I will use the iView OTG cable, and the normal USB cable that I use with the radio on the laptop.

At first, DroidPlanner didn't seem to work (radio lights weren't flashing quite right, and DroidPlanner would not Connect). I checked the page at DroidPlanner GitHub, and it mentioned trying the USB Host Check app. Sure enough, the checks all failed (which I thought was strange ... since old OTG USB Adapter was already working for Flash drives). I went ahead and clicked the "Fix It" button and rebooted. I still had the 915mhz radio connected. After it booted up, it detected the radio and ICS asked me if I wanted to use it with DroidPlanner. This was a sure sign that things were looking better. Sure enough, after starting DroidPlanner, it connected with no problems. HUD is working nicely.

I was then getting a "Unfortunately, TTS has stopped" (crashed) on every startup. I clicked OK, and the app worked fine. The error went away completely after the Google Play Store offered a "TTS Update" and I let it install. Now, TTS (Speech Prompts) work fine in DroidPlanner.



I used this mount from HobbyKing. I also upgraded to this 5inch USB Mini-Micro male OTG cable for a much cleaner look.

Edit: In March 2015, I upgraded to a better Android tablet.

Troubleshooting:

USB-OTG cables are asymmetrical (only properly communicate when connected in proper direction). It has more to do with internal wiring than connectors that might be soldered on each end. USB-OTG port should at least work with USB flash drives or "wired" computer direct-connected storage (as a starting point).

DroidPlanner (even DP v1) requires ICS v4.x or higher on Android device. Test with DP v1 first (it has smaller memory and lower resource footprint). If that works, you can uninstall it and try a higher version. DP v2 and v3 might crash or malfunction if your device is not up-to running them. DP v3 (Tower) might require a dual-core or better and 1gb ram (depending on what background apps you are running).

With the Nova's main LiPo battery connected, get Nova working with 915mhz v2 radios in MissionPlanner for Windows first. This checks telemetry radios (important step) and Nova. Always properly Disconnect MP with button (before disconnecting physical cable). Leave radio on Nova, but move laptop's radio to Android device, now using USB-OTG cable.

To verify the your Android device even has a functioning USB port, I like to first test it with a flash-memory device.

You can really only have one version (either v1, 2, or 3) installed at a time (to avoid conflicts). Be sure radio-dongle and/or USB-OTG cable is disconnected at first. Install Droid Planner and reboot device. After full boot, connect radio (it should be detected). Select radio as Default device for DP. Start DP and try to connect.

If radio is not detected, run USB Host Check App from TaurusLabs. If device abilities fail, click Fix button and run Check again. After Connect, move quad and see if Hud responds (this will check basic communications). Forum member Jester1964 reports that they had to enable "USB Debugging" in Developer options before it would work for them.
 

RX install complete

Basic 5 channels and 3 flight modes are setup. I mounted the RX antenna better (the external one uses small strips of foam tape and a tie-strap). Also, tied the wires down.

I can tilt quad and see it respond in MissionPlanner. I can also arm motors and run them a bit (no props yet).

 

 

Edit 2015-04 : Antenna Mounting and Placement Notes

So while this is the general idea for RX antenna placement, my RX has been moved to the other side since this pic was taken. Remember to use Taranis RSSI meter to evaluate antenna placement (with all electronics and radios ON). I like the RX antennas to be at 90-degrees from each other. The one in back (although inside) is good because often the back is facing me. At least one outside is good. However, I'm not currently seeing much of a difference having it in similar position (but inside, just on other side of thin plastic body). I'm not drilling another hole (for outside mount) until I decide exactly where my 915mhz Telemetry antenna will be finally (I have moved it several times) and also a possible 5.8ghz FPV TX. I would like all 3 antennas to be on different sides (and also no interfere with GPS, Compass, etc.).

 

So, the whole time during "bench build & setup" (non-flight and no props) I have not had the body shell screws installed (so I can get back inside if needed). If powered-up and connected to MP, I also like to have the compass connected. I have been using 4 large rubber-bands to keep it together while handling and it works pretty good .

 

 

 

Another important benefit of this FrSky radio set... Between the Telemetry display on the TX and RSSI monitoring ... it's easy to know if the TX and RX are still bound together (without observing the status-led on the RX).