Skip to the content
2 layers30 × 70 mmTecan tray, the printed circuit board in 3D

A complete project to enable direct software control over the waste tray position of Tecan's Te-Chrom microchromatography module

Size
30 × 70 mm
Copper layers
2
Thickness
1.6 mm
Parts
24
Nets
38
Pads
110
Tracks, vias
79, 0
Pours
1
Routed
Yes
KiCad
KiCad 9.0 (file 20241229)
Created
5 Aug 2026
Updated
5 Aug 2026

Overview

Tecan tray is an open-source printed circuit board by niaid, from the niaid/techrom-tray repository on GitHub. It is a 2-layer board of 30 × 70 mm with 24 parts on 38 nets, routed with 79 tracks and 0 vias.

Its parts include 8 connectors, 5 resistors, 2 capacitors, 1 diode and 1 transistor. It belongs with the AVR (ATmega, ATtiny) boards of this library.

README

README.md

Te-Chrom Waste Tray Automation

Primary authors: Elihu Ihms and Nathan Jones Organizational contact: Elihu Ihms (elihu.ihms AT nih.gov) Date of release: August 10, 2026 Version: 1.0 License details: See LICENSE file

Description: This repository contains firmware, hardware files, and host-side control tools for automating insertion and retraction of the waste tray on a Te-Chrom microchromatography module. The Te-Chrom is an optional module sold by Tecan for use with Tecan EVO and Fluent automated liquid handlers.

The automator is built around an Arduino Nano-compatible controller, a FS90R continuous-rotation servo, and 3D-printed housing parts. Commands can be sent over USB from the included browser UI, the Python command-line script, the Arduino IDE Serial Monitor, EVOWare, FluentControl, or any other program that can write single-byte serial commands.

Repository structure

PathContents
README.mdProject documentation
techrom_tray.inoArduino firmware for the tray controller
techrom_tray.htmlBrowser-based Web Serial control panel
techrom_tray.pyPython serial-control CLI for automation software integration
kicad/KiCad schematics and PCB design files
pcb/PCB Gerbers, bill of materials, and reference files
stl/Fusion 360 design files and STL models for the housing and moving parts
nano/Arduino Nano reference diagrams and pinouts

Hardware overview

The automator consists of inexpensive, off-the-shelf components attached to a Te-Chrom microchromatography module without permanently modifying the instrument. Several 3D-printed parts provide the mechanical interface:

  • An Arduino Nano-compatible microcontroller, typically an ATmega328P/Nano-compatible board with an FT232RL or CH340G USB-to-serial interface.
  • A continuous-rotation servo, specifically a Fitec/FEETECH FS90R.
  • Two active-low limit microswitches: one for the out/retracted position and one for the in/inserted position.
  • Optional status LEDs.
  • An assembled PCB and 3D-printed rack-and-pinion housing.
  • Optional reset wiring or remote pushbutton wiring.

Construction

Electrical

Custom PCB Gerber files are provided in pcb/ and can be submitted to a PCB manufacturer for economical fabrication in small batches. The use of through-hole components makes manual assembly straightforward. A bill of materials for the electrical components is provided in pcb/bom.csv.

Limit switches and status LEDs can be wired with standard jumper wires or female DuPont-style connectors. Refer to the PCB reference image at pcb/reference.png when wiring switch and LED headers. Male and female pin headers can be bought in exact lengths or cut down from longer strips.

Hardware

The plastic parts for mounting the custom PCB and microswitches were printed in PLA with a 0.4 mm nozzle diameter on a Prusa 3D FDM printer. Default PrusaSlicer settings were used for slicing.

Inserts were not found to be necessary, and M3 stainless screws should be used to assemble the parts. A photograph of a fully assembled automator attached to a Te-Chrom can be found in stl/automator.jpg.

The pinion that drives the waste-tray rack incorporates a friction clutch. The clutch helps prevent damage to the servo or Te-Chrom if a hardware or software error causes the servo to continue running against an obstruction. Small variations in FDM printing may require adjustment of the clutch friction. The clutch must provide enough friction to move the waste tray reliably without slipping while still allowing the gear to freewheel if an obstruction is encountered.

