Ignition-Based Protocol for Pellet Grills

Abstract

A pellet grill including a control system that implements, manages, and / or controls various ignition-based protocols and / or processes is disclosed. An example pellet grill includes a cooking chamber, a burn pot, an igniter, and a controller. The igniter extends into the burn pot and is configured to ignite pellet fuel located within the burn pot. The controller is configured to command the igniter to activate during a first duration. The controller is further configured to determine, after expiration of the first duration, whether a temperature of the cooking chamber has reached a threshold temperature. The controller is further configured to, in response to determining that the temperature has not reached the threshold temperature, command the igniter to activate during a second duration.

Description

[0001] Related Applications

[0002] This application claims priority to U.S. Patent Application No. 16 / 926,271, filed on July 10, 2020, and U.S. Provisional Patent Application No. 62 / 990,788, filed on March 17, 2020, both of which are entitled "Ignition-Based Protocol for Pellet Grills." The entire contents of U.S. Patent Application No. 16 / 926,271 and U.S. Provisional Patent Application No. 62 / 990,788 are hereby incorporated herein by reference. Technical Field

[0003] The present disclosure relates generally to barbecue grills and, more particularly, to ignition based protocols and / or processes for pellet barbecue grills. Background Art

[0004] A pellet grill is an electrically controlled cooking device that is configured to cook (e.g., smoke, grill, bake, roast, broil, sear, and / or otherwise heat) a food item that is located within a cooking chamber of the pellet grill (e.g., placed on one or more cooking grates located within the cooking chamber). The controllable electronics of the pellet grill may be powered via AC power (e.g., supplied to the pellet grill via household electricity or wall power) or DC power (e.g., supplied via an onboard or connected battery and / or DC power supply).

[0005] Conventional pellet grills store a large amount of combustible pellet fuel (e.g., wood pellets) in a hopper mounted and / or coupled to the pellet grill. A motor-driven auger in communication with an outlet of the hopper feeds and / or supplies the pellet fuel from the hopper to a burn pot of the pellet grill in a controlled and / or automated manner. The speed, rate, and / or duty cycle of the auger is typically based on a user-selected temperature (e.g., a temperature set point) established for and / or desired by a cooking chamber of the pellet grill. The pellet fuel deposited in the burn pot may be initially ignited by an electronic starter of the pellet grill.

[0006] The combustion and / or burning of the pellet fuel within the burner produces, generates and / or outputs heat, which is then distributed throughout the cooking chamber in a manner that causes food located within the cooking chamber to be gradually cooked. A motor-driven fan is typically implemented to assist in the combustion of the pellet fuel and / or to assist in the distribution and / or circulation of heat (e.g., heat that may be generated by the burning pellet fuel) throughout the cooking chamber. Summary of the invention

[0007] In one aspect, the present invention relates to a pellet grill, the pellet grill comprising: a cooking chamber; a burn pot; an igniter, the igniter extending into the burn pot and configured to ignite pellet fuel located in the burn pot; and a controller, the controller being configured to: command the igniter to be activated during a first duration; after expiration of the first duration, determine whether a temperature of the cooking chamber has reached a threshold temperature; and in response to determining that the temperature has not reached the threshold temperature, command the igniter to be activated during a second duration.

[0008] In another aspect, the present invention relates to a pellet grill, the pellet grill comprising: a cooking chamber; a burner pot; an igniter, the igniter extending into the burner pot and configured to ignite pellet fuel located in the burner pot; and a controller, the controller configured to: detect a temperature pattern of the cooking chamber corresponding to a flameout condition of the burner pot; in response to detecting the temperature pattern, command the igniter to be activated during a first duration; after the first duration expires, determine whether the temperature of the cooking chamber increased during the first duration; and in response to determining that the temperature did not increase during the first duration, command the igniter to be activated during a second duration.

[0009] In another aspect, the present invention relates to a pellet grill, the pellet grill comprising: a cooking chamber; a burn pot; an igniter, the igniter extending into the burn pot and configured to ignite pellet fuel located in the burn pot; and a controller, the controller configured to: determine a startup temperature of the cooking chamber; command the igniter to activate during a first duration associated with a preheating operation of an engine of the pellet grill; after expiration of the first duration, determine a current temperature of the cooking chamber; determine whether a temperature difference between the current temperature and the startup temperature exceeds a threshold temperature difference; in response to determining that the temperature difference exceeds the threshold temperature difference, determine whether the temperature difference has exceeded the threshold temperature difference for a second duration; and in response to determining that the temperature difference has exceeded the threshold temperature difference for the second duration, command the igniter to activate.

[0010] In another aspect, the present invention relates to a pellet grill, the pellet grill comprising: a cooking chamber; a burn pot; an igniter, the igniter extending into the burn pot and configured to ignite pellet fuel located in the burn pot; and a controller, the controller configured to: determine a first temperature of the cooking chamber during a first duration, the first temperature being recorded as a previous temperature; after the first duration expires, determine a second temperature of the cooking chamber, the second temperature being recorded as a current temperature; determine whether the previous temperature is greater than the current temperature; in response to determining that the previous temperature is greater than the current temperature, command a counter of the pellet grill to increase a fault count; determine whether the fault count is greater than or equal to a first threshold fault count; and in response to determining that the fault count is not greater than or equal to the first threshold fault count, enable a re-ignition subroutine, wherein the controller commands the igniter to be activated in conjunction with execution of the re-ignition subroutine. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 is a perspective view of an example pellet grill constructed in accordance with the teachings of the present disclosure.

[0012] Figure 2 yes Figure 1 Exploded view of a pellet grill.

[0013] Figure 3 yes Figure 1 and Figure 2 Front view of a pellet grill.

[0014] Figure 4 is along Figure 3 Section AA cut Figures 1 to 3 A cross-sectional view of a pellet grill.

[0015] Figure 5 is a first perspective view of an example engine of a pellet grill.

[0016] Figure 6 yes Figure 5 A second perspective view of the engine.

[0017] Fig. 7A and Figure 7B yes Figure 5 and Figure 6 Exploded view of the engine.

[0018] Figure 8 yes Figure 5 To Figure 7 a side view of the engine.

[0019] Fig. 9 yes Figures 5 to 8 Front view of the engine.

[0020] Fig.10 is along Fig. 9 Section BB cut Figures 5 to 9 A cutaway view of an engine.

[0021] Fig.11 It is a combination Figures 1 to 4 Block diagram of an example control system implemented for a pellet grill.

[0022] Fig.12 It means that it is used for Fig.11 A flow chart of an example method of implementing a startup protocol and / or process for a control system.

[0023] Fig.13 It means that it is used for Fig.11 A flow chart of an example method of implementing a flameout detection protocol and / or process for a control system.

[0024] Fig.14A and Fig. 14B It means that it is used for Fig.11 A flow chart of an example method for implementing another ignition-based protocol and / or process in a control system.

[0025] FIG. 15A to FIG. 15C It means that it is used for Fig.11 A flow chart of an example method for implementing another ignition-based protocol and / or process in a control system.

[0026] Fig.16 is used through Fig.11 A flow chart of an example method of implementing a re-ignition subroutine in a control system of a computer program product.

[0027] Certain examples are shown in the above-mentioned drawings and described in detail below. In describing these examples, similar or identical reference numerals are used to identify the same or similar elements. These figures are not necessarily drawn to scale, and certain features and certain views of the drawings may be exaggerated in scale or shown schematically for the sake of clarity and / or conciseness.

[0028] When identifying multiple elements or components that may be mentioned separately, the descriptors "first", "second", "third", etc. are used herein. Unless otherwise specified or understood based on their use context, such descriptors are not intended to impose any priority, or time ordering, but are only used as labels for referring to multiple elements or components respectively to facilitate understanding of the disclosed examples. In some examples, the descriptor "first" can be used to refer to an element in the detailed description, while the same element can be referred to in the claims with different descriptors such as "second" or "third". In such a case, it should be understood that such descriptors are only used to facilitate reference to multiple elements or components. DETAILED DESCRIPTION

[0029] The example pellet grills disclosed herein include a control system that implements, manages, and / or controls various ignition-based protocols and / or processes that facilitate operation and / or use of the pellet grill. In some examples, the control system implements, manages, and / or controls the ignition-based protocols and / or processes disclosed herein in conjunction with an engine of the pellet grill. In some examples, the engine includes: a burn pot; an igniter extending into the burn pot; an auger configured to deliver pellet fuel to the burn pot; an auger motor configured to drive the auger; and a fan configured to generate an airflow directed toward the burn pot. In some examples, the igniter is a controllable, DC-powered glow plug that operates in response to data, commands, and / or signals received from the control system of the pellet grill. In some examples, the auger motor is a controllable, DC-powered variable speed electric motor that operates in response to data, commands, and / or signals received from the control system of the pellet grill. In some examples, the fan is a controllable, DC powered, variable speed electric motor fan that operates in response to data, commands, and / or signals received from a control system of the pellet grill.

[0030] In some disclosed examples, a control system of a pellet grill implements, manages, and / or controls an ignition-based start protocol and / or process in conjunction with an engine. The control system is configured to detect the presence of a false start, which may be indicated by a failure of a temperature within a cooking chamber of the pellet grill to rise above a threshold temperature prior to expiration of a predetermined duration and / or time period associated with an initial activation of an igniter of the pellet grill. In some examples, a false start is detected based on data sensed, measured, and / or detected by a temperature sensor of the pellet grill. In response to detecting the false start, the control system commands an activation (e.g., reactivation) of the engine's igniter in order to initiate and / or resume incineration and / or combustion of pellet fuel present in a burner can of the engine.

[0031] In some disclosed examples, the control system generates (e.g., in the form of a command, message, signal, etc.) one or more notifications and / or alarms in conjunction with detecting a faulty initiation for local presentation on a user interface of the pellet grill. The notifications and / or alarms may indicate, for example, that a faulty initiation has been detected, that a faulty initiation has been successfully remedied, and / or that a faulty initiation has not been successfully remedied. The control system may additionally or alternatively cause the generated notifications and / or alarms to be wirelessly transmitted from the pellet grill to a remote device (e.g., a cloud server, a smartphone, a tablet, a laptop, a personal computer, etc.) for presentation and / or analysis thereon.

[0032] In some disclosed examples, a control system of a pellet grill additionally or alternatively implements, manages, and / or controls an ignition-based flameout detection protocol and / or process in conjunction with an engine. The control system is configured to detect the presence of a flameout condition (e.g., an unexpected cessation of fuel combustion), which can be indicated by a temperature of the cooking chamber continuing to drop over a period of time while an auger of the engine is actively attempting to feed and / or supply pellet fuel to a burner can of the engine. In some examples, the flameout condition is detected based on data sensed, measured, and / or detected by a temperature sensor of the pellet grill. In response to detecting the flameout condition, the control system commands an igniter of the engine to activate (e.g., reactivate) in order to resume burning and / or combustion of pellet fuel present in the burner can of the engine.

[0033] In some disclosed examples, the control system generates (e.g., in the form of a command, message, signal, etc.) one or more notifications and / or alerts in conjunction with detecting a flameout condition for local presentation on a user interface of the pellet grill. The notifications and / or alerts may indicate, for example, that a flameout condition has been detected, that the flameout condition has been successfully remedied, and / or that the flameout condition has not been successfully remedied. The control system may additionally or alternatively cause the generated notifications and / or alerts to be wirelessly transmitted from the pellet grill to a remote device (e.g., a cloud server, a smartphone, a tablet, a laptop, a personal computer, etc.) for presentation and / or analysis thereon.

[0034] The above features and other advantageous features of the pellet grill of the present disclosure are further described below in conjunction with the drawings of the present application. U.S. Provisional Patent Application No. 62 / 796,861 filed on January 25, 2019, U.S. Provisional Patent Application No. 62 / 891,011 filed on August 23, 2019, U.S. Patent Application No. 16 / 677,874 filed on November 8, 2019, U.S. Patent Application No. 16 / 677,914 filed on November 8, 2019, U.S. Patent Application No. 16 / 677,931 filed on November 8, 2019, U.S. Patent Application No. 16 / 677,938 filed on November 8, 2019, Certain aspects of the disclosed pellet grills are generally described in U.S. Patent Application No. 16 / 677,959, filed on November 8, 2019, U.S. Patent Application No. 16 / 677,980, filed on November 8, 2019, U.S. Patent Application No. 16 / 677,995, filed on November 8, 2019, U.S. Patent Application No. 16 / 678,006, filed on November 8, 2019, and U.S. Patent Application No. 16 / 678,022, filed on November 8, 2019, the entire contents of each of which are hereby incorporated herein by reference.

