Varian Module 325 UV Detector Error

[DSV]

Hello,

Has anyone experienced the following Varian ProStar 325 module error message when running Galaxie?

COM_CC_DELAY_TOO_LONG_RE_INIT


I'm attempting to run a semi-prep SEC separation self packed low/medium pressure glass column. Run times are very long (6 hours, @0.3mL/min), which might be the source of the problem I’ve been experiencing recently, which is as follows. If I run a sequence of 5 injections (~30 hours run time) the first injection works. The following 1 or 2 injections actually “injectâ€

[Chris0000]

Maybe you can solve this with trying this:

In your Method change every 30 minutes the wavelength for one minute:
For example:
Initial: 220nm
30min: 225nm
31min 220nm
and so on...

I think the communication between the Detector and the software ist lost with that long run time, so if we can send some commands to the detector, the communication will hopefully stay alive.

Another common possibillity are the energy saving settings under Windows
I would just disable all except of the screen saver

Best regards
Christian

[DSV]

Thanks for your suggestions Christian. Attempted to run another sequence over yesterday and last night with the 6 hour run time and the 30 minute wavelength changes, but unfortunately to no avail! Interestingly (up to a point, anyway!), is that the first wavelength change (in my case from 280nm to 290nm) occured fine, but then the wavelength change back to 280nm didn't happen. So perhaps even a 30 minute communication frequency between Galaxie and the UV module is too long. I'll set it up again but with 10 minute wavelength changes, but I can't help but think that I'm flogging a dead horse. I'll go through the energy saving options on the PC again, but I'm certain that those are set correctly for Galaxie. I'll post updates as and when anything new happens.
Dan.

[Chris0000]

another possible reason is an old GPIB driver for the pump - I was faced to hangups with an old driver - In this case the detector error would be only a symptom of the hangup

You can check for an Driver update at national Instruments

Best regards
Christian

[DSV]

Hello again! I did the GPIB driver update suggested by Christian, which went suprisingly well. Incidentally the driver that was updated was from 2004, and the latest one (as far as I could tell) which we're now using was from late-2009. I set up a new sequence to perform 10 x 6 hour runs, and as before the first one went fine, with the 2nd and 3rd injecting but not acquiring any data, and the whole thing collapsed competely at the 4th injection. I now have another problem in that I can't get the detector (325 module) online. Can't activate it through the Configuration, so checked all connections etc and there's nothing obviously wrong with the cables. The remote call proceedure fails too, so can't think of anything else to try, so if you've any further comments Christian, then feel free to post them! Varian are visiting at some point soon (but not soon enough given that we've a service contract) so it's over to them now. Dan.

[Chris0000]

This sounds not good

If the remote-procedure fail happend in the configuration manager after configuring your system (or looking for DET connection) - the system information might be corrupted
One way to solve this is to delete the system and create a new one with he same settings. You only should so this if you are used to the configuration manager - a wrong setting in the system can be fatal.

I would also check, if the fan of the detector is working, maybe heat might be the problem.

And I also want to point out, that if you have trouble with the galaxie and communication, for a restart, you have to reboot windows, just shutting down the software wont help.

I hope this did help you
Best regards
Christian