DEV Community: Evgenii Konkin

Why the 1.08 Constant in HVAC Sensible Heat Formulas Fails at Altitude

Evgenii Konkin — Fri, 04 Sep 2026 04:23:02 +0000

The standard sensible heat formula for air systems:

Q (BTU/hr) = 1.08 × CFM × ΔT

That 1.08 constant comes from:

1.08 = ρ × Cp × 60

Where:
ρ  = 0.075 lb/ft³ (air density at sea level, 59°F)
Cp = 0.24 BTU/lb·°F (specific heat of air)
60 = minutes per hour

0.075 × 0.24 × 60 = 1.08

The problem: 0.075 lb/ft³ is only valid at sea level and 59°F.

Air density from the ideal gas law

ρ = P / (R × T)

Where:

ρ = air density, kg/m³
P = absolute atmospheric pressure, Pa
R = 287.058 J/(kg·K) (specific gas constant for dry air)
T = absolute temperature, K

At sea level, 15°C (59°F):

ρ = 101,325 / (287.058 × 288.15)
ρ = 1.225 kg/m³
ρ = 0.0765 lb/ft³

What changes at altitude

Atmospheric pressure drops with elevation:

P = 101,325 × (1 − 0.0000225577 × h)^5.25588

Where h is altitude in meters.

Altitude    Pressure (Pa)    Density (kg/m³)    vs Sea Level
──────────────────────────────────────────────────────────────
Sea level   101,325          1.225              baseline
1,000 m     89,875           1.112              −9.2%
1,500 m     84,556           1.058              −13.6%
2,000 m     79,501           1.007              −17.8%
2,500 m     74,692           0.957              −21.9%

At Denver (1,609 m / 5,280 ft):

P = 101,325 × (1 − 0.0000225577 × 1609)^5.25588
P ≈ 83,436 Pa

ρ = 83,436 / (287.058 × 288.15)
ρ ≈ 1.009 kg/m³ (vs 1.225 at sea level)

That is an 18% density reduction.

Impact on the sensible heat constant

The 1.08 constant scales linearly with density:

Sea level:    1.08 × (1.225/1.225) = 1.08
Denver:       1.08 × (1.009/1.225) = 0.89
Albuquerque:  1.08 × (0.957/1.225) = 0.84
Mexico City:  1.08 × (0.880/1.225) = 0.78

A system designed with 1.08 in Denver actually delivers:

Q_actual = 0.89 × CFM × ΔT

vs

Q_assumed = 1.08 × CFM × ΔT

The system delivers 18% less cooling capacity than the calculation predicted.

Temperature effect

Even at sea level, hot air is thinner:

Temperature    Density (kg/m³)    vs Standard (15°C)
─────────────────────────────────────────────────────
15°C (59°F)    1.225              baseline
25°C (77°F)    1.184              −3.3%
35°C (95°F)    1.146              −6.5%
45°C (113°F)   1.110              −9.4%

Rule of thumb: density drops about 3.3% per 10°C (18°F) temperature increase.

Combined effect

Denver at 95°F outdoor air:

Altitude effect:    −18%
Temperature effect: −6.5%
Combined:           −23%

Corrected constant: 1.08 × 0.77 = 0.83

A system designed with 1.08 at those conditions overstates capacity by nearly a quarter.

When to correct

Always correct when:
  Altitude > 2,000 ft (600 m)
  Air temperature > 100°F (38°C)
  Both conditions combined

Usually safe to skip when:
  Sea level to 1,000 ft
  Air temperature 60–80°F
  Both conditions apply

What this calculation does not cover

It does not account for:
  Humidity (adds 1–2% variation in standard HVAC range)
  Non-standard atmospheric conditions
  Fan curve shift at altitude
  Motor derating at altitude
  Combustion air correction for gas equipment

The density calculation is a first-pass correction. Full altitude design requires adjusted fan curves, motor derating factors, and combustion analysis for gas-fired equipment.

Quick Tip: Dew Point vs Relative Humidity for Condensation Risk

Evgenii Konkin — Thu, 03 Sep 2026 03:56:58 +0000

Relative humidity tells you a ratio. Dew point tells you where condensation will form.

RH = how full the air is relative to its capacity at that temperature
Dew point = the temperature at which moisture starts condensing

The critical difference: RH changes when you heat or cool the air. Dew point does not (unless you add or remove moisture).

Same room, different RH, different condensation risk

Scenario A:
  Room: 75°F, 50% RH
  Dew point: 55°F
  Cold water pipe surface: 50°F
  50°F < 55°F → condensation forms

Scenario B:
  Room: 75°F, 30% RH
  Dew point: 41°F
  Cold water pipe surface: 50°F
  50°F > 41°F → pipe stays dry

The rule: condensation forms when a surface temperature drops below the dew point. Not below some RH percentage.

Dew point depression as a quick diagnostic

Depression = Dry-bulb temp − Dew point temp

< 5°F   → near saturation, high condensation risk
15–35°F → typical comfortable range
> 55°F  → very dry air

Comfort boundary

ASHRAE 55 upper comfort limit: ~62°F dew point
Typical comfortable range:     50–60°F dew point
                               (~40–55% RH at 75°F)

Above 62°F dew point, most people feel the air is too humid regardless of the thermostat setting.

Why RH alone fails

Heat the air from 75°F to 95°F without adding moisture:

Before: 75°F, 50% RH, dew point 55°F
After:  95°F, 23% RH, dew point 55°F

RH dropped from 50% to 23%. Feels drier. But the dew point is still 55°F. The same cold pipe will still sweat.

For quick dew point checks from dry-bulb and RH or wet-bulb readings, there is a dew point calculator on CalcEngineer.

CFM Calculation: Why Floor Area Is Not Enough to Size Ventilation

Evgenii Konkin — Wed, 02 Sep 2026 04:21:33 +0000

The CFM formula for room ventilation:

CFM = (L × W × H × ACH) / 60

Where:

L = room length, ft
W = room width, ft
H = ceiling height, ft
ACH = air changes per hour
60 = minutes per hour (converts ft³/hr to ft³/min)

The metric version:

Airflow (m³/hr) = L × W × H × ACH

The volume mistake

The most common error: using floor area instead of volume.

Room: 20 ft × 15 ft
Floor area: 300 ft²

With 9 ft ceilings:
Volume = 300 × 9 = 2,700 ft³
CFM = 2,700 × 6 / 60 = 270 CFM

With 12 ft ceilings:
Volume = 300 × 12 = 3,600 ft³
CFM = 3,600 × 6 / 60 = 360 CFM

Same footprint. 33% more air required. If you sized the fan for 270 CFM in the 12-foot room, the actual air change rate drops to 4.5 ACH instead of 6.

ACH requirements by space type

Space type                ACH
────────────────────────────────
Residential living room   4–6
Office, retail            6–8
Kitchen, restaurant       8–12
Laboratory, hospital      10–20+
Clean room                20–60+
Industrial, welding       15+

Choosing the wrong ACH is worse than getting the volume wrong. An office at 6 ACH is comfortable. A lab at 6 ACH violates ASHRAE 62.1.

Worked example

Office space:

Room: 20 × 15 × 9 ft
ACH: 6 (standard office)

Volume = 20 × 15 × 9 = 2,700 ft³
CFM = 2,700 × 6 / 60
CFM = 270

The room needs 270 CFM of delivered air.

Fan selection: add system losses

The 270 CFM is room demand. The fan must overcome:

Duct friction
Filter pressure drop
Damper resistance
Fitting losses

Rule of thumb: add 10–20% to calculated CFM for fan selection.

Room demand:     270 CFM
System margin:   +15%
Fan selection:   270 × 1.15 = 311 CFM

Select a fan rated at 310+ CFM at the design static pressure. Not 270.

CFM vs FPM

These are different measurements:

CFM = volume flow rate (ft³/min)  → how much air
FPM = velocity (ft/min)           → how fast the air moves

They are related through duct area:

CFM = FPM × Duct Area (ft²)

Example:

270 CFM through a 12-inch round duct:
Area = π × (12/24)² = 0.785 ft²
FPM = 270 / 0.785 = 344 FPM

Specifying 270 FPM instead of 270 CFM is a completely different number. One is volume. The other is velocity.

What the CFM calculation does not cover

It does not account for:
  Outdoor air ventilation requirements (ASHRAE 62.1)
  Exhaust makeup air
  Pressurization requirements
  Duct static pressure budget
  Noise criteria
  Thermal load matching
  Humidity control

