1The Young In Chromass models.
These are Young In Chromass 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
- ChroZen HPLC FLD
- ChroZen PDA
- ChroZen RID
- ChroZen UHPLC PDA
- ChroZen UHPLC UVD
- ChroZen UVD
- YL9120 UV/Vis Detector
- YL9140 FLD
- YL9160 PDA
- YL9170 RI Detector
- YL9172 RID
- YL9180
- YL9181
LC autosamplers
- ChroZen AS
- ChroZen UHPLC ALS
- YL9150 Autosampler
- YL9150 Plus Autosampler
- YL9151 Autosampler
LC pumps
- ChroZen Binary Pump
- ChroZen UHPLC Pump
- YL9110 Pump
- YL9111 Pump
- YL9112 Pump
Gas chromatographs
- ChroZen GC
- ChroZen Plus GC
- YL6100 GC
- YL6500 GC
HPLC / UHPLC systems
- ChroZen HPLC
- YL9100 HPLC
- YL9300 HPLC
Column ovens
- YL9130 Column Oven
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 Young In Chromass instruments.