Search these docs, or ask Revo a question — answers link the pages they came from.
Keyence Barcode Reader
Revolution has a driver for a Keyence fixed-mount barcode reader, used to read labware barcodes as labware passes a fixed reading position.
Which model
Section titled “Which model”The driver does not name a specific Keyence model, and Keyence’s barcode readers differ substantially between families in reading distance, code resolution and scanning rate. No specifications are reproduced here, because quoting figures from the wrong family would be worse than quoting none.
Confirm your unit’s model, then check its reading distance and code resolution against where you intend to mount it — on Keyence’s own datasheet for that model. If you need this page to name the model your system uses, get in touch and we will pin it down.
How Revolution uses it
Section titled “How Revolution uses it”A barcode reader is not a scheduled instrument. It implements Revolution’s barcode-read contract, so the system asks it for a barcode when a workflow needs one — during a transfer, or when labware is identified on arrival. You do not call a read from a method.
One operation is exposed, for commissioning:
- Test bar code reader — trigger a read with a timeout and report what came back. Use this to confirm aim, distance and label quality before relying on the reader in a schedule.
Integration
Section titled “Integration”Revolution talks to the reader over a serial connection.
Prerequisites
Section titled “Prerequisites”- The reader must be cabled to the Revolution host and its port settings known before the device is initialised.
- The reader must be mounted within its own model’s reading distance, with the label inside its aperture.
Device configuration
Section titled “Device configuration”| Property | Purpose |
|---|---|
| COM Port Settings | Serial port and line settings for the reader |
| Response header length | Number of leading characters to strip from the reader’s response before the barcode itself |
The response header length is the setting that most often explains a barcode that reads but comes back wrong: if the reader prefixes its reply and the driver is not told how long that prefix is, the prefix ends up inside the barcode value.
If you need more of this instrument driven from a schedule, get in touch — the driver is extended on demand.