Hi,
We’ve had a few runs stop due to an unexpected Y-axis error. Based off of the files shown below, could this be hardware related (motor dying)? I haven’t seen the crash happen live yet, but from the description, the instrument is just performing whatever it normally would… so if its in the middle of a run, the error can occur there, it can occur during an abort sequence once a method is stopped, or just normal operation. I tried to create a move test where I just told the 8 channels to move around the deck from labware to labware, over and over in a set of loops, but was not able to catch this issue.
Here’s the commlink file
Here’s the trace file
