-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: labware error when trying to "proceed to run" prevents run #12952
Comments
I have a similar experience. I had a protocol loading on the OT-2, but has the OT-2 was not responsive I cancelled the protocol. Unfortunately, I now get a similar error, though my "file_identifier" complains about another file (custom labware for LVL tubes). I have tried to remove the custom json and add it back to the library (testing in between). I have restarted the PC, the OT-2 and reinstalled the OT-2 software without luck. The same protocols I want to up on it, can be analysed and opened on our other OT-2 |
Hi!
I was finally able to solve the problem by performing a factory reset:
Factory resetting the OT-2 (opentrons.com)<https://support.opentrons.com/s/article/Factory-resetting-the-OT-2>
Hope this helps!
Catherine Mullins
Research Specialist
Gangarosa Department of Environmental Health
Rollins School of Public Health, Emory University
Atlanta, GA
…________________________________
From: KU-JonasL ***@***.***>
Sent: Monday, July 3, 2023 6:34 AM
To: Opentrons/opentrons ***@***.***>
Cc: Mullins, Catherine Elaine ***@***.***>; Author ***@***.***>
Subject: [External] Re: [Opentrons/opentrons] bug: labware error when trying to "proceed to run" prevents run (Issue #12952)
I have a similar experience. I had a protocol loading on the OT-2, but has the OT-2 was not responsive I cancelled the protocol. Unfortunately, I now get a similar error, though my "file_identifier" complains about another file (custom labware for LVL tubes).
I have tried to remove the custom json and add it back to the library (testing in between). I have restarted the PC, the OT-2 and reinstalled the OT-2 software without luck. The same protocols I want to up on it, can be analysed and opened on our other OT-2
—
Reply to this email directly, view it on GitHub<#12952 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A75VFJDVCCOZ77QRVOJW4JDXOKN3JANCNFSM6AAAAAAZPQVMIA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Thank you Catherine! It helped me as well, I can now load protocols again. Well done! |
Thank you for the suggestion of the factory reset. We are currently experiencing the same thing and will proceed as you have done. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This was a problem related to the robot's storage of protocols being prone to corruption. (Tracked internally as RSS-147.) It was fixed for OT-2 users in v7.0.1 (PR #12341). After updating, you'll need to reset your robot's run and protocol history, as @cemull3 suggested. I agree that what @yuanlee0325 is reporting seems like a different thing. @yuanlee0325, if you're still having trouble with that, please reach out to Opentrons Support. Thank you all! |
Overview
Whenever I try to run a protocol, I receive this error, even when the protocol does not use this labware and this labware has been removed from the library:
Steps to reproduce
Upload and Attempt to run any protocol and hit "proceed to set up"
Prior to this, the Opentron had a protocol that was cancelled prematurely. The robot and app has been restarted multiple times. The computer also has been restarted.
Current behavior
Unable to run any protocol
Robot does not seem to have reset itself after the last canceled protocol
Expected behavior
Robot should reset itself, with pipets moving back into position over waste
Protocol should run, unobstructed by a labware definition that is not used in the protocol or even in the library.
Operating system
Windows
System and robot setup or anything else?
USB connection
Version 6.3.1
The text was updated successfully, but these errors were encountered: