One button interface of a blender

A blender using different modes of operation is disclosed. Exemplary implementations may include a base assembly, a container assembly, a blending component, a control interface, control circuitry, and/or other components. The control interface includes a button configured to be pushed by the user, which controls transitions between the different blending modes of operation and a ready-to-blend mode. Rotation of the blending component is controlled through the control circuitry.

FIELD OF THE DISCLOSURE

The present disclosure relates to blenders configured to control different blending modes of operation.

BACKGROUND

Blenders are known, typically as consumer-grade home appliances. User interfaces are known, e.g., for home appliances.

SUMMARY

One aspect of the present disclosure relates to a blender configured to blend foodstuffs using different blending modes of operation. In some implementations, the blender may be portable due to its size, and/or its rechargeability. By virtue of true portability, a user can take the blender anywhere and create drinks, shakes, smoothies, baby food, sauces, and/or other concoctions. Once the blender is fully charged, a user can prepare multiple servings quickly and easily. In some implementations, lack of an external power source, much less a reliable external power source, is no longer preventing users from enjoying blended drinks. By virtue of the control interface and corresponding control circuitry described in this disclosure, different blending modes of operation may be available through an easy-to-use control interface. In some implementations, the control interface may use only a single button that is configured to be pushed by the user.

The blender may include a blending component, a base assembly, a container assembly, a control interface, control circuitry, and/or other components. As used herein, the term “foodstuffs” may include ingredients ranging from solid to liquid, from hot to cold or frozen, in any combination. As used herein, the term “ingredient” merely connotates something fit to ingest, and not necessarily nutritional value. For example, ice and/or ice cubes may be ingredients.

As used herein, any association (or relation, or reflection, or indication, or correspondency) involving assemblies, blending components, blades, motors, rotational axes, longitudinal axes, diameters, batteries, couplings, interfaces, buttons, detectors, indicators, magnetic components, caps, rotations, and/or another entity or object that interacts with any part of the blender and/or plays a part in the operation of the blender, may be a one-to-one association, a one-to-many association, a many-to-one association, and/or a many-to-many association or N-to-M association (note that N and M may be different numbers greater than 1).

DETAILED DESCRIPTION

FIG.1shows a blender100configured to blend foodstuffs using different blending modes of operation, in accordance with one or more implementations. Blender100may include one or more of a base assembly11, a container assembly12, a blending component133, a control interface29, control circuitry17(depicted inFIG.1as a dotted rectangle to indicate this component may be embedded within base assembly11, and not readily visible from the outside), and/or other components. Base assembly11and container assembly12may be configured to be coupled during blending by blender100. For example, in some implementations, base assembly11and container assembly12may be mechanically coupled, e.g., through one or more threaded couplings. Other types of couplings may be envisioned for blender100, though leak-proof options are preferred, since most uses include one or more liquid ingredients. In some implementations, control circuitry17and/or other components may be included in base assembly11, e.g., within base assembly11. For example, one or more of control interface29, control circuitry17, electrical motor14(depicted inFIG.1as a dotted rectangle to indicate this component may be embedded within base assembly11, and not readily visible from the outside), rechargeable battery15(depicted inFIG.1as a dotted rectangle to indicate this component may be embedded within base assembly11, and not readily visible from the outside), and/or other components may be integrated permanently into base assembly11such that base assembly11forms an integral whole. In some implementations, the phrase integrated permanently may refer to components being integrated such that they are not readily accessible, serviceable, and/or replaceable by a user, or at least not during ordinary usage by the user, including, but not limited to, charging, blending, cleaning, and storing for later use.

In some implementations, base assembly11may include one or more of a base body11b(as depicted inFIG.5, containing the components of the base assembly11), blending component133(e.g., a set of blades13, also referred to as a set of one or more blades13), electrical motor14, a rechargeable battery15, a (standardized) charging interface25, one or more mechanical couplings16, a detector18(depicted inFIG.1as a dotted rectangle to indicate this component may be embedded within base assembly11, and not readily visible from the outside), one or more alignment indicators19, control interface29, and/or other components.

