Simulate with pipetting error

Hamilton (Venus)
1

Hello!

I was wondering if it is possible to simulate runs to test pipetting errors?

For instance to check how a “Excluded” error is handled by the method.

Just so that one can save some time and does not need to create the pipetting error “live”.

Has anyone experience in this?

Best wishes

Hans-Otto

1 Like
2

Hi there,
Not sure what you mean but you can definitively simulate your run.
In the Run Control: Settings, Simulate:
image

If you want to crash your method on purpose, just include some errors in your method.

If you want to see how the system handles them, check the trace file or include custom traces.

You can also use the user handler step to automatically handle errors (if you do not see it: right click in the general section and remove the smart step DATA Handling steps)

image
image316×155 6.74 KB
.

Hope this helps.

1 Like
3

Hi @yunghans,

I built a library just for this purpose; it can be downloaded here: ErrorSimulator 1.0.0.zip :: Hamilton

Installation

There is no installer for the ErrorSimulator Library. Follow the steps below for setup:

  1. Download ‘ErrorSimulator v1.0.0.zip’

  2. Extract the zip to the “C:\Program Files (x86)\Hamilton\Library\ErrorSimulator” folder.

  3. Open ‘ErrorSimulator Demo.med’ in the “C:\Program Files (x86)\Hamilton\Library\ErrorSimulator\Test Method” and modify the Deck Layout as needed.

  4. Run the demo method to confirm functionality.

Note: the ErrorSimulator Library requires the HSLExtensions library already be installed on the system.

How to use:

The ErrorSimulator Library contains four functions:

InitializeLibrary

Call this function at any time in a method before using any other function from the library. This function performs various checks to confirm the instrument type, database connection, and simulation mode. It also has three parameters to toggle library settings, including Trace Level, Internal dialogs for library error handling, and whether to reset the Simulator Config file as part of initialization.

ResetConfigFile

Call this function at any time to set all functions in the Simulator Config file back to a “No Error” state. This is the same functionality performed as part of the InitializeLibrary function, if set to true. While not required, calling this step at the end of a method and/or in the OnAbort submethod can help avoid incorrect error calls between runs.

SetError

This is the main function of this library, and is used to activate the instrument error at runtime in simulation mode. Call this function any time before calling the instrument step that is intended to error. SetError has three parameters, which are used to determine the function and error to activate.

  • i_strModule - the device to receive the error (e.g. “1ml channels” or “IPG”)
  • i_strFunction - the step the receive the error (e.g. “Aspirate” or “Load Carrier")
  • i_strError - the description of the error to activate on the given step (e.g. “1.Insufficient Liquid Level” or “Y-drive step lost”)

SetErrorByCode

This function can be used in place of the SetError function to the same effect, but requires knowledge of the specific Firmware command and error code syntax. It’s useful to call functions/errors that don’t exist in the library database.

Refer to the Demo Method for more information on using the ErrorSimulator Library.

Thank you,
Dan

6 Likes
4

Wow amazing!

Thank you so much, @DanHartman_Hamilton !

2 Likes