[0035] Figure 1 is a perspective view of an example pellet grill 100 constructed in accordance with the teachings of the present disclosure. Figure 2 yes Figure 1 An exploded view of the pellet grill 100 is shown. Figure 3 yes Figure 1 and Figure 2 A front view of a pellet grill 100 is shown. Figure 4 is along Figure 3 Section AA cut Figures 1 to 3 FIG. 1 is a cross-sectional view of a pellet grill 100 . Figures 1 to 4 The pellet grill 100 includes an example body 102. The body 102 of the pellet grill 100 is formed and / or defined by an example first (e.g., left) end cap 104, an example second (e.g., right) end cap 106 opposite the first end cap 104, and an example outer wall 108 extending between the first end cap 104 and the second end cap 106. Figure 4 As shown in the drawings, the first end cap 104, the second end cap 106, the outer wall 108, and / or, more generally, the body 102 of the pellet grill 100 define an example cooking chamber 402 of the pellet grill 100 located within the body 102. The cooking chamber 402 and / or, more generally, the body 102 of the pellet grill 100 includes an example first cooking grate 202 and an example second cooking grate 204, which respectively support cooked, cooking, and / or to-be-cooked food within the cooking chamber 402.

[0036] exist Figures 1 to 4 In the illustrated example, the outer wall 108 of the body 102 is formed by an example first (e.g., lower) outer wall segment 206 and an example second (e.g., upper) outer wall segment 208, which can be coupled to the first outer wall segment 206. In other examples, the first outer wall segment 206 and the second outer wall segment 208 of the outer wall 108 of the body 102 can be integrally formed as a single component. Figures 1 to 4 In the illustrated example, the first outer wall segment 206 and / or, more generally, the outer wall 108 of the body 102 includes an example first opening 210 that is configured (e.g., sized, shaped, and / or positioned) to receive an example engine 212 of the pellet grill 100. The outer wall 108 and / or, more generally, the body 102 of the pellet grill also includes and / or defines an example second opening that is configured (e.g., sized, shaped, and / or positioned) to be selectively covered or uncovered by an example lid 110 of the pellet grill 100. Placing the lid 110 in the open position allows a user to access the cooking chamber 402, as may be desired to load, remove, and / or otherwise access food that has been cooked, is being cooked, and / or is to be cooked within the cooking chamber 402. In the closed position (e.g., as shown in FIG. 1 ), the lid 110 is opened and closed. Figure 1 , Figure 2 and Figure 4Movement between the open position (shown in FIG. 1 ) and the open position may be facilitated by an example handle 112 coupled to the lid 110 .

[0037] Figures 1 to 4 The pellet grill 100 further includes an example hopper 114. The hopper 114 holds a quantity of pellet fuel to be fed and / or supplied (eg, by gravity) to the engine 212 of the pellet grill 100. Figures 1 to 4 In the illustrated example, the hopper 114 is mounted on and / or to the rear of the pellet grill 100 and is generally oriented toward the second end cap 106 of the body 102. The hopper 114 extends laterally past the second end cap 106, thereby facilitating loading and / or filling of the hopper 114 from the front and / or side areas of the pellet grill 100 proximate the side platform 130. In other examples, the hopper 114 may be mounted on and / or to the rear of the pellet grill 100, but may alternatively be oriented toward and extend laterally past the first end cap 104 of the body 102. In other examples, the hopper 114 may alternatively be mounted on and / or to the left or right side of the pellet grill 100.

[0038] Figures 1 to 4 The pellet grill 100 further includes an engine 212. The engine 212 extends through a first opening 210 formed in the outer wall 108 of the body 102. A frame of the engine is coupled to the outer wall 108 and / or, more generally, the body 102 to rigidly secure the engine 212 to the body. The engine 212 receives pellet fuel from the hopper 114 of the pellet grill 100. The engine 212 causes the received pellet fuel to burn to produce, generate and / or output heat, which is then distributed throughout the cooking chamber 402 of the pellet grill 100 to cook one or more food items located therein. Figures 5 to 10 Further description Figures 1 to 4 An example implementation of the engine 212 of the pellet grill 100 is shown.

[0039] Figures 1 to 4 The pellet grill 100 further includes an example user interface 116. The user interface 116 includes one or more example input devices 118 (e.g., buttons, switches, knobs, touch screens, etc.) and / or one or more example output devices 120 (e.g., liquid crystal displays, light emitting diodes, speakers, etc.) that enable a user of the pellet grill 100 to interact with a control system of the pellet grill 100 (e.g., the control system discussed below). Fig.11 The control system 1100) interacts with the Figures 1 to 4In the illustrated example, the user interface 116 is mounted on and / or to the front of the hopper 114. In other examples, the user interface 116 may be mounted on and / or to a different surface of the hopper 114. In other examples, the user interface 138 may be mounted on and / or to a different component of the pellet grill 100 (e.g., the side table 130 of the pellet grill 100). Fig.11 Further description Figures 1 to 4 An example implementation of the user interface 116 of the pellet grill 100 is shown.

[0040] Figure 5 is a first perspective view of an example engine 500 for a pellet grill. Figure 6 yes Figure 5 A second perspective view of the engine 500 is shown. Fig. 7A and Figure 7B yes Figure 5 and Figure 6 An exploded view of engine 500 is shown. Figure 8 yes Figure 5 To FIG. 7 a side view of the engine 500 . Fig. 9 yes Figures 5 to 8 A front view of the engine 500. Fig.10 is along Fig. 9 Section BB cut Figures 5 to 9 A cross-sectional view of an engine 500 is shown. Figures 5 to 10 The engine 500 may be implemented as described above. Figures 1 to 4 The engine 212 of the pellet grill 100 .

[0041] Figures 5 to 10 The engine 500 includes an example frame 502, an example housing 504, an example fuel chute 506, an example auger conduit 508, an example auger 510, an example auger motor 512, an example burner can 514, an example fan 516, an example fuel grid 702, an example igniter 704, and an example igniter bracket 706. Figures 5 to 10 In the illustrated example, the frame 502 of the engine 500 has an arcuate shape that complements and / or matches the arcuate shape of the outer wall 108 of the body 102 of the pellet grill 100 (proximate the first opening 210 of the outer wall 108). The frame 502 includes a plurality of example nuts 518 that are configured (e.g., sized, shaped, and / or arranged) to align with corresponding through holes formed in the outer wall 108 of the body 102 of the pellet grill 100 to facilitate coupling the frame 502 (e.g., via fasteners) to the outer wall 108 of the body 102 of the pellet grill 100 such that a portion of the engine 500 extends through the first opening 210 of the outer wall 108 of the body 102. For example, when Figures 5 to 10 When the frame 502 is coupled to the outer wall 108 of the body 102 of the pellet grill 100, portions of the housing 504, fuel chute 506, auger conduit 508, auger 510, burn pot 514, fuel grid 702, igniter 704, and igniter bracket 706 extend inwardly through the first opening 210 of the outer wall 108 and are located within the body 102 of the pellet grill 100 (e.g., within the cooking chamber 402).

[0042] Figures 5 to 10 The housing 504 of the engine 500 extends through the frame 502 of the engine 500 and is partially supported by the frame 502. Figures 5 to 10 In the illustrated example, the housing 504 is a rectangular box structure that includes and / or is defined by an example front wall 708, an example rear wall 710 that is opposite to the front wall 708, an example first (e.g., left) side wall 712 that extends between the front wall 708 and the rear wall 710, an example second (e.g., right) side wall 714 that extends between the front wall 708 and the rear wall 710 and is opposite to the first side wall 712, and an example bottom wall 716 that extends between the front wall 708 and the rear wall 710 and further extends between the first side wall 712 and the second side wall 714. An example cover plate 718 defines an example top surface 720 of the housing 504.

[0043] The housing 504 further includes an example first opening 722, an example second opening 724, an example third opening 1002, and an example fourth opening 726. The first opening 722 of the housing 504 is located at the top surface 720 of the housing 504 in front of the cover plate 718. The second opening 724 of the housing 504 is located at and / or formed in the rear wall 710 of the housing 504 near the bottom wall 716 of the housing 504. The third opening 1002 of the housing 504 is located at and / or formed in the bottom wall 716 of the housing 504 near the front wall 708 of the housing 504. The fourth opening 726 of the housing 504 is located at and / or formed in the bottom wall 716 of the housing 504 near the rear wall 710 of the housing 504.

[0044] like Fig.10As shown in FIG. 1 , the housing 504 of the engine 500 houses, contains and / or carries the burn pot 514, the fuel grid 702, the igniter 704 and the igniter bracket 706 of the engine 500. The burn pot 514 (including the fuel grid 702) is received within the housing 504 via the first opening 722 of the housing 504 and is positioned and / or located above and / or vertically aligned with the third opening 1002 of the housing 504. The vertical alignment of the burn pot 514 and the fuel grid 702 above the third opening 1002 of the housing 504 advantageously allows ash (e.g., ash that may be generated and / or produced during the incineration and / or combustion of the particulate fuel contained within the burn pot 514) to pass through and / or fall through the fuel grid 702 and through the third opening 1002 of the housing 504 onto the example ash chute 520 of the engine 500. The ash chute 520 is configured (e.g., sized, shaped, and / or arranged) to direct the ash downward (e.g., away from the burn pot 514) and prevent the swirling flow of the ash from traveling upward toward the burn pot 514. When the burn pot 514 is placed in the housing 504, the example upper plate 522 of the burn pot 514 covers and / or closes a portion of the first opening 722 of the housing 504 in front of the cover plate 718. As further described below, the fuel chute 506 of the engine 500 is mounted and / or coupled to the upper plate 522 of the burn pot 514. Fig.10 As further shown in FIG. 5 , the igniter 704 and igniter bracket 706 of the engine 500 are slidably received in the housing 504 via the second opening 724 of the housing 504. When the igniter 704 and igniter bracket 706 are placed in the housing 504, the example rear tab 728 of the igniter bracket 706 covers and / or closes the second opening 724 of the housing 504.

[0045] The fan 516 of the engine 500 is mounted and / or coupled to the housing 504 at the bottom wall 716 of the housing 504 by means of an example fan retainer 524 and is positioned and / or located below and / or vertically aligned with a fourth opening 726 of the housing 504. The vertical alignment of the fan 516 below the fourth opening 726 of the housing 504 enables the airflow generated, produced and / or output by the fan 516 to pass through the fourth opening 726 into the housing 504. Once the airflow penetrates the housing 504 from the fan 516, the airflow is then directed and / or introduced into the combustion can 514.

[0046] exist Figures 5 to 10In the illustrated example, the fuel chute 506 includes an example panel 730 having an example front end 732, an example rear end 734 opposite the front end 743, a first example outwardly extending flange 736 extending between the front end 732 and the rear end 734, and a second example outwardly extending flange 738 extending between the front end 732 and the rear end 734 and opposite the first outwardly extending flange 736. The panel 730 further includes: a first mounting tab 740 proximate the front end 732 of the panel 730 and extending forwardly from the first outwardly extending flange 736; a second mounting tab 742 proximate the front end 732 of the panel 730 and extending forwardly from the second outwardly extending flange 738; and an example opening 744 proximate the rear end 734 of the panel 730.

[0047] exist Figures 5 to 10 In the illustrated example, each of the first mounting tab 740 and the second mounting tab 742 of the panel 730 is configured (e.g., sized, shaped, and / or arranged) to align and / or mate with a through hole formed in the upper plate 522 of the burn can 514 to facilitate mounting and / or coupling the fuel runner 506 of the engine 500 to the burn can 514 of the engine 500. The opening 744 of the panel 730 is configured (e.g., sized, shaped, and / or arranged) to slidingly receive the auger conduit 508 to facilitate mounting and / or coupling the fuel runner 506 of the engine 500 to the auger conduit 508 of the engine 500. The panel 730 of the fuel runner 506 is oriented and / or angled in a descending manner from rear to front (e.g., a rear end 734 of the panel 730 is higher than a front end 732 of the panel 730). Panel 730 is configured to receive particulate fuel discharged from the screw conveyor pipe 508 of the engine 500, and feed and / or guide the received particulate fuel downwardly and / or forwardly from the rear end (e.g., upper end) 734 of the panel 730 to the front end (e.g., lower end) 732 of the panel 730, and then enter the combustion tank 514 of the engine 500.

