On five separate occasions in the last month or so, we have
had overnight EA sequences halted due to one of two ISODAT errors:
Modul # 33283
Error # 90
RT: Devision by zero (Z)
RT: Bounds exceeded (B)
I have received the former message in scenarios where no
sample or reference gas peaks were detected. In this case, however,
behind the error message, peaks in both the ratio and isotope traces
have been clearly visible.
More baffling, however, is the latter error message. In the
case where I have observed this misbehavior, the sample was combusted
and the nitrogen data was acquired as expected. It was during the
CO2 analysis that this message occurred. Despite the absence of the
44 and ratio traces,the software stopped the data acquisition at the
designated time, and choked when there was no data.
If anyone has experienced anything similar, or has some sort
of idea what could cause such errors, please contact me directly...
NASA/Ames Research Center
Mail Stop 239-4
Moffett Field, CA 94035
650-604-1430 (voice mail)
[log in to unmask]