You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using pipette.starting_tip with api version 2.14, for example, when I write pipette.starting_tip = tip_rack_1.well('C3') in my protocol, the first pipette pick_up_tip() picks up C3 as expected, but the next pipette.pick_up_tip() picks up A1 instead of D3, and the third and subsequent times, B1, C1, and so on.
Steps to reproduce
No response
Current behavior
No response
Expected behavior
Using pipette.starting_tip with api version 2.14, for example, when I write pipette.starting_tip = tip_rack_1.well('C3') in my protocol, the first pipette .pick_up_tip() picks up C3, and then the robot should pick up D3, E3, and so on, instead of A1, B1.
Operating system
None
System and robot setup or anything else?
Changing to api version 2.13 eliminates this unexpected pickup chip behavior. So I think this unexpected move of OT-2R is originated in the api 2.14 bug error.
The text was updated successfully, but these errors were encountered:
Overview
Using pipette.starting_tip with api version 2.14, for example, when I write pipette.starting_tip = tip_rack_1.well('C3') in my protocol, the first pipette pick_up_tip() picks up C3 as expected, but the next pipette.pick_up_tip() picks up A1 instead of D3, and the third and subsequent times, B1, C1, and so on.
Steps to reproduce
No response
Current behavior
No response
Expected behavior
Using pipette.starting_tip with api version 2.14, for example, when I write pipette.starting_tip = tip_rack_1.well('C3') in my protocol, the first pipette .pick_up_tip() picks up C3, and then the robot should pick up D3, E3, and so on, instead of A1, B1.
Operating system
None
System and robot setup or anything else?
Changing to api version 2.13 eliminates this unexpected pickup chip behavior. So I think this unexpected move of OT-2R is originated in the api 2.14 bug error.
The text was updated successfully, but these errors were encountered: