version: 1.5.0
files:
  - url: Opentrons-OT3-v1.5.0-win-b42355.exe
    sha512: MhudXT69yKyjERC/RWbNdkumbWAhse5ARtsDtmJ+gMRN2racb+rcGr6DSRwczTRex7MaWrj0Oyn8mhkaI/RsIQ==
    size: 304349592
path: Opentrons-OT3-v1.5.0-win-b42355.exe
sha512: MhudXT69yKyjERC/RWbNdkumbWAhse5ARtsDtmJ+gMRN2racb+rcGr6DSRwczTRex7MaWrj0Oyn8mhkaI/RsIQ==
releaseNotes: "For more details about this release, please see the full [technical change log]: https://github.com/Opentrons/opentrons/releases\r\n\r\n# Internal Release 1.5.0\r\n\r\nThe primary purpose of the release is to allow science and design to test, given known bugs and work arounds, as we continue to develop features for 7.3.0.\r\n\r\n## Before making any changes to the robot, reset the run history. Robot Settings > Advanced > Choose reset settings > Clear protocol run history\r\n\r\n## Known Bugs and work arounds\r\n\r\n### Do not use the USB connection to the robot. Please use the desktop app via WiFi and/or ODD\r\n\r\n### There are multiple firmware updates that will run and you may encounter the ODD stuck on the update gripper modal. Do Not Click! Firmware will update automatically\r\n\r\n### Viewing a protocol's run record after the run completes may not show all the steps. Download the run record to view all steps\r\n\r\n### Deck maps during module calibration may not render correctly\r\n\r\n### Modules and fixtures may not be removed via deckmap on ODD\r\n\r\n### Run again may not work on first click in the desktop app\r\n\r\n### 96channel detach flow will fail on confirmation of step 1. You will receive an stall detection error. Go ahead and clear the error. Remove the support bracket. Home the gantry. Enter into attach flow for the right pipette so the right pipette interface can again be used\r\n\r\n### If you interact with the gantry while a gripper is attached and you are not in a detach/attach flow it is possible the gripper may fall. Always be in an attach/detach flow when interacting with the gantry\r\n\r\n### \"out of date protocol\" on the desktop app will show a white deckmap. Most protocols will get the \"protocol analysis out of date\" banner. Click re-analyze protocol\r\n\r\n<https://github.com/Opentrons/opentrons/compare/ot3@v1.2.0...ot3@v1.5.0>\r\n\r\n---\r\n\r\n## Internal Release 1.5.0-alpha.3\r\n\r\nThis internal release is from the `edge` branch to contain rapid dev on new features for 7.3.0. This release is for internal testing purposes and if used may require a factory reset of the robot to return to a stable version.\r\n\r\nThis release is to address live run command display issues.\r\n\r\n<https://github.com/Opentrons/opentrons/compare/ot3@1.5.0-alpha.2...ot3@1.5.0-alpha.3>\r\n\r\n---\r\n\r\n## Internal Release 1.5.0-alpha.2\r\n\r\nThis internal release is from the `edge` branch to contain rapid dev on new features for 7.3.0. This release is for internal testing purposes and if used may require a factory reset of the robot to return to a stable version.\r\n\r\nThis release is to address bugs in the update and downgrade flows for the app and robot.\r\n\r\n<https://github.com/Opentrons/opentrons/compare/ot3@1.5.0-alpha.1...ot3@1.5.0-alpha.2>\r\n\r\n---\r\n\r\n## Internal Release 1.5.0-alpha.1\r\n\r\nThis internal release is from the `edge` branch to contain rapid dev on new features for 7.3.0. This release is for internal testing purposes and if used may require a factory reset of the robot to return to a stable version.\r\n\r\n<https://github.com/Opentrons/opentrons/compare/ot3@1.5.0-alpha.0...ot3@1.5.0-alpha.1>\r\n\r\n---\r\n\r\n## Internal Release 1.5.0-alpha.0\r\n\r\nThis internal release is from the `edge` branch to contain rapid dev on new features for 7.3.0. This release is for internal testing purposes and if used may require a factory reset of the robot to return to a stable version.\r\n\r\n<https://github.com/Opentrons/opentrons/compare/ot3@1.4.0-alpha.1...ot3@1.5.0-alpha.0>\r\n\r\n---\r\n\r\n## Internal Release 1.4.0-alpha.1\r\n\r\nThis internal release is from the `edge` branch to contain rapid dev on new features for 7.3.0. This release is for internal testing purposes and if used may require a factory reset of the robot to return to a stable version.\r\n\r\n### Notable bug fixes\r\n\r\nApp and robot update prompts should now function properly. However, updating from 1.4.0-alpha.0 to 1.4.0-alpha.1 will still present issues, as the fix is not in 1.4.0-alpha.0. After installing 1.4.0-alpha.1, switch your update channel to \"latest\" to receive the latest stable internal release prompt, which validates the fix.\r\n\r\n### All changes\r\n\r\n<https://github.com/Opentrons/opentrons/compare/ot3@1.4.0-alpha.0...ot3@1.4.0-alpha.1>\r\n\r\n---\r\n\r\n## Internal Release 1.4.0-alpha.0\r\n\r\nThis internal release is from the `edge` branch to contain rapid dev on new features for 7.3.0. This release is for internal testing purposes and if used may require a factory reset of the robot to return to a stable version.\r\n\r\n<https://github.com/Opentrons/opentrons/compare/ot3@1.3.0-alpha.0...ot3@1.4.0-alpha.0>\r\n\r\n---\r\n\r\n## Internal Release 1.3.0-alpha.0\r\n\r\nThis internal release is from the `edge` branch to contain rapid dev on new features for 7.3.0. This release is for internal testing purposes and if used may require a factory reset of the robot to return to a stable version.\r\n\r\n<https://github.com/Opentrons/opentrons/compare/v7.2.2...ot3@1.3.0-alpha.0>\r\n\r\n---\r\n\r\n# Internal Release 1.1.0\r\n\r\nThis is 1.0.0, an internal release for the app supporting the Opentrons Flex.\r\n\r\nThis is still pretty early in the process, so some things are known not to work, and are listed below. Some things that may surprise you do work, and are also listed below. There may also be some littler things of note, and those are at the bottom.\r\n\r\n\r\n## New Stuff In This Release\r\n\r\n- There is now UI for configuring the loaded deck fixtures such as trash chutes on your Flex.\r\n- Support for analyzing python protocol API 2.16 and JSON protocol V8\r\n- Labware position check now uses the calibration (the same one used for pipette and module calibration) instead of a tip; this should increase the accuracy of LPC.\r\n- Connecting a Flex to a wifi network while the app is connected to it with USB should work now\r\n- The app should generally be better about figuring out what kind of robot a protocol is for, and displaying the correct deck layout accordingly\r\n\r\n## Known Issues\r\n\r\n- Labware Renders are slightly askew towards the top right.\r\n"
releaseDate: '2024-04-26T13:34:28.641Z'
