Aerotenna User and Developer Hub

Aerotenna User and Developer Hub

Welcome to the Aerotenna User and Developer Hub. Here you'll find guides, manuals and tutorials to help you get started with using OcPoC and μ radars, as well as support and discussions if you get stuck. Let's jump right in!

Get Started

FAQ: OcPoC™ Zynq Mini

FAQ

ArduCopter Not Executing or No Filesize

One common cause of the Ardupilot executable (arducopter, arduplane, etc...) not running may be due to an error while copying the binary from the PC onto the SD card. You may see something like the image below.

arducopter not executing

arducopter not executing

You can double check the file size of your Ardupilot executable using the following command in the gtk terminal (or PuTTY from Windows):

ls -la
arducopter executable has no filesize (as underlined above)

arducopter executable has no filesize (as underlined above)

Solution: Recopy the Ardupilot binary from your PC onto the SD card for OcPoC - making sure to properly eject the SD card - and check the file size. You can follow the steps HERE to accomplish this process. Start OcPoC again and check the file size on the executable on the OcPoC; you should see something similar to the following image.

Correct file size of ArduCopter

Correct file size of ArduCopter

Under normal circumstances, when you start Ardupilot (in this case, arducopter), you should see something like the gtkterm display shown below.

./arducopter -A /dev/ttyPS0	
proper ArduCopter output

proper ArduCopter output

Problems with Waf: ./waf configure --board ocpoc_zynq

If you encounter an error with the "./waf configure --board ocpoc_zynq" command, you may be missing some required toolchains. This error will look similar to the following image:

Solution: This issue can usually be resolved by double checking the installation of the required tools. Please refer to the '[Downloading Required Files'] section(https://dash.readme.io/project/aerotenna/v1.0/docs/downloading-required-files-1) to make sure you have everything you need.

Connecting to OcPoC™ from Windows

If you need to connect to the OcPoC™ from a Windows PC, you'll first need to install PuTTY. Connect the OcPoC™ to your PC, open the Device Manager in Windows (in Windows 10 you can simply search for 'Device Manager'). With power supplied to the OcPoC™ you should see something like the image below, wherein you should see a drop-down item for "Ports (COM & LPT), and in that section should be a device similar to "USB to UART Bridge". The "(COM#)" tells you what COM port you'll use to connect via PuTTY.
Note: if you have multiple devices connected to your PC, unplug the USB cable coming from the OcPoC™ and plug it in again. The Device Manager window will remove one COM device, then reveal it again. That's the correct COM port for the OcPoC™.

Once you have determined the correct COM port, open PuTTY, select the "Session" category (which should be the default upon opening PuTTY), and select the following settings:

  • Serial Line: COM#
  • Speed: 115200
  • Connection type: Serial

Your setup should look like this:

Making sure you have the OcPoC™ powered on and connected to your PC, click Open. Once OcPoC™ has finished its boot up sequence, you should see something like the image below.

Building Ardupilot in a Linux OS on a Flash Drive

If you are running Linux from a flash drive, you may encounter several issues throughout the "Get Up and Running Quickly" tutorial while trying to build the Ardupilot executable. For example:

  • You may see an error that says "Could not create the directory ...". This error means you need to fix the permissions on your flash drive (see tutorials for 'chmod' and 'chown').
  • When you build the Ardupilot executable with the "./waf --targets bin/arducopter" command, you may get an error that says "ImportError: No module named future". There are two potential reasons for this error:
    • You're missing the prereqs to build ardupilot. Be sure to run all of the "Building autopilot:" commands in the Load Files onto SD Card section.
    • The OS update may not be working properly wherein your OS on the flash drive may be using a non-existent CD-ROM. Explicitly remove the CD-ROM drive from your flash drive based OS, and try the Get Up and Running Quickly tutorial from the start.

Setting Up OcPoC™ from a Virtual Machine

Running Linux in a virtual machine generally shouldn't cause any issues with the initial setup of OcPoC™. However, you may have problems talking to the OcPoC™ from gtkterm. If this is the case, we recommend using PuTTY from Windows to connect to OcPoC™ after you've setup the SD card with the flight software executable.

Changing/Replacing your USB WiFi Adapter

Once you connect a USB WiFi adapter to the OcPoC, the board will assign the device a name and address in memory. If you need to replace your WiFi adapter, you should follow these steps.

  1. Power on your board, connect via USB and log in with GTK terminal.

  2. Remove old WiFi adapter.

  3. execute the following command in GTK terminal

sudo rm /etc/udev/rules.d/70-persistent0net.rules
  1. Power down your Ocpoc, plug your new WiFi adapter in and power back up.

If your new WiFi adapter is compatible with the OcPoC it should automatically be recognized and configured.

FAQ: OcPoC™ Zynq Mini

FAQ