METHODS AND APPARATUS FOR COMMUNICATING CONTROL SIGNALS IN A GRILL

Example methods and apparatus for communicating control signals in a gas grill are disclosed herein. An example user-interface assembly for use in a grill includes control knob, knob sensor to detect a user interaction with the control knob, lighting circuitry including a plurality of light emitting diodes, and user-interface controller circuitry to identify an addressing block connected via an input wiring harness, the knob controller to select an address to be used to communicate with a central controller of the gas grill.

FIELD OF THE DISCLOSURE

This disclosure relates generally to grills and, more specifically, to methods and apparatus for communicating control signals in a grill.

BACKGROUND

Gas grills are conventionally equipped with one or more burner(s) (e.g., one or more tube(s) configured to carry combustible gas) located within a cookbox of the grill. A gas train (e.g., implemented via one or more rigid or flexible pipe(s), tube(s), and/or conduit(s)) typically extends from a fuel source (e.g., a propane tank, or a piped (e.g., household) natural gas line) associated with the grill to a manifold of the grill, and from the manifold of the grill to respective ones of the burner(s) of the grill. One or more burner valve(s) (e.g., typically corresponding in number to the number of burner(s) of the grill) is/are coupled to and operatively positioned within the gas train between the manifold and corresponding ones of the burner(s). Each burner valve is configured to be movable between a closed position that prevents gas contained within the manifold from flowing into the corresponding burner, and an open position that enables gas contained within the manifold to flow from the manifold into the corresponding burner.

In known gas grills of the type described above, each burner valve typically has a stem that extends away from the cookbox of the grill and through a control panel of the grill, with the control panel commonly being located along a front side of the cookbox of the grill. For each burner valve, a control knob is mechanically coupled to the stem of the burner valve such that manual rotation of the control knob (e.g., by a user of the grill) mechanically causes a corresponding rotation of the stem of the burner valve. Rotating the stem of the burner valve in turn causes the burner valve to move between its closed position and its open position, thereby affecting the extent and/or the rate at which gas is able to flow from the manifold of the grill, through the burner valve of the grill, and into the corresponding burner of the grill. Such known gas grills accordingly have a mechanical control architecture with regard to the relationship between the position(s) of the one or more control knob(s) of the grill and the flow of gas into the corresponding one or more burner(s) of the grill.

Certain examples are shown in the above-identified figures and described in detail below. In describing these examples, like or identical reference numbers are used to identify the same or similar elements. The figures are not necessarily to scale and certain features and certain views of the figures may be shown exaggerated in scale or in schematic for clarity and/or conciseness.

DETAILED DESCRIPTION

Conventional gas grills of the type described above have a mechanical control architecture with regard to the relationship between the position(s) of one or more control knob(s) of the grill and the flow of gas into a corresponding one or more burner(s) of the grill. In this regard, such known gas grills include one or more burner valve(s), each having a stem that extends away from a cookbox of the grill and through a control panel of the grill, with the control panel commonly being located along a front side of the cookbox of the grill. For each burner valve, a control knob is mechanically coupled to the stem of the burner valve such that manual rotation of the control knob (e.g., by a user of the grill) mechanically causes a corresponding rotation of the stem of the burner valve. Rotating the stem of the burner valve in turn causes the burner valve to move between its closed position and its open position, thereby affecting the extent and/or the rate at which gas is able to flow from a manifold of the grill, through the burner valve of the grill, and into a corresponding burner of the grill.

Beyond grills that utilize gas (e.g., natural gas, propane, etc.) as a fuel source, other types of grills also exist that may use other types of fuel. Such grills may include, for example, charcoal grills, pellet grills, wood-fired grills, electric grills, etc. While different fuels may be used, such grills may also benefit from the use of control systems to, for example, control a rate at which fuel and/or heat is provided to a cookbox, control a rate of combustion, provide user interfaces, etc. While techniques disclosed herein are described in the context of a gas grill, such techniques are also equally applicable for use in non-gas grills.

In contrast to conventional gas grills that implement mechanical control architectures of the type described above, the methods and apparatus disclosed herein advantageously provide “control-by-wire” architectures for grills that eliminate the above-described mechanical connection which conventionally exists between each control knob of the grill and each corresponding burner valve of the grill. In some examples, grills disclosed herein include a burner valve, a control knob, a rotary encoder, and a controller (e.g., a central controller).

In some other implementations, a fuel control system may be used in place of a burner valve. The fuel control system may control providing of fuel to a cookbox of the grill and/or a rate at which such fuel is to be combusted. For example, the fuel control system may include an auger to feed fuel (e.g., pellets) to the cookbox and/or other location for combustion, a fan and/or vent controller to control airflow, etc.

In example grills that include a burner valve, a control knob, a rotary encoder, and a controller, the burner valve is movable between an open position and a closed position. The rotary encoder includes a rotatable portion and a fixed portion. The control knob is mechanically coupled to the rotatable portion of the rotary encoder, which is rotatable relative to the fixed portion of the rotary encoder. No mechanical connection exists, however, between the control knob and the burner valve.

In this regard, the rotary encoder is configured to detect a rotational position of the control knob. The rotational position of the control knob corresponds to a rotational position of the rotatable portion of the rotary encoder relative to the fixed portion of the rotary encoder. The controller is in electrical communication with the rotary encoder. The controller is also in electrical communication with the burner valve, which is implemented as a controllable electric valve (e.g., a solenoid valve). The controller is configured to determine a target position of the burner valve based on the rotational position of the control knob. The controller is further configured to instruct the burner valve to move to the target position, thereby implementing a “control-by-wire” architecture with regard to the relationship between the position(s) of the one or more control knob(s) of the grill and the flow of gas into the corresponding one or more burner(s) of the grill.

In some examples, the controller is further configured to instruct one or more lighting modules of the grill to present a notification indicating at least one of the rotational position of the control knob or the target position of the burner valve. In some such examples, the lighting module(s) includes a light source, and presenting the notification includes illuminating the light source. In other such examples, the lighting module(s) includes a light source, and presenting the notification includes pulsing the light source. In some examples, the controller is further configured to instruct one or more output devices of a user interface of the grill to present a notification indicating at least one of the rotational position of the control knob or the target position of the burner valve. In some examples, the controller is further configured to instruct a notification indicating at least one of the rotational position of the control knob or the target position of the burner valve to be presented at a remote device in electrical communication with the grill.

In some examples, the example grill includes user-interface assemblies that include user interface elements (e.g., knobs) that are used to control the position of a respective burner valve. Each user-interface assembly further includes a lighting module to display information about the status of the grill (e.g., a status with respect to the corresponding burner). In a grill system, certain procedures, such as igniting a burner, can cause significant electrical noise that may, in some examples, interfere with the ability of the controller to communicate with the user-interface assembly(ies). It is therefore a goal to reduce the amount of wiring necessary to manufacture the grill (e.g., to reduce locations in which electrical noise can be introduced). In examples disclosed herein, user-interface assemblies are wired in a daisy-chained configuration. That is, instead of connecting each user-interface assembly directly to a controller and/or a central bus, each user-interface assembly is connected to a sequentially previous user-interface assembly.

In examples disclosed herein, the controller communicates with the user-interface assemblies via a controller bus and a lighting bus. In examples disclosed herein, the controller bus is implemented using an inter-integrated circuit communication protocol, and the lighting bus is implemented using a single wire communication protocol (e.g., using a WS2811 communication protocol). However, such communication protocols are intended to facilitate on-device communications (e.g., communications on a printed circuit board (PCB)), and are not intended to be carried over wire harnesses more than a couple of inches as wiring of such length can be easily distorted by interference.

In some examples, instead of using two separate communication buses (e.g., the controller bus and the lighting bus), a single communication bus may be used. Such a single bus may convey both lighting and control information between the central controller and the user-interface assemblies. Such communication may be accomplished using the inter-integrated circuit communication protocol noted above, or any other communication protocol that facilitates communication of information between two devices including, for example, a serial communication protocol (e.g., RS-485), an Ethernet communication protocol, wireless communication protocols (e.g., Bluetooth, Wi-Fi), etc.

In some examples, such communication protocols can additionally or alternatively be used to convey status and/or control information to/from other peripheral devices associated with the grill including, for example, sensor information (e.g., lid sensor information indicating whether a lid of a grill is open or closed, vent position information, temperature information, etc.) and/or control information (e.g., information for controlling a position of an actuator/valve, temperature information for display on an output device, etc.).

In example approaches disclosed herein, signals are communicated using a differential pair signal, which increases the resistance to interference. In this manner, both the controller bus and the lighting bus are implemented using differential wiring. Wiring harnesses can therefore be of a longer length (e.g., multiple feet), enabling device-to-device connections to be made in the chain, and allowing greater flexibility of placement for the electronics. In the context of a grill, this allows for pre-wiring of a front panel with a single connector originating from a first knob in the chain to connect to a controlling device.

In examples disclosed herein, the controller bus is implemented using a node-drop to each user-interface assembly. In contrast, the lighting bus is implemented as a pass through from one user-interface assembly to another knob assembly. Such an approach simplifies wire harnessing and allows each knob to self-identify its respective position. Alternate approaches could have signal integrity issues, or require each knob to be unique and have a larger quantity of harness connections.

The above-identified features as well as other advantageous features of example methods and apparatus for controlling fuel flow in grills based on position data detected via user interface sensors (e.g., rotary encoders) as disclosed herein are further described below in connection with the figures of the application. As used herein in a mechanical context, the term “configured” means sized, shaped, arranged, structured, oriented, positioned, and/or located. For example, in the context of a first object configured to fit within a second object, the first object is sized, shaped, arranged, structured, oriented, positioned, and/or located to fit within the second object. As used herein in an electrical and/or computing context, the term “configured” means arranged, structured, and/or programmed. For example, in the context of a controller configured to perform a specified operation, the controller is arranged, structured, and/or programmed (e.g., based on machine-readable instructions) to perform the specified operation. As used herein, the phrase “in electrical communication,” including variations thereof, encompasses direct communication and/or indirect communication through one or more intermediary components, and does not require direct physical (e.g., wired) communication and/or constant communication, but rather additionally includes selective communication at periodic intervals, scheduled intervals, aperiodic intervals, and/or one-time events. As used herein, the term “processor circuitry” is defined to include (i) one or more special purpose electrical circuits structured to perform specific operation(s) and including one or more semiconductor-based logic devices (e.g., electrical hardware implemented by one or more transistors), and/or (ii) one or more general purpose semiconductor-based electrical circuits programmed with instructions to perform specific operations and including one or more semiconductor-based logic devices (e.g., electrical hardware implemented by one or more transistors). Examples of processor circuitry include programmed microprocessors, Field Programmable Gate Arrays (FPGAs) that may instantiate instructions, Central Processor Units (CPUs), Graphics Processor Units (GPUs), Digital Signal Processors (DSPs), XPUs, or microcontrollers and integrated circuits such as Application Specific Integrated Circuits (ASICs). For example, an XPU may be implemented by a heterogeneous computing system including multiple types of processor circuitry (e.g., one or more FPGAs, one or more CPUs, one or more GPUs, one or more DSPs, etc., and/or a combination thereof) and application programming interface(s) (API(s)) that may assign computing task(s) to whichever one(s) of the multiple types of the processing circuitry is/are best suited to execute the computing task(s).

FIG.1is a block diagram of an example grill100constructed in accordance with the teachings of this disclosure. The grill100ofFIG.1is a gas grill including a plurality of burners. In other examples, the grill100can be implemented as a different type of grill having a controllable heat source (e.g., a pellet grill, an electric grill, etc.). In the illustrated example ofFIG.1, the grill100includes an example first burner102and an example second burner104. In other examples, the grill100can include one or more other burner(s) (e.g., a third burner, a fourth burner, a fifth burner, etc.) in addition to the first burner102and the second burner104shown and described in connection withFIG.1. The first burner102and the second burner104ofFIG.1are each constructed as a burner tube (e.g., a linear burner tube) including a gas inlet for receiving a flow of combustible gas, and further including a plurality of apertures configured to emit flames generated in response to ignition of the gas flowing into and/or through the burner tube. In some examples, additional burners may be implemented, as is represented by burner #N105ofFIG.1. One or more of the additional burner(s)105may be structured, configured, and/or implemented in a manner that is substantially similar to the first burner102and/or the second burner104ofFIG.1.