[0048] Figures 5 to 10 The auger conduit 508 of the engine 500 extends through and is partially supported by an example opening 746 formed in the frame 502 of the engine 500. The auger conduit 508 also extends through and is partially supported by an opening 744 formed in the rear (e.g., upper) end 734 of the panel 730 proximate the fuel chute 506. Figures 5 to 10 In the illustrated example, the auger conduit 508 is a cylindrical structure that is configured (e.g., sized, shaped, and / or arranged) to accommodate and / or contain the auger 510 of the engine 500 and pellet fuel to be fed and / or supplied by the auger 510 from the feed conduit of the hopper 114 of the pellet grill 100 to the panel 730 of the fuel chute 506 of the engine 500. Figures 5 to 10 The auger conduit 508 includes and / or is defined by an example front end 748, an example rear end 750 opposite the front end 748, and an example sidewall 752 extending between the front end 748 and the rear end 750. Figures 5 to 10 In the illustrated example, the auger conduit 508 is oriented and / or angled in a rear-to-front tilted manner (e.g., a rear end 750 of the auger conduit 508 is lower than a front end 748 of the auger conduit 508). The auger conduit 508 is coupled to an example conduit mount 754. The conduit mount 754 is configured (e.g., sized, shaped, and / or arranged) to facilitate coupling the auger conduit 508 to the auger 510 and / or auger motor 512 of the engine 500.

[0049] Figures 5 to 10 The auger conduit 508 further includes an example first opening 756 formed in the front end 748 of the auger conduit 508, an example second opening 758 formed in the rear end 750 of the auger conduit 508, and an example third opening 760 formed in the upper portion of the sidewall 752 of the auger conduit 508. The first opening 756 and the second opening 758 of the auger conduit 508 are respectively configured (e.g., sized, shaped, and / or arranged) to enable the auger conduit 508 to be slidably positioned around and / or over (e.g., over the length of) the auger 510 so that the auger 510 is received and / or contained within the auger conduit 508. The third opening 760 of the auger conduit 508 is configured (e.g., sized, shaped, and / or arranged) to receive pellet fuel from a feed conduit of the hopper 114 of the pellet grill 100.

[0050] Figures 5 to 10 The auger 510 of the engine 500 extends through the auger conduit 508 of the engine 500. The auger 510 is configured (e.g., sized, shaped, and / or arranged) to move pellet fuel received within the auger conduit 508 toward (e.g., during a cooking operation) or away from (e.g., in response to a blockage of the auger 510, and / or during an end-of-cook purge of the pellet fuel) a front end 748 of the auger conduit 508 and / or a faceplate 730 of the fuel chute 506 of the engine 500. Figures 5 to 10In the illustrated example, the screw conveyor 510 includes: an example front end 762 oriented toward the front end 748 of the screw conveyor conduit 508; an example rear end 764 opposite the front end 762 of the screw conveyor 510 and oriented toward the rear end 750 of the screw conveyor conduit 508; and an example spiral winding portion and / or a flighting 766 extending between the front end 762 and the rear end 764 of the screw conveyor 510. Figures 5 to 10 The scraper 766 of the auger 510 is a non-variable pitch (e.g., constant pitch) scraper. In other examples, the scraper 766 of the auger 510 can be a variable pitch scraper whose pitch increases from back to front (e.g., the scraper pitch increases as it moves from the rear end 764 of the auger 510 to the front end 762 of the auger 510). The movement of the auger 510 (e.g., the rotation direction, rotation rate, and / or duty cycle of the auger 510) can be controlled by the auger motor 512 of the engine 500.

[0051] Figures 5 to 10 The auger motor 512 of the engine 500 is coupled to the auger 510 and to the pipe base 754. The auger motor 512 includes an example shaft 768 that operably couples the auger motor 512 with the flight 766 of the auger 510 to provide motor-driven rotation thereof. The auger motor 512 controls the movement (e.g., direction of rotation, rate of rotation, and / or duty cycle) of the auger 510. Figures 5 to 10 In the illustrated example, the auger motor 512 is a controllable, DC powered, variable speed electric motor that responds to signals from a control system of the pellet grill 100 (e.g., described below). Fig.11 The system operates based on data, commands and / or signals received by the control system 1100).

[0052] In some examples, Figures 5 to 10 The auger motor 512 rotates the auger 510 in a first (e.g., clockwise) direction to move particulate fuel contained in the auger conduit 508 away from the rear end 750 of the auger conduit 508 and / or toward the front end 748 of the auger conduit 508 and / or toward the panel 730 of the fuel chute 506 of the engine 500. Figures 5 to 10The auger motor 512 of the engine 500 can also rotate the auger 510 in a second (e.g., counterclockwise) direction to move the particulate fuel contained in the auger conduit 508 away from the front end 748 of the auger conduit 508 and / or toward the rear end 750 of the auger conduit 508 and / or away from the panel 730 of the fuel chute 506 of the engine 500. Therefore, the auger 510 of the engine 500 is a reversible auger whose rotation direction is controlled via the auger motor 512 of the engine 500.

[0053] Figures 5 to 10 The burn pot 514 is configured to contain the particulate fuel to be burned, being burned and / or burning in the burn pot 5146. The burn pot 2216 is also configured to direct heat produced, generated and / or output as a byproduct of the burning and / or burning of the particulate fuel upward, and to direct ash produced and / or generated as a byproduct of the burning and / or burning of the particulate fuel downward. Figures 5 to 10 In the illustrated example, the burn pot 514 includes an example upper end 526 defined by an upper plate 522 of the burn pot 514, an example lower end 770 opposite the upper end 526 of the burn pot 514, and an example sidewall 772 extending between the upper end 526 and the lower end 770 of the burn pot 514. The burn pot 514 further includes an example first opening 528 formed along and / or at the upper end 526 of the burn pot 514. The first opening 528 of the burn pot 514 is configured (e.g., sized, shaped, and / or arranged) to receive particulate fuel from a panel 730 of a fuel chute 506 of the engine 500 and to discharge and / or output upwardly heat generated and / or produced as a byproduct of the incineration and / or combustion of the particulate fuel. Figures 5 to 10 The burn pot 514 further includes an example second opening 1004 formed along and / or at the lower end 770 of the burn pot 514. The second opening 1004 of the burn pot 514 is configured (e.g., sized, shaped, and / or arranged) to release ash generated and / or produced as a byproduct of the burning and / or combustion of the particulate fuel downwardly. The fuel grid 702 is positioned within the burn pot 514 and / or located between the first opening 528 and the second opening 1004 of the burn pot 514.

[0054] Figures 5 to 10The burn can 514 further includes an example third opening 1006 and an example through hole 1008, respectively formed in the side wall 772 of the burn can 514. The third opening 1006 of the burn can 514 is configured (e.g., sized, shaped, and / or arranged) to slidably receive the igniter 704 of the engine 500 so that the tip end of the igniter 704 is positioned and / or located within the burn can 514 near the lower end 770 of the burn can 514. The through hole 1008 of the burn can 514 is configured (e.g., sized, shaped, and / or arranged) around the side wall 772 of the burn can 514 so that the airflow generated, produced, and / or output by the fan 516 of the engine 500 is received within the burn can 514. The movement of airflow into the burn pot 514 via the through-holes 1008 helps control the incineration and / or combustion of the pellet fuel within the burn pot 514, and / or helps control the movement of heat generated, produced and / or output from the burn pot 514 as a byproduct of the incineration and / or combustion of the pellet fuel throughout the cooking chamber 402 of the pellet grill 100.

[0055] Figures 5 to 10 The fuel grate 702 of the burn pot 514 is configured to support and / or hold the pellet fuel to be burned, burning and / or burning in the burn pot 514. The fuel grate 702 is also configured to release ash generated and / or produced as a byproduct of the burning and / or combustion of the pellet fuel downwardly toward the lower end 770 and / or the second opening 1004 of the burn pot 514, and / or toward the ash chute 520 of the pellet grill 100. The fuel grate 702 includes an example upper surface 774, an example trough 776 extending downwardly from and / or below the upper surface 774, and an example opening 778 (e.g., a slot and / or hole) formed along the upper surface 774 and the trough 776 of the fuel grate 702.

[0056] The upper surface 774 of the fuel grid 702 defines a circular and / or disc-like shape of the fuel grid 702 that is configured (e.g., sized and / or shaped) to fill a cross-sectional area defined by the sidewall 772 of the burn pot 514 at a location along the sidewall 772 where the fuel grid 702 will be positioned and / or located. The fuel grid 702 is positioned and / or located within the burn pot 514 between the first opening 528 and the second opening 1004 of the burn pot 514. The openings 778 formed in the upper surface 774 and the grooves 776 of the fuel grid 702 can be configured (e.g., sized, shaped, and / or arranged) in any manner to facilitate the passage of ash (e.g., ash generated and / or produced as a byproduct of the incineration and / or combustion of the particulate fuel) downward through the openings 778 to a location below the fuel grid 702.

[0057] The grooves 776 of the fuel grid 702 are configured to funnel, direct and / or collect particulate fuel that has been deposited into the combustion pot 514 toward and / or within a concentrated location and / or place of the fuel grid 702. Fig.10 As shown in FIG. 7 , the grooves 776 of the fuel grid 702 extend across the fuel grid 702 and are oriented perpendicular to the orientation of the axis of the igniter 704 of the engine 500. In other examples, the orientation of the grooves 776 of the fuel grid 702 may alternatively differ from FIG. 7 and Fig.10 . For example, the orientation of the grooves 776 of the fuel grid 702 can alternatively be parallel to the orientation of the axis of the igniter 704 of the engine 500.

[0058] In some examples, the groove 776 and / or, more generally, the fuel grid 702 of the burn pot 514 is oriented such that a portion (e.g., a tip) of the igniter 704 of the engine 500 is positioned within and / or located within the groove 776. In such examples, the groove 776 of the fuel grid 702 advantageously directs and / or collects the particulate fuel toward and / or within a concentrated location and / or place of the fuel grid 702, thereby placing the collected particulate fuel adjacent to and / or in contact with the igniter 704. As described above, concentrating and / or positioning the particulate fuel within the groove 776 is advantageous for starting and / or initiating the burning of the particulate fuel. Concentrating and / or positioning the particulate fuel within the groove 776 as described above is also advantageous for low temperature cooking operations (e.g., smoking), in which the burn pot 514 of the engine 500 will contain a relatively small amount of particulate fuel.

[0059] As shown in Figure 7 and Fig.10 As shown in FIG. 7 and FIG. 8 , the groove 776 of the fuel grid 702 is generally V-shaped. In other examples, the groove 776 may have a shape different from that shown in FIG. Fig.10 . For example, the groove 776 of the fuel grid 702 may alternatively have a rectangular shape or an arcuate (e.g., concave upward) shape. The groove 776 may be configured to have any shape that funnels, guides, and / or collects particulate fuel that has been deposited into the burn pot 514 toward a concentrated location and / or place of the fuel grid 702 of the burn pot 514 and / or within a concentrated location and / or place of the fuel grid 702 of the burn pot 514.

[0060] Figures 5 to 10 The igniter 704 of the engine 500 includes an example front end 780, an example rear end 782 opposite the front end 780 of the igniter 704, and an example shaft 784 extending from the front end 780 of the igniter 704 toward the rear end 782. Figures 5 to 10In the illustrated example, the front end 780 of the igniter 704 extends through one of the openings 778 formed in the groove 776 of the fuel grid 702, so that the front end 780 of the igniter 704 is positioned and / or located in the groove 776 of the fuel grid 702 and / or, more generally, in the combustion pot 514 of the engine 500. The rear end 782 of the igniter 704 is positioned and / or located in the igniter bracket 706 and / or supported by the igniter bracket. The middle portion of the shaft 784 of the igniter 704 extends through the third opening 1006 of the side wall 772 of the combustion pot 514. The rear portion of the shaft 784 is supported by the igniter bracket 706 and / or removably coupled thereto. The igniter 704 may be activated to generate, produce, and / or output heat to ignite and / or initiate combustion of particulate fuel positioned and / or located within the burn pot 514 (e.g., positioned and / or located on the fuel grid 702 of the burn pot 514). Figures 5 to 10 In the illustrated example, the igniter 704 is a controllable, DC powered glow plug that responds to a control system from the pellet grill 100 (e.g., described below). Fig.11 The system operates based on data, commands and / or signals received by the control system 1100).

