[Adam Y.]

During recent utilization of the spectrometer the device attempted to execute a number of standard operations, with anomalous results. When the sensor payload software attempted to turn on the payload FPGA, the FPGA failed to power on before the FPGA Power On Timer timed out. Subsequently, the payload software issued a MTES image command. The MTES image command failed due to an MTES interface timeout. Further MTES image commands failed similarly, and generated several more instances of the FPGA Power On Timer timeout EVR. A fault EVR was then generated due to the failure of the PMA azimuth actuator to move. However, since there is a hardware level handshake between MTES and PMA, this is likely to be a secondary failure due to the failure of the FPGA to power on during the original attempt. Initial analysis of the anomaly indicates it is likely due to an insufficient interval between the MTES_ABORT_IMAGE command from e3383 and the subsequent MTES_IMAGE command from p3576. If the timing is "just right", the pyld software can be put into a state such that all subsequent attempts to power the FPGA will fail. Only a reboot clears the condition. We are currently attempting to recreate the anomaly on the spare backup robot to better understand the condition. In the interim, use of the APXS and other spectrometers, as well as the PMA, is precluded until the anomaly is resolved.

Give me five years and I may be able to answer that question. All I know now is that you used a lot of acronyms. So many acronyms. Maybe you should whack it a few times with a hammer. That always seems to fix our robots. By the way I was refering to sensors that you would find on FIRST robots. Nothing you would find in outerspace.