Search these docs, or ask Revo a question — answers link the pages they came from.
VANTAstar
BMG LABTECH VANTAstar Compact multimode microplate reader. The BMG LABTECH VANTAstar is a multimode microplate reader for plates up to 384 wells. Like the CLARIOstar it combines filters, BMG’s Linear Variable Filter (LVF) monochromators and a UV/vis spectrometer, so one instrument covers fluorescence, luminescence, polarisation, time-resolved and absorbance assays. BMG lists the VANTAstar as the successor to the POLARstar Omega, which it states was replaced in 2022.
At a glance
Section titled “At a glance”| Type | Multimode microplate reader with filters, LVF monochromators and a UV/vis spectrometer |
| Detection modes | Fluorescence intensity (incl. FRET), fluorescence polarisation, luminescence (flash and glow, incl. BRET), time-resolved fluorescence, TR-FRET, UV/vis absorbance spectra |
| Plate formats | 6- to 384-well, user-definable |
| Instrument software | SMART Control and Voyager for reader control; MARS for data analysis |
| Revolution control | None yet — the driver is a scaffold. Its only operation writes a message to the log. |
Specifications
Section titled “Specifications”BMG LABTECH publishes the following for the VANTAstar on its product page.
| Filters (FI, LUM, TRF, FP, TR-FRET) | 240–740 nm |
| LVF monochromators (FI, LUM) | 320–740 nm, dual LVF Monochromators |
| Linear variable dichroic mirror | 340–740 nm |
| Absorbance spectrometer | 220–1000 nm, wavelength precision ≤0.5 nm |
| Plate formats | 6- to 384-well, user-definable; LVis Plate with 16 low-volume microspots of 2 µL |
| Read times, flying mode (1 flash) | 9 s (96-well), 16 s (384-well) |
| Reagent injectors | Up to 2; 3–500 µL (optionally up to 1 mL); up to 420 µL/s |
| Incubation | 4 °C above ambient up to 45 °C or 60 °C |
| Shaking | Linear, circular and double-circular, user-definable time and speed |
| Software | SMART Control and Voyager (multi-user reader control), MARS (data analysis) |
| Reader dimensions (W × D × H) | 35 × 52 × 36 cm |
| Reader weight | 27 kg |
| Injector unit dimensions (W × D × H) | 13 × 31 × 26 cm |
| Injector unit weight | 6 kg |
The figure that most often decides a placement is the plate format ceiling of 384 wells. A 1536-well workflow needs a reader such as the CLARIOstar instead. Note also that BMG lists the injectors as a separate unit with its own footprint, so a VANTAstar with injectors needs bench space beside the reader.
BMG states the VANTAstar is for research use only.
Supported methods
Section titled “Supported methods”None that reach the instrument. The Revolution driver for the VANTAstar is a scaffold: it registers the device and its model so that a system can be configured against it, and it does not yet open any connection to the reader. Initialising the device logs that no instrument connection is made.
- Debug — writes the given message to the device log and does nothing else. It exists so the scaffold can be exercised from a schedule; no command reaches the reader.
A schedule cannot start a read, run a protocol, move the plate carrier or query the instrument’s state through this driver. Unlike the PHERAstar driver, it also does not drive the plate carrier out and in around a robot transfer, so the carrier has to be in the load position by other means. Any measurement made while a plate sits at the VANTAstar is started outside Revolution.
Integration
Section titled “Integration”There is no transport configured: no serial or network connection, and no BMG software in the path. BMG’s own control software (SMART Control or Voyager) is how the instrument is operated today, and the Revolution driver does not use it.
Prerequisites
Section titled “Prerequisites”- The instrument must be positioned so the system’s mover can reach its plate carrier, and the carrier must be at the load position when a transfer happens. Revolution does not command it.
- Any read must be set up and started in BMG’s software at the instrument. A schedule step cannot do it.
- Timing must be arranged by hand. Revolution cannot ask the reader whether it is busy, so a schedule cannot wait on a read finishing.
Device configuration
Section titled “Device configuration”| Property | Purpose |
|---|---|
| — | The driver declares no configurable device properties. Only the standard device settings apply. |
If you need more of this instrument driven from a schedule, get in touch — the driver is extended on demand.
Operations
These are available from a Run Device Operation step.
Debug
Writes the given message to the device log and does nothing else. This driver is a scaffold awaiting implementation, so no command reaches the instrument.
| Parameter | Type | Default | Description |
|---|---|---|---|
| message | string | VANTAstar debug |
Raise Error
Makes this device report a failure on demand: the step fails with an error naming the device, and the operator is offered the usual error recovery choices. No command reaches the instrument and nothing moves, and the failure is raised in simulation as well as on a real system, so this is the step to use when rehearsing how a schedule handles a device failure.