Chromatography Forum

Finally swapped out the god forbid VWD for a DAD we have on hand to see if that would get Analyst to finally recognize the entire setup. Still no go. Here are the things I have had to do:

1. Change the hardware IP from the one the VWD used (10.10.10.2) to the DAD one (10.10.10.54)
2. Reestablish GPIB communication between instrument and computer using National Instrument programs
3. Use Analyst software and test individual moduals of the LC system
4. Pump, auto sampler, column comp all activate with profile and detector fails

I was thinking it could be a software glitch since I had some trouble with the GPIB yesterday and had to remove the drivers and reinstall. Would uninstalling Analyst 1.4.2 (including all hotfixes) and reinstalling be a worthwhile thing to do? Any help would be greatly appreciated!

Finally swapped out the god forbid VWD for a DAD we have on hand to see if that would get Analyst to finally recognize the entire setup. Still no go. Here are the things I have had to do:

1. Change the hardware IP from the one the VWD used (10.10.10.2) to the DAD one (10.10.10.54)
2. Reestablish GPIB communication between instrument and computer using National Instrument programs
3. Use Analyst software and test individual moduals of the LC system
4. Pump, auto sampler, column comp all activate with profile and detector fails

I was thinking it could be a software glitch since I had some trouble with the GPIB yesterday and had to remove the drivers and reinstall. Would uninstalling Analyst 1.4.2 (including all hotfixes) and reinstalling be a worthwhile thing to do? Any help would be greatly appreciated!

I didn't have any trouble with setting one up on our system but I was using a serial connection for the LC stack and only using the GPIB for the Mass Spec(API3200)

I have the serial cable going to the autosampler and then connect the rest of the units together with the CAN cables and it sees it ok. Sometimes it will fail to recognize the LC and I just have to power cycle the stack and kill the Analyst process running in the background then restart and all is good.

Another trick I have found, if you get an error and something pops red in the status bar which usually means you have to restart Analyst to clear the error, if you just loosen the probe until you hear the click that indicates it thinks the probe is removed, wait a couple seconds then tighten it back up and hear the click again where it thinks a new probe is installed, it clears out any errors without needing to shutdown the software.

Finally swapped out the god forbid VWD for a DAD we have on hand to see if that would get Analyst to finally recognize the entire setup. Still no go. Here are the things I have had to do:

1. Change the hardware IP from the one the VWD used (10.10.10.2) to the DAD one (10.10.10.54)
2. Reestablish GPIB communication between instrument and computer using National Instrument programs
3. Use Analyst software and test individual moduals of the LC system
4. Pump, auto sampler, column comp all activate with profile and detector fails

I was thinking it could be a software glitch since I had some trouble with the GPIB yesterday and had to remove the drivers and reinstall. Would uninstalling Analyst 1.4.2 (including all hotfixes) and reinstalling be a worthwhile thing to do? Any help would be greatly appreciated!

I didn't have any trouble with setting one up on our system but I was using a serial connection for the LC stack and only using the GPIB for the Mass Spec(API3200)

I have the serial cable going to the autosampler and then connect the rest of the units together with the CAN cables and it sees it ok. Sometimes it will fail to recognize the LC and I just have to power cycle the stack and kill the Analyst process running in the background then restart and all is good.

Another trick I have found, if you get an error and something pops red in the status bar which usually means you have to restart Analyst to clear the error, if you just loosen the probe until you hear the click that indicates it thinks the probe is removed, wait a couple seconds then tighten it back up and hear the click again where it thinks a new probe is installed, it clears out any errors without needing to shutdown the software.

One thing I forgot to mention is that this is an inherited machine. I have all the parts needed to make it work and I just can't do it. There isn't an extra serial port on the computer and a serial cable wasn't included so I think thats a no go?

It is odd that Analyst just would not recognize the DAD at all. It just hangs when I try and activate the profile and after several minutes it would say Failed to activate: Agilent Detector.

Finally swapped out the god forbid VWD for a DAD we have on hand to see if that would get Analyst to finally recognize the entire setup. Still no go. Here are the things I have had to do:

1. Change the hardware IP from the one the VWD used (10.10.10.2) to the DAD one (10.10.10.54)
2. Reestablish GPIB communication between instrument and computer using National Instrument programs
3. Use Analyst software and test individual moduals of the LC system
4. Pump, auto sampler, column comp all activate with profile and detector fails

I was thinking it could be a software glitch since I had some trouble with the GPIB yesterday and had to remove the drivers and reinstall. Would uninstalling Analyst 1.4.2 (including all hotfixes) and reinstalling be a worthwhile thing to do? Any help would be greatly appreciated!

I didn't have any trouble with setting one up on our system but I was using a serial connection for the LC stack and only using the GPIB for the Mass Spec(API3200)

I have the serial cable going to the autosampler and then connect the rest of the units together with the CAN cables and it sees it ok. Sometimes it will fail to recognize the LC and I just have to power cycle the stack and kill the Analyst process running in the background then restart and all is good.

Another trick I have found, if you get an error and something pops red in the status bar which usually means you have to restart Analyst to clear the error, if you just loosen the probe until you hear the click that indicates it thinks the probe is removed, wait a couple seconds then tighten it back up and hear the click again where it thinks a new probe is installed, it clears out any errors without needing to shutdown the software.

One thing I forgot to mention is that this is an inherited machine. I have all the parts needed to make it work and I just can't do it. There isn't an extra serial port on the computer and a serial cable wasn't included so I think thats a no go?

It is odd that Analyst just would not recognize the DAD at all. It just hangs when I try and activate the profile and after several minutes it would say Failed to activate: Agilent Detector.

Do you have the LAN cable connected to the DAD? Are you sure the IP address is correct, since you usually need a BootP running to give the DAD a new address when it power cycles.

If it will communicate with the VWD, try putting it back into the stack and connecting the instrument to it, and a CAN cable from the VWD to the DAD and see if it will see it then.

I didn't have any trouble with setting one up on our system but I was using a serial connection for the LC stack and only using the GPIB for the Mass Spec(API3200)

I have the serial cable going to the autosampler and then connect the rest of the units together with the CAN cables and it sees it ok. Sometimes it will fail to recognize the LC and I just have to power cycle the stack and kill the Analyst process running in the background then restart and all is good.

Another trick I have found, if you get an error and something pops red in the status bar which usually means you have to restart Analyst to clear the error, if you just loosen the probe until you hear the click that indicates it thinks the probe is removed, wait a couple seconds then tighten it back up and hear the click again where it thinks a new probe is installed, it clears out any errors without needing to shutdown the software.

One thing I forgot to mention is that this is an inherited machine. I have all the parts needed to make it work and I just can't do it. There isn't an extra serial port on the computer and a serial cable wasn't included so I think thats a no go?

It is odd that Analyst just would not recognize the DAD at all. It just hangs when I try and activate the profile and after several minutes it would say Failed to activate: Agilent Detector.

Do you have the LAN cable connected to the DAD? Are you sure the IP address is correct, since you usually need a BootP running to give the DAD a new address when it power cycles.

If it will communicate with the VWD, try putting it back into the stack and connecting the instrument to it, and a CAN cable from the VWD to the DAD and see if it will see it then.

Well we are pretty sure that the VWD is not compatible with the Analyst software. I finally got the DAD to communicate through LAN and is able to activate the profile on Analyst. However, I foresee a problem since the MS, LC and PC used to be hooked up by GPIB back when I used the instrument and the fact that I can't seem to get the LC and PC to communicate through GPIB might complicate things when I set up the MS.