Example 1. In this example, the RAPU v6.0 Device is connected to a control board, such as a Lynxmotion SSC32U, ENTTEC DMX USB Pro, Pololu Maestro Servo controller, etc. via USB. Power is provided via the USB-C input, and speakers connect to the 3.5mm audio jack. The Device acts as a Wi-Fi server and can be controlled from any connected Wi-Fi device via HTTP. The Device can also be controlled via wired Ethernet or with a monitor and keyboard.
Example 2. In this example, a Lynxmotion SSC32U is connected to the Android device via a USB-OTG cable (see System Requirements). Audio is output on the Android device's internal speakers.
Example 3. In this example, an ENTTEC DMX USB Pro (or a Open DMX USB) is connected to the Android device via a USB-OTG cable (see System Requirements). Audio is output through the built-in headphone adapter to external speakers.
Example 4. In this example, an FTDI USB-to-serial cable is connected to the Android device via a USB-OTG cable (see System Requirements). The serial port can be connected to legacy devices, for example, a Mini-SSC compatible controller.
Example 5. In this example, an FTDI USB-to-serial cable is connected to the Android device via a USB-OTG charging cable (see System Requirements). The charging cable, supported on some Android devices, enables the phone to be charged while acting as the USB host port. The serial port can be connected to legacy devices, for example, a Mini-SSC compatible controller.
Example 6. In this example, an embedded Android device, such as the ODROID-N2+, is used. The audio is output on the built-in head phone jack and one of the USB ports is connected to a Pololu Maestro Servo controller. An external monitor is also connected, enabling the RAPU app to be controlled.