FIG.2is a perspective view of an example implementation of the grill100ofFIG.1, with an example lid204of the grill100shown in an example closed position200relative to an example cookbox202of the grill100.FIG.3is a perspective view of the implementation of the grill100shown inFIG.2, with the lid204of the grill100shown in an example open position300relative to the cookbox202of the grill100.FIG.4Ais an exploded view of the implementation of the grill100shown inFIGS.2and3.FIG.4Bis an alternative implementation212bof the example control panel212aofFIG.4A.FIG.5is a perspective view of the cookbox202of the implementation of the grill100shown inFIGS.2-4A.

The cookbox202of the grill100supports, carries, and/or houses the burners (e.g., the first burner102and the second burner104) of the grill100, with respective ones of the burners being spaced apart from one another within the cookbox202. As shown inFIG.5, the cookbox202supports, carries, and/or houses a total of five example burners502(e.g., including the first burner102and the second burner104ofFIG.1), with each of the five burners502being spaced apart from one another within the cookbox202. In other examples, the cookbox202can support, carry, and/or house a different number (e.g., two, three, four, six, etc.) of burners502. In the illustrated example ofFIGS.2-5, each of the burners502is constructed as a linear burner tube positioned in a front-to-rear orientation within the cookbox202(e.g., extending from a front wall504of the cookbox202to a rear wall506of the cookbox202). In other examples, one or more of the burner(s)502can have a different shape (e.g., a non-linear shape such as a P-tube), and/or can have a different orientation (e.g., a left-to-right orientation) within the cookbox202. It should accordingly be understood that the cookbox configuration shown inFIGS.2-5is but one example of a cookbox202that can be implemented as part of the grill100ofFIG.1.

The lid204of the grill100is configured to cover and/or enclose the cookbox202of the grill100when the lid is in a closed position (e.g., the closed position200ofFIG.2). In the illustrated example ofFIGS.2-4A, the lid204is movably (e.g., pivotally) coupled to the cookbox202such that the lid204can be moved (e.g., pivoted) relative to the cookbox202between a closed position (e.g., the closed position200ofFIG.2) and an open position (e.g., the open position300ofFIG.3). In other examples, the lid204of the grill100can instead be removably positioned on the cookbox202of the grill100without there being any direct mechanical coupling between the lid204and the cookbox202. In some such other examples, the lid204can be movably (e.g., pivotally) coupled to one or more structure(s) of the grill100other than the cookbox202. For example, the lid204can be movably (e.g., pivotally) coupled to a frame, to a cabinet, and/or to one or more side table(s) of the grill100. Movement of the lid204of the grill100between the closed position200shown inFIG.2and the open position300shown inFIG.3can be facilitated via user interaction with an example handle206of the grill100that is coupled to the lid204.

In the illustrated example ofFIGS.2-4A, the cookbox202and the lid204of the grill100collectively define an example cooking chamber302configured to cook one or more item(s) of food. The cooking chamber302of the grill100becomes accessible to a user of the grill100when the lid204of the grill100is in the open position300shown inFIG.3. Conversely, the cooking chamber302of the grill100is generally inaccessible to the user of the grill100when the lid204of the grill100is in the closed position200shown inFIG.2. User access to the cooking chamber302of the grill100may periodically become necessary, for example, to add an item of food to the cooking chamber302(e.g., at or toward the beginning of a cook), to remove an item of food from the cooking chamber302(e.g., at or toward the end of a cook), and/or to flip, rotate, relocate, or otherwise move an item of food within the cooking chamber302(e.g., during the middle of a cook).

As further shown inFIGS.2-4A, the grill100includes an example frame208that supports the cookbox202of the grill100. In the illustrated example ofFIGS.2-4A, the frame208forms an example cabinet210within which one or more component(s) of the grill100can be housed and/or stored. In other examples, the cabinet210of the grill100can be omitted in favor of an open-space configuration of the frame208. As further shown inFIGS.2-4B, the grill100includes an example control panel212aor212blocated along the front portion of the cookbox202, the frame208, and/or the cabinet210of the grill100, an example first side table214located on a first side (e.g., a right side) of the cookbox202, the frame208, and/or the cabinet210of the grill100, and an example second side table216located on a second side (e.g., a left side) of the cookbox202, the frame208, and/or the cabinet210of the grill100. Various components of the grill100ofFIG.1described herein can be supported by, carried by, housed by, mounted to, and/or otherwise coupled to at least one of the cookbox202, the lid204, the handle206, the frame208, the cabinet210, the control panel212aor212b, the first side table214, and/or the second side table216of the grill100.

In the illustrated example ofFIG.4A, the control panel212autilizes rotary knobs220. As shown in the illustrated example ofFIG.4B, the control panel212bmay utilize buttons222. In the illustrated example ofFIG.4B, an additional ignitor button224is shown that may be used to trigger ignition of the grill. In the illustrated example ofFIG.4B, a control panel226is shown that may be used to present status information to a user of the grill.

Returning to the illustrated example ofFIG.1, the grill100ofFIG.1receives fuel from a fuel source106. The example grill100ofFIG.1includes an example fuel source valve108, an example manifold110, an example first burner valve112, an example second burner valve114, an example first ignitor116, an example second ignitor118, example user-interface assemblies120,122,124, an example temperature sensor128, one or more example flame sensor(s)130, one or more example lighting module(s)132, an example user interface134(e.g., including one or more example input device(s)136and one or more example output device(s)138), an example network interface140(e.g., including one or more example communication device(s)142), an example controller144(e.g., including example control circuitry146and example detection circuitry148), and an example memory150. The grill100ofFIG.1is configured to communicate (e.g., wirelessly communicate) with one or more example remote device(s)152, as further described below.

The grill100ofFIG.1includes a control system for controlling, managing, performing, and/or otherwise carrying out one or more operation(s) of the grill100including, for example, for presenting safety-based temperature status notifications associated with the grill100. In the illustrated example ofFIG.1, the control system of the grill100includes the fuel source valve108, the first burner valve112, the second burner valve114, the first ignitor116, the second ignitor118, the user-interface assemblies120,122,124, the temperature sensor128, the flame sensor(s)130, the user interface134(e.g., including the input device(s)136and the output device(s)138), the network interface140(e.g., including the communication device(s)142), the controller144(e.g., including the control circuitry146and the detection circuitry148), and the memory150. In other examples, one or more of the aforementioned components of the grill100can be omitted from the control system of the grill100. For example, the fuel source valve108can be omitted from the control system of the grill100in instances where the fuel source valve108is not configured to be electrically controlled and/or electrically actuated by the controller144, with the fuel source valve108instead being configured only for manual control and/or manual actuation. In still other examples, the control system of the grill100can further include the remote device(s)152that are configured to communicate (e.g., wirelessly communicate) with the grill100.

The control system of the grill100ofFIG.1is powered and/or operated by a power source. For example, the electrical components that form the control system of the grill100can be powered and/or operated by DC power supplied via one or more on-board or connected batteries of the grill100. As another example, the electrical components that form the control system of the grill100can alternatively be powered and/or operated by AC power supplied via household electricity or wall power to which the grill100is connected. The grill100includes a power button (e.g., a power switch) that is configured to enable (e.g., power on) or disable (e.g., power off) the control system of the grill100in response to the power button being manually actuated by a user of the grill100.

The grill100ofFIG.1further includes an example gas train154that extends from the fuel source106to the manifold110of the grill100, and from the manifold110to respective ones of the first burner102and the second burner104of the grill100. The gas train154can be implemented via one ore more conduit(s) (e.g., one or more rigid or flexible pipe(s), tube(s), etc.) that are configured to carry combustible gas from the fuel source106to the first burner102and/or the second burner104of the grill100. In some examples, the fuel source106is implemented as a fuel tank (e.g., a propane tank) containing combustible gas. In such examples, the fuel source106will typically be located partially or fully within the cabinet210of the grill100, partially or fully within a spatial footprint formed by the frame208of the grill100, below the cookbox202of the grill100and partially or fully within a spatial footprint formed by the cookbox202of the grill100, or below the cookbox202of the grill100and partially or fully within a spatial footprint formed by the first side table214or the second side table216of the grill100. In other examples, the fuel source106can instead be implemented as a piped (e.g., household) natural gas line that provides an accessible flow of combustible gas.

The fuel source valve108ofFIG.1is coupled to and operatively positioned within the gas train154between the fuel source106and the manifold110of the grill100. The fuel source valve108is configured to be movable between a closed position that prevents gas contained within the fuel source106from flowing into the manifold110, and an open position that enables gas contained within the fuel source106to flow from the fuel source106into the manifold110. In the illustrated example ofFIG.1, the fuel source valve108is operatively coupled to (e.g., in electrical communication with) the controller144of the grill100, with the fuel source valve108being implemented as a controllable electric valve (e.g., a solenoid valve) that is configured to transition from the closed position to the open position, and vice-versa, in response to instructions, commands, and/or signals (e.g., a supply of current) generated by the controller144. In other examples, the fuel source valve108can instead be implemented as a valve having a knob or a lever operatively coupled (e.g., mechanically coupled) thereto, with the knob or the lever being configured to be electrically actuated (e.g., via a motor) in response to instructions, commands, and/or signals generated by the controller144of the grill100. In still other examples, the fuel source valve108may have no electrically-controllable components, in which case actuation of the fuel source valve108from the closed position to the open position, and vice-versa, occurs in response to a user of the grill100manually actuating a knob or a lever that is operatively coupled (e.g., mechanically coupled) to the fuel source valve108.

The first burner valve112ofFIG.1is coupled to and operatively positioned within the gas train154between the manifold110and the first burner102of the grill100. In some examples, a gas inlet of the first burner valve112is located within the manifold110, and a gas outlet of the first burner valve112is located within the first burner102. The first burner valve112is configured to be movable between a closed position that prevents gas contained within the manifold110from flowing into the first burner102, and an open position that enables gas contained within the manifold110to flow from the manifold110into the first burner102. In the illustrated example ofFIG.1, the first burner valve112is operatively coupled to (e.g., in electrical communication with) the controller144of the grill100, with the first burner valve112being is implemented as a controllable electric valve (e.g., a solenoid valve) that is configured to transition from the closed position to the open position, and vice-versa, in response to instructions, commands, and/or signals (e.g., a supply of current) generated by the controller144. In some examples, the first burner valve112is controllable to any position (e.g., infinite position control) between the above-described closed position (e.g., fully closed) and the above-described open position (e.g., fully open). In such examples, the first burner valve112ofFIG.1may be controlled to various positions to achieve different specified temperatures (e.g., different setpoint temperatures) within the cooking chamber302of the grill100, as may be required by the various ordered steps, instructions, and/or operations of one or more selectable cook program(s) to be implemented via the control system of the grill100.

The second burner valve114ofFIG.1is coupled to and operatively positioned within the gas train154between the manifold110and the second burner104of the grill100. In some examples, a gas inlet of the second burner valve114is located within the manifold110, and a gas outlet of the second burner valve114is located within the second burner104. The second burner valve114is configured to be movable between a closed position that prevents gas contained within the manifold110from flowing into the second burner104, and an open position that enables gas contained within the manifold110to flow from the manifold110into the second burner104. In the illustrated example ofFIG.1, the second burner valve114is operatively coupled to (e.g., in electrical communication with) the controller144of the grill100, with the second burner valve114being implemented as a controllable electric valve (e.g., a solenoid valve) that is configured to transition from the closed position to the open position, and vice-versa, in response to instructions, commands, and/or signals (e.g., a supply of current) generated by the controller144. In some examples, the second burner valve114is controllable to any position (e.g., infinite position control) between the above-described closed position (e.g., fully closed) and the above-described open position (e.g., fully open). In such examples, the second burner valve114ofFIG.1may be controlled to various positions to achieve different specified temperatures (e.g., different setpoint temperatures) within the cooking chamber302of the grill100, as may be required by the various ordered steps, instructions, and/or operations of one or more selectable cook program(s) to be implemented via the control system of the grill100.

As described above, the first burner valve112and the second burner valve114ofFIG.1respectively differ from known burner valves of conventional gas grills in that neither the first burner valve112nor the second burner valve114includes a stem that is mechanically coupled to a user-accessible control knob of the grill, whereby the control knob traditionally facilitates manual control and/or manual actuation of the operable position of the burner valve. The first burner valve112and the second burner valve114ofFIG.1are instead only controllable and/or actuatable via the “control-by-wire” functionality further described herein.