In some implementations, one or more mechanical couplings16may include threaded couplings. By way of non-limiting example,FIG.4shows an isometric elevated view of blender100configured to blend foodstuffs. For example, one or more mechanical couplings16may include a first mechanical coupling and a second mechanical coupling. In some implementations, the first mechanical coupling may be included in base assemble11, and may be a female threaded coupling configured to fit together with the second mechanical coupling (which may be included in container assembly12). The first mechanical coupling and the second mechanical coupling may be configured to (temporarily and detachably) couple base assembly11to container assemble12.

Referring toFIG.1, blending component133may include one or more structural components configured to blend foodstuffs, including but not limited to one or more blending bars, one or more blades, and/or other structural components configured to rotate. For example, in some implementations, blending component133may include set of blades13, which may be rotatably mounted to base assembly11to blend foodstuffs. Blending component133may be configured to rotate around a rotational axis13a. Rotational axis13ais depicted inFIG.1as a geometric 2-dimensional line extending indefinitely through blending component133, and is not a physical axis. Rather, rotational axis13aindicates how blending component133rotates in relation to other components of blender100, in a rotational direction13b. In some implementations, blending component133may be mounted permanently to base assembly11. In some implementations, set of blades13may include 1, 2, 3, 4, 5, or more pairs of blades. In some implementations, a pair of blades may include two blades on opposite sides of rotational axis13a. In some implementations, a pair of blades may have two blades such that the distal ends of these two blades are at the same horizontal level. In some implementations, as depicted in the upright configuration of blender100inFIG.1, set of blades13may include six blades that form 3 pairs of blades. In some implementations, set of blades13may include at least two downward blades, which may prevent and/or reduce foodstuffs remaining unblended when disposed under the upward blades. In some implementations, set of blades13may include at least four upward blades. In some implementations, including six blades may be preferred over including less than six blades, in particular for blending ice and/or ice cubes. By using more blades, more points of contact will hit the ice at substantially the same time, which reduces the likelihood that a piece of ice is merely propelled rather than broken, crushed, and/or blended, in particular for implementations having limited power (here, the term limited is used in comparison to blenders that are connected to common outlets during blending), such as disclosed herein. As used herein, directional terms such as upward, downward, left, right, front, back, and so forth are relative toFIG.1unless otherwise noted.

Referring toFIG.1, in some implementations, base assembly11may have a cylindrical and/or conical shape (apart from blending component133and/or set of blades13). In some implementations, the shape of base assembly11may have a base diameter between 2 and 4 inches. In some implementations, the shape of base assembly11may have a base diameter between 3 and 3.5 inches. Such a base diameter may improve portability, as well as allow blender100to be stored in a cup holder, e.g., in a vehicle. For example,FIG.5shows a front view of base assembly11, depicting a blade diameter13d(e.g., the diameter of the circle described by rotation of the distal ends of the lowest (and/or widest) pair of blades in set of blades13) and a base diameter11a(as measured at or near the top of base assembly11). In some implementations, blade diameter13dmay refer to the largest diameter of any circle described by rotation of distal ends of pairs of blades in set of blades13(or other distal ends of blending component133), as measured perpendicular to rotation. In some implementations, the orientation of blade diameter13dmay be orthogonal/perpendicular to the direction of rotational axis13a. In some implementations, the plane of rotation of the distal ends of the blades (or other distal ends of blending component133) that define blade diameter13dmay be orthogonal/perpendicular to the direction of rotational axis13a. Blade diameter13dmay refer to a blending bar, or to set of blades13, and/or to other types of blending components.

Referring toFIG.1, container assembly12may include one or more of a container body20, a cap24(e.g., to prevent spilling during blending), a carrying strap3(e.g., configured to carry blender100), and/or other components. Container body20may form a vessel to hold and/or contain foodstuffs within container assembly12. In some implementations, container body20may be a cylindrical body and/or have a cylindrical shape, as depicted inFIG.4. In some implementations, container body20may be open at one or both ends. In some implementations, container body20may be closed at the bottom. In some implementations, the dimensions of container assembly12may be such that the internal volume of container assembly12can hold 8, 10, 12, 14, 16, 18, 20, 22, 24, 28, 32, 36, 48, or more ounces. In some implementations, container assembly12and/or container body20may have cylindrical shapes.

