I am attempting to add in a variable amount of tubes for my workflow and have been able to do so successfully before but have never done it with the registration of barcodes into variables for the reporting that we do at the end. The specific problem is coming from the set variable command as I am trying to get it to include the loop command that I made. I have already turned the string variable into an array to attempt and store the variable values from it but am still getting an error. Any assistance would be great.
The problem is that within the „GetAttribute“ Function, the content enclosed by quotes is only interpreted once, taken literally. So what the GetAttribute function „sees“ in your script is pool_tube[cycle] while it should be seeing pool_tube[1], pool_tube[2] and so on. One fix is to declare a new string variable within the loop, removing the need to interpret the variable array index counter „cycle“. Check this example where I named the new string variable „pool_tube_current“:
So the content of pool_tube_current is holding a string concatenation forming the string you need for the GetAttribute function.
It worked in simulation, hope this solves your problem!
3 Likes
Hi Leon, thank you that seemed to work excellently, I am currently testing it on instrument for our purposes.
1 Like
Hi,
In FluentControl, if I use the “Add Labware” command and want to add a tube runner containing Falcon tubes to the deck layout, do you know if this works?
I’m asking because the runner is technically defined as a carrier in FluentControl rather than as labware. So I was wondering whether, when adding it this way, the system still correctly identifies the runner and the Falcon tubes positioned on it
1 Like
From my observations the ‘Add Labware’ command also works fine to add carriers, it can even be used to add Deck Segment carriers on Worktable Grids and then in a second ‘Add Labware’ command add a plate on a Nest on that Deck Segment. Hence I assume it shall also work for tube runners and tubes
2 Likes
FluentControl contains existing labware that can be queried directly with the add labware command that do contain Falcon tubes already. But we have been able to implement a looped add labware command for the carriers(tube runners), then a looped add labware command for the addition of all necessary Falcon tubes within the carrier. This allows us to use our integrated barcode scanner on the tubes to apply the barcodes for worklisting later in our scripts.
We operate through having a base worktable that is manipulated as necessary throughout the script via add and remove labware commands in tandem with touchtools commands to guide operators from start to finish.
2 Likes
In my case, I would be using a Labware Group, since the Falcon tubes and the runner are coupled together. If I use this Labware Group in the “Add Labware” command, then do you think that would also work without any issues?