[0061] Figures 5 to 10 The igniter bracket 706 of the engine 500 includes an example front end 786, an example rear end 788 opposite the front end 786 of the igniter bracket 706, and an example arm 790 extending between the front end 786 and the rear end 788 of the igniter bracket 706. The front end 786 of the igniter bracket 706 includes an example connection socket 792 that is configured (e.g., sized, shaped, and / or arranged) to receive the rear end 782 of the igniter 704 and / or the rear portion of the shaft 784. The igniter 704 is supported and / or carried by the igniter bracket 706 and is removably connected to the igniter bracket 706 via the connection socket 792 located at the front end 786 of the igniter bracket 706. The rear end 788 of the igniter bracket 706 forms a rear tab 728 of the igniter bracket 706, which can be removed from the igniter bracket 706 as described above. Figures 5 to 10 The rear side of the housing 504 of the engine 500 is close to the rear tab.

[0062] Figures 5 to 10The igniter bracket 706 and igniter 704 can be removed from the housing 504 of the engine 500 and / or, more generally, from the pellet grill 100 (e.g., to facilitate replacement of the igniter 704) via the rear tab 728 of the igniter bracket 706. For example, the igniter bracket 706 is pulled rearwardly via the rear tab 728 of the igniter bracket 706, so that the igniter 704 is removed from the groove of the fuel grill 702 (e.g., through one opening 778 formed in the groove 776), removed from the burner can 514 of the engine 500 (e.g., through the third opening 1006 formed in the side wall 772 of the burner can 514), and removed from the housing 504 of the engine 500 (e.g., through the second opening 724 formed in the rear wall 710 of the housing 504). Once the igniter bracket 706 and igniter 704 are removed from the housing 504 and / or the pellet grill 100, the igniter 704 can be removed from the igniter bracket 706 (e.g., by pulling the igniter 704 out of the connection socket 792 of the igniter bracket 706) and replaced with another (e.g., new and / or replacement) igniter 704. Thereafter, the igniter bracket 706 and replacement igniter 704 can be reinserted and / or slid back into the housing 504 and / or the pellet grill 100.

[0063] Figures 5 to 10 The fan 516 of the engine 500 is coupled to the bottom wall 716 of the housing 504 of the engine 500 by means of a fan retainer 524. The fan retainer 524 includes an example grille 602 that is configured (e.g., sized and / or shaped) to allow air to enter the fan 516 while also advantageously preventing solid foreign matter from being accidentally drawn into the fan 516. Figures 5 to 10 In the illustrated example, the fan 516 and the fan holder 524 are located and / or positioned in a position vertically aligned with the fourth opening 726 of the housing 504. The fan 516 generates, produces, outputs and / or controls an airflow that is directed from the fan 516 through the housing 504 toward the burn pot 514. The airflow generated, produced and / or output by the fan 516 can then enter the cooking chamber 402 of the pellet grill 100 from the burn pot 514 to provide controlled circulation of hot air within the cooking chamber 402. Figures 5 to 10 In the illustrated example, the fan 516 is a controllable, DC powered, variable speed electric motor fan that responds to a control system from the pellet grill 100 (e.g., described below). Fig.11 The system operates based on data, commands and / or signals received by the control system 1100).

[0064] Fig.11 It is a combination Figures 1 to 4 1 is a block diagram of an example control system 1100 implemented with the pellet grill 100. Fig.11 The control system 1100 includes the above Figures 1 to 10The user interface 116 (eg, including the input device 118 and the output device 120) and the engine 500 (eg, including the auger motor 512, the fan 516, and the igniter 704). Fig.11 The control system 1100 further includes an example DC power supply 1102 , an example temperature sensor 1104 , an example timer 1106 , an example counter 1108 , an example controller 1110 , and an example memory 1112 .

[0065] Fig.11 The DC power supply 1102 receives AC power from an example AC line power source 1114 (e.g., a wall outlet) that is electrically connected to the DC power supply 1102 and / or, more generally, to the pellet grill 100. The DC power supply 1102 converts the AC power received from the AC line power source 1114 to DC power, which may then be supplied to the user interface 116, auger motor 512, fan 516, igniter 704, temperature sensor 1104, timer 1106, counter 1108, controller 1110, and / or memory 1112 of the pellet grill 100. In some examples, the distribution of DC power from the DC power supply 1102 to any of the above-described components of the control system 1100 may be controlled and / or managed by the controller 1110.

[0066] Fig.11 The temperature sensor 1104 senses, measures and / or detects the temperature of the cooking chamber 402 of the pellet grill 100. In some examples, the temperature sensor 1104 may be implemented as a thermocouple positioned and / or extending into the cooking chamber 402 of the pellet grill 100 and / or as a thermocouple positioned and / or extending into the cooking chamber 402 of the pellet grill 100. Fig.11 The data and / or signals sensed, measured and / or detected by the temperature sensor 1104 may be of any quantity, type, form and / or format and may be stored in a computer-readable storage medium (e.g., Fig.11 in memory 1112).

[0067] Fig.11 The timer 1106 is configured to measure and / or maintain an elapsed time. In some examples, one or more operations of the timer 1106 can be controlled and / or managed by the controller 1110. For example, the controller 1110 can command and / or instruct the timer 1106 to start, stop, and / or reset the elapsed time measured and / or maintained by the timer 1106. Based on the elapsed time measured and / or maintained by the timer 1106, the controller 1110 can detect whether the elapsed time exceeds a threshold time period (e.g., a threshold duration). In some examples, the threshold time period can be related to the elapsed time measured and / or maintained by the timer 1106. Fig.11The automation protocols, processes, sequences and / or methods implemented by the control system 1100 are associated with, including but not limited to, the following combined Figures 12 to 16 Various protocols, processes, sequences and / or methods described.

[0068] Fig.11 The counter 1108 is configured to maintain a count. In some examples, one or more operations of the counter 1108 may be controlled and / or managed by the controller 1110. For example, the controller 1110 may command and / or instruct the counter 1108 to increase, decrease, and / or reset an activation count maintained by the counter 1108, whereby the activation count corresponds to the number of activations of the igniter 704. Based on the activation count maintained by the counter 1108, the controller 1110 may detect whether the number of activations of the igniter 704 exceeds a threshold activation count. In some examples, the threshold activation count may be associated with a predetermined time period. In other examples, the threshold activation count may be associated with a predetermined time period in addition to or alternatively to a time period maintained by the controller 1110. Fig.11 The automation protocols, processes, sequences and / or methods implemented by the control system 1100 are associated with, including but not limited to, the following combined Figures 12 to 16 Various protocols, processes, sequences and / or methods described.

[0069] In other examples, counter 1108 may additionally or alternatively maintain a fault count. For example, controller 1110 may command and / or instruct counter 1108 to increase, decrease, and / or reset a fault count maintained by counter 1108, whereby the fault count corresponds to the number of failed attempts to meet a temperature requirement associated with a temperature within cooking chamber 402 of pellet grill 100. Based on the fault count maintained by counter 1108, controller 1110 may detect whether the fault count has reached and / or exceeded a threshold fault count. In some examples, the threshold fault count may be associated with a predetermined time period. In other examples, the threshold fault count may additionally or alternatively be associated with a predetermined time period. Fig.11 The automation protocols, processes, sequences and / or methods implemented by the control system 1100 are associated with, including but not limited to, the following combined Figures 12 to 16 Various protocols, processes, sequences and / or methods described.

[0070] Fig.11 The controller 1110 may be implemented by any type and / or any number of processors, microprocessors, controllers, microcontrollers, transmitters, receivers, timers, counters, circuits, and / or other electrical components. Fig.11 The timer 1106 and the counter 1108 are shown as being separate from the controller 1110, but in other examples, the timer 1106 and / or the counter 1108 can be implemented by the controller 1110 and / or integrated within the controller 1110. Fig.11 1100 is shown as a single controller, but in other examples, the controller 1110 may be implemented as multiple controllers, which may be implemented on and / or by one or more control boards. Fig.11 In the illustrated example, the controller 1110 is operably coupled to (eg, electrically coupled to) the user interface 116 , the auger motor 512 , the fan 516 , the igniter 704 , the temperature sensor 1104 , the timer 1106 , the counter 1108 , and / or the memory 1112 of the control system 1100 .

[0071] Fig.11 The controller 1110 controls and / or manages one or more operations of the user interface 116, the auger motor 512, the fan 516, the igniter 704, the temperature sensor 1104, the timer 1106, the counter 1108, and / or the memory 1112. In some examples, the controller 1110 is Fig.11 The controller 1110 may receive data, commands, and / or signals from and / or transmit data, commands, and / or signals to the user interface 116, the auger motor 512, the fan 516, the igniter 704, the temperature sensor 1104, the timer 1106, the counter 1108, and / or the memory 1112. In other examples, the controller 1110 may wirelessly receive data, commands, and / or signals from and / or transmit data, commands, and / or signals to one or more remote electronic devices (e.g., cloud servers, smart phones, tablet computers, laptop computers, personal computers, etc.) remote electronic devices (e.g., cloud servers, smart phones, tablet computers, laptop computers, personal computers, etc.).

[0072] In some examples, Fig.11 The controller 1110 of the control system 1100 manages and / or controls the ignition-based start-up protocol and / or process in conjunction with the engine 500 of the control system 1100. The controller 1110 is configured to detect the presence of a false start, which may be indicated by the failure of the temperature within the cooking chamber 402 of the pellet grill 100 to rise above a threshold temperature prior to the expiration of a predetermined duration and / or time period associated with the initial activation of the igniter 704 of the engine 500. In some examples, the false start is detected based on data sensed, measured, and / or detected by the temperature sensor 1104 of the control system 1100. In response to detecting the false start, the controller 1110 commands the igniter 704 of the engine 500 to activate (e.g., reactivate) with the intent of initiating and / or resuming incineration and / or combustion of pellet fuel present in the burn can 514 of the engine 500.

[0073] In some examples, the controller 1110 generates (e.g., in the form of a command, message, signal, etc.) one or more notifications and / or alarms in conjunction with detecting a faulty initiation for local presentation on the user interface 116 of the control system 1100 and / or the pellet grill 100. The notifications and / or alarms may indicate, for example, that a faulty initiation has been detected, that a faulty initiation has been successfully remedied, and / or that a faulty initiation has not been successfully remedied. The controller 1110 may additionally or alternatively cause the generated notifications and / or alarms to be wirelessly transmitted from the control system 1100 and / or the pellet grill 100 to a remote device (e.g., a cloud server, a smartphone, a tablet, a laptop, a personal computer, etc.) for presentation and / or analysis thereon.

[0074] In some examples, Fig.11 The controller 1110 of the control system 1100 additionally or alternatively implements, manages and / or controls an ignition-based flameout detection protocol and / or process in conjunction with the engine 500 of the control system 1100. The controller 1110 is configured to detect the presence of a flameout condition (e.g., an unexpected cessation of fuel combustion), which may be indicated by a temperature within the cooking chamber 402 of the pellet grill 100 that continues to drop over a period of time while the auger 510 of the engine 500 is actively attempting to feed and / or supply pellet fuel to the burn pot 514 of the engine 500. In some examples, the flameout condition is detected based on data sensed, measured and / or detected by the temperature sensor 1104 of the control system 1100. In response to detecting the flameout condition, the controller 1110 commands the igniter 704 of the engine 500 to activate (e.g., reactivate) in order to resume burning and / or combustion of the pellet fuel present in the burn pot 514 of the engine 500.

[0075] In some examples, the controller 1110 generates (e.g., in the form of a command, message, signal, etc.) one or more notifications and / or alarms in conjunction with detecting a flameout condition for local presentation on the user interface 116 of the control system 1100 and / or the pellet grill 100. The notifications and / or alarms may indicate, for example, that a flameout condition has been detected, that the flameout condition has been successfully remedied, and / or that the flameout condition has not been successfully remedied. The controller 1110 may additionally or alternatively cause the generated notifications and / or alarms to be wirelessly transmitted from the control system 1100 and / or the pellet grill 100 to a remote device (e.g., a cloud server, a smartphone, a tablet, a laptop, a personal computer, etc.) for presentation and / or analysis thereon.

[0076] Fig.11The memory 1112 may be implemented by any type and / or any number of storage devices, such as storage drives, flash memory, read-only memory (ROM), random access memory (RAM), cache, and / or any other physical storage medium in which information is stored for any duration (e.g., for an extended period of time, permanently, for a short period of time, temporarily buffered, and / or cached information). Fig.11 The information in the memory 1112 may be stored in any file and / or data structure format, organizational scheme, and / or arrangement.