Three separate friction values for the clutch are provided: stl/clutch_15.stl, stl/clutch_25.stl, and stl/clutch_35.stl. Selecting the appropriate friction value is largely a matter of judgment. The clutch is splined to match the 29-point spline pattern of the FS90R and should be secured using the 1.5 mm screw supplied with the servo's control-horn kit. Should additional friction values be necessary, the public OnShape model for the clutch and gear exposes a parametric clutchDrag variable that can be incremented or decremented as necessary.

Firmware

The provided techrom_tray.ino sketch uses the standard Arduino Servo library and no additional third-party libraries. It can be opened, compiled, and uploaded using the Arduino IDE.

The microcontroller can be flashed either before or after it is installed in the PCB.

Remove the D5 LOCK/DTR jumper before flashing when the microcontroller is installed in the custom PCB.

Constants

ConstantValueMeaning
SERIAL_BAUD9600USB serial baud rate
LOOP_DELAY5 msDelay at the end of each main loop iteration
SERVO_SPEED50Servo write offset from neutral during movement
SERVO_STOP90Default neutral/stop value for Servo.write()
SERVO_TIMEOUT8,000 msMaximum time the servo may run for one movement command

Arduino Nano pinout

See the Nano's pinout diagram for a comprehensive list of all pin capabilities. The following GPIO pins are used in the automator:

Arduino pinSketch nameDirection/modeFunction
D5SERVO_PWM_PINPWMServo control signal
D6SERVO_ENABLE_PINOutputEnables servo drive while moving; LOW when stopped
D2OUT_LIMIT_PININPUT_PULLUPOut/retracted limit switch, active LOW
D3IN_LIMIT_PININPUT_PULLUPIn/inserted limit switch, active LOW
D8OUT_LED_PINOutputOut/retracted status LED
D9IN_LED_PINOutputIn/inserted status LED
D10M_LED_PINOutputMoving/error status LED

The limit switches use internal pullups and are active LOW.

OUT switchIN switchInterpreted state
LOWHIGHTray is out/retracted
HIGHLOWTray is in/inserted
LOWLOWError: both limit switches are active
HIGHHIGHStart/unknown position

At startup, the firmware reads both limit switches and initializes the tray state from those inputs.

Serial commands

During normal operation, the automator responds to single-character commands by emitting a single-character state value followed by a newline.

CommandFirmware actionResponse
IMove tray in/insertPrints I when the in limit switch is reached; prints E if an error occurs; prints I immediately if already in.
OMove tray out/retractPrints O when the out limit switch is reached; prints E if an error occurs; prints O immediately if already out.
PQuery current tray statePrints one of S, o, O, i, I, or E
EClear error state only; do not moveRe-reads the switches and prints the resulting state.
+Increment the servo neutral/stop value by 1Prints the new neutral value.
-Decrement the servo neutral/stop value by 1Prints the new neutral value.
?Read the current servo neutral/stop valuePrints the current neutral value.
Any other characterNo actionPrints ?

Movement commands do not print an immediate moving response when motion starts. They print only after the destination limit switch is reached, the tray is already at the requested limit, or when an error occurs. If you query with P while the servo is actively running, the state will be i or o.

For the FS90R continuous-rotation servo, small deviations from the 1.5 ms pulse-width signal can cause asymmetric rotational speeds or drift at the default neutral setting. The preferred fix is to adjust the small potentiometer on the servo itself. Alternatively, use firmware + and - trim commands carefully and in small increments.

Emitted state characters:

StateMeaning
SStart/unknown position
oMoving out
OParked out/retracted
iMoving in
IParked in/inserted
EError state

Error handling

The firmware enters an error state when:

  • Both limit switches are active LOW at the same time (this should be a physical impossibility).
  • The tray is moving and no destination limit switch is reached within SERVO_TIMEOUT, currently 8,000 ms.

When an error occurs, the servo is stopped and disabled.

Status LED behavior

ConditionOut LEDIn LEDMoving LED
Tray outONOFFOFF
Tray inOFFONOFF
Tray movingOFFOFFON
Both limit switches activeONONOFF
Movement timeout errorONONON
Start/unknownOFFOFFOFF

