// Connectors · Instrument category
Centrifuges.
Connect your centrifuges to your LIMS, your monitoring and your automated workflow. Every run event your centrifuge reports, from start to fault to stop, carries a Gateway timestamp. Every command sent to it is logged in the audit trail.
OPC UA / LADS for your robots and schedulers
Mid-run parameter writes where your model supports them
Vendor protocols over RS-232 and Ethernet
Gateway timestamps and audit trail
// Your centrifuge fleet
Example: a fault at 19:30 can wait until 09:00 for someone to find it. Connected, the Gateway timestamps the fault event, ready for your monitoring system to pick up.
Centrifuges from different vendors, in one OPC UA / LADS data model.
Parameter writes on centrifuges whose protocol supports them. Ramp profiles, cyclical changes and conditional adjustments become programmable.
Gateway-stamped run records, so you can link each sample to the run that processed it.
// Centrifuge types
Centrifuge types and form factors
- Robotic centrifuges with tray loading and unloading, and an extra door for robot arm access. Here, a connection adds the most to your automated workflow.
- Standard and manual benchtop and floor-standing centrifuges
- Refrigerated centrifuges
- Microcentrifuges
- Bucket-based vessel centrifuges
- Fixed-rotor and swing-rotor types
- Ultracentrifuges, high-throughput and continuous-flow centrifuges, where the model offers a data interface
// Protocols
Vendor protocols, translated into OPC UA / LADS
Most centrifuges in labs today speak a vendor-specific protocol over RS-232 or Ethernet. Some models also offer OPC UA or SiLA 2 natively. We connect both kinds and translate the vendor protocol into one OPC UA / LADS model.
Manufacturers: examples from this instrument family include Sigma, Hermle, Thermo, Beckman and Eppendorf. Tell us your model and we’ll confirm its status: Available, In testing or On request.
What a centrifuge connector typically covers:
- Set-up parameters (target speed, duration, temperature, rotor type)
- Start, stop and abort controls
- Live status (current speed, temperature, elapsed run time, fault flags)
- Method recall and execution
The control options differ by vendor and model. Your connector uses the options your model offers.
// Common challenges
Six common centrifuge challenges
1 · Unattended overnight runs. A multi-hour run starts at 18:00, and a fault occurs at 19:30. Your team finds it at 09:00 the next morning, after 13.5 hours of lost run time.
2 · Run-log integrity. Which speed, duration and temperature? Which sample? Was the rotor balanced correctly? Answers from memory and notes are hard to check later.
3 · Sample-to-run linkage. Which centrifuge processed which sample, and when? With many centrifuges and many samples, your team often links them by hand.
4 · Method versioning. Lab protocols evolve: A.3 replaces A.2, which replaced A.1. The version used in a run is often inferred from revision dates and run dates.
5 · Run data in your records. Your LIMS or ELN needs the centrifuge run data: parameters used, deviations and completion. Typing it in by hand is slow and invites errors.
6 · Fixed run profiles. Standalone centrifuges run fixed parameters: set, start, run, stop. Front-panel programs offer preset acceleration and braking curves, sometimes a few steps. Some separations need changes during the run, triggered by a condition or an external system.
// Today
Connect your standalone centrifuges
Today, a standalone centrifuge runs the fixed parameters set at launch, from the front panel. Your team finds a fault at the next physical check.
Sample-to-run links live in a paper logbook or in someone’s memory. Method versions are rebuilt from revision dates and run dates when someone asks which version ran.
// Connected
Your centrifuge as part of your workflow
The Gateway timestamps every run event your centrifuge reports. Your monitoring system picks up fault events from the Gateway, each run record is ready to link to its samples, and the program used in each run is recorded with the run data.
Where the vendor protocol allows parameter writes during a run, ramp profiles, cyclical changes and conditional adjustments become programmable. You run them by hand or from an automated protocol.
// What you get
What you get with connected centrifuges
Run events with provenance
Start, stop, fault and parameter changes each get a Gateway timestamp. Every command sent to the centrifuge is logged in the audit trail with the sender’s identity. You get the complete run history along with the result.
Fault and completion events
Fault and completion events carry a Gateway timestamp. Your LIMS or monitoring system pulls them from the Gateway or receives them through a Node-RED push flow. It can flag a fault as soon as it reads the event.
Link each sample to its run
See which centrifuge processed which sample, and when. Each run is recorded with Gateway timestamps, ready to link to the samples it processed.
Method versions with each run
The program and the parameters used in each run are recorded with the run data, so you can check the method version against what ran.
5 · Dynamic mid-run control
For centrifuges whose protocol allows parameter writes, you can program ramp-up and ramp-down phases, cyclical changes and conditional adjustments during a run. You get separation profiles beyond the front-panel programs.
6 · Robotic centrifuge orchestration
Robot-loaded centrifuges become part of your larger automation workflow. Over OPC UA / LADS, the Gateway makes the centrifuge available to your workcell scheduler. Your scheduler reads its status and, where your model supports it, drives the run. The centrifuge works as one node among many.
Centrifuge integrations at a glance
Connecting your centrifuges to a workcell or LIMS?
Tell us your centrifuge models, the workflows you want to monitor or automate, and your target system. We’ll come back with the connector mapping, a monitoring plan and a scoped proposal.
// Learn more
Related pages
Why Synefex
AI-readiness via MCP
Example prompt: “Did anything unusual happen in the lab last night?” The MCP Server answers from the data your connected instruments recorded overnight. We set it up on your Gateway on request.
Why Synefex
Open standards
How OPC UA / LADS brings centrifuges from many vendors into one data model.