[0077] The memory 1112 stores Fig.11 The user interface 116 of the control system 1100, the screw conveyor motor 512, the fan 516, the igniter 704, the temperature sensor 1104, the timer 1106, the counter 1108 and / or the controller 1110 sense, measure, detect, generate, transmit and / or receive data. The memory 1112 also stores the following in conjunction with Figures 12 to 16 Instructions (eg, computer-readable instructions) and associated data corresponding to the described protocols, processes, sequences, and / or methods. Fig.11 The memory 1112 may be comprised of one or more of the user interface 116, the auger motor 512, the fan 516, the igniter 704, the temperature sensor 1104, the timer 1106, the counter 1108, the controller 1110, and / or, more generally, Fig.11 1100 access to the control system.

[0078] Although Fig.11 An example method of implementing the control system 1100 is illustrated in Fig.11 One or more of the components, elements and / or devices illustrated in the examples may be combined, divided, rearranged, omitted, omitted and / or implemented in any other manner. In addition, the user interface 116 (including the input device 118 and the output device 120), the engine 500 (including the screw conveyor motor 512, the fan 516 and the igniter 704), the DC power supply 1102, the temperature sensor 1104, the timer 1106, the counter 1108, the controller 1110, the memory 1112 and / or, more generally, Fig.11 The control system 1100 may be implemented in hardware, software, firmware, and / or any combination of hardware, software, and / or firmware. Thus, for example, Fig.11Any of the user interface 116 (including input device 118 and output device 120), DC power supply 1102, temperature sensor 1104, timer 1106, counter 1108, controller 1110 and / or memory 1112 can be implemented by one or more analog or digital circuits, logic circuits, programmable processors, programmable controllers, digital signal processors, application specific integrated circuits, programmable logic devices and / or field programmable logic devices. When reading any device or system claims of this patent to cover pure software and / or firmware implementations, Fig.11 At least one of the controller 1110 and / or the memory 1112 of the control system 1100 is expressly defined herein as comprising a non-transitory computer-readable storage device or storage disk (e.g., memory, digital versatile disk, optical disk, Blu-ray disk, etc.) containing software and / or firmware. As used herein, the phrase "communication" includes variations thereof, encompassing direct communication and / or indirect communication via one or more intermediate components, and does not require direct physical (e.g., wired) communication and / or continuous communication, but rather includes selective communication at regular intervals, predetermined intervals, non-regular intervals, and / or one-time events.

[0079] Figures 12 to 16 The diagram shows a method for implementing Fig.11 Flowcharts of example hardware logic, machine-readable instructions, hardware-implemented state machines, and / or any combination thereof of the control system 1100. The machine-readable instructions may be one or more executable programs or portions of executable programs for execution by one or more processors and / or controllers. The programs may be implemented in software stored on a non-transitory computer-readable storage medium (e.g., a hard drive, a flash drive, or a memory associated with a processor and / or controller), but the entire program and / or portions thereof may alternatively be executed by a device other than a processor and / or controller and / or implemented in firmware or dedicated hardware. In addition, although reference is made to Figures 12 to 16 The flowchart shown in describes an example procedure, but may alternatively be implemented using Fig.11 Many other methods of controlling the system 1100 of the present invention may be described. For example, the order of execution of the blocks may be changed, and / or some of the blocks described may be changed, eliminated, or combined. Additionally or alternatively, any or all of the blocks may be implemented by one or more hardware circuits (e.g., discrete and / or integrated analog and / or digital circuits, FPGAs, ASICs, comparators, operational amplifiers (op-amps), logic circuits, etc.) configured to perform corresponding operations without executing software or firmware.

[0080] The machine-readable instructions described herein may be stored in one or more of a compressed format, an encrypted format, a segmented format, a packaged format, and the like. The machine-readable instructions described herein may be stored as data (e.g., portions of instructions, codes, code representations, and the like) that may be used to create, make, and / or generate machine-executable instructions. For example, the machine-readable instructions may be segmented and stored on one or more storage devices and / or computing devices (e.g., servers). The machine-readable instructions may require one or more of installation, modification, adaptation, updating, combination, supplementation, configuration, decryption, decompression, unpacking, distribution, redistribution, and the like so that they may be directly read and / or executed by a computing device and / or other machine. For example, the machine-readable instructions may be stored in a plurality of portions that are individually compressed, encrypted, and stored on separate computing devices, wherein the portions, when decrypted, decompressed, and combined, form a set of executable instructions that implement a program such as described herein. In another example, the machine-readable instructions may be stored in a state that is readable by a computer, but require the addition of a library (e.g., a dynamic link library (DLL)), a software development kit (SDK), an application programming interface (API), etc., in order to execute the instructions on a particular computing device or other device. In another example, the machine-readable instructions and / or corresponding programs may need to be configured (e.g., stored settings, data inputs, recorded network addresses, etc.) before they can be executed in whole or in part. Therefore, the disclosed machine-readable instructions and / or corresponding programs are intended to cover such machine-readable instructions and / or programs, regardless of the specific format or state of the machine-readable instructions and / or programs when stored or otherwise at rest or transmitted.

[0081] As mentioned above, Figures 12 to 16 The example processing of can be implemented using executable instructions (e.g., computer and / or machine readable instructions) stored on a non-transitory computer and / or machine readable medium (such as a hard drive, flash memory, read-only memory, cache, random access memory, and / or any other storage device or storage disk) where information is stored for any duration (e.g., an extended period of time, permanently, for a short period of time, temporarily buffered, and / or cached information). As used herein, the term "non-transitory computer readable medium" is expressly defined to include any type of computer readable storage device and / or storage disk, and does not include propagating signals and does not include transmission media.

[0082] "Include" and "comprising" (and all their forms and tenses) are used herein as open-ended terms. Thus, whenever a claim adopts any form of "includes" or "comprising" (e.g., comprises, includes, comprising, including, having, etc.) as a preamble or within any kind of claim recitation, it should be understood that additional elements, items, etc. may be present without exceeding the scope of the corresponding claim or recitation. As used herein, when the phrase "at least" is used as a transitional term, such as in the preamble of a claim, it is open-ended in the same manner as the terms "include" and "comprising" are open-ended. The term "and / or" when used in the form of, for example, A, B, and / or C, refers to any combination or subset of A, B, C, such as (1) A alone, (2) B alone, (3) C alone, (4) A and B, (5) A and C, (6) B and C, and (7) A and B and C. As used herein in the context of describing structures, components, items, objects, and / or things, the phrase “at least one of A and B” is intended to refer to implementations that include any of (1) at least one A, (2) at least one B, and (3) at least one A and at least one B. Similarly, as used herein in the context of describing structures, components, items, objects, and / or things, the phrase “at least one of A or B” is intended to refer to implementations that include any of (1) at least one A, (2) at least one B, and (3) at least one A and at least one B.

[0083] Fig.12 It means that it is used for Fig.11 Flowchart of an example method 1200 of implementing a startup protocol and / or process for the control system 1100 . Fig.12 The method 1200 begins with the control system 1100 determining whether to initiate a startup operation (e.g., a startup, preheating, and / or cooking protocol, process, sequence, and / or method) of the pellet grill 100 (block 1202). For example, the control system 1100 may receive (e.g., via the user interface 116) one or more inputs, signals, commands, and / or instructions indicating that a startup operation of the pellet grill 100 is to be initiated. If the control system 1100 determines at block 1202 not to initiate a startup operation of the pellet grill 100, then Fig.12 The method 1200 remains at block 1202. Alternatively, if the control system 1100 determines at block 1202 that a startup operation of the pellet grill 100 is to be initiated, then Fig.12 Method 1200 proceeds to box 1204.

[0084] At block 1204, controller 1110 instructs (e.g., via one or more signals and / or instructions generated by controller 1110) timer 1106 of control system 1100 to initiate and / or begin measuring and / or maintaining elapsed time. In some examples, timer 1106 is reset prior to and / or in conjunction with execution of block 1204, such that when timer 1106 is started, the value of elapsed time measured and / or maintained by timer 1106 is zero. After block 1204, Fig.12 Method 1200 proceeds to box 1206.

[0085] At block 1206, the controller 1110 commands (e.g., via one or more signals and / or instructions generated by the controller 1110) the auger motor 512 of the engine 500 to rotate the auger 510 of the engine 500 to add the particulate fuel to the burn pot 514 of the engine 500. In some examples, the controller 1110 commands the auger motor 512 of the engine 500 to rotate the engine auger 510 for a predetermined period of time corresponding to a desired amount of particulate fuel to be added to the burn pot 514 of the engine 500. In some examples, the controller 1110 additionally commands (e.g., via one or more signals and / or instructions generated by the controller 1110) the fan 516 of the engine 500 to operate for a predetermined period of time (e.g., in a continuous or pulsed manner). After block 1206, Fig.12 Method 1200 proceeds to box 1208.

[0086] At block 1208, the controller 1110 commands (e.g., via one or more signals and / or instructions generated by the controller 1110) the igniter 704 of the engine 500 to activate. In some examples, the controller 1110 commands the igniter 704 of the engine 500 to activate for a predetermined period of time. After block 1208, Fig.12 Method 1200 proceeds to box 1210.

[0087] At block 1210, controller 1110 instructs (e.g., via one or more signals and / or instructions generated by controller 1110) counter 1108 of control system 1100 to increment an activation count counted and / or maintained by counter 1108, whereby the activation count corresponds to the number of activations of igniter 704. In some examples, upon executing Fig.12 Prior to method 1200, counter 1108 is reset so that when block 1210 of method 1200 is executed for the first time, the activation count counted and / or maintained by counter 1108 has a specified value (e.g., 0). After block 1210, Fig.12 Method 1200 proceeds to box 1212.

[0088] At block 1212, the controller 1110 determines whether the timer 1106 has expired. For example, the controller 1110 may determine whether the elapsed time measured and / or maintained by the timer 1106 has reached and / or exceeded a threshold duration. If the controller 1110 determines at block 1312 that the timer 1106 has not expired (e.g., the elapsed time has not reached and / or exceeded the threshold duration), then Fig.12 The method 1200 remains at block 1212. Alternatively, if the controller 1110 determines at block 1212 that the timer 1106 has expired (eg, the elapsed time has reached and / or exceeded a threshold duration), then Fig.12 Method 1200 proceeds to box 1214.

[0089] At block 1214, the controller 1110 determines whether the temperature within the cooking chamber 402 has reached and / or exceeded the threshold temperature. For example, the controller 1110 may determine that the temperature within the cooking chamber 402 has increased to or exceeded the threshold temperature between the start (block 1204) and expiration (block 1212) of the timer 1106 based on data sensed and / or measured by the temperature sensor 1104 of the control system 1100 when the timer 1106 is operating. If the controller 1110 determines at block 1214 that the temperature within the cooking chamber 402 has not reached and / or exceeded the threshold temperature, then Fig.12 Method 1200 proceeds to block 1216. Alternatively, if controller 1110 determines at block 1214 that the temperature within cooking chamber 402 has reached and / or exceeded the threshold temperature, then Fig.12 Method 1200 ends.

[0090] At block 1216, the controller 1110 determines whether the counter 1108 has reached and / or exceeded a threshold activation count. For example, the controller 1110 may determine whether the activation count counted and / or maintained by the counter 1108 has reached and / or exceeded a threshold activation count. If the controller 1110 determines at block 1216 that the counter 1108 has not reached and / or exceeded the threshold activation count, then Fig.12 The method 1200 returns to block 1204. Alternatively, if the controller 1110 determines at block 1216 that the counter 1108 has reached and / or exceeded the threshold activation count, then Fig.12 Method 1200 proceeds to box 1218.

[0091] At block 1218, the controller 1110 generates one or more notifications and / or alarms indicating that the startup operation of the pellet grill 100 has failed. In some examples, the notifications and / or alarms generated by the controller 1110 at block 1218 are only Fig.11After the controller 1110 and / or, more generally, the control system 1100 attempts at least once to re-ignite the pellet fuel located in the combustion can 514 of the engine 500 by reactivating the igniter 704 of the engine 500. After block 1218, Fig.12 Method 1200 proceeds to box 1220.

[0092] At block 1220, the controller 1110 causes the generated notification and / or alert (e.g., generated at block 1218) to be presented locally at the user interface 116 of the pellet grill 100. At block 1220, the controller 1110 may additionally or alternatively wirelessly transmit the generated notification and / or alert (e.g., generated at block 1218) from the pellet grill 100 to a remote device (e.g., a cloud server, a smartphone, a tablet, a laptop, a personal computer, etc.) for presentation and / or analysis thereon. After block 1220, Fig.12 Method 1200 proceeds to box 1222.

