fix(api,app): Block protocol start if the Flex Stacker is not homed or shuttle is missing + home stacker from Desktop app.

[vegano1]

Overview

The Flex stacker Platform might not always be at the homed (gripper) position, which could cause a problem when loading labware on a stacker occupied column 4, since the labware would not be physically where we expected. So let's ensure we can't start the protocol if the relevant stackers are not homed or the shuttle is missing. The Platform missing status coming from the backend was also wrong, let's also fix that.

Stacker needs home

Stacker Missing shuttle

Module needs setup

Modules and fixtures ready

Closes: EXEC-1563 EXEC-1572

Test Plan and Hands on Testing

• Make sure the "Play" or "Start Protocol" button is disabled on the ODD and Desktop app if a stacker needs homing or the shuttle is missing.
• Make sure that the "Home Stacker" button is shown in protocol setup for the Desktop App and ODD if the stacker needs to be homed.
• Make sure the "Action needed" button is shown in protocol setup on the desktop app if the shuttle is missing
• Make sure the "missing-shuttle" status is shown in protocol setup on the ODD if the shuttle is missing

Changelog

• Move PlatformState.MISSING logic to the get_platform_sensor_state method of the FlexStacker Reader, since we need up-to-date limit switch status
• Added 'set_refresh_state' to the FlexStacker module in the API to tell the reader when to refetch states not polled, like limit switch status, TOF sensors, etc.
• Change "Calibration needed" copy in deck configuration to "Action needed" per design
• Added "Home Stacker" button to the protocol setup of the desktop app if the flex stacker needs to home.
• Block protocol start if the flex stacker is not homed or the platform is not extended

Review requests

• Makes sense?

Risk assessment

Low, unreleased.

[sfoster1]

Approving to unblock since this is time sensitive, but there's some small things I think we can improve

[sfoster1]

this is probably not the right place fo rthis, since it will disable the run button with "calibrate attached module(s) to continue" - wants its own reason, right?

[vegano1]

@smb2268 and I spoke about it,

I think it should be, I think the confusion is that calibration is now a part of the greater "Module Setup" flow. However, some areas reference "calibration required," which should say "Module Setup Required" or something similar.

[vegano1]

Spoke to design, will change the copy to "Action needed".

[ahiuchingau]

Tested on robot and worked as expected