Skip to main content

BINDER instruments in Seal

Seal Edge collects the files BINDER software saves and sends each original to Seal, linked to its sample, method and run.

BINDER instruments to SealInstrument export

Seal reads
Exports from APT-COM 4
Writes back
No
Source of truth
Instrument software
Set up
Seal Edge and an upload Script

1How the results reach Seal.

In the laboratory

BINDER incubators

  • APT-COM 4Saves PDF, HTML and CSV 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

Chamber

  • Temperature
  • Set point
  • Alarm
  • Original file, kept
How a result from the BINDER incubators reaches Seal.

Results from the BINDER incubators come from APT-COM 4.

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 APT-COM 4: 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.

APT-COM 4
56 models: incubators, climate chambers and freezers. Saves PDF, HTML and CSV reports.

Saved by the instrument

Incubators, climate chambers and freezers
40 models. Each saves the data logger’s readings over USB, in an open format.
Incubators
11 models. Each saves recorded data over USB.

3The BINDER models.

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

Incubators

Chamber temperature over time, with carbon dioxide and humidity where they are controlled, and alarm events.

  • BD 23
  • BD 56
  • BD 115
  • BD 260
  • BD 400
  • BD 720
  • BD-S 56
  • BD-S 115
  • BF 56
  • BF 115
  • BF 260
  • BF 400
  • Show all 39 models
  • BF 720
  • CB 56
  • CB 170
  • CB 260
  • CB-S 170
  • CB-S 260
  • CBF 170
  • CBF 260
  • KB 65
  • KB 130
  • KB 260
  • KB 470
  • KB 720
  • KB 1060
  • KB ECO 240
  • KB ECO 400
  • KB ECO 720
  • KB ECO 1020
  • KB PRO 130
  • KB PRO 260
  • KB PRO 470
  • KB PRO 720
  • KB PRO 1060
  • KB PRO 1600
  • KT 53
  • KT 115
  • KT 170

Climate chambers

Chamber temperature and humidity over time, the conditions a stability study depends on.

  • KBF 130
  • KBF 260
  • KBF 470
  • KBF 720
  • KBF 1060
  • KBF 1600
  • KBF PRO 130
  • KBF PRO 260
  • KBF PRO 470
  • KBF PRO 720
  • KBF PRO 1060
  • KBF PRO 1600
  • KBF-S ECO 240
  • KBF-S ECO 400
  • KBF-S ECO 720
  • KBF-S ECO 1020

Freezers

Cabinet temperature over time and alarm events, from the unit’s own log or a monitoring system.

  • UF V 350
  • UF V 500
  • UF V 700

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

See your process in Seal.

Bring a procedure or a recurring problem. See how your team configures it with Neil and improves the next run.