Jubilee Sonication Station

Project notes

Choose the controller environment first

The README describes local operation on Jubilee's attached Raspberry Pi and a separate-PC network route. It recommends the local route for production use and warns that network loss can halt remote execution and latency can slow it. These are upstream operating recommendations, not production reliability established here. The motion controller has a simulated mode, but SonicationStation still constructs Sonicator unconditionally. That initializes I2C/GPIO on the local Python host, including with simulated=True. Selecting a remote motion address does not route those sonicator interfaces to the machine's Pi; neither a hardware-free station mode nor the separate-PC interface arrangement was established. [1] [3] [6] [7]

The documented installation is pip3 install -e . from the repository. Setup metadata declares Python 3.6 or later, package 0.0.1 and dependencies including inpromptu 0.0.5, Adafruit MCP4725 and Blinka. A current compatible environment was not reproduced; those declarations do not establish availability for an arbitrary PC or operating system. [1] [2]

Configure the machine state and deck deliberately

The quickstart requires powering on with no labware, homing, selecting or creating the deck configuration, loading labware and only then executing operations or protocols. Use setup_plate to define plate locations, well counts and heights, and a safe_z clearance that accommodates loaded labware and the actual tools. The implementation guards setup_plate/sonicate_well on safe_z rather than supplying a universal safe height. The documented sequence ends with tool return, labware removal and power-off. The README also calls for recovering tools after emergency power loss. Those prerequisites matter before adapting the example protocol; a Python import does not home or calibrate the machine. [1] [8]

The controller implementation sends G-code through the configured machine HTTP interface, and the sonicator module initializes an I2C DAC at address 0x60 with a GPIO enable output. Match the physical DAC/enable wiring and interface board rather than assuming an application command reaches the correct instrument. The original KiCad board and schematic were retrieved and identity-checked, but no native DRC or electrical/host connection was tested. [3] [4] [5] [6]

The README's JSON example wraps commands in a protocol object, while execute_protocol_from_file passes the parsed object directly to code iterating operation entries. Its example also omits power, pulse_duty_cycle and pulse_interval required by sonicate_well. Reconcile the JSON structure and required arguments against the pinned implementation before adapting the example; these are static mismatches, not reproduced runtime failures. [1] [7]

Inspect interruption behavior before physical use

The sampled sonicator operation sets DAC power, toggles enable in a timed loop, and resets outputs at normal completion. That reset is not enclosed in an encompassing finally block in the inspected method; an exception or interruption cannot be assumed to take the normal completion path. Its __exit__ cleanup method also does not itself prove how every calling context handles failure. This review establishes no safe-interruption or shutdown behavior. [6] [7]

The package metadata declares MIT, but no root license text was identified; that declaration does not establish a hardware or media grant. External dependencies, sonicator and parent platform retain separate terms. No complete cost, package installation, machine connection, homing, tool calibration, acoustic output, exposure accuracy or assay efficacy was tested. [2] [4] [5] [6]