Building an autopilot from scratch using a RaspBerryPi Zero : Mini Zee

ppoirier · September 27, 2016, 1:21pm

Here is another update on conflicting 2,4 Ghz between WIFI and Radio-Control.
,I switched WIFI to an EDIMAX AC600 running as an Access Point on 5 GHZ with the use of HostApd and loading this DRIVER.
Here is a picture of the modified USB Dongle with the micro USB adapter cable soldered directly + a 5volts BEC + a RP-SMA adapter cable to attach the 5GHZ antenna.
So far the tests are good, I’ts flying smoothly and the video is fluid at 640x480 x 20fps up to 500 Meter.

ppoirier · September 27, 2016, 1:22pm

Here is a picture of my routing; Imu on top , Baro bottom, they share the same SPI bus, with different CS (Chip Select), VCC, Ground and X=Not Connected.
Hope it can help

Joao_D_Junior · August 16, 2017, 5:03pm

First of all congratulations for the project, very inspiring, it’s the first one I meet.

I’m starting in the area of drone projects, and I have an idea of making an autopilot for mine, I found your topic interesting and would like to exchange some ideas with you, for example, does the drone follow a preconfigured route? Can he have a reasonable speed?

I am grateful now.

ppoirier · August 16, 2017, 5:27pm

Thank You.

The speed is related to the type of quadcopter, In the model showned here , the speed can be quite good (up to 100 Kmh) in manual (stabilized or acro mode).

I suggest you go through the wiki , you will find answer to most of your questions: http://ardupilot.org/copter/docs/auto-mode.html

And for building, you might consider building a BBBMINI https://github.com/mirkix/BBBMINI this is easier to build and you benefit from a better support.

Joao_D_Junior · August 16, 2017, 5:35pm

Ok, I’m very grateful, it will be of great help, and I already read about BBBMINI, it really supplies all expectations.

Once again, congratulations on the project!

Joao_D_Junior · August 18, 2017, 1:42pm

Could you tell me where you bought the drone structure? I live in Brazil, there are no stores with this material.

ppoirier · August 18, 2017, 1:59pm

@Joao_D_Junior ,
most of my stuff is from China, either Banggood , Aliexpress or HobbyKing

JAR4x4 · December 13, 2018, 3:58pm

@ppoirier , and others…

Hi!
I got inspired by this post a long time ago, and finally I started to build my own version of your project. I understand that the Pi0 isn’t the best option for running Ardupilot, I’m using the Pi0 because to learn both Raspberry and the Ardupilot code.

I’m running Raspian Stretch with kernel 4.14.81-rt47+ (RT patch from the official raspian kernel git) and Arducopter 3.6.3 compiled for PXFMINI with the mods for PCA9685 as you have described. I see that the code has changed a bit since you made your controller.

I have got everything working except the PCA9685. Without the PCA9685 I can start arducopter on the PI, and connect to my GCS. When I connect the PCA9685 it’s not possible to establish an connection with the GCS. It looks like arducopter starts without any errors.

Is the problem the change in the code regarding how ardupilot handles the PCA9685 over i2c?

Best regards
Alex

ppoirier · December 13, 2018, 4:15pm

@JAR4x4 cool, as noted here:

Have you modified these lines ?

github.com

ArduPilot/ardupilot/blob/master/libraries/AP_HAL_Linux/HAL_Linux_Class.cpp#L179


      
          #elif CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_NAVIO || \
                CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_ERLEBRAIN2 || \
                CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_BH || \
                CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_DARK || \
                CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_PXFMINI || \
                CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_OBAL_V1 || \
                CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_CANZERO
          static RCInput_RPI rcinDriver;
          #elif CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_ZYNQ || \
                CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_OCPOC_ZYNQ
          static RCInput_ZYNQ rcinDriver;
          #elif CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_BEBOP
          static RCInput_UDP  rcinDriver;
          #elif CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_DISCO
          static RCInput_Multi rcinDriver{2, new RCInput_RCProtocol("/dev/uart-sbus", "/dev/uart-sumd"), new RCInput_UDP()};
          #elif CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_AERO
          static RCInput_SoloLink rcinDriver;
          #elif CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_NAVIO2 || \
                CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_EDGE
          static RCInput_Navio2 rcinDriver;
          #elif CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_RST_ZYNQ

JAR4x4 · December 13, 2018, 4:22pm

@ppoirier , thanks for your quick reply!

Yes, I have modified that line, just changing true to false, and 3 to 0

running sudo i2cdetect -y 1 shows the address of the PCA9685. I have also tried to run raspbian without the RT patch = same problem

ppoirier · December 13, 2018, 5:35pm

Did you connect the PWM enable (GPIO27) pin 13 to the PCA OE ?

JAR4x4 · December 13, 2018, 5:39pm

Yes, I have tried both with and without PWM enable connected

JAR4x4 · December 13, 2018, 5:46pm

I’m going to check now if the PCA is actually working with the Adafruit python library

ppoirier · December 13, 2018, 5:59pm

Yep, I was about to suggest that and checking with a bus analyser if you have one. Otherwise the code might be broken, I dont think anyone is building pxfmini these days… It’s a ChiBios world with F4 & F7 FC now…

JAR4x4 · December 13, 2018, 6:07pm

Hehe, I know… But I want Linux onboard for the learning… I don’t have a bus analyzer, but i wil hook my scope up to PWM0 and see what happens when i run the python example. I will post back with my results.

