1The Gilson models.
These are Gilson 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 pumps
- 302 Pump
- 303 Pump
- 305 Pump
- 306 Pump
- 307 Pump
- 331 Pump
- 331, 332
- 332 Pump
- 333 Pump
- 333, 334
- 334 Pump
LC detectors
- 112 Detector
- 151 UV/VIS Detector
- 151, 152
- 152 UV/VIS Detector
- 155 UV/VIS Detector
- 155, 156
- 156 UV/VIS Detector
- 157 Detector
- 159 Detector
- PrepELS II Detector
LC autosamplers
- 215
- 215 Liquid Handler
- 221XL Autosampler
- 221XL, 222XL, 231XL, 232XL, 233XL
- 222XL Autosampler
- 231XL Autosampler
- 232XL Autosampler
- 233XL Autosampler
Liquid handlers
- PIPETMAX 278
Other
- FC 203B Fraction Collector
- FC 204 Fraction Collector
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 Chromeleon CDS and 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 Gilson instruments.