Referring toFIG.1, electrical motor14may be configured to rotationally drive blending component133. In some implementations, electrical motor14may operate at a voltage between 5V and 15V. In one or more preferential implementations, electrical motor14may operate at a voltage of about 7.4V. In some implementations, electrical motor14may be configured to spin blending component133at a maximum speed between 20,000 rotations per minute (RPM) and 40,000 RPM. In one or more preferential implementations, electrical motor14may spin blending component133at a maximum speed of about 22,000 RPM. Electrical motor may be configured to be powered by rechargeable battery15. Simultaneously, in some implementations, electrical motor14may be further configured to be powered through (standardized) charging interface25, though that may not be the preferred way of operating blender100. In one or more preferential implementations, no power is (or need be) supplied to electrical motor14from an external power source during blending by blender100. In some implementations, control circuit17may be configured to control electrical motor14during rotation of blending component133. For example, control circuit17may control the speed of the rotation of blending component133during blending by blender100.

Referring toFIG.1, rechargeable battery15may be configured to power electrical motor14. In some implementations, rechargeable battery15may be configured to power electrical motor14such that, during blending by blender100, no power is supplied to electrical motor14from an external power source. In some implementations, rechargeable battery15may be non-removable. As used herein, the term “non-removable” may mean not accessible to users during common usage of blender100, including charging, blending, cleaning, and storing for later use. In some implementations, rechargeable battery15may be not user-replaceable (in other words, non-removable). In some implementations, rechargeable battery15may be user-replaceable. In some implementations, rechargeable battery15may be store-bought. In some implementations, rechargeable battery15may have a capacity between 1000 mAh and 8000 mAh. In one or more preferential implementations, rechargeable battery15may have a capacity of about 2500 mAh. In some implementations, control circuit17may be configured to control charging of rechargeable battery15. For example, control circuit17may control the transfer of electrical power through standardized charging interface25into rechargeable battery15. For example, responsive to a detection that rechargeable battery15is fully charged, control circuit17may prevent the transfer of electrical power through standardized charging interface25into rechargeable battery15.

Charging interface25may be standardized and may be configured to conduct electrical power to rechargeable battery15. In some implementations, charging interface25may be configured to conduct electrical power to charge rechargeable battery15, e.g., from an external power source. In some implementations, charging interface25may be configured to support wireless charging of rechargeable battery15, e.g., from an external power source, including but not limited to induction-based charging. In some implementations, charging interface25may be a universal serial bus (USB) port configured to receive an electrical connector for charging rechargeable battery15. A USB port is merely one type of standardized charging interface. Other standards are contemplated within the scope of this disclosure. The electrical connector may be connected to an external power source. In some implementations, charging interface25may be covered for protection and/or other reasons.

Detector18may be configured to detect whether mechanical couplings16are coupled in a manner operable and suitable for blending by blender100. In some implementations, operation of detector18may use one or more magnetic components. For example, in some implementations, one or more magnetic components are included in container body20. Engagement may be detected responsive to these one or more magnetic components being aligned and sufficiently close to one or more matching magnetic components that may be included in base assembly11. In some implementations, blender100may include one or more alignment indicators19, depicted inFIG.1as matching triangles, to visually aid the user in aligning base assembly11with container assembly12in a manner operable and suitable for blending. In some implementations, one or more alignment indicators19may be in the front, in the back, and/or in other parts of blender100.

Control interface29may be part of the user interface of blender100. Through the user interface, a user of blender100may control the operation of blender100, including but not limited to transitions between different modes of operation. For example, the different modes of operation may include multiple blending modes of operation. For example, in some implementations, the modes of operation include a ready-to-blend mode. During the ready-to-blend mode, blender100is not blending, but blender100may be ready to blend. For example, blender100may have sufficient power through rechargeable battery15, and mechanical couplings16may be coupled in a manner operable and suitable for blending by blender100. The transitions may include transitions from the ready-to-blend mode to one of the blending modes of operation, and/or vice versa.

