Discussions

Notifications
Clear all

Occasional autosampler glitch. ASC64

3 Posts
2 Users
0 Reactions
13 Views
Posts: 0
Guest
Topic starter
(@Anonymous)
Joined: 1 second ago

There is an occasional malfunction on the autosampler on the 500. It has happened twice and so far I haven’t found the cause.

 It causes samples to be put in the wrong slot when returned to the autosampler. 

Though it just means you need to restart the run, it could cause confusion with students who may end up taking the wrong samples.

  1. You see a failed to load or retrieve error and the queue probably stops.

    2. The last time it happened, the computer thought it was at position 38.

    3. The autosampler also thought it was it is at position 38, according to the number on the front panel.

    4. But the actual position was at 37.  That is where the laser on the carrier was pointing.

    5. Prior to failure it also caused the sample submitted from position 42 to end up in 41.

I got things operational and back on track by simply rotating the carousel, with the white light arrow buttons on the carousel, and resubmitting the failed experiment. The carousel did a reset and carried on as usual. However as it has only happen twice I have yet to find a cause.

Ian Stewart

2 Replies
Posts: 0
Guest
(@Anonymous)
Joined: 1 second ago

This has not happened in the previous version 5.2 of Delta.  Also on the last service visit the firmware was upgraded on the auto samplers which might have introduced a 'bug'.

It happened with our ASC64 autosampler as well.  In my case it picks up the sample n-1.  (submitted position -1).  Resubmitting did not resolve the problem. Also rotating the autosampler to a different position prior to submitting did not solve the problem. I am running the 'walkup mode' on Delta.

The only way I could bypass the problem which is not a fix is to submit sample position number 1 which seemed to reset the autosampler because position 0 does not exist.  Using the abort on the autosampler introduced other problems.

Hopefully we might get an engineer on this to help and solve this issue.

 

Reply
Posts: 0
Guest
(@Anonymous)
Joined: 1 second ago

This apparently was fixed during the last service visit.  Have a look at the lab manager section,.

Reply