Send E to clear an error after resolving the mechanical or switch problem. If the underlying switch condition still indicates an error, the device will immediately return to an error state.

Control

The automator can be controlled using the Arduino IDE Serial Monitor, a serial-terminal application, or any other program capable of opening and writing to a serial port. The included web app and Python script use the same command and response protocol. EVOWare and FluentControl can control the automator and receive status values by invoking the included Python script with the Start Application command or by using VBA.

Serial settings

SettingValue
Baud9600
Data bits8
Paritynone
Stop bits1
Command formatOne ASCII character
Response formatASCII response ending in newline

Browser control with techrom_tray.html

techrom_tray.html is a self-contained HTML application that uses Chrome's Web Serial API and is intended for troubleshooting. It provides buttons for:

  • Connect to Arduino
  • Move Tray In
  • Move Tray Out
  • Query Position
  • Reset Error

The current web application does not include a disconnect button or servo-trim controls. Refresh the page if you need to reconnect, pick a different port, or recover from a browser-side serial state problem.

Python CLI: techrom_tray.py

The Python script lets automation software issue commands to the automator and inspect stdout, stderr, or exit codes. It requires pyserial, which is not part of the Python standard library.

Usage:

python techrom_tray.py [-h] [-O | -I | -P | -o OFFSET | --reset | --debug CHAR | --detect] [COM[n]|/dev/ttyUSB0|AUTO]

ArgumentMeaning
comportSerial port to use; defaults to COM3; use AUTO to probe likely serial ports
-I, --inMove tray in/insert
-O, --outMove tray out/retract
-P, --positionQuery tray position/error status
-o OFFSET, --offset OFFSETSet servo neutral offset from 90; accepted range -10 to 10
--resetClear tray error status without moving
--debug CHARSend one raw ASCII test character and print the raw response
--detectProbe likely serial ports, print the first matching port, and exit

The action arguments are mutually exclusive; run one tray command per script invocation.

Examples

Detect a connected tray controller:

bash
python techrom_tray.py --detect

Use an automatically detected port:

bash
python techrom_tray.py AUTO --position
python techrom_tray.py AUTO --in
python techrom_tray.py AUTO --out

Use an explicit Windows port:

bash
python techrom_tray.py COM5 --position
python techrom_tray.py COM5 --in
python techrom_tray.py COM5 --out
python techrom_tray.py COM5 --reset
python techrom_tray.py COM5 --offset 2
python techrom_tray.py COM5 --debug P

Use an explicit Linux port:

bash
python techrom_tray.py /dev/ttyUSB0 --position
python techrom_tray.py /dev/ttyACM0 --out

Python stdout examples

The script prints human-readable status messages to stdout.

text
$ python techrom_tray.py COM5 --position
In

$ python techrom_tray.py COM5 --out
Tray is OUT.

$ python techrom_tray.py COM5 --reset
Tray at start position.

$ python techrom_tray.py COM5 --offset 2
Servo neutral value is now 92 (offset +2 from 90).

Python exit codes

In addition to printing human-readable messages to stdout, the script itself returns meaningful exit codes so that automation software such as FluentControl's Start Application command can detect the result without needing to parse messages.

General exit codes:

Exit codeMeaning
0Success
1Generic failure, unparseable response, unexpected servo trim response, or final fallback failure
2Failure to connect to serial port, failure to autodetect a port, or missing pyserial
3Failure to write to serial port
4Failure to read a response before timeout, or failure while waiting for serial data
5Failure to close serial port
6Failure to decode response as ASCII
7Tray is in error state when using --position
21Negative acknowledge: movement blocked by error state, unknown response, or unexpected tray response
24--reset was sent, but the device still reported error state

When --position receives a recognized non-error tray state, the script prints the state and exits with the ASCII code for the returned state character.

ResponsePrinted textExit code
SStart83
iMoving In105
IIn73
oMoving Out111
OOut79
EError printed to stderr7

Movement commands exit 0 when the expected final state is reached: --in expects I, and --out expects O. If the device reports E, movement exits 21. If another known tray state is returned unexpectedly, the script prints that state to stderr and exits with the ASCII code for that state.

