Missing Functionality of Channel Single Steps


So in Venus I’m attempting to do an aspiration and dispense using the 8 channels, but the only options available are smart step aspiration and dispense with the only single step being a “on the fly” dispense.

How do I get single step aspiration and dispense to show up in my toolbox?

Open Hamilton Method Editor and select Tools > System Configuration Editor > Step Selection

The default install has quite a few useful single step commands hidden, so I suggest going through the entire list and enabling functions that are useful to your hardware config

Thanks! I did this to get error handling to become visible, but I don’t see any for single steps

There are two different step selection menus in system configuration editor. The tab/menu you used to enable custom error handling is the menu for general steps.


To toggle the ML_STAR single steps you want visible, go to the ML_STAR section in system config editor, and toggle the commands you want available in the single steps subsection, within the ML_STAR category. I usually just double click the subsection header to enable all steps visible in one action, and then deselect any individual ones not desired to be visible in method editor. You don’t need to worry about deselecting steps for hardware components not enabled in the ‘Simulator Configuration’ subsection (components not relevant to your system) as VENUS will automatically hide these even if they are marked as ‘Step Visible’.


1 Like

This is an old post but it’s relevant to the question I have now. How does one add the single steps to sub-method libraries? I’m trying to build a library that involves the single steps but it is not appearing on my toolbox despite the steps being visible in the step selection. I’ve seen other libraries that have the single steps but failed to recreate how they did it.

You need to add the ML_STAR to the submethod to get access to the ML_STAR commands.

Regular methods don’t need this as they are linked to a system deck layout which is how they get the ML_STAR commands. Submethod libraries don’t have layouts so you need to tell it what instrument it is.

1 Like

Thank you Eric!

1 Like