- Modules appear correctly in WDHCP, but communication was not established in MassLynx or Console.
- In the Console, a message appeared stating that firmware is needed for SM-FTN.
- Firmware loader worked, but stopped responding when analyzing current firmware version.
- PC was slow. For example, it took a long time to open the inlet method.
- ACQUITY UPLC
- MassLynx 4.1
- MassLynx 4.2
Panda antivirus program installed on MassLynx PC.
FIX or WORKAROUND
Uninstall Panda antivirus program.
Local IT made exceptions for MassLynx folder and Waters Instruments folder, but that did not resolve the issue. Had to uninstall Panda.
comms, MLYNX, MLYNXV41, SUPMM, UPBINARY, UPSMPMGR