I think Erle still is selling the Pxfmini? Maybe they run a custom erle ardupilot flavour?

ppoirier · December 13, 2018, 6:11pm

I think Erle is running an oudated version of ardupilot, … looking at Erle Forum I dont see much activity either…
Anyway, this is still a good primer project for anyone interested in linux integration , as long as the code is not broken and be aware that the PPM routine using the DMA Soft Int has not aged well, it had a tendency to crash on since 3.5

JAR4x4 · December 13, 2018, 6:25pm

Ok, I have seen that, but I will try to compile the erle fork now, and see if that helps.

I hooked my PCA to my scope and ran the Adafruit test code, looks like the PCA works =)

Yes, I have seen that there has been some issues regarding PPM. No problem for me in this project, I’m going to use mavlink for controls over a wifibroadcast setup I’m also working on =)

ppoirier · December 13, 2018, 6:58pm

Might try adding a bus define ? … something like:
#define HAL_RCOUT_RCOutput_PCA9685_I2C_BUS 1
here:

github.com

ArduPilot/ardupilot/blob/master/libraries/AP_HAL/board/linux.h#L269


#define HAL_RCOUT_RGBLED_BLUE     15
#elif CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_PXFMINI
#define HAL_INS_DEFAULT           HAL_INS_MPU9250_SPI
#define HAL_INS_DEFAULT_ROTATION ROTATION_YAW_270
#define HAL_INS_MPU9250_NAME "mpu9250"
#define HAL_BARO_DEFAULT          HAL_BARO_MS5611_SPI
#define HAL_BARO_MS5611_NAME "ms5611"
#define HAL_COMPASS_DEFAULT       HAL_COMPASS_AK8963_MPU9250
/* HMC5843 can be an external compass */
#define HAL_COMPASS_HMC5843_I2C_BUS 1
#define HAL_COMPASS_HMC5843_I2C_ADDR 0x1E
#define HAL_GPIO_A_LED_PIN        24
#define HAL_GPIO_B_LED_PIN        25
#define HAL_GPIO_C_LED_PIN        16
#define HAL_GPIO_LED_ON           LOW
#define HAL_GPIO_LED_OFF          HIGH
#elif CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_AERO
#define HAL_INS_DEFAULT HAL_INS_AERO
#define HAL_BARO_DEFAULT HAL_BARO_MS5611_I2C
#define HAL_BARO_MS5611_I2C_BUS 2
#define HAL_BARO_MS5611_I2C_ADDR 0x76

JAR4x4 · December 13, 2018, 8:17pm

Thanks for the tip, but I’m not that into the code yet… I found that the PCA address is defined here:

github.com

ArduPilot/ardupilot/blob/master/libraries/AP_HAL_Linux/RCOutput_PCA9685.h#L7


#pragma once


#include <AP_HAL/I2CDevice.h>


#include "AP_HAL_Linux.h"


#define PCA9685_PRIMARY_ADDRESS             0x40 // All address pins low, PCA9685 default
#define PCA9685_SECONDARY_ADDRESS           0x41
#define PCA9685_TERTIARY_ADDRESS            0x42
#define PCA9685_QUATENARY_ADDRESS           0x55
#define PCA9685_QUINARY_ADDRESS             0x61


namespace Linux {


class RCOutput_PCA9685 : public AP_HAL::RCOutput {
public:
RCOutput_PCA9685(AP_HAL::OwnPtr<AP_HAL::I2CDevice> dev,

This is the same address that pi@raspberrypi:~ $ sudo i2cdetect -y 1 displays…

Has anyone tested that this code works?:

github.com

ArduPilot/ardupilot/blob/fbf072d84be9e54ee9973309ac0bfc9c7d882981/libraries/AP_HAL_Linux/HAL_Linux_Class.cpp#L179


static RCOutput_PRU rcoutDriver;
#elif CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_BBBMINI || \
     CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_BLUE || \
     CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_POCKET
static RCOutput_AioPRU rcoutDriver;
/*
 use the PCA9685 based RCOutput driver on Navio and Erle-Brain 2
*/
#elif CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_ERLEBRAIN2  || \
     CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_PXFMINI
static RCOutput_PCA9685 rcoutDriver(i2c_mgr_instance.get_device(1, PCA9685_PRIMARY_ADDRESS), true, 3, RPI_GPIO_27);
#elif CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_NAVIO
static RCOutput_PCA9685 rcoutDriver(i2c_mgr_instance.get_device(1, PCA9685_PRIMARY_ADDRESS), true, 3, NAVIO_GPIO_PCA_OE);
#elif CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_BH
static RCOutput_PCA9685 rcoutDriver(i2c_mgr_instance.get_device(1, PCA9685_QUATENARY_ADDRESS), false, 0, RPI_GPIO_4);
#elif CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_DARK
static RCOutput_PCA9685 rcoutDriver(i2c_mgr_instance.get_device(1, PCA9685_QUINARY_ADDRESS), false, 0, RPI_GPIO_27);
#elif CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_ZYNQ || \
     CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_OCPOC_ZYNQ
static RCOutput_ZYNQ rcoutDriver;
#elif CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_BEBOP

@ppoirier is there any chance you still have the arducopter binary you compiled for your project still?

I tried to compile from the Erle fork, but it seems the waf code is broken in their fork

ppoirier · December 13, 2018, 9:16pm

Well. I might try building it , where did you get your RT kernel ?
What cross compiler are you using for the RPI Zero ?