IOIO OSD Camera Controller

Droid IOIO is an application that turns your Android smartphones into a powerful remote IOIO-OTG based drones controller system enhanced with Video-Streaming and OSD (On-Screen Display) capabilities.

The system is based on three (3) components:

1. Droid IOIO: The CLIENT applicaiton running on the smartphone connected to the IOIO-OTG (drone)

2. The IOIO-OTG Board

3. The Droid IOIO Controller: The SERVER application sending commands to the Driod IOIO CLIENT and receiving Video-Streaming and telemetry information

The Droid IOIO Controller (SERVER) is designed to work with standard Game Pads supporting ANALOG mode.

The Droid IOIO (CLIENT) negotiate a TCP/IP and a UDP connections to the Droid IOIO Controller (SERVER). The TCP/IP connection is used for commands and telemetry communications, while the UDP connection is used for the real time Video-Straming. The IOIO-OTG board is linked to the Droid IOIO (CLIENT) receiving the commands from the Droid IOIO Controller (SERVER).

The Droid IOIO (CLIENT) connects to to the Droid IOIO Controller (SERVER) according to the Client/Server architecture. In this way the Droid IOIO, the client, can connect to the Droid IOIO Controller, the server, also over the INTERNET. In this case, only the Droid IOIO Controller requires a public IP or a reachable Host Name, while the Droid IOIO (CLIENT), the client, does not require neither a public IP nor a reachable Host Name!

The Droid IOIO (CLIENT) records videos locally so that the quality of the video can be the best possible according to the smartphone camera hardware. Droid IOIO (CLIENT) automatically detects the best settings and camera configuration for recording the best possible quality video (recording functionality is available for the professional version only).

Since it is the Client (Droid Camera) connecting to the server (Droid Controller) several different network architectures are possible:

1. LAN (Local Area Network): the simplest network architecture to work with Droid Camera 'N Controller. In this case both Droid Camera (Client) and Droid Controller (Server) will connect to a local router using local IP addresses. This configuration can be used for "monitoring" specific places of a house, office, etc...

2. INTERNET: this is the most complex network architecture where Droid Camera 'N Controller can operate. Since it is the Droid Camera (Client) connecting to the Droid Controller (Server), the Droid Camera (Client) does NOT require a public IP, but only the Droid Controller (Server) would require a public IP address or an Host Name registered with a DNS. The application has been designed to work with DynDNS.