The volume × ACH method is a screening estimate. It tells you approximately how much air the room needs. Full ventilation design requires ASHRAE procedures, duct sizing, and fan curve analysis.

Quick Tip: HVAC Delta T Ranges You Should Know

Evgenii Konkin — Tue, 01 Sep 2026 04:16:08 +0000

Delta T is the temperature difference between return air and supply air:

ΔT = T_return − T_supply

Normal ranges by system type:

System                    ΔT (°F)
──────────────────────────────────
Residential cooling (DX)  14–22
Gas furnace               40–70
Heat pump (heating)       25–35
Chilled water             10–12
Hot water boiler          20–40
Condenser water           10–15

What out-of-range delta T tells you

In cooling mode:

ΔT < 14°F → low refrigerant charge
             excessive airflow
             dirty evaporator coil

ΔT > 22°F → restricted airflow
             dirty filter
             frozen coil

In heating mode (gas furnace):

ΔT > 70°F → low airflow through heat exchanger
             potential cracking risk

From delta T to capacity

Combine delta T with airflow to get sensible capacity:

Q (BTU/hr) = 1.08 × CFM × ΔT

Example:

CFM = 1,000
ΔT  = 20°F

Q = 1.08 × 1,000 × 20
Q = 21,600 BTU/hr
Q = 1.8 tons

If the system is rated at 2 tons, it is delivering 90% of capacity. Normal.

If ΔT drops to 12°F:

Q = 1.08 × 1,000 × 12
Q = 12,960 BTU/hr
Q = 1.08 tons → 54% of rated capacity

Something is wrong. The homeowner feels it.

Two measurement rules

1. Supply temp: measure 6+ ft downstream from coil (not at coil exit)
2. Wait 15+ min after startup before reading (steady-state required)

Breaking either rule gives a false delta T.

The Energy Cost Formula Most Engineers Use Wrong for Three-Phase Loads

Evgenii Konkin — Mon, 31 Aug 2026 04:08:47 +0000

Energy consumption is power multiplied by time:

kWh = kW × hours

Cost is energy multiplied by rate:

Cost = kWh × rate per kWh

The challenge is getting the power number right. For single-phase loads, power in watts is:

P = V × I × PF

For three-phase loads:

P = √3 × V × I × PF
P = 1.732 × V × I × PF

The 1.732 is the square root of 3. It accounts for the phase relationship in a three-phase system. Leaving it out underestimates three-phase power by 42 percent.

Example: one motor, one year

A commercial HVAC chiller motor:

Voltage:      480V line-to-line
Current:      100A
Power factor: 0.85
Runtime:      8 hours/day
Rate:         $0.15/kWh

Step 1 — calculate power:

P = 1.732 × 480 × 100 × 0.85
P = 70,668 W
P = 70.7 kW

Step 2 — daily energy:

kWh/day = 70.7 × 8
kWh/day = 565.3

Step 3 — monthly energy:

kWh/month = 565.3 × 30.44
kWh/month = 17,207

Step 4 — monthly cost:

Cost/month = 17,207 × $0.15
Cost/month = $2,581

Step 5 — annual cost:

Cost/year = $2,581 × 12
Cost/year = $30,972

One motor. Thirty thousand dollars a year.

The three mistakes that break the calculation

Mistake 1: using nameplate power for cycling loads

A 5 kW compressor with a 60 percent duty cycle does not consume 5 kW continuously.

Nameplate calculation: 5 kW × 8 hr = 40 kWh/day
Actual calculation:    5 kW × 8 hr × 0.60 = 24 kWh/day

The nameplate method overstates consumption by 67 percent. Use measured average power or apply the duty cycle factor.

Mistake 2: ignoring power factor

Calculating power as voltage times current without power factor gives apparent power in kVA, not real power in kW.

Without PF: P = 1.732 × 480 × 100 = 83,138 VA = 83.1 kVA
With PF:    P = 1.732 × 480 × 100 × 0.85 = 70,668 W = 70.7 kW

The electricity meter measures real power (kW), not apparent power (kVA). Omitting power factor overstates energy consumption by 18 percent for a motor at PF 0.85.

Mistake 3: entering rate as whole cents

Wrong: rate = 15    → cost = 17,207 × 15 = $258,105/month
Right: rate = 0.15  → cost = 17,207 × 0.15 = $2,581/month

One hundred times too high. This happens in spreadsheet calculations more often than anyone admits.

Why it matters for equipment decisions

When you know the per-equipment energy cost, upgrade decisions become math:

Motor annual cost:           $30,972
VFD savings (30% reduction): $9,292/year
VFD installed cost:          $5,000
Payback period:              6.5 months

Without the per-equipment calculation, this decision is a guess. With it, the payback is obvious.

What the formula does not cover

It does not account for:
  Demand charges (kW peak billing)
  Tiered rate structures
  Time-of-use pricing
  Power factor penalties
  Tax and distribution fees
  Motor efficiency losses
  Seasonal load variation
  Actual metered data

The kWh cost calculation is a screening estimate. It tells you the approximate operating cost of a piece of equipment at a flat rate. For precise energy accounting, use metered data and your actual utility rate schedule.

Quick reference

For any piece of equipment, you need three numbers:

1. Power in kW
2. Daily runtime in hours
3. Electricity rate in $/kWh

Multiply all three for daily cost. Multiply by 30.4 for monthly. By 365 for annual.

For three-phase equipment where you only know voltage and current:

kW = 1.732 × V × I × PF

Use PF = 0.85 for motors, 0.95 for electronic loads, 1.0 for heaters.

For quick energy cost estimates with single-phase, three-phase, and direct kWh entry, there is an energy consumption calculator on CalcEngineer.

Duct Sizing: The Aspect Ratio Mistake That Doubles Friction Loss

Evgenii Konkin — Fri, 28 Aug 2026 05:15:33 +0000

Duct sizing starts with one formula:

Area = Airflow / Velocity

In imperial units:

A (ft²) = Q (CFM) / V (FPM)

Where:

A = duct cross-sectional area, ft²
Q = airflow rate, CFM
V = air velocity, FPM

For a round duct, the diameter is:

D = √(4A / π)

For a rectangular duct with a known width:

H = A / W

These formulas are simple. The mistakes come from what happens after the calculation.

Example: sizing a 1,200 CFM supply duct

Given:

Q = 1,200 CFM
V = 800 FPM (commercial branch supply)

Calculate area:

A = 1,200 / 800
A = 1.5 ft²
A = 216 in²

Calculate round diameter:

D = √(4 × 1.5 / π)
D = √(1.909)
D = 1.382 ft
D = 16.6 inches

Standard round duct sizes go 14, 16, 18, 20 inches. The calculation lands between 16 and 18. Select 18 inches.

If you select 16 inches instead:

A_16 = π × (16/2)² = 201 in² = 1.396 ft²
V_actual = 1,200 / 1.396 = 859 FPM

That is still within the commercial branch range of 500 to 900 FPM. Acceptable.

If you select 14 inches:

A_14 = π × (14/2)² = 154 in² = 1.069 ft²
V_actual = 1,200 / 1.069 = 1,122 FPM

Now velocity exceeds the branch supply range. Noise and friction increase significantly.

The rectangular aspect ratio problem

When ceiling space is tight, engineers switch to rectangular duct. Same area, different shape. But not all rectangles perform equally.

For 216 in² of area, you could use:

Option A: 24 × 9 inches  (aspect ratio 2.7:1)
Option B: 18 × 12 inches (aspect ratio 1.5:1)
Option C: 36 × 6 inches  (aspect ratio 6.0:1)

All three have the same area. But the equivalent round diameter is different for each:

De = 1.3 × (W × H)^0.625 / (W + H)^0.25

Calculate for each option:

Option A (24×9):  De = 15.6 in
Option B (18×12): De = 16.1 in
Option C (36×6):  De = 13.8 in

Option C has the same cross-sectional area but behaves like a duct that is 2.3 inches smaller in equivalent diameter. That means more friction, more pressure drop, more fan energy.

The rule: keep aspect ratios at 4:1 or below. Above that, friction loss increases faster than the space savings justify.

Velocity guidelines by application

Application              FPM          m/s
─────────────────────────────────────────
Residential supply       400–700      2.0–3.6
Commercial branch        500–900      2.5–4.6
Commercial main supply   700–1,500    3.5–7.6
Return air               500–1,200    2.5–6.1
Kitchen exhaust          1,500–2,500  7.6–12.7
Industrial exhaust       1,000–4,000  5.1–20.3

