Presto Sealer

Revolution drives a unit its driver identifies as the Presto Sealer, applying a seal to labware on demand from a schedule. Unlike most instruments in this catalogue it is not driven over a protocol or an SDK — it is wired in over discrete digital I/O.

No published specifications

The driver names the device only as “Presto Sealer”, and we could not confirm a manufacturer product page for a microplate sealer under that name. No temperature, cycle time, seal-film or labware specification is stated here, because there is nothing verified to state.

If you are specifying or servicing a system with one of these, confirm the unit’s make and model from the machine plate, then work from its own documentation — or get in touch and we will identify what your system carries.

How Revolution drives it

The control model is worth understanding because it shapes what can and cannot be known from a schedule. Revolution asserts an output to start a cycle and waits for an input to say the cycle finished — a handshake, not a conversation.

The I/O the driver works with:

Signal	Direction	Purpose
Remote cycle start	Output	Asserted by Revolution to begin a seal cycle
Cycle complete	Input	Asserted by the machine when the cycle has finished
Cycle confirmation clear	Output	Clears the confirmation, readying the next cycle
Tamp pad home	Input	Confirms the tamp pad is in its home position
Low label roll	Input	Warns that the consumable roll is running low

Two of these are more useful than they first appear.

Tamp pad home is a safety and sequencing interlock: a plate should not be presented to, or taken from, a machine whose tamp pad is not parked. Where a robot serves the sealer, that input is what makes the handoff safe rather than hopeful.

Low label roll is the one that saves an unattended run. A consumable that runs out mid-campaign produces plates that look processed but are not, and the failure is silent. Surfacing the warning into the schedule lets a run stop deliberately instead.

Supported methods

• Seal — run one seal cycle: start it, and wait for the completion handshake

Integration

Revolution drives the unit through an I/O client — a digital I/O interface — rather than a serial or network connection to the machine itself.

Prerequisites

• The machine must be wired to an I/O interface Revolution can address, and its signals mapped.
• The I/O map must match the physical wiring. This is the whole configuration: a mis-mapped input means Revolution waits for a signal that never arrives, or worse, believes a cycle finished when it did not.
• The machine must be set up for remote cycle start rather than local operation.

Device configuration

Property	Purpose
IO Client Element	The I/O client this device addresses
IO Map	Mapping from the driver’s signal names to physical I/O points

If you need more of this instrument driven from a schedule, get in touch — the driver is extended on demand.