Installing devices - 4.7 Automation sender

Automation Senders use the basic design of the Bruker NMR Receiver. 

They are mounted on a deck or mounting plate. There are two tapped holes in the base for this. 

4.7.1 Automation sender interface

External software applications create a connection to the lab2lab Oracle database. To do this they need the connection details which could be defined in a single connection string, for example: 

Data Source=(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=l2l_pc)(PORT=1521))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=XE))); User Id= C##lab2lab_extern;Password=l2lpw1126; 

When a registering a vial and a method for it, the third-party software will execute two SQL commands. They could be like this: 

INSERT INTO LAB2LAB_VIALS 
(BARCODE, SAMPLE_REFERENCE, SECONDARY_REFERENCE, PRIORITY, ON_COMPLETION, STORAGE_TARGET) 
VALUES 
('0112511854', 'GSK876', 'PROJ_A', 'Low', 'RetainInBuffer', 'Chilled'); 

INSERT INTO LAB2LAB_ANALYSES (METHOD_NAME, VIAL_BARCODE) 
VALUES ('LOWPH','0112511854'); 

When the robot inserts a new vial into the extended arm the third-party software will execute an SQL command like: 

UPDATE LAB2LAB_ARMS SET VIAL_PRESENT=1 WHERE ADDRESS_ID=743; 

Alternatively, it could use the Device name as the reference, e.g. 

UPDATE LAB2LAB_ARMS SET VIAL_PRESENT=1 WHERE NAME=’AutoSender1’; 

The third party software can also query lab2lab's status. The main purpose for querying status feedback is that if the Transport or Scheduler software subsystems are in the Error state then the third-party software may want to delay submitting any new vials until they are both back to either Busy or Ready. 

The third-party software could query it like this: 

SELECT STATUS FROM SUBSYSTEMS WHERE SYSTEM='AB_123' AND TYPE IN ('Transport','Scheduler');  

Installing devices - 4.8 Buffer >>>