Skip to the content
4 layers150 × 100 mmCm4-robo controller, the printed circuit board in 3D

Satellite dish controller using a ROBOCLAW-2X15A-OEM controlled by a Raspberry Pi CM4 module. Powered by DC battery.

Size
150 × 100 mm
Copper layers
4
Thickness
1.6 mm
Parts
292
Nets
313
Pads
1,133
Tracks, vias
2,073, 924
Pours
35
Routed
Yes
KiCad
KiCad 10.0 (file 20260206)
Created
9 Oct 2026
Updated
6 Nov 2026

Overview

Cm4-robo controller is an open-source printed circuit board by jrseti, from the jrseti/roboclaw-cm4-dc-dish-controller repository on GitHub, published under the MIT licence. It is a 4-layer board of 150 × 100 mm with 292 parts on 313 nets, routed with 2,073 tracks and 924 vias.

It is built around the 74LVC1G07SE-7-MS, TPD4EUSB30DQAR and CL21B106KPQNNNE, with the CC0603KRX7R9BB104, 0402B103K500CT and TPESD0402G12V among its other parts. Its parts include 86 resistors, 75 capacitors, 22 diodes, 22 connectors and 11 ICs. It belongs with the computers and single-board computers and power boards of this library.

Main components

12

README

README.md

roboclaw-cm4-dc-dish-controller

A satellite dish controller board in the form of a carrier board for a Raspberry Pi Compute Module 4 (CM4) which commands a Basicmicro RoboClaw 2x15A OEM motor controller. Drives the dish's azimuth and elevation motors. The board runs from a 12.8 V LiFePO4 battery.

Schematic: kicad/cm4-robo-controller.pdf

Simulations: sim/README.md

Tomachie AI reviewed the schematic. Here is the Certificate of Accomplishment. Scored 97/100 (which I think is pretty good).

3D render of the controller PCB

Overview

The board combines two modules:

  • Raspberry Pi CM4: runs the pointing software and provides networking, USB, GPS timing and spare I/O. It plugs into two Hirose mezzanine connectors in the middle of the board.
  • RoboClaw 2x15A OEM: a dual-channel brushed DC motor controller with closed-loop position and speed control. It plugs into two pin-header sockets on the right of the board. The CM4 sends it commands over a TTL serial link (RoboClaw packet serial).

The CM4 decides where the dish should point. The RoboClaw reads the axis sensors and runs the motor control loops.

Functional diagram

The functional diagram shows the board's layout: the CM4 on the left, the RoboClaw on the right, and the field connections along the edges. Its source is drawings/FunctionalDiagram.drawio.

Motors and axis sensing

AxisMotorPosition sensorRoboClaw input
Elevation (M1)Firgelli F-SD-H-450-12V linear actuator (5.5 A max, 450 lb)Built-in Hall sensors, quadrature A/BEN1 (J8)
Azimuth (M2)Bringsmart JGY-370 12 V worm-gear motor (1.8 A max)AS5600 magnetic angle sensor, analog outputEN2 (J9)

Both encoder channels are identical and jumper-configurable, so either axis can use a quadrature encoder (the Firgelli Hall sensors, or an Omron E6B2-CWZ6C open-collector encoder) or an absolute analog encoder (0–2 V at the RoboClaw). Each 4-pin connector carries V+, A (or the analog signal), B and GND, with ESD clamps on both signals.

Jumper (ENC1 / ENC2)ShuntSetting
JP1 / JP4 — sensor supply (2x3, shunt across a row)1-25 V from the RoboClaw BEC (RC_5V)
3-43.3 V from the on-board LDO U18 (ENC_3V3)
5-6Battery voltage, 10–14.6 V (ENC_12V: V_MOTOR via a 250 mA PTC, SMAJ20A clamp), e.g. for an E6B2-CWZ6C
JP2 / JP5 — mode (2x3)1-3 + 2-4QUAD: A gets a 1k pull-up to 5 V and a 100R/10nF filter; B always does
3-5 + 4-6ABS: A goes to the analog node (100k/100nF); the pull-up is disconnected
JP3 / JP6 — ABS scaling1-268k/100k divider (×0.6) for a 3.3 V sensor such as the AS5600
2-31k series, for a source that already outputs 0–2 V