In some examples, additional burner valves may be implemented, as is represented by burner valve #N115ofFIG.1. One or more of the additional burner valve(s)115may be structured, configured, and/or implemented in a manner that is substantially similar to the first burner valve112and/or the second burner valve114ofFIG.1.

The first ignitor116ofFIG.1is mechanically coupled and/or operatively positioned relative to the first burner102of the grill100. More specifically, the first ignitor116is located adjacent the first burner102at a position that enables the first ignitor116to ignite combustible gas as the gas emanates from within the first burner102via apertures formed in the first burner102. The first ignitor116ofFIG.1is operatively coupled to (e.g., in electrical communication with) the controller144of the grill100, with the first ignitor116being configured to generate sparks (e.g., via a spark electrode of the first ignitor116) and/or otherwise induces ignition of the combustible gas in response to an instruction, a command, and/or a signal generated by the controller144.

The second ignitor118ofFIG.1is mechanically coupled and/or operatively positioned relative to the second burner104of the grill100. More specifically, the second ignitor118is located adjacent the second burner104at a position that enables the second ignitor118to ignite combustible gas as the gas emanates from within the second burner104via apertures formed in the second burner104. The second ignitor118ofFIG.1is operatively coupled to (e.g., in electrical communication with) the controller144of the grill100, with the second ignitor118being configured to generate sparks (e.g., via a spark electrode of the second ignitor118) and/or otherwise induces ignition of the combustible gas in response to an instruction, a command, and/or a signal generated by the controller144.

In some examples, the first ignitor116and/or the second ignitor118ofFIG.1can respectively be structured, configured, and/or implemented as one of the various ignitors described in U.S. patent application Ser. No. 17/144,038, filed on Jan. 7, 2021. In such examples, the first ignitor116and/or the second ignitor118ofFIG.1can respectively be mechanically coupled to a corresponding one of the first burner102and/or the second burner104of the grill100via a ceramic harness as described in U.S. patent application Ser. No. 17/144,038. The entirety of U.S. patent application Ser. No. 17/144,038 is hereby incorporated by reference herein.

In some examples, additional ignitors may be implemented, as is represented by ignitor #N119ofFIG.1. One or more of the additional ignitor(s)119may be structured, configured, and/or implemented in a manner that is substantially similar to the first ignitor116and/or the second ignitor118ofFIG.1.

The example grill100ofFIG.1includes user-interface assemblies120,122,124. As described in greater detail below, each user-interface assembly includes a knob that is used to control the position of a respective burner valve. Each user-interface assembly further includes a lighting module to display information about the status of the grill (e.g., a status with respect to the corresponding burner). In a grill system, certain procedures, such as igniting a burner, can cause significant electrical noise that may, in some examples, interfere with the ability of the controller144to communicate with the user-interface assembly(ies). It is therefore a goal to reduce the amount of wiring necessary to manufacture the grill100. In the illustrated example ofFIG.1, the user-interface assemblies120,122,124are wired in a daisy-chained configuration. That is, instead of connecting each user-interface assembly to the controller144and/or a central bus, each user-interface assembly120,122,124is connected to a sequentially previous user-interface assembly (or the controller144in the case of a first user-interface assembly).

In examples disclosed herein, the controller144communicates with the user interface assemblies via a controller bus and a lighting bus. In examples disclosed herein, the controller bus is implemented using an inter-integrated circuit communication protocol, and the lighting bus is implemented using a single wire communication protocol (e.g., using a WS2811 communication protocol). However, such communication protocols are intended to facilitate on-device communications (e.g., communications on a printed circuit board (PCB)), and are not intended to be carried over wire harnesses more than a couple of inches as wiring of such length can be easily distorted by interference.

In example approaches disclosed herein, signals are communicated using a differential pair signal, which increases the resistance to interference. In this manner, both the controller bus and the lighting bus are implemented using differential wiring. Wiring harnesses can therefore be of a longer length (e.g., multiple feet), enabling device-to-device connections to be made in the chain, and allowing greater flexibility of placement for the electronics. In the context of a grill, this allows for pre-wiring of a front panel with a single connector originating from a first knob in the chain to connect to a controlling device (e.g., the controller144).

In examples disclosed herein, the controller bus is implemented using a node-drop to each user-interface assembly120,122,124. In contrast, the lighting bus is implemented as a pass through from one user-interface assembly to another user-interface assembly (originating at the controller144). Such an approach simplifies wire harnessing and allows each user interface assembly to self-identify its respective position. Alternate approaches could have signal integrity issues, or require each user interface assembly to be unique and have a larger quantity of harness connections.

As noted above, the example grill100includes user-interface assemblies120,122,124. As described in further detail below in connection withFIG.6, the user-interface assemblies120,122,124communicate with the controller144to provide inputs to the controller144, and/or provide outputs to the user (e.g., via lighting modules included in the user-interface assemblies). The controller144can, in turn, use information provided from the user-interface assemblies120,122,124to control the burner valves112,114. In the illustrated example ofFIG.1, each one of the user-interface assemblies120,122,124corresponds with a respective one of the burner valves112,114,115and/or a respective one of the ignitors116,118,119. However, in some examples, a user-interface assembly may correspond to multiple burner valves. Thus, while conventional multi-burner gas grills typically include a plurality of control knobs (e.g., located on or along a control panel of the grill), with each control knob being physically associated with a corresponding one of the burners of the gas grill by virtue of a mechanical connection existing between the control knob and a stem of a corresponding burner valve (e.g., such that rotation of the control knob by a user of the grill opens, closes, or otherwise adjusts the position of the burner valve), by contrast, the grill100ofFIG.1implements a “control-by-wire” architecture. Such a “control-by-wire” architecture eliminates the mechanical connection in favor of electrical control.

Although the first user-interface assembly120ofFIG.1is not mechanically coupled to the first burner valve112ofFIG.1, rotation of the control knob of the first user-interface assembly120by a user of the grill100can nonetheless cause the first burner valve112to open, close, or otherwise adjust its position. In this regard, the controller144ofFIG.1is configured to interpret different rotational positions of a control knob (and/or other user interface element) of the first user-interface assembly120ofFIG.1(e.g., as sensed, measured, and/or detected by a sensor of the first user-interface assembly120ofFIG.1) as being indicative of correlated user requests associated with different operational states (e.g., ignite, high, medium, low, or off) of the first burner102ofFIG.1. For example, in response to determining that the control knob of the first user-interface assembly120has been positioned at a relative angle of negative one hundred eighty degrees (−180°), the controller144may interpret the determined rotational position as a user request that the first burner102operate in a “medium” state. To satisfy the user request indicated by the determined rotational position of the control knob of the first user-interface assembly120, the controller144may instruct, command, and/or signal the first burner valve112ofFIG.1to assume a first corresponding target position, such as a partially open (e.g., 50% open) position that facilitates a “medium” flow of gas through the first burner valve112and into the first burner102, thereby effecting the “medium” operational state of the first burner102.

As another example, in response to determining that the control knob of the first user-interface assembly120has been positioned at a relative angle of negative ninety degrees (−90°), the controller144may interpret the determined rotational position as a user request that the first burner102operate in a “high” state. To satisfy the user request indicated by the determined rotational position of the control knob of the first user-interface assembly120, the controller144may instruct, command, and/or signal the first burner valve112ofFIG.1to assume a second corresponding target position, such as a fully open (e.g., 100% open) position that facilitates a “high” flow of gas through the first burner valve112and into the first burner102, thereby effecting the “high” operational state of the first burner102. As yet another example, in response to determining that the control knob of the first user-interface assembly120has been positioned at a relative angle of zero degrees (0°), the controller144may interpret the determined rotational position as a user request that the first burner102be placed in an “off” state. To satisfy the user request indicated by the determined rotational position of the control knob of the first user-interface assembly120, the controller144may instruct, command, and/or signal the first burner valve112ofFIG.1to assume a third corresponding target position, such as a fully closed (e.g., 0% open, or 100% closed) position that prevents any flow of gas through the first burner valve112and into the first burner102, thereby effecting the “off” state of the first burner102.

As yet another example, in response to determining that the control knob of the first user-interface assembly120has been pushed and/or pressed inward, the controller144may interpret the determined translational position as a user request that the first burner102be ignited. To satisfy the user request indicated by the determined translational position of the control knob of the first user-interface assembly120, the controller144may instruct, command, and/or signal the first burner valve112ofFIG.1to assume a fully open (e.g., 100% open) position that facilitates a “high” flow of gas through the first burner valve112and into the first burner102. The controller144may further instruct, command, and/or signal the first ignitor116ofFIG.1to ignite the flow of gas emanating from the first burner102, thereby effecting the “ignited” state of the first burner102. As yet another example, in response to determining that the control knob of the first user-interface assembly120has been pushed and/or pressed inward, the controller144may interpret the determined translational position as a user request that all burners (e.g., the first burner102and the second burner104) of the grill100be ignited. To satisfy the user request indicated by the determined translational rotational position of the control knob of the first user-interface assembly120, the controller144may instruct, command, and/or signal the first burner valve112and the second burner valve114ofFIG.1to respectively assume (e.g., either concurrently, or sequentially) a fully open (e.g., 100% open) position that facilitates a “high” flow of gas through the first burner valve112and into the first burner102, as well as a “high” flow of gas through the second burner valve114and into the second burner104. The controller144may further instruct, command, and/or signal the first ignitor116and the second ignitor118ofFIG.1to respectively ignite (e.g., either concurrently or sequentially) the flow of gas emanating from the first burner102and the flow of gas emanating from the second burner104, thereby effecting the “ignited” state of both the first burner102and the second burner104.

Correlation data (e.g., a correlation table) establishing and/or defining one or more correlation(s) and/or relationship(s) between one or more position(s) (e.g., one or more rotational and/or translational position(s)) of the control knob of the first user-interface assembly120of the grill100ofFIG.1on the one hand, and one or more position(s) (e.g., one or more target position(s)) of the first burner valve112of the grill ofFIG.1on the other hand may be stored in the memory150of the grill100ofFIG.1. Such correlation data may be accessed from the memory150by the controller144of the grill100ofFIG.1in the course of the controller144determining a target position for the first burner valve112(e.g., a position to which the controller144is to instruct, command, and/or otherwise cause the first burner valve112to move to) based on a detected and/or determined position (e.g., a rotational and/or a translational position) of the control knob of the first user-interface assembly120ofFIG.1, as further described below.

As noted above, the grill100ofFIG.1includes a plurality of user-interface assemblies120,122,124. While the above description explains the operation of the grill100with respect to the first user-interface assembly120, other user-interface assemblies, such as user-interface assembly #2122and user-interface assembly #n124may additionally and/or alternatively be used. Moreover, while in the illustrated example ofFIG.1, three user-interface assemblies are shown, any number of user-interface assemblies may be used. In the illustrated example ofFIG.1, user-interface assembly #1120corresponds to and/or controls operation of the burner valve #1112, burner #1102, and ignitor #1116; user-interface assembly #2122corresponds to and/or controls operation of the burner valve #2114, burner #2104, and ignitor #2118; and user-interface assembly #n124corresponds to and/or controls operation of the burner valve #n115, burner #n105, and ignitor #n119. In this manner, there is a one-to-one correspondence between each user-interface assembly and its corresponding burner valve, burner, and ignitor. However, in some examples, there may be a one-to-many correspondence, where a user-interface assembly may be used to control more than one burner valve, burner, and ignitor.

FIG.6is a block diagram of an example implementation of a user-interface assembly, such as one of the user-interface assemblies120,122,124ofFIG.1. The example user-interface assembly600ofFIG.6includes an input connector605, addressing terminals608, an output connector610, user-interface controller circuitry620, knob sensor(s)630, a control knob640, a lighting circuitry650, a differential controller bus623, a differential lighting bus654, and differential signaling translators625,655,657. The user-interface assembly600connects with an input wiring harness680which includes an addressing block682. The user-interface assembly600further connects with an output wiring harness690. In some examples, the user-interface assembly may be implemented as a knob assembly. The term “knob assembly” may be used, for example, because of the connection to a rotary knob-style input device. In contrast, other styles of input devices may additionally or alternatively be used such as, for example, sliders, buttons, etc. Examples disclosed herein are not limited solely to control systems that utilize rotary knob-styled input devices but, instead may be utilized with any type and/or style of input device.

