Skip Navigational Links
LISTSERV email list manager
LISTSERV - LIST.UVM.EDU
LISTSERV Menu
Log In
Log In
LISTSERV 17.5 Help - ISOGEOCHEM Archives
LISTSERV Archives
LISTSERV Archives
Search Archives
Search Archives
Register
Register
Log In
Log In

ISOGEOCHEM Archives

Stable Isotope Geochemistry

ISOGEOCHEM@LIST.UVM.EDU

Menu
LISTSERV Archives LISTSERV Archives
ISOGEOCHEM Home ISOGEOCHEM Home

Log In Log In
Register Register

Subscribe or Unsubscribe Subscribe or Unsubscribe

Search Archives Search Archives
Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
Stable Isotope Geochemistry <[log in to unmask]>
Date:
Wed, 9 Feb 2000 09:51:47 +0100
Reply-To:
Stable Isotope Geochemistry <[log in to unmask]>
Subject:
Re: ISODAT error messages
MIME-Version:
1.0
Content-Transfer-Encoding:
7bit
Content-Type:
text/plain; charset=us-ascii; x-mac-type="54455854"; x-mac-creator="4D4F5353"
Organization:
Paul Scherrer Institut
From:
Rolf Siegwolf <[log in to unmask]>
Parts/Attachments:
text/plain (79 lines)
We too were confronted with these errors and error messages with all the

described consequences. After recording all the error messages with date

and documentation of the circimstances, and after trying all the hints
we got
from Finnigan we contacted Bremen again.
The remedy: We got the newest version of ISODAT, replaced our PC with
a UNISYS 66MHz and changed to the operating system REAL 32.
Since then it works and the error messages have practically disappeared.

My suggestion: install REAL 32 and the newest Version of ISODAT
from scratch (NO patches etc) and you will most likely have peace.
Make sure your PC hardware is OK, clones and cheep brand products
might be an other source of problems.

Good Luck

Rolf



 Kendra Turk wrote:

> Hello all,
>
>         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)
> Adr: 419
>
> and
>
> Modul# 20133
> Error #6
> RT: Bounds exceeded (B)
> Adr:955h
>
>         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...
>
> Thanks,
> Kendra
> _________________________
>    Kendra Turk
>    NASA/Ames Research Center
>    Mail Stop 239-4
>    Moffett Field, CA  94035
>     650-604-1430 (voice mail)
>     650-604-6110 (lab)
>    [log in to unmask]

--
_______________________________________________________

 Dr. Rolf Siegwolf
 Laboratory of Atmospheric Chemistry
 Stable Isotope Research Group / Ecosystem Fluxes
 Paul Scherrer Institute
 CH-5232 Villigen-PSI
 Switzerland
 Phone  : +41 (0)56 310 27 86
 Fax      : +41 (0)56 310 45 25
 e-mail  :  [log in to unmask]
_______________________________________________________

ATOM RSS1 RSS2

LIST.UVM.EDU CataList Email List Search Powered by LISTSERV