Tecan Error Deciphering

Error: An item with the same key has already been added

Does anyone know what this error could be triggered from? I tried deleting the Tecan STATE files, rebooting, and running the protocol again to no avail. A less cryptic error summary would be helpful. Unfortunately I can’t seem to find any further information in the Tecan Log files. Tomorrow I will attempt the run in Real Mode, and report back with results.

@Liam7b The error message text sounds quite generic.

To troubleshoot you could create the Reagent Distribution Command with one of the default liquid classes like Water Free Multi, with fixed numeric values instead of variables and see if that works. And if it still doesn’t work try further to Aspirate from a trough instead of a tube. Until you have again a working version of the Reagent Distribution command.

And from there add bit by bit - add back the variable, add back your own liquid class try until it stops working in order to identify the part that causes it. Or vice-versa take the non-working version and remove bit by bit the variable, using a default liquid class, using a trough instead of a tube etc… until it works again until you find which item causes the error.

1 Like

@Snowball

Thanks. It has something to do with my liquid class. This same LC worked fine in FluentControl version 3.3. I think we may have something corrupted in the database. A ticket has been filed with Tecan. Changing the LC to “Water Free Multi” ran just fine, thanks for the suggestion.

Yes, with software updates come new features within the liquid class editor, so errors like these can be common. I’ve also seen these errors when importing LCs from other PCs (with different FC versions). I usually end up recreating the LC by duplicating and modifying water free dispense. A good habit to get into is to “print as PDF” your most important liquid classes and storing them so you can recreate them if needed, regardless of FC version.

Has this been resolved @Liam7b ? I’ve been reflecting on this issue and it may be wise to look into whether there’s a problem with labware or sample IDs. Are you using sample tracking or worklists? Try a default labware like a 96w microplate.