KiCad project for the replacement controller: an ESP32 DevKit, six Pololu DRV8874 carriers and a DROK mini 5 V buck module plug into a master board, and the robot's DD-50 cable plugs straight into the board edge.
Scorbot controller is an open-source printed circuit board by ColumbiaGadgetWorks, from the ColumbiaGadgetWorks/scorbot repository on GitHub. It is a 2-layer board of 185 × 128 mm with 102 parts on 81 nets, routed with 1,477 tracks and 319 vias.
It is built around the SS14. Its parts include 43 resistors, 29 capacitors, 11 ICs, 7 diodes and 7 connectors. It belongs with the ESP32 boards of this library.
KiCad project for the replacement controller: an ESP32 DevKit, six Pololu
DRV8874 carriers and a DROK mini 5 V buck module plug into a master board,
and the robot's DD-50 cable plugs straight into the board edge. JLCPCB
places the SMD parts: passives, LEDs, the SS14, the TCA9555 I/O expander and
two ADS1115 ADCs.
Status: v0.4, generated: schematic complete, carrier and DD-50 footprints checked against their datasheets, PCB autorouted. Ready to order; check part orientation in JLC's preview.
Single source of truth: every part, footprint, pin-to-net map and placement
generate.sh
Regenerates everything from design.py, then checks it
Regenerating
sh
pip install kiutils cairosvg # plus KiCad 7+ (kicad-cli and its pcbnew Python module)# optional autorouting: Java 17+, xvfb-run and the Freerouting 1.9.0 jar# (https://github.com/freerouting/freerouting/releases/tag/v1.9.0)
FREEROUTING_JAR=/path/freerouting-1.9.0.jar ./generate.sh
Routing takes about 3 minutes. gen_route.py retries up to FREEROUTING_TRIES
times (default 3) because Freerouting's result varies between runs, and it
keeps the run with the fewest unconnected items.
generate.sh writes the library, schematic, PCB and BOM, then:
exports KiCad's own netlist from the schematic and checks it against
design.py pin by pin (currently 354 connections, 0 mismatches);
runs KiCad DRC on the board. Current result: 0 unconnected items, 0
clearance or courtyard errors, and a few silkscreen and thermal-relief
warnings. lib_footprint_issues only appears when the
standard KiCad libraries aren't in the global library table.
Editing the .kicad_sch / .kicad_pcb by hand is fine once you take over
the design; just stop running the generator after that, or it overwrites your
changes.
Must check before ordering boards
Done:
Pololu carrier pinout is taken from Pololu's labeled top view: left
row VM, GND, EN, PH, PMODE, SLEEP, VREF; right row VIN, GND, OUT1, OUT2,
IMODE, FAULT, CS; rows 0.5" apart. Silkscreen marks VM (top left) and VIN
(top right) on each socket: plug the carrier in components-up with its VM
pin at the VM mark.
DevKit pinout matches a photo of the board in hand (DevKitC V4 layout,
3V3 at the antenna end).
Copper: 1 oz. VIN/VM traces are 2.5 mm with 1.6/0.8 mm vias, motor
traces 1.2 mm with 1.2/0.6 mm vias.
DevKit row spacing confirmed at 1.0" (25.4 mm).
DD-50 footprint follows Amphenol's D-Sub brochure for DD50S564TLF
(stamped contacts, termination type 5): tail rows 2.54 mm apart, the row
nearest the flange 10.40 mm from it, 2.77 mm pitch, 61.11 mm between the
shell holes.
LCSC numbers checked by search (C465732 is TI's TCA9555PWR; its LCSC
attribute text is a generic I/O-expander template).
Still to check:
DD-50 bracket holes (not blocking): the brochure doesn't dimension
the 50-way plastic bracket, so the two 3.2 mm holes sit on the shell-hole
centres (61.11 mm apart), 12.94 mm behind the flange. The connector is
held by its 50 soldered pins either way.
Part orientation in JLC's placement preview (see below). First pass
checked: the TSSOPs were 90 degrees off and are now corrected in the CPL;
D5 and the LEDs were already right. Re-check U5-U7 after re-uploading.
Autorouted copper. DRC-clean but not pretty; look over the VIN/VM
and MOT paths, and the long parallel runs across the middle.
Screw terminal wire entry (J2, J3, J7) should face the board edge.
Check in KiCad's 3D viewer.
Fit by hand, one of each pair:
D1 (SMBJ18A, SMB) or D8 (1.5KE18A / P6KE18A, through-hole): the
reverse-polarity / over-voltage clamp. Neither is placed by JLC.
F1 (blade fuse holder) or J7 (screw terminal + inline fuse).
J1 (barrel jack) or J2 (screw terminal) for the 12 V input.
Silkscreen
generator/gen_silk.py runs after routing and adds front labels without
touching copper:
Power: 12V IN (barrel, centre +, 18 V max), 12V IN 2 (+/-), both fuse
options (5 A blade F1, inline-fuse terminal J7: fit one), E-STOP (NC), and
"TVS: fit D1 OR D8".
Buck module: "12V -> 5V BUCK, set to 5.0 V before fitting the ESP32",
and each pin: IN+ 12V, IN- GND, OUT- GND, OUT+ 5V.
Headers: I2C (3V3 GND SDA SCL) and GPIO from the TCA9555 (P06 P07 P17
GND), each pin named.
ESP32 DevKit: USB-end arrow; 5V, 3V3 and GND turned and moved inward,
off the board edge and clear of the pins.
Driver sockets: M1-M6 with their joints (BASE, SHOULDER, ELBOW,
WRIST A, WRIST B, GRIPPER) inside each outline.
Status LEDs: VM, 5V, STATUS, 3V3.
DB-50: ROBOT CABLE / DD-50.
CGW logo: 23 mm tall, bottom middle.
Edit LABELS, LOGO and LOGO_H in gen_silk.py to change them.
Logo art: art/columbia_gadget_works_logo.png (front, placed by
gen_silk.py) and art/stealie.png (back, LOGO_BACK in gen_pcb.py)
become filled silkscreen through generator/silk_art.py. Silkscreen is one
colour: every non-white area of the image prints.
Ordering at JLCPCB
generator/gen_fab.py (run by generate.sh) writes fab/:
scorbot_controller_gerbers.zip: upload as the PCB (2 layers, 1.6 mm,
1 oz copper).
jlc_bom.csv and jlc_cpl.csv: upload for PCB Assembly, top side only.
These list only the SMD parts JLC places. Everything else is
hand-soldered: see the buy list in the plan doc.
Checking the JLC part numbers
For each line of fab/jlc_bom.csv, search the LCSC number at
https://jlcpcb.com/parts and confirm:
value and package match the Comment and Footprint columns (0805, 1206,
SMA, TSSOP-24, MSOP/VSSOP-10);
capacitors are X7R/X5R and 25 V or more; R31-R36 are 47 R, 2512, 1 W
(they dissipate about 0.3 W each);
Basic vs Extended (each Extended part adds a one-off loading fee, about
$1.50-3);
stock covers (quantity x number of boards).
If a number is wrong or out of stock, pick any equivalent Basic part and
change it in the LCSC table in generator/gen_fab.py (or edit the CSV).
Checking orientation in JLC's placement preview
After uploading the BOM and CPL, JLC shows each part on the board. Zoom in
and check:
U5 (TCA9555), U6/U7 (ADS1115): the pin-1 dot on the chip sits on the
pin-1 marker of the footprint.
D5 (SS14): the cathode band is on the pad marked as cathode (toward
the DevKit's 5 V feed).
LEDs D3, D4, D6, D7 (green, green, red, green): the cathode mark
faces the GND side.
Resistors and capacitors have no polarity.
If a part is turned the wrong way, rotate it in JLC's tool (or add 90/180 to
its Rotation in jlc_cpl.csv). To make the fix permanent, add the
footprint to ROT_FIX in generator/gen_fab.py. It already turns the TSSOPs
(U5-U7) by -90 degrees, because JLC's TSSOP models sit 90 degrees from KiCad's.
Design notes
DB50 pinout: SCORBOT-ER 4u User Manual, Chapter 8 (identical to the
ER III manual Table D-1). Pins 37-44 unused; pin 22 (gripper switch) has no
connection in the arm. Motor +/- labels differ between manuals; firmware
sets direction.
Encoders: bare IR LEDs + phototransistors. 47 R per axis from 5 V for
VLED (ER III reference value; check against the ER-4u's upgraded PC510
encoders). P0/P1 have 4.7 k pull-ups to 3.3 V and 1 nF, straight into the
ESP32 (no buffer); the PCNT glitch filter handles noise.
Power input, two options: barrel jack J1 or screw terminal J2 (same
nets; use one).
Fuse, two options: fit EITHER the on-board mini blade holder F1
(Keystone 3568, 5 A ATM fuse) OR the screw terminal J7 with an inline
fuse holder wired across it. They are in parallel: two fuses in at once
double the trip current, and a bare wire in J7 bypasses F1.
No reverse-polarity FET: a reversed supply forward-biases the
unidirectional SMBJ18A and blows the fuse.
E-stop: no relay; the NC contacts sit in the VM line (J3), so they must
be rated for total motor current. Logic stays powered.
Carrier current limit: VREF is pulled to SLEEP (3.3 V) by 10 k on the
carrier. CS has 2.4 k on the hardware/drv8874-carrier board (about
3.1 A) and 2.49 k on Pololu's (about 2.9 A with the #4035 DRV8874, about
1.33 A with the #4036 DRV8876).
R21-R26 (DNP) lower it.
Current sense: two ADS1115IDGSR chips on the board (0x48: CS1-4,
0x49: CS5, CS6 and VM/5.7; ADDR strapped to GND / 3V3). CS reads 1.08 V/A on the CGW carrier (1.12 V/A on a #4035, 2.49 V/A on a #4036);
use the ADS1115's +/-4.096 V range.
Plan, firmware architecture and API: see the "Scorbot ER-4u ESP32
Controller Plan" doc.
KiCad project for the replacement controller: an ESP32 DevKit, six Pololu DRV8874 carriers and a DROK mini 5 V buck module plug into a master board, and the robot's DD-50 cable plugs straight into the board edge.
KiCad project for the replacement controller: an ESP32 DevKit, six Pololu DRV8874 carriers and a DROK mini 5 V buck module plug into a master board, and the robot's DD-50 cable plugs straight into the board edge.
The Smart Plant is a board that can be plugged directly on the soil, close to the plant, that allows the measurement of the environment (soil moisture, environment temperature & illuminance), and presents the…
Drone Show Software is software designed for drone shows, allowing flight path planning as well as control of dozens of drones simultaneously in a synchronized manner.
Vector Network Analyzer based on the STM32F103C8T6 bluepill
178 parts93
Questions
How big is the Scorbot controller PCB?
It measures 185 × 128 mm and has 2 copper layers, 1.6 mm thick.
What parts does the Scorbot controller use?
102 parts, built around the SS14. 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 Scorbot controller KiCad files?
From the ColumbiaGadgetWorks/scorbot repository on GitHub, at the commit this page was made from: the board is hardware/scorbot-controller/scorbot_controller.kicad_pcb and its schematic hardware/scorbot-controller/scorbot_controller.kicad_sch. PCBKit opens the board in the browser, with nothing to install.
Can I use the Scorbot controller design in my own project?
Its repository states no licence, so its author keeps all rights: ask ColumbiaGadgetWorks before reusing the design.