1How the results reach Seal.
In the laboratory
NETZSCH thermal analyzers
- Proteus
Export folder
On the workstation or a network share
Seal Edge
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
Sample and run
- Transition
- Onset
- Mass loss
- Original file, kept
Results from the NETZSCH thermal analyzers come from Proteus.
Seal Edge 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 Proteus: 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 NETZSCH models.
These are NETZSCH 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.
Thermal analyzers
Heat flow, mass or dimension against temperature, evaluated into transitions, mass loss or expansion.
- DIL 402 Expedis
- DMA 242 E Artemis
- STA 319 Jupiter
- STA 449 F1 Jupiter
- STA 449 F3 Jupiter
- STA 449 F3 Nevio
- STA 449 F5 Jupiter
- STA 449 Jupiter
- STA 509 Jupiter
- STA 2500 Regulus
- TG 209 F1 Libra
- TG 209 F1 Nevio
- TG 209 F3 Nevio
- TG 209 F3 Tarsus
DSC
Heat flow against temperature, evaluated into transitions such as melting temperature and enthalpy.
- DSC 204 F1 Nevio
- DSC 204 F1 Phoenix
- DSC 204 HP Phoenix
- DSC 214 Nevio
- DSC 214 Polyma
- DSC 300 Caliris
- DSC 404 F1 Pegasus
- DSC 404 F3 Pegasus
- DSC 500 Pegasus
3Where the results go next.
Blueprints
- Analytical development →
Connect method experiments and performance to the intended analytical purpose.
- QC laboratory →
Follow samples from receipt through testing and result review.
4Start 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 NETZSCH instruments.