[0093] At block 1222, the controller 1110 initiates a shutdown operation (e.g., a shutdown protocol, process, sequence, and / or method) that causes the engine 500 of the pellet grill 100 and / or, more generally, the control system 1100 to cease operation. Fig.12 Method 1200 ends.

[0094] Fig.13 It means that it is used for Fig.11 Flowchart of an example method 1300 of implementing a flameout detection protocol and / or process for the control system 1100 . Fig.13 Method 1300 begins with controller 1110 of control system 1100 determining whether a flameout condition of engine 500 of pellet grill 100 has been detected (block 1302). For example, controller 1110 may determine that a flameout condition (e.g., an unexpected cessation of fuel combustion) has occurred, which may be indicated by a temperature of cooking chamber 402 continuing to drop over a period of time while auger 510 of engine 500 is actively attempting to feed and / or supply pellet fuel to burner can 514 of engine 500. In some examples, a flameout condition is detected based on data sensed, measured, and / or detected by temperature sensor 1104 of control system 1100. If controller 1110 determines at block 1302 that a flameout condition of engine 500 has not been detected, then Fig.13 The method 1300 remains at box 1302. Alternatively, if the controller 1110 determines at box 1302 that a flameout condition of the engine 500 has been detected, then Fig.13 Method 1300 proceeds to box 1304.

[0095] At block 1304, the controller 1110 instructs (e.g., via one or more signals and / or instructions generated by the controller 1110) the timer 1106 of the control system 1100 to initiate and / or begin measuring and / or maintaining elapsed time. In some examples, the timer 1106 is reset prior to and / or in conjunction with executing block 1304 so that when the timer 1106 is started, the value of the elapsed time measured and / or maintained by the timer 1106 is zero. After block 1304, Fig.13 Method 1300 proceeds to box 1306.

[0096] At block 1306, the controller 1110 commands (e.g., via one or more signals and / or instructions generated by the controller 1110) the auger motor 512 of the engine 500 to rotate the auger 510 of the engine 500 to add the particulate fuel to the burn pot 514 of the engine 500. In some examples, the controller 1110 commands the auger motor 512 of the engine 500 to rotate the engine auger 510 for a predetermined period of time corresponding to a desired amount of particulate fuel to be added to the burn pot 514 of the engine 500. In some examples, the controller 1110 additionally commands (e.g., via one or more signals and / or instructions generated by the controller 1110) the fan 516 of the engine 500 to operate for a predetermined period of time (e.g., in a continuous or pulsed manner). After block 1306, Fig.13 Method 1300 proceeds to box 1308.

[0097] At block 1308, the controller 1110 commands (e.g., via one or more signals and / or instructions generated by the controller 1110) the igniter 704 of the engine 500 to activate. In some examples, the controller 1110 commands the igniter 704 of the engine 500 to activate for a predetermined period of time. After block 1308, Fig.13 Method 1300 proceeds to box 1310.

[0098] At block 1310, controller 1110 instructs (e.g., via one or more signals and / or instructions generated by controller 1110) counter 1108 of control system 1100 to increment an activation count counted and / or maintained by counter 1108, whereby the activation count corresponds to the number of activations of igniter 704. In some examples, upon executing Fig.13 Prior to method 1300, counter 1108 is reset so that when block 1310 of method 1300 is executed for the first time, the activation count counted and / or maintained by counter 1108 has a specified value (e.g., 0 or 1). After block 1310, Fig.13 Method 1300 proceeds to box 1312.

[0099] At block 1312, the controller 1110 determines whether the timer 1106 has expired. For example, the controller 1110 may determine whether the elapsed time measured and / or maintained by the timer 1106 has reached and / or exceeded a threshold duration. If the controller 1110 determines at block 1312 that the timer 1106 has not expired (e.g., the elapsed time has not reached and / or exceeded the threshold duration), then Fig.13 The method 1300 remains at block 1312. Alternatively, if the controller 1110 determines at block 1312 that the timer 1106 has expired (eg, the elapsed time has reached and / or exceeded a threshold duration), then Fig.13 Method 1300 proceeds to box 1314.

[0100] At block 1314, the controller 1110 determines whether the temperature within the cooking chamber 402 has increased since the flameout condition was first detected at block 1302. For example, the controller 1110 may determine that the temperature within the cooking chamber 402 has increased between the start (block 1304) and expiration (block 1312) of the timer 1106 based on data sensed and / or measured by the temperature sensor 1104 of the control system 1100 when the timer 1106 is operating. If the controller 1110 determines at block 1314 that the temperature within the cooking chamber 402 has not increased, then Fig.13 The method 1300 proceeds to block 1316. Alternatively, if the controller 1110 determines at block 1314 that the temperature within the cooking chamber 402 has increased, then Fig.13 Method 1300 ends.

[0101] At block 1316, the controller 1110 determines whether the counter 1108 has reached and / or exceeded a threshold activation count. For example, the controller 1110 may determine whether the activation count counted and / or maintained by the counter 1108 has reached and / or exceeded a threshold activation count. If the controller 1110 determines at block 1316 that the counter 1108 has not reached and / or exceeded the threshold activation count, then Fig.13 The method 1300 returns to block 1304. Alternatively, if the controller 1110 determines at block 1316 that the counter 1108 has reached and / or exceeded the threshold activation count, then Fig.13 Method 1300 proceeds to box 1318.

[0102] At block 1318, the controller 1110 generates one or more notifications and / or alarms indicating that the flameout condition has not been remedied. In some examples, the notifications and / or alarms generated by the controller 1110 at block 1318 are only Fig.11After the controller 1110 and / or, more generally, the control system 1100 attempts at least once to re-ignite the pellet fuel located in the combustion can 514 of the engine 500 by reactivating the igniter 704 of the engine 500. After block 1318, Fig.13 Method 1300 proceeds to box 1320.

[0103] At block 1320, the controller 1110 causes the generated notification and / or alert (e.g., generated at block 1318) to be presented locally at the user interface 116 of the pellet grill 100. At block 1320, the controller 1110 may additionally or alternatively wirelessly transmit the generated notification and / or alert (e.g., generated at block 1318) from the pellet grill 100 to a remote device (e.g., a cloud server, a smartphone, a tablet, a laptop, a personal computer, etc.) for presentation and / or analysis thereon. After block 1320, Fig.13 Method 1300 proceeds to box 1322.

[0104] At block 1322, the controller 1110 initiates a shutdown operation (e.g., a shutdown protocol, process, sequence, and / or method) that causes the engine 500 of the pellet grill 100 and / or, more generally, the control system 1100 to cease operation. Fig.13 Method 1300 ends.

[0105] Fig.14A and Fig. 14B It means that it is used for Fig.11 Flowchart of an example method 1400 of implementing another ignition-based protocol and / or process by the control system 1100 . Fig.14A and Fig. 14B The method 1400 begins with the control system 1100 determining whether to initiate a startup operation (e.g., a startup, preheating, and / or cooking protocol, process, sequence, and / or method) of the pellet grill 100 (block 1402). For example, the control system 1100 may receive (e.g., via the user interface 116) one or more inputs, signals, commands, and / or instructions indicating that a startup operation of the pellet grill 100 is to be initiated. If the control system 1100 determines at block 1402 not to initiate a startup operation of the pellet grill 100, then Fig.14A and Fig. 14B Method 1400 remains at block 1402. Alternatively, if control system 1100 determines at block 1402 that a startup operation of pellet grill 100 is to be initiated, then Fig.14A and Fig. 14B Method 1400 proceeds to box 1404.

[0106] At block 1404, the controller 1110 determines a starting temperature within the cooking chamber 402. For example, the controller 1110 may determine a starting temperature within the cooking chamber 402 based on data sensed and / or measured by the temperature sensor 1104 of the control system 1100 when the startup operation is initiated. Fig.14A and Fig. 14B Method 1400 proceeds to box 1406.

[0107] At box 1406, the controller 1110 commands (e.g., via one or more signals and / or instructions generated by the controller 1110) the engine 500 to operate in the first state for a first duration measured by the timer 1106. In some examples, the first duration is approximately two hundred seconds. In other examples, the first duration can have a different value (e.g., greater than or less than two hundred seconds). In some examples, the first state is a first preheating phase. In some examples, the controller 1110 commands the engine 500 to operate in the first state by: (a) commanding the auger motor 512 of the engine 500 to rotate the auger 510 of the engine 500 to add pellet fuel to the burner can 514 of the engine 500; (b) commanding the fan 516 of the engine 500 to operate (e.g., at a low speed and in a pulsed manner); and (c) activating the engine's igniter 704. After box 1406, Fig.14A and Fig. 14B Method 1400 proceeds to box 1408.

[0108] At box 1408, the controller 1110 commands (e.g., via one or more signals and / or instructions generated by the controller 1110) the engine 500 to operate in the second state for a second duration measured by the timer 1106. In some examples, the second duration is approximately ninety seconds. In other examples, the second duration can have a different value (e.g., greater than or less than ninety seconds). In some examples, the second state is a second warm-up phase. In some examples, the controller 1110 commands the engine 500 to operate in the second state by: (a) commanding the auger motor 512 of the engine 500 to stop rotating the auger 510 of the engine 500; (b) commanding the fan 516 of the engine 500 to operate (e.g., at a low speed and in a continuous manner); and (c) activating the engine's igniter 704. After box 1408, Fig.14A and Fig. 14B Method 1400 proceeds to box 1410.

[0109] At box 1410, the controller 1110 commands (e.g., via one or more signals and / or instructions generated by the controller 1110) the engine 500 to operate in the third state for a third duration measured by the timer 1106. In some examples, the third duration is approximately thirty seconds. In other examples, the third duration can have a different value (e.g., greater than or less than thirty seconds). In some examples, the third state is a third warm-up phase. In some examples, the controller 1110 commands the engine 500 to operate in the second state by: (a) commanding the auger motor 512 of the engine 500 to stop rotating the auger 510 of the engine 500; (b) commanding the fan 516 of the engine 500 to operate (e.g., at normal speed and in a continuous manner); and (c) deactivating the engine's igniter 704. After box 1410, Fig.14A and Fig. 14B Method 1400 proceeds to box 1412.

[0110] At block 1412, the controller 1110 determines the current temperature within the cooking chamber 402. For example, the controller 1110 may determine the current temperature within the cooking chamber 402 based on data sensed and / or measured by the temperature sensor 1104 of the control system 1100 at and / or around the time of executing and / or performing block 1412 of the method 1400. Fig.14A and Fig. 14B Method 1400 proceeds to box 1414.

[0111] At block 1414, the controller 1110 determines a temperature difference calculated by subtracting the starting temperature (e.g., determined at block 1404) from the current temperature (e.g., determined at block 1412). Fig.14A and Fig. 14B Method 1400 proceeds to box 1416.

[0112] At block 1416, the controller 1110 determines whether the temperature difference exceeds a threshold temperature difference. In some examples, the threshold temperature difference is approximately 18 degrees Fahrenheit. In other examples, the threshold temperature difference may have a different value (e.g., greater than or less than 18 degrees Fahrenheit). If the controller 1110 determines at block 1416 that the temperature difference exceeds the threshold temperature difference, then Fig.14A and Fig. 14B Method 1400 proceeds to block 1418. Alternatively, if controller 1110 determines at block 1416 that the temperature difference does not exceed the threshold temperature difference, then Fig.14A And the method 1400 of Figure 14 proceeds to box 1424.

[0113] At block 1418, the controller 1110 commands (e.g., via one or more signals and / or instructions generated by the controller 1110) the engine 500 to operate based on and / or according to a proportional-integral-derivative (PID) control loop. Fig.14A and Fig. 14B Method 1400 proceeds to box 1420.

[0114] At block 1420, the control system 1100 determines whether to initiate a shutdown operation (e.g., a shutdown protocol, process, sequence, and / or method) of the pellet grill 100. For example, the control system 1100 may receive (e.g., via the user interface 116) one or more inputs, signals, commands, and / or instructions indicating that a shutdown operation of the pellet grill 100 is to be initiated. If the control system 1100 determines at block 1420 that a shutdown operation of the pellet grill 100 is not to be initiated, then Fig.14A and Fig. 14B The method 1400 remains at block 1420. Alternatively, if the control system 1100 determines at block 1420 that a shutdown operation of the pellet grill 100 is to be initiated, then Fig.14A and Fig. 14B Method 1400 proceeds to box 1422.