Residential is the most noise-sensitive. Most homeowners notice duct noise above 700 FPM.

What the duct size calculation does not cover

It does not verify:
  Friction loss per 100 ft of duct
  System static pressure budget
  Fitting equivalent lengths
  Noise criteria (NC) rating
  Duct leakage class
  Insulation requirements
  Fire damper pressure drop
  ASHRAE 90.1 fan power limits

The area-velocity calculation is a first-pass screen. It tells you whether the duct is in the right size range. Full duct design requires equal friction or static regain methods per ASHRAE and SMACNA standards.

How Power Factor Turns a 100 kVA Generator Into 80 kW of Usable Power

Evgenii Konkin — Wed, 26 Aug 2026 06:22:49 +0000

A generator nameplate shows two numbers: kVA and kW. They are not the same thing.

The difference between them is power factor.

The conversion formula is:

kW = kVA × PF

Where:

kW = real power (useful work)
kVA = apparent power (total demand on the source)
PF = power factor of the connected load (0 to 1.0)

Power factor tells you what fraction of the current flowing through the circuit is actually doing useful work. The rest is reactive current. It flows through the conductors, heats up the cables, occupies transformer capacity, and performs zero work. The source has to supply it, the cables have to carry it, but the load gives it back every half cycle.

For resistive loads, PF = 1.0. For induction motors, PF is typically 0.75 to 0.90. For mixed commercial buildings, 0.80 to 0.85 is a common range.

Example: generator sizing for a chiller plant

A mechanical contractor needs standby power for a chiller plant. The equipment list:

Equipment                kW      PF      kVA
Chiller compressor       150     0.85    176.5
Chilled water pumps       30     0.82     36.6
Condenser water pumps     25     0.82     30.5
Cooling tower fans        15     0.80     18.8
Controls and lighting     10     0.95     10.5
─────────────────────────────────────────────
Total                    230     0.843   272.9

Each kVA value is calculated as:

kVA = kW / PF

For the chiller compressor:

kVA = 150 / 0.85
kVA = 176.5

The composite power factor of the entire plant is:

PF = 230 kW / 272.9 kVA
PF = 0.843

Total apparent power demand is 272.9 kVA.

The sizing mistake

If you order a 250 kVA generator, you might think you have 20 kW of headroom.

Real power demand:     230 kW
Generator kW rating:   250 kVA × 0.80 PF = 200 kW (typical rating)

But the apparent power demand tells a different story:

Apparent power demand: 272.9 kVA
Generator capacity:    250 kVA
Deficit:               22.9 kVA over limit

The 250 kVA generator is oversized by 20 kW but undersized by 23 kVA. It will trip on overcurrent even though the kW load is within rating.

The overcurrent protection sees 272.9 kVA against a 250 kVA limit and does exactly what it is supposed to do.

Correct selection

kVA required = 230 / 0.843 = 273 kVA minimum

A 300 kVA generator is the correct selection. That gives you 273 kVA demand against 300 kVA capacity, plus margin for motor starting current which the steady-state calculation does not include.

The nameplate trap

Some manufacturers rate generators at 0.80 PF:

"250 kVA / 200 kW" = manufacturer already applied 0.80

Other manufacturers, especially in the European market, rate at unity PF:

"250 kVA / 250 kW" = assumes all loads are resistive

Same kVA rating. Very different real capacity for motor loads.

Always check whether the nameplate kW is at rated PF or at unity.

Motor starting makes it worse

Motor starting current can draw 5 to 7 times the running current for several seconds. During that inrush, the power factor drops dramatically, sometimes below 0.30.

Running:  150 kW at PF 0.85 = 176 kVA
Starting: 150 kW × 6 inrush at PF 0.30 = approx 3,000 kVA transient

The generator must handle that transient kVA demand without voltage collapse.

This is why generator sizing requires more than just adding up nameplate kW. But the first step, before you even get to starting analysis, is making sure you are not confusing kVA with kW.

What the kVA to kW conversion does not cover

A correct kVA to kW conversion does not mean the generator is fully sized.

It does not verify:
  Motor starting kVA
  Harmonic distortion
  Transient response
  Step loading sequence
  Altitude or temperature derating
  Fuel system capacity
  Manufacturer acceptance

The kVA to kW check is a first-pass screen.

It tells you whether the source capacity matches the load demand in both real and apparent power.

It does not prove the full system design is complete.

Practical takeaway

Before ordering a generator, transformer, or UPS for a mixed load:

1. List all equipment with kW and power factor
2. Calculate kVA for each: kVA = kW / PF
3. Sum the kVA column (not just the kW column)
4. Compare total kVA to the source kVA rating
5. Check whether the manufacturer's kW rating is at 0.80 PF or unity

That is enough to catch the most common sizing mistake before it becomes a commissioning problem.

Harmonic Filter Design: The LC Tuning Mistake That Can Miss the Target Harmonic

Evgenii Konkin — Sun, 09 Aug 2026 07:41:12 +0000

A passive harmonic filter can look correct on a drawing.
A reactor.
A capacitor.
A target harmonic order.

But if the LC values tune the filter to the wrong frequency, the filter may not absorb the harmonic it was supposed to handle.

That is the basic risk in harmonic filter design.

The key formula is:

f_t = 1 / (2π√(LC))

Where:

f_t = filter tuning frequency, Hz
L = reactor inductance, H
C = capacitor capacitance, F

Once the tuning frequency is known, the actual tuning harmonic order is:

h_t = f_t / f_1

And the target harmonic frequency is:

f_target = h_target × f_1

For a 60 Hz system, the 5th harmonic is:

f_target = 5 × 60
f_target = 300 Hz

So if a filter intended for the 5th harmonic is actually tuned near 300 Hz, it is in the right region.

If it is tuned far away from 300 Hz, the filter may miss the problem.

Example: a filter intended for the 5th harmonic

Suppose a passive LC filter has:

L = 5 mH
C = 100 µF
f_1 = 60 Hz
Target harmonic = 5th

Convert units first:

L = 5 / 1000 = 0.005 H
C = 100 / 1,000,000 = 0.0001 F

Calculate the LC product:

LC = 0.005 × 0.0001
LC = 0.0000005

Now calculate tuning frequency:

f_t = 1 / (2π√0.0000005)
f_t ≈ 225 Hz

The actual tuning harmonic order is:

h_t = 225 / 60
h_t ≈ 3.75

But the target 5th harmonic frequency is:

f_target = 5 × 60
f_target = 300 Hz

Now calculate detuning:

Detuning = [(225 − 300) / 300] × 100
Detuning ≈ −25%

The filter is tuned about 25% below the target harmonic.

That is not a small difference.

It means the selected reactor and capacitor values do not align well with the intended 5th harmonic target.

The common mistake: checking the THD but not the tuning

A common workflow mistake is:

Measure high THD.
Decide the 5th harmonic is the problem.
Install a passive filter.
Assume the filter is tuned correctly.

But the LC values decide where the filter actually resonates.

The label or design intent does not tune the filter.

The formula does.

A filter intended for the 5th harmonic can end up closer to the 4th harmonic region if the inductance or capacitance is wrong.

That can reduce attenuation at the intended harmonic and may create unwanted interaction with the system impedance.

Detuning is not always bad

A filter does not always need to be tuned exactly on the target harmonic.

In many capacitor bank applications, engineers intentionally tune slightly below the lowest dominant harmonic. For example, a system with strong 5th harmonic distortion may use a detuned filter around order 4.7 or 4.85.

That is done to reduce resonance risk.

So the issue is not simply:

Exact target = good
Any detuning = bad

The better question is:

Is the detuning intentional and within the expected design range?

A small negative detuning may be part of a good design.

A large accidental detuning is a warning sign.

Unit mistakes can destroy the result

The LC formula is very sensitive to units.

The calculator expects:

Inductance in mH
Capacitance in µF

and converts them internally to:

H
F

If someone enters 5 mH as 5 H, the tuning frequency shifts by a huge amount.

If someone enters 100 µF as 100 F, the result becomes unrealistic.

This is why the first review step should always be:

Check mH vs H.
Check µF vs F.
Check 50 Hz vs 60 Hz.
Check the target harmonic order.

The formula itself is simple.

The input units are where the mistake often starts.

What the calculation does not prove

A correct tuning frequency does not mean the harmonic filter is fully designed.