Default fit: ENC1 = 5 V, QUAD (Firgelli); ENC2 = 3.3 V, ABS, 3.3 V scaling (AS5600).

docs/encoder-inputs.md explains, part by part, how the channel handles each encoder type: the E6B2-CWZ6C's NPN open-collector outputs, the Firgelli Hall quadrature, and an absolute 0–2 V encoder such as the AS5600.

Elevation: Firgelli F-SD-H-450 linear actuatorAzimuth: Bringsmart JGY-370 worm-gear motor
Firgelli F-SD-H-450 linear actuatorBringsmart JGY-370 worm-gear motor
  • Elevation: the actuator's Hall outputs (J8, JP2 in QUAD) are pulled up to the sensor supply (JP1 = 5 V), ESD-protected and RC-filtered before they reach EN1. The count is incremental, so the axis is homed at start-up.
  • Azimuth: the AS5600 (J9, JP5 in ABS) gives an absolute angle as a 0–3.3 V signal. The 68k/100k divider (JP6 1-2) scales it to the RoboClaw's 0–2 V absolute-encoder input, so no homing is needed.
  • Switch inputs: E-stop (J10 → S3), elevation limit (J12 → S4) and azimuth limit (J13 → S5). All use normally-closed switches and have ESD protection and filtering. The RoboClaw has one limit input per motor but supports two switches on it: wire the forward and reverse NC switches in series on J12/J13 (either one opening trips the input), set Invert, and set S4/S5 to Limit (Both) or Home (User)/Limit (Fwd) — the latter also zeroes the encoder against the reverse-end switch, which is how the elevation axis homes. All three switch loops run at battery voltage (ENC_12V, 4.7k pull-up, about 2.6 mA through the contacts for wetting on long cables) and a 47k/20k divider brings the open-switch 10–14.6 V down to 3.0–4.4 V at the RoboClaw pins.
  • Motor outputs: J11 and J14, both 7.62 mm screw terminals.

The Motor Notes schematic sheet describes the sensor wiring and RoboClaw setup in detail.

Power

GoldenMate CRIUS12 12.8 V 12 Ah LiFePO4 battery
  • Input: a 12.8 V, 12 Ah LiFePO4 battery (10.0–14.6 V) on J1, a 7.62 mm screw terminal. The battery is a GoldenMate CRIUS12, IP67 rated, and sits inside the enclosure. Its manual is in docs/.

  • Reverse-polarity protection: a P-channel MOSFET (Q1) on the input blocks a battery connected backwards. It still conducts in both directions in normal use, so motor regenerative braking can return energy to the battery.

  • Fuses: two ATO blade fuses split the supply:

    • F1 (15 A) feeds the RoboClaw motor supply (V_MOTOR).
    • F2 (5 A) feeds the logic branch.
    5 A ATO automotive blade fuse

    These are ordinary automotive blade fuses, the kind sold for car wiring. They are cheap and available almost anywhere. They plug into Keystone 3557-2 holders, so a blown fuse can be replaced in the field without tools. The board uses Littelfuse 0287005.PXCN (5 A) and 0287015.PXCN (15 A), but any ATO/ATC fuse of the same rating fits.

    Q1 is the main protection against a reversed battery. A healthy Q1 blocks the reverse voltage, and no fuse should blow. The fuses are the backup. If Q1 has failed shorted, the reversed battery drives current forward through the input TVS diodes (D1, D3) and the RoboClaw's internal diodes. That current passes through F1 and F2, and the fuses are what stop it. A blown fuse after connecting the battery therefore means: check the polarity, and check Q1, before you fit a new fuse.

    The fuses do not cover every reverse fault. If board ground is also connected to the battery's negative terminal by another route, such as a USB device or other equipment that shares the battery, reverse current can flow through the ground wiring and bypass both Q1 and the fuses.

  • Logic supply: the logic branch goes through a hot-swap eFuse (U11), a power switch (SW1) and a 5 A buck converter (U15). The buck makes 5 V for the CM4 and the USB ports. The CM4's own 3.3 V output powers the 3.3 V logic.

  • SW1 is not a battery disconnect. It switches the CM4 and logic supply only. With SW1 off the board still draws about 31 mA from the battery: about 30 mA for the RoboClaw's logic, which runs straight from V_MOTOR, plus about 1.3 mA for U11 and its dividers. A full 12 Ah battery runs flat in about 16 days. For storage or transport, unplug J1 (or pull F1 and F2), and charge the battery first. A LiFePO4 battery left at its BMS cutoff for months loses capacity.

  • Grounding:

    • Motor return current stays on a separate ground (PGND). It joins the logic ground at a single point (NT1) next to the battery terminal.
    • Connector shields and mounting holes go to CHASSIS, which is bled to ground through 1 MΩ in parallel with 4.7 nF.