In some implementations, the blending modes of operation of blender100may include at least two blending modes of operation: a fixed-time blending mode of operation, a variable-time blending mode of operation, and/or other blending modes of operation. For example, during the fixed-time blending mode of operation of blender100, control circuitry17may be configured to effectuate rotation of blending component133(in other words, to effectuate blending) for a particular duration. In some implementations, the particular duration may be limited to a predetermined time limit. For example, the predetermined time limit may be 10 seconds, 20 seconds, 30 seconds, 40 seconds, 50 seconds, 1 minute, and/or other time limit. In some implementations, the predetermined time limit may be between 10 and 60 seconds, between 20 and 50 seconds, between 30 and 40 seconds, between 1 and 2 minutes, and/or have another range of durations. For example, during the variable-time blending mode of operation of blender100, control circuitry17may be configured to effectuate rotation of blending component133for one or more durations. Individual ones of the one or more durations may correspond to individual occurrences of the button of control interface29being pushed down by the user. In other words, as long as the user holds the button pushed down, blender100blends. The user may use short pulses or longer pulses, or any combination as desired during the variable-time blending mode of operation of blender100.

In some implementations, control interface29may include one or more buttons. For example, a button of control interface29may be configured to be pushed by the user (as used herein, a push may be released quickly or may be held down, or may be followed by one or more additional pushes, e.g. in the case of a double push). In some implementations, control interface29includes exactly one button. For example, in some implementations, the button may be the only user-manipulatable portion of control interface29, such that no other button or user interface component controls the operation of blender100or the transitions between different blending modes of operation used by blender100. In some implementations, control interface29may include one or more controllable light-emitting components. For example, the light-emitting components may be LEDs or other types of lights. In some implementations, the one or more controllable light-emitting components may be configured to selectively light up. In some implementations, the one or more controllable light-emitting components may be configured to indicate, to a user, a current mode of operation of blender100, an occurrence of a transition between different modes of operation, a warning for the user, and/or other information regarding the operation of blender100. For example, the one or more controllable light-emitting components may use different colors, intensities, patterns, sequences, and/or other combinations of light to provide information to the user. In some implementations, control interface29may include one or more controllable sound-emitting components, such as a speaker, configured to selectively emit sound. In some implementations, the one or more controllable sound-emitting components may be configured to indicate, to a user, a current mode of operation of blender100, an occurrence of a transition between different modes of operation, a warning for the user, and/or other information regarding the operation of blender100. For example, the one or more controllable sound-emitting components may use different frequencies, volumes, patterns, sequences, and/or other combinations of sound to provide information to the user. In some implementations, control interface29may include one or more haptic components to provide feedback to a user.

Control circuitry17may be configured to control different functions and/or operations of blender100, including but not limited to turning blender100on and off, transitioning between different modes of operation, charging of rechargeable battery15, controlling of electrical motor14regarding and/or during rotation of blending component133, determining whether mechanical couplings16are engaged properly for blending, controlling or otherwise using control interface29, and/or performing other functions for blender100. In some implementations, control circuitry17may be configured to prevent rotation of blending component133responsive to a determination that mechanical couplings16are not engaged (or not engaged properly for the intended operation of blender100). In some implementations, control circuitry17may be configured to use control interface29to convey information regarding the operational status of blender100to a user. For example, control interface29may include a light that can illuminate in various colors and/or patterns. In some implementations, control circuitry17may be implemented as a printed circuit board (PCB).

In some implementations, control circuitry17may be configured to make detections regarding one or more buttons of control interface29. For example, control circuitry may detect whether a button of control interface29has been pushed by a user, or released, or pushed again. Control circuitry17may be configured to make different types of detections, including but not limited to first, second, third, fourth types of detections. A first type of detections may indicate occurrences of the user single-pushing a button of control interface29. A second type of detections may indicate occurrences of the user double-pushing a button of control interface29. In some implementations, a third type of detections may indicate occurrences of the user pushing a button of control interface29and holding the button pushed down for at least a predetermined duration. The predetermined duration may be at least 2 seconds, at least 3 seconds, at least 4 seconds, at least 5 seconds, at least between 2 and 4 seconds, at least between 3 and 5 seconds, and/or another (range of) duration. In some implementations, a fourth type of detections may indicate occurrences of any type of push of a button of control interface29by the user.

