7890A / 5977B GC-MS Run Method Error & Error: Timeout - Download command timed out

Hello!

We have been encountering an issue with our GC-MS system that is connected to a Markes TD100-xr. Every maybe 6 months the following error has popped up: 

'Source: ManualMode. Message: Run Method Error - Consult Logbook.

Source: ManualMode. Message: Error: error: Timeout - Download command timed out; User aborted run.'

Last, it occured during a sequence, where it had succesfully run 127 samples, and then at sample 128 the error happened, and the instrument stopped. 

Here is the part of the error sequence info file where the error appears:
TST2AcqStart
TS2AcqStart$=reglangtime$(3)
2024-10-05T15:38:28+02:00
ts2AcqStart=time()
1.72814E+09
if eqstr(getinistring$("","PCS","universal"),"UNIVERSAL")=1
endif
return
RunStart 1
Run method initiated to collect 12801097.D
MSD:
Error: error: Timeout - Download command timed out
Download command timed out
5. oktober 2024 16:13:33
Macro: RUNMETHOD, Cmd: RunStart 1
Msg: Error: error: Timeout - Download command timed out


_ManualMode 1,_$(21451,"Run Method Error - Consult Logbook."),,1
print _error,_errmsg$
1 Error: error: Timeout - Download command timed out
local dattemp$,retvials$
dattemp$=_datafile$
12801097.D
ON_ERROR
local OK
if ErrorHappened <> 0
MMCheckError OK
local RD_Log
RD_Log = 0

It is a 7890A / 5977B GC-MS connected to a Windows 10 PC with MassHunter Acquisition10.1.49.

Surprisingly, the 7890A is configured as a 7890B, and I am unsure whether this might introduce some problems. I tried to reconfigure it as a 7890A, but it would not let me.

The reason why it is such a big issue is that the thermal desorption instrument and its software for some reason does not recognize that the GC-MS is in an error/not ready mode, and it keeps desorbing the tubes - and then they are lost for good.

Any ideas for things to try? Since the error only comes rarely, it is quite tricky to troubleshoot.

  • There is a remote start/stop/ready Y cable connected between the Markes, the GC, and the MS.  Is the Markes configured to look for the ready signal?  Did it used to work that way where the Markes would wait for system ready?  I'm guessing not - as it says "Manual Mode" in the logbook, so the Markes may be just going on time and pressing start so it doesn't know or care if the system is ready.

    Every six months?  You've rebooted the computer, MS, and GC somewhere in there? Microsoft recommends rebooting at least once a week.  Check the LAN card and CPU configuration for timeout, sleep, power save mode, etc.

    Please update to MassHunter Acquisition 10.2 SR3....that version has some fixes that everyone on 10.0 through 10.2 SR2 should have.

Was this helpful?