CM4 interfaces

  • Ethernet: gigabit RJ45 with integrated magnetics. The PHY is on the CM4.
  • USB:
    • A USB2514B hub drives a dual USB-A port, with current limiting and ESD protection. The hub's ports 3 and 4 are not used and are disabled by strap.
    • A USB mux switches the CM4's USB port to the USB-C connector for rpiboot (OTG programming of the eMMC).
  • GPS:
    • A u-blox MAX-M10S receiver provides UTC time and a 1PPS pulse. Its antenna connects to an SMA jack, and a coin cell backs up the receiver for fast restarts.
    • A second SMA input accepts an external 1PPS reference, such as an FE-5680A rubidium clock.
  • GPIO header (J4): spare CM4 GPIOs and two protected analog inputs. Two on-axis E6B2-CWZ6C encoders can be read here, see On-axis encoders on J4. H7, an M2.5 hole next to J4, secures a plug-on HAT board; see Mounting a HAT board on J4.
  • Jumpers: boot control, EEPROM write protect and self power-cycle.
  • Boot console UART (J5): a serial console on the CM4's UART0. See below.

Boot console UART (J5)

J5 is a 3-pin, 2.54 mm header that brings out the CM4's UART0. It shows bootloader and Linux boot messages and gives a login prompt. That makes it the way into the board when the network is down or the CM4 won't boot.

J5 pinSignalConnect to the adapter's
1BOOT_CONSOLE_RXD (GPIO15, CM4 receives)TXD
2BOOT_CONSOLE_TXD (GPIO14, CM4 transmits)RXD
3GNDGND

TX and RX cross over: the adapter's TXD goes to the CM4's RXD.

USB to TTL serial cable with four female jumper leads

Any inexpensive USB-to-TTL serial cable works. Cables like the one shown, based on the PL2303, CP2102 or FTDI chips, cost a few dollars on Amazon. They usually have four female jumper leads: black GND, white RXD, green TXD and red 5V. Check the labels on your cable.

  • Do not connect the red 5V lead. The board powers itself, and J5 has no 5 V pin. A loose 5 V lead can short against the header or the board, so it's best to cut it off, or at least insulate it.
  • Use a cable with 3.3 V signals. The CM4's GPIOs are not 5 V tolerant. Before connecting, check with a meter that the adapter's TXD idles at about 3.3 V.
  • Settings: 115200 baud, 8N1, no flow control.
  • Enabling the console:
    • For the Linux console, add enable_uart=1 to config.txt. Raspberry Pi OS already puts console=serial0,115200 in cmdline.txt.
    • For bootloader messages, set BOOT_UART=1 in the EEPROM config with rpi-eeprom-config.

Recommended CM4