It does not verify:

Harmonic attenuation
System impedance scan
Quality factor
Damping
Capacitor kvar
Reactor current rating
Thermal loading
Switching transients
Resonance amplification
IEEE 519 or utility compliance

The LC tuning check is a first-pass design screen.

It tells you whether the filter is aimed at the right frequency region.

It does not prove that the full power quality problem is solved.

Practical takeaway

Use the harmonic filter tuning calculation early.

It helps answer:

What frequency is this LC filter actually tuned to?
Which harmonic order does that represent?
How far is it from the intended target harmonic?
Is the detuning intentional or accidental?
Are the L and C units entered correctly?

That is enough to catch many obvious filter selection mistakes before going deeper into manufacturer review, harmonic measurements, or a full impedance study.

Final thought

A passive harmonic filter is not tuned by its name.

It is tuned by its inductance and capacitance.

f_t = 1 / (2π√(LC))

If the LC values put the filter near the intended harmonic, the design may be moving in the right direction.

If the tuning point is far from the target harmonic, the filter may miss the harmonic it was meant to absorb.

For quick checks of passive single-tuned LC harmonic filters, tuning harmonic order, target frequency, and detuning percentage, use the Harmonic Filter Design Calculator on CalcEngineer.

Ground Ring Resistance: The Soil Resistivity Mistake That Can Break a Grounding Estimate

Evgenii Konkin — Wed, 05 Aug 2026 17:05:05 +0000

Ground ring resistance looks like a simple grounding calculation.

Enter soil resistivity.

Enter ring size.

Enter conductor diameter.

Get resistance in ohms.

But the result can change dramatically depending on one input: soil resistivity.

That is where many early grounding estimates become misleading.

A ground ring may look acceptable in moist clay and completely weak in dry sand or rocky soil. The same conductor. The same ring diameter. Very different resistance to earth.

The formula is useful, but it should not be treated as a final grounding design.

It is a screening tool.

The basic ground ring resistance formula

For a single circular buried ground ring, the resistance can be estimated with:

R = (ρ / 2π²r) × ln(8r / d)

Where:

R = ground ring resistance, ohms
ρ = soil resistivity, Ω·m
r = ring radius, m
d = conductor diameter, m
ln = natural logarithm

The formula shows three important things:

Higher soil resistivity increases resistance.
Larger ring radius reduces resistance.
Larger conductor diameter reduces resistance, but usually less strongly.

That last point matters.

Increasing conductor diameter may help a little, but increasing the ring radius or improving the grounding system layout usually has a much stronger effect.

Soil resistivity is the big driver

Soil resistivity is often the most important input.

For example, use:

ρ = 100 Ω·m
r = 5 m
d = 20 mm = 0.020 m

First check the geometry ratio:

8r / d = (8 × 5) / 0.020
8r / d = 2000

Natural logarithm:

ln(2000) ≈ 7.601

Denominator:

2π²r = 2 × π² × 5
2π²r ≈ 98.696

Now calculate resistance:

R = (100 / 98.696) × 7.601
R ≈ 7.70 Ω

So the estimated ground ring resistance is:

R ≈ 7.70 Ω

That may be a moderate result depending on the project target.

Now keep the same ring geometry, but change only the soil resistivity.

If the site has dry or rocky soil:

ρ = 500 Ω·m

Because soil resistivity is directly proportional in the formula, the result becomes about five times higher:

R ≈ 38.5 Ω

Same ring.

Same conductor.

Different soil.

Very different grounding performance.

That is the engineering lesson.

The soil assumption can dominate the result.

The common mistake: using a guessed soil resistivity

A frequent early-design mistake is entering a generic soil resistivity value without checking whether it matches the actual site.

For example:

Assumed soil resistivity = 100 Ω·m
Actual dry-site resistivity = 500 Ω·m

The estimate can look five times better than reality.

That is not a small rounding error.

It can change the design decision completely.

With 100 Ω·m, the engineer may think:

The ring is probably acceptable.

With 500 Ω·m, the better conclusion may be:

The ring alone is likely not enough.
Additional grounding measures or field testing are needed.

So the ground ring calculation should always be tied to a realistic soil resistivity assumption.

For serious projects, that means soil resistivity testing, not just a table value.

Ring radius matters more than conductor diameter

The formula also explains why ring size is powerful.

Resistance is divided by ring radius:

R ∝ 1 / r

There is also a logarithmic term, but the main practical effect is clear: a larger ring usually reduces resistance significantly.

Using the same soil:

ρ = 100 Ω·m
d = 20 mm

At:

r = 5 m

we got:

R ≈ 7.70 Ω

Now increase the radius:

r = 10 m

The new estimate is about:

R ≈ 4.20 Ω

That is a major improvement.

Now compare that with increasing conductor diameter instead.

Keep:

ρ = 100 Ω·m
r = 5 m

Double the conductor diameter:

d = 20 mm → 40 mm

The result improves only from about:

7.70 Ω → 7.00 Ω

That helps, but it is not nearly as strong as increasing the ring radius.

Why?

Because conductor diameter is inside the logarithm:

ln(8r / d)

Logarithmic changes are slower.

This is why oversizing the grounding conductor is not always the most effective way to reduce earth resistance.

The layout and soil conditions usually matter more.

Radius vs diameter: a simple input mistake

Another common mistake is entering ring diameter as ring radius.

Suppose the actual ground ring has:

Diameter = 10 m
Radius = 5 m

The calculator asks for radius.

If the engineer accidentally enters:

r = 10 m

instead of:

r = 5 m

the result may look much better than reality.

With:

ρ = 100 Ω·m
d = 20 mm

Correct radius:

r = 5 m
R ≈ 7.70 Ω

Wrong radius input:

r = 10 m
R ≈ 4.20 Ω

That mistake can make the grounding design look stronger than it really is.

The physical ring did not improve.

Only the input was wrong.

This is why radius and diameter should be checked carefully before trusting the result.

What the calculation does not prove

A single-ring resistance estimate is not a complete grounding design.

It does not model:

Layered soil
Multiple ground rods
Grounding grids or meshes
Ring-plus-rod systems
Touch voltage
Step voltage
Ground potential rise
Fault current distribution
Lightning impulse behavior
Seasonal soil moisture changes
Corrosion or clamp resistance
Field measurement results

That limitation matters.

A low resistance value is useful, but grounding safety is not only about one ohm number.

For substations, towers, generator pads, transformer pads, solar inverters, battery systems, and industrial equipment, the grounding review may need much more than single-ring resistance.

A good result from the formula means:

This single-ring estimate looks promising.

It does not mean:

The grounding system is fully verified.

Practical design takeaway

Use ground ring resistance as an early screening calculation.

It helps answer:

Is the ring likely to be low, moderate, or high resistance?
How sensitive is the result to soil resistivity?
Would a larger ring radius help?
Is conductor diameter actually the best place to improve the design?
Does the project need supplemental electrodes or a grounding grid?
Is field testing required before final acceptance?

But do not use it as the final safety decision.

The most important engineering habit is to separate:

Preliminary calculation
Final grounding design
Field verification

The formula gives the first part.

It does not replace the other two.

Final thought

Ground ring resistance is not just a conductor-size calculation.

It is mainly a soil and geometry problem.

A ring in low-resistivity soil can perform very differently from the same ring in dry, rocky ground.

Increasing the conductor diameter may help a little, but increasing the ring radius or changing the grounding layout often has a much stronger effect.

And if the wrong soil resistivity or wrong radius is entered, the result can look much better than the real installation.

For quick preliminary checks of a single circular buried ground ring using soil resistivity, ring radius, and conductor diameter, use the Ground Ring Resistance Calculator on CalcEngineer.

Residential Electrical Load: The Service Size Mistake Hidden Behind Square Feet

Evgenii Konkin — Thu, 30 Jul 2026 04:59:23 +0000

A house does not need a 200 A service just because it is “modern.”

And it does not automatically fit on an old 100 A service just because the lights turn on today.

Residential service sizing is more structured than that.

The calculation starts with floor area, small-appliance circuits, laundry, major appliances, HVAC, motors, and EV charging. Then demand factors are applied. The result is a calculated load in volt-amperes and amperes.

The mistake is thinking this is just a square-footage problem.

It is not.

A 2,000 ft² house with gas appliances can look very different from a 2,000 ft² all-electric house with electric heat, electric range, dryer, and EV charger.

Same floor area.

Very different service calculation.

The basic idea

