Skip to main content

Vaisala instruments in Seal

Seal IoT collects the files viewLinc and Viewlinc Cloud Suite save and sends each original to Seal over outbound HTTPS, linked to its sample, method and run.

Illustration of a seal following a sample vial to an analytical instrument and its result.

Vaisala instruments to SealInstrument export

Seal reads
Exports from viewLinc and Viewlinc Cloud Suite
Writes back
No
Source of truth
Instrument software
Set up
Seal IoT and an upload Script

1How the results reach Seal.

In the laboratory

Vaisala environmental monitors

  • viewLinc

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

Location and reading

  • Reading
  • Limit
  • Alarm
  • Original file, kept
How a result from the Vaisala environmental monitors reaches Seal.

Results from the Vaisala environmental monitors come from viewLinc.

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 viewLinc: 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.

viewLinc
26 models: environmental monitors, data loggers and temperature monitors.
Viewlinc Cloud Suite
1 model: data logger.

3The Vaisala models.

These are Vaisala 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.

Environmental monitors

Continuous readings, such as temperature, humidity, carbon dioxide or pressure, with alarms against limits.

  • GMP231
  • GMP251
  • GMP252
  • HMD60
  • HMM100
  • HMM170
  • HMP110
  • HMT120
  • HMT130
  • HPP270
  • Indigo80
  • Indigo200
  • Indigo500
  • Indigo510
  • Indigo520
  • PDT101

Data loggers

Temperature readings over time, and pressure or humidity on some loggers, for each sensor in a study or cycle.

  • CWL100
  • DL1000
  • DL1016
  • DL1400
  • DL1416
  • DL1700
  • DL2000
  • DL4000
  • RFL100
  • VDL200

Temperature monitors

Temperature readings over time, with alarms against limits.

  • TMP115

4Where the results go next.

Blueprints

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 Vaisala instruments.