Use a CM4 without wireless and with eMMC, for example CM4004032 (4 GB RAM, 32 GB eMMC) or CM4004016 (16 GB eMMC).

  • The board has no SD-card slot, so a CM4 Lite (part numbers ending 000) cannot boot on it.
  • On a wireless CM4, Bluetooth takes UART0, which this board uses.

Board

  • 4-layer PCB, 150 × 90 mm, with four M3 mounting holes.
  • Assembled on one side by JLCPCB. Parts carry LCSC part numbers. The RoboClaw (A1) and the CM4 (A2) are DNP: bought separately and fitted by hand. The two Hirose DF40 receptacles under the CM4 are J17/J18, BOM and placement entries only, since their pads are part of the CM4 footprint.
  • The RoboClaw sits in sockets (J15/J16) so it can be removed. Nothing is placed under the CM4 or the RoboClaw.
  • The inner layers are planes:
    • In1.Cu is ground, split into logic GND and PGND.
    • In2.Cu carries power: +5 V on the logic side, V_MOTOR on the RoboClaw side.

Status

The schematic is complete. PCB placement and plane layout are done, and routing is in progress. The software has not been started yet.

Repository layout

PathContents
kicad/KiCad 10 project: schematic sheets and PCB
parts/Git submodule (jrseti/parts): the MyParts symbol, footprint and 3D-model library, its datasheets, and add.py for importing LCSC parts
docs/Component datasheets and design notes
drawings/Draw.io source for the functional diagram
images/Images used in this README
software/CM4 software (not yet started)

Cloning

parts/ is a submodule, and the KiCad project needs it to find its symbols, footprints and 3D models. Clone with:

sh
git clone --recurse-submodules https://github.com/jrseti/roboclaw-cm4-dc-dish-controller.git

If you have already cloned the repository, run git submodule update --init to fetch it.

KiCad finds the library through two path variables. Set them in Preferences → Configure Paths:

VariableValue
MYPARTS<clone>/parts
MYPARTS_DATASHEETS<clone>/parts/datasheets

License

MIT. See LICENSE.

Parts

292
QtyValueFootprintReferences
23TestPoint_SmallMyParts:TestPoint_Pad_D0.8mmTP1, TP2, TP10, TP14, TP15, TP16, TP17, TP18, TP19, TP21, TP23, TP25, TP26, TP27, TP28, TP29 +7
21100nFMyPartsIPC:CAPC1005X55NC2, C6, C15, C16, C17, C18, C19, C20, C21, C23, C29, C40, C62, C63, C64, C66 +5
1810uFMyPartsIPC:CAPC2012X145NC5, C10, C11, C12, C13, C14, C38, C41, C42, C43, C44, C48, C49, C50, C51, C52 +2
11100ΩMyPartsIPC:RESC1005X40NR4, R5, R33, R35, R37, R45, R46, R49, R53, R103, R106
1110kΩMyPartsIPC:RESC1005X40NR6, R7, R8, R16, R60, R64, R66, R94, R95, R96, R97
8100nFMyPartsIPC:CAPC1608X95NC24, C25, C27, C31, C34, C35, C39, C47
710nFMyPartsIPC:CAPC1005X55NC57, C58, C59, C60, C61, C87, C88
71kΩMyPartsIPC:RESC1005X40NR34, R47, R51, R100, R102, R104, R105
6Header-Male-2.54_2x3MyParts:HDR-TH_6P-P2.54-V-M-R2-C3-S2.54-1J3, J6, JP1, JP2, JP4, JP5
510kΩMyPartsIPC:RESC1608X55NR24, R25, R31, R36, R93
52.2kΩMyPartsIPC:RESC1005X40NR20, R21, R44, R59, R61
5TPESD0402G12VMyPartsIPC:DIOC1005X55ND13, D16, D18, D22, D27
410uFMyPartsIPC:CAPC1608X95NC33, C65, C81, C89
420kΩMyPartsIPC:RESC1005X40NR43, R107, R108, R109
436kΩMyPartsIPC:RESC1005X40NR12, R13, R14, R15
447kΩMyPartsIPC:RESC1005X40NR1, R50, R54, R56
474LVC1G17SE-7MyPartsIPC:SOT65P210X110-5NU13, U14, U16, U19
4M3MountingHole:MountingHole_3.2mm_M3_Pad_ViaH1, H2, H3, H4
4TPD4EUSB30DQARMyPartsIPC:SON50P100X250X60-10NU5, U6, U8, U9
3100kΩMyPartsIPC:RESC1005X40NR58, R65, R101
31uFMyPartsIPC:CAPC1608X95NC30, C32, C80
3220ΩMyPartsIPC:RESC1005X40NR18, R19, R39
34.7kΩMyPartsIPC:RESC1608X55NR48, R52, R55
374LVC1G07SE-7MyPartsIPC:SOT65P210X110-5NU1, U10, U17
3Header-Male-2.54_1x3MyParts:HDR-TH_3P-P2.54-V-M-1J5, JP3, JP6
3KF2EDGR-2.54-2PMyParts:CONN-TH_P2.54_KF2EDGR-2.54-2PJ10, J12, J13
3KF7620-7.62-2PMyParts:CONN-TH_P7.62_KF7620-7.62-2PJ1, J11, J14
3SMF6.0AMyPartsIPC:SODFL3718X110ND8, D21, D24
3TPESD0402G15VMyPartsIPC:DIOC1005X55ND17, D19, D20
21.5kΩMyPartsIPC:RESC1005X40NR3, R9
2100kΩMyPartsIPC:RESC1608X55NR11, R38
2100uFMyPartsIPC:CAPMP7343X310NC7, C45
212kΩMyPartsIPC:RESC1005X40NR10, R42
213kΩMyPartsIPC:RESC1608X55NR26, R30
215pFMyPartsIPC:CAPC1005X55NC3, C4
222ΩMyPartsIPC:RESC1005X40NR69, R70
233kΩMyPartsIPC:RESC1608X55NR22, R91
25.1kΩMyPartsIPC:RESC1005X40NR62, R63
268kΩMyPartsIPC:RESC1005X40NR57, R99
2BAT54SMyPartsIPC:SOT95P280X110-3ND4, D5
2DF40C-100DS-0.4V(51)MyParts:DF40C-100DS-0.4V_BOM-ONLYJ17, J18
2GREENMyPartsIPC:LEDC2012X110NLED1, LED3
2KF2EDGR-2.54-4PMyParts:CONN-TH_4P-P2.54_KF2EDGR-2.54-4PJ8, J9
2SMA-KWE_C7498154MyParts:SMA-TH_SMA-KWE_C7498154J2, J7
2SMAJ20AMyPartsIPC:DIOM5226X244ND11, D28
2SMCJ18A_C53260906MyPartsIPC:DIOM7959X262ND1, D3
2TPESD0402G05VMyPartsIPC:DIOC1005X55ND25, D26
11.2nFMyPartsIPC:CAPC1005X55NC56
1100mAMyPartsIPC:FUSC3216X110NF3
110nFMyPartsIPC:CAPC1608X95NC37
110uFMyPartsIPC:CAPC3216X180NC26
110ΩMyPartsIPC:RESC3216X70NR41
1120Ω@100MHzMyPartsIPC:INDC3216X130NFB1
1120Ω@100MHzMyPartsIPC:INDC1608X95NFB2
112VMyParts:TESTPOINT-SMD_L3.0-W2.0TP12
115AMyParts:FUSE-TH_4P-L19.8-W6.7_3557-2F1
115kΩMyPartsIPC:RESC1005X40NR17
1174kΩMyPartsIPC:RESC1005X40NR98
1180kΩMyPartsIPC:RESC1608X55NR27
11MΩMyPartsIPC:RESC3216X70NR2
11N4148WS T4MyPartsIPC:SOD2513X110ND12
1210S-1*2P L=11.6MMGold-plated blackMyParts:HDR-TH_2P-P2.54-V-M-1H5
1220uFMyPartsIPC:CAPAE660X770NC28
124MHzMyParts:CRYSTAL-SMD_4P-L3.2-W2.5-BLX1
1250mAMyPartsIPC:FUSC3216X110NF4
12541WV-2X12PMyParts:HDR-TH_24P-P2.54-V-M-R2-C12-S2.54J4
127nHMyPartsIPC:INDC1005X55NL1
13.3uHMyPartsIPC:INDM7366X280NL2
1330kΩMyPartsIPC:RESC1608X55NR29
1330ΩMyPartsIPC:RESC1608X55NR92
133pFMyPartsIPC:CAPC1005X55NC55
133ΩMyPartsIPC:RESC6332X70NR40
13KΩMyPartsIPC:RESC1608X55NR23
14.7nFMyPartsIPC:CAPC3216X180NC1
14.7uFMyPartsIPC:CAPC1005X55NC22
1470pFMyPartsIPC:CAPC1005X55NC46
147nFMyPartsIPC:CAPC1608X95NC82
147pFMyPartsIPC:CAPC1608X95NC36
156kΩMyPartsIPC:RESC1608X55NR32
15AMyParts:FUSE-TH_4P-L19.8-W6.7_3557-2F2