A dwelling electrical load calculation tries to answer a practical question:

How much load should the service be sized for?

The result is usually expressed as:

Total Calculated Load = VA
Service Current = Total VA / Service Voltage
Recommended Service Size = next standard ampere rating above the sizing basis

For a typical one-family dwelling service:

Service Voltage = 240 V

So:

Service Current = Total Calculated Load / 240

If the calculated load is:

Total Calculated Load = 33,125 VA

Then:

Service Current = 33,125 / 240
Service Current ≈ 138 A

The next common standard service size above that is:

150 A

That is the engineering logic.

But getting the 33,125 VA number is where most of the work happens.

General dwelling loads

The general load starts with floor area.

For the standard dwelling calculation:

Lighting VA = Floor Area × 3 VA/ft²

Then add required small-appliance and laundry circuits:

Small-appliance circuits = 1,500 VA each
Laundry circuits = 1,500 VA each

A common baseline for a dwelling is:

2 small-appliance circuits
1 laundry circuit

That adds:

2 × 1,500 + 1 × 1,500 = 4,500 VA

before the range, dryer, HVAC, fixed appliances, EV charger, or motor loads are even considered.

This is one of the first mistakes engineers and homeowners make.

They start with the visible appliances, but forget that the base dwelling calculation already includes required circuit allowances.

Example: base general load

Suppose a dwelling has:

Floor area = 2,000 ft²
Small-appliance circuits = 2
Laundry circuits = 1

Calculate lighting load:

Lighting VA = 2,000 × 3
Lighting VA = 6,000 VA

Add the small-appliance and laundry circuits:

General VA = 6,000 + 2 × 1,500 + 1 × 1,500
General VA = 6,000 + 3,000 + 1,500
General VA = 10,500 VA

So the general load starts at:

10,500 VA

That is before adding the range, dryer, fixed appliances, HVAC, largest motor, or EV charger.

This is why “just use watts per square foot” is not enough.

The service calculation is not only an area calculation.

Standard method demand factors

Under the standard method, general lighting demand is not simply carried at 100% forever.

A simplified demand structure is:

First 3,000 VA @ 100%
Next portion up to 120,000 VA @ 35%
Remainder @ 25%

For the 10,500 VA general load example:

First 3,000 VA = 3,000 VA
Remainder = 10,500 − 3,000
Remainder = 7,500 VA

Apply 35% to the remainder:

Remainder demand = 7,500 × 0.35
Remainder demand = 2,625 VA

Total lighting/general demand:

General demand = 3,000 + 2,625
General demand = 5,625 VA

Notice what happened.

The connected general load was:

10,500 VA

But the demand load became:

5,625 VA

That is why residential service calculations cannot be done by simply adding all nameplate loads at 100%.

Demand factors matter.

Range demand is not always nameplate

A household range is another common source of mistakes.

For one household range:

Range ≤ 12 kW → 8,000 VA demand

So a 12 kW range does not necessarily enter the standard method as 12,000 VA.

It can enter as:

8,000 VA

That surprises people.

The nameplate is not always the demand value.

For a range above 12 kW, an adjustment is applied, but the key engineering habit is simple:

Do not blindly enter range nameplate as full demand under the standard method.

Use the correct demand rule for the calculation method and range size.

Dryer load has a floor

A household dryer is also easy to misread.

The dryer demand is:

Dryer demand = max(5,000 VA, nameplate VA)

So if a dryer nameplate is:

4,500 VA

the demand value is not 4,500 VA.

It is:

5,000 VA

The mistake is entering the smaller nameplate and thinking the load calculation is finished.

The floor matters.

Fixed appliances and the 75% factor

Other fixed appliances may include:

Water heater
Dishwasher
Garbage disposal
Built-in microwave
Trash compactor
Other fastened-in-place appliances

For the standard method, when there are four or more fixed appliances, a 75% demand factor may apply:

Fixed appliance demand = Total fixed appliance VA × 0.75

But this factor does not apply to everything.

A common mistake is applying the 75% factor to the range, dryer, HVAC, or EV charger.

That is not the same category.

The fixed-appliance count matters.

The load type matters.

A clean load calculation needs categories, not just a pile of wattage numbers.

Heating and cooling are usually non-coincident

For many dwellings, heating and cooling are not expected to operate at full load at the same time.

So the calculation uses the larger of the two:

HVAC demand = max(air-conditioning load, electric heat load)

Example:

Air-conditioning load = 5,000 VA
Electric heat load = 10,000 VA

Then:

HVAC demand = max(5,000, 10,000)
HVAC demand = 10,000 VA

The mistake is adding both:

5,000 + 10,000 = 15,000 VA

That can oversize the service calculation.

But the opposite mistake is also possible: ignoring electric heat because “the house has AC.”

If electric heat is installed, it must be evaluated.

The calculation must reflect the actual equipment.

Largest motor allowance

Motor starting and motor load behavior can affect service calculations.

Under the standard method, the largest motor receives an additional allowance:

Largest motor adder = 25% × largest motor VA

If the largest motor is:

Largest motor = 1,800 VA

Then:

Motor adder = 0.25 × 1,800
Motor adder = 450 VA

This is not usually the biggest number in a dwelling service calculation, but it is still part of the method.

Small omissions add up.

EV charger load can change the answer

EV charging is where many existing residential services get stressed.

An EV charger is often treated as a continuous load:

EVSE demand = EV charger nameplate VA × 1.25

If the charger is:

EV charger = 9,600 VA

Then:

EVSE demand = 9,600 × 1.25
EVSE demand = 12,000 VA

At 240 V, that is:

12,000 / 240 = 50 A

So a 9.6 kW charger can add 50 A to the service calculation.

This is why a house that looked comfortable before EV charging may suddenly land near the next service size.

The charger nameplate is not the final load in the calculation.

The 125% factor can matter.

Worked example: 2,000 ft² all-electric house

Suppose a dwelling has:

Floor area = 2,000 ft²
Small-appliance circuits = 2
Laundry circuits = 1
Range = 12 kW
Dryer = 5 kW
Fixed appliances = 4,500 VA
Air-conditioning = 5,000 VA
Electric heat = 10,000 VA
Service voltage = 240 V

Start with general load:

Lighting VA = 2,000 × 3
Lighting VA = 6,000 VA

Add small-appliance and laundry circuits:

General VA = 6,000 + 3,000 + 1,500
General VA = 10,500 VA

Apply standard-method lighting demand:

First 3,000 VA @ 100% = 3,000 VA
Remainder = 10,500 − 3,000 = 7,500 VA
Remainder @ 35% = 7,500 × 0.35 = 2,625 VA

So:

General demand = 3,000 + 2,625
General demand = 5,625 VA

Range demand:

12 kW range → 8,000 VA

Dryer demand:

Dryer demand = max(5,000 VA, nameplate)
Dryer demand = 5,000 VA

Fixed appliances:

Fixed appliances = 4,500 VA

HVAC demand:

HVAC demand = max(5,000, 10,000)
HVAC demand = 10,000 VA

Total calculated load:

Total VA = 5,625 + 8,000 + 5,000 + 4,500 + 10,000
Total VA = 33,125 VA

Convert to service current:

Service Current = 33,125 / 240
Service Current ≈ 138 A

Recommended service size:

150 A

That result is not based only on the 2,000 ft² floor area.

It is based on the actual load categories and demand rules.

What happens when an EV charger is added?

Now add:

EV charger nameplate = 9,600 VA

Apply the 125% factor:

EVSE demand = 9,600 × 1.25
EVSE demand = 12,000 VA

New total load:

New Total VA = 33,125 + 12,000
New Total VA = 45,125 VA

New service current:

Service Current = 45,125 / 240
Service Current ≈ 188 A

Recommended service size:

200 A

That is a major change.

The same house moved from a 150 A result to a 200 A result because of one EV charger.

This is the kind of thing that gets missed when someone says:

The house is only 2,000 square feet.

Square footage alone does not describe the service load.

Optional method can produce a lower result

The optional method groups many general loads together and applies a different demand structure:

General demand = first 10,000 VA @ 100% + remainder @ 40%

Then HVAC is handled separately.

For the same general group:

General total = 32,000 VA

The optional-method demand is:

First 10,000 VA = 10,000 VA
Remainder = 32,000 − 10,000
Remainder = 22,000 VA
Remainder @ 40% = 22,000 × 0.40
Remainder @ 40% = 8,800 VA

So:

General demand = 10,000 + 8,800
General demand = 18,800 VA

If the HVAC demand comes out as:

HVAC demand = 6,500 VA

Then:

Total VA = 18,800 + 6,500
Total VA = 25,300 VA

Service current:

Service Current = 25,300 / 240
Service Current ≈ 105 A

Recommended service size:

110 A

The same house can produce different calculated loads under the standard and optional methods.

That does not mean one calculation is “fake.”

It means the method matters.

But the optional method is not a casual shortcut. Eligibility must be checked before using it as the sizing basis.

The 100 A minimum trap

Another common mistake is screening old services against the raw calculated amperes only.

For a one-family dwelling, the sizing basis cannot drop below the minimum service requirement.

So the sizing basis is:

Sizing basis = max(calculated amps, 100 A)

Example:

Calculated load = 19,200 VA
Service voltage = 240 V

Calculated amps:

Calculated amps = 19,200 / 240
Calculated amps = 80 A

Existing service:

Existing service = 90 A

If you compare only against the calculated load:

90 A > 80 A

It looks adequate.

But the sizing basis is:

Sizing basis = max(80, 100)
Sizing basis = 100 A

Now compare:

90 A < 100 A

So the service is undersized against the minimum sizing basis.

The mistake is saying:

The calculated load is only 80 A, so a 90 A service is fine.

The correct interpretation is:

The load calculation is 80 A, but the dwelling service minimum governs at 100 A.

That distinction matters during old-service reviews.

Do not use 120 V for total service current

A typical one-family dwelling service is 120/240 V single-phase.

The total calculated VA is divided by 240 V, not 120 V.

If someone uses 120 V by mistake, the calculated service current doubles.

Example:

Total load = 33,125 VA

Correct calculation:

Service Current = 33,125 / 240
Service Current ≈ 138 A

Wrong calculation:

Service Current = 33,125 / 120
Service Current ≈ 276 A

That mistake could turn a 150 A result into something that looks like it needs a 300 A service.

The arithmetic is simple.

The voltage basis matters.

The calculation does not size everything

A dwelling load calculator gives the service load and service-size screening.

It does not complete the entire electrical design.

It does not automatically size:

Service-entrance conductors
Main breaker
Neutral conductor
Grounding electrode conductor
Panelboard layout
Feeder taps
Voltage drop
Short-circuit rating
Load-management controls
Local amendment requirements

Those are separate checks.

This is important because people often treat one calculator result as a complete permit package.

It is not.

A service load result is a major input.

It is not the whole design.

Practical design takeaway

A good residential load calculation should answer:

What method was used?
What NEC edition or reference basis was assumed?
What floor area was included?
Were small-appliance and laundry circuits included?
Was the range treated by demand rules?
Was the dryer floor applied?
Were fixed appliances counted correctly?
Was only the larger of heating and cooling included?
Was the largest motor adder included?
Was the EV charger counted at 125%?
Was the result divided by 240 V, not 120 V?
Did the 100 A minimum govern?
What standard service size is recommended?

That workflow prevents the biggest mistakes.

The final service size should not come from a guess, a square-foot rule, or a nameplate sum.

It should come from a structured load calculation.

Final thought

Residential electrical load sizing is not just:

House size × watts per square foot

And it is not just:

Add every appliance nameplate at 100%

The real calculation is category-based.

Some loads have demand factors.

Some loads have floors.

Some loads are non-coincident.

Some loads, like EV chargers, can push the service to the next standard size.

And sometimes the calculated load is below 100 A, but the minimum service requirement still governs.

That is why the most important part of a dwelling load calculation is not only the final amp value.

It is the breakdown.

The breakdown shows what was counted, what was demand-adjusted, which method was used, and why the service size changed.

For quick residential service load checks using the standard and optional methods, including general loads, appliances, HVAC, EV charging, service current, and service adequacy screening, use the Electrical Load Calculator on CalcEngineer.

Harmonic Distortion: The THD Number That Can Hide a Power Quality Problem

Evgenii Konkin — Fri, 24 Jul 2026 05:11:51 +0000

Harmonic distortion is one of those power quality numbers that looks simple until someone uses it as a diagnosis.

A power analyzer gives a THD percentage.

The number looks clean.

Maybe it says:

Voltage THD = 4.8%

or:

Current THD = 13%

Then the mistake begins.

Someone treats that one number as the whole power quality story.

But THD is not the whole story.

It is a ratio. It tells you how much harmonic RMS content exists compared with the fundamental RMS component. It does not tell you every harmonic order, resonance risk, neutral loading, transformer heating, capacitor bank stress, or whether the site complies with every applicable limit.

The formula is useful.

The interpretation needs care.

The basic THD formula

Total Harmonic Distortion compares the RMS value of harmonic components with the RMS value of the fundamental component.

For voltage THD:

THD (%) = [sqrt(H2² + H3² + H4² + ... + H13²) / V1] × 100

For current THD:

THD (%) = [sqrt(I2² + I3² + I4² + ... + I13²) / I1] × 100

Where:

V1 or I1 = fundamental RMS value
H2...H13 = harmonic RMS values above the fundamental
THD = total harmonic distortion, percent

The same RMS structure applies to voltage and current.

But the values must not be mixed.

For voltage THD, use volts RMS for the fundamental and all harmonic components.

For current THD, use amps RMS for the fundamental and all harmonic components.

Do not mix volts and amps.

Do not mix peak values and RMS values.

Do not enter harmonic percentages when the calculator expects RMS magnitudes.

That sounds obvious, but it is one of the most common ways to get a wrong THD result.

THD is an RMS calculation, not an arithmetic sum

A common mistake is adding the harmonic values directly.

That is not how THD is calculated.

Harmonic components are combined as root-sum-square:

Harmonic_RMS = sqrt(H2² + H3² + H4² + ... + H13²)

Then that combined harmonic RMS value is compared with the fundamental.

Example:

Fundamental voltage V1 = 230 V RMS
3rd harmonic H3 = 6 V RMS
5th harmonic H5 = 9 V RMS
7th harmonic H7 = 4 V RMS

Wrong approach:

6 + 9 + 4 = 19 V
THD = 19 / 230 × 100
THD = 8.26%

Correct RMS approach:

Harmonic_RMS = sqrt(6² + 9² + 4²)
Harmonic_RMS = sqrt(36 + 81 + 16)
Harmonic_RMS = sqrt(133)
Harmonic_RMS ≈ 11.53 V

Now calculate THD:

THD = 11.53 / 230 × 100
THD ≈ 5.01%

The wrong arithmetic-sum method gave 8.26%.

The correct RMS method gives about 5.01%.

That is a big difference.

The harmonic values were the same.

The calculation method changed the conclusion.

Worked example: current THD from a nonlinear load

Suppose a power quality check on a panel with VFDs and switching power supplies shows:

Fundamental current I1 = 120 A RMS
3rd harmonic I3 = 8 A RMS
5th harmonic I5 = 12 A RMS
7th harmonic I7 = 5 A RMS

Use the current THD formula:

THD (%) = [sqrt(I3² + I5² + I7²) / I1] × 100

Square the harmonic currents:

I3² = 8² = 64
I5² = 12² = 144
I7² = 5² = 25

Add them:

64 + 144 + 25 = 233

Take the square root:

sqrt(233) ≈ 15.26 A

Divide by the fundamental current:

THD = 15.26 / 120 × 100
THD ≈ 12.72%

So the current THD is about:

Current THD ≈ 12.7%

That is not a clean sinusoidal current waveform.

It does not automatically prove equipment failure, but it is high enough to justify a closer review of nonlinear loads, transformer loading, neutral currents, cable heating, harmonic filters, and possible resonance conditions.

Voltage THD and current THD are not the same problem

Voltage THD and current THD both use the same mathematical structure.

But they do not mean the same thing.

Voltage THD describes distortion in the voltage waveform.

Current THD describes distortion in the load current waveform.

A site can have high current THD but acceptable voltage THD if the upstream system is stiff enough.

For example:

Current THD = high
Voltage THD = moderate or low

That may mean the nonlinear loads are drawing distorted current, but the source impedance is low enough that the voltage waveform is not heavily distorted.

On the other hand, if current harmonics flow through system impedance, they can create voltage distortion:

Harmonic current × system impedance = harmonic voltage distortion

That distorted voltage can then affect other equipment connected to the same system.

So the mistake is saying:

Current THD is high, therefore voltage quality is definitely bad.

Or the opposite:

