GC-MSD Communications Error

Hi all,

This is a bit of misleading error. This command (MSC:SENS?QUAD) is used to check the quad temperature and is sent frequently between the PC/control software and the MS while the instrument is idle as well as when it is running. When the instrument is operating normally this command reads back the quad temperature-- If you lose communication between the MS and the PC for any reason it is likely that you will see this message as the first error simply because of how frequently this message is going back and forth between the PC and instrument. It does not mean that there is anything wrong with the heater/sensor, it just means that the software noticed it was no longer getting any responses back from the MS.

If this is happening frequently check to make sure the PC is not set to go to sleep, and check to make sure the ethernet adapter is not set to go to sleep/conserve energy. These settings are configured by default on an Agilent bundled PC but could be reset by windows update, or not configured correctly if a non-Agilent windows image was used.

If the error is very frequent I would consider checking a few other things that could interrupt the connection: are the ethernet cables old/damaged/dirty? They are cheap and easily replaced. Is the PC set to do virus checks or automated backups that occur around the same time as the problem? Is the PC experiencing any other problems that cause it to freeze or become unresponsive? The connection to the GCMS does not require a lot of bandwidth but any interruption will cause it to lose the connection.

Hi all,

This is a bit of misleading error. This command (MSC:SENS?QUAD) is used to check the quad temperature and is sent frequently between the PC/control software and the MS while the instrument is idle as well as when it is running. When the instrument is operating normally this command reads back the quad temperature-- If you lose communication between the MS and the PC for any reason it is likely that you will see this message as the first error simply because of how frequently this message is going back and forth between the PC and instrument. It does not mean that there is anything wrong with the heater/sensor, it just means that the software noticed it was no longer getting any responses back from the MS.

If this is happening frequently check to make sure the PC is not set to go to sleep, and check to make sure the ethernet adapter is not set to go to sleep/conserve energy. These settings are configured by default on an Agilent bundled PC but could be reset by windows update, or not configured correctly if a non-Agilent windows image was used.

If the error is very frequent I would consider checking a few other things that could interrupt the connection: are the ethernet cables old/damaged/dirty? They are cheap and easily replaced. Is the PC set to do virus checks or automated backups that occur around the same time as the problem? Is the PC experiencing any other problems that cause it to freeze or become unresponsive? The connection to the GCMS does not require a lot of bandwidth but any interruption will cause it to lose the connection.