Communication timeout UV detector in Chromeleon
Posted: Fri Jun 09, 2023 6:16 pm
I am running chromeleon 7.3 on a spectrasystem HPLC (all parts model numbers: degasser SCHM1000, pump P100, autosampler AS3000, UV detector UV6000LP).
When I try to run a sequence the UV connection suddenly goes off after a warning message that says: "A communication timeout occurred while waiting for device answer in OnStoreMeth". This doesn't always happen, sometimes 1-2 samples run without a problem and it only appears when starting the 3rd sample. It seems that the error occurs not only at the start of a run but can also happen in-between (one of my runs of 13min stopped after only 4). The system retries to establish connection and the same message appears like 4times. Then an error message appears: "A communication timeout occurred while waiting for device answer in TaskSetMeth". The method is aborted.
This has only started to happen today and I am not sure why. The cables are fine and the UV reconnects within seconds, but will disconnect again if I try to resume the sequence and will produce the same messages again.
Does anyone have an idea why this can happen? Or even just what the error/warning messages really mean?
When I try to run a sequence the UV connection suddenly goes off after a warning message that says: "A communication timeout occurred while waiting for device answer in OnStoreMeth". This doesn't always happen, sometimes 1-2 samples run without a problem and it only appears when starting the 3rd sample. It seems that the error occurs not only at the start of a run but can also happen in-between (one of my runs of 13min stopped after only 4). The system retries to establish connection and the same message appears like 4times. Then an error message appears: "A communication timeout occurred while waiting for device answer in TaskSetMeth". The method is aborted.
This has only started to happen today and I am not sure why. The cables are fine and the UV reconnects within seconds, but will disconnect again if I try to resume the sequence and will produce the same messages again.
Does anyone have an idea why this can happen? Or even just what the error/warning messages really mean?