Voltage THD is low, therefore harmonics are not a problem.

Both can be wrong.

You need to understand which waveform was measured and where.

The common mistake: confusing THD with TDD

THD and TDD are not the same.

THD compares harmonic RMS content with the fundamental RMS component:

THD = harmonic RMS content / fundamental RMS component

TDD compares current harmonic content with maximum demand load current:

TDD = harmonic current content / maximum demand load current

That difference matters in electrical power systems.

Current THD can look high at light load because the fundamental current is small.

Example:

Harmonic current RMS = 10 A
Fundamental current = 40 A

Then:

Current THD = 10 / 40 × 100
Current THD = 25%

Now suppose the same harmonic current exists when the fundamental current is higher:

Harmonic current RMS = 10 A
Fundamental current = 200 A

Then:

Current THD = 10 / 200 × 100
Current THD = 5%

The harmonic current stayed the same.

The THD percentage changed because the fundamental current changed.

That is one reason current distortion compliance work often needs more than a simple current THD number.

THD is useful.

But for standards review, utility requirements, and point-of-common-coupling studies, TDD and individual harmonic limits may be required.

A single THD number can hide the dominant harmonic

Another mistake is looking only at total THD and ignoring which harmonic order is causing it.

For example, two systems may both show:

THD = 8%

But the harmonic spectrum may be very different.

System A:

Mostly 5th harmonic

System B:

Mostly 3rd harmonic

Those are not the same engineering problem.

A strong 5th harmonic may be associated with six-pulse rectifiers, VFDs, and certain power electronic loads.

A strong 3rd harmonic is a triplen harmonic and can be especially important in three-phase four-wire systems because triplen harmonics can add in the neutral conductor instead of cancelling like balanced fundamental currents.

So the total THD value is useful, but the spectrum matters.

A total number tells you distortion exists.

The individual harmonic orders help explain what kind of distortion you have.

Why harmonics matter

Harmonics are not just waveform aesthetics.

They can create real system effects:

Extra transformer heating
Extra conductor heating
Neutral conductor loading
Motor heating and torque pulsation
Capacitor bank stress
Nuisance trips
Generator voltage distortion
Poor power factor behavior
Control and sensor interference
Resonance risk with power factor correction capacitors

A waveform can deliver power and still be distorted.

A panel can operate and still run hotter than expected.

A transformer can be within kVA rating and still be stressed by harmonic heating.

That is why THD is often used as an early warning indicator.

It does not complete the diagnosis, but it tells you whether the waveform is close to sinusoidal or noticeably distorted.

Example: why low voltage THD may not mean “no harmonic issue”

Suppose a facility has several VFDs.

Measured values:

Voltage THD = 3.5%
Current THD = 38%

Someone may say:

Voltage THD is only 3.5%, so harmonics are fine.

That may be too optimistic.

The voltage waveform may still be acceptable because the source is strong, but the current waveform is heavily distorted. That distorted current may still contribute to:

Transformer heating
Cable heating
Generator loading issues
Harmonic filter requirements
Neutral conductor concerns
Distorted voltage under weaker source conditions

The correct conclusion is more careful:

Voltage distortion is currently moderate, but current distortion is high and should be reviewed at the load and distribution level.

That is a better engineering interpretation.

Example: why high current THD at light load may be misleading

Now consider a UPS or VFD at very light load.

Measured values:

Fundamental current = 10 A
Combined harmonic RMS current = 5 A

Then:

Current THD = 5 / 10 × 100
Current THD = 50%

That looks terrible.

But the absolute harmonic current is only 5 A.

At higher load, the same equipment may show:

Fundamental current = 100 A
Combined harmonic RMS current = 10 A

Then:

Current THD = 10 / 100 × 100
Current THD = 10%

The THD percentage dropped a lot.

But the harmonic current doubled from 5 A to 10 A.

So current THD must be interpreted with load level.

High THD at light load can look dramatic because the denominator is small.

That does not mean it should be ignored, but it should not be interpreted without load context.

RMS values matter

The THD formula requires RMS values.

If someone enters peak values for harmonics but RMS for the fundamental, the result is wrong.

For a sine component:

Vpeak = Vrms × sqrt(2)

If a harmonic component is accidentally entered as peak instead of RMS, it will be about 1.414 times too large.

That error propagates into the root-sum-square calculation and inflates the THD result.

The safest workflow is:

Confirm the analyzer reports RMS harmonic magnitudes.
Use the same unit for all components.
Do not mix voltage and current.
Do not mix RMS and peak.
Do not enter percentages as RMS values.

The formula is only as good as the input definitions.

THD does not prove compliance by itself

THD is a screening metric.

It is not a full compliance report.

A final power quality review may require:

Measured harmonic spectrum
Individual harmonic order limits
Point of common coupling definition
Short-circuit ratio
Maximum demand load current
TDD calculation
Voltage distortion limits
Current distortion limits
Measurement duration
Operating scenarios
Utility interconnection requirements

This is especially important for large facilities, industrial plants, data centers, solar inverters, generator systems, and sites with major nonlinear loads.

A calculator can give a consistent first-pass THD estimate.

It cannot replace a full power quality study when standards compliance or utility approval is involved.

Practical design takeaway

Use THD as a power quality screening number.

It helps answer:

How distorted is the waveform compared with the fundamental?
Which harmonic RMS values dominate the result?
Is the waveform close to sinusoidal or heavily distorted?
Is the distortion voltage THD or current THD?
Is a detailed harmonic review needed?

But do not use THD as the only conclusion.

It does not show the full harmonic spectrum by itself.

It does not calculate TDD.

It does not check IEEE 519 compliance by itself.

It does not model resonance.

It does not calculate transformer derating.

It does not prove that neutral current, capacitor stress, or motor heating is acceptable.

It is a first-pass indicator.

A useful one.

But still only one part of the power quality picture.

Final thought

Total Harmonic Distortion is a compact number:

THD (%) = [sqrt(sum of harmonic RMS values squared) / fundamental RMS] × 100

That compact number can be very useful.

It can show when a waveform is close to sinusoidal.

It can warn that nonlinear loads are producing significant distortion.

It can help compare voltage and current quality between systems.

But it can also mislead if the engineer forgets the context.

Current THD changes with load level.

Voltage THD and current THD describe different things.

A single THD value can hide the dominant harmonic order.

And THD is not the same as TDD or full standards compliance.

For quick THD checks from fundamental and harmonic RMS values, use the Harmonic Distortion Calculator on CalcEngineer.

Signal Propagation Delay: The Small Cable Delay That Can Break a Timing Budget

Evgenii Konkin — Thu, 16 Jul 2026 16:30:24 +0000

Signal propagation delay is easy to underestimate.

A cable looks passive.
A fiber run looks like a simple connection.
A PCB trace looks short.

But a signal still needs time to travel through that physical path. It does not arrive instantly.

The basic formula is simple:

Delay = Length / Propagation Velocity

That formula gives the one-way geometric delay.

But the engineering mistake is treating that number as either “too small to matter” or as the full end-to-end system latency. Both assumptions can be wrong.

In fast digital systems, protection relays, synchronization links, trigger circuits, and long communication paths, propagation delay can become a real timing-budget item.

The basic formula

The one-way propagation delay is:

Delay_s = Length_m / Velocity_mps

Where:

Delay_s = one-way propagation delay, seconds
Length_m = signal travel distance, meters
Velocity_mps = propagation velocity, meters per second

If the velocity is entered as a fraction of the speed of light:

Velocity_mps = Velocity_factor × 299,792,458

For example:

Velocity_factor = 0.66

Velocity_mps = 0.66 × 299,792,458
Velocity_mps ≈ 197,863,022 m/s

Then the delay can be converted into more readable units:

Delay_ns = Delay_s × 1,000,000,000
Delay_µs = Delay_s × 1,000,000
Delay_ms = Delay_s × 1,000

That is the whole calculation.

But the interpretation is where the problems start.

One-way delay is not round-trip latency

The calculator gives one-way propagation delay.

That means the signal travels from point A to point B once.

If the system needs a response back from point B to point A, the propagation portion of round-trip delay is roughly:

Round-trip propagation delay ≈ 2 × one-way delay

That still does not include:

Device delay
Connector delay
Repeater delay
Switching delay
Serialization delay
Protocol overhead
Software processing time
Queueing delay
Measurement instrument delay

So propagation delay is one term in the timing budget.

It is not the entire timing budget.

That distinction matters a lot.

