Burst-Fired Thick Film Heaters: Minimum Energy Packet and Temperature Ripple

System boundary

A resistive thick-film heater, its installed load, mains supply, whole-cycle burst power stage, temperature sensor and controller. The analysis assumes an approved electrical installation and does not prescribe mains wiring or protective ratings.

Integration interfaces

Integration risks

Find the smallest energy command the hardware can deliver

Whole-cycle burst firing applies complete supply cycles separated by non-firing intervals. A single-cycle mode can use one complete cycle as its minimum firing event; other configurations impose several cycles. Obtain the actual mode and minimum-on setting for the selected power controller rather than inferring them from its generic product family.

A fixed window, a variable off interval and a distributed-cycle scheduler can produce different packet patterns at the same requested percentage. State which behavior the heater will receive. Half-cycle or phase-angle alternatives have their own load compatibility and electrical requirements and should not be introduced as an undocumented software workaround.

Convert minimum firing time into energy

For an ideal resistive load whose resistance remains approximately constant over the packet, on-state average power is the cycle-average heating power while firing. If the smallest packet contains n complete cycles at mains frequency f, its duration is n/f and its energy is approximately P_on n/f.

For illustration, a 60 W on-state heater at 50 Hz receives 1.2 J in one complete cycle. A five-cycle minimum supplies 6 J. These are hypothetical electrical conditions, not approved ratings for a particular thick-film part. Use measured voltage and current integration when resistance, supply distortion or the switching pattern makes the constant-power assumption unsuitable.

Use the heat capacity that participates during the packet

Dividing packet energy by the heat capacity of the entire machine can greatly understate the initial heater excursion. On a short timescale, only the heater and the thermally coupled portion of its surroundings may participate. The distant load responds through a finite thermal path.

With an illustrative effective capacity of 2 J/K and negligible loss during the packet, 1.2 J corresponds to a 0.6 K average rise of that effective thermal mass; 6 J corresponds to 3 K. This lumped estimate is a screening calculation, not a local hot-spot guarantee. A printed region can have spatial temperature differences that require measurement or a more resolved thermal model.

Distinguish average-power resolution from packet size

At a demand of 0.6 W, repeated 1.2 J packets would need an average spacing of 2 s. A scheduler can increase the interval to reduce average power further, but each isolated packet still carries 1.2 J. Increasing the numerical resolution of a command does not reduce this physical increment.

In a fixed 2 s accounting window, one 1.2 J packet represents 0.6 W of window-average power. A demand below that value requires either alternating windows or a different scheduling rule. Review rounding, accumulated demand and any minimum-output clamp. A controller that rounds every low request to zero behaves differently from one that retains fractional energy demand for later delivery.

Check whether the scheduler groups energy unnecessarily

Several packets delivered consecutively can cause a larger excursion than the same packets spread over the accounting interval. The total joules are equal, but the intervening heat transfer differs. Controller updates, communication cycles or minimum-on constraints may group the output even when the supervisory command looks smooth.

Record the sequence of actual firing events at the lowest useful load. Include a small setpoint change and a transition from a higher demand. Determine whether any internal accumulated demand is cleared, preserved or released as a cluster. That behavior is a controller integration property, not a characteristic that can be inferred from heater resistance.

Use packet behavior to choose the corrective action

A stable mean temperature is not sufficient when the process limits instantaneous temperature or local overshoot. Select the action from the observed limitation rather than retuning the regulator for every hardware mismatch.

Measure the packet and the temperature on a common timeline

Use appropriately rated, isolated instrumentation and qualified procedures for mains-connected measurements. Integrate electrical power over complete firing packets and record the temperature channels against the same clock. A slow power display can confirm a mean but may not reveal the minimum event size or its placement.

Choose temperature sensing that resolves the region and timescale of concern without materially changing the heater's thermal mass. Compare the lightest intended load, representative coupling variations and the smallest sustained demand. Document sensor lag and filtering so an apparently quiet trace is not mistaken for proof that no fast excursion exists.

Release a low-load operating envelope, not just one tuned point

Define the approved relationship among heater resistance, supply range, minimum packet setting, load coupling and temperature requirement. A resistance change alters on-state power at a fixed voltage and therefore changes packet energy even if the controller settings are unchanged.

Check entry into regulation, steady light load and recovery from an interruption. Keep independent protective controls appropriate to the equipment; ordinary burst scheduling is not a protective temperature limit. The completed review should identify why the smallest delivered energy event is acceptable, how the controller distributes it, and which changes require that conclusion to be revisited.