--reset exits 0 if the device reports any known non-error state after reset. It exits 24 if the device still reports E.

--offset exits 0 when the requested neutral offset has been reached. It exits 1 if the device reports an unparseable or unexpected servo neutral value.

Operation

All power for the Arduino and servo is supplied through the USB connection on the Nano, with commands sent over the same USB serial connection. Although a large capacitor helps suppress voltage drops caused by servo inrush current, the automator should be connected to a USB host capable of supplying at least 500 mA. Insufficient current may cause voltage transients that reset the microcontroller.

When first connected, the Arduino Nano power LED should illuminate.

Normal operation:

  1. Connect the device over USB.
  2. Query the current state with P, the web UI Query Position button, or python techrom_tray.py <PORT> --position.
  3. Send I to insert the tray or O to retract it.
  4. Wait for the firmware response. A final I or O means the requested limit switch was reached.
  5. If the device reports E, inspect the tray motion path and limit switches, fix the cause, then clear the error with E or --reset.

Hard reset options:

  • Use the momentary reset button on the Arduino Nano PCB.
  • Use the optional remote reset header, if installed.
  • Power-cycle the Arduino.

A hard reset clears RAM-only trim values and reinitializes state from the current limit-switch readings.

Servo offset notes / LOCK/DTR

The Arduino sketch stores servo neutral trim values in RAM. The value is initialized to 90 after a reset, and the script treats offsets as relative to that value. For example, --offset 2 drives the firmware neutral value to 92, while --offset -3 drives it to 87.

Because the Arduino normally resets when a serial port opens, the D5 LOCK/DTR jumper on the PCB is important if you need trim values to survive repeated host-side serial connections, which is likely. Although the Python script keeps the port open during a single --offset operation, the current firmware does not persist the trim value across an Arduino reset or power loss, regardless of whether the D5 LOCK/DTR jumper is installed.

Troubleshooting

No serial port appears

Check Device Manager on Windows or the equivalent serial-device list on your operating system. Arduino Nano clones commonly appear as Arduino Nano, USB-SERIAL CH340, or a similar USB serial adapter. If the port does not appear, install or update the driver for the USB-to-serial adapter used by your board.

The Arduino resets when the serial port opens

The PCB includes a D5 LOCK/DTR jumper. When installed, it holds the DTR line low to reduce automatic resets when the serial port opens. Remove this jumper before flashing the Arduino in the custom PCB.

The browser UI and Python script both wait 2 seconds after opening the serial port to allow an Arduino reset/settle cycle to complete.

Movement times out

The firmware allows only 8,000 ms of servo motion per command. If the tray does not reach the target limit switch in that time, the firmware stops the servo and enters error state. Check for mechanical binding, reversed servo direction, disconnected switches, incorrect switch wiring, or insufficient servo power.

The browser UI and Python script wait up to 12,000 ms for a newline-terminated response.

Both limit switches appear active

Both switches active LOW at the same time is treated as an error. Check switch placement, wiring shorts, and whether both switches are being pressed mechanically.

Web UI reports timeout

A timeout usually means the Arduino did not send a response, the wrong serial port was selected, the firmware is not running, the serial protocol does not match, or the tray failed to reach a limit switch.

Python reports no response

Check that the port is correct, the firmware is flashed, the Arduino has finished resetting after the port opens, and the serial protocol matches this README. The current Python script sends P for tray position, I for in, O for out, and E for reset.

Servo drifts while stopped

First adjust the physical trim potentiometer on the continuous-rotation servo. If small firmware trim changes are still needed, use +, -, and ? over serial or use the Python --offset command. Remember that the current sketch does not save the trim value across reset or power loss.

Current limitations

  • The web UI does not expose servo trim/debug commands or a disconnect button.
  • The Arduino sketch stores servo neutral trim in RAM only; it is not saved to EEPROM.

Acknowledgments

It is the sincere hope of the VRC Data Science and Automation team that this addition improves the reliability and versatility of your Te-Chrom. If you publish data generated with the help of this device, please let the maintainer know; acknowledgments are appreciated.

Parts

