<?xml version="1.0" encoding="utf-8"?>
<ErrorLibrary xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" Version="1.0.2102.2601">
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER</ModuleName>
    <Name>STAT_DRIVER_OVER_CURRENT</Name>
    <ErrorCode>1</ErrorCode>
    <ErrorText>Over current error. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Circuitry over current, tuning parameter not optimized</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER</ModuleName>
    <Name>STAT_IC_THERMAL1_SHUTDOWN</Name>
    <ErrorCode>2</ErrorCode>
    <ErrorText>Motor driver thermal shutdown error. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Thermal shutdown/overheat</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER</ModuleName>
    <Name>STAT_PID_POSITION_ERROR_LIMIT</Name>
    <ErrorCode>3</ErrorCode>
    <ErrorText>Position error. Motor movement has exceeded the threshold. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>motor movement not accurate</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER</ModuleName>
    <Name>STAT_MOVEMENT_TIMEOUT</Name>
    <ErrorCode>4</ErrorCode>
    <ErrorText>Motion unable to complete. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Possibly motor or encoder failure</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER</ModuleName>
    <Name>STAT_COMMUTATE_FAILED</Name>
    <ErrorCode>5</ErrorCode>
    <ErrorText>Motor commutation failure. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Rotor alignment not achieved during initialization</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER</ModuleName>
    <Name>STAT_TIPS_ON_POSITION_ERROR_LIMIT</Name>
    <ErrorCode>6</ErrorCode>
    <ErrorText>No tip box is detected. Please confirm if tip boxes are in the correct location. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>No tip box detected</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER</ModuleName>
    <Name>STAT_SEMAPHORE_TIMEOUT</Name>
    <ErrorCode>7</ErrorCode>
    <ErrorText>Could not obtain semaphore. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Firmware bug</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER</ModuleName>
    <Name>STAT_PID_OVER_CURRENT</Name>
    <ErrorCode>8</ErrorCode>
    <ErrorText>PID over current. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>motor over current, tuning parameter not optimized</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER</ModuleName>
    <Name>STAT_PID_TIMEOUT</Name>
    <ErrorCode>9</ErrorCode>
    <ErrorText>PID timeout. Motion is unable to complete. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Motion unable to complete </PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER</ModuleName>
    <Name>SYNC_CMD_NOT_RECV</Name>
    <ErrorCode>10</ErrorCode>
    <ErrorText>Sync command not received. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Sync command not received, but received sync broadcast command</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER</ModuleName>
    <Name>SYNC_BROADCAST_MULTI_RECV</Name>
    <ErrorCode>11</ErrorCode>
    <ErrorText>Received multiple sync boardcast command. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Received multiple sync broadcast command</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER</ModuleName>
    <Name>SYNC_BROADCAST_TIMEOUT</Name>
    <ErrorCode>12</ErrorCode>
    <ErrorText>No broadcast command received within the timeout period. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Not receiving sync broadcast cmd within timeout period(5s)</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER</ModuleName>
    <Name>VSENSE_MOTOR_UNDERVOLTAGE</Name>
    <ErrorCode>13</ErrorCode>
    <ErrorText>Under voltage error / Motor voltage below specification. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Under voltage error. Motor voltage below specification.</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER</ModuleName>
    <Name>VSENSE_DRIVER_UNDERVOLTAGE</Name>
    <ErrorCode>14</ErrorCode>
    <ErrorText>Under voltage error / Driver voltage below specification. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Under voltage error. Driver voltage below specification.</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER</ModuleName>
    <Name>MOTOR_HOMING_FAILED</Name>
    <ErrorCode>15</ErrorCode>
    <ErrorText>No transition detected on home sensor. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Home Sensor fault / Motor moved beyond Home sensor</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER</ModuleName>
    <Name>MOTOR_ENCODER_MISSING_COUNT</Name>
    <ErrorCode>16</ErrorCode>
    <ErrorText>Encoder count does not match the index count. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Faulty encoder</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE</ModuleName>
    <Name>STAT_OVER_CURRENT</Name>
    <ErrorCode>1</ErrorCode>
    <ErrorText>Over current error. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Circuitry over current, tuning parameter not optimized</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE</ModuleName>
    <Name>STAT_IC_THERMAL1_SHUTDOWN</Name>
    <ErrorCode>2</ErrorCode>
    <ErrorText>Thermal shutdown error. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Thermal shutdown/overheat</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE</ModuleName>
    <Name>STAT_PID_POSITION_ERROR_LIMIT</Name>
    <ErrorCode>3</ErrorCode>
    <ErrorText>Motor movement has exceeded the threshold. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>motor movement not accurate</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE</ModuleName>
    <Name>STAT_MOVEMENT_TIMEOUT</Name>
    <ErrorCode>4</ErrorCode>
    <ErrorText>Motor is unable to complete motion. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Possibly motor or encoder failure</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE</ModuleName>
    <Name>SYNC_CMD_NOT_RECV</Name>
    <ErrorCode>5</ErrorCode>
    <ErrorText>Sync command not received. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Sync command not received, but received sync broadcast command</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE</ModuleName>
    <Name>SYNC_BROADCAST_MULTI_RECV</Name>
    <ErrorCode>6</ErrorCode>
    <ErrorText>Multiple sync broadcast commands were received. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Received multiple sync broadcast command</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE</ModuleName>
    <Name>SYNC_BROADCAST_TIMEOUT</Name>
    <ErrorCode>7</ErrorCode>
    <ErrorText>No broadcast command received within the timeout period. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Not receiving sync broadcast cmd within timeout period(5s)</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE</ModuleName>
    <Name>VSENSE_MOTOR_UNDERVOLTAGE</Name>
    <ErrorCode>8</ErrorCode>
    <ErrorText>Under voltage error / Motor voltage below specification. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Under voltage error. Motor voltage below specification.</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE</ModuleName>
    <Name>VSENSE_DRIVER_UNDERVOLTAGE</Name>
    <ErrorCode>9</ErrorCode>
    <ErrorText>Under voltage error / Driver voltage below specification. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Under voltage error. Driver voltage below specification.</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE</ModuleName>
    <Name>ENCODER_FAULT_UNSTABLE</Name>
    <ErrorCode>10</ErrorCode>
    <ErrorText>Faulty encoder. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Encoder unstable (if encoder assembly problem and encoder distance too far from magnetic strip)</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE</ModuleName>
    <Name>ENCODER_FAULT_SSI</Name>
    <ErrorCode>11</ErrorCode>
    <ErrorText>Faulty encoder. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Encoder fault (if encoder assembly problem, encoder distance too far/near/misalign from magnetic strip or defective magnetic strip)</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_PELTIER1_FLT</Name>
    <ErrorCode>2</ErrorCode>
    <ErrorText>Peltier_1 HW circuit failure. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Peltier circuitry return fault /control fault</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_PELTIER2_FLT</Name>
    <ErrorCode>3</ErrorCode>
    <ErrorText>Peltier_2 HW circuit failure. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Peltier circuitry return fault /control fault</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_PELTIER3_FLT</Name>
    <ErrorCode>4</ErrorCode>
    <ErrorText>Peltier_3 HW circuit failure. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Peltier circuitry return fault /control fault</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_PELTIER4_FLT</Name>
    <ErrorCode>5</ErrorCode>
    <ErrorText>Peltier_4 HW circuit failure. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Peltier circuitry return fault /control fault</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_PELTIER5_FLT</Name>
    <ErrorCode>6</ErrorCode>
    <ErrorText>Peltier_5 HW circuit failure. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Peltier circuitry return fault /control fault</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_PELTIER6_FLT</Name>
    <ErrorCode>7</ErrorCode>
    <ErrorText>Peltier_6 HW circuit failure. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Peltier circuitry return fault /control fault</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_HOTTOP_FLT</Name>
    <ErrorCode>8</ErrorCode>
    <ErrorText>Hot top hardware circuit failure. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Hot Top circuitry return fault/control fault</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_PELTIER1_OVRCURR</Name>
    <ErrorCode>9</ErrorCode>
    <ErrorText>Peltier_1 readback current value exceeds safety limit. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Peltier monitor circuitry issue, adc problem, control fault</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_PELTIER2_OVRCURR</Name>
    <ErrorCode>10</ErrorCode>
    <ErrorText>Peltier_2 readback current value exceeds safety limit. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Peltier monitor circuitry issue, adc problem, control fault</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_PELTIER3_OVRCURR</Name>
    <ErrorCode>11</ErrorCode>
    <ErrorText>Peltier_3 readback current value exceeds safety limit. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Peltier monitor circuitry issue, adc problem, control fault</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_PELTIER4_OVRCURR</Name>
    <ErrorCode>12</ErrorCode>
    <ErrorText>Peltier_4 readback current value exceeds safety limit. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Peltier monitor circuitry issue, adc problem, control fault</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_PELTIER5_OVRCURR</Name>
    <ErrorCode>13</ErrorCode>
    <ErrorText>Peltier_5 readback current value exceeds safety limit. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Peltier monitor circuitry issue, adc problem, control fault</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_PELTIER6_OVRCURR</Name>
    <ErrorCode>14</ErrorCode>
    <ErrorText>Peltier_6 readback current value exceeds safety limit. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Peltier monitor circuitry issue, adc problem, control fault</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_HOTTOP_OVRCURR</Name>
    <ErrorCode>15</ErrorCode>
    <ErrorText>Hot Top readback current value exceeds safety limit. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Peltier monitor circuitry issue, adc problem, control fault</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_FAN_SENSE_ABNORMAL</Name>
    <ErrorCode>18</ErrorCode>
    <ErrorText>Fan sensor abnormal behavior is detected. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Fan damage/circuitry damage</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_THERMISTOR1_READING_INVALID</Name>
    <ErrorCode>19</ErrorCode>
    <ErrorText>Firmware thermistor_1 is out of range. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Thermistor shorted or not connected</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_THERMISTOR2_READING_INVALID</Name>
    <ErrorCode>20</ErrorCode>
    <ErrorText>Firmware thermistor_2 is out of range. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Thermistor shorted or not connected</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_THERMISTOR3_READING_INVALID</Name>
    <ErrorCode>21</ErrorCode>
    <ErrorText>Firmware thermistor_3 is out of range. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Thermistor shorted or not connected</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_THERMISTOR4_READING_INVALID</Name>
    <ErrorCode>22</ErrorCode>
    <ErrorText>Firmware thermistor_4 is out of range. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Thermistor shorted or not connected</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_THERMISTOR5_READING_INVALID</Name>
    <ErrorCode>23</ErrorCode>
    <ErrorText>Firmware thermistor_5 is out of range. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Thermistor shorted or not connected</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_THERMISTOR6_READING_INVALID</Name>
    <ErrorCode>24</ErrorCode>
    <ErrorText>Firmware thermistor_6 is out of range. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Thermistor shorted or not connected</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_THERMISTORHT_READING_INVALID</Name>
    <ErrorCode>25</ErrorCode>
    <ErrorText>Hot top Firmware thermistor is out of range. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Thermistor shorted or not connected</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_THERMISTORHS_READING_INVALID</Name>
    <ErrorCode>26</ErrorCode>
    <ErrorText>Firmware heat sink thermistor is out of range. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Thermistor shorted or not connected</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_HW_THERMISTOR1_OVER_TEMPERATURE</Name>
    <ErrorCode>29</ErrorCode>
    <ErrorText>Hardware thermistor_1 over temperature is detected. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Peltier reaches over temperature threshold</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_HW_THERMISTOR2_OVER_TEMPERATURE</Name>
    <ErrorCode>30</ErrorCode>
    <ErrorText>Hardware thermistor_2 over temperature is detected. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Peltier reaches over temperature threshold</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_HW_THERMISTOR3_OVER_TEMPERATURE</Name>
    <ErrorCode>31</ErrorCode>
    <ErrorText>Hardware thermistor_3 over temperature is detected. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Peltier reaches over temperature threshold</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_HW_THERMISTOR4_OVER_TEMPERATURE</Name>
    <ErrorCode>32</ErrorCode>
    <ErrorText>Hardware thermistor_4 over temperature is detected. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Peltier reaches over temperature threshold</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_HW_THERMISTOR5_OVER_TEMPERATURE</Name>
    <ErrorCode>33</ErrorCode>
    <ErrorText>Hardware thermistor_5 over temperature is detected. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Peltier reaches over temperature threshold</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_HW_THERMISTOR6_OVER_TEMPERATURE</Name>
    <ErrorCode>34</ErrorCode>
    <ErrorText>Hardware thermistor_6 over temperature is detected. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Peltier reaches over temperature threshold</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_HW_THERMISTOR_HT_OVER_TEMPERATURE</Name>
    <ErrorCode>35</ErrorCode>
    <ErrorText>Peltier has reached the over temperature threshold. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>HotTop reaches over temperature threshold</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_HW_THERMAL_PWM_ERROR</Name>
    <ErrorCode>42</ErrorCode>
    <ErrorText>PWM output failure. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>PWM register has corrupted</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_CHILLER_DOOR_OPENED</Name>
    <ErrorCode>43</ErrorCode>
    <ErrorText>Chiller door is open while chiller is running. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Chiller door sensor down</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR,HSM_HEATER,CHILLER_1</ModuleName>
    <Name>STAT_THERMISTOR_NUMBER_OUT_OF_RANGE</Name>
    <ErrorCode>44</ErrorCode>
    <ErrorText>Firmware thermistor number is out of range. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Firmware bug</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z</ModuleName>
    <Name>UNDER_VOLTAGE_LOCKOUT</Name>
    <ErrorCode>1</ErrorCode>
    <ErrorText>Voltage is under the standard level. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Under voltage supply</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z</ModuleName>
    <Name>DRIVER_THERMAL_SHUTDOWN</Name>
    <ErrorCode>2</ErrorCode>
    <ErrorText>IC thermal over temperature is detected. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Stepper motor driver thermal shutdown</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z</ModuleName>
    <Name>OVER_CURRENT</Name>
    <ErrorCode>3</ErrorCode>
    <ErrorText>Motor driver over current is detected. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Motor over current</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z</ModuleName>
    <Name>BRIDGE_B_STALL</Name>
    <ErrorCode>4</ErrorCode>
    <ErrorText>Motor driver stall current B is triggered. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Motor phase B stall</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z</ModuleName>
    <Name>BRIDGE_A_STALL</Name>
    <ErrorCode>5</ErrorCode>
    <ErrorText>Motor driver stall current A is triggered. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Motor phase A stall</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z</ModuleName>
    <Name>SPI_CONNECTION_FAIL</Name>
    <ErrorCode>6</ErrorCode>
    <ErrorText>SPI communication has failed. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Connection/setup failure</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z</ModuleName>
    <Name>FORCE_SENSOR_CONNECTION_FAIL</Name>
    <ErrorCode>7</ErrorCode>
    <ErrorText>Force sensor communication has failed. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Connection/setup failure</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z</ModuleName>
    <Name>FORCE_SENSOR_BELOW_THRESHOLD</Name>
    <ErrorCode>8</ErrorCode>
    <ErrorText>Force sensor compression value below threshold is detected. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Compression failure</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z</ModuleName>
    <Name>FORCE_SENSOR_OUTPUT_OUT_OF_RANGE</Name>
    <ErrorCode>9</ErrorCode>
    <ErrorText>Force sensor output has exceeded the expected range. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Compression failure</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z</ModuleName>
    <Name>FORCE_SENSOR_BASELINE_EXCEEDED_LIMIT</Name>
    <ErrorCode>10</ErrorCode>
    <ErrorText>Force sensor baseline has exceeded the limit. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Connection/setup failure</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>STAT_WATCHDOG_ERROR</Name>
    <ErrorCode>45</ErrorCode>
    <ErrorText>Firmware has stopped responding. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Firmware bug</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>STAT_CPUTEMP_ERROR</Name>
    <ErrorCode>46</ErrorCode>
    <ErrorText>Ambient over temperature has been detected. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Over heat</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>STAT_NODEID_ERROR</Name>
    <ErrorCode>47</ErrorCode>
    <ErrorText>Firmware is unable to obtain node ID. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Hardware IO expander issue</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>STAT_HWREV_ERROR</Name>
    <ErrorCode>48</ErrorCode>
    <ErrorText>Firmware is unable to obtain hardware revision. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Hardware IO expander issue</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>STAT_EEPROM_I2C_ERROR</Name>
    <ErrorCode>49</ErrorCode>
    <ErrorText>EEPROM I2C Line error. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Hardware connector/cable/IC fault.</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>STAT_EEPROM_MATCH_ERROR</Name>
    <ErrorCode>50</ErrorCode>
    <ErrorText>EEPROM has reached the write limit. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>EEPROM reach write limit</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>STAT_CAN_ERROR_BIT</Name>
    <ErrorCode>51</ErrorCode>
    <ErrorText>An issue with CAN bus has been detected. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Hardware connection problem</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>STAT_CAN_TX_TIMEOUT_BIT</Name>
    <ErrorCode>52</ErrorCode>
    <ErrorText>An issue with CAN bus has been detected. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Hardware connection problem</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>POWER_MISC</ModuleName>
    <Name>STAT_UNDERVOLT_ERROR</Name>
    <ErrorCode>1</ErrorCode>
    <ErrorText>Under voltage error. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Power supply under voltage</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>POWER_MISC</ModuleName>
    <Name>STAT_OVERVOLT_ERROR</Name>
    <ErrorCode>2</ErrorCode>
    <ErrorText>Over voltage error. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Power supply over voltage</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>POWER_MISC</ModuleName>
    <Name>STAT_INVALID_DOOR_OPEN</Name>
    <ErrorCode>3</ErrorCode>
    <ErrorText>Door sensor is disengaged. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Door open</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>POWER_MISC</ModuleName>
    <Name>STAT_WASTE_BIN1_OPEN_ERROR</Name>
    <ErrorCode>4</ErrorCode>
    <ErrorText>Wastebin sensor is disengaged. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Wastebin 1 door open at invalid situation</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>POWER_MISC</ModuleName>
    <Name>STAT_WASTE_BIN2_OPEN_ERROR</Name>
    <ErrorCode>5</ErrorCode>
    <ErrorText>Wastebin sensor is disengaged. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Wastebin 2 door open at invalid situation</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>POWER_MISC</ModuleName>
    <Name>STAT_UV_ERROR</Name>
    <ErrorCode>6</ErrorCode>
    <ErrorText>UV ballast or UV tube is faulty. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Ballast fault</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>POWER_MISC</ModuleName>
    <Name>STAT_FAN_ERROR</Name>
    <ErrorCode>7</ErrorCode>
    <ErrorText>Fan is faulty. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Fan not moving</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>POWER_MISC</ModuleName>
    <Name>STAT_DOOR_SENSOR_LOGIC_ERROR</Name>
    <ErrorCode>8</ErrorCode>
    <ErrorText>Door sensor and switch are not tally. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Sensor faulty</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>POWER_MISC</ModuleName>
    <Name>STAT_WASTE_BIN_LOGIC_ERROR</Name>
    <ErrorCode>9</ErrorCode>
    <ErrorText>Waste bin 1 and 2 signal not tally. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Sensor faulty</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>HW_UART_ERROR</Name>
    <ErrorCode>1</ErrorCode>
    <ErrorText>Faulty hardware or cable. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Hardware fault or cable fault</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>HW_SETUP_ERROR</Name>
    <ErrorCode>2</ErrorCode>
    <ErrorText>Incorrect firmware version. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Barcode settings incorrect or hardware fault</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>HW_FW_VERSION_ERROR</Name>
    <ErrorCode>4</ErrorCode>
    <ErrorText>Incorrect firmware version. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Updated wrong firmware</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>HW_WRONG_BC_HW_ERROR</Name>
    <ErrorCode>5</ErrorCode>
    <ErrorText>Communication error or faulty hardware. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Firmware bugs</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>HW_BARCODE_MUTEX_UNABLE_GET</Name>
    <ErrorCode>6</ErrorCode>
    <ErrorText>Unable to get Mutex during barcode process. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Firmware Bug</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>XMODEM_IMAGE_RETRIEVE_ERROR</Name>
    <ErrorCode>7</ErrorCode>
    <ErrorText>Error encountered in xmodem during retrieving image. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Communication problem or HW fault</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>XMODEM_JOB_ERROR</Name>
    <ErrorCode>8</ErrorCode>
    <ErrorText>Error encountered in xmodem during download to camera. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Communication problem or HW fault</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>SDRAM_TEST_MUTEX_UNABLE_GET</Name>
    <ErrorCode>9</ErrorCode>
    <ErrorText>Unable to get Mutex during SDRAM Validation process. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>Firmware Bug</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>SDRAM_TEST_VALIDATION_FAIL</Name>
    <ErrorCode>10</ErrorCode>
    <ErrorText>Validation fail during Write and Read back data from SDRAM. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>SDRAM IC or SDRAM Communication line Hardware problem</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>SETTING_ERROR_0_EXPOSURE_WINDOW_0</Name>
    <ErrorCode>21</ErrorCode>
    <ErrorText>Settings error due to exposure window. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>barcode settings changed</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>SETTING_ERROR_1_EXPOSURE_WINDOW_4</Name>
    <ErrorCode>22</ErrorCode>
    <ErrorText>Settings error due to exposure window. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>barcode settings changed</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>SETTING_ERROR_2_DISABLE_SYMBOLOGIES</Name>
    <ErrorCode>23</ErrorCode>
    <ErrorText>Settings error due to disabling symbology. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>barcode settings changed</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>SETTING_ERROR_3_ENABLE_DATA_MATRIX</Name>
    <ErrorCode>24</ErrorCode>
    <ErrorText>Settings error due to disabled data matrix. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>barcode settings changed</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>SETTING_ERROR_4_ENABLE_DRAWING_IN_SHIPPED_IMAGES</Name>
    <ErrorCode>25</ErrorCode>
    <ErrorText>Settings error due to enabled drawing in shipped images. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>barcode settings changed</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>SETTING_ERROR_5_ENABLE_SCEN_MASK</Name>
    <ErrorCode>26</ErrorCode>
    <ErrorText>Settings error due to enabled scen mask. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>barcode settings changed</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>SETTING_ERROR_6_NOT_USE_BARCODE_HEADER</Name>
    <ErrorCode>27</ErrorCode>
    <ErrorText>Settings error due to incorrect use of barcode header. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>barcode settings changed</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>SETTING_ERROR_7_USE_FOOTER_SUFFIX</Name>
    <ErrorCode>28</ErrorCode>
    <ErrorText>Settings error due to use of footer suffix. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>barcode settings changed</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>SETTING_ERROR_8_USE_BARCODE_SEPERATOR</Name>
    <ErrorCode>29</ErrorCode>
    <ErrorText>Settings error due to use of barcode separator. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>barcode settings changed</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>SETTING_ERROR_9_NO_READ_TEXT_SETTING</Name>
    <ErrorCode>30</ErrorCode>
    <ErrorText>Settings error due to absence of a read text setting. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>barcode settings changed</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>SETTING_ERROR_10_BEEP_LEVEL</Name>
    <ErrorCode>31</ErrorCode>
    <ErrorText>Settings error due to beep level. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>barcode settings changed</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>SETTING_ERROR_11_FRAME_TOSS_COUNT</Name>
    <ErrorCode>32</ErrorCode>
    <ErrorText>Settings error due to frame toss count. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>barcode settings changed</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>SETTING_ERROR_12_SCN_TRG_WINDOW_MODE</Name>
    <ErrorCode>33</ErrorCode>
    <ErrorText>Settings error due to scan trg window mode. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>barcode settings changed</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>SETTING_ERROR_13_PULSE_DELAY</Name>
    <ErrorCode>34</ErrorCode>
    <ErrorText>Settings error due to pulse delay. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>barcode settings changed</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>SETTING_ERROR_14_EXTERNAL_LED_POWER</Name>
    <ErrorCode>35</ErrorCode>
    <ErrorText>Settings error due to external LED power. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>barcode settings changed</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>SETTING_ERROR_15_RED_VS_WHITE_LED_SPLIT</Name>
    <ErrorCode>36</ErrorCode>
    <ErrorText>Settings error due to enabled drawing in shipped images. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>barcode settings changed</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>SETTING_ERROR_16_REREAD_DELAY</Name>
    <ErrorCode>37</ErrorCode>
    <ErrorText>Settings error due to re-read delay. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>barcode settings changed</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>SETTING_ERROR_17_GOOD_READ_DELAY</Name>
    <ErrorCode>38</ErrorCode>
    <ErrorText>Settings error due to good read delay. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>barcode settings changed</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>SETTING_ERROR_18_TARGET_WHITE_VALUE</Name>
    <ErrorCode>39</ErrorCode>
    <ErrorText>Settings error due to  target white value. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>barcode settings changed</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>SETTING_ERROR_19_EXPOSURE_MODE</Name>
    <ErrorCode>40</ErrorCode>
    <ErrorText>Settings error due to exposure mode. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>barcode settings changed</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>SETTING_ERROR_20_MAX_EXPOSURE</Name>
    <ErrorCode>41</ErrorCode>
    <ErrorText>Settings error due to reaching maximum exposure limit. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>barcode settings changed</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>SETTING_ERROR_21_ILLUMINATION_INTENSITY_PERCENTAGE</Name>
    <ErrorCode>42</ErrorCode>
    <ErrorText>Settings error due to illumination intensity percentage. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>barcode settings changed</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>SETTING_ERROR_22_TRIGGER_TIMEOUT</Name>
    <ErrorCode>43</ErrorCode>
    <ErrorText>Settings error due to trigger timeout. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_ERROR</ErrorType>
    <PossibleCause>barcode settings changed</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <!-- ###################################System errors##################################### -->
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>MISMATCHED_DEVICE_ID_2</Name>
    <ErrorCode>1</ErrorCode>
    <ErrorText>Mismatched CAN device ID. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Communication issue</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (1))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>FAIL_EXECUTE_OPERATION</Name>
    <ErrorCode>2</ErrorCode>
    <ErrorText>Appropriate module to execute the operation cannot be found. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Communication issue</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (2))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>FAIL_VALIDATION_RESPONSE</Name>
    <ErrorCode>3</ErrorCode>
    <ErrorText>Response validation failure. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Communication issue</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (3))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>NULL_RESPONSE</Name>
    <ErrorCode>4</ErrorCode>
    <ErrorText>Firmware has reported a null data response. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Communication issue</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (4))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>FIRMWARE_ERROR</Name>
    <ErrorCode>5</ErrorCode>
    <ErrorText>Error received from Firmware. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Communication issue</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (5))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>FIRMWARE_WARNING</Name>
    <ErrorCode>6</ErrorCode>
    <ErrorText>Warning received from Firmware. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Communication issue</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (6))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>FIRMWARE_UNDEFINED_MESSAGE</Name>
    <ErrorCode>7</ErrorCode>
    <ErrorText>Undefined message received from Firmware. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Communication issue</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (7))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>FAIL_WRITE_CANBUS_2</Name>
    <ErrorCode>8</ErrorCode>
    <ErrorText>Unable to write into CAN bus. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Communication issue</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (8))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>RESPONSE_TIMEOUT</Name>
    <ErrorCode>9</ErrorCode>
    <ErrorText>Response timeout. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Communication issue</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (9))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>COMPLETE_TIMEOUT</Name>
    <ErrorCode>10</ErrorCode>
    <ErrorText>Complete timeout. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Communication issue</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (10))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>FIRMWARE_REJECT</Name>
    <ErrorCode>11</ErrorCode>
    <ErrorText>Firmware has rejected command. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Communication issue</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (11))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>OVER_RETRY_LIMIT_1</Name>
    <ErrorCode>12</ErrorCode>
    <ErrorText>Over retry limit. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Communication issue</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (12))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>GANTRY_NULL_OF_PIPETTE</Name>
    <ErrorCode>13</ErrorCode>
    <ErrorText>No gantry module found in pipette module. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Host validation failure</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (13))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>OPERATION_NOT_SUCCESS</Name>
    <ErrorCode>14</ErrorCode>
    <ErrorText>Operation execution is not successful. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Host validation failure</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (14))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>THERMAL_NULL_OF_GANTRY</Name>
    <ErrorCode>15</ErrorCode>
    <ErrorText>No thermal module is found in gantry module. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Host validation failure</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (15))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>GANTRY_NULL_OF_THERMAL</Name>
    <ErrorCode>16</ErrorCode>
    <ErrorText>No Gantry module found in Thermal module. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Host validation failure</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (16))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>GANTRY_NULL_OF_SYSTEM</Name>
    <ErrorCode>17</ErrorCode>
    <ErrorText>No Gantry module found in System module. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Host validation failure</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (17))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>GANTRY_NULL_OF_POWER_MISC</Name>
    <ErrorCode>18</ErrorCode>
    <ErrorText>No gantry module found in power miscellaneous module. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Host validation failure</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (18))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>GANTRY_NULL_OF_CHILLER</Name>
    <ErrorCode>19</ErrorCode>
    <ErrorText>No gantry module found in chiller module. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Host validation failure</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ModulesController</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (19))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>POWERMISC_NULL_OF_PIPETTE</Name>
    <ErrorCode>20</ErrorCode>
    <ErrorText>No Power Miscellaneous module found in pipette module. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Host validation failure</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (20))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>PIPETTE_NULL_OF_SYSTEM</Name>
    <ErrorCode>21</ErrorCode>
    <ErrorText>No Pipette module found in System module. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Host validation failure</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (21))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>THERMAL_NULL_OF_SYSTEM</Name>
    <ErrorCode>22</ErrorCode>
    <ErrorText>No Thermal module found in System module. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Host validation failure</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (22))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>HSM_NULL_OF_SYSTEM</Name>
    <ErrorCode>23</ErrorCode>
    <ErrorText>No HSM module found in System module. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Host validation failure</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (23))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>POWERMISC_NULL_OF_SYSTEM</Name>
    <ErrorCode>24</ErrorCode>
    <ErrorText>No Power Miscellaneous module found in System module. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Host validation failure</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ModulesController</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (24))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>CHILLER_NULL_OF_SYSTEM</Name>
    <ErrorCode>25</ErrorCode>
    <ErrorText>No Chiller module found in System module. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Host validation failure</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ModulesController</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (25))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>CHILLER_NOT_SUPPORTED</Name>
    <ErrorCode>26</ErrorCode>
    <ErrorText>Unsupported chiller board. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Communication issue</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (26))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>CONFIGURATION_NO_STRIPTUBE</Name>
    <ErrorCode>27</ErrorCode>
    <ErrorText>Invalid configuration. Unable to find target strip tube. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Configuration values</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (27))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>CONFIGURATION_NO_TARGETWELL</Name>
    <ErrorCode>28</ErrorCode>
    <ErrorText>Unable to find target well. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Configuration values</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (28))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>LABWARE_NO_WELLDEFINITION</Name>
    <ErrorCode>29</ErrorCode>
    <ErrorText>Selected labware do not contain well definitions. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Configuration values</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (29))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>LABWARE_WRONG</Name>
    <ErrorCode>30</ErrorCode>
    <ErrorText>Unable to detect proper labware. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Configuration values</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (30))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>FAIL_GET_TEACHPOINT</Name>
    <ErrorCode>31</ErrorCode>
    <ErrorText>Unable to get teach point from calibration file. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Calibration values</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (31))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_ZONE_CONFIGURATION_FILE</Name>
    <ErrorCode>32</ErrorCode>
    <ErrorText>Unable to read illegal zones. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid illegal zone values</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (32))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_GANTRY_CONFIGURATION_FILE</Name>
    <ErrorCode>33</ErrorCode>
    <ErrorText>Unable to find gantry calibration. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Configuration values</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (33))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>NO_CALIBRATION_FILE</Name>
    <ErrorCode>34</ErrorCode>
    <ErrorText>No calibration file is loaded. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Calibration values</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (34))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_CALIBRATION_FILE</Name>
    <ErrorCode>35</ErrorCode>
    <ErrorText>Invalid calibration file. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Calibration values</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (35))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_CALIBRATION_FILE_1</Name>
    <ErrorCode>36</ErrorCode>
    <ErrorText>Calibration file does not contain module information. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Calibration values</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (36))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>LIQUIDCLASS_NOTFOUND</Name>
    <ErrorCode>37</ErrorCode>
    <ErrorText>Unable to get liquid class. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid library</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (37))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_WELL_SELECTION</Name>
    <ErrorCode>38</ErrorCode>
    <ErrorText>Invalid well selection. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Protocol (Well Selections) or Configuration values</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (38))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_ROW_FORMAT</Name>
    <ErrorCode>39</ErrorCode>
    <ErrorText>Invalid row format. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Protocol (Well Selections) or Configuration values</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (39))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_CHANNEL_FORMAT</Name>
    <ErrorCode>40</ErrorCode>
    <ErrorText>Invalid channel name format. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Protocol (Well Selections)</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (40))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>COLUMNS_LESS_THAN_CHANNEL</Name>
    <ErrorCode>41</ErrorCode>
    <ErrorText>Selected columns are less than the number of channels. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Protocol (Well Selections) or Configuration values</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (41))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>UNABLE_GET_SHIRTED_CHANNEL</Name>
    <ErrorCode>42</ErrorCode>
    <ErrorText>Unable to calculate shifted channels. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Protocol (Well Selections)</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (42))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>COLUMN_OUTOFRANGE</Name>
    <ErrorCode>43</ErrorCode>
    <ErrorText>Column selection is out of range. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Protocol (Well Selections) or Configuration values</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (43))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>UNABLE_TIPSOFF_INVALID_LABWARE</Name>
    <ErrorCode>44</ErrorCode>
    <ErrorText>Unable to perform tip off at station. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Protocol (Tips off location)</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (44))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>LESS_THAN_Y_MIN</Name>
    <ErrorCode>45</ErrorCode>
    <ErrorText>Y goto position is beyond gantry's reachable location. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Configuration values</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (45))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>LESS_THAN_X_MIN</Name>
    <ErrorCode>46</ErrorCode>
    <ErrorText>X goto position is beyond gantry or magnet's reachable location. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Configuration values</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (46))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>BIAS_VOLUME_OVERLIMIT_5</Name>
    <ErrorCode>47</ErrorCode>
    <ErrorText>Over tips limit. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Protocol (Volume), Pipette encoder fault</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (47))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>BIAS_VOLUME_OVERLIMIT_3</Name>
    <ErrorCode>48</ErrorCode>
    <ErrorText>Over well limit. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Protocol (Volume), Pipette encoder fault</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (48))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>VOLUME_OVERLIMIT_TIPS</Name>
    <ErrorCode>49</ErrorCode>
    <ErrorText>Bias equation is over limit. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Protocol (Volume), Pipette encoder fault</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (49))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>DYNAMIC_EXTENSION_OVERRANGE_3</Name>
    <ErrorCode>50</ErrorCode>
    <ErrorText>Invalid dynamic extension. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Protocol (DTX)</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (50))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>DYNAMIC_RETRACTION_OVERRANGE_3</Name>
    <ErrorCode>51</ErrorCode>
    <ErrorText>Invalid dynamic retraction. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Protocol (DTX)</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (51))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_ASPIRATE_PARAMETERS</Name>
    <ErrorCode>52</ErrorCode>
    <ErrorText>Invalid aspirate parameters. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Protocol (Aspirate parameters)</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (52))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_DISPENSE_PARAMETERS</Name>
    <ErrorCode>53</ErrorCode>
    <ErrorText>Operation is aborted. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Protocol (Dispense parameters)</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (53))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_CYCLE_PARAMETERS</Name>
    <ErrorCode>54</ErrorCode>
    <ErrorText>Invalid cycle parameters. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Protocol (Mix parameters)</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (54))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_VOLUME_PARAMETERS</Name>
    <ErrorCode>55</ErrorCode>
    <ErrorText>Invalid cycle parameters. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Protocol (Mix parameters)</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (55))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_MIX_OVER_VOLUME</Name>
    <ErrorCode>56</ErrorCode>
    <ErrorText>Unable to perform mixing. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Protocol (Mix parameters)</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (56))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_LABWARE</Name>
    <ErrorCode>57</ErrorCode>
    <ErrorText>Unable to perform operation due to invalid labware. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Configuration values</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (57))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_TIPTOUCH</Name>
    <ErrorCode>58</ErrorCode>
    <ErrorText>Unable to perform side tip touch. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Protocol (Tip touch)</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (58))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_TOPSIDE_OPERATION</Name>
    <ErrorCode>59</ErrorCode>
    <ErrorText>Unable to perform top side operation. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid teaching position or Invalid Configuration values</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (59))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_BOTTOMSIDE_OPERATION</Name>
    <ErrorCode>60</ErrorCode>
    <ErrorText>Unable to perform bottom side operation. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid teaching position or Invalid Configuration values</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (60))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_SIDE_OPERATION</Name>
    <ErrorCode>61</ErrorCode>
    <ErrorText>Unable to perform side operation. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Protocol (Pipette operations)</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (61))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>OVER_WELL_LIMIT</Name>
    <ErrorCode>62</ErrorCode>
    <ErrorText>Unable to dispense. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Protocol (Well volume)</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (62))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_TIPS_DETECTED</Name>
    <ErrorCode>63</ErrorCode>
    <ErrorText>Tips detected are not as expected. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Teaching point for tips detection is not accurate.</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (63))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>FAIL_UNDEFINED_OPERATION</Name>
    <ErrorCode>64</ErrorCode>
    <ErrorText>Cannot execute the undefined operation. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>General</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (64))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>USER_ABORTED_OPERATION</Name>
    <ErrorCode>65</ErrorCode>
    <ErrorText>User has aborted operations. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>User aborted protocol</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (65))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>UNSUPPORTED_STOP_TYPE</Name>
    <ErrorCode>66</ErrorCode>
    <ErrorText>Unable to perform stop operation due to invalid stop type. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Host validation failure</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (66))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>UNREGISTERED_MODULE</Name>
    <ErrorCode>67</ErrorCode>
    <ErrorText>Unable to perform command due to unregistered module ID in handshake communication. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Host validation failure</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (67))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_ERRORCODE</Name>
    <ErrorCode>68</ErrorCode>
    <ErrorText>Error code longer than expected (4 bytes). Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid error code length</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (68))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_CALIBRATION_VALUE</Name>
    <ErrorCode>69</ErrorCode>
    <ErrorText>Invalid calibration value from EEPROM. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Host validation failure</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ModulesController</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (69))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>GANTRY_ALL_DIRECTION_NOTSUPPORTED</Name>
    <ErrorCode>70</ErrorCode>
    <ErrorText>All directions are not supported. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Host validation failure</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (70))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>GANTRY_DIRECTION_NOTSUPPORTED</Name>
    <ErrorCode>71</ErrorCode>
    <ErrorText>Directions are not supported. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Host validation failure</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (71))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>SAFEMOVE_FAIL_LID_BLOCKING</Name>
    <ErrorCode>72</ErrorCode>
    <ErrorText>Unable to move gantry to thermal cycler because the lid is closed. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Thermal Cycler lid is closed</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (72))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>SAFEMOVE_FAIL_UNDEFINED_ZONE</Name>
    <ErrorCode>73</ErrorCode>
    <ErrorText>Unable to move gantry into the illegal zone. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Gantry current position is not in defined safe zone.</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (73))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>SAFEMOVE_CURRENT_AT_UNDEFINED_ZONE</Name>
    <ErrorCode>74</ErrorCode>
    <ErrorText>Unable to move Gantry because it is in illegal zone. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Gantry aborted at position that not defined in safe zone.</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (74))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>SAFEHOME_UNABLE_TO_HOME_Y</Name>
    <ErrorCode>75</ErrorCode>
    <ErrorText>Unable to perform homing of the Y axis because the thermal cycler is in the way. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Gantry Y aborted on unsafe position to perform homing.</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (75))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>THERMAL_CYCLER_NOT_INITIALIZE</Name>
    <ErrorCode>76</ErrorCode>
    <ErrorText>Gantry is unable to go to thermal cycler because the thermal cycler is not initialized. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Thermal Cycler lid is not initialized.</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (76))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>MAGNET_SUPPORT_ONLY_X_Z_DIRECTION</Name>
    <ErrorCode>77</ErrorCode>
    <ErrorText>Only X or Z directions are supported. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Host validation failure</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (77))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>MAGNET_RUN_SPEED_OUT_OF_RANGE_1</Name>
    <ErrorCode>78</ErrorCode>
    <ErrorText>Magnet has encountered an error. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Unsupported magnet speed</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (78))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>HSM_UNABLE_REACH_COLUMN_1</Name>
    <ErrorCode>79</ErrorCode>
    <ErrorText>Gantry is unable to reach in intended column. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Unsupported column range</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (79))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_XML_FORMAT</Name>
    <ErrorCode>80</ErrorCode>
    <ErrorText>Unable to read the .xml file. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid thermal profile</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (80))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>PROFILE_IS_NULL</Name>
    <ErrorCode>81</ErrorCode>
    <ErrorText>Invalid .xml format. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Protocol (Thermal profile is not set)</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (81))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_PROFILE</Name>
    <ErrorCode>82</ErrorCode>
    <ErrorText>Unable to set profile. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid Protocol (Thermal profile)</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (82))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>SAFEMOVE_GANTRY_BLOCKING</Name>
    <ErrorCode>83</ErrorCode>
    <ErrorText>Unable move to that location due to gantry is blocking. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Gantry is on top of thermal cycler’s thermal block or Protocol file is invalid.</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (83))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>GANTRY_NOT_INITIALIZE</Name>
    <ErrorCode>84</ErrorCode>
    <ErrorText>Unable to perform operation because gantry has not been initialized. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Gantry is not initialized.</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (84))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>THERMAL_STATUS_NOTSUPPORTED</Name>
    <ErrorCode>85</ErrorCode>
    <ErrorText>Unable to set thermal status due to invalid parameters. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Unsupported thermal cycler status</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (85))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_THERMAL_DURATION_2</Name>
    <ErrorCode>86</ErrorCode>
    <ErrorText>Invalid thermal duration. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Unsupported thermal profile duration</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (86))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_THERMAL_ZONE</Name>
    <ErrorCode>87</ErrorCode>
    <ErrorText>Invalid thermal zone. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Unsupported thermal profile zone</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (87))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_COLOR</Name>
    <ErrorCode>88</ErrorCode>
    <ErrorText>Invalid color name. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Unsupported LED color</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (88))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_TIPS_SENSE_DURATION</Name>
    <ErrorCode>89</ErrorCode>
    <ErrorText>Invalid tips detection duration. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Unsupported tips detection duration</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (89))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>UNKNOWN_LOCK_STATUS_OF_INSTRUMENT_DOOR_1</Name>
    <ErrorCode>90</ErrorCode>
    <ErrorText>Unknown LockStatusOfInstrumentDoor. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Communication issue or instrument door sensor fault</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (90))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>UNABLE_TO_QUERY_LOCK_STATUS</Name>
    <ErrorCode>91</ErrorCode>
    <ErrorText>Unable to query lock status. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Communication issue or instrument door sensor fault</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (91))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>TIPS_DETECTION_FAIL</Name>
    <ErrorCode>92</ErrorCode>
    <ErrorText>Unable to detect tips. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Teaching position is inaccurate or Power Miscellaneous module is not responding</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (92))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>FAIL_GET_TEACHING_INFO</Name>
    <ErrorCode>93</ErrorCode>
    <ErrorText>Fail to get teaching info for this layout. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Might be connection issue. Fail to download teaching info</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (93))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>FAILED_RESET</Name>
    <ErrorCode>94</ErrorCode>
    <ErrorText>Unable to reset firmware. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Fail to reset firmware from error</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (94))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_THERMAL_DIMENSION</Name>
    <ErrorCode>95</ErrorCode>
    <ErrorText>Invalid thermal dimension. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Unsupported thermal dimension</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (95))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>PIPETTE_IS_BUSY</Name>
    <ErrorCode>96</ErrorCode>
    <ErrorText>Pipette is busy on another operation. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Pipette is currently in used.</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (96))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>INVALID_GANTRY_Z_VALUE</Name>
    <ErrorCode>97</ErrorCode>
    <ErrorText>Gantry Z go to location's value is over Gantry Z motor max range value. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Gantry Z go to position is invalid. Incorrect teaching position or invalid Gantry Z resolution.</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (97))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>INVALID_GANTRY_Y_VALUE</Name>
    <ErrorCode>98</ErrorCode>
    <ErrorText>Gantry Y go to location's value is over Gantry Y motor max range value. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Gantry Y go to position is invalid. Incorrect teaching position or invalid Gantry Y resolution.</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (98))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>INVALID_INVOKE_PROCESSID</Name>
    <ErrorCode>99</ErrorCode>
    <ErrorText>Invalid invoke process ID. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invoke Process or Condition Invoke operation is null or invalid.</PossibleCause>s
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (99))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>BARCODE_NULL_OF_SYSTEM</Name>
    <ErrorCode>100</ErrorCode>
    <ErrorText>Barcode not exist in system module. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Host validation failure</PossibleCause>s
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (100))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>WASTE_BIN_DOOR_OPEN</Name>
    <ErrorCode>101</ErrorCode>
    <ErrorText>Waste bin is open. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Waste bin is opened or waste bin sensor is not functioning</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (101))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>GANTRY_NULL_OF_BARCODE</Name>
    <ErrorCode>102</ErrorCode>
    <ErrorText>No Gantry module found in barcode module. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>System</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (102))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>INVALID_BARCODE_CONFIGURATION_FILE</Name>
    <ErrorCode>103</ErrorCode>
    <ErrorText>Invalid configuration. Unable to find barcode calibration. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Configuration file is not loaded</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (103))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>FAIL_GET_STATION_PROPERTY</Name>
    <ErrorCode>104</ErrorCode>
    <ErrorText>Unable to get station property from AutoTeachInfo file. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Deck station is not supported</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (104))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>UNSUPPORTED_LENGTH</Name>
    <ErrorCode>105</ErrorCode>
    <ErrorText>Unsupported length. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid input</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (105))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>FAIL_GET_GANTRY_RESOLUTION</Name>
    <ErrorCode>106</ErrorCode>
    <ErrorText>Failed to get gantry resolution. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Gantry Y offline or CAN bus disconnected</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (106))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>FAIL_GET_LAYOUT_VERSION</Name>
    <ErrorCode>107</ErrorCode>
    <ErrorText>Failed to get layout version. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Gantry Y offline or CAN bus disconnected or layout version not programmed</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (107))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>FAIL_GET_MIN_MAX</Name>
    <ErrorCode>108</ErrorCode>
    <ErrorText>Failed to get gantry min max. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Gantry Y offline or CAN bus disconnected</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (108))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>FAIL_GET_TEACHAREA</Name>
    <ErrorCode>109</ErrorCode>
    <ErrorText>Failed to get teach area. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Gantry Y offline or CAN bus disconnected or layout version not programmed</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (109))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>FAIL_UPDATE_ILLEGAL_ZONE</Name>
    <ErrorCode>110</ErrorCode>
    <ErrorText>Failed to update illegal zone. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid illegal zone values</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (110))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>NO_CONFIGURATION_FILE</Name>
    <ErrorCode>111</ErrorCode>
    <ErrorText>No configuration file is loaded. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Runtime error by application</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (111))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>FAIL_GET_LAYOUT_DEFINITION</Name>
    <ErrorCode>112</ErrorCode>
    <ErrorText>Unsupported layout version. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>Invalid layout version</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (112))</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>
      GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,
      PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,
      HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE
    </ModuleName>
    <Name>ABORTED_OPERATION</Name>
    <ErrorCode>113</ErrorCode>
    <ErrorText>Aborted operation. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>SYSTEM_ERROR</ErrorType>
    <PossibleCause>User aborted operation</PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Touchscreen-Specific Errors session, Error ID (113))</ProposedAction>
  </ErrorHandlingData>
  <!-- ###################################System errors##################################### -->

  <!-- ###################################Warnings ##################################### -->
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>WARNING_PROTOCOLVAR_NOT_SUPPORTED</Name>
    <ErrorCode>1</ErrorCode>
    <ErrorText>Protocol code is not supported. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>WARNING_TUNINGVAR_NOT_SUPPORTED</Name>
    <ErrorCode>2</ErrorCode>
    <ErrorText>Tuning code is not supported. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>WARNING_GETVAR_NOT_SUPPORTED</Name>
    <ErrorCode>3</ErrorCode>
    <ErrorText>GetVar code is not supported. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>WARNING_SETVAR_NOT_SUPPORTED</Name>
    <ErrorCode>4</ErrorCode>
    <ErrorText>SetVar code is not supported. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>WARNING_DATALOG_PARAM_NOT_SUPPORTED</Name>
    <ErrorCode>5</ErrorCode>
    <ErrorText>DataLog code is not supported. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>WARNING_BUSY_NOT_PREF_CMD</Name>
    <ErrorCode>6</ErrorCode>
    <ErrorText>Module is busy. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>WARNING_RECEIVE_PAYLOAD_NOT_SUPPORTED</Name>
    <ErrorCode>7</ErrorCode>
    <ErrorText>Received payload is not supported. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>WARNING_DATALOG_TOTAL_PARM_EXCEEDED</Name>
    <ErrorCode>8</ErrorCode>
    <ErrorText>DataLog total parameters has exceeded. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>WARNING_DATALOG_BUFFER_UNDERFLOW</Name>
    <ErrorCode>9</ErrorCode>
    <ErrorText>DataLog buffer underflow. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>WARNING_COMMAND_NOT_SUPPORTED</Name>
    <ErrorCode>10</ErrorCode>
    <ErrorText>Command is not supported. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Module-Specific Errors session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>WARNING_INVALID_STAT</Name>
    <ErrorCode>11</ErrorCode>
    <ErrorText>Invalid status. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>WARNING_ERROR_STAT</Name>
    <ErrorCode>12</ErrorCode>
    <ErrorText>Error status. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>WARNING_PAYLOAD_LENGTH_NOT_SUPPORTED</Name>
    <ErrorCode>13</ErrorCode>
    <ErrorText>Payload length not supported. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>WARNING_PRODVAR_NOT_SUPPORTED</Name>
    <ErrorCode>14</ErrorCode>
    <ErrorText>ProdVar not supported. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,GANTRY_X,GANTRY_Y,GANTRY_Z</ModuleName>
    <Name>WARNING_SYNC_CMD_NOT_RECV</Name>
    <ErrorCode>15</ErrorCode>
    <ErrorText>Synchronized command has not been received. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,GANTRY_X,GANTRY_Y,GANTRY_Z</ModuleName>
    <Name>WARNING_SYNC_BROADCAST_MULTI_RECV</Name>
    <ErrorCode>16</ErrorCode>
    <ErrorText>Multiple Synchronized commands have been received. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_PARAM1_EXCEEDED</Name>
    <ErrorCode>32</ErrorCode>
    <ErrorText>Parameter 1 exceeds the limit. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings sessionn)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_PARAM1_BELOW</Name>
    <ErrorCode>33</ErrorCode>
    <ErrorText>Parameter 1 is below the limit. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_PARAM2_EXCEEDED</Name>
    <ErrorCode>34</ErrorCode>
    <ErrorText>Parameter 2 exceeds the limit. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_PARAM2_BELOW</Name>
    <ErrorCode>35</ErrorCode>
    <ErrorText>Parameter 2 is below the limit. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_DUTY_EXCEEDED</Name>
    <ErrorCode>36</ErrorCode>
    <ErrorText>Duty exceeds the limit. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_DUTY_BELOW</Name>
    <ErrorCode>37</ErrorCode>
    <ErrorText>Duty is below the limit. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_DATALOG_NONEED_SAVED</Name>
    <ErrorCode>48</ErrorCode>
    <ErrorText>Datalog does not need to be saved. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_DATALOG_PARAM_UNINIT</Name>
    <ErrorCode>49</ErrorCode>
    <ErrorText>Datalog parameter is not initialized. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_DATALOG_PARAM_NOT_SET</Name>
    <ErrorCode>50</ErrorCode>
    <ErrorText>Datalog parameter is not set. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_DATALOG_PARAM_NOT_SUPPORTED</Name>
    <ErrorCode>51</ErrorCode>
    <ErrorText>Datalog parameter is not supported. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_DATALOG_OUT_OF_RANGE</Name>
    <ErrorCode>52</ErrorCode>
    <ErrorText>Datalog is out of range. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_TOTAL_PARAM_EXCEEDED</Name>
    <ErrorCode>53</ErrorCode>
    <ErrorText>Datalog total parameter has been exceeded. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_DATALOG_BUFFER_UNDERFLOW</Name>
    <ErrorCode>54</ErrorCode>
    <ErrorText>Datalog buffer underflow. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_DATALOG_ENQUEUE_FAILED</Name>
    <ErrorCode>55</ErrorCode>
    <ErrorText>Datalog buffer underflow. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_DATALOG_RESET_FAILED</Name>
    <ErrorCode>56</ErrorCode>
    <ErrorText>Datalog reset has failed. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,PIPETTE,PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z</ModuleName>
    <Name>STAT_MOTOR_ROTATION_COUNT_OVERFLOW</Name>
    <ErrorCode>80</ErrorCode>
    <ErrorText>Motor rotation count overflow. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>POWER_MISC</ModuleName>
    <Name>STAT_UV_ELAPSED_TIME_OVERFLOW</Name>
    <ErrorCode>81</ErrorCode>
    <ErrorText>UV elapsed time overflow. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_NOT_MOVING</Name>
    <ErrorCode>112</ErrorCode>
    <ErrorText>Not moving. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_TIMEOUT</Name>
    <ErrorCode>113</ErrorCode>
    <ErrorText>Module timeout. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_FW_TIMEOUT</Name>
    <ErrorCode>114</ErrorCode>
    <ErrorText>Firmware timeout. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_HW_TIMEOUT</Name>
    <ErrorCode>115</ErrorCode>
    <ErrorText>Hardware timeout. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_HOST_TIMEOUT</Name>
    <ErrorCode>116</ErrorCode>
    <ErrorText>Host timeout. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_DATA_MISMATCHED</Name>
    <ErrorCode>117</ErrorCode>
    <ErrorText>Data mismatched. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_NO_DATA</Name>
    <ErrorCode>118</ErrorCode>
    <ErrorText>No Data. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_HW_UART_RX_FAULT</Name>
    <ErrorCode>119</ErrorCode>
    <ErrorText>Hardware UART RX Fault. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_HW_SETUP_FAULT</Name>
    <ErrorCode>120</ErrorCode>
    <ErrorText>Hardware UART RX Fault. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_HW_UART_TX_FAULT</Name>
    <ErrorCode>121</ErrorCode>
    <ErrorText>Hardware UART TX Fault. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_HW_REV_NOT_SUPPORTED</Name>
    <ErrorCode>122</ErrorCode>
    <ErrorText>Hardware revision is not supported. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_HW_NOT_SUPPORTED</Name>
    <ErrorCode>123</ErrorCode>
    <ErrorText>Hardware is not supported. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>PIPETTE,BARCODE,POWER_MISC</ModuleName>
    <Name>STAT_HW2_REV_NOT_SUPPORTED</Name>
    <ErrorCode>124</ErrorCode>
    <ErrorText>Hardware2 revision is not supported. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>STAT_HW_SETTING_NOT_MATCH</Name>
    <ErrorCode>125</ErrorCode>
    <ErrorText>Hardware settings do not match. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>CHILLER_1</ModuleName>
    <Name>STAT_CHILLER_DOOR_UNLATCHED</Name>
    <ErrorCode>128</ErrorCode>
    <ErrorText>Chiller door is unlatched. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>STAT_IMAGE_IN_CAMERA_NOT_FOUND</Name>
    <ErrorCode>144</ErrorCode>
    <ErrorText>Image from camera cannot be found. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>STAT_IMAGE_RETRIEVE_ERROR</Name>
    <ErrorCode>145</ErrorCode>
    <ErrorText>Image from camera cannot be retrieved. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>STAT_BARCODE_STATUS_BUSY</Name>
    <ErrorCode>146</ErrorCode>
    <ErrorText>Barcode module is busy. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>STAT_JOB_WRITE_START_ERROR</Name>
    <ErrorCode>147</ErrorCode>
    <ErrorText>Barcode start write job error. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>BARCODE</ModuleName>
    <Name>STAT_NO_CAMERA_XMODEM_OPERATION_ONGOING</Name>
    <ErrorCode>148</ErrorCode>
    <ErrorText>No camera xmodem operation is on going. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
  <ErrorHandlingData>
    <ModuleName>GANTRY_X,GANTRY_Y,GANTRY_Z,HSM_SHAKER,PIPETTE,PCR,HSM_HEATER,CHILLER_1,PCR_HOTTOP_X,PCR_HOTTOP_Z,HSM_MAGNET_X,HSM_MAGNET_Z,POWER_MISC,BARCODE</ModuleName>
    <Name>UNDEFINED_WARNING</Name>
    <ErrorCode>255</ErrorCode>
    <ErrorText>Undefined warning. Reboot the system. Contact Technical Support if the problem persists.</ErrorText>
    <ErrorType>FIRMWARE_WARNING</ErrorType>
    <PossibleCause></PossibleCause>
    <ActionType>StopProtocol</ActionType>
    <ActionLevel>ProtocolHandler</ActionLevel>
    <ProposedAction>Refer to troubleshooting guide document, Runtime Errors (Warnings session)</ProposedAction>
  </ErrorHandlingData>
</ErrorLibrary>
