Chromatography Forum

Hello Chroms!

I'm posting this to get an answer to this question: how do I get my Empower 2 system to connect to a Waters 996 PDA detector instead of a Waters 486?

I started with buying a system from ALT (American Laboratory Trading, a great company BTW). It was very simple: a computer running Empower 2, and a Waters 486 single wavelength detector. It was essentially plug-and-play, and worked great for a while. Couple of years.

Here's the specs on the system:
Computer: Optiplex 380 SFF running Windows XP Pro v2002 Service Pack 3
Empower Pro: Empower 2 Pro Build 2154 with Service Packs A and B and Feature Releases 2 and 3, and Installed Options = Base Package, System Suitability, A1100 Support, A1100 Plus.

The system with the 486, when I recently fired it up after a few months idle, gave me a "detector failure" status (or something similar) when I tried to run a simple baseline scan or run any samples. I tightened the screws on the IEEE cable and looked online for help (despite having a Total Assurance Plan ID, I can't figure out how to access Waters tech support). No joy. Interestingly, when I load a different instrument method, the 486 goes to the new wavelength and zeros, so Empower is talking to it.

Then I got an old Waters 996 PDA detector, and, being an optimist, I simply shut down everything, switched the IEEE cable connection from the 486 to the 996, and then fired up the 996. The LAMP and STATUS lights stayed unlit, so I thought I'd picked up a fried detector, but then they both lit up with a steady green light. Yay!

I fired up the computer, and then Empower, and went to the System Configuration section. I selected the row that had my project, and left clicked and selected Properties... Under the General tab, only System Suitability was checked, so I also checked the Photo Diode Array box. Quit Empower and restarted.

Under Empower Configuration > Systems, I still have a row with the System Name = Waters 486 System, Empower Node Name = Lab-3f5d8f52133, and On Line = Yes. Curious, as the 486 is no longer on the IEEE, I selected the row, left clicked on the Yes, and selected Bring Online. A Working... dialogue with "Connecting to node 'Lab-3f5d8f52133'" came up, and stayed up. After about 10 minutes I got a "Waters 486 System is already online". Interesting.

Well then. I did the same, and instead selected Take Offline. Up comes the same Connecting to Empower Node 'Lab-3f5d8f52133'. Then I get a Configuration Manager dialogue reading "BusLAC/E on node 'Lab-3f5d8f52133' couldn't be booted". And then another Configuration Manager dialogue reading "Successfully brought system 'Waters 486 System' Offline."

Next, I hit the New System icon, and left it at Create New System. Back to the Connecting to Empower Node 'Lab-3f5d8f52133'. Get a cuppa Joe. Drink half. Result? "BusLAC/E on node 'Lab-3f5d8f52133' couldn't be booted", then "COM Fatal error". Then "No instruments are configured in the selected Empower node. Would you like to create some example instruments for demonstration purposes?" I assume No is the right answer. Then "COM Fatal error".

Now I get the New Chromatographic System Wizard - System Selection window. In the Available Instruments there is Unused Components and two unnamed ones. In the New System Instruments there is New System. No draggable instruments.

I tried New Empower Node, and Browse the Network... yielded a domain labeled Workgroup, but hitting the + sign gave no network nodes. Finally, I tried bringing the Waters 486 System back online. Result? "BusLAC/E on node 'Lab-3f5d8f52133' couldn't be booted". Then "Bringing system 'Waters 486 System' Online". Then "Unable to start system".

Did I break something (like the BusLAC/E) by simply switching the IEEE to a new instrument? I did it cold, and always waited for the 996 to fully come up (both lights green) before booting the computer. The previous problem with the 486 might mean I have something funky going on on the computer side. Sigh.

Anyone able to help?

Best,

Richard

have a look at the waters knowledge bade support.waters.com

some driver packs are available without support plan but may need a simple registration.

once the bus lac/e boots again, you probably need to install the instrument driver (aka ICOS) for the 996 pda, if it was not installed before.
Look for the "Driver Pack (DP)" on waters homepage
You may need to read the release notes to get the correct driver pack version because 996 is an old module, out of support now, so it may not be contained in the latest DP edition.

also you may need to configure the ports in the bus lac/e card and the dip detector to matching numbers (don't remember if there are some dip-switches at the back of the detectors. Each module connected to the bus lac/e needs a unique number which then is set in the bus lace configuration (should be found somewhere in the "configure system" sections, either in the menu or in node properties etc))

Thank you, Hollow, for your reply, it was helpful. Here's my reply to your reply:

> have a look at the waters knowledge bade support.waters.com

I went chapter and verse, but the best thing I found was a post on this site by another user with what sounds like the same problem:

https://www.chromforum.org/viewtopic.ph ... ed#p122327

> some driver packs are available without support plan but may need a simple registration.

> once the bus lac/e boots again, you probably need to install the instrument driver (aka ICOS) for the 996 pda, if it was not installed before.
> Look for the "Driver Pack (DP)" on waters homepage
> You may need to read the release notes to get the correct driver pack version because 996 is an old module, out of support now, so it may not be contained in the latest DP edition.

Boy, I went through every downloadable after a search for driver packs using various search terms. Oldest seemed to be DP 4, which doesn't appear from the description of supported instruments to have one for the 996. Sigh.

> also you may need to configure the ports in the bus lac/e card and the dip detector to matching numbers (don't remember if there are some dip-switches at the back of the detectors. Each module connected to the bus lac/e needs a unique number which then is set in the bus lace configuration (should be found somewhere in the "configure system" sections, either in the menu or in node properties etc))

I'll look into that one, the 996 has no control panel but does have DIP switches (currently set to 10). Since there are no other instruments hooked into the system, dunno if that matters. The other post on this site from 2014 had suggestions of insuring the LAC/E board was properly seated, making sure the instrument is set to Empower Control through config options (don't think I can do this one, as there are no controls on the 996 and I can't get it to show up in Empower), check with Waters rep to make sure it's running the current firmware (again, old instrument not supported), changing batteries on the motherboard of the computer and instrument (may try this, particularly on the 996).

Anyone have a copy of the 996 driver?

Thanks again, Hollow.

what about WKB231624 on Waters KB?

even if it's related to Empower 3 and some Agilent devices, it sounds like it may be worth a try. Just move or rename that file and reboot.

Check the addresses of the HPLC and 486 as well and make sure each of the three devices has a unique one. If the HPLC or 486 also has/had #10, then you run into an configuration conflicts. (eg. if 486@10 is still configured but now on the same address a 996 wants to connect...)

as for the driver, maybe 2996 will also work as the 996 could be upgraded to it (but maybe I'm wrong because of different boards, but if you find a driver pack with 2996, you may try if it works).

Sorry, I don't have any driver pack of that "age" here with me

General note - 800 252 HPLC will get you to Waters support people.
If your TAP is current, they'll even stay on the line with you for more than a few minutes to assist to the extent they can given that your PDA has been unsupported for at least 10 years now.

Thanks again, Hollow;

Unfortunately, while I can create an account and login, trying to access the Waters KB gives me a charming web page consisting of:

{}

That's from hitting the Support link (https://support.waters.com/) from various pages. Waters has been pretty scrupulous about locking down anything much related to support unless I have a support contract.

I can get to https://www.waters.com/nextgen/us/en/search.html?..., which is where I found the downloadable Driver Packs (the old ones are, anyway). If found 41 documents in a search for WKB231624 (if I use "article 231624"). The only one that appears to be relevant is titled:

IEEE-488 instrument connection guidelines and recommendations

which basically addresses the DIP switch/address issue. My system consists of the computer with LAC/E card, the IEEE cable, and _either_ the 486 or the 996. I simply switched the IEEE cable from one to the other (while the system is completely off). I also tried switching back to the 486, which formerly showed up and was online (and when I loaded a new method, the 486 switched to the new wavelength and zeroed the machine), but threw an instrument failure status when I tried to run a baseline or an injection. I just use the Empower/486 as a detector, I run the pump and column separately. It's a cobbled together system.

Which means the address should be irrelevant. Sigh. Now the 486, when plugged in instead of the 996, can't be brought online, and I get fatal COM errors. I also get messages about rebooting the LAC/E, but I suspect that's about a standalone LAC/E, not the card, which I believe boots when the computer does. I've tried a hard reboot (reverse of startup, shut down Empower, then the computer, then the 486, then startup). No joy.

I'm wondering if the LAC/E card is at fault.

I bought the system (computer, LAC/E, IEEE, and 486) through American Laboratory Trading, and it does have a TAP in the Empower properties. I'll try them to see if they can help me. Thanks DR

If you bought it years ago, it is probably not going to do you much good as TAP is a subscription sort of thing (service contract, really).
I don't think they offer that for 996, Empower 2 or any of your kit anymore (if it's IEEE, no more support as they're likely out of parts, but they may still offer suggestions).

Unfortunately, while I can create an account and login, trying to access the Waters KB gives me a charming web page consisting of:
{}
That's from hitting the Support link (https://support.waters.com/) from various pages. Waters has been pretty scrupulous about locking down anything much related to support unless I have a support contract.

weird...
I can see the full page even without login and in privacy browser mode.
Have you tried different browser or via a different access point? maybe there are some firewalls blocking your requests?

https://support.waters.com/KB_Inf/Empow ... _Empower_3#

In brief, it says to delete the "instsrv.dat" file and reboot, because the configuration held in that file may got corrupted by physically removing a system which then causes a "COM fatal error" when the (bus)Lac/e boots and wants to connect to the non-existing device.

I've found that file under "\empower\InstrumentServer\" folder.
In a first step, I would just move that file out of the folder, so one may copy it back, in case things get worse.

...then if busLac/e boots again, as Empower-Admin under node\properties\instrument you should be able to scan and see your detectors with the "@#" address, where # is the address set by dip-switches. Also the serial number should be listed and the status seen as OK-yes if online.

From there you can configure your systems as new, with the detector(s) you want to control e.g. "Det-486" and "Det-996", depending on the detector/s connected.
With the IEEE, both detectors can be connected in series, if you have a second cable (and set different addresses by the dip-switches).

Then, only one (configured) system at a time can be online under the "systems".
"Take offline" and "bring online" as you already did it, if you want to switch the detectors.

Heya Hollow;

And thanks to you too, DR. So reassured in the fundamental solidity of humanity when I post to a forum like this and get people who spend their precious time helping out a stranger. Kudos!

Hollow, you wrote:

"...it says to delete the "instsrv.dat" file and reboot, because the configuration held in that file may got corrupted by physically removing a system which then causes a "COM fatal error" when the (bus)Lac/e boots and wants to connect to the non-existing device."

First, I had disconnected the 996 and put the 486 on the IEEE, but it still gave the instrument not present dialogue. I moved the instsrv.dat file, rebooted, and I got a dialogue with busLAC/e rebooted. Yay! When I went to config>Systems, the system I'd been working with with the 486 previously gave an is-not-here dialogue. Sigh. But when hit New System, an instrument called W484 showed up. Yay! I set up a new instrument method and it works.

I have noticed I get weird results with the 486 using it at 210 nm. I don't see the peaks I expect that elute mid to late in the run. The chromatogram looks good for about 4 min, nice flat baseline, a peak or two, then I get fewer peaks than expected (some don't appear at all), the baseline is sinusoidal. Hmmm. Wonder if I need a new lamp. Sigh.

Now for the 996 . . .

Thanks again.

Best,

R

A new lamp is always a good bet for any D2 >2 years old (used or not).

PS - good call just moving that DAT file out. (I usually just rename them in-situ, change .dat to .olddat or something - same result)