Skip to the content
2 layers14.5 × 11.9 mmMic board, the printed circuit board in 3D

Robot project for the Embedded Software Project [521275A] and Software Project [521479S]

Size
14.5 × 11.9 mm
Copper layers
2
Thickness
1.6 mm
Parts
4
Nets
4
Pads
11
Tracks, vias
9, 2
Pours
1
Routed
Yes
KiCad
KiCad 7 (file 20221018)
Created
14 Jan 2020
Updated
4 Nov 2026

Overview

Mic board is an open-source printed circuit board by ouspg, from the ouspg/SOP-Robot repository on GitHub. It is a 2-layer board of 14.5 × 11.9 mm with 4 parts on 4 nets, routed with 9 tracks and 2 vias.

Its parts include 2 capacitors and 1 connector. It belongs with the robots and motor control boards of this library.

README

README.md

Getting started

The robot uses ROS2 (Robot Operating System 2). Read the ROS2 wiki!. Tutorials and how-to guides are worth to check.

Read also controller documentation to understand why certain controllers are needed and how they control the motion. Here are ros2 control demo repositories and more documentation about controllers.

Quick start

SOP-Robot uses Pixi to install ROS 2 Humble, Python packages, and build tools into a local .pixi/ environment.

console
sudo apt update
sudo apt install -y git curl espeak
curl -fsSL https://pixi.sh/install.sh | bash
git clone --recurse-submodules https://github.com/ouspg/SOP-Robot.git
cd SOP-Robot
pixi run setup-runtime
pixi run build
pixi run robot-fake

Setting up Lehmus AI api key:

console
cp .env.example .env.local
code
LLM_API_KEY=your lehmus ai api key goes here

For real Dynamixel hardware, install the U2D2 udev rule once:

console
pixi run setup-udev

The launch tasks source install/local_setup.bash for you. If you enter pixi shell for manual ROS commands, source the overlay first:

console
source install/local_setup.bash

Launch the complete demo from one terminal with pixi run robot-demo-fake for simulation or pixi run robot-demo-real for real hardware. Press Ctrl+C in that terminal to stop the stack. See Robot bring-up for individual components and logging options.

The Robot

The robot uses dynamixel servos. Servos are controlled via the robot_hardware ROS node, which implements the hardware interface for ros2_control. robot package contains the servo controller configurations for the robot. See robot.yaml, for example. The head supports joint_trajectory_controller. When using this controller, joints can be controlled by sending action messages to the trajectory controller. See bring up for an example of action message.

Joint -> Servo mappings are defined in two files. Configuration file connects servo ID with certain joint. dynamixel_arm.yaml is for servos of robot arm and dynamixel_head.yaml for servos of head.

Project structure

  • client - contains client to send actions for robot hand
  • config - dynamixel servo configuration
  • src - all packages
    • src/face_tracker - tracks the faces using camera feed and calculates locations and distances of faces and detects mouth movement.
    • src/inmoov_description - robot files, which define the robot geometry and configuration for simulation (URDF, SRDF & rviz configuration)
    • src/robot - robot launch files & servo controller configurations
    • src/robot_hardware - hardware interface for ros2_controller, communicates with U2D2 via dynamixel workbench
    • src/tts_package - Text-to-speech package for finnish speech synthesis
    • src/sst_package - Speech-to-text package for finnish speech recognition
    • src/llm_package - OpenAI client package used for using llm model with Lehmus AI API
    • src/unified_arms- unified node for controlling arms thought serial and hands with topics
    • src/full_demo - Main control node for the robot

While the robot is idle, full_demo_node selects an arm action every 120 seconds by default: a randomized arm-and-hand action 70% of the time, or one of wave, rock, rotate, and swingarms 30% of the time. The random action is implemented by unified_arms_node and runs for 40-60 seconds using the original randomized joint ranges. It does not command the head. The interval can be changed with the random_gesture_interval parameter on full_demo_node.

Servo Table

Note: Servos can be configured using Dynamixel Wizard 2.0

Baud rate: 57600, Voltage: 7.5

Note: You can use Dynamixel Wizard 2.0 to check that servos have enough voltage to operate normally.

