Data Collection Stops Early - Instrument Failures - Empower 2 busSAT/IN

GPK
GPK
in Software Products
<p>Has anyone experienced issues with data collection stopping early in Empower 2? We've observed several chromtagraphy runs stop collecting a minute or so early. Typically there are no signs of instrument failure, although we observed one run stop 1 minute early for one injection, two minutes early for the subsequent injection and fail altogether in the next injection. So far there have been no observed issues with the related instruments and their programmed run times. This group is using busSAT/IN's only, no software/instrument control. It appears that data collection may be starting later than expected based on the elution profile on the chromatograms. </p><p></p><p>We've also experienced "instrument failures" of busSAT/INs with no assignable cause. They are displayed as "Instrument Failure: Unspecified Instrument", Instrument Failure" or Instrument Failure <a href="mailto:SAT/IN@1">SAT/IN@1</a> in the Message Center. These runs frequently run to completion on the instrument, but data collection stops altogether in Empower 2. Waters has not been able to identify any causes of these issues so far. </p><p>Thanks for any knowledge that you can pass on. </p>

Comments

  • GSS123
    GSS123

    Hello,

    We may need to gather a little more information in order to assist you with this issue.

    Since it does not happen on every run, how often does the run stop early?

    Using the Empower 2 Pro interface, go to the Empower Nodes, select the Empower Node where the busSAT/IN module is configured then right click and select properties. On the instrument tab in the node properties window locate the SAT/IN@1 for example then scroll to the right and note the revision of firmware. What is the revision?

    "Instrument Failure: Unspecified Instrument" or "Instrument Failure:SAT/IN@1" in the Message Center may indicate the cables should be checked and possibly the instrument itself .

    A test can be performed but very carefully so not to permanently damage the busSAT/IN module.

    1. Deconfigure the SAT/IN modules from the serial ports by setting it to NOSAT/IN.

    2. Disconnect cable from wall - Important! Never disconnect power cable from DIN connector. Disconnect only from the wall socket.

    3. Reboot the LAC/E32

    4. Reconnect power cable cable to the wall socket.

    5. Reconfigure the SAT/IN modules in the serial ports.

    This test will allow the firmware to be refreshed to busSAT/IN module.

    I hope this helps.

  • GPK
    GPK

    Since it does not happen on every run, how often does the run stop early?

    -We are still determining this. It has occurred on an additional injection on a subsequent run since the initial observation.

    Using the Empower 2 Pro interface, go to the Empower Nodes, select the Empower Node where the busSAT/IN module is configured then right click and select properties. On the instrument tab in the node properties window locate the SAT/IN@1 for example then scroll to the right and note the revision of firmware. What is the revision?

    -20.0

    "Instrument Failure: Unspecified Instrument" or "Instrument Failure:SAT/IN@1" in the Message Center may indicate the cables should be checked and possibly the instrument itself .

    -There have been other issues on this same LACE with a several different systems. We've replaced all cabling and have used several SAT/IN's. To date, no issues have been found with the instrument that we can see.

    A test can be performed but very carefully so not to permanently damage the busSAT/IN module.

    1. Deconfigure the SAT/IN modules from the serial ports by setting it to NOSAT/IN.

    2. Disconnect cable from wall - Important! Never disconnect power cable from DIN connector. Disconnect only from the wall socket.

    3. Reboot the LAC/E32

    4. Reconnect power cable cable to the wall socket.

    5. Reconfigure the SAT/IN modules in the serial ports.

    This test will allow the firmware to be refreshed to busSAT/IN module.

    -We've replaced the LAC/E32 as of yesterday which essentially does everything you describe. We'll see if this makes a difference. If it does, we'll likely request a replacement of the busLACE card.

    Thanks

Categories