24
QtyValueFootprintReferences
3500 ΩResistor_THT:R_Axial_DIN0204_L3.6mm_D1.6mm_P7.62mm_HorizontalR3, R4, R5
110 kΩResistor_THT:R_Axial_DIN0204_L3.6mm_D1.6mm_P7.62mm_HorizontalR2
110uF_16VCapacitor_THT:CP_Radial_D5.0mm_P2.50mmC2
11N5817Diode_THT:D_A-405_P7.62mm_HorizontalD1
1250 ΩResistor_THT:R_Axial_DIN0204_L3.6mm_D1.6mm_P7.62mm_HorizontalR1
12N7000Package_TO_SOT_THT:TO-92_Inline_WideQ1
1470uF_16VCapacitor_THT:CP_Radial_D10.0mm_P5.00mmC1
1Arduino_Nano_v3.xModule:Arduino_NanoA1
1ICSPConnector_PinSocket_2.54mm:PinSocket_2x03_P2.54mm_VerticalJ4
1LEFTConnector_PinHeader_2.54mm:PinHeader_1x02_P2.54mm_VerticalJ7
1LIMITConnector_PinHeader_2.54mm:PinHeader_2x02_P2.54mm_VerticalJ2
1LOCK / DTRConnector_PinHeader_2.54mm:PinHeader_1x02_P2.54mm_VerticalJ5
1RESETConnector_PinHeader_2.54mm:PinHeader_1x02_P2.54mm_VerticalJ6
1RIGHTConnector_PinHeader_2.54mm:PinHeader_1x02_P2.54mm_VerticalJ8
1SERVOConnector_PinHeader_2.54mm:PinHeader_1x03_P2.54mm_VerticalJ1
1STATUS LEDSConnector_PinHeader_2.54mm:PinHeader_2x03_P2.54mm_VerticalJ3

The 18 most common of 24 parts.

Similar boards

  • 2 layers56 × 65 mmSeaTalk1, the printed circuit board in 3D

    SeaTalk1

    dotnet/iot

    This repo includes .NET Core implementations for various IoT boards, chips, displays and PCBs.

    24 parts2.4kMIT
  • 2 layers26.2 × 45.5 mmPL18 multiprotocol, the printed circuit board in 3D

    PL18 multiprotocol

    pascallanger/DIY-Multiprotocol-TX-Module

    Multiprotocol TX Module (or MULTI-Module) is a 2.4GHz transmitter module which controls many different receivers and models.

    24 parts1.9kGPL-3.0
  • 2 layers58 × 35.5 mmHat, the printed circuit board in 3D

    Hat

    menloresearch/asimov-1

    v1 of Asimov, an open-source humanoid robot

    24 parts1.4kCERN-OHL-S-2.0
  • 2 layers21.6 × 19.5 mmMicron Logo LED, the printed circuit board in 3D

    Micron Logo LED

    DraftShift/StealthChanger

    Tool changing system for Vorons and other front mount printer motion systems, not just stealthburner.

    24 parts1.2kGPL-3.0
  • 2 layers158 × 11 mmRainbow Matchstick, the printed circuit board in 3D

    Rainbow Matchstick

    VoronDesign/Voron-Hardware

    Cool Hardware designed by the Voron Design group

    24 parts1.1kGPL-3.0
  • 2 layers85.6 × 54 mmTRACED wio1262-carrier, the printed circuit board in 3D

    TRACED wio1262-carrier

    hackclub/OnBoard

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

    24 parts915
  • 2 layers36 × 20 mmCombined, the printed circuit board in 3D

    Combined

    adamb314/ServoProject

    Getting the most out of your hobby servo

    24 parts545

Questions

How big is the Tecan tray PCB?

It measures 30 × 70 mm and has 2 copper layers, 1.6 mm thick.

What parts does the Tecan tray use?

24 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 Tecan tray KiCad files?

From the niaid/techrom-tray repository on GitHub, at the commit this page was made from: the board is kicad/tecan_tray.kicad_pcb and its schematic kicad/tecan_tray.kicad_sch. PCBKit opens the board in the browser, with nothing to install.

Can I use the Tecan tray design in my own project?

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