[0115] At block 1422, the controller 1110 initiates a shutdown operation (e.g., a shutdown protocol, process, sequence, and / or method) to deactivate the engine 500 of the pellet grill 100 and / or, more generally, the control system 1100. After block 1422, Fig.14A and Fig. 14B Method 1400 ends.

[0116] At block 1424, the controller 1110 instructs (e.g., via one or more signals and / or instructions generated by the controller 1110) the auger motor 512 of the engine 500 to rotate the auger 510 of the engine 500 to add the pellet fuel to the burner canister 514 of the engine 500. For example, the controller 1110 may instruct the auger motor 512 of the engine 500 to rotate the auger 510 of the engine 500 at a low speed (e.g., a minimum speed). After block 1424, Fig.14A and Fig. 14B Method 1400 proceeds to box 1426.

[0117] At block 1426, the controller 1110 determines whether the temperature difference fails to exceed the threshold temperature difference within a fourth duration measured by the timer 1106. In some examples, the fourth duration is approximately five minutes. In other examples, the fourth duration may have a different value (e.g., greater than or less than five minutes). If the controller 1110 determines at block 1426 that the temperature difference exceeds the threshold temperature difference within the fourth duration, then Fig.14A and Fig. 14B The method 1400 returns to block 1412. Alternatively, if the controller 1110 determines at block 1426 that the temperature difference has failed to exceed the threshold temperature difference within the fourth duration, then Fig.14A And the method 1400 of Figure 14 proceeds to box 1428.

[0118] At block 1428, the controller 1110 commands (e.g., via one or more signals and / or instructions generated by the controller 1110) the igniter 704 of the engine 500 to activate (e.g., reactivate). Fig.14A and Fig. 14B Method 1400 proceeds to box 1430.

[0119] At block 1430, the controller 1110 determines whether the temperature difference fails to exceed the threshold temperature difference within a fifth duration measured by the timer 1106. In some examples, the fifth duration is approximately 7 minutes. In other examples, the fifth duration may have a different value (e.g., greater than or less than seven minutes) that exceeds the value of the fourth duration described above. If the controller 1110 determines at block 1430 that the temperature difference exceeds the threshold temperature difference within the fifth duration, then Fig.14A and Fig. 14B The method 1400 returns to block 1412. Alternatively, if the controller 1110 determines at block 1430 that the temperature difference has failed to exceed the threshold temperature difference within the fifth duration, then Fig.14A And the method 1400 of Figure 14 proceeds to box 1432.

[0120] At block 1432, the controller 1110 commands (eg, via one or more signals and / or instructions generated by the controller 1110) that the igniter 704 of the engine 500 be deactivated. Fig.14A and Fig. 14B Method 1400 proceeds to box 1434.

[0121] At block 1434, the controller 1110 determines whether the temperature difference fails to exceed the threshold temperature difference within a sixth duration measured by the timer 1106. In some examples, the sixth duration is approximately 15 minutes. In other examples, the sixth duration may have a different value (e.g., greater than or less than 15 minutes) that exceeds the value of the fifth duration described above. If the controller 1110 determines at block 1434 that the temperature difference exceeds the threshold temperature difference within the sixth duration, then Fig.14A and Fig. 14B The method 1400 returns to block 1412. Alternatively, if the controller 1110 determines at block 1430 that the temperature difference has failed to exceed the threshold temperature difference within the sixth duration, then Fig.14A And the method 1400 of Figure 14 proceeds to box 1436.

[0122] At block 1436, the controller 1110 generates one or more notifications and / or alarms indicating that the startup operation of the pellet grill 100 has failed. In some examples, the notifications and / or alarms generated by the controller 1110 at block 1436 are only Fig.11 After the controller 1110 and / or, more generally, the control system 1100 attempts at least once to re-ignite the pellet fuel located in the combustion can 514 of the engine 500 by reactivating the igniter 704 of the engine 500. After block 1436, Fig.14A and Fig. 14B Method 1400 proceeds to box 1438.

[0123] At block 1438, the controller 1110 causes the generated notification and / or alert (e.g., generated at block 1436) to be presented locally at the user interface 116 of the pellet grill 100. At block 1438, the controller 1110 may additionally or alternatively wirelessly transmit the generated notification and / or alert (e.g., generated at block 1436) from the pellet grill 100 to a remote device (e.g., a cloud server, a smartphone, a tablet, a laptop, a personal computer, etc.) for presentation and / or analysis thereon. After block 1438, Fig.14A and Fig. 14B Method 1400 proceeds to box 1440.

[0124] At block 1440, the controller 1110 initiates a shutdown operation (e.g., a shutdown protocol, process, sequence, and / or method) that causes the engine 500 of the pellet grill 100 and / or, more generally, the control system 1100 to cease operation. Fig.14A and Fig. 14B Method 1400 ends.

[0125] FIG. 15A to FIG. 15C It means that it is used for Fig.11 A flow chart of an example method for implementing another ignition-based protocol and / or process in a control system. FIG. 15A to FIG. 15C The method 1500 begins with the control system 1100 determining whether to initiate a cooking operation (e.g., a cooking protocol, process, sequence, and / or method) of the pellet grill 100 (block 1502). For example, the control system 1100 may receive (e.g., via the user interface 116) one or more inputs, signals, commands, and / or instructions indicating that a cooking operation of the pellet grill 100 is to be initiated. As another example, the control system 1100 may determine that a cooking operation is to be initiated in response to the control system 1100 successfully completing a startup and / or preheating operation of the pellet grill 100. If the control system 1100 determines at block 1502 not to initiate a cooking operation of the pellet grill 100, then FIG. 15A to FIG. 15C The method 1500 remains at block 1502. Alternatively, if the control system 1100 determines at block 1502 that a cooking operation of the pellet grill 100 is to be initiated, then FIG. 15A to FIG. 15C Method 1500 proceeds to box 1504.

[0126] At block 1504, the controller 1110 commands (e.g., via one or more signals and / or instructions generated by the controller 1110) the timer 1106 of the control system 1100 to reset so that when the timer 1106 is started, the value of any elapsed time measured and / or maintained by the timer 1106 is zero. FIG. 15A to FIG. 15C Method 1500 proceeds to box 1506.

[0127] At block 1506, the controller 1110 instructs (e.g., via one or more signals and / or instructions generated by the controller 1110) the timer 1106 to initiate and / or begin measuring and / or maintaining elapsed time. FIG. 15A to FIG. 15C Method 1500 proceeds to box 1508.

[0128] At block 1508, the controller 1110 determines the current temperature within the cooking chamber 402 and records the current temperature as the previous temperature. For example, the controller 1110 may determine the current temperature within the cooking chamber 402 based on data sensed and / or measured by the temperature sensor 1104 of the control system 1100 at and / or around the time of executing and / or performing block 1508 of the method 1500, and may thereafter record the current temperature (e.g., via the memory 1112) as the previous temperature. After block 1508, FIG. 15A to FIG. 15C Method 1500 proceeds to box 1510.

[0129] At block 1510, controller 1110 determines whether timer 1106 has expired. For example, controller 1110 may determine whether the elapsed time measured and / or maintained by timer 1106 has reached and / or exceeded a threshold duration. In some examples, the threshold duration is approximately sixty seconds. In other examples, the threshold duration may have a different value (e.g., greater than or less than sixty seconds). If controller 1110 determines at block 1510 that timer 1106 has not expired (e.g., the elapsed time has not reached and / or exceeded the threshold duration), then FIG. 15A to FIG. 15C The method 1500 remains at block 1510. Alternatively, if the controller 1110 determines at block 1510 that the timer 1106 has expired (eg, the elapsed time has reached and / or exceeded the threshold duration), then FIG. 15A to FIG. 15C Method 1500 proceeds to box 1512.

[0130] At block 1512, the controller 1110 determines the current temperature within the cooking chamber 402. For example, the controller 1110 may determine the current temperature within the cooking chamber 402 based on data sensed and / or measured by the temperature sensor 1104 of the control system 1100 at and / or around the time when block 1512 of the method 1500 is executed and / or performed. FIG. 15A to FIG. 15C Method 1500 proceeds to box 1514.

[0131] At block 1514, the controller 1110 determines whether the cooking operation being implemented by the pellet grill's control system 1100 is a searing operation. For example, the control system 1100 may receive (e.g., via the user interface 116) one or more inputs, signals, commands, and / or instructions indicating that the cooking operation is a searing operation (e.g., as opposed to a different type of cooking operation, such as a smoking operation). As another example, the control system 1100 may determine that the cooking operation is a searing operation based on a value (e.g., a relatively high value) of a temperature set point associated with the cooking operation (e.g., as opposed to a relatively low value of a temperature set point associated with a different type of cooking operation, such as a smoking operation). If the controller 1110 determines at block 1514 that the cooking operation is a searing operation, then FIG. 15A to FIG. 15C Method 1500 proceeds to block 1516. Alternatively, if controller 1110 determines at block 1514 that the cooking operation is not a searing operation, then FIG. 15A to FIG. 15C Method 1500 proceeds to box 1520.

[0132] At block 1516, the controller 1110 determines whether the current temperature of the cooking chamber 402 is less than a threshold sear temperature. For example, the controller 1110 may determine that the current temperature of the cooking chamber 402 (e.g., determined at block 1512) is less than the threshold sear temperature. If the controller 1110 determines at block 1516 that the current temperature of the cooking chamber 402 is less than the threshold sear temperature, then FIG. 15A to FIG. 15C Method 1500 proceeds to block 1518. Alternatively, if controller 1110 determines at block 1516 that the current temperature of cooking chamber 402 is not below the threshold searing temperature, then FIG. 15A to FIG. 15C Method 1500 proceeds to box 1522.

[0133] At block 1518, the controller 1110 instructs (e.g., via one or more signals and / or instructions generated by the controller 1110) the counter 1108 of the control system 1100 to increase the fault count being counted and / or maintained by the counter 1108. After block 1518, FIG. 15A to FIG. 15C Method 1500 proceeds to box 1524.

[0134] At block 1520, the controller 1110 determines whether the previous temperature of the cooking chamber 402 is greater than the current temperature of the cooking chamber 402. For example, the controller 1110 may determine that the previous temperature of the cooking chamber 402 (e.g., determined at block 1508) is greater than the current temperature of the cooking chamber 402 (e.g., determined at block 1512). If the controller 1110 determines at block 1520 that the previous temperature of the cooking chamber 402 is not greater than the current temperature of the cooking chamber 402, then FIG. 15A to FIG. 15C Method 1500 proceeds to block 1522. Alternatively, if controller 1110 determines at block 1520 that the previous temperature of cooking chamber 402 is greater than the current temperature of cooking chamber 402, then FIG. 15A to FIG. 15C Method 1500 returns to box 1518.

[0135] At block 1522, the controller 1110 instructs (e.g., via one or more signals and / or instructions generated by the controller 1110) the counter 1108 to decrement the fault count being counted and / or maintained by the counter 1108. After block 1522, FIG. 15A to FIG. 15C Method 1500 proceeds to box 1524.

[0136] At block 1524, the controller 1110 determines whether the fault count being counted and / or maintained by the counter 1108 is greater than or equal to a first threshold fault count. In some examples, the first threshold fault count may have a value equal to five. In other examples, the first threshold fault count may have a different value (e.g., greater than or less than five). If the controller 1110 determines at block 1524 that the fault count being counted and / or maintained by the counter 1108 is greater than or equal to the first threshold fault count, then FIG. 15A to FIG. 15C Method 1500 proceeds to block 1526. Alternatively, if controller 1110 determines at block 1524 that the fault count being counted and / or maintained by counter 1108 is not greater than or equal to the first threshold fault count, then FIG. 15A to FIG. 15C Method 1500 returns to box 1504.

[0137] At block 1526, the controller 1110 blocks all set points (e.g., any set points associated with a cooking operation). In some examples, the controller 1110 maintains the set point blocking operation implemented at block 1526 until the fault count being counted and / or maintained by the counter 1108 returns to a value less than the first threshold fault count. After block 1526, FIG. 15A to FIG. 15C Method 1500 proceeds to box 1528.

[0138] At block 1528, the controller 1110 enables presentation of an error flag (e.g., a temperature drop error flag, a flameout condition error flag, etc.) via the user interface 116 of the control system 1100 of the pellet grill 100. In some examples, the controller 1110 may cause the enabled error flag to be presented locally at the user interface 116 of the pellet grill 100. In other examples, the controller 1110 may additionally or alternatively cause the enabled error flag to be wirelessly transmitted from the pellet grill 100 to a remote device (e.g., a cloud server, a smartphone, a tablet, a laptop, a personal computer, etc.) for presentation and / or analysis thereon.