The 254 most common of 292 parts.

Similar boards

  • 4 layers140 × 100 mmRcm dish controller, the printed circuit board in 3D

    Rcm dish controller

    jrseti/Dish

    Simple controller with toggle switches to move the dish motors

    314 partsCC0-1.0
  • 2 layers66 × 44 mmFgl g1, the printed circuit board in 3D

    Fgl g1

    roblim/fused_glass_lighting

    46 parts
  • 6 layers80 × 20 mmPoe usb hid bridge rev4e, the printed circuit board in 3D

    Poe usb hid bridge rev4e

    sire234/VatPoeToUsb

    Ein Gerät, das über ein Ethernet-Kabel mit PoE (IEEE 802.3af) gespeist wird und an einem USB-A-Host-Port ein HID-Gerät (Tastatur, Barcode-Scanner, Maus) betreibt. Die HID-Daten stellt die Firmware über Ethernet bereit.

    85 parts
  • 6 layers128 × 91 mmMythra hub, the printed circuit board in 3D

    Mythra hub

    bad-alloc-heavy-industries/Mythra

    259 parts7BSD-3-Clause
  • 4 layers24.6 × 33.1 mmPower supply2, the printed circuit board in 3D

    Power supply2

    jrseti/dishy1pi

    Satellite dish motor control for Raspberry Pi, hardware and software

    21 partsMIT
  • 4 layers100 × 100 mmPCBA BU16, the printed circuit board in 3D

    PCBA BU16

    intechstudio/grid-hardware

    292 parts59GPL-3.0
  • 4 layers100 × 100 mmLabathome pcb, the printed circuit board in 3D

    Labathome pcb

    klaus-liebler/labathome

    Der kleine Bruder von lab@home. Ermöglicht das Experimentieren mit PT1...PTn-Gliedern, die intern als RC-Kombination (entkoppelt über Operationsverstärker) ausgeführt sind.

    292 parts5MIT

Questions

How big is the Cm4-robo controller PCB?

It measures 150 × 100 mm and has 4 copper layers, 1.6 mm thick.

What parts does the Cm4-robo controller use?

292 parts, built around the 74LVC1G07SE-7-MS, TPD4EUSB30DQAR, CL21B106KPQNNNE and CC0603KRX7R9BB104. 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 Cm4-robo controller KiCad files?

From the jrseti/roboclaw-cm4-dc-dish-controller repository on GitHub, at the commit this page was made from: the board is kicad/cm4-robo-controller.kicad_pcb and its schematic kicad/RCM4.kicad_sch. PCBKit opens the board in the browser, with nothing to install.

Can I use the Cm4-robo controller 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).