Fatal Sequence Error Detected

Question

7890A GC / 5975C MS tandem system

The log file shows 'Fatal sequence error detected after a run is complete and there is no chromatogram/MS data available for the sample. Can anyone help with what the cause might be?

assumed_answered · Accepted Answer

This question has been marked as assumed answered.

james_jenkins · Answer

Hi Tom,

Do you perhaps see "neither GC or MS data collected" ? If so, check your remote cable from you GC to your MSD to be sure its connected. If that looks ok, then close chemstation and restart the MSD using the keypad on the front. Press the menu key until you see the word controller, press the item key and you will be prompted to restart by pressing the yes key. This is a nice way of restating the MSD without interrupting the vacuum system. Once restarted, try and run a short sequence as a test. If this works, let us know and I may have an idea why this happened.

Regards

James

tom.hodsden · Answer

Hi James,

Thanks for the quick response. I've rebooted the MSD via the keypad and now everything is working again.

Thanks for the help.

Regards,

Tom

james_jenkins · Answer

Hi Chris,

There is a version of firmware out there that has a timer that runs approx 49 days, give or take. The timer is meant for some house keeping on the smart card but in inadvertently disables the remote start. The MSD will tune, but you will never see a solvent delay or MSD run start. The issue can be intermittent with a smart card 3.2 and firmware 5.02.09.

Regards

James

chris.sparks · Answer

Thanks James,

Yes, yesterday I reseated all the communication cables and restarted the MSD per your original comment in this thread. We had several successful runs last night, but I'm just hoping to avoid any lost data issues in the future.

I was in the back of this instrument last week changing the micro ion gauge, maybe I jostled a cable doing that.

cheers,

Chris

chris.sparks · Answer

This happened again to us last night, restarting the MSD and checking connections per james_jenkins first suggestion did the trick again. I did have to search these archives to run across the "fix" again though.

Fatal Sequence Error Detected

Top Replies