In some implementations, control circuitry17may be configured to control operation of control interface29to enable transitions between different modes of operation. The transitions may include a first, second, third, fourth, fifth transition, and so forth. For example, a first transition may be from the ready-to-blend mode to the fixed-time blending mode of operation. In some implementations, the first transition may occur responsive to an occurrence of the first type of detections (in the ready-to-blend mode). For example, a second transition may be from the ready-to-blend mode to the variable-time blending mode of operation. In some implementations, the second transition may occur responsive to an occurrence of the second type of detections (in the ready-to-blend mode). In some implementations, a third transition may be from the variable-time blending mode of operation to the ready-to-blend mode. In some implementations, the third transition may occur responsive to an occurrence of a particular type of detections (in the variable-time blending mode of operation). For example, the particular type of detection may be a detection of an idle duration during which a button of control interface29is not being pushed by the user. For example, the idle duration may be at least 2 seconds, at least 3 seconds, at least 4 seconds, at least 5 seconds, at least 6 seconds, at least 7 seconds, at least 8 seconds, at least between 2 and 4 seconds, at least between 3 and 5 seconds, at least between 4 and 6 seconds, at least between 5 and 7 seconds, and/or another (range of) duration. In other words, the variable-time blending mode of operation may automatically time-out responsive to no push by the user being detection in a timely manner. In some implementations, a fourth transition may be from the fixed-time blending mode of operation to the ready-to-blend mode. In some implementations, the fourth transition may occur responsive to an individual occurrence of the button of control interface29being pushed by the user prior to completion, during the fixed-time blending mode of operation, of the particular duration of the rotation of blending component133. For example, in some implementations, the fourth transition may occur responsive to an occurrence of the fourth type of detections. For example, a fifth transition may be from the fixed-time blending mode of operation to the ready-to-blend mode. In some implementations, the fifth transition may occur automatically responsive to completion of the particular duration of the rotation of blending component133(in other words, after the predetermined time limit of, say, 30 seconds).

