ForHosting KIT · Engineering & construction

Monostable timer period calculator

A 47 kΩ resistor and a 10 µF capacitor give a 0.517 s pulse (517 ms) with the usual factor of 1.1. Enter R and C, keep or change that factor, and get the duration of any RC one-shot. Free in your browser.

  • Free
  • Runs in your browser
  • No sign-up
  • Your data stays on your device
Use it from WebAPIEmailTelegramApp soon
If you enter
Resistance
47,000
Capacitance
0.00001
You get
Period seconds
0.517
Period milliseconds
517
Resistance ohms
47,000
Capacitance farads
0.00001

This monostable timer period calculator finds the stable output duration of a generic RC one-shot from its timing resistor and timing capacitor. It uses the common model T = K × R × C, with resistance in ohms, capacitance in farads, and the result in seconds. The coefficient defaults to 1.1 but remains adjustable because timer families and circuit topologies use different threshold ratios. The response also provides milliseconds, echoes normalized inputs, and identifies the applied formula for easy checking in design notes, lessons, and automated workflows.

Understand the generic monostable timing model

A monostable circuit has one stable state. A trigger temporarily moves its output into the other state, and an RC network determines how long the output remains there before returning. In the generic first-order model, that duration is T = K × R × C.

R is the timing resistance in ohms, C is the timing capacitance in farads, and K is a dimensionless coefficient set by the circuit thresholds and topology. Ohms multiplied by farads produce seconds, so the unit conversion is built into the formula. The default coefficient of 1.1 is a familiar one-shot approximation, but this calculator exposes K instead of assuming every monostable uses identical thresholds.

That distinction matters when working from a comparator circuit, logic-gate one-shot, timer datasheet, or application note that specifies another multiplier. Enter component values in base SI units and copy the coefficient from the governing design equation. The result is the ideal nominal period, not a promise about a physical assembly.

Resistor tolerance, capacitor tolerance, leakage, threshold variation, supply conditions, and temperature can all move a measured pulse away from the calculated center value. Use the nominal calculation to select parts, then apply worst-case analysis when timing limits are safety-critical or interface-critical.

Apply the result to selection and verification

Use the calculator early in a design to compare practical resistor and capacitor combinations. If a target period is known, rearrange the same equation to estimate one missing component, then enter the selected standard values here to confirm the actual nominal duration. Larger capacitors can introduce leakage and wide tolerance, while very large resistors can make a timing node more sensitive to contamination and input current, so several mathematically equivalent combinations may not be electrically equivalent.

The calculator deliberately reports the ideal RC result and does not hide these engineering choices behind an unexplained correction. In documentation, record the coefficient and source alongside the computed period; this prevents a later reviewer from assuming that 1.1, ln(2), or another threshold factor was intended. In test work, compare the nominal result with oscilloscope measurements across supply voltage and temperature, and set acceptance limits using component and device specifications.

Treat the result as the stable output pulse period for one trigger under the stated generic model, then consult the actual device datasheet before releasing hardware.

Choose one-shot timing parts

Compare standard resistor and capacitor pairs for a required nominal output pulse duration.

Check a datasheet equation

Apply the coefficient specified by a timer or comparator circuit and verify the resulting period.

What formula is used?

The calculator uses T = K × R × C, where R is in ohms, C is in farads, and T is in seconds.

Why is the coefficient adjustable?

Different monostable topologies and threshold ratios produce different multipliers. Use the value given by the relevant circuit or datasheet.

What coefficient is used by default?

The default is 1.1. Override it when the governing design equation specifies another positive value.

Can I enter 47k or 10uF?

No. Enter base SI numbers: 47000 ohms and 0.00001 farads. Unit suffix strings are not parsed.

Why is my measured pulse longer or shorter than the result?

Because the result is the ideal nominal period. Resistor and capacitor tolerance, leakage, threshold variation, supply conditions and temperature all move a real pulse away from it, so use a worst-case check when the timing really matters.

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

POSThttps://api.kit.forhosting.com/elec/monostable-period

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

curl -X POST https://api.kit.forhosting.com/elec/monostable-period \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"resistance":47000,"capacitance":0.00001}'
{
  "resistance": 47000,
  "capacitance": 0.00001
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "elec.monostable_period",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.

Enter values correctly and interpret the response

Provide resistance as a positive finite number of ohms and capacitance as a positive finite number of farads. For example, 47 kΩ should be entered as 47000, while 10 µF should be entered as 0.00001. Text suffixes such as kΩ, uF, or nF are intentionally not interpreted, because silent prefix mistakes can change a period by factors of one thousand or one million. You may provide coefficient when your circuit documentation gives a specific K value; otherwise the calculator uses 1.1. The short aliases r, c, and k are accepted for compact API calls, but do not send both an ordinary field and its alias in the same request. Successful output includes period_seconds and period_milliseconds so short pulses can be read without manual conversion. It also returns the normalized resistance, capacitance, coefficient, and formula. All arithmetic is deterministic and rounded to a stable significant precision for repeatable JSON output. Missing values, zero or negative components, non-finite numbers, duplicate aliases, and results beyond the supported numeric range return invalid_input rather than a misleading answer. A successful API item costs $0.002; the browser calculation can use the same pure calculation logic without network access.

Apply the result to selection and verification

The endpoint is also useful for generating worksheets, checking bills of materials, and adding deterministic timing assertions to scripts. It does not calculate repetitive astable frequency, duty cycle, recovery time, trigger requirements, maximum retrigger rate, or component stress. Those depend on additional circuit details.

Automate design checks

Generate repeatable seconds and milliseconds values for worksheets, BOM reviews, or test fixtures.

What does an API calculation cost?

Each successful API item uses the published base price of $0.002.

Read the full KIT documentation →