2023-09-25 ChromSword NovoNordisk

Waters Acquity - The simplest way to set up a new instrument

1. Open C:\Program Files (x86)\Waters Instruments\Waters DHCP Server Configuration.exe

2. If there are existing instrument modules then remove them

3. Choose Server->Configuration Wizard.. Choose the correct Network Card and IP address

4. Finish wizard, but do not Restart the computer when asked

5. In Task Manager stop all processes that start with Acquity or Waters or WDHCP

   

6. In Windows Network and Internet => Network Connections dialog Disable and then Enable(Important step ⚠️)

7. Start again C:\Program Files (x86)\Waters Instruments\Waters DHCP Server Configuration.exe

8. Reboot all physical modules, slowly they will appear in the list

9. Start Waters Acquity console, Click on System on left, then Configure => Configure instrument modules..

10. Then press Scan

11. Then in Task Manager stop all processes that start with Acquity or Waters or WDHCP

12. Then open again C:\Program Files (x86)\Waters Instruments\Waters DHCP Server Configuration.exe and Waters Acquity console

13. If any modules in an error state, reset them using Waters Acquity console

Waters Acquity - Transfering existing configuration from Empower Data acquisition node so that there is no interruption in their operations

⚠️Also this procedure can be used if the above procedure does not recognize instruments

1. Set manually IP address in Windows Network and Internet => Network Connections dialog as it is in Waters Data Acquisition server

2. In Windows Network and Internet => Network Connections dialog Disable and then Enable(Important step ⚠️)

3. In C:\Program Files (x86)\Waters Instruments\Waters DHCP Server Configuration.exe manually add each module excluding Type (like QSM), but precise IP and MAC address as it is in Waters Data acquisition PC

4. You can also test if access of the modules using Windows CMD ping 192.168.0.2 etc

5. Then in Task Manager stop all processes that start with Acquity or Waters or WDHCP

6. Then open again C:\Program Files (x86)\Waters Instruments\Waters DHCP Server Configuration.exe

7. In short moment Type (like QSM) will appear meaning that configuration works

8. Alternatively this can be done by manually entering IP addresses in file C:\Program Files (x86)\Waters Instruments\DHCP.xml (Caution on top of file there are server settings as well that need to be changed)

DHCP example entries (Type can be added or will be detected automatically)

​x
1
<Leases>
2
<Lease><IP>192.168.0.5</IP><MAC>00-00-C4-0E-CF-D8</MAC><Name>M22FTP411G</Name></Lease>
3
<Lease><IP>192.168.0.6</IP><MAC>00-00-C4-0E-EE-86</MAC><Name>B23QSP406A</Name></Lease>
4
<Lease><IP>192.168.0.7</IP><MAC>00-00-C4-0E-96-3D</MAC><Name>J22TUV358A</Name></Lease>
5
<Lease><IP>192.168.0.8</IP><MAC>00-00-C4-0E-B3-96</MAC><Name>K22CMP076G</Name></Lease>
6
</Leases>

🔴 Waters Acquity - Controlling multiple instruments from the same computer

1. In testing, I managed to add 2 Network card interfaces to the same C:\Program Files (x86)\Waters Instruments\Waters DHCP Server Configuration.exe configuration, but Waters Acquity Console mixes them and cannot work on the same computer with multiple Waters instruments

2. Each Windows Network card can only have a unique IP address - they cannot be the same for multiple cards

3. The largest problem is that all Windows services are shared by all users on the same Windows machine, all windows users will have the same DHCP service running meaning that when you switch between different instruments all users will get switched

🟢 Waters Acquity - Controlling multiple instruments from the same computer

1. Option A: Using Windows Virtual Machines running on same computer (emulating multiple PCs on same PC) where each Virtual machine have assigned seperate Network Card for instrument and shared Network Card for Internet. Each Virtual Machine will need to have all of the user rights and policies installed, each virtual machine will be dedicated to single Waters instrument. All of virtual machines can be identical copies that can be easily cloned form master virtual machine. Files, project configurations and reports would be stored in file server, not on local machine.

2. Option B: Seperate Windows computer by each Waters Data acqustion node. Each Physical Machine will need to have all of the user rights and policies installed, each Physical machine will be dedicated to single Waters instrument. All of Physical machines can be identical copies that can be easily cloned form master virtual machine. Files, project configurations and reports would be stored in file server, not on local machine.

3. Option C: Need to have access to Waters datasystem with 2+ Empower instruments, not Data Acqusition node itself, but operator PC. Waters do not have documentation, but there must be a way how to connect to instrument using Waters Drivers using Acquity central control nodes through network. This option is not implemented yet and we have no place to test it.

Key personnel of NovoNordisk

• Lene - Lab manager lkej@novonordisk.com (little daughter)

• ANRS (Ann Reimers) - Woman that manages IT services, anrs@novonordisk.com

• PXAA (Peter Baade - Main IT administrator) PXAA@novonordisk.com

• DPLD (David Poulsen de Sousa) dpld@novonordisk.com

Additionaly NovoNordisk have 10+ labs like these that would benefit from ChromSword.