Replacing all the plate-type detection sensors on the autosampler did
the trick for us. Well, I think it did. We aren't getting that error
anymore. Time will tell.
By the way, if you are under warranty or have a service contract, you
can just contact the service dept. of ABI and open a service call. Then
your engineer will contact you within a few (working) hours.
Fulton, Ciaran wrote:
> Hi Philip...ironically we were just discussing the same error message
> that occurred on our 48-cap (3730) machine a week ago. This happened
> after the first half of the plate had been processed. The water tray had
> moved under the array and the machine just hung after generating this
> error message which was rather bizarre given that it was processing the
> same plate. No instrument warning light was observed and the error
> hasn't occurred subsequently. I'm sorry I can't shed anymore light on
> the matter Philip, nor have ABI technical support (I'm still waiting for
> them to return my call).
>>>> -----Original Message-----
> 1. DNA SEQ: 3730XL Tray on deck error (Phillip San Miguel)
>>> Message: 1
>> Date: Tue, 15 Nov 2005 13:45:18 -0500
>> From: Phillip San Miguel <pmiguel at purdue.edu>
>> Subject: [Automated-sequencing] DNA SEQ: 3730XL Tray on deck error
>> To: bionet-genome-autosequencing at moderators.isc.org>> Message-ID: <437A2CBE.4090708 at purdue.edu>
>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>>> We keep running into a maddening error on our 3730XL:
>>>> Tray on deck does not match tray type in run setup
>>>> Maddening because this error usually happens in the middle of a batch of
>> runs from a 384-well plate. That is, the first or first few quads get
>> loaded and run fine. Then the batch errors out.
>>>> Usually it requires a service call to get the machine running again. But
>> I'm not entirely sure that the service call is what "fixes" the problem.
>> It might be turning the machine off for a couple of days. (An hour isn't
>> long enough. I just tried it.)
>>>> Replacing the plate sensor is among the methods that gets us running
>> again--for a time. But looking through old 3730.log files I can see 4
>> times that this has shut us down for a couple of days since the middle
>> of the summer.
>>>> Last time it coincided with our laser going out. The laser was replaced
>> and we ran for four days. Only to see this error pop up again.
>>>> Any ideas?