A propagation delay estimate can tell you the minimum physical delay caused by path length and signal velocity. It cannot tell you the total system response time.

Worked example: 100 m cable at 0.66c

Suppose an engineer is checking a 100 m copper cable run.

Use:

Path Length = 100 m
Velocity Factor = 0.66c

First calculate signal velocity:

Velocity_mps = 0.66 × 299,792,458
Velocity_mps ≈ 197,863,022 m/s

Now calculate one-way delay:

Delay_s = 100 / 197,863,022
Delay_s ≈ 0.000000505 s

Convert to nanoseconds and microseconds:

Delay_ns ≈ 505 ns
Delay_µs ≈ 0.505 µs
Delay_ms ≈ 0.000505 ms

So the cable adds about:

One-way delay ≈ 505 ns

That sounds tiny.

For a human interface, it is tiny.

For some industrial controls, it may still be tiny.

But for high-speed timing, precision triggering, clock distribution, or protection coordination, 505 ns may be large enough to matter.

The same number can be irrelevant in one system and critical in another.

That is why propagation delay must always be compared against the actual timing budget.

Length matters linearly

Propagation delay is directly proportional to path length.

If the same cable velocity is used:

Delay ∝ Length

So if 100 m gives 505 ns, then:

200 m gives about 1.01 µs
500 m gives about 2.53 µs
1000 m gives about 5.05 µs

There is no hidden magic here.

Double the distance, double the delay.

That is why long fiber and cable paths can become important even when each meter feels harmless.

In many systems, a few meters do not matter.

In some systems, a few meters absolutely matter.

The circuit or protocol decides which case you are in.

Velocity factor matters too

Delay is inversely proportional to signal velocity:

Delay ∝ 1 / Velocity

If the propagation velocity is lower, delay is higher.

A common mistake is assuming the signal travels at the full speed of light.

It does not in real cable or fiber.

A velocity factor of 0.66 means the signal travels at 66% of the speed of light.

For 100 m:

At 1.00c:

Velocity = 299,792,458 m/s
Delay = 100 / 299,792,458
Delay ≈ 333 ns

At 0.66c:

Velocity ≈ 197,863,022 m/s
Delay ≈ 505 ns

The length did not change.

Only the propagation velocity assumption changed.

The delay increased from about 333 ns to about 505 ns.

That is about 52% higher.

So using the wrong velocity factor can make the timing estimate look much better than the real system.

The common engineering mistake: treating cable delay as total latency

One common mistake is calculating propagation delay and then saying:

The system latency is 505 ns.

That is usually wrong.

The correct statement is:

The one-way geometric propagation delay through this cable is about 505 ns.

The full system may include many additional delays.

For example:

Cable propagation delay = 505 ns
Input circuit delay = 80 ns
Isolation device delay = 120 ns
FPGA input synchronization = 20 ns
Processing delay = 300 ns
Output driver delay = 60 ns
Second cable path = 505 ns

Total delay:

Total delay = 505 + 80 + 120 + 20 + 300 + 60 + 505
Total delay = 1,590 ns
Total delay = 1.59 µs

In this example, the cable is important, but it is not the only delay.

If the engineer only reports the 505 ns propagation delay, the timing budget is incomplete.

If the engineer ignores the cable entirely, the timing budget is also incomplete.

Both errors are common.

Short cables can still matter

Another mistake is assuming short distance means zero delay.

Take a 10 m cable at 0.66c:

Velocity_mps ≈ 197,863,022 m/s

Delay_s = 10 / 197,863,022
Delay_s ≈ 50.5 ns

So:

One-way delay ≈ 50 ns

For slow control logic, that may be irrelevant.

But in a 10 Gbit/s system, one bit period is:

Bit period = 1 / 10,000,000,000
Bit period = 0.1 ns

A 50 ns propagation delay is not “small” compared with that bit period.

That does not automatically mean the link fails. High-speed systems are designed around serialization, equalization, clocking, encoding, and protocol behavior.

But it does mean that the physical path delay is real and must be handled in the system design.

The same 10 m cable can be invisible to a relay input and very relevant to a high-speed timing path.

Long paths become microseconds or milliseconds

For long links, propagation delay can become easier to visualize.

Suppose a fiber path is:

Path Length = 50 km
Velocity Factor = 0.67c

Convert length:

Length_m = 50 × 1000
Length_m = 50,000 m

Velocity:

Velocity_mps = 0.67 × 299,792,458
Velocity_mps ≈ 200,860,947 m/s

One-way delay:

Delay_s = 50,000 / 200,860,947
Delay_s ≈ 0.000249 s

Convert:

Delay_ms ≈ 0.249 ms
Delay_µs ≈ 249 µs

Round-trip propagation delay would be approximately:

Round-trip propagation delay ≈ 2 × 0.249 ms
Round-trip propagation delay ≈ 0.498 ms

That is only the physical travel time.

Real network latency will be higher once transceivers, switches, routing, buffering, and protocol overhead are included.

This is exactly why propagation delay should be separated from full end-to-end latency.

The timing-budget problem

A useful timing budget should separate delay terms.

For example:

Propagation delay
Transceiver delay
Connector or interface delay
Logic delay
Switch or relay delay
Serialization delay
Protocol delay
Software delay
Safety margin

If a system has a maximum allowable timing error of 2 µs, and the cable alone contributes 0.5 µs, then cable delay is already 25% of the budget.

That may be acceptable.

But it is not negligible.

If several cable paths exist, or if one path is longer than another, skew can appear between channels.

For multi-channel trigger systems, protection relay links, clock distribution, and measurement setups, the difference between path delays may matter more than the absolute delay.

Example:

Channel A cable length = 20 m
Channel B cable length = 80 m
Velocity factor = 0.66c

Length difference:

ΔLength = 80 − 20
ΔLength = 60 m

Delay skew:

ΔDelay = 60 / 197,863,022
ΔDelay ≈ 303 ns

So even if both channels “work,” they do not arrive at the same time.

That skew may need compensation.

Unit mistakes can be severe

Propagation delay calculations are sensitive to length units.

The calculator supports common distance units, but the engineer must select the correct one.

A path length of:

100 ft

is not the same as:

100 m

Convert 100 ft:

100 ft × 0.3048 = 30.48 m

At 0.66c:

Delay = 30.48 / 197,863,022
Delay ≈ 154 ns

For 100 m:

Delay ≈ 505 ns

That is more than 3× different.

The same issue applies to miles and kilometers.

A wrong unit selection can make a link look much faster or slower than it really is.

Propagation delay is not signal integrity

A cable can have the right delay and still have poor signal quality.

Propagation delay tells you when the signal arrives.

It does not tell you whether the signal arrives cleanly.

It does not check:

Attenuation
Reflections
Impedance mismatch
Rise-time degradation
Crosstalk
Jitter
Dispersion
Return loss
Connector quality
Shielding
Ground reference problems
Receiver threshold margin

This is an important distinction.

Timing and signal integrity are related, but they are not the same calculation.

A propagation delay estimate may say the signal should arrive in 505 ns.

It does not prove the receiver sees a clean digital edge at 505 ns.

For high-speed or precision systems, propagation delay is only one part of the design review.

Practical design takeaway

Use propagation delay as a timing-budget term.

It helps answer:

How much delay does this cable, trace, or fiber path add?
Is the delay in ns, µs, or ms?
How much path mismatch exists between channels?
Is one-way delay being confused with round-trip latency?
Is the assumed velocity factor realistic?
Is the path delay small compared with the system timing budget?

But do not use it as a full system latency calculation.

It does not include electronics delay.
It does not include switch or repeater delay.
It does not include protocol overhead.
It does not prove signal integrity.
It does not replace measurement or detailed timing analysis.

It gives you the geometric delay term — the part set by distance and propagation speed.

That is often the right first number to calculate before building the full timing budget.

Final thought

Signal propagation delay is simple:

Delay = Length / Velocity

But the simplicity is the trap.

A 100 m cable at 0.66c adds about 505 ns of one-way delay.

That may be irrelevant for a slow control input, but meaningful for synchronization, protection, trigger, or high-speed timing work.

The important habit is not to call the delay “small” or “large” in isolation.

Compare it with the timing budget.

Check whether you need one-way or round-trip delay.

Use a realistic velocity factor.

And remember that propagation delay is not total latency and not signal integrity.

For quick one-way delay checks from path length and propagation velocity, use the Signal Propagation Delay Calculator on CalcEngineer.