Skip to the content
2 layers39.9 × 40 mmEnkoder, the printed circuit board in 3D

ROS based UAV (Unmanned Autonomous Vehicle), Master's degree final project

Size
39.9 × 40 mm
Copper layers
2
Thickness
1.6 mm
Parts
21
Nets
23
Pads
72
Tracks, vias
170, 12
Pours
2
Routed
Yes
KiCad
KiCad 5 (file 20171130)
Created
4 Dec 2020
Updated
7 Nov 2021

Overview

Enkoder is an open-source printed circuit board by Tai-Min, from the Tai-Min/Statek-UAV repository on GitHub, published under the MIT licence. It is a 2-layer board of 39.9 × 40 mm with 21 parts on 23 nets, routed with 170 tracks and 12 vias.

Its parts include 9 capacitors, 7 connectors and 1 IC. It belongs with the sensors and measurement and robots and motor control boards of this library.

README

README.md

Statek-UAV

ROS based UAV, Master's degree final project.

This repository consists of CAD files for the chassis, CAD files for electronic boards, catkin workspace for all ROS nodes created for the project and some additional scripts used during development.

The core part of this project is the real, 3D printed vehicle along with all the hardware attached to it (Jetson Nano B01 for main controller and STM32f103RBT6 for real time core).

The software part of this project can be split into real time (closed loop wheel control), short term navigation (movement between two GPS waypoints) and long term navigation (navigation through series of GPS waypoints). During the project's development, my main focus was on short term navigation, which is also the biggest and most complicated part of the project. Short term navigation stack consists of static local map generator, dynamic local map generator (human leg detector mostly based on U-Net fully convolutional neural network), Voronoi graph generator, A* path planner and non linear model predictive controller for navigation.

For more info see this arcitle.