Servo IDModelJoint nameDescription
1XL430head_tilt_right_jointHead tilt right-side
2XL430head_tilt_vertical_jointHead tilt up/down
3XL430head_tilt_left_jointHead tilt left-side
4XL430head_pan_jointHead turn left/right
9XL320eyes_shift_horizontal_jointEyes shift left/right
11XL320eyes_shift_vertical_jointEyes shift up/down
12XL320head_jaw_jointOpen/close jaw
31XL320r_thumb_jointOpen/close thumb
34XL320r_index1_jointOpen/close index
37XL320r_middle1_jointOpen/close middle
40XL320r_ring_jointOpen/close ring
44XL320r_pinky_jointOpen/close pinky
47XL320unnamed jointRotate wrist

Cautions

Note: head tilt range of motion is poor

Note: wrist joint seems to overload very easily

  • Reason for this detected during inspection of the mechanical assembly. The hand is installed wrong way to the wrist.

Note: servo angle limits are not configured

Note: Be careful not to move joints too much, limits are not set yet

Next steps

  1. See Development
  2. See Robot bring-up

Parts

4
QtyValueFootprintReferences
2C_1206fab:C_1206C1, C2
1Conn_PinHeader_1x03_P2.54mm_Horizontal_SMDfab:PinHeader_1x03_P2.54mm_Vertical_THT_D1mmJ1
1Mic_MEMS_Analog_SPU0414HR5Hfab:Mic_MEMS_Analog_Knowles_SPU0414HR5HMK1

More from ouspg/SOP-Robot

1
  • 2 layers52.6 × 25.9 mmPreampV3, the printed circuit board in 3D

    PreampV3

    ouspg/SOP-Robot

    Robot project for the Embedded Software Project [521275A] and Software Project [521479S]

    18 parts5

Similar boards

  • 2 layers18.5 × 26 mm24g2usb rp2350zero, the printed circuit board in 3D

    24g2usb rp2350zero

    joypad-ai/joypad-os

    Universal controller firmware for building adapters, dongles, and custom controllers.

    4 parts1.7kApache-2.0
  • 2 layers116 × 33 mm966595-1 and 963356-1, the printed circuit board in 3D

    966595-1 and 963356-1

    rusefi/rusefi

    rusefi - GPL internal combustion engine control unit

    4 parts1.2k
  • 2 layers19 × 18 mmDaughter board, the printed circuit board in 3D

    Daughter board

    hackclub/OnBoard

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

    4 parts915
  • 2 layers24.8 × 24.8 mmNrf24 breakout, the printed circuit board in 3D

    Nrf24 breakout

    tardate/LittleArduinoProjects

    a collection of "Little Electronic & Arduino Projects", most involving electronics or an Arduino in one way or another!

    4 parts803MIT
  • 2 layers26 × 20 mmCap chain, the printed circuit board in 3D

    Cap chain

    drandyhaas/KiCadRoutingTools

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

    4 parts744MIT
  • 2 layers34.7 × 20 mmXG Station Power MSI, the printed circuit board in 3D

    XG Station Power MSI

    osy/XG_Mobile_Station

    Open source eGPU dock for ROG Ally and ROG Flow

    4 parts712CC-BY-4.0
  • 2 layers20.3 × 24.5 mmJack power input, the printed circuit board in 3D

    Jack power input

    Luos-io/luos_engine

    Open-source and real-time orchestrator for cyber-physical-systems, to easily design, test and deploy embedded applications and digital twins.

    4 parts546MIT

Questions

How big is the Mic board PCB?

It measures 14.5 × 11.9 mm and has 2 copper layers, 1.6 mm thick.

What parts does the Mic board use?

4 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 Mic board KiCad files?

From the ouspg/SOP-Robot repository on GitHub, at the commit this page was made from: the board is 3d_models/microphone_and_preamp/CAD_files/mic_board/mic_board.kicad_pcb and its schematic 3d_models/microphone_and_preamp/CAD_files/mic_board/mic_board.kicad_sch. PCBKit opens the board in the browser, with nothing to install.

Can I use the Mic board design in my own project?

Its repository states no licence, so its author keeps all rights: ask ouspg before reusing the design.