Zero Pilot 3.0 MCU Requirements

• Not connected to zp (on a separate board)

• Pressing a push button will arm the motors

• switches and sticks should be in the right spot to arm (when the button is pressed)

• gpio input

ZeroPilot must have a method to physically Arm/Disarm the aircraft

HIGHMEDIUM LOW

• Buzzer will also be external (on the same board as the arm/disarm switch)

• Buzzer uses a pwm signal to drive tones

ZeroPilot shall have an audible buzzer

• maximum 7 LEDs, minimum 4

• some are different colours

• A colour reserved for power is red

• gpio output

ZeroPilot shall have debugging LED’s of multiple colours

• Voltage monitoring (external ADC)

• Overall voltage (not individual cells)

• nice to have temp monitoring for zeropilot and batteries if there are extra ADC pins

ZeroPilot must have the ability to monitor the battery

• External IMU

  • Vectornav uses UART

  • BMX160 drivers we have is I2C & SPI

• onboard IMU’s probably going to be more popular to get something like an MPU9250 (commonly used for arduinos) instead of bmx160… but mpu9250 is eol? https://invensense.tdk.com/wp-content/uploads/2018/10/AN-000146-v2.0-TDK_Migration_MPU_9250toICM-20948.pdf?

ZeroPilot will have an IMU

• MicroSD Card for data logging

• MicroSD Card for saving model configuration

• MicroSD cards MUST use SPI

• No other external storage

ZeroPilot will have Non-Volatile Data Storage

ZeroPilot will have one microcontroller

• UART based comms (USB UART)

  • CV opens a virtual com port, firmware already has software to do this

ZeroPilot must be able to communicate with other boards on the aircraft

• At least 8 output must support DSHOT

  • DSHOT uses PWM & DMA

  • Consult @Christopher Chung and @Aidan Bowers (Deactivated) Re: clock speeds

• The remaining 4 just support PWM

ZeroPilot will have at least 12 Motor/Servo/Actuator outputs

• @Sahil Kale will deal with the GPS accuracy requirements

  Open

  

• We will have extra of UART, SPI, I2C, GPIO, PWM input

ZeroPilot must be able to communicate with a GPS

• SWO & stlink will handle this

  • We need SWO breakout

• 1 connector (such as ribbon) for programming and data output - No FTDI no Onboard STlink

ZeroPilot will have a debugging output data pipe

• PPM input

• UART upgrade path

ZeroPilot must accept tele-op input

• XBees use UART

• open for future upgrades

ZeroPilot shall have a DataLink to ground

• This is being discussed by electrical

• Reverse polarity protection

• Overvoltage protection (fuse and zener diode)

• For all inputs/output have ESD protection through zener diode

• External and internal power will have separate fuses

The board will have user power input protection

• Locking connectors for key peripherals

• Compatible with jumpers

The board shall have the option to use locking, non-reversible connectors and simple jumpers

• 4 mounting holes?

• Talk to @Steven Wang,@Daniel Puratich (Unlicensed)

ZeroPilot will be possible to place into a case

• This depends on the peripherals that are going to be connected

  • 5v & 3.3v side by side, and the connector will be crimped appropriately

  • each peripheral connection will have 5, 3.3, GND, and appropriate data pins

ZeroPilot will have power outputs for peripheral devices

• 4 GPIO for LEDs (most likely neopixel)

• (High current e.g. 3A per strip) current source could be from an external board or onboard zp

ZeroPilot will have an LED driver

• all sensors will be external and should use common protocols (I2C, SPI, UART, GPIO, PWM)

• extras of all these common protocols (whatever that means for the protocol)

ZeroPilot will have sensor breakouts

• Talk to @Steven Wang , @Daniel Puratich (Unlicensed)

ZeroPilot will have mounting holes that can support anti-vibration mounts

Comms emulator (that can be connected to a PC) will be used instead of this