Hamilton Star Plus Support

Hi everyone,

I am working on bringing PyLabRobot onto a Hamilton Microlab STAR Plus and wanted to check in with the community on best practices for the extended STAR platform. My understanding is that this is being implemented in V1 but is not in the current V0.2?

My understanding is that the layout being implemented is different from my hardware (according to claude):

Upstream STARPlusDeck() My STAR Plus (ML_FlexStar.dck / .lay)
Width 2040 mm, 76 tracks Dim.Dx 2590, rails 1–82
Waste block Right end, X ≈ 1810 Middle, X ≈ 778 (gap at rails 31–41)
Channel trash X ≈ 1835 X = 800
384 head waste Not modelled StarPlusCore384Waste at (827.45, 350.05, 232)
Rail gap / no-place zone None Rails 31–41

Is the standard layout for the Star plus having the waste at the end? I am not super familiar so I couldn’t say. And if this is the case, would it better to build a custom deck definition for the specific star plus I am working with currently?

Also good to see the previous progress on the 384 head pipetting! Thank you all!

2 Likes

@CamilloMoschner will be able to help

Hi @Whammer296,

This is super exciting, and very happy to help!

When I created the v1 STAR system I wanted to create a starting point for anyone with a STAR Plus, but have never had the chance to work with one myself.
So all data I had came from the publicly released material from Hamilton. This is PyLabRobot’s chance to replace that with real device info :slight_smile:

Yes exactly: the pipette/channel waste is normally on a waste_block starting right after the last track (STARlet and STAR).

I think you are saying that on a STAR Plus it is after track 30 like on a STARlet, i.e. not the total end track (which is variable as well)?

Is it possible for you to share some pictures?

We can definitely make a nice deck definition and get it into main.

I will also review what the operator manual says about STAR Plus again :sweat_smile:

1 Like