Sykam instruments in Seal

Seal IoT collects the files Clarity saves and sends them to Seal over outbound HTTPS. Each original file stays with its results, linked to the sample, method and run.

Illustration of a seal following a sample vial to an analytical instrument and its result.

1The Sykam models.

These are Sykam instruments laboratories connect to Seal, listed from the manufacturer’s own documents. A model not listed here works the same way if its software saves a file: send us the model and an example output.

LC detectors

  • RI2000 Detector
  • S3245 Detector
  • S3250 Detector
  • S3585 Detector
  • S3590 Detector

LC pumps

  • S1122 Pump
  • S1125 Pump
  • S1130 Pump
  • S1132 Pump
  • S2100 Pump

LC autosamplers

  • S5200 Autosampler
  • S5250 Autosampler
  • S5300 Autosampler

Column ovens

  • S4115 Column Oven
  • S4120 Column Oven

HPLC / UHPLC systems

  • S 500 HPLC
  • S 600 HPLC

Other

  • S4300 Amino Acid Reaction Module System

2How Seal collects the results.

Seal IoT runs on the instrument workstation, or a host that can read the files, and watches the folder the software exports to. For these instruments that is usually Clarity. When a file is complete it sends it to Seal over outbound HTTPS; no inbound connection to the workstation is needed.

A Seal Script checks the export’s layout, resolves the run and sample it belongs to and writes the selected values into typed fields. The original file is kept with the result. Acquisition and the vendor’s analysis stay in the instrument software: Seal collects completed results and sends no instructions to the instrument.

How capture works and what IT confirms are set out on the instruments page; the setup instructions cover installation.

3Start with one instrument.

Bring the model, the installed software version and an example output. We map the connection into your workflow and test it with a late file, a duplicate transfer and a failed integrity check before you rely on it. Discuss your Sykam instruments.