The Local Console Controller plugs in and communicates through Ethernet Switch.
Included with the controller is a bracket that mounts to the front door of the Sample Manager to store the LCC into when not in use.
I hope this information is helpful.
Just a further addition. Depending on which sample manager it also requires a power cable to plug into a wall socket. For the ACQUITY UPLC H-Class systems only the ethernet switch is required. Here is a link to the web site and the parts locator, which in cases like this sometimes a picture and an explanation is useful.
Thanks for your responses so far.
The reason why we are looking at this is that the console screen within Empower for our Acquities is sometimes slow and unresponsive as our database is in the US and we are in the UK. Thinking is that this will be increased if we have the local controller.
How does the Console Controller communicate with the instrument? Is it independent of the main Empower system, or does it have to go through Empower to contact the instrument? I presume if it is the former, we would need to input the IP address of the Sample Manager module to allow it to communicate.
Perhaps someone could advise.
This is an intereting situation, my understanding is that the software that enables the LCC to function is a driver that is transferred to the LCC at start-up which allows the transfer of read only information to the LCC for display from the ACQUITY UPLC Console software.
The LCC only works when the system is not acquiring data or being controlled by Empower/acquisition software, that is the ONLY time the LCC can effect changes on a per module basis to initial conditions or parameters or to invoke a specific set of diagnostics. It requires the system IP address to do this, but I will check into the exact mechanics of this.
This occurs when there is no connection between the console software and the Empower/acquisition software. So I would expect the LCC would only connect when the system is idle, the LCC would wait to get the comms from Empower indicating there is no control, if Empower is slow, release to the LCC initially will be slow.
However, I will run this by the LCC s/w engineer and the LCC s/w engineer and be in touch.
The engineers agree that slowness of Empower should not affect the LCC, but I do hope that you will discuss this with your data specialist is aware of this.The LCC developer confirmed that the LCC doesn't communicate directly with the instruments but rather via the individual instrument servers on the acquisition computer.
While the slowness of Empower could, and probably does to some extent, effect the responsiveness of the LCC, I would not expect this to be significant.
Applications can become slow for different reasons and the LCC is communicating through the computer. If the computer is slowed down enough or bogged down in a way that specifically causes problems with the communication to the instruments then this will effect the performance of the LCC.
Just a quck follow up,