The brain behind the sensors

Larus-10 is the gateway where signals become diagnostics. It accepts raw waveforms from Passer-V (vibration) and Passer-T (motor current) controllers, runs FFT, envelope analysis, RMS / Peak / Crest factor, bearing-fault frequency detection and ML classifiers — all on the edge — and ships the results upstream as OPC UA tags, MQTT messages or Sparkplug B payloads.

For non-vibration use cases (PLC data, meter aggregation, generic SCADA bridging), Larus-10 also functions as a plain industrial protocol gateway, similar to Kepware or HighByte — without the licensing cost.

What runs on Larus-10

• Vibration diagnostics: spectrum (FFT), envelope spectrum (bearing faults), time-domain features (RMS, Peak, Crest factor), ISO 10816 zoning.
• Motor signature analysis (with Passer-T): rotor bar, eccentricity, load profile.
• Anomaly detection: pre-trained ML models for common defect classes; bring your own ONNX model when needed.
• Protocol translation: OPC UA / Modbus / MQTT / REST — both as source and as output.

When teams pick Larus-10 over Larus-100

• Diagnostics-first deployment without on-edge interlocks: one Larus-10 handles Passer streams + protocol bridging.
• Smaller skids and sub-stations where local control logic isn’t required.
• Lowest CAPEX entry point for the vibration/diagnostics stack.

Pairs naturally with

• 1-3× Passer-V (vibration acquisition)
• 1× Passer-T (motor current acquisition)
• Strix software upstream (analytics, asset twin, multi-site rollups)

Technical drawings

Larus-10 and Larus-100 share the same enclosure — the drawings below apply to both.

Wiring diagrams