Example embodiments generally relate to an outdoor power equipment tool and, more particularly, to facilitating personalized control of the device by a user based on health or fitness data or metrics received from a fitness device of the user.
Lawn care tasks may be performed using various devices or tools configured for the performance of corresponding specific tasks. For example, certain tasks, like grass cutting, are typically performed by lawn mowers. Regardless of the outdoor power equipment device or tool and the specific task they are configured to perform, a user of the outdoor power equipment device or tool, in particular walk-behind devices or tools, may desire to have more control over the specific settings and operation of the tool. In this regard, the user may wish to have more personalized and tailored settings when operating the tool. For instance, the user may wish to have settings tailored to their specific health or fitness metrics. Thus, for example, rather than having generic drive speed control settings on the tool, a user may wish to have a drive speed setting that corresponds to the user's normal walking speed.
Accordingly, in order to facilitate a tailored and personalized operation of an outdoor power equipment tool by a user, some example embodiments may provide a tool that is configured to receive health or fitness data or metrics from a fitness device of a user. The health or fitness data or metrics received by the tool may be used in adjusting settings of the tool to correspond to the user and therefore optimize operation of the tool while ensuring the optimal safety and health of the user.
In one example embodiment, a controller for an outdoor power equipment tool may be provided. The controller may include processing circuitry operably coupled to a sensor network of the outdoor power equipment tool and in data communication with a network. The processing circuitry may be configured to receive fitness data of a user from a fitness device via the network. The processing circuitry may be further configured to receive sensor data from the sensor network, the sensor data corresponding to operational parameters of the outdoor power equipment tool. The processing circuitry may be even further configured to compare the fitness data to the sensor data, and in response to the comparison of the fitness data to the sensor data, cause an adjustment to the operational parameters of the outdoor power equipment tool.
In a further example embodiment, a method for adjusting operational parameters of an outdoor power equipment tool may be provided. The method may include receiving fitness data of a user from a fitness device via a network. The method may further include receiving sensor data from a sensor network of the outdoor power equipment tool, the sensor data corresponding to operational parameters of the outdoor power equipment tool. The method may even further include comparing the fitness data to the sensor data, and in response to the comparison of the fitness data to the sensor data, causing an adjustment to the operational parameters of the outdoor power equipment tool.
In an even further example embodiment, a system may be provided. The system may include an outdoor power equipment tool and a fitness device. The outdoor power equipment tool may include a sensor network and controller. The controller may include processing circuitry operably coupled to the sensor network of the outdoor power equipment tool and in data communication with a network. The processing circuitry may be configured to receive fitness data of a user from the fitness device via the network. The processing circuitry may be further configured to receive sensor data from the sensor network, the sensor data corresponding to operational parameters of the outdoor power equipment tool. The processing circuitry may be even further configured to compare the fitness data to the sensor data, and in response to the comparison of the fitness data to the sensor data, cause an adjustment to the operational parameters of the outdoor power equipment tool.
Having thus described the invention in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:
Some example embodiments now will be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all example embodiments are shown. Indeed, the examples described and pictured herein should not be construed as being limiting as to the scope, applicability or configuration of the present disclosure. Rather, these example embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like reference numerals refer to like elements throughout. Furthermore, as used herein, the term “or” is to be interpreted as a logical operator that results in true whenever one or more of its operands are true. As used herein, operable coupling should be understood to relate to direct or indirect connection that, in either case, enables functional interconnection of components that are operably coupled to each other.
Example embodiments herein may improve and simplify the ability of a user of an outdoor power equipment tool (tool) to personalize or tailor operation of the tool in manner that corresponds to a detected overall health or fitness of the user. Accordingly, in order to facilitate personalized control over the tool, the tool may be configured to receive health or fitness data (fitness data) or metrics from a fitness device of the user. The fitness data or metrics received by the tool may ensure that operation of the tool corresponds to the fitness ability of the user.
As shown in
The cutting blade of the tool 10 may be suspended above the ground by a rotatable shaft (also not shown) of the tool 10 that may be rotated responsive to operation of the power source 14 of the tool 10. In some cases, the power source 14 may be an engine that is battery-powered. It should be understood, however, that the power source 14 may alternatively be an electric or gasoline-powered engine or the like.
As further shown in
In accordance with an example embodiment, the tool 10 may further include a handle assembly 30. The handle assembly 30 may include two handle members 32 that extend generally rearward and upward from opposing sides of a rear portion of the blade housing 16. The handle members 32 may be substantially parallel to each other and may be connected to each other at their distal ends via a cross bar 34. The handle members 32 may be adjustable in length or may be foldable to reduce the amount of space that the tool 10 consumes when stored or shipped.
In some cases, the tool 10 may also include a sensor network 60 (see
The tool 10 of
Furthermore, the tool 10 may include a controller 100 (see
To facilitate interaction between the tool 10 and the user fitness device 250, the controller 100 may include circuitry that enables communication directly or indirectly between the tool 10 and the user fitness device 250. In this regard, the controller 100 allows for information gathered from the user fitness device 250 to be transferred to the tool 10 for adjustment of settings of the tool 10 to thereby enabling optimum performance of the tool 10 that is tailored to the user of the tool 10. Furthermore, the controller 100 may cause the information unit 70 to display certain user fitness data, tool data, or the like such that the user may have full access to the data being received or the operational settings of the tool 10 and may change them as desired.
As will be further described below, the controller 100 may be configured to interact with and gather certain operational parameters (e.g., battery status, energy efficiency, device speed, blade speed, blade height, or the like) about the tool 10 via the sensor network 60. The controller 100 may be further configured to compare these operational data or parameters of the tool 10 to the data received from the user fitness device 250 (e.g., average walking speed, heart rate, blood pressure, sweat volume, temperature, blood glucose levels, calories burned, UV exposure, oxygen content, or the like). In this regard, for example, the controller 100 may be configured to compare a detected tool speed to a received average walking speed of the user. In some cases, the comparison may include comparing the run time of the tool 10 to calories burned, UV exposure, sweat volume, or temperature of the user.
Based on the comparison, the controller 100 may be then configured to change certain settings of the tool 10 such that the settings of the tool 10 correspond to the fitness data of the user received from the user fitness device 250 or to ensure the well-being of the user. Using the examples above, the controller 100 may receive the average walking speed of the user from the user fitness device 250, and if necessary, the controller 100 may change a drive speed of the tool 10 to correspond to the user's average walking speed. Furthermore, the controller 100 may receive the run time of the device and recommend or cause a shutdown of the device. In this regard, the controller 100 may have certain stored preset health limits or thresholds that a user's fitness data may be compared to (e.g., recommended sun exposure, sweat volume, body temperature, etc.). Accordingly, in order to enable personalized operation of the tool 10, the controller 100 may be configured to extract information from the sensor network 60 about the operation of the tool 10 (i.e., operational parameters) and cause the sensor network 60 to change certain settings of the tool 10 to correspond to the user. Furthermore, the controller 100 may be configured to cause the information unit 70 to display the fitness data received from the user fitness device 250 (e.g., heart rate, walking speed, blood pressure, etc.) and certain operational parameters of the tool 10 (e.g., tool speed, battery status, etc.).
The processing circuitry 210 may be configured to perform data processing, control function execution, or other processing and management services according to an example embodiment of the present invention. In some embodiments, the processing circuitry 210 may be embodied as a chip or chip set. In other words, the processing circuitry 210 may comprise one or more physical packages (e.g., chips) including materials, components, or wires on a structural assembly (e.g., a baseboard). The structural assembly may provide physical strength, conservation of size, or limitation of electrical interaction for component circuitry included thereon. The processing circuitry 210 may therefore, in some cases, be configured to implement an embodiment of the present invention on a single chip or as a single “system on a chip.” As such, in some cases, a chip or chipset may constitute means for performing one or more operations for providing the functionalities described herein.
In an example embodiment, the processing circuitry 210 may include a processor 212 and memory 214 that may be in communication with or otherwise control a tool interface 230. As such, the processing circuitry 210 may be embodied as a circuit chip (e.g., an integrated circuit chip) configured (e.g., with hardware, software or a combination of hardware and software) to perform operations described herein. However, in some embodiments, the processing circuitry 210 may be embodied as a portion of an on-board computer housed in the tool 10 with a tool manager 234 or communications manager 232 to control operation of the tool 10 relative to its interaction with other devices.
The tool manager 234 and the communications manager 232 of the controller 100 may be embodied as or otherwise controlled by the processing circuitry 210. However, in some cases, the processing circuitry 210 may be associated with only a specific one of the tool manager 234 or the communications manager 232, and a separate instance of processing circuitry may be associated with the other. Yet in some cases, the processing circuitry 210 could be shared between the tool manager 234 and the communications manager 232 or the processing circuitry 210 could be configured to instantiate both such entities. Thus, although
Each of the tool manager 234 and the communications manager 232 may employ or utilize components or circuitry that acts as a tool interface 230. The tool interface 230 may include one or more interface mechanisms for enabling communication with other devices (e.g., the tool 10 (via the sensor network 60) and associated information unit 70 or the user fitness device 250 (via a network 270)). In some cases, the tool interface 230 may be any means such as a device or circuitry embodied in either hardware, or a combination of hardware and software that may be configured to receive or transmit data from/to components in communication with the processing circuitry 210 via internal communication systems of the controller 100. With respect to the communications manager 232, the tool interface 230 may further include wireless communication equipment (e.g., a one way or two way radio) for at least receiving information from the user fitness device 250 via the network 270. As such, the tool interface 230 of the communications manager 232 may include an antenna and radio equipment for conducting Bluetooth, WiFi, or other short range communication, or for employing other longer range wireless communication protocols for communicating with the user fitness device 250 (via the network 270) instances associated with access to a wide area network. The network 270, in some cases, may be representative of a direct connection between the controller 100 and the sensor network 60, user fitness 250, information unit 70, or the like.
The processor 212 may be embodied in a number of different ways. For example, the processor 212 may be embodied as various processing means such as one or more of a microprocessor or other processing element, a coprocessor, a controller or various other computing or processing devices including integrated circuits such as, for example, an ASIC (application specific integrated circuit), an FPGA (field programmable gate array), or the like. In an example embodiment, the processor 212 may be configured to execute instructions stored in the memory 214 or otherwise accessible to the processor 212. As such, whether configured by hardware or by a combination of hardware and software, the processor 212 may represent an entity (e.g., physically embodied in circuitry in the form of processing circuitry 210) capable of performing operations according to embodiments of the present invention while configured accordingly. Thus, for example, when the processor 212 is embodied as an ASIC, FPGA or the like, the processor 212 may be specifically configured hardware for conducting the operations described herein. Alternatively, as another example, when the processor 212 is embodied as an executor of software instructions, the instructions may specifically configure the processor 212 to perform the operations described herein.
In an example embodiment, the processor 212 (or the processing circuitry 210) may be embodied as, include or otherwise control the operation of the controller 100 based on inputs received by the processing circuitry 210. As such, in some embodiments, the processor 212 (or the processing circuitry 210) may be said to cause each of the operations described in connection with the controller 100 relative to undertaking the corresponding functionalities associated therewith responsive to execution of instructions or algorithms configuring the processor 212 (or processing circuitry 210) accordingly.
In an example embodiment, the memory 214 may include one or more non-transitory memory devices such as, for example, volatile and/or non-volatile memory that may be either fixed or removable. The memory 214 may be configured to store information, data, applications, instructions or the like for enabling the processing circuitry 210 to carry out various functions in accordance with example embodiments. For example, the memory 214 could be configured to buffer input data for processing by the processor 212. Additionally or alternatively, the memory 214 could be configured to store instructions for execution by the processor 212. As yet another alternative or additional capability, the memory 214 may include one or more databases that may store a variety of data sets responsive to input from the tool 10 or the user fitness device 250, or any other functional units or devices from which the controller 100 has previously extracted data. Among the contents of the memory 214, applications may be stored for execution by the processor 212 in order to carry out the functionality associated with each respective application. In some cases, the applications may include instructions for recognition of certain user fitness data and for initiation of one or more responses to the recognition of the data as described herein.
In some embodiments, the tool manager 234 may be any means such as a device or circuitry embodied in either hardware, or a combination of hardware and software that may be configured to receive or transmit data (e.g., operational parameters of the tool 10, fitness data of the user fitness device 250) to/from the tool 10. The tool manager 234 may also control or provide electrical connections or interfaces between the controller 100 and the tool 10 to monitor the sensor network 60 and enable the tool manager 234 to implement operational, safeguard, or protective functions as appropriate. These functions may be implemented based upon examination of the tool data and comparison of such data to various predefined thresholds or limits received from the user fitness device 250. In this regard, the tool manager 234 may receive the tool data (e.g., operational parameters) from the sensor network 60 and control the storage of the tool data (e.g., operational parameters) extracted from the sensor network 60 in order for comparison with any fitness data received from the user fitness device 250.
In an example embodiment, the communications manager 232 may be any means such as a device or circuitry embodied in either hardware, or a combination of hardware and software that is configured to receive or transmit tool data from/to the tool 10. In this regard, the communication manager 232 may include a transceiver 233 to facilitate communication between the controller 100 and any network devices (via the network 270). The network devices being, for example, the user fitness device 250. The communication manager 232 may therefore receive fitness data of the user via the network 270. This fitness data may include average walking speed, heart rate, blood pressure, sweat volume, temperature, blood glucose levels, calories burned, UV exposure, oxygen content, or the like. The fitness data may be stored in association with a user based on a specific user identifier or a user profile. However, it should also be understood that the controller 100 may be configured to intuitively determine the user based on the fitness data received without any explicit knowledge of the identity of the user (e.g., a first user has a first average walking speed and a second user has a second average walking speed). In other words, the controller 100 may be configured to determine the identity of the user based on recognizable patterns from fitness data received.
Furthermore, the fitness data may also be stored in association with temporal information that may indicate the time (or time period) that the metrics were obtained by the user fitness device 250 or the time that the metrics were transmitted from the user fitness device 250. The fitness data may be retrieved by or sent to the controller 100 at regular intervals or continuously, for example, during operation of the tool 10. In this regard, the controller 100 may be configured to start receiving data from the user fitness device 250 in response to a power on condition of the tool 10, and this data may be received continuously, at regular interval, or at predefined times in order to intuitively adjust the operational parameters of the tool 10. In some cases, the data from the user fitness device 250 may be received even when the tool 10 is not operational. For example, the tool 10 may periodically (e.g., nightly) receive the data when non-operational in order to ensure the tool 10 is started with settings specifically tailored for the user.
In some embodiments, for example, the application server 340 may therefore include an instance of a data manager 344 comprising stored instructions for handling activities associated with practicing example embodiments as described herein. As such, in some embodiments, the user fitness device 250 (e.g., the user's mobile phone) may access the data manager 344 online via an application 322 and utilize the services provided thereby. However, it should be appreciated that in other embodiments, the data manager 344 may be initiated from an integrated memory of the user fitness device 250. It should be understood that the user fitness device 250 may be a fitness tracker located on a mobile phone or computing device of the user, for example. In other cases, however, the user fitness device 250 may be a computing device or mobile phone that has received health or fitness information from the user from an external fitness tracker (e.g., stand along fitness devices worn on wrist or the like).
In some example embodiments, the data manager 344 may be provided from the application server 340 (e.g., via download over the network 270) to the data manager 344 to enable the user fitness device 250 to instantiate an instance of the data manager 344 for local operation. As yet another example, the data manager 344 may be instantiated at the user fitness device 250 responsive to downloading instructions from a removable or transferable memory device carrying instructions for instantiating the data manager 344 at the user fitness device 250. In such an example, the network 170 may, for example, be a peer-to-peer (P2P) network where the data manager 344 includes an instance of the data manager 344 to enable another data manager 344 to act as a server to the user fitness device 250. In a further example embodiment, the data manager 344 may be distributed amongst the user fitness device 250 and the application server 340.
In an example embodiment, the application server 340 may include or have access to memory (e.g., internal memory or the database server 342) for storing instructions or applications for the performance of various functions and a corresponding processor for executing stored instructions or applications. For example, the memory may store an instance of the data manager 344 configured to operate in accordance with an example embodiment. In this regard, for example, the data manager 344 may include software for enabling the application server 340 to communicate with the network 270 or the user fitness device 250 for the provision or receipt of information associated with performing activities as described herein. Moreover, in some embodiments, the application server 340 may include or otherwise be in communication with an access terminal (e.g., a computer including a user interface) via which analysts may interact with, configure or otherwise maintain the system 100.
Furthermore, it should be understood that that applications executable at the application server 340 may include an application for reviewing, monitoring, or analyzing the data received from the tool 10 or the user fitness device 250. In some cases, the applications at the application server 340 may include an application for cloud management of the data received from the tool 10 or the user fitness device 250. Thus, for example, adaptive device settings, instructions or the like calculated or received from the data received may be used to specifically configure the device under identified circumstances or scenarios to maximize personalization of, for example, the tool 10 or, in some cases, a fleet of tools 10. In some example embodiments, either the application server 340 or the controller 100 may store configuration information specific to the tool 10 based on the fitness data of the user.
Accordingly, the controller 100 or the application server 340 or combination thereof may perform analysis of the operational parameters of the tool 10 and the fitness data of the user and generate alerts, configuration information, or the like that is specific to the tool 10. Thus, the data (device or fitness data) may be used for configuring the tool 10 accordingly, analyzing for trends, or other specific issues and then transmitted to the tool 10, and individual users or organizations can receive information specific to their tool 10. However, it should be understood that the information specific to the tool 10 may be benchmarked against the performance of other tools not associated with the individual users or organizations. This may be useful in determining the settings that correspond to optimal performance of the tool 10 and recommending the same to the user. Thus, the individual users or organizations can determine how hard they run their equipment or tools, or how well their battery or tool performs relative to all other tools monitored by the server network 332. Accordingly, it should be understood that the server network 332 may be used to monitor or receive data from several tools not necessarily owned or operated by the same organization or user (e.g., tools specific to a particular manufacturer or retailer).
Furthermore, as shown in
Thus, in accordance with example embodiments herein, the controller 100 (or in some cases the application server 340) may receive the operational parameters (i.e., the tool data) from the sensor network 60 of the tool 10 and the fitness data from the user fitness device 250. The fitness data may be analyzed in comparison to the sensor network data or other preset health or fitness thresholds or limits to determine if any adjustments are needed to various operating parameters of the tool 10 in order to provide a personalized and tailored operation of the tool 10 for the user. For example, at a general level, the controller 100 may receive information related to a drive speed of the tool 10 from the sensor network 60 and information related to a historical average walking speed of the user from the user fitness device 250—the historical average walking speed being based on a user fitness profile or previous data received from the user fitness device 250. If the historical average walking speed is greater than the drive speed of the tool 10, the controller 100 may be configured to cause the sensor network 60 to adjust the drive speed to an increased level to match the average walking speed of the user. If the historical average walking speed is less than the drive speed of the tool 10, the controller 100 may be configured to cause the sensor network 60 to adjust the drive speed to a decreased level to match the average walking speed of the user. In cases where the historical average walking speed of the user is substantially the same as the drive speed, the controller 100 will not cause the sensor network 60 to adjust the drive speed of the tool 10. For example, the controller 100 may receive data from the user fitness device 250 that the historical average walking speed of the user is 3 mph in normal conditions. Thus, in cases where the tool 10 is a walk-behind lawn mower (i.e., a tool used in normal ground conditions), the controller 100 may be configured to adjust the speed of the walk-behind lawn mower to 3 mph. Furthermore, the controller may additionally receive data from the user fitness device 250 that the historical average walking speed of the user is 2 mph in snow conditions. In cases, where the tool 10 is a snow thrower (i.e., a tool used in snow conditions), the controller 100 may be configured to adjust the speed of the snow thrower to 2 mph. Of course, it should be understood that the user may override or adjust the personalized drive speed via the application 322 or the informational unit 70.
As mentioned above, the data received from the user fitness device 250 may include average walking speed, heart rate, blood pressure, sweat volume, temperature, blood glucose levels, calories burned, UV exposure, oxygen content, or the like, or any combination thereof. Accordingly, any of these metric received by the controller 100 or the application server 340 may be used to adjust or configure the operational settings of the tool 10. In some cases, the operational settings of the tool 10 may be configured to never exceed the fitness ability of the user, as determined based on the data received from the user fitness device 250 or preset health or fitness thresholds. These thresholds may be set by the user via the informational unit 70 or the application 322 or may be thresholds recommended by various healthcare organizations (U.S. Federal Drug Administration or the like). For example, if the sweat volume or temperature of the user is detected as exceeding a predetermined limit, the controller 100 may be configured to decrease the operating speed of, power off the tool 10, recommend the user take a rest break, or the like in order to ensure well-being of the user (e.g., ensuring the user does not overheat, etc.). Furthermore, the controller 100 may be configured to take into account external parameters such as detected weather conditions, temperature, lot/lawn conditions, or the like when determining operational settings of the tool 10. These settings may be detected by the controller 100 or inputted as discussed herein.
Furthermore, in some example embodiments, the controller 100 may be configured to use the last received fitness data or metrics of the user to determine the initial settings of the tool 10 upon startup or powering on of the device. In other words, the last received fitness data or metrics of the user received by the controller may be predictive of initial startup settings of the next operation of the tool 10. In some cases, the controller 100 may be configured to average the health or fitness metrics of the user over a predetermined period of a time (e.g., a week, month, etc.) and use the average of the metrics to determine the initial settings of the tool 10 upon the startup of the tool 10.
In further example embodiments, the controller 100 may be configured to use the fitness data or metrics to calculate how long the remaining charge level of the battery-powered power source 14 will last at the detected fitness level of the user. In this regard, the controller 100 may be configured to use metrics such as the maximum or average walking speed of the user to determine how long the battery charge will last. This determination may be optionally communicated to the user (via application 322 or the information unit 70) such that the user has access to the remaining charge level of the battery pack 150 and can plan the use of the tool 10 accordingly. It should be understood that metrics that include determined maximums or averages (e.g., average or maximum walking speed) may be determined directly by the user fitness device 250 or by the controller 100 or the application server 340 based on data received by the user fitness device 250.
In some cases and as discussed above, the user via the application 322 or the information unit 70 may override or manually adjust or input any changes the controller 100 makes to the operation of the tool 10. For example, the user may manually increase or decrease an operating speed of the tool 10. Furthermore, the user may input lawn/lot size, ground condition, grass type, weather conditions, fitness goals, etc., and these conditions may be used to in determining the personalized settings of the tool 10 or otherwise configuring the tool 10 accordingly. Additionally, the controller may be configured to cause, either on the application 322 or the information unit 70, an alert or warning that notifies the user that a metric of the user fitness profile has been exceeded (e.g., blood pressure, temperature, etc.). The alert may give the user the option to override the alert or warning within a predetermined period of time (e.g., 30 seconds) in order to avoid a change in operational parameters of the tool 10 (e.g., shutdown of the tool 10).
In accordance with other example embodiments, the controller 100 may be configured to recommend settings of the tool 10 to ensure the tool 10 is being operated in a manner that ensures the most efficient and optimum operation of the tool 10. In this regard, based on the fitness data received by the controller 10, the tool 10 may be operated according to conditions that correspond to the fitness data of the user. However, these operating conditions may not necessarily correspond to operating conditions that will ensure optimal performance of the tool 10. Accordingly, the controller 100 may recommend operating conditions that will enable the tool 10 to operate at an optimal performance level. The user may then have the option to adjust the settings to correspond to optimal performance operating conditions rather than exclusively or periodically based on the fitness data or metrics.
It should also be understood that the user may have access to the data that is being communicated to the controller 100 or the application server 340. For example, the user may be notified (via the application 322 or the information unit 70) when the controller 100 changes operational parameters or when the controller 100 has recommendations. In this regard, the controller 100 may cause one or more alerts or reports to be displayed, via application 322, on the user fitness device or the information unit 70.
Furthermore, a manufacturer or retailer may have access to the data (e.g., via the server network 332) in order to enable the manufacturer or retailer to make recommendations regarding use of the tool 10 or if a different tool 10 will enable the user to achieve better performance and further optimize the time spent with the tool 10. The data may also be recorded or stored via the server network 332 so that the data may be transferred to a new tool 10 in the event the user replaces the tool 10.
Additionally, while embodiments described herein were generally described in relation to a single user of the tool 10, the capability of the system 310 may be particularly useful in applications that involve the management of a fleet of devices 110 used in a commercial setting. A manager of the fleet, for example, may then have the ability to monitor the health and safety of the users operating the tools 10 in the fleet and ensure each tool 10 of the fleet is being operated appropriately.
As can be appreciated from the example embodiments above, some embodiments may provide a controller 100 that may receive certain operational parameters from the tool 10 and certain fitness data from the user fitness device 250. The fitness data may be compared, by the controller 100, to the operational parameters of the tool 10 or other preset thresholds to determine personalized operating settings for the specific user. In order to determine the personalized operating settings of the user, different communication paradigms and analyses may be performed on the operational parameters and fitness data.
At operation 422, the controller may cause the tool 10 (via the sensor network 60) to change the operational settings of the tool 10 accordingly. Even after the adjustment of operational settings of the tool 10, the controller 100 may continue to extract operational parameters from the tool 10 by the controller 100 at predetermined times at operation 424. User fitness data may also be continued to be periodically received from the user fitness device 250 by the controller 100 at operation 426. Of course, it should be understood that rather than periodically receiving data from the tool 10 and the user fitness device 250, the data may continually be received and monitored by the controller 100, for example, during operation of the tool 10. At operation 430, the controller 100 may again compare the operational parameters to the user fitness data or preset thresholds to ensure the tool 10 is operating in a manner to ensure optimum user health. If necessary, at operation 440, the controller 100 may again determine if adjustments are needed to the operational parameters. In this example, no further operational changes were communicated to the tool 10 by the controller 100. Further receipt of the operational parameters from the tool 10 was received by the controller 100 at operation 444. At operation 450, the controller 100 may detect a power off condition of the tool 10 (e.g., current draw below a predetermined threshold).
In the example of
In the example of
The method may include, detecting a power or startup condition of the tool 10 at operation 700. The method may further include extracting operational parameters from the tool 10 at operation 712 and receiving fitness data of the user from the user fitness device 140 at operation 714. The operational parameters may include the battery status, energy efficiency, device speed, blade speed, blade height, or the like of the tool 10, and the fitness data may include average walking speed, heart rate, blood pressure, sweat volume, temperature, blood glucose levels, calories burned, UV exposure, oxygen content, or the like. These operational parameters may be compared to the fitness data of the user at operation 720. In some cases, the comparison may include establishing an initial user fitness profile based on data inputted from or sent via the user in association with, for example, an initial use of the tool 10, the data previously received from previous operations of the device (e.g., machine learned), or preset health thresholds received either from the user or based on recommendations from health organizations.
The user fitness profile may include a maximum and average walk speed of the user, a resting and active heart rate, recommended UV exposure, blood pressure, temperature and sweat volume guidelines, or the like. In this regard, the user fitness profile may be a static profile during use of the tool 10 that is set at a predetermined time (before or after an operation of the device) for use during the operation of the tool 10. However, it should be understood that the user fitness profile may change periodically—after each of use of the tool 10, for example, to account for new fitness data received—and used to compare to the tool data. In this regard, the user fitness profile and the tool data may be used as a benchmark against all received fitness data of the user received during user of the tool 10. For instance, the user fitness profile may be used to enable the user to achieve particular fitness goals or to ensure the safety of the user. The comparison of the received fitness data of the user to the sensor data and the user fitness profile may be used to monitor the work level of the user or to ensure control over various components of the tool 10 (e.g., working assembly or mobility assembly 20).
The method may also include determining adjustments to the operational parameters to ensure the operational settings of the tool 10 correspond to the user's fitness profile at operation 730 and causing the adjustments to the operational parameters of the tool 10 in accordance with the instructions received at operation 740. The determination of adjustments includes, for instance, that if the user fitness profile contains a maximum heart rate and data received from the user fitness device 250 indicates that user's detected rate is above this maximum heart rate, the controller 100 may cause a shut down or slowdown of the tool 10. The slowdown of the tool 10 may include a slowdown only to the mobility assembly 20. In some cases, any change to the mobility assembly 20 may also include a corresponding change to the working assembly or various other components of the tool 10. In some cases, in response to the receipt of data that indicates that the tool 10 has been in operation for 2.5 hours, which exceeds the recommend UV exposure of 2 hours as set forth in the user's fitness profile, the controller 100 may cause a shutdown of the tool 10. Of course, these examples should be understood to be in no way limiting to the capability of the controller 100 described herein.
Example embodiments therefore represent a controller for an outdoor power equipment tool. The controller may include processing circuitry operably coupled to a sensor network of the outdoor power equipment tool and in data communication with a network. The processing circuitry is configured to receive fitness data of a user from a fitness device via the network. The processing circuitry is further configured to receive sensor data from the sensor network, the sensor data corresponding to operational parameters of the outdoor power equipment tool. The processing circuitry is even further configured to compare the fitness data to the sensor data, and in response to the comparison of the fitness data to the sensor data, causing an adjustment to the operational parameters of the outdoor power equipment tool.
In some embodiments, additional optional structures or features may be included or the structures/features described above may be modified or augmented. Each of the additional features, structures, modifications, or augmentations may be practiced in combination with the structures/features above or in combination with each other. Thus, some, all or none of the additional features, structures, modifications, or augmentations may be utilized in some embodiments. Some example additional optional features, structures, modifications, or augmentations are described below, and may include, for example, that the comparison of the fitness data to the sensor data further includes comparing the fitness data to the sensor data and preset fitness thresholds, and in response to the comparison of the fitness data to the sensor data or preset fitness thresholds, causing the adjustment to the operational parameters. Alternatively or additionally, the comparison of the fitness data to the sensor data may further include comparing the fitness data to the sensor data and preset fitness thresholds, and in response to the comparison of the fitness data to the sensor data or preset fitness thresholds, causing the adjustment to the operational parameters. Alternatively or additionally, the comparison of the fitness data to the sensor data may further include comparing the fitness data to the sensor data and preset fitness thresholds, and in response to the comparison of the fitness data to the sensor data or preset fitness thresholds, causing the adjustment to the operational parameters. Alternatively or additionally, the preset fitness thresholds or the fitness data associated with a previous operation of the outdoor power equipment tool may be used to create a user fitness profile, the comparison of the fitness data to the sensor data and the preset fitness thresholds including comparing fitness data being currently received to the sensor data and the user fitness profile, and in response to the comparison of the fitness data currently being received to the sensor data or the user fitness profile, causing the adjustment to the operational parameters of the outdoor power equipment tool. Alternatively or additionally, the user fitness profile may remain static during operation of the outdoor power equipment tool. Alternatively or additionally, the user fitness profile may be updated before or after the operation of the outdoor power equipment tool based on the fitness data received during the previous operation of the outdoor power equipment tool. Alternatively or additionally, the processing circuitry may be configured to set initial operational parameters of the outdoor power equipment tool based on the user fitness profile. Alternatively or additionally, the preset fitness thresholds may be also based in part on recommendations from a healthcare organization. Alternatively or additionally, the operational parameters may include battery status, energy efficiency, device speed, blade speed, or blade height. Alternatively or additionally, the fitness data may include heart rate, blood pressure, sweat volume, temperature, blood glucose levels, calories burned, UV exposure, or oxygen content. Alternatively or additionally, the outdoor power equipment tool may be a walk behind lawn care device. Alternatively or additionally, the adjustment to the operational parameters may include adjusting a speed of a mobility assembly of the outdoor power equipment tool. Alternatively or additionally, adjusting the speed of the mobility assembly may cause a corresponding adjustment to a speed of the working assembly.
Many modifications and other embodiments of the inventions set forth herein will come to mind to one skilled in the art to which these inventions pertain having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the inventions are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Moreover, although the foregoing descriptions and the associated drawings describe exemplary embodiments in the context of certain exemplary combinations of elements or functions, it should be appreciated that different combinations of elements or functions may be provided by alternative embodiments without departing from the scope of the appended claims. In this regard, for example, different combinations of elements or functions than those explicitly described above are also contemplated as may be set forth in some of the appended claims. In cases where advantages, benefits or solutions to problems are described herein, it should be appreciated that such advantages, benefits or solutions may be applicable to some example embodiments, but not necessarily all example embodiments. Thus, any advantages, benefits or solutions described herein should not be thought of as being critical, required or essential to all embodiments or to that which is claimed herein. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/IB2018/058163 | 10/19/2018 | WO |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2020/079480 | 4/23/2020 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
5314389 | Dotan | May 1994 | A |
5893817 | Morgan | Apr 1999 | A |
8938261 | Lee et al. | Jan 2015 | B2 |
9319860 | Tanaka et al. | Apr 2016 | B2 |
9973831 | Mejegård | May 2018 | B2 |
10032123 | Mejegård | Jul 2018 | B2 |
11055979 | Hitt | Jul 2021 | B1 |
11297766 | Wynn-Grayson | Apr 2022 | B1 |
11701063 | Hitt | Jul 2023 | B2 |
20070037668 | Cofrin | Feb 2007 | A1 |
20140303899 | Fung | Oct 2014 | A1 |
20150105687 | Abreu | Apr 2015 | A1 |
20150123815 | Mejegard | May 2015 | A1 |
20180126248 | Dion | May 2018 | A1 |
20180263182 | Albinger | Sep 2018 | A1 |
20190077003 | Lennings | Mar 2019 | A1 |
20200245938 | Xu | Aug 2020 | A1 |
20210052221 | Panneer Selvam | Feb 2021 | A1 |
20210153754 | Ozawa | May 2021 | A1 |
20210169417 | Burton | Jun 2021 | A1 |
20210213956 | Schön | Jul 2021 | A1 |
20210299518 | Brammer | Sep 2021 | A1 |
20220176829 | Haugen | Jun 2022 | A1 |
20230172101 | Lardieri | Jun 2023 | A1 |
Number | Date | Country |
---|---|---|
107065796 | Aug 2017 | CN |
108040578 | May 2018 | CN |
202006008176 | Aug 2006 | DE |
H0521938 | Mar 1993 | JP |
WO-2014120893 | Aug 2014 | WO |
2017151045 | Sep 2017 | WO |
WO-2017151045 | Sep 2017 | WO |
Entry |
---|
International Search Report and Written Opinion in the International Application No. PCT/IB2018/058163 dated Jul. 1, 2019. |
Number | Date | Country | |
---|---|---|---|
20210389735 A1 | Dec 2021 | US |