Engineering

Calibrate

Jalaran Calibrate logs periodic sensor calibration checks — reference against measured across test points — and shows drift over time against your own tolerance band.

Who Calibrate is for

For anyone maintaining instrumentation where measurements have consequences — lab equipment, production sensors, test rigs. A sensor that has drifted is worse than one that has failed, because it keeps producing numbers people believe.

What Calibrate does

Each check records reference against measured across a set of test points, and passes or fails against a tolerance band you define — because tolerance is a property of your application, not of the tool. Across checks it shows a drift trend by comparing earlier readings against later ones, with a status-coloured history chart. The commentary is deliberately descriptive: it tells you the drift is there and does not diagnose why, because a cause suggested by software is a hypothesis someone will stop testing.

  • Reference against measured per test point
  • Pass or fail from your own tolerance band
  • Drift trend across the check history
  • Descriptive commentary, never diagnostic

How Calibrate works

  1. Define test points and tolerance

    Your reference points and the band that counts as acceptable for your application.

  2. Log a check

    Reference against measured at each point, recorded as a dated check.

  3. Read pass or fail

    Against your band, per point, so a sensor failing at one end of its range is visible as exactly that.

  4. Watch the drift trend

    Earlier checks against later ones. Drift is a direction, and one check cannot show you a direction.

What Calibrate does not do

Calibrate is a manual log — it does not read instruments, ingest live data or connect to anything, so checks are entered by you. It is not a certification or metrological traceability record and should not be presented as one where an accredited process is required. The commentary describes drift and deliberately never diagnoses a cause, because a plausible cause from software is one nobody investigates properly.

Common questions

Does it read my instruments automatically?

No. It is a deliberate manual log. You perform the check and record the readings, which is also what makes the record meaningful.

Why does it not tell me why a sensor drifted?

Because a cause suggested by software is a hypothesis people stop testing. It reports the drift precisely and leaves diagnosis to the engineer, which is where it belongs.

Is this a calibration certificate?

No. It is a tracking log. Where an accredited calibration with metrological traceability is required, this does not substitute for it.