Gas Burner Control Redesign Example for OEMs

A field-return pattern can reveal more about a burner control than a bench test ever will. Consider an OEM whose commercial cooking equipment showed intermittent ignition lockouts after installation, despite passing production tests. This gas burner control redesign example shows how an engineering team can address the actual system causes - not merely replace a controller with a newer board.

For gas appliance manufacturers, a redesign is rarely just a matter of changing components. The ignition controller sits at the intersection of line power, valve actuation, spark generation, flame sensing, grounding, wiring harnesses, enclosure conditions, and user behavior. A change that improves one function can introduce cost, emissions, certification, or serviceability issues elsewhere. The best result comes from treating the controller as part of a complete combustion and appliance system.

The Starting Point: An Intermittent Ignition Failure

In this representative case, the original burner control used a conventional spark ignition module with a fixed trial-for-ignition period. When heat was requested, the control energized the gas valve, generated spark pulses at the electrode, and attempted to verify flame through a flame-sensing circuit. If flame was not confirmed within the programmed window, it shut down and entered lockout.

The design performed consistently under controlled factory conditions. In the field, however, service teams reported three related problems: delayed ignition at certain sites, nuisance lockouts after extended operation, and boards returned with no reproducible defect. Replacing the controller often appeared to solve the problem temporarily, but the return data did not support a simple component-failure explanation.

That distinction matters. If an OEM redesigns around an assumed defective board, it may increase the component count and cost while leaving the underlying installation sensitivity unresolved. The engineering question was broader: what conditions were preventing reliable ignition and flame confirmation across the expected operating range?

Gas Burner Control Redesign Example: Finding the Root Causes

The redesign effort began with structured failure analysis rather than schematic changes. Returned units, burner assemblies, electrodes, harnesses, and installation records were reviewed together. The team also reproduced difficult conditions using variations in supply voltage, ground continuity, electrode gap, gas pressure, ambient temperature, and electrical noise.

Several contributors emerged. The flame signal margin was low on some units because the sensing path depended heavily on the quality of chassis grounding. Long wiring runs and inconsistent field bonding added noise to a signal that was already close to the controller threshold. At the same time, electrode placement variation reduced spark consistency. A fixed ignition timing strategy was adequate for most starts but did not provide enough tolerance for cold equipment, marginal gas pressure, or deposits that developed during normal use.

None of these findings meant the original architecture was fundamentally wrong. The issue was that its operating margin was too narrow for the full range of real-world conditions. That is a common redesign trigger for OEMs: a product meets nominal requirements but lacks resilience against normal production and installation variation.

Separate Spark, Flame, and Valve Questions

A productive diagnostic method is to separate the ignition event into three questions. First, does the electrode consistently create spark energy at the burner under load? Second, does the burner light within the allowed trial period? Third, does the flame-sensing circuit recognize a stable flame without reacting to electrical interference?

These questions should not be collapsed into a single “no ignition” failure code during development. A burner may ignite correctly while the control fails to detect flame. Conversely, a strong flame signal cannot compensate for poor spark delivery. Separating the failure paths gives engineering and service teams usable data and prevents unnecessary replacement of healthy subsystems.

Redesigning for Operating Margin, Not Feature Count

The revised control architecture retained the required safety sequence but improved its tolerance and diagnosability. The objective was not to add functions for their own sake. It was to make the ignition system more predictable across production lots, installation environments, and appliance life.

The flame-sensing input was redesigned with improved filtering and a more deliberate threshold strategy. Filtering must be carefully balanced: too little filtering allows electrical noise to create false readings, while too much can delay recognition of a flame or mask a legitimate flame-loss event. The final parameters should be based on measured signal behavior, required response times, and applicable safety requirements rather than a generic circuit value.

The spark output section was also reviewed as an assembly, including transformer performance, high-voltage routing, electrode lead length, and connector selection. High-voltage ignition is especially sensitive to unintended paths. A board may produce acceptable spark in open-air testing but behave differently when installed beside grounded metal, moisture, residue, or a tightly routed harness.

For this example, the controller also introduced controlled retry logic within the permitted safety strategy. Rather than treating every unsuccessful first attempt as an identical event, the sequence could distinguish between a failed ignition attempt and a loss of flame after successful proof. This distinction improved service diagnostics and reduced nuisance lockouts without compromising the required safe shutdown behavior.

Design for Manufacturing Is Part of Reliability

A redesign that works only in the engineering lab is not ready for an OEM production line. Component availability, test access, assembly variation, and programming control must be addressed before release.

The redesigned board reduced dependence on manually adjusted parameters and clarified inspection points for electrode and harness installation. Where practical, connector keying and harness routing were used to prevent incorrect assembly. The production test fixture was updated to verify critical outputs, flame-sensing behavior, valve-drive timing, and fault responses. This is more effective than relying on a basic power-on test that confirms only that the board is energized.

Component selection also required a lifecycle view. A lower-cost substitute may appear attractive, but ignition systems operate near high-voltage circuitry and frequently face heat, vibration, contamination, and switching transients. The right choice depends on electrical ratings, supplier consistency, qualification evidence, and availability over the expected production life. For a high-volume appliance program, avoiding a future redesign caused by an obsolete or unstable component can outweigh a modest unit-cost difference.

Validation Must Reflect the Appliance, Not Just the PCB

The validation plan tested the controller inside the actual burner platform. Board-level testing remains necessary, but it cannot replicate every grounding path, gas behavior, airflow condition, or electromagnetic interaction present in the finished equipment.

The program included repeated cold and hot starts, supply-voltage variation, degraded grounding scenarios, electrode gap tolerance, long harness conditions, and simulated flame-loss events. Engineers evaluated both successful ignition rates and the quality of shutdown behavior. A safe controller must not only light reliably; it must also respond correctly when ignition fails or a proven flame is lost.

Environmental and electrical testing should reflect the product's intended duty cycle. A countertop appliance, a commercial range, and an industrial heating system may share ignition principles while facing very different thermal loads, contamination profiles, and service expectations. There is no universal timing value, flame threshold, or enclosure approach that fits every burner application.

Compliance planning also belongs early in the redesign. Depending on the appliance category and destination market, requirements may affect creepage and clearance, insulation systems, fault behavior, material selection, emissions performance, documentation, and production controls. Addressing these constraints after the hardware is frozen is expensive and can force avoidable layout changes.

What OEM Teams Should Document Before a Redesign

The quality of the redesign brief determines how quickly engineering can move from symptoms to a manufacturable solution. Field-return data is valuable, but it should be paired with appliance-level details: burner configuration, gas type and pressure range, ignition electrode geometry, flame-sensing method, harness length, enclosure construction, expected ambient conditions, duty cycle, and applicable certifications.

It is equally useful to define what must remain unchanged. Mechanical mounting, connectors, firmware interfaces, test equipment, approved suppliers, and target cost can all shape the best technical path. In some cases, a drop-in replacement is the priority. In others, a modest mechanical change creates enough design margin to solve a recurring reliability issue permanently.

A capable engineering partner can turn that information into requirements, prototypes, verification plans, and production-ready controls. Electronica Eltec approaches gas ignition and spark ignition module development as an integrated engineering and manufacturing effort, helping OEMs avoid the handoff gaps that occur when design, validation, and production are treated as separate projects.

The practical lesson is simple: a burner control redesign succeeds when it improves the complete ignition system's margin, traceability, and manufacturability. Start with measured field conditions, validate at the appliance level, and make each design change earn its place through safer, more repeatable performance.