1How the results reach Seal.
In the laboratory
NanoEntek cell counters
- EVE HT FL softwareSaves PDF reports, CSV data and JPG images
- EVE HT software
Export folder
On the workstation or a network share
Seal IoT
Waits until each file is complete, then sends it
Outbound HTTPSNo inbound connection
Nothing is written back to the instrument or its software
In Seal
Seal Script
Checks the file’s layout and matches it to its record
Record
Culture sample
- Viable cells/mL
- Viability
- Mean diameter
- Original file, kept
Results from the NanoEntek cell counters come from EVE HT FL software or EVE HT software.
Seal IoT runs on the instrument workstation, or a host that can read the files, and watches the folder the software exports to. 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 record it belongs to and writes the selected values into typed fields. The original file is kept with the result. Acquisition and analysis stay in EVE HT FL software or EVE HT software: Seal collects completed results and sends nothing back to the instrument or its software.
How capture works and what IT confirms are set out on the instruments page; the setup instructions cover installation.
2The software and what it saves.
- EVE HT FL software
- 1 model: cell counter. Saves PDF reports, CSV data and JPG images.
- EVE HT software
- 1 model: cell counter.
3The NanoEntek models.
These are NanoEntek 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.
Cell counters
Total and viable cell counts, viability and cell size for each sample.
- EVE HT A26
- EVE HT Automated Cell Counter
- EVE HT FL
4Where the results go next.
Connection guides
Blueprints
- Upstream process development →
Compare bioreactor runs, feed strategies and culture performance.
- Process development →
Compare experiments and carry the selected process forward.
5Start 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 NanoEntek instruments.