In some implementations, the transitions may include a sixth and seventh transition, and so forth. In some implementations, the sixth transition may be from the ready-to-blend mode to a locked mode of operation. In some implementations, the seventh transition may be from the locked mode of operation to the ready-to-blend mode. In some implementations, the sixth transition may occur responsive to an individual occurrence of the third type of detections (except, for example, using a predetermined duration of holding the button pressing down of at least 4 seconds, at least 5 seconds, at least 6 seconds, at least 7 seconds, at least between 4 and 6 seconds, at least between 5 and 7 seconds, and/or another (range of) duration. In some implementations, the seventh transition may occur responsive to an individual occurrence of the third type of detections. For example, during an unlocked mode of operation (e.g., the ready-to-blend mode), control circuitry17may be configured to transition to a locked mode of operation. For example, during a locked mode of operation, control circuitry17may be configured to transition to an unlocked mode of operation (e.g., the ready-to-blend mode). In some implementations, control circuitry17may be configured to prevent rotation of blending component133in the locked mode of operation. In some implementations, control circuitry17may be configured to allow rotation of blending component133in the unlocked mode of operation (e.g., the ready-to-blend mode).

In some implementations, control by a user of blender100may be based on a switch (not shown), a button, a touchscreen (not shown), voice-controlled operation (not shown), gesture-based operation (not shown), and/or other types of user interfaces suitable to turn consumer appliances on and off. Control interface29(e.g., through one or more light-emitting components) may be configured to illuminate in various colors (red, blue, purple, etc.) and/or patterns (solid, fast blinking, slow blinking, alternating red and blue, etc.). Control interface29may convey information regarding the operational status of blender100to a user. The operational status of blender100may be determined by control circuitry17. Control interface29may be controlled by control circuitry17. For example, if control interface29is solid purple, blender100may be charging and/or insufficiently charged to blend. For example, if control interface29is solid blue, blender100may be ready for blending (e.g., in the ready-to-blend mode). For example, if control interface29is alternating red and blue, blender100may not be ready for blending due to base assembly11and container assembly12not being coupled properly and/or fully. For example, in some implementations, threaded couplings between assembly11and container assembly12may need to be tightened sufficiently for proper blending, and control interface29may warn the user when the threaded couplings are not tightened sufficiently and/or correctly.

By way of non-limiting example,FIG.3Aillustrates state transitions in a state diagram30aas may be used by blender100, e.g., responsive to different types of detections regarding control interface29being manipulated by a user as described elsewhere in this disclosure. As depicted, state diagram30amay include a first state35a(labeled “S1”) and a second state35b(labeled “S2”). First state35amay correspond to a ready-to-blend mode of blender100. Second state35bmay correspond to a fixed-time blending mode of operation of blender100. As depicted here, a first transition31may transition the mode of operation of blender100from first state35ato second state35b. A second transition32may transition the mode of operation of blender100from second state35bto first state35a. First transition31may occur responsive to detection of the first type of detection. Second transition32may occur automatically, e.g., after completion of a fixed-time blending operation.

By way of non-limiting example,FIG.3Billustrates state transitions in a state diagram30bas may be used by blender100, e.g., responsive to different types of detections regarding control interface29being manipulated by a user as described elsewhere in this disclosure. As depicted, state diagram30bmay include a first state35a(labeled “S1”), a second state35b(labeled “S2”), and a third state35c(labeled “S3”). First state35amay be similar as described regardingFIG.3A. Second state35bmay correspond to a fixed-time blending mode of operation of blender100. Third state35cmay correspond to a different and/or intermediate mode of operation of blender100. As depicted in state diagram30b, a first transition31may transition the mode of operation of blender100from first state35ato third state35c. A second transition32may transition the mode of operation of blender100from second state35bto first state35a. A third transition33may transition the mode of operation of blender100from third state35cto second state35b. First transition31may occur responsive to detection of the first type of detection. Third transition33may occur responsive to completion of operations during third state35c. Second transition32may occur automatically.

By way of non-limiting example,FIG.3Cillustrates state transitions in a state diagram30cas may be used by blender100, e.g., responsive to different types of detections regarding control interface29being manipulated by a user as described elsewhere in this disclosure. As depicted, state diagram30cmay include a first state35a(labeled “S1”), a second state35b(labeled “S2”), and a third state35c(labeled “S3”). First state35amay be similar as described regardingFIG.3A. Second state35bmay correspond to a fixed-time blending mode of operation of blender100. Third state35cmay correspond to a variable-time blending mode of operation of blender100. As depicted in state diagram30c, a first transition31may transition the mode of operation of blender100from first state35ato second state35b. A second transition32may transition the mode of operation of blender100from third state35cto first state35a. A third transition33may transition the mode of operation of blender100from second state35bto third state35c. First transition31may occur responsive to detection of the first type of detection. Third transition33may occur responsive to detection of a particular type of detection. Second transition32may occur responsive to detection of a given type of detection, and/or automatically after a time-out.

By way of non-limiting example,FIG.3Dillustrates state transitions in a state diagram30das may be used by blender100, e.g., responsive to different types of detections regarding control interface29being manipulated by a user as described elsewhere in this disclosure. As depicted, state diagram30cmay include a first state35a(labeled “S1”), a second state35b(labeled “S2”), a third state35c(labeled “S3”), and a fourth state35d(labeled “S4”). First state35amay be similar as described regardingFIG.3A. Second state35bmay correspond to a fixed-time blending mode of operation of blender100. Third state35cand fourth state35dmay correspond to temporary modes of operation of blender100. As depicted in state diagram30d, a first transition31may transition the mode of operation of blender100from first state35ato third state35c. A second transition32may transition the mode of operation of blender100from fourth state35dto first state35a. A third transition33may transition the mode of operation of blender100from third state35cto second state35b. A fourth transition34may transition the mode of operation of blender100from second state35bto fourth state35d. First transition31may occur responsive to detection of the first type of detection. Second transition32may occur responsive to a particular type of detection, or automatically. Third transition33may occur responsive to completion of a predefined blending operation. Fourth transition34may occur responsive to a given type of detection.

By way of non-limiting example,FIG.3Eillustrates state transitions in a state diagram30eas may be used by blender100, e.g., responsive to different types of detections regarding control interface29being manipulated by a user as described elsewhere in this disclosure. As depicted, state diagram30emay include a first state35a(labeled “S1”), a second state35b(labeled “S2”), and a third state35c(labeled “S3”). First state35amay correspond to a ready-to-blend mode of blender100. Second state35bmay correspond to a fixed-time blending mode of operation of blender100. Third state35cmay correspond to a variable-time blending mode of operation of blender100. As depicted here, a first transition31may transition the mode of operation of blender100from first state35ato second state35b. A second transition32may transition the mode of operation of blender100from first state35ato third state35c. A third transition33may transition the mode of operation of blender100from second state35bto first state35a. A fourth transition34may transition the mode of operation of blender100from third state35cto first state35a. First transition31may occur responsive to detection of the first type of detection (e.g., a single push of a button). Second transition32may occur responsive to detection of the second type of detection (e.g., a double push of the button). Third transition33may occur responsive to detection of the third type of detection. Fourth transition34may occur responsive to detection of the fourth type of detection.

By way of non-limiting example,FIG.3Fillustrates state transitions in a state diagram30fas may be used by blender100, e.g., responsive to different types of detections regarding control interface29being manipulated by a user as described elsewhere in this disclosure. As depicted, state diagram30fmay include a first state35a(labeled “S1”), a second state35b(labeled “S2”), and a third state35c(labeled “S3”). First state35amay correspond to a ready-to-blend mode of blender100. Second state35bmay correspond to a fixed-time blending mode of operation of blender100. Third state35cmay correspond to a variable-time blending mode of operation of blender100. As depicted here, a first transition31, a second transition32, a third transition33, and a fourth transition34may transition modes of operation in a manner similar toFIG.3E. Fifth transition33bmay transition the mode of operation of blender100from second state35bto first state35a. Fifth transition33bmay occur responsive to detection of the fifth type of detection (e.g., a single push of a button while blender100is blending during the fixed-time blending mode of operation).

By way of non-limiting example,FIG.3Gillustrates state transitions in a state diagram30gas may be used by blender100, e.g., responsive to different types of detections regarding control interface29being manipulated by a user as described elsewhere in this disclosure. As depicted, state diagram30gmay include a first state35a(labeled “S1”), a second state35b(labeled “S2”), a third state35c(labeled “S3”), and a fourth state35d(labeled “S4”). First state35amay correspond to a ready-to-blend mode of blender100(which is also an unlocked mode of operation). Second state35bmay correspond to a fixed-time blending mode of operation of blender100. Third state35cmay correspond to a variable-time blending mode of operation of blender100. Fourth state35dmay correspond to a locked mode of operation of blender100. As depicted here, a first transition31, a second transition32, a third transition33, a fourth transition34, and a fifth transition33bmay transition modes of operation in a manner similar toFIG.3F. Sixth transition36may transition the mode of operation of blender100from first state35ato fourth state35d. Seventh transition37may transition the mode of operation of blender100from fourth state35dto first state35a. Sixth transition36may occur responsive to detection of the third type of detection (e.g., a single push of a button held down for at least 6 seconds while blender100is in the ready-to-blend mode). Seventh transition37may occur responsive to detection of the third type of detection (e.g., a single push of a button held down for at least 6 seconds while blender100is in the locked mode of operation).

By way of non-limiting example,FIG.3Hillustrates state transitions in a state diagram30has may be used by blender100, e.g., responsive to different types of detections regarding control interface29being manipulated by a user as described elsewhere in this disclosure. As depicted, state diagram30gmay include a first state35a(labeled “S1”), a second state35b(labeled “S2”), a third state35c(labeled “S3”), a fourth state35d(labeled “S4”), and a fifth state35e(labeled “S5”). First state35amay correspond to a ready-to-blend mode of blender100. Second state35bmay correspond to another mode of blender100(as described below). Third state35cmay correspond to a fixed-time mode of blender100. Fourth state35dmay correspond to a variable-time mode of blender100. Fifth state35emay correspond to a locked mode of blender100. As depicted here, a first transition31may transition the mode of operation of blender100from first state35ato second state35b. A second transition32may transition the mode of operation of blender100from second state35bto third state35c. A third transition33may transition the mode of operation of blender100from second state35bto fourth state35d. A fourth transition34may transition the mode of operation of blender100from second state35bto fifth state35e. A fifth transition35may transition the mode of operation of blender100from third state35cto first state35a. A sixth transition36may transition the mode of operation of blender100from fourth state35dto first state35a. A seventh transition37may transition the mode of operation of blender100from fifth state35eto first state35a.

RegardingFIG.3H, first transition31may occur responsive to detection of the first type of detection, i.e., a single push that pushes down the button of control interface29. In this case, at this point, a single push could be followed by no other pushes, by another push, or it could be held down for a relatively longer duration (say, 6 seconds). Second transition32may occur responsive to a detection of a release of the button of control interface29, and no other push following the first push. This may effectuate the fixed-time blending mode of operation. Third transition33may occur responsive to detection of the first type of detection, i.e., another single push that pushes down the button of control interface29. Third transition33may occur responsive to a detection of a second single push, which may in effect be a double push (when considered from the starting point of the ready-to-blend mode). This may effectuate the variable-time blending mode of operation. Fourth transition34may occur responsive to detection of the third type of detection, i.e., the button of control interface29is held down for a relatively longer duration (say, 6 seconds). This may effectuate the locked mode of operation. Fifth transition35may occur either automatically (when the fixed duration operation has completed) or responsive to detection of the fourth type of detection, i.e. any push of the button of control interface29before completion of the fixed duration operation. Sixth transition36may occur responsive to a detection of an idle duration during which the button of the control interface is not being pushed by the user. Seventh transition37may occur responsive to detection of the third type of detection (e.g., the single push of the button is held down for at least 6 seconds while blender100is in the ready-to-blend mode of operation).

FIG.2illustrates a method200for transitioning between different blending modes of operation of a blender and a ready-to-blend mode, in accordance with one or more implementations. The operations of method200presented below are intended to be illustrative. In some implementations, method200may be accomplished with one or more additional operations not described, and/or without one or more of the operations discussed. Additionally, the order in which the operations of method200are illustrated inFIG.2and described below is not intended to be limiting.

At an operation202, detections are made regarding a button of a control interface of the blender being pushed by a user. The detections include a first type of detections and a second type of detections. The first type of detections indicate occurrences of the user single-pushing the button of the control interface. The second type of detections indicate occurrences of the user double-pushing the button of the control interface. In some embodiments, operation202is performed by control circuitry the same as or similar to control circuitry17(shown inFIG.1and described herein).

At an operation204, the transitions are effectuated between the different blending modes of operation based on the detections. The transitions include a first transition from the ready-to-blend mode to the fixed-time blending mode of operation, a second transition from the ready-to-blend mode to the variable-time blending mode of operation, and a third transition from the variable-time blending mode of operation to the ready-to-blend mode. The first transition occurs responsive to an occurrence of the first type of detections, wherein, during the fixed-time blending mode of operation, the control circuitry is configured to effectuate the rotation of the blending component for a particular duration. The particular duration is limited to a predetermined time limit. The second transition occurs responsive to an occurrence of the second type of detections, wherein, during the variable-time blending mode of operation, the control circuitry is configured to effectuate the rotation of the blending component for one or more durations. Individual ones of the one or more durations correspond to individual occurrences of the button of the control interface being pushed down by the user. The third transition occurs automatically responsive to a detection of an idle duration during which the button of the control interface is not being pushed by the user. In some embodiments, operation204is performed by control circuitry the same as or similar to control circuitry17(shown inFIG.1and described herein).