Skip to content

Search these docs, or ask Revo a question — answers link the pages they came from.

HiRes Stores

Revolution drives two HighRes Biosolutions stores:

DeviceWhat it isRevolution control
AmbiStoreAmbient, high-density, random-access carouselRandom-access storage — no schedule-callable operations
MicroServeLabware and consumable storageLoad, unload, by stacker number

HighRes offers other stores — SteriStore for incubation and environmental control, TundraStore for cold storage at −20 °C to 4 °C, and NanoServe for consumable storage — but Revolution does not drive those today. If you need one integrated, get in touch.

HighRes describes the AmbiStore as high-density, ambient, random-access storage.

Labware96-, 384- and 1536-well plates, deep-well plates, and tip boxes
Delivery timeAs little as ~12 seconds
Stacker pitches8, 19, 24 and 33-pitch standard configurations
ModelsAmbiStore D and AmbiStore M — the M around twice the capacity of the D
PresentationPortrait or landscape
ControlTouchscreen, integrated API, or CellarioScheduler

Two features are worth planning around:

Swappable stackers with automatic self-inventory. HighRes state stackers can be reloaded with tips and plates even mid-operation, and the store re-inventories itself. That is what allows a long unattended run to be topped up rather than stopped.

Portrait or landscape presentation. The store can present labware either way round, which means the orientation a robot receives is a configuration choice — worth settling before positions are taught, not after.

An AmbiStore may also be mounted on a HighRes cart that docks to a MicroDock, which HighRes state allows moving it between systems without reteaching positions or reconnecting power, communications and gas.

Labware and consumable storage, part of HighRes’s MicroServe / NanoServe / PicoServe range.

HighRes does not publish detailed MicroServe specifications on the pages above, so no capacity or dimensions are stated here. Confirm against your own unit’s documentation.

The Revolution device carries a stack configuration, which is what tells the driver how the unit’s stacks are arranged — get this wrong and load and unload address the wrong place.

None. The AmbiStore is a random-access store, so Revolution drives it the way it drives any store: a schedule asks Revolution’s storage manager for a plate, or hands one back, and the driver resolves that into a physical store location on the carousel. There is no store-plate or retrieve-plate operation to call from a method, and none is needed.

  • Load — move the MicroServe to the load position for a given stacker number (1–14)
  • Unload — move it to the unload position for a given stacker number (1–14)

Both take the stacker number, so a schedule addresses a specific stacker rather than the unit as a whole. Get the stack configuration wrong and these will present the wrong stacker.

Inventory and environmental telemetry are not exposed to a schedule on either store — the AmbiStore self-inventories internally, but Revolution does not query that inventory from a method.

Both stores are reached over the network, by IP address and port.

  • The store must be reachable from the Revolution host at the configured address and port.
  • On the MicroServe, the stack configuration must match the physical unit, and the stacker numbers a schedule calls must exist on it.
  • On the AmbiStore, the store’s position layout must be configured, the stacker pitch must suit the labware, and presentation orientation must match what the robot was taught.
  • Reloading a stacker mid-run is supported by the hardware — but Revolution will not know what changed unless the store’s own self-inventory is relied on.

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