The trial for ignition, usually abbreviated TFI, is the fixed window of time during a burner startup in which the burner management system attempts to establish a flame and waits for proof that one has been made. During this window the control system energizes the ignition source and opens the appropriate fuel valve, then watches its flame detector for a confirming signal. If a flame is proven before the window expires, the sequence continues; if it is not, the system shuts off fuel and locks out. The whole point of bounding this period is to limit how long fuel can be admitted while no flame has yet been confirmed.
Trial for ignition (TFI) in one line: A trial for ignition is the fixed, timed period during burner light-off in which the burner management system energizes the ignition source and fuel valve and waits for a proven flame. If no flame signal appears before the trial time expires, the flame safeguard shuts off fuel and locks out to prevent unburned fuel from accumulating.
The trial for ignition begins after the startup prerequisites have been satisfied, such as a completed air purge and correct valve and damper positions. At the start of the trial, the burner management system energizes the ignition transformer to create a spark and opens the pilot or main fuel valve as appropriate for the design. From that instant, fuel is being admitted to the combustion chamber and the system is actively trying to light it.
Throughout the trial the flame detector is watched for a valid flame signal. If a flame is proven within the allotted time, the sequence advances: on a pilot trial the system then proceeds toward lighting the main burner from the established pilot, and on a direct main light-off it moves to normal firing. The successful establishment of flame within the window is the condition that allows the startup to continue safely.
The trial for ignition is often referred to as a flame establishing period because its purpose is to give the burner a defined chance to establish a stable flame. It is deliberately short, because every second of the trial is a second in which fuel is entering the chamber on the assumption that ignition will occur. Keeping the window fixed and bounded is what prevents an indefinite attempt to light in the presence of accumulating fuel.
If the trial for ignition ends without a proven flame, the flame safeguard trips: it de-energizes the ignition, closes the fuel safety shutoff valves, and drives the system into a lockout that requires a deliberate reset before another attempt. This failure-to-ignite response is one of the core safety functions of a burner management system, ensuring that fuel is not left flowing into an unlit chamber.
The length of the trial is bounded because admitting fuel without ignition allows a combustible fuel-air mixture to build in the furnace. The longer fuel flows before a flame is confirmed, the more fuel accumulates, and if it later ignites all at once the result can be an explosion. Codes and standards therefore constrain how long the trial may last, tying the limit to the amount of ignition energy and fuel that can safely be accumulated for the burner size involved.
This is why the trial for ignition is a fixed timer rather than an open-ended wait. A patient controller that kept trying to light indefinitely would defeat the purpose, since the hazard grows with time. By enforcing a short, definite window and then tripping to safety if flame is not proven, the system keeps the quantity of unburned fuel within limits that will not produce a damaging explosion if ignition eventually occurs or the chamber is purged.
Failed ignition attempts, or nuisance lockouts, are a common operational headache, and diagnosing them requires knowing exactly what happened during each trial. When burner management events are reported to a SCADA system, the historian time-stamps each light-off attempt, including when the ignition energized, when the fuel valve opened, whether and when a flame signal appeared, and whether the trial ended in a proven flame or a lockout.
That recorded sequence is invaluable for troubleshooting. An operator or engineer reviewing the history can see whether flame was being detected late in the trial but not quite in time, whether the flame signal was absent entirely, or whether a marginal signal flickered near the detection threshold. Patterns across many attempts, such as lockouts clustering at certain conditions, point toward root causes like a fouled igniter, a weak pilot, or a marginal flame detector.
Bringing this into a cloud monitoring platform extends the benefit across time and across sites. Rather than relying on an operator's memory of a lockout, the time-stamped record persists, can be trended, and can be compared between similar burners. This turns intermittent, hard-to-reproduce ignition problems into something an integrity or reliability team can analyze from the logged data, targeting maintenance at the burners and components that are actually causing repeated failed trials.
A pilot trial for ignition is the window in which the system tries to light the small pilot or igniter that will in turn light the main burner. A main trial for ignition is the window in which the main burner fuel is admitted and expected to light, either from an established pilot or directly. Both are timed windows that end in a proven flame or a trip, but they apply to different stages of the light-off.
During the trial, fuel is being admitted to the chamber before any flame is confirmed, so a combustible mixture accumulates for as long as the trial lasts. Keeping the window short limits how much unburned fuel can build up, so that if ignition finally occurs the resulting combustion is not violent enough to cause an explosion. That is why standards bound the trial time rather than allowing an open-ended attempt.
The flame safeguard trips: it de-energizes the ignition, closes the fuel safety shutoff valves, and puts the system into a lockout. The lockout must be deliberately reset before another light-off can be attempted, which forces attention to why ignition failed. This response prevents fuel from continuing to flow into a chamber that has not established a flame.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.