CAIBI project benchmark: Open Syringe Pump v4
Prompt version 1.0

Help me build Open Syringe Pump v4 using the existing creator project at https://github.com/Karpova-Lab/syringe-pump. This is a CAIBI benchmark adaptation of the project build brief, not a claim about how the creator used AI.

Project context:
- A modular open laboratory syringe-pump platform with a compact mechanical pump, a separate controller and serial control for repeatable research fluid handling.
- Build context: Bent aluminium pump frame and current v4 fasteners; FDM printed syringe clamps, carriage and related mechanical parts; Stepper motor, 2 mm pitch leadscrew, linear shaft and bearings; Integrated pull and push limit switches; Controller PCB with TMC5041 motor drive and user-interface electronics; Display, buttons and rotary encoder; Connector module for the selected power and communication route; 12 V supply for the source-safe baseline configuration; Syringe plus experiment-specific tubing, outlet and fluid-path consumables.
- Where AI helps: Navigate the v4 BOM, mechanical source, controller files and documentation, Help distinguish current v4 parts from older v2 and v3 hardware, Explain controller configuration and serial commands, Calculate source-defined flow relationships from syringe diameter and plunger speed, Help build calibration plans and data-logging scripts for the actual fluid path, Review firmware or host-side integration changes before physical testing, Help troubleshoot repeatability using measured results rather than theoretical microstep claims.
- Physical work: Source or fabricate the exact v4 bent aluminium and printed mechanical parts, Assemble the rods, bearings, leadscrew, carriage, clamps, stepper and limit switches, Build or source the controller electronics and inspect every connection before power is applied, Use the source-safe 12 V route unless the experiment genuinely requires and validates a different supported setup, Fit the real syringe and fluid path and check clearances, loading and limit-switch operation, Calibrate delivered volume and flow with the actual syringe, tubing and fluid, Manage experiment-specific physical, fluid and contamination risks, Validate suitability for the intended research process rather than assuming an open design is a certified instrument.
- Main limitation: The source cost and 10-minute assembly statement do not describe an all-in first build. The frame and printed parts must already exist, the controller still has to be built or sourced, and real dispensing accuracy depends on the syringe, tubing, needle or outlet, fluid properties, plunger friction and calibration. CAIBI does not treat the theoretical step size as guaranteed delivered-volume accuracy and does not present this as clinical dosing equipment.

Read the source first. Use its published design, files, dimensions and parts as the baseline; do not redesign it unless a missing detail requires a clearly labelled proposal. If you cannot access a source or verify a revision, say so.

Provide one practical build package:
1. Design and files: explain the source design, link the original editable files, and identify missing files or modifications.
2. Parts and fabrication: give quantities, exact variants and compatibility, plus a cutting or printing list where applicable. Preserve source dimensions; flag anything unconfirmed.
3. UK and US purchasing: direct product links, checked dates, stock, pack sizes, taxes, delivery and regional costs. Mark unverifiable details as unknown; do not invent links, prices or availability.
4. Assembly: an ordered guide covering fabrication, fitting, wiring or software as applicable, setup, checks and troubleshooting.
5. Cost and time: separate parts, fabrication, delivery, hands-on time and machine time, with assumptions and exclusions.
6. Function and ease: a test plan for the project's stated purpose, likely difficulties, required skills and any corrections or limitations.

Keep source facts, your proposals and items needing physical verification distinct. An estimate is not a measured build result. Do not claim to have built or tested hardware. Include failed attempts and omissions. If a section does not apply, say why.

Use the source as accessed during this run and record its revision or access date. The prompt is fixed; the linked source can change.