The user-interface controller circuitry620of the illustrated example ofFIG.6communicates via an example differential controller bus654. As noted above, the differential controller bus654is implemented using an inter-integrated circuit protocol. As such, the user-interface controller circuitry620, when initializing communications via the differential controller bus654, identifies itself using an address. The address to be used by the user-interface assembly600is selected by the addressing block682, which selectively shorts terminals within the addressing terminals608. In this manner, different addressing blocks can be used for different user-interface assemblies, resulting in each user-interface assembly communicating using different addresses via the differential controller bus654.

The user-interface controller circuitry620receives data from the knob sensor(s)630, and provides such information to the controller144ofFIG.1via the differential controller bus654. In examples disclosed herein, the knob sensor(s)630are implemented by one or more of a rotary encoder, a potentiometer, a switch, a button, a plurality of buttons, a slider, etc. The knob sensor(s)630enable detection of the position and/or interaction with the control knob640. In some examples, the knob sensor(s)630are, more generically, implemented as sensors that enable detection of user interaction with other types of user interface elements such as, for example, buttons, sliders, etc.

In some examples, the user-interface controller circuitry620may additionally or alternatively be in communication with other input and/or output devices. For example, in addition to the knob sensor(s)630, the user-interface controller circuitry620may be in communication with input devices such as, for example, a touchscreen display, an electromechanical input (e.g., an encoder, pushbuttons, etc.) and/or any combination thereof. Moreover, the user-interface controller circuitry620may additionally or alternatively be in communication with output devices such as, for example, a display, a speaker, a buzzer, an actuator, a servo, etc.

The example lighting circuitry650of the illustrated example ofFIG.6is implemented as one or more light emitting diodes (LEDs). However, any other lighting circuitry may additionally or alternatively be used. The LEDs of the illustrated example ofFIG.6are connected in a serial fashion. In this manner, the user-interface assembly600receives a control signal via the input connector605, translates the differential signal into a traditional (e.g., non-differential signal) using the differential signaling translator655, lights the lighting circuitry650, converts the output of the lighting circuitry650into a differential signal using the differential signaling translator657, and outputs the differential signal via the output connector610.

The lighting circuitry650of the grill100ofFIG.1can be implemented by any number(s), any type(s), and/or any configuration(s) of lighting circuits(s). The lighting circuitry650ofFIG.6is configured to project light (e.g., emitted from one or more incandescent, halogen, or light-emitting diode (LED) light source(s) of the lighting circuitry650) toward or away from one or more structure(s) of the grill100including, for example, the cookbox202, the lid204, the handle206, the frame208, the cabinet210, the control panel212, the first side table214, and/or the second side table216of the grill100. In some examples, the lighting circuitry650is mechanically coupled to (e.g., fixedly connected to) the grill100. For example, one or more of the lighting circuits can be mounted to the cookbox202, the lid204, the handle206, the frame208, the cabinet210, the control panel212, the first side table214, and/or the second side table216of the grill100. In such examples, the lighting circuitry650is preferably mounted to a portion of the grill100that enables the light source(s) of the lighting circuitry650to be easily viewed by a user of the grill100, such as a front portion of the cookbox202, a front portion of the lid204, a front portion of the handle206, a front portion of the frame208, a front portion of the cabinet210, a front portion of the control panel212, a front portion of the first side table214, and/or a front portion of the second side table216of the grill100. In some examples, the lighting circuitry650can be implemented by and/or as one or more of the output device(s)138of the user interface134of the grill100, as further described below.

The lighting circuitry650can be implemented as a controllable electric lighting module having one or more light source(s) that is/are configured to transition from an off state (e.g., a non-light-projecting state of the light source(s) of the lighting module) to an on state (e.g., a light-projecting state of the light source(s) of the lighting module), and vice-versa, in response to instructions, commands, and/or signals (e.g., a supply of current) generated by the controller144of the grill100. In some examples, one or more of the light source(s) may be instructed, commanded, and/or signaled (e.g., by the controller144) to illuminate in a manner that causes the light source(s) to appear as being constantly lit (e.g., in a constant light-projecting state) over a duration of time. In other examples, one or more of the light source(s) may be instructed, commanded, and/or signaled (e.g., by the controller144) to illuminate in a manner that causes the light source(s) to appear as being periodically lit and/or blinking (e.g., switching up and back between a light-projecting state and a non-light-projecting state) over a duration of time. In still other examples, one or more of the light source(s) of the lighting circuitry650may be instructed, commanded, and/or signaled (e.g., by the controller144) to cease illuminating such that the light source(s) appear as being constantly unlit (e.g., in a constant non-light-projecting state) over a duration of time.

In instances where one or more of the light source(s) of the lighting circuitry650is/are implemented as an LED, one or more of such LED(s) can be implemented as multi-color LED that can be instructed, commanded, and/or signaled (e.g., by the controller144) to illuminate in different colors (e.g., white, red, blue, etc.) of the color spectrum. In some such examples, one or more of the multi-color LED(s) may be instructed, commanded, and/or signaled to illuminate in a first color (e.g., white) to indicate that the grill100is powered on, and a second color (e.g., red) to indicate that a control knob (e.g., the control knob of the first user-interface assembly120) of the grill100is in a rotational position that corresponds to a burner valve (e.g., the first burner valve112) of the grill100being in an open position (e.g., a partially-open position or a fully-open position). In some such examples, the intensity of the second color to which the LED(s) is/are illuminated may change in relation to the extent to which the control knob of the grill100is rotated, and/or in relation to the extent to which the burner valve of the grill100is open. In other such examples, the second color to which the LED(s) is/are illuminated may change to one or more other color(s) (e.g., a third color, a fourth color, etc.) in relation to the extent to which the control knob of the grill100is rotated, and/or in relation to the extent to which the burner valve of the grill100is open. The aforementioned color schemes are advantageous in that they intuitively informs a user of the grill100of the operational status of the burner valve (e.g., the first burner valve112) and/or the burner (the first burner102) of the grill100. In this regard, users of various objects conventionally associate the color red with a warm or hot status of an object, as would exist in a scenario where flames are emanating from a burner of the grill100.

The example differential signaling translators625,655,657enable translation between differential signaling (e.g., used when communicating via the harness(es)) and non-differential signaling.

FIG.7is a partial cross-sectional view of the implementation of the grill100shown inFIGS.2-4A. As shown inFIG.7, the knob sensor(s)630of the user-interface assembly600is implemented as a rotary encoder having an example rotatable portion702(e.g., a rotatable shaft) to which the control knob640of the user-interface assembly600is mechanically coupled. The rotatable portion702of the knob sensor(s)630can be rotated via user interaction with the control knob640(e.g., manual rotation of the control knob640). In the illustrated example ofFIG.7, the rotatable portion702of the knob sensor(s) is mechanically connected to a printed circuit board706. In some examples, the printed circuit board706is populated with the electronic components of the user-interface assembly600. The knob sensor(s)630includes one or more sensor(s) that is/are configured to sense, measure, and/or detect the relative angular position of the control knob640. Data, information, and/or signals that is/are sensed, measured, and/or detected by the knob sensor(s)630can be transmitted directly to the controller144ofFIG.1, and/or can be transmitted to and stored in the memory150ofFIG.1.

As further shown inFIG.7, the control knob640is not mechanically coupled to the second burner valve114of the grill100. Nor is any portion of the user-interface assembly600mechanically coupled to the second burner valve114of the grill100. Instead, a “control-by-wire” architecture exists in relation to the control knob640and the burner valve114.

Returning to the illustrated example ofFIG.1, the temperature sensor128ofFIG.1senses, measures, and/or detects the temperature within the cooking chamber302of the grill100. In some examples, the temperature sensor128can be implemented by and/or as a thermocouple coupled to either the cookbox202or the lid204of the grill100, and positioned in and/or extending into the cooking chamber302of the grill100. Data, information, and/or signals sensed, measured, and/or detected by the temperature sensor128ofFIG.1can be of any quantity, type, form, and/or format. Data, information, and/or signals sensed, measured, and/or detected by the temperature sensor128ofFIG.1can be transmitted directly to the controller144ofFIG.1, and/or can be transmitted to and stored in the memory150ofFIG.1.

The flame sensor(s)130of the grill100ofFIG.1can be implemented by any number(s), any type(s), and/or any configuration(s) of flame sensor(s). The flame sensor(s)130is/are configured to sense, measure, and/or detect the presence and/or the absence of a flame emanating from the first burner102and/or the second burner104of the grill100. In some examples, one or more of the flame sensor(s)130of the grill100can be structured, configured, and/or implemented as one of the various flame sensors described in U.S. patent application Ser. No. 17/144,038, filed on Jan. 7, 2021. The entirety of U.S. patent application Ser. No. 17/144,038 is hereby incorporated by reference herein. Data, information, and/or signals sensed, measured, and/or detected by the flame sensor(s)130ofFIG.1can be of any quantity, type, form, and/or format. In some examples, data, information, and/or signals sensed, measured, and/or detected by the flame sensor(s)130ofFIG.1can be transmitted directly to the controller144ofFIG.1, and/or can be transmitted to and stored in the memory150ofFIG.1.

FIG.8Ais a front view of an example lighting module800that can be implemented by or as the lighting circuitry650ofFIG.6. In the illustrated example ofFIG.8A, the lighting module800includes a plurality of example LEDs802mounted to, positioned on, and/or otherwise located relative to an example printed circuit board804of a control panel of a grill (e.g., the control panel212of the grill100ofFIGS.2-4A and7). As shown inFIG.8A, the LEDs802are configured as an example ring806, with the ring806being concentrically positioned relative to an example control knob808that is also mounted to, positioned on, and/or otherwise located relative to the printed circuit board804of the control panel. The control knob808ofFIG.8can be implemented by and or as the control knob640ofFIG.6described above.FIG.8Bis a front view of the lighting module800shown inFIG.8A, with the control knob808ofFIG.8Aremoved.FIG.9is a side view of the lighting module800shown inFIGS.8A and8B, with the control knob808ofFIG.8Aremoved.

As shown inFIGS.8B and9, the ring806of the LEDs802is also concentrically positioned relative to an example rotary encoder822having an example rotatable portion824(e.g., a rotatable shaft) to which the control knob808shown inFIG.8Ais mechanically coupled. The rotatable portion824of the rotary encoder822can be rotated relative to an example fixed portion826of the rotary encoder822via user interaction with the control knob808(e.g., manual rotation of the control knob808). The fixed portion826of the rotary encoder822includes one or more sensor(s) that is/are configured to sense, measure, and/or detect the relative angular position of the rotatable portion824and/or the relative angular position of the control knob808. The rotary encoder822ofFIGS.8B and9can be implemented by knob sensor(s) ofFIG.6. Data, information, and/or signals that is/are sensed, measured, and/or detected by the sensor(s) of the rotary encoder802can accordingly be transmitted directly to the controller144ofFIG.1, and/or can be transmitted to and stored in the memory150ofFIG.1.

As shown inFIGS.8B and9, the fixed portion826of the rotary encoder822is mounted to, positioned on, and/or otherwise located relative to the printed circuit board804of the control panel. In the illustrated example ofFIGS.8A,8B, and/or9, the ring806of the LEDs802circumscribes the rotary encoder822and also circumscribes the control knob808. In other examples (e.g., when one or more portion(s) of the control knob808is/are transparent or translucent), the ring806of the LEDs802may circumscribe the rotary encoder822, and the control knob808may circumscribe the ring806of the LEDs802.

In the illustrated example ofFIGS.8A,8B, and/or9, the LEDs802of the lighting module800can be either individually or collectively controllable to transition from an off state (e.g., a non-light-projecting state) to an on state (e.g., a light-projecting state) and vice-versa, in response to instructions, commands, and/or signals (e.g., a supply of current) generated by the controller144of the grill100. In this regard, the LEDs802can be individually or collectively instructed, commanded, and/or signaled (e.g., by the controller144) to illuminate in a manner that causes one or more of the LEDs802to appear as being constantly lit (e.g., in a constant light-projecting state) over a duration of time. The LEDs802can alternatively be individually or collectively instructed, commanded, and/or signaled (e.g., by the controller144) to illuminate in a manner that causes one or more of the LEDs802to appear as being periodically lit and/or blinking (e.g., switching up and back between a light-projecting state and a non-light-projecting state) over a duration of time. The LEDs802can alternatively be individually or collectively instructed, commanded, and/or signaled (e.g., by the controller144) to cease illuminating such that one or more of the LEDs802appear(s) as being constantly unlit (e.g., in a constant non-light-projecting state) over a duration of time.

