Empower error connected to Agilent 1100/1200 stack

[jtoshea2005]

HI
I am recieving a "Agilent LC communication error, waiting on single object_timeout" error after starting a sequence. I can control the agilent through empower, no problem but when I hit start in empower, it gives me the error after 20 seconds every time. There is no noise (startup sounds from the autosampler.

Other methods duplicate this error, so it is not method specific. I tried taking offline and back online, no luck.
I tried deleting instrument and re-scanning it from "scan Instruments in the empower nodes section under "systems" no luck

any suggestions?
the stack is 1100 pump, and the rest are 1200 modules. It is connected to Lace box, and everything has been re-booted.

thanks

[DR]

Ethernet or serial connection?

My first guess is that there is something not ready among the Agilent components. Check the handheld controller (gameboy) for any errors and such.

My next guess is that perhaps a thermostatted component is still sending data to Empower and needs to be told not to do that. A thermostatted ALS or column compartment can hold up Empower as can an "error if empty" solvent bottle fill monitor setting.

[jtoshea2005]

It is ethernet connection. Communicating fine. Good idea, it has a FC/ALS G1330B thermostat compartmentwhich has no LAN input, just seial to adjacent module. How do I disable communication to just that module?

[DR]

from welcome screen on Agilent hand held controller for 1200 systems:
More, Configure, Autosampler
select "Temp Not Ready" --->OFF

Good luck.

[johnwu]

Has the issue resolved yet? Anyway, I encountered similiar issues recently but with a HP 1100 stack. We're not sure exactly what and where the problem was, but it seems pc related. It simply won't work for certain pc models.

[EmpowerGuru]

we get the same error occasionally but we also get an error that there has been a configuration change and that the system should be re-identified. we have gotten this mid run

[johnwu]

We don't see these errors anymore once we moved to a different pc. Unfortunately we have no time or interests in digging out the root cause (we had wasted many hours in computer rather than MS with a previous Waters MassLynx experience).