1How the results reach Seal.
In the laboratory
Halo Labs particle size analyzers
- Particle Vue SoftwareSaves Particle Vue results, images and reports
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 measurement
- Dv10
- Dv50
- Dv90
- Original file, kept
Results from the Halo Labs particle size analyzers come from Particle Vue Software.
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 Particle Vue 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.
- Particle Vue Software
- 4 models: particle size analyzers. Saves Particle Vue results, images and reports.
3The Halo Labs models.
These are Halo Labs 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.
Particle size analyzers
A particle size distribution with its summary values, such as Dv50 or a mean size.
- Aura CL
- Aura GT
- Aura PTx
- Aura+
4Where 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.
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 Halo Labs instruments.