In some examples, the LEDs802of the lighting module800ofFIGS.8A,8B, and/or9are implemented as multi-color LEDs that can be individually or collectively instructed, commanded, and/or signaled (e.g., by the controller144) to illuminate in different colors (e.g., white, red, blue, etc.) of the color spectrum. In some such examples, one or more of the multi-color LEDs802can be individually or collectively instructed, commanded, and/or signaled to illuminate in a first color (e.g., white) to indicate that the grill100is powered on, and a second color (e.g., red) to indicate that the control knob808is in a rotational position that corresponds to a burner valve (e.g., the first burner valve112or the second burner valve114) of the grill100being in an open position (e.g., a partially-open position or a fully-open position). In some such examples, the intensity of the second color to which the LED(s)802is/are illuminated may change in relation to the extent to which the control knob808is rotated, and/or in relation to the extent to which the burner valve of the grill100is open. In other such examples, the second color to which the LED(s)802is/are illuminated may change to one or more other color(s) (e.g., a third color, a fourth color, etc.) in relation to the extent to which the control knob808is rotated, and/or in relation to the extent to which the burner valve of the grill100is open.

In some examples, respective ones of the LEDs802of the lighting module800ofFIGS.8A,8B, and/or9can be instructed, commanded, and/or signaled (e.g., by the controller144) to progressively illuminate in a sequential manner (e.g., moving clockwise or counterclockwise) around the circumference of the ring806as the control knob808is progressively rotated, and/or as the burner valve that is logically connected to the control knob808is progressively opened (e.g., moved from a fully-closed position toward a fully-open position). In some such examples, all of the LEDs802of the lighting module800ofFIGS.8A,8B, and/or9may be in a non-light-projecting state (or, alternatively in a light-projecting state in which the LEDs802are illuminated the color white) when the control knob808is in a first relative rotational position (e.g., a zero degree position) that corresponds to the burner valve which is logically connected to the control knob808being in a fully-closed position (e.g., 0% open position). In such an example, rotation of the control knob808in a clockwise direction to a second relative rotational position (e.g., a ninety degree position) may cause the burner valve to be instructed, commanded, and signaled (e.g., by the controller144) to a first partially-open position (e.g., a 10% open position), and/or may cause several (e.g., between one and four) sequentially-arranged ones of the LEDs802to be instructed, commanded, and/or signaled (e.g., by the controller144) to progressively illuminate (e.g., in a specific color, such as red).

Continuing with such an example, further rotation of the control knob808in the clockwise direction to a third relative rotational position (e.g., a one hundred and eighty degree position) may cause the burner valve to be instructed, commanded, and signaled (e.g., by the controller144) to a second partially-open position (e.g., a 50% open position), and/or may cause several (e.g., between five and eight) sequentially-arranged ones of the LEDs802to be instructed, commanded, and/or signaled (e.g., by the controller144) to progressively illuminate (e.g., in a specific color, such as red). Still further rotation of the control knob808in the clockwise direction to a fourth relative rotational position (e.g., a two hundred and seventy degree position) may cause the burner valve to be instructed, commanded, and signaled (e.g., by the controller144) to a fully-open position (e.g., a 100% open position), and/or may cause several (e.g., between twelve and sixteen) sequentially-arranged ones of the LEDs802to be instructed, commanded, and/or signaled (e.g., by the controller144) to progressively illuminate (e.g., in a specific color, such as red).

FIG.10a front view of another example control assembly1000that may be implemented in place of one of the user-interface assemblies120ofFIG.1. In the illustrated example ofFIG.10, the control assembly1000includes a plurality of example LEDs1002mounted to, positioned on, and/or otherwise located relative to an example control panel1004. As shown inFIG.10, the LEDs1002are configured as an example linear series1006(e.g., a vertically-oriented column, a horizontally-oriented row, etc.), with the linear series1006being positioned between a first example control button1008and a second example control button1010that are also mounted to, positioned on, and/or otherwise located relative to the control panel1004.

In the illustrated example ofFIG.10, the LEDs1002of the control assembly1000can be either individually or collectively controllable to transition from an off state (e.g., a non-light-projecting state) to an on state (e.g., a light-projecting state) and vice-versa, in response to instructions, commands, and/or signals (e.g., a supply of current) generated by the controller144of the grill100. In this regard, the LEDs1002can be individually or collectively commanded (e.g., by the controller144) to illuminate in a manner that causes one or more of the LEDs1002to appear as being constantly lit (e.g., in a constant light-projecting state) over a duration of time. The LEDs1002can alternatively be individually or collectively commanded (e.g., by the controller144) to illuminate in a manner that causes one or more of the LEDs1002to appear as being periodically lit and/or blinking (e.g., switching up and back between a light-projecting state and a non-light-projecting state) over a duration of time. The LEDs1002can alternatively be individually or collectively commanded (e.g., by the controller144) to cease illuminating such that one or more of the LEDs1002appear(s) as being constantly unlit (e.g., in a constant non-light-projecting state) over a duration of time.

In some examples, the LEDs1002of the control assembly1000ofFIG.10are implemented as multi-color LEDs that can be individually or collectively commanded (e.g., by the controller144) to illuminate in different colors (e.g., white, red, blue, etc.) of the color spectrum.

Returning to the illustrated example ofFIG.1, the user interface134ofFIG.1includes one or more input device(s)136(e.g., buttons, dials, knobs, switches, touchscreens, etc.) and/or one or more output device(s)138(e.g., liquid crystal displays, light emitting diodes, speakers, etc.) that enable a user of the grill100to interact with the above-described control system of the grill100. In some examples, the output device(s)138of the user interface134can include the lighting circuitry650described above. The output device(s)138of the user interface134can be configured to present one or more notification(s) textually (e.g., as a written notification, message, or alert), graphically (e.g., as an illustrated or viewable notification, message, or alert), and/or audibly (e.g., as an audible notification, message, or alert). For example, the output device(s)138of the user interface134can be configured to textually (e.g., as a written notification, message, or alert), graphically (e.g., as an illustrated or viewable notification, message, or alert), and/or audibly (e.g., as an audible notification, message, or alert) inform the user of the grill100that a control knob is in a specific rotational position. As another example, the output device(s)138of the user interface134can be configured to textually (e.g., as a written notification, message, or alert), graphically (e.g., as an illustrated or viewable notification, message, or alert), and/or audibly (e.g., as an audible notification, message, or alert) inform the user of the grill100that a burner valve (e.g., the first burner valve112or the second burner valve114) of the grill100is in a specific operational position (e.g., a fully-closed position, a partially-open position, a fully-open position, etc.).

In the illustrated example ofFIG.1, the user interface134is operatively coupled to (e.g., in electrical communication with) the controller144and/or the memory150of the grill100. In some examples, the user interface134is mechanically coupled to (e.g., fixedly connected to) the grill100. For example, the user interface134can be mounted to the cookbox202, the lid204, the handle206, the frame208, the cabinet210, the control panel212, the first side table214, and/or the second side table216of the grill100. The user interface134is preferably mounted to a portion of the grill100that is readily accessible to a user of the grill100, such as a front portion of the cookbox202, a front portion of the lid204, a front portion of the handle206, a front portion of the frame208, a front portion of the cabinet210, a front portion of the control panel212, a front portion of the first side table214, and/or a front portion of the second side table216of the grill100.

In some examples, respective ones of the input device(s)136and/or the output device(s)138of the user interface134can be mounted to different portions of the grill100. For example, a first one of the input device(s)136can be mounted to a side portion of either the cookbox202, the lid204, the handle206, the frame208, the cabinet210, the control panel212, the first side table214, or the second side table216of the grill100, and a second one of the input device(s)136can be mounted to a front portion of either the cookbox202, the lid204, the handle206, the frame208, the cabinet210, the control panel212, the first side table214, or the second side table216of the grill100. The architecture and/or operations of the user interface134can be distributed among any number of user interfaces respectively having any number of input device(s)136and/or output device(s)138located at and/or mounted to any portion of the grill100.

FIG.11is diagram of an example connector1100that may be used to connect either the controller144or one of the user-interface assemblies120,122,124ofFIG.1to another one of the user-interface assemblies120,122,124ofFIG.1. The example connector1100includes the output wiring harness690ofFIG.6, wires1105, the input wiring harness680ofFIG.6, and the addressing block682ofFIG.6. The output wiring harness690is to be connected to the controller144, or to one of the user-interface assemblies120,122,124. The input wiring harness680is to be connected to one of the user-interface assemblies120,122,124. In this manner, the connector1100can be used in a daisy chain configuration to connect multiple ones of the user-interface assemblies120,122,124to the controller144.

In the illustrated example ofFIG.11, the addressing block682is used to specify an address to be used by the user-interface assembly to which it is connected. In this manner, different addressing blocks may be used when connecting to different user-interface assemblies. For example, a first addressing block may identify to the user-interface assembly to which it is connected that the user-interface assembly is a first user-interface assembly in the grill, while a second addressing block may identify to the user-interface assembly to which it is connected that the user-interface assembly is a second user-interface assembly in the grill, etc. Such an approach reduces the need for users and/or installers to select addresses by using jumpers on the user-interface assemblies.

FIG.12a front view of an example user interface1200that can be implemented by or as the user interface134of the grill100ofFIG.1. As shown inFIG.12, the user interface1200includes an example dial1202, an example first button1204, an example second button1206, and an example third button1208that can be implemented by or as the input device(s)136of the user interface134ofFIG.1, and an example display1210that can be implemented by or as the output device(s)138of the user interface134ofFIG.1. In the illustrated example ofFIG.12, the dial1202of the user interface1200is a selection dial that can be rotated by a user of the grill100to adjust temperatures of the grill100, and/or to navigate through options presented on the display1210of the user interface1200. In addition to being rotatable, the dial1202can also be pushed by a user of the grill100to make and/or confirm a selection of one of the options presented on the display1210. The first button1204of the user interface1200is a menu button that can be pressed by a user of the grill100to access a main menu (e.g., a “home” menu) of selectable options, and to cause the main menu to be presented on the display1210of the user interface1200. The second button1206of the user interface1200is a cook program button that can be pressed by a user of the grill100to access a library of selectable cook programs, and to cause steps, instructions, operations, notifications, and/or alerts associated with the selectable cook programs to be presented on the display1210of the user interface1200. The third button1208of the user interface1200is a timer button that can be pressed by a user of the grill100to initiate a timer, and to cause the running time associated with the timer to be presented on the display1210of the user interface1200. The display1210of the user interface1200is a liquid crystal display configured to present textual and/or graphical information to a user of the grill100. In some examples, the display1210can be implemented as a touch screen, in which case the display1210can be implemented not only as one of the output device(s)138of the user interface134, but also as another one of the input device(s)136of the user interface134.

In some examples, one or more notification(s) presented via the display1210of the user interface1210may inform the user of the grill100of a specific rotational position of a control knob of the grill100. For example, the display1210of the user interface1200may textually (e.g., as a written notification, message, or alert), graphically (e.g., as an illustrated or viewable notification, message, or alert), and/or audibly (e.g., as an audible notification, message, or alert) inform the user of the grill100that a control knob of the grill100is/are in a specific rotational position. As another example, the display1210of the user interface1200may textually (e.g., as a written notification, message, or alert), graphically (e.g., as an illustrated or viewable notification, message, or alert), and/or audibly (e.g., as an audible notification, message, or alert) inform the user of the grill100that a burner valve (e.g., the first burner valve112or the second burner valve114) of the grill100is in a specific operational position.

The network interface140ofFIG.1includes one or more communication device(s)142(e.g., transmitter(s), receiver(s), transceiver(s), modem(s), gateway(s), wireless access point(s), etc.) to facilitate exchange of data with external machines (e.g., computing devices of any kind, including the remote device(s)152ofFIG.1) by a wired or wireless communication network. Communications transmitted and/or received via the communication device(s)142and/or, more generally, via the network interface140can be made over and/or carried by, for example, an Ethernet connection, a digital subscriber line (DSL) connection, a telephone line connection, a coaxial cable system, a satellite system, a wireless system, a cellular telephone system, an optical connection, etc. The network interface140enables a user of the grill100to remotely interact (e.g., via one or more of the remote device(s)152) with the above-described control system of the grill100. In the illustrated example ofFIG.1, the network interface140is operatively coupled to (e.g., in electrical communication with) the controller144and/or the memory150of the grill100.