[0139] At block 1530, the controller 1110 determines whether the fault count being counted and / or maintained by the counter 1108 is greater than or equal to a second threshold fault count. In some examples, the second threshold fault count may have a value equal to six. In other examples, the second threshold fault count may have a different value (e.g., greater than or less than six) that is greater than the first threshold fault count. If the controller 1110 determines at block 1530 that the fault count being counted and / or maintained by the counter 1108 is greater than or equal to the second threshold fault count, then FIG. 15A to FIG. 15CMethod 1500 proceeds to block 1532. Alternatively, if controller 1110 determines at block 1530 that the fault count being counted and / or maintained by counter 1108 is not greater than or equal to the second threshold fault count, then FIG. 15A to FIG. 15C Method 1500 proceeds to box 1534.

[0140] At block 1532, the controller 1110 disables the re-ignition subroutine. Fig.16 Further description can be obtained by Fig.11 The control system 1100 in conjunction with block 1532 and / or, more generally, in conjunction with FIG. 15A to FIG. 15C An example re-ignition subroutine implemented by method 1500 of FIG. 1532 is shown in FIG. FIG. 15A to FIG. 15C Method 1500 returns to box 1504.

[0141] At block 1534, the controller 1110 enables the re-ignition subroutine. Fig.16 Further description can be obtained by Fig.11 The control system 1100 combines FIG. 15A to FIG. 15C 1534 and / or, more generally, the example re-ignition subroutine implemented in conjunction with method 1500. After block 1534, FIG. 15A to FIG. 15C Method 1500 proceeds to box 1536.

[0142] At block 1536, the controller 1110 determines whether the fault count being counted and / or maintained by the counter 1108 is greater than or equal to a third threshold fault count. In some examples, the third threshold fault count may have a value equal to twenty. In other examples, the third threshold fault count may have a different value (e.g., greater than or less than twenty) that is greater than the second threshold fault count. If the controller 1110 determines at block 1536 that the fault count being counted and / or maintained by the counter 1108 is greater than or equal to the third threshold fault count, then FIG. 15A to FIG. 15C Method 1500 proceeds to block 1538. Alternatively, if controller 1110 determines at block 1536 that the fault count being counted and / or maintained by counter 1108 is not greater than or equal to the third threshold fault count, then FIG. 15A to FIG. 15C Method 1500 returns to box 1504.

[0143] At block 1538, the controller 1110 initiates a shutdown operation (e.g., a shutdown protocol, process, sequence, and / or method) that causes the engine 500 and / or, more generally, the control system 1100 of the pellet grill 100 to cease operation. FIG. 15A to FIG. 15C The method 1500 ends.

[0144] Fig.16 is used through Fig.11Flowchart of an example method 1600 of implementing a re-ignition subroutine for the control system 1100 . Fig.16 The method 1600 may be combined with the above-described FIG. 15A to FIG. 15C Method 1500 is implemented. Fig.16 The method 1600 begins with the controller 1110 of the control system 1100 determining whether the re-ignition subroutine has been enabled (block 1602). For example, the controller 1110 may perform the above-described FIG. 15A to FIG. 15C The controller 1110 determines at block 1602 that the re-ignition subroutine is enabled. Fig.16 Method 1600 remains at box 1602. Alternatively, if the control system 1100 determines at box 1602 that the ignition subroutine has been enabled, then Fig.16 Method 1600 proceeds to box 1604.

[0145] At block 1604, the controller 1110 commands (e.g., via one or more signals and / or instructions generated by the controller 1110) the igniter 704 of the engine 500 to activate for a first duration measured by the timer 1106. In some examples, the first duration is approximately one hundred and eighty seconds. In other examples, the first duration may have a different value (e.g., greater than or less than one hundred and eighty seconds). After block 1604, Fig.16 Method 1600 proceeds to box 1606.

[0146] At block 1606, the controller 1110 commands (e.g., via one or more signals and / or instructions generated by the controller 1110) that the igniter 704 of the engine 500 be deactivated for a second duration measured by the timer 1106. In some examples, the second duration is approximately sixty seconds. In other examples, the second duration may have a different value (e.g., greater than or less than sixty seconds). After block 1606, Fig.16 Method 1600 proceeds to box 1608.

[0147] At block 1608, the controller 1110 of the control system 1100 determines whether the re-ignition subroutine has been disabled (block 1608). For example, the controller 1110 may perform the above-described FIG. 15A to FIG. 15C If the controller 1110 determines at block 1608 that the re-ignition subroutine is not disabled, then Fig.16 Method 1600 returns to box 1404. Alternatively, if the control system 1100 determines at box 1608 that the ignition subroutine has been disabled, then Fig.16Method 1600 proceeds to box 1610.

[0148] At block 1610, the controller 1110 commands (eg, via one or more signals and / or instructions generated by the controller 1110) that the igniter 704 of the engine 500 be deactivated. Fig.16 Method 1600 ends.

[0149] Although certain example methods, apparatus, and articles of manufacture are disclosed herein, the scope of coverage of this patent is not limited thereto. On the contrary, this patent covers all methods, apparatus, and articles of manufacture fairly falling within the scope of the claims of this patent.

Claims

1. A pellet grill, comprising: Cooking room; Burning cans; an igniter extending into the burn pot and configured to ignite particulate fuel within the burn pot; as well as A controller, the controller being configured to: commanding the igniter to activate during a first duration; after expiration of the first duration, determining whether a temperature of the cooking chamber has reached a threshold temperature; in response to determining that the temperature has not reached the threshold temperature, commanding the igniter to be activated during a second duration; commanding a counter to increment an activation count in response to a respective activation of the igniter; determining whether the activation count has reached a threshold activation count; as well as In response to determining that the activation count has reached the threshold activation count, a notification is generated indicating at least one of: a startup failure associated with an engine of the pellet grill, or initiation of a shutdown operation.

2. The pellet grill according to claim 1, wherein: The igniter is a DC powered glow plug.

3. The pellet grill according to claim 1, wherein: The controller is also configured to cause the notification to be presented at a user interface of the pellet grill.

4. The pellet grill according to claim 1, wherein: The controller is also configured to cause the notification to be wirelessly transmitted from the pellet grill to a device remotely located relative to the pellet grill.

5. The pellet grill according to claim 1, wherein: The controller is also configured to, In response to determining that the activation count has reached the threshold activation count, the shut down operation associated with the engine of the pellet grill is initiated.

6. The pellet grill of claim 1, wherein: The controller is also configured to command an auger motor of the pellet grill to rotate an auger of the pellet grill during the first duration, the rotation of the auger causing pellet fuel to be added to the fire pot during the first duration.

7. A pellet grill, comprising: Cooking room; Burning cans; an igniter extending into the burn pot and configured to ignite particulate fuel within the burn pot; as well as A controller, the controller being configured to: detecting a temperature pattern of the cooking chamber corresponding to a flameout condition of the combustion pot; responsive to detecting the temperature pattern, commanding the igniter to be activated during a first duration; after expiration of the first duration, determining whether the temperature of the cooking chamber increased during the first duration; in response to determining that the temperature has not increased during the first duration, commanding the igniter to be activated during a second duration; commanding a counter to increment an activation count in response to a respective activation of the igniter; determining whether the activation count has reached a threshold activation count; as well as In response to determining that the activation count has reached a threshold activation count, a notification is generated indicating at least one of the occurrence of the flameout condition, failure to remediate the flameout condition, or initiation of a shutdown operation associated with an engine of the pellet grill.

8. The pellet grill of claim 7, wherein: The igniter is a DC powered glow plug.

9. The pellet grill of claim 7, wherein: The controller is also configured to cause the notification to be presented at a user interface of the pellet grill.

10. The pellet grill of claim 7, wherein: The controller is also configured to cause the notification to be wirelessly transmitted from the pellet grill to a device remotely located relative to the pellet grill.

11. The pellet grill of claim 7, wherein: The controller is also configured to, In response to determining that the activation count has reached the threshold activation count, the shut down operation associated with the engine of the pellet grill is initiated.

12. The pellet grill of claim 7, wherein: The controller is also configured to command an auger motor of the pellet grill to rotate an auger of the pellet grill during the first duration, the rotation of the auger causing pellet fuel to be added to the fire pot during the first duration.

13. A pellet grill, comprising: Cooking room; Burning cans; an igniter extending into the burn pot and configured to ignite particulate fuel within the burn pot; as well as A controller, the controller being configured to: determining a start-up temperature of the cooking chamber; commanding the igniter to activate during a first duration associated with a warm-up operation of an engine of the pellet grill; after expiration of the first duration, determining a current temperature of the cooking chamber; determining whether a temperature difference between the current temperature and the start temperature exceeds a threshold temperature difference; responsive to determining that the temperature difference exceeds the threshold temperature difference, determining whether the temperature difference has exceeded the threshold temperature difference for a second duration; responsive to determining that the temperature difference has exceeded the threshold temperature difference for the second duration, commanding activation of the igniter; determining whether the temperature difference has exceeded the threshold temperature difference for a third duration; as well as In response to determining that the temperature difference has exceeded the threshold temperature difference for the third duration, a notification is generated indicating at least one of: a startup failure associated with the engine of the pellet grill, or initiation of a shutdown operation.

14. The pellet grill of claim 13, wherein: The igniter is a DC powered glow plug.

15. The pellet grill of claim 13, wherein: The controller is also configured to: commanding an auger motor of the pellet grill to rotate an auger of the pellet grill during the first duration, rotation of the auger causing pellet fuel to be added to the burn pot during the first duration; and A fan of the pellet grill is commanded to rotate during the first duration.

16. The pellet grill of claim 13, wherein: The warm-up operation of the engine includes a first state and a second state different from the first state, wherein the controller is configured to command the engine to operate in the second state after the first state is completed.

17. The pellet grill of claim 13, wherein: The controller is also configured to, in response to determining that the temperature difference exceeds the threshold temperature difference, command the engine to operate according to a proportional-integral-derivative control loop.

18. The pellet grill of claim 13, wherein: The controller is also configured to cause the notification to be presented at a user interface of the pellet grill.

19. The pellet grill of claim 13, wherein: The controller is also configured to cause the notification to be wirelessly transmitted from the pellet grill to a device remotely located relative to the pellet grill.

20. A pellet grill, comprising: Cooking room; Burning cans; an igniter extending into the burn pot and configured to ignite particulate fuel within the burn pot; as well as A controller, the controller being configured to: determining a first temperature of the cooking chamber during a first duration, the first temperature being recorded as a previous temperature; After expiration of the first duration, determining a second temperature of the cooking chamber, the second temperature being recorded as a current temperature; determining whether the previous temperature is greater than the current temperature; In response to determining that the previous temperature is greater than the current temperature, commanding a counter of the pellet grill to increase a fault count; determining whether the fault count is greater than or equal to a first threshold fault count; as well as In response to determining that the fault count is not greater than or equal to the first threshold fault count, a re-ignition subroutine is enabled, wherein the controller commands the igniter to be activated in conjunction with execution of the re-ignition subroutine.

21. The pellet grill of claim 20, wherein: The igniter is a DC powered glow plug.

22. The pellet grill of claim 20, wherein: The controller is further configured to, in response to determining that the previous temperature is not greater than the current temperature, command the counter to decrement the fault count.

23. The pellet grill of claim 20, wherein: The controller is also configured to, in response to determining that the fault count is greater than or equal to the first threshold fault count, disable the re-ignition subroutine.

24. The pellet grill of claim 20, wherein: The controller is also configured to: responsive to enabling the re-ignition subroutine, determining whether the fault count is greater than or equal to a second threshold fault count, the second threshold fault count being greater than the first threshold fault count; as well as In response to determining that the fault count is greater than or equal to the second threshold fault count, a shutdown operation associated with an engine of the pellet grill is initiated.

25. The pellet grill of claim 20, wherein: The controller is also configured to: After expiration of the first duration, determining whether a control system of the pellet grill is performing a grilling operation; and In response to determining that the control system is performing the searing operation, a determination is made as to whether the current temperature is less than a threshold searing temperature.

26. The pellet grill of claim 25, wherein: The controller is further configured to, in response to determining that the current temperature is less than the threshold sear temperature, command the counter to increment the fault count.

27. The pellet grill of claim 25, wherein: The controller is further configured to, in response to determining that the current temperature is not less than the threshold sear temperature, command the counter to decrement the fault count.

Images