Just to warn you: If you want to use this project somehow, use it as reference only. It is NOT meant to be assembled as it contains some design flaws both in hardware and software that I don't intent to fix in this iteration of the project as code in this repository will stay in unchanged since the moment I handed over my thesis. Most of the files in the "instructions" folder consists of the steps I've did to setup my hardware and Ipopt solver. Those might not work for you/could be dangerous (I might've abused sudo a bit) so use them at your own risk. The code quality depends on the time I had untill the deadline to hand over my thesis. In my opinion it should be fine for the most part, well documented and easy to follow but judge for yourself.

Disclaimer: I've tried to credit all authors of 3D files used in the project. All of the models had permissive license allowing me to use them. If you see your work here without being credited or you just don't want to have your files used here - open an issue on this project and I'll fix any problems.

The files in this folder have the following structure:

  • CAD
    • detailed - Inventor files for the 3D printing and assembling.
    • low_poly - Inventor files for simple low poly model for Gazebo and Rviz.
  • catkin_ws/src
    • statek - Metapackage for the project
    • statek_calibrate - Calibration algorithms for cameras, GPS Kalman filter, IMU, Motor's PI controller autotuning.
    • statek_config - Config files for the robot, including transformations, urdf and parameters for ROS nodes.
    • statek_hw - code to launch hardware based nodes (lidar, rosserial, cameras etc.) along with source code for real time controller.
    • statek_map - Mapping algorithms (dynamic local mapper, voronoi generator and GPS to hyperplane casting).
    • statek_ml - Leg detector based mostly on U-net fully convolutional neural network
    • statek_nav - Navigation algorithms (NMPC and GPS waypoint follower script).
    • statek_plan - A* path planner for short term navigation.
    • statek_playground - Simple launch nodes to play with the hardware.
    • statek_rviz - Rviz visualization files.
    • statek_sim - Gazebo simulation files.
    • statek_srv - Server files to communicate with web application (really rough draft).
    • statek_teleop - Teleoperation nodes for Dualshock 4 gamepad.
  • electronics
    • AM4096_encoder - KiCad's files for AM4096 encoder board.
    • Nucleo_screw_shield - KiCad's files for screw shield that fits morpho connector.
    • button_panel - Unused in the project.
    • connections - Electrical connections of the project.
  • instructions - Rough draft of what I did to setup the robot.
  • media - Contains camera's calibration chessboard.
  • thesis_scripts - Some files used to add more value to the project.

alt text

Parts

21
QtyValueFootprintReferences
4100nCapacitor_SMD:C_1206_3216Metric_Pad1.42x1.75mm_HandSolderC1, C5, C6, C8
4MountingHole_3.2mm_M3_ISO7380_PadMountingHole:MountingHole_3.2mm_M3_ISO7380_Pad , , ,
32.2uCapacitor_Tantalum_SMD:CP_EIA-3216-18_Kemet-A_Pad1.58x1.35mm_HandSolderC3, C7, C9
210nCapacitor_SMD:C_1206_3216Metric_Pad1.42x1.75mm_HandSolderC2, C4
2Conn_01x02Connector_PinSocket_2.54mm:PinSocket_1x02_P2.54mm_VerticalJ5, J7
2Conn_01x03Connector_PinSocket_2.54mm:PinSocket_1x03_P2.54mm_VerticalJ3, J6
2Conn_01x04Connector_PinSocket_2.54mm:PinSocket_1x04_P2.54mm_VerticalJ1, J4
1Conn_01x04TerminalBlock_MetzConnect:TerminalBlock_MetzConnect_Type086_RT03404HBLC_1x04_P3.81mm_HorizontalJ2
1am4096Package_SO:SSOP-28_5.3x10.2mm_P0.65mmU1

More from Tai-Min/Statek-UAV

2
  • 2 layers91 × 95.3 mmScrew connector, the printed circuit board in 3D

    Screw connector

    Tai-Min/Statek-UAV

    ROS based UAV (Unmanned Autonomous Vehicle), Master's degree final project

    642 parts6MIT
  • 2 layers92.5 × 41.3 mmButton panel, the printed circuit board in 3D

    Button panel

    Tai-Min/Statek-UAV

    ROS based UAV (Unmanned Autonomous Vehicle), Master's degree final project

    36 parts6MIT

Similar boards

  • 2 layers28.3 × 39.8 mmLevelShifter, the printed circuit board in 3D

    LevelShifter

    gusmanb/logicanalyzer

    24 channel, 100Msps logic analyzer hardware and software

    21 parts5.1kGPL-3.0
  • 2 layers171.2 × 72.9 mmAmiga gfxcard before pour, the printed circuit board in 3D

    Amiga gfxcard before pour

    mntmn/amiga2000-gfxcard

    MNT VA2000, an Open Source Amiga 2/3/4000 Graphics Card (Zorro II/III), written in Verilog

    21 parts1k
  • 2 layers93.9 × 46 mmRectifier, the printed circuit board in 3D

    Rectifier

    rene-dev/stmbl

    AC Servo Driver for STM32F4

    21 parts990GPL-3.0
  • 2 layers45.5 × 42.9 mmEsphome han reader, the printed circuit board in 3D

    Esphome han reader

    hackclub/OnBoard

    💡 Join 1,000 teenagers and make your first PCB with a $100 grant!

    21 parts915
  • 2 layers31.8 × 14.5 mmEsp prog, the printed circuit board in 3D

    Esp prog

    drandyhaas/KiCadRoutingTools

    A set of Python/Rust tools to aid routing in KiCad

    21 parts744MIT
  • 2 layers23.5 × 15.8 mmQuiverAttachPCB, the printed circuit board in 3D

    QuiverAttachPCB

    Arrow-air/project-quiver

    Project Quiver documentation, designs, and project artifacts.

    21 parts617CERN-OHL-S-2.0
  • 2 layers69.9 × 41.3 mmHeaterMeterLCD, the printed circuit board in 3D

    HeaterMeterLCD

    CapnBry/HeaterMeter

    HeaterMeter and LinkMeter Arduino BBQ Controller

    21 parts557MIT
  • 2 layers161.3 × 111.8 mmDoj, the printed circuit board in 3D

    Doj

    kelu124/echomods

    Open source ultrasound processing modules and building blocks

    21 parts463

Questions

How big is the Enkoder PCB?

It measures 39.9 × 40 mm and has 2 copper layers, 1.6 mm thick.

What parts does the Enkoder use?

21 parts. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.

Where can I download the Enkoder KiCad files?

From the Tai-Min/Statek-UAV repository on GitHub, at the commit this page was made from: the board is electronics/AM4096_encoder/enkoder.kicad_pcb. PCBKit opens the board in the browser, with nothing to install.

Can I use the Enkoder design in my own project?

Its repository publishes it under the MIT licence: you may reuse it on that licence's terms (keep the author's notice, and for a copyleft licence share your changes alike).