Skip to content

Main content

Microcontroller: RTC Sub Second Register Fraction Tool

Convert an explicit inclusive RTC subsecond counter value to elapsed fraction under a declared up/down convention; no device-specific latch or rollover assumptions.

Loading tool…

Description

For down counting use reload minus subsecondRegister; for up counting use the register itself.

Timer formulas depend on whether endpoints are inclusive, the count direction, prescaling, and wrap behavior. A counter reading alone cannot reveal an arbitrary number of elapsed wraps.

For down counting use reload minus subsecondRegister; for up counting use the register itself.

When to use this tool

Use Microcontroller: RTC Sub Second Register Fraction when you need a timer period, wrap delta, or explicit count-budget term.

How to use the tool and how it works

  1. Enter subsecondRegister, reload, countDirection. 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 result. Expand result to inspect the returned fields.

For down counting use reload minus subsecondRegister; for up counting use the register itself. Divide by reload + 1 for elapsedFraction.1

Input fieldMeaning and unitsAccepted input
subsecondRegisterSubsecond RegisterRequired. Safe integer.
reloadReloadRequired. Safe integer.
countDirectionCount DirectionRequired. Text; one of "up", "down". Implementation limit: 8192 Unicode code points and 16384 UTF-16 code units.
Output fieldInterpretationReturned shape
resultResultRequired. Object.
result.elapsedFractionElapsed FractionCalculated result member: number.
json
{
  "input": {
    "subsecondRegister": 7,
    "reload": 9,
    "countDirection": "down"
  },
  "output": {
    "result": {
      "elapsedFraction": 0.2
    }
  }
}

Limitations and assumptions

  • The supplied register must be within the inclusive reload range; synchronization and device-specific RTC behavior are not handled.
  • Outputs are nested inside result. 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 timer mode and register semantics in the device documentation, including synchronization and latency.

References

  1. Calculation and input contract: microcontroller/rtc-sub-second-register-fraction — tool.io

Similar or alternative tools