Why do we need this start state? For modes, we have the transitionTo...() functions that get called automatically before starting a new mode. For sub-modes and their states, the general approach should be to handle transition logic at the same point the code changes the sub-mode/state. You can consider a separate transition state like this if there are a lot of states that could transition to this state or if the transition is very complex, but this one doesn't seem to fit either category.
Not quite what I had in mind. I meant that, regardless of whether sharing a connector, you would always "get" the new heat disinfect temperature. Inside TempSensors, you would have the build switch. If using TRO connector for new sensor, fill THd from TRo temp sensor and fill TRo from TDi temp sensor (both TDi and TRo share TDi sensor). If THd has its own connector (DVT system?), then fill THd from THd sensor and TRo from TRo sensor as you would normally expect.
The reservoir should be settled for the first verify already. There is no need to wait for another settle to start second displacement. Removed the check for settle time in second displacement setup.
Replace logic with a temp parameter (call it whatever you like) and then use that parameter in the function call. This will make the code a lot more legible.