The remote device(s)152ofFIG.1can be implemented by any type(s) and/or any number(s) of mobile or stationary computing devices. In this regard, examples of such remote device(s)152include a smartphone, a tablet, a laptop, a desktop, a cloud server, a wearable computing device, etc. The remote device(s)152ofFIG.1facilitate a remote (e.g., wired, or wireless) extension of the above-described user interface134of the grill100. In this regard, each remote device152includes one or more input device(s) and/or one or more output device(s) that mimic and/or enable a remotely-located version of the above-described functionality of the corresponding input device(s)136and/or the corresponding output device(s)138of the user interface134of the grill100. Accordingly, one or more notification(s) transmitted from the grill100(e.g., via the communication device(s)142of the network interface140of the grill100) can be presented via the output device(s) of the remote device(s)152much in the same way that such notification(s) would be presented via the output device(s)138of the user interface134of the grill100.

The controller144ofFIG.1manages and/or controls the control system of the grill100and/or the components thereof. In the illustrated example ofFIG.1, the controller144is operatively coupled to (e.g., in electrical communication with) the fuel source valve108, the first burner valve112, the second burner valve114, the first ignitor116, the second ignitor118, the user-interface assemblies120,122,124, the temperature sensor128, the flame sensor(s)130, the user interface134(e.g., including the input device(s)136and the output device(s)138), the network interface140(e.g., including the communication device(s)142), and/or the memory150of the grill100ofFIG.1. The controller144ofFIG.1is also operatively coupled to (e.g., in wired or wireless electrical communication with) the remote device(s)152ofFIG.1via the network interface140(e.g., including the communication device(s)142) of the grill100ofFIG.1. In the illustrated example ofFIG.1, the controller144includes the control circuitry146and the detection circuitry148ofFIG.1, each of which is discussed in further detail herein. The control circuitry146, the detection circuitry148, and/or, more generally, the controller144ofFIG.1can individually and/or collectively be implemented by any type(s) and/or any number(s) of semiconductor device(s) (e.g., processor(s), microprocessor(s), microcontroller(s), etc.) and/or circuit(s).

In the illustrated example ofFIG.1, the controller144is graphically represented as a single, discrete structure that manages and/or controls the operation(s) of various components of the control system of the grill100. It is to be understood, however, that in other examples, the architecture and/or operations of the controller144can be distributed among any number of controllers, with each separate controller having a dedicated subset of one or more operation(s) described herein. As but one example, the controller144ofFIG.1can be separated into two distinct controllers, whereby a first one of the two controllers includes the control circuitry146of the controller144, and a second one of the two controllers includes the detection circuitry148of the controller144. In some examples, the grill100can further include separate, distinct controllers for one or more of the fuel source valve108, the first burner valve112, the second burner valve114, the first ignitor116, the second ignitor118, the user-interface assemblies120,122,124, the temperature sensor128, the flame sensor(s)130, the user interface134(e.g., including the input device(s)136and the output device(s)138), the network interface140(e.g., including the communication device(s)142), and/or the memory150of the grill100ofFIG.1.

The controller144ofFIG.1manages and/or controls the implementation and/or execution of one or more process(es), protocol(s), program(s), sequence(s), and/or method(s) associated with controlling the flow of gas through the first burner valve112and/or the second burner valve114of the grill100ofFIG.1based on position data detected via the user-interface assemblies120,122,124of the grill100ofFIG.1. In some examples, the controller144ofFIG.1additionally or alternatively manages and/or controls the implementation and/or execution of one or more process(es), protocol(s), program(s), sequence(s), and/or method(s) associated with causing the lighting circuitry650ofFIG.6to present one or more notification(s) indicating the rotational position(s) of the control knob640ofFIG.6, and/or to present one or more notification(s) indicating the target position(s) of the first burner valve112and/or the second burner valve114of the grill100ofFIG.1. In some examples, the controller144ofFIG.1additionally or alternatively manages and/or controls the implementation and/or execution of one or more process(es), protocol(s), program(s), sequence(s), and/or method(s) associated with causing one or more of the output device(s)138of the user interface134of the grill100ofFIG.1to present one or more notification(s) indicating the rotational position(s) of the control knob of the first user-interface assembly120and/or the control knob of the second user-interface assembly122of the grill100ofFIG.1, and/or to present one or more notification(s) indicating the target position(s) of the first burner valve112and/or the second burner valve114of the grill100ofFIG.1. In some examples, the controller144ofFIG.1additionally or alternatively manages and/or controls the implementation and/or execution of one or more process(es), protocol(s), program(s), sequence(s), and/or method(s) associated with causing one or more notification(s) indicating the rotational position(s) of the control knob of the first user-interface assembly120and/or the control knob of the second user-interface assembly122of the grill100ofFIG.1, and/or one or more notification(s) indicating the target position(s) of the first burner valve112and/or the second burner valve114of the grill100ofFIG.1, to be presented at one or more of the remote device(s)152ofFIG.1that is/are in electrical communication with the grill100ofFIG.1.

The control circuitry146of the controller144ofFIG.1manages and/or controls one or more operation(s) of one or more controllable component(s) of the grill100that is/are operatively coupled to (e.g., in electrical communication with) the controller144of the grill100. For example, the control circuitry146may include valve control circuitry configured to instruct, command, signal, and/or otherwise cause the fuel source valve108, the first burner valve112, and/or the second burner valve114of the grill100to open (e.g., fully open), to close (e.g., fully close), or to otherwise change position. The control circuitry146may additionally or alternatively include ignitor control circuitry configured to instruct, command, signal, and/or otherwise cause the first ignitor116and/or the second ignitor118of the grill100to ignite corresponding ones of the first burner102and/or the second burner104of the grill100. The control circuitry146may additionally or alternatively include lighting control circuitry configured to instruct, command, signal, and/or otherwise cause one or more light source(s) of the lighting circuitry650ofFIG.6to transition (e.g., once, or repeatedly) from an off state (e.g., a non-light-projecting state) to an on state (e.g., a light-projecting state), or vice-versa. In some examples, the transitioning of the one or more light source(s) of the lighting circuitry650ofFIG.6from the off state to the on state, or vice-versa, effects the presentation of one or more notification(s) (e.g., one or more visible message(s) or alert(s)).

The control circuitry146may additionally or alternatively include user interface control circuitry configured to instruct, command, signal, and/or otherwise cause one or more of the output device(s)138of the user interface134of the grill100to textually, graphically, or audibly present data and/or information, which may include one or more notification(s) (e.g., one or more visible, audible, and/or tactile message(s) or alert(s)). The control circuitry146may additionally or alternatively include network interface control circuitry configured to instruct, command, signal, and/or otherwise cause one or more of the communication device(s)142of the network interface140of the grill100to transmit data and/or information, which may include one or more notification(s) (e.g., one or more visible, audible, and/or tactile message(s) or alert(s)) to one or more of the remote device(s)152ofFIG.1.

The detection circuitry148of the controller144ofFIG.1detects and/or determines one or more state(s), condition(s), operation(s), and/or event(s) associated with the grill100based on data, information, and/or signals received from one or more component(s) of the grill100that is/are operatively coupled to (e.g., in wired or wireless electrical communication with) the controller144of the grill100. For example, the detection circuitry148may include valve detection circuitry configured to detect and/or determine a relative position of the fuel source valve108, the first burner valve112, and/or the second burner valve114of the grill100based on one or more instruction(s), command(s), and/or signal(s) generated at the control circuitry146of the controller144and/or transmitted to the fuel source valve108, the first burner valve112, and/or the second burner valve114.

The detection circuitry148may additionally or alternatively include encoder detection circuitry configured to detect and/or determine a relative position (e.g., a relative rotational position) of one or more control knob(s) associated with corresponding ones of the user-interface assemblies120,122,124. The detection circuitry148may additionally or alternatively include temperature detection circuitry configured to detect and/or determine one or more temperature state(s), condition(s), operation(s), and/or event(s) associated with the grill100(e.g., that a temperature of the cooking chamber302of the grill100is either above or below a predetermined temperature threshold) based on data, information, and/or signals received from the temperature sensor128of the grill100. The detection circuitry148may additionally or alternatively include flame detection circuitry configured to detect and/or determine the presence or the absence of a flame at the first burner102and/or the second burner104of the grill100based on data, information, and/or signals received from one or more of the flame sensor(s)130of the grill100.

The detection circuitry148may additionally or alternatively include user interface detection circuitry configured to detect and/or determine one or more user interface state(s), condition(s), operation(s), and/or event(s) associated with the grill100(e.g., that a user has interacted with one or more of the input device(s)136of the user interface134, that a user has failed to interact with one or more of the input device(s)136of the user interface134, etc.) based on data, information, and/or signals received from the user interface134of the grill100. The detection circuitry148may additionally or alternatively include network interface detection circuitry configured to detect and/or determine one or more network interface state(s), condition(s), operation(s), and/or event(s) associated with the grill100(e.g., that one or more of the communication device(s)142of the network interface140has received data, information, and/or signals indicating that a user has interacted with one or more input device(s) of one or more of the remote device(s)152, that one or more of the communication device(s)142of the network interface140has failed to receive data, information, and/or signals indicating that a user has interacted with one or more input device(s) of one or more of the remote device(s)152, etc.) based on data, information, and/or signals received from the network interface140of the grill100.

In some examples, the controller144of the grill100ofFIG.1is configured to implement a gas flow control process. In some examples, the detection circuitry148of the controller144ofFIG.1is configured to determine a rotational position of a control knob (e.g., a control knob of the first user-interface assembly120ofFIG.1) of the grill100ofFIG.1based on position data sensed, measured, and/or detected (e.g., continuously, or periodically) via a sensor of a corresponding one of the user-interface assemblies120,122,124to which the control knob is mechanically coupled. In some examples, the detection circuitry148of the controller144is further configured to determine a target position of a burner valve (e.g., the first burner valve112or the second burner valve114ofFIG.1) of the grill100based on the rotational position of the control knob of the grill100. For example, the detection circuitry148of the controller144may be configured to determine the target position of the burner valve of the grill100by accessing a correlation table (e.g., as may be stored in the memory150of the grill100) that establishes and/or defines one or more correlation(s) and/or relationship(s) between one or more position(s) (e.g., one or more rotational position(s)) of the rotary encoder and/or the control knob of the grill100ofFIG.1on the one hand, and one or more position(s) (e.g., one or more target position(s)) of the burner valve of the grill100ofFIG.1on the other hand (e.g., the target position of the burner valve is Y percent open when the relative rotational position of the control knob is X degrees). In some examples, the control circuitry146of the controller144ofFIG.1is configured to instruct, command, signal, and/or otherwise cause the burner valve (e.g., the first burner valve112or the second burner valve114ofFIG.1) of the grill100ofFIG.1to move to the target position of the burner valve.

In some examples, the controller144of the grill100ofFIG.1is configured to implement a control knob position notification process. In some examples, the detection circuitry148of the controller144ofFIG.1is configured to determine a rotational position of a control knob of the grill100ofFIG.1based on position data sensed, measured, and/or detected (e.g., continuously, or periodically) via communicating with the user-interface assembly(ies) of the grill100. In some examples, the control circuitry146of the controller144ofFIG.1is configured to generate one or more notification(s) (e.g., visible, audible, and/or tactile message(s) or alert(s)) indicating the rotational position of the control knob of the grill100ofFIG.1.

