Skip to content

Main content

Watchdog Clock Tolerance Interval Tool

Compute watchdog clock tolerance interval from explicit bounded inputs.

Loading tool…

Description

For positive ticks and nominalHz, divide ticks by nominalHz × (1 + relativeTolerance) for minimumSeconds and by nominalHz × (1 - relativeTolerance) for maximumSeconds.

A watchdog refresh window is an interval of allowed elapsed time. Clock tolerance and inclusive endpoints affect whether a nominal refresh time falls inside that interval.

For positive ticks and nominalHz, divide ticks by nominalHz × (1 + relativeTolerance) for minimumSeconds and by nominalHz × (1 - relativeTolerance) for maximumSeconds.

When to use this tool

Use Watchdog Clock Tolerance Interval when you need an explicit watchdog timing window or clock bound.

How to use the tool and how it works

  1. Enter ticks, nominalHz, relativeTolerance. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read minimumSeconds, maximumSeconds. Use the output convention below.

For positive ticks and nominalHz, divide ticks by nominalHz × (1 + relativeTolerance) for minimumSeconds and by nominalHz × (1 - relativeTolerance) for maximumSeconds.1

Input fieldMeaning and unitsAccepted input
ticksTicksRequired. Safe integer; minimum 1.
nominalHzNominal clock frequency in Hz.Required. Finite number; strictly above 0.
relativeToleranceDimensionless fractional tolerance; the applicable bound is specified above.Required. Finite number.
Output fieldInterpretationReturned shape
minimumSecondsMinimum SecondsRequired. Finite number.
maximumSecondsMaximum SecondsRequired. Finite number.
json
{
  "input": {
    "ticks": 100,
    "nominalHz": 100,
    "relativeTolerance": 0
  },
  "output": {
    "minimumSeconds": 1,
    "maximumSeconds": 1
  }
}

Limitations and assumptions

  • Tolerance is a fraction in [0, 1), not percent; this bounds a clock-derived interval without startup, quantization, or software latency.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Check the device datasheet and measured worst-case execution timing before relying on a refresh schedule.

References

  1. Calculation and input contract: microcontroller/watchdog-clock-tolerance-interval — tool.io

Similar or alternative tools