In some examples, the control circuitry146of the controller144ofFIG.1is configured to instruct, command, signal, and/or otherwise cause the notification(s) indicating the rotational position of the control knob of the grill100ofFIG.1to be presented locally and/or remotely. For example, the control circuitry146may be configured to instruct, command, signal, and/or otherwise cause the lighting circuitry650ofFIG.6to locally present one or more of the notification(s) indicating the rotational position of the control knob of the grill100. The control circuitry146may additionally or alternatively be configured to instruct, command, signal, and/or otherwise cause the user interface134of the grill100ofFIG.1to locally present (e.g., via one or more of the output device(s)138of the user interface134) one or more of the notification(s) indicating the rotational position of the control knob of the grill100. The control circuitry146may additionally or alternatively be configured to instruct, command, signal, and/or otherwise cause the network interface140of the grill100ofFIG.1to transmit (e.g., via one or more of the communication device(s)142of the network interface140) one or more of the notification(s) indicating the rotational position of the control knob of the grill100to one or more of the remote device(s)152ofFIG.1for remote presentation via one or more of the output device(s) of the remote device(s)152. In some examples, one or more of the notification(s) indicating the rotational position of the control knob of the grill100may be presented for a predetermined duration (e.g., a predetermined presentation duration, as may be stored in the memory150of the grill100). In other examples, one or more of the notification(s) indicating the rotational position of the control knob of the grill100may be presented until a countering event (e.g., determining that the rotational position of the control knob of the grill100has changed, receiving a request, command, and/or instruction to terminate the presentation of the notification(s), etc.) occurs.

In some examples, the controller144of the grill100ofFIG.1is configured to implement a burner valve position notification process. In some examples, the detection circuitry148of the controller144ofFIG.1is configured to determine a position (e.g., a current operational position) of a burner valve (e.g., the first burner valve112or the second burner valve114ofFIG.1) of the grill100ofFIG.1. For example, the detection circuitry148may be configured to determine the position of the burner valve of the grill100based on one or more instruction(s), command(s), and/or signal(s) previously generated at the control circuitry146of the controller144and/or previously transmitted to the burner valve of the grill100. The control circuitry146of the controller144ofFIG.1is configured to generate one or more notification(s) (e.g., visible, audible, and/or tactile message(s) or alert(s)) indicating the position of the burner valve of the grill100ofFIG.1.

In some examples, the control circuitry146of the controller144ofFIG.1is configured to instruct, command, signal, and/or otherwise cause the notification(s) indicating the position of the burner valve of the grill100ofFIG.1to be presented locally and/or remotely. For example, the control circuitry146may be configured to instruct, command, signal, and/or otherwise cause the lighting circuitry650ofFIG.6to locally present one or more of the notification(s) indicating the position of the burner valve of the grill100. The control circuitry146may additionally or alternatively be configured to instruct, command, signal, and/or otherwise cause the user interface134of the grill100ofFIG.1to locally present (e.g., via one or more of the output device(s)138of the user interface134) one or more of the notification(s) indicating the position of the burner valve of the grill100. The control circuitry146may additionally or alternatively be configured to instruct, command, signal, and/or otherwise cause the network interface140of the grill100ofFIG.1to transmit (e.g., via one or more of the communication device(s)142of the network interface140) one or more of the notification(s) indicating the position of the burner valve of the grill100to one or more of the remote device(s)152ofFIG.1for remote presentation via one or more of the output device(s) of the remote device(s)152. In some examples, one or more of the notification(s) indicating the position of the burner valve of the grill100may be presented for a predetermined duration (e.g., a predetermined presentation duration, as may be stored in the memory150of the grill100). In other examples, one or more of the notification(s) indicating the position of the burner valve of the grill100may be presented until a countering event (e.g., determining that the position of the burner valve of the grill100has changed, receiving a request, command, and/or instruction to terminate the presentation of the notification(s), etc.) occurs.

The memory150ofFIG.1can be implemented by any type(s) and/or any number(s) of storage device(s) such as a storage drive, a flash memory, a read-only memory (ROM), a random-access memory (RAM), a cache and/or any other physical storage medium in which information is stored for any duration (e.g., for extended time periods, permanently, brief instances, for temporarily buffering, and/or for caching of the information). The information stored in the memory150ofFIG.1can be stored in any file and/or data structure format, organization scheme, and/or arrangement.

The memory150stores data sensed, measured, detected, generated, accessed, input, output, transmitted, and/or received by, to, and/or from the fuel source valve108, the first burner valve112, the second burner valve114, the first ignitor116, the second ignitor118, the user-interface assemblies120,122,124, the temperature sensor128, the flame sensor(s)130, the user interface134(e.g., including the input device(s)136and the output device(s)138), the network interface140(e.g., including the communication device(s)142), the controller144(e.g., including the control circuitry146and the detection circuitry148), the remote device(s)152, and/or, more generally, the control system of the grill100ofFIG.1. The memory150also stores instructions (e.g., machine-readable instructions) and associated data (e.g., correlation data including, for example, one or more correlation table(s), etc.) corresponding to the processes, protocols, programs, sequences, and/or methods described below in connection withFIGS.12-14. The memory150ofFIG.1is accessible to one or more of the fuel source valve108, the first burner valve112, the second burner valve114, the first ignitor116, the second ignitor118, the user-interface assemblies120,122,124, the temperature sensor128, the flame sensor(s)130, the user interface134(e.g., including the input device(s)136and the output device(s)138), the network interface140(e.g., including the communication device(s)142), the controller144(e.g., including the control circuitry146and the detection circuitry148), the remote device(s)152, and/or, more generally, the control system of the grill100ofFIG.1.

While an example manner of implementing the control system of the grill100is illustrated inFIG.1, one or more of the elements, processes, and/or devices illustrated inFIG.1may be combined, divided, re-arranged, omitted, eliminated, and/or implemented in any other way. Further, the example fuel source valve108, the example first burner valve112, the example second burner valve114, the example first ignitor116, the example second ignitor118, the example user-interface assemblies120,122,124, the example temperature sensor128, the example flame sensor(s)130, the example user interface134(e.g., including the example input device(s)136and the example output device(s)138), the example network interface140(e.g., including the example communication device(s)142), the example controller144(e.g., including the example control circuitry146and the example detection circuitry148), the example memory150, and/or, more generally, the control system of the grill100ofFIG.1, may be implemented by hardware alone or by hardware in combination with software and/or firmware. Thus, for example, any of the example fuel source valve108, the example first burner valve112, the example second burner valve114, the example first ignitor116, the example second ignitor118, the example user-interface assemblies120,122,124, the example temperature sensor128, the example flame sensor(s)130, the example user interface134(e.g., including the example input device(s)136and the example output device(s)138), the example network interface140(e.g., including the example communication device(s)142), the example controller144(e.g., including the example control circuitry146and the example detection circuitry148), the example memory150, and/or, more generally, the control system of the grill100ofFIG.1, could be implemented by processor circuitry, analog circuit(s), digital circuit(s), logic circuit(s), programmable processor(s), programmable microcontroller(s), graphics processing unit(s) (GPU(s)), digital signal processor(s) (DSP(s)), application specific integrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)), and/or field programmable logic device(s) (FPLD(s)) such as Field Programmable Gate Arrays (FPGAs). Further still, the example control system of the grill ofFIG.1may include one or more elements, processes, and/or devices in addition to, or instead of, those illustrated inFIG.1, and/or may include more than one of any or all of the illustrated elements, processes, and devices.

In another example, the machine-readable instructions may be stored in a state in which they may be read by processor circuitry, but require 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 machine-readable instructions on a particular computing device or any other device. In another example, the machine-readable instructions may need to be configured (e.g., settings stored, data input, network addresses recorded, etc.) before the machine-readable instructions and/or the corresponding program(s) can be executed in whole or in part. Thus, machine-readable media, as used herein, may include machine-readable instructions and/or program(s) regardless of the particular format or state of the machine-readable instructions and/or program(s) when stored or otherwise at rest or in transit.

As mentioned above, the example operations ofFIGS.13-14may be implemented using executable instructions (e.g., computer and/or machine-readable instructions) stored on one or more non-transitory computer and/or machine-readable media such as optical storage devices, magnetic storage devices, an HDD, a flash memory, a read-only memory (ROM), a CD, a DVD, a cache, a RAM of any type, a register, and/or any other storage device or storage disk in which information is stored for any duration (e.g., for extended time periods, permanently, for brief instances, for temporarily buffering, and/or for caching of the information). As used herein, the terms “non-transitory computer-readable medium” and “non-transitory computer-readable storage medium” are expressly defined to include any type of computer-readable storage device and/or storage disk and to exclude propagating signals and to exclude transmission media.

FIG.13is a flowchart representative of example machine-readable instructions and/or example operations1300that may be executed by processor circuitry to implement a connection initialization process of the user-interface assembly120ofFIG.1. The machine-readable instructions and/or operations1300ofFIG.13begin at block1310when the user-interface controller circuitry620detects a wiring harness connected via the addressing terminals. (Block1310). The addressing terminals are, in turn, connected to the addressing block, which selects an identifier to be used by the user-interface controller circuitry620when communicating with the controller144. The user-interface controller circuitry620configures an address based on the detected addressing block. (Block1320). Using the configured address, the user-interface controller circuitry620then enables communication with the controller144. (Block1330). It should be understood that, when different addressing blocks are used for different user-interface assemblies, such various user-interface assemblies will communicate with the controller144using different addresses.

FIG.14is a flowchart representative of example machine-readable instructions and/or example operations1400that may be executed by processor circuitry to communicate with one or more user-interface assemblies communicating via a controller bus and/or a lighting bus. The machine-readable instructions and/or operations1400ofFIG.14begin at block1410when the controller144detects one or more user-interface assemblies communicating via the controller bus. (Block1410). The controller144identifies a number of user-interface assemblies communicating via the controller bus. (Block1420). In examples disclosed herein, the controller detect the number of user-interface assemblies based on the number of unique user-interface assembly addresses. Using the number of user-interface assembly addresses and, in some examples, statistics about the connected user-interface assemblies provided via the controller bus, the example controller144configures addresses used by the lighting circuitry(ies) of the connected user-interface assemblies. (Block1430). In examples disclosed herein, because the lighting bus is implemented in a serial fashion, the LEDs of lighting circuitry within a first user-interface assembly are addressed lower than addresses of LEDs of lighting circuitry within a second user-interface assembly.

The controller144receives control information from the user-interface assembly(ies) via the controller bus. (Block1440). Such control information may include, for example rotation positions of the knobs, whether the knob is depressed (e.g., to initiate ignition of a corresponding burner), etc. Based on the received control information, the example controller144controls operations of the grill100including, for example, setting a position of a gas valve, enabling an igniter, controlling lighting circuitry(ies) of the user-interface assemblies, communicating with a remote device, etc. (Block1450).

FIG.15is a block diagram of an example processor platform1500including processor circuitry structured to execute and/or instantiate the machine-readable instructions and/or operations ofFIGS.13-14to implement the grill100ofFIG.1. The processor platform1500of the illustrated example includes processor circuitry1502. The processor circuitry1502of the illustrated example is hardware. For example, the processor circuitry1502can be implemented by one or more integrated circuit(s), logic circuit(s), FPGA(s), microprocessor(s), CPU(s), GPU(s), DSP(s), and/or microcontroller(s) from any desired family or manufacturer. The processor circuitry1502may be implemented by one or more semiconductor based (e.g., silicon based) device(s). In this example, the processor circuitry1502implements the controller144ofFIG.1, including the control circuitry146and the detection circuitry148of the controller144.

The processor circuitry1502of the illustrated example includes a local memory1504(e.g., a cache, registers, etc.). The processor circuitry1502is in electrical communication with one or more valve(s)1506via a bus1508. In this example, the valve(s)1506include the fuel source valve108, the first burner valve112, the second burner valve114, and the “Nth” burner valve115ofFIG.1. The processor circuitry1502is also in electrical communication with one or more ignitor(s)1510via the bus1508. In this example, the ignitor(s)1510include the first ignitor116, the second ignitor118, and the “Nth” ignitor119ofFIG.1. The processor circuitry1502is also in electrical communication with one or more sensor(s)1512via the bus1508. In this example, the sensor(s)1512include the temperature sensor128and the flame sensor(s)130ofFIG.1. The processor circuitry1502is also in electrical communication with one or more user-interface assembly(ies)1514via the bus1508. In this example, the user-interface assembly(ies)1514include the user-interface assemblies120,122,124ofFIG.1, which in turn include the lighting circuitries of the corresponding user-interface assemblies600ofFIG.6.

The processor circuitry1502is also in electrical communication with a main memory via the bus1508, with the main memory including a volatile memory1516and a non-volatile memory1518. The volatile memory1516may be implemented by Synchronous Dynamic Random Access Memory (SDRAM), Dynamic Random Access Memory (DRAM), RAMBUS® Dynamic Random Access Memory (RDRAM®), and/or any other type of RAM device. The non-volatile memory1518may be implemented by flash memory and/or any other desired type of memory device. Access to the main memory1516,1518of the illustrated example is controlled by a memory controller.

The processor platform1500of the illustrated example also includes one or more mass storage device(s)1520to store software and/or data. Examples of such mass storage device(s)1520include magnetic storage devices, optical storage devices, floppy disk drives, HDDs, CDs, Blu-ray disk drives, redundant array of independent disks (RAID) systems, solid state storage devices such as flash memory devices, and DVD drives. In the illustrated example ofFIG.15, one or more of the volatile memory1516, the non-volatile memory1518, and/or the mass storage device(s)1520implement(s) the memory150ofFIG.1.

The processor platform1500of the illustrated example also includes user interface circuitry1522. The user interface circuitry1522may be implemented by hardware in accordance with any type of interface standard, such as an Ethernet interface, a universal serial bus (USB) interface, a Bluetooth® interface, a near field communication (NFC) interface, a PCI interface, and/or a PCIe interface. In the illustrated example, one or more input device(s)136are connected to the user interface circuitry1522. The input device(s)136permit(s) a user to enter data and/or commands into the processor circuitry1502. The input device(s)136can be implemented by, for example, one or more button(s), dial(s), knob(s), switch(es), touchscreen(s), audio sensor(s), microphone(s), image sensor(s), and/or camera(s). One or more output device(s)138are also connected to the user interface circuitry1522of the illustrated example. The output device(s)138can be implemented, for example, by one or more display device(s) (e.g., light emitting diode(s) (LED(s)), organic light emitting diode(s) (OLED(s)), liquid crystal display(s) (LCD(s)), cathode ray tube (CRT) display(s), in-place switching (IPS) display(s), touchscreen(s), etc.), tactile output device(s), and/or speaker(s). The user interface circuitry1522of the illustrated example, thus, typically includes a graphics driver card, a graphics driver chip, and/or graphics processor circuitry such as a GPU. In the illustrated example ofFIG.15, the user interface circuitry1522, the input device(s)136, and the output device(s)138collectively implement the user interface134ofFIG.1.

The processor platform1500of the illustrated example also includes network interface circuitry1524. The network interface circuitry1524includes one or more communication device(s) (e.g., transmitter(s), receiver(s), transceiver(s), modem(s), gateway(s), wireless access point(s), etc.) to facilitate exchange of data with external machines (e.g., computing devices of any kind, including the remote device(s)152ofFIG.1) by a network1526. The communication can be by, for example, an Ethernet connection, a digital subscriber line (DSL) connection, a telephone line connection, a coaxial cable system, a satellite system, a wireless system, a cellular telephone system, an optical connection, etc. In the illustrated example ofFIG.15, the network interface circuitry1524implements the network interface140(e.g., including the communication device(s)142) ofFIG.1.

Coded instructions1528including the above-described machine-readable instructions and/or operations ofFIGS.13-14may be stored the local memory1504, in the volatile memory1516, in the non-volatile memory1518, on the mass storage device(s)1520, and/or on a removable non-transitory computer-readable storage medium such as a flash memory stick, a dongle, a CD, or a DVD.

FIG.16is a block diagram of an example implementation of the processor circuitry1502ofFIG.15. In this example, the processor circuitry1502ofFIG.15is implemented by a microprocessor1600. For example, the microprocessor1600may implement multi-core hardware circuitry such as a CPU, a DSP, a GPU, an XPU, etc. Although it may include any number of example cores1602(e.g., 1 core), the microprocessor1600of this example is a multi-core semiconductor device including N cores. The cores1602of the microprocessor1600may operate independently or may cooperate to execute machine-readable instructions. For example, machine code corresponding to a firmware program, an embedded software program, or a software program may be executed by one of the cores1602or may be executed by multiple ones of the cores1602at the same or different times. In some examples, the machine code corresponding to the firmware program, the embedded software program, or the software program is split into threads and executed in parallel by two or more of the cores1602. The software program may correspond to a portion or all of the machine-readable instructions and/or operations represented by the flowcharts ofFIGS.13-14.

The cores1602may communicate by an example bus1604. In some examples, the bus1604may implement a communication bus to effectuate communication associated with one(s) of the cores1602. For example, the bus1604may implement at least one of an Inter-Integrated Circuit (I2C) bus, a Serial Peripheral Interface (SPI) bus, a PCI bus, or a PCIe bus. Additionally, or alternatively, the bus1604may implement any other type of computing or electrical bus. The cores1602may obtain data, instructions, and/or signals from one or more external devices by example interface circuitry1606. The cores1602may output data, instructions, and/or signals to the one or more external devices by the interface circuitry1606. Although the cores1602of this example include example local memory1620(e.g., Level 1 (L1) cache that may be split into an L1 data cache and an L1 instruction cache), the microprocessor1600also includes example shared memory1610that may be shared by the cores (e.g., Level 2 (L2_ cache)) for high-speed access to data and/or instructions. Data and/or instructions may be transferred (e.g., shared) by writing to and/or reading from the shared memory1610. The local memory1620of each of the cores1602and the shared memory1610may be part of a hierarchy of storage devices including multiple levels of cache memory and the main memory (e.g., the main memory1516,1518ofFIG.15). Typically, higher levels of memory in the hierarchy exhibit lower access time and have smaller storage capacity than lower levels of memory. Changes in the various levels of the cache hierarchy are managed (e.g., coordinated) by a cache coherency policy.

Each core1602may be referred to as a CPU, DSP, GPU, etc., or any other type of hardware circuitry. Each core1602includes control unit circuitry1614, arithmetic and logic (AL) circuitry (sometimes referred to as an ALU)1616, a plurality of registers1618, the L1 cache1620, and an example bus1622. Other structures may be present. For example, each core1602may include vector unit circuitry, single instruction multiple data (SIMD) unit circuitry, load/store unit (LSU) circuitry, branch/jump unit circuitry, floating-point unit (FPU) circuitry, etc. The control unit circuitry1614includes semiconductor-based circuits structured to control (e.g., coordinate) data movement within the corresponding core1602. The AL circuitry1616includes semiconductor-based circuits structured to perform one or more mathematic and/or logic operations on the data within the corresponding core1602. The AL circuitry1616of some examples performs integer based operations. In other examples, the AL circuitry1616also performs floating point operations. In yet other examples, the AL circuitry1616may include first AL circuitry that performs integer based operations and second AL circuitry that performs floating point operations. In some examples, the AL circuitry1616may be referred to as an Arithmetic Logic Unit (ALU). The registers1618are semiconductor-based structures to store data and/or instructions such as results of one or more of the operations performed by the AL circuitry1616of the corresponding core1602. For example, the registers1618may include vector register(s), SIMD register(s), general purpose register(s), flag register(s), segment register(s), machine specific register(s), instruction pointer register(s), control register(s), debug register(s), memory management register(s), machine check register(s), etc. The registers1618may be arranged in a bank as shown inFIG.16. Alternatively, the registers1618may be organized in any other arrangement, format, or structure including distributed throughout the core1602to shorten access time. The bus1622may implement at least one of an I2C bus, a SPI bus (e.g., a serial bus), a PCI bus, or a PCIe bus.

FIG.17is a block diagram of another example implementation of the processor circuitry1502ofFIG.15. In this example, the processor circuitry1502is implemented by FPGA circuitry1700. The FPGA circuitry1700can be used, for example, to perform operations that could otherwise be performed by the example microprocessor1600ofFIG.16executing corresponding machine-readable instructions. However, once configured, the FPGA circuitry1700instantiates the machine-readable instructions in hardware and, thus, can often execute the operations faster than they could be performed by a general purpose microprocessor executing the corresponding software.

In the example ofFIG.17, the FPGA circuitry1700is structured to be programmed (and/or reprogrammed one or more times) by an end user by a hardware description language (HDL) such as Verilog. The FPGA circuitry1700ofFIG.17includes example input/output (I/O) circuitry1702to obtain and/or output data to/from example configuration circuitry1704and/or external hardware (e.g., external hardware circuitry)1706. For example, the configuration circuitry1704may implement interface circuitry that may obtain machine-readable instructions to configure the FPGA circuitry1700, or portion(s) thereof. In some such examples, the configuration circuitry1704may obtain the machine-readable instructions from a user, a machine (e.g., hardware circuitry (e.g., programmed, or dedicated circuitry) that may implement an Artificial Intelligence/Machine Learning (AI/ML) model to generate the instructions), etc. In some examples, the external hardware1706may implement the microprocessor1600ofFIG.16. The FPGA circuitry1700also includes an array of example logic gate circuitry1708, a plurality of example configurable interconnections1710, and example storage circuitry1712. The logic gate circuitry1708and interconnections1710are configurable to instantiate one or more operations that may correspond to at least some of the machine-readable instructions ofFIGS.12-14and/or other desired operations. The logic gate circuitry1708shown inFIG.17is fabricated in groups or blocks. Each block includes semiconductor-based electrical structures that may be configured into logic circuits. In some examples, the electrical structures include logic gates (e.g., AND gates, OR gates, NOR gates, etc.) that provide basic building blocks for logic circuits. Electrically controllable switches (e.g., transistors) are present within each of the logic gate circuitry1708to enable configuration of the electrical structures and/or the logic gates to form circuits to perform desired operations. The logic gate circuitry1708may include other electrical structures such as look-up tables (LUTs), registers (e.g., flip-flops or latches), multiplexers, etc.

The storage circuitry1712of the illustrated example is structured to store result(s) of the one or more of the operations performed by corresponding logic gates. The storage circuitry1712may be implemented by registers or the like. In the illustrated example, the storage circuitry1712is distributed amongst the logic gate circuitry1708to facilitate access and increase execution speed.

The example FPGA circuitry1700ofFIG.17also includes example Dedicated Operations Circuitry1714. In this example, the Dedicated Operations Circuitry1714includes special purpose circuitry1716that may be invoked to implement commonly used functions to avoid the need to program those functions in the field. Examples of such special purpose circuitry1716include memory (e.g., DRAM) controller circuitry, PCIe controller circuitry, clock circuitry, transceiver circuitry, memory, and multiplier-accumulator circuitry. Other types of special purpose circuitry may be present. In some examples, the FPGA circuitry1700may also include example general purpose programmable circuitry1718such as an example CPU1720and/or an example DSP1722. Other general purpose programmable circuitry1718may additionally or alternatively be present such as a GPU, an XPU, etc., that can be programmed to perform other operations.

AlthoughFIGS.16and17illustrate two example implementations of the processor circuitry1502ofFIG.15, many other approaches are contemplated. For example, as mentioned above, modern FPGA circuitry may include an on-board CPU, such as one or more of the example CPU1720ofFIG.17. Therefore, the processor circuitry1502ofFIG.15may additionally be implemented by combining the example microprocessor1600ofFIG.16and the example FPGA circuitry1700ofFIG.17. In some such hybrid examples, a first portion of the machine-readable instructions and/or operations represented by the flowcharts ofFIGS.13-14may be executed by one or more of the cores1602ofFIG.16and a second portion of the machine-readable instructions and/or operations represented by the flowcharts ofFIGS.13-14may be executed by the FPGA circuitry1700ofFIG.17.

In some examples, the processor circuitry1502ofFIG.15may be in one or more packages. For example, the microprocessor1600ofFIG.16and/or the FPGA circuitry1700ofFIG.17may be in one or more packages. In some examples, an XPU may be implemented by the processor circuitry1502ofFIG.15, which may be in one or more packages. For example, the XPU may include a CPU in one package, a DSP in another package, a GPU in yet another package, and an FPGA in still yet another package.

From the foregoing, it will be appreciated that the above-disclosed methods and apparatus advantageously provide “control-by-wire” architectures for grills (e.g., gas grills) that eliminate the mechanical connection which conventionally exists between each control knob of the grill and each corresponding burner valve of the grill. In some examples, the above-described “control-by-wire” architectures can be implemented using an addressing block as a component of an input wiring harness to identify, to a user-interface assembly, an identifier to be used by the user-interface assembly. Furthermore, example approaches disclosed herein utilize differential signaling to communicate via such electrical connectors, thereby reducing the effects of electrical noise. Advantageously, utilizing a daisy-chain configuration as disclosed herein enables a reduction in overall wiring and wiring complexity.