TREADMILL POWER STATION

[0001] Many treadmills employ current sensors internal to their motor controllers in order to improve the smoothness of the motor and/or belt. These sensors, however, are internal to the electrical system in the treadmill and do not interact with or monitor other, external, treadmills.

[0002] The disclosed Treadmill Power Station is connected between a treadmill and its power outlet. The Treadmill Power Station contains a power consumption sensor that reads information about the usage of the treadmill by externally analyzing its power consumption pattern, much as a cardiologist would interpret an EKG strip. Information that can be derived in this manner includes, but is not limited to, the user's speed, distance covered and step count, as well as the general power consumption trend for the treadmill itself.

[0012] In FIG. 1, dotted lines illustrate an electrical connection, while solid lines indicate a logical connection. In FIG. 1, logical and electrical connections may be routed through the Treadmill Power Station 300. In FIG. 1, both types of connections are shown between all of the devices, though in embodiments and/or use cases certain of the connections may not be present. For example, there may not be either logical or electrical connection between Treadmill-Desk Controller 120 and Treadmill 110 (or Desk 115), such as if Treadmill 110 (or Desk 115) is provided by a third party. In this example, Treadmill 110 may still connect to Treadmill Power Station 300 and Treadmill-Desk Controller 120 may view activity at Treadmill 110 via Treadmill Power Station 300.

[0013] In FIG. 1, Treadmill Power Station 300 is designed to take any treadmill and make it an “internet appliance” so that information about the treadmill user's performance, as well as the maintenance condition of the treadmill itself can be uploaded to remote computers, such as the Treadmill Server 200, and shared with various applications.

[0014] Treadmill Power Station 300 is connected between Treadmill 110 and its power outlet. Treadmill Power Station 300 contains a power consumption sensor that, in conjunction with Client-Side Power Consumption Monitor Routine 360, reads information about the usage of the treadmill by externally analyzing its power consumption pattern. Information that can be derived in this manner includes, but is not limited to, the user's speed, distance covered and step count, as well as the general power consumption trend for the treadmill itself. Embodiments of circuitry utilized by Treadmill Power Station 300 are illustrated in FIGS. 4-9.

[0015] Treadmill Power Station 300 employs a current sensor external to the treadmill system. In being an external device with no need to interface directly to the control electronics in the treadmill, it can be used universally with any model of treadmill. The current sensor may be monitored by Client-Side Power Consumption Monitor Routine 360. An example of an embodiment of a current sensor is illustrated in FIGS. 5, 6, and 7.

[0016] Client-Side Power Consumption Monitor Routine 360 can provide a number of different services, including but not limited to:

[0017] Showing the user performance data such as accurate representation of time spent walking (leaving out pauses in which no user was on the belt), distance covered, calories burned, steps taken and other derivative data. Treadmills ordinarily record such information internally but the data can be inaccurate if the user stepped off the treadmill at any time without pausing the motor.

[0018] Showing the treadmill desk owner, operator, service provider and/or manufacturer the usage patterns of the equipment.

[0019] Triggering maintenance notifications when power consumption trends indicate a treadmill is in need of lubrication or repair. On treadmills equipped with an automatic lubrication system employing a reservoir of lubricate, notification signals can be sent directly to Treadmill 110 when high friction causes the power consumption level to exceed acceptable levels.

[0020] Electricity usage can be derived and retained for the purpose of understanding the economic and ecological impact of the activities on Treadmill 110.

[0021] Information from Client-Side Power Consumption Monitor Routine 360 can be uploaded to Server-Side Power Consumption Monitor Routine 260 to provide server-side services relating to power consumption.

[0022] Treadmill Power Station 300 connects via Wi-Fi, Ethernet port - or any other available method of connected to a network or the Internet—to a server, such as Treadmill Server 200, that is used to collect data from any number of treadmill desk workstations in the field. Users can also record preferences for desk and monitor height settings (for treadmill desk applications) and for preferred speed an incline settings for the treadmill.

[0023] Treadmill Power Station 300 may also contain a web- or Internet-connected power switch controlled by Server-Side Remote Control Power Switch Routine 265 in Treadmill Power Station 200 and Client-Side Remote Control Power Switch Routine 365 in Treadmill Power Station 300 so that power to the treadmill can be remotely turned on or off by an application executed by, for example, External Computer 160. An example of an embodiment of such a relay is illustrated in FIGS. 8 and 9. For example, in a large organization or in the case of a publicly accessible treadmill or treadmill desk (e.g. library, airport lounge, hotel business center) the operator of the facility, or the employer, may want to limit use of the treadmill or treadmill desk only to individuals who have a) identified themselves, b) accepted a liability waiver, and/or c) have an account on the server for storing their personal performance information and equipment setting preferences. A login procedure would be followed through either the treadmill's controller, such as Treadmill-Desk Controller 120 (if electronically linked to Treadmill Power Station 300) or any web or smartphone application (as may be executed by External Computer 160). Once logged in and the liability waiver is acknowledged the treadmill power would be toggled on by Server-Side Remote Control Power Switch Routine 265 and Client-Side Remote Control Power Switch Routine 365. Facility operators and employers may also set certain limitations on the use of the equipment—such as allowable top speed—monitored and enforced by and through Treadmill Power Station 300 and applications that connect to it, such as via Treadmill Server 200.

[0024] Treadmill Power Station 300 derives information from the power consumption analysis performed by Client-Side Power Consumption Monitor Routine 360 by having a Performance Profile Table 370 stored in memory of the power consumed when a person weighing (x) pounds walks or runs at speed (y). A stored program will upon initialization and from time to time thereafter remind users to calibrate the system by performing a routine of walking at incrementally faster speeds, and recording their current body weight in the system. Power consumption profile models can be derived by aggregating multiple users' calibration profiles in Treadmill Server 200. Default profiles, such as Default Profile 270, for common treadmill models can also be downloaded to or included in the programming of Treadmill Power Station 300, based on tests of factory-new units.

[0025] FIG. 2 is a functional block diagram of an exemplary Treadmill Server 200 computing device and some data structures and/or components thereof. The computing device 200 comprises at least one Processing Unit 210, Treadmill Server Memory 250, and an optional Display 240, all interconnected along with the Network Interface 230 via a Bus 220. The Network Interface 230 may be utilized to form connections with the Network 150 and to send and receive radio frequency (“RF”) and other wireless and wireline signals.

[0026] Treadmill Server Memory 250 generally comprises a random access memory (“RAM”), a read only memory (“ROM”), and a permanent mass storage device, such as a disk drive or SDRAM (synchronous dynamic random-access memory). Treadmill Server Memory 250 stores program code for software routines, such as, for example, Server-Side Power Consumption Monitor Routine 260 and Server-Side Remote Control Power Switch Routine 265 as well as browser, webserver, email client and server routines, camera, other client applications, and database applications. In addition, Treadmill Server Memory 250 also stores Operating System 255. These software components may be loaded from a non-transient Computer Readable Storage Medium 295 into Treadmill Server Memory 250 of the computing device using a drive mechanism (not shown) associated with a non-transient Computer Readable Storage Medium 295, such as a floppy disc, tape, DVD/CD-ROM drive, memory card, or other like storage medium. In some embodiments, software components may also or instead be loaded via a mechanism other than a drive mechanism and Computer Readable Storage Medium 295 (e.g., via Network Interface 230).

[0027] The computing device 200 may also comprise hardware supported input modalities, Input 245, such as, for example, a touchscreen, a keyboard, a mouse, a trackball, a stylus, a microphone, accelerometer(s), compass(es), RF receivers (to the extent not part of the Network Interface 230), and a camera, all in conjunction with corresponding routines.

[0028] Treadmill Server 200 may also comprise or communicate via Bus 220 with a datastore utilized by Treadmill Server 200. In various embodiments, Bus 220 may comprise a storage area network (“SAN”), a high speed serial bus, and/or via other suitable communication technology. In some embodiments, Treadmill Server 200 may communicate with the datastore via Network Interface 230. Treadmill Server 200 may, in some embodiments, include many more components than those shown in this Figure. However, it is not necessary that all of these (or other) generally conventional components be shown in order to disclose an illustrative embodiment.

[0029] Treadmill Server 200 is illustrated in FIG. 2 as comprising data groups for routines, such as routines for Server-Side Power Consumption Monitor Routine 260 and Server-Side Remote Control Power Switch Routine 265. Additional data groups for routines, such as for a webserver and web browser, may also be present on and executed by Treadmill Server 200. Webserver and browser routines may provide an interface for interacting with the other computing devices illustrated in FIG. 1 (all which may serve and respond to data and information in the form of webpages and html documents or files). The browsers and webservers are meant to illustrate user-interface and user-interface enabling routines generally, and may be replaced by equivalent routines for serving and rendering information to and in a user interface in a computing device (whether in a web browser or in, for example, a mobile device application).

[0030] FIG. 3 is a functional block diagram of an exemplary Treadmill Power Station 300 computing device and some data structures and/or components thereof. The computing device 300 comprises at least one Processing Unit 310, Treadmill Power Station Memory 350, and an optional Display 340, all interconnected along with the Network Interface 330 via a Bus 320. Network Interface 330 may be utilized to form connections with the Network 150 and to send and receive radio frequency (“RF”) and other wireless and wireline signals.

[0031] Treadmill Power Station Memory 350 generally comprises a random access memory (“RAM”), a read only memory (“ROM”), and a permanent mass storage device, such as a disk drive or SDRAM (synchronous dynamic random-access memory). Treadmill Power Station Memory 350 stores program code for software routines, such as, for example, Client-Side Power Consumption Monitor Routine 360 and Client-Side Remote Control Power Switch Routine 365 as well as browser, webserver, email client and server routines, camera, other client applications, and database applications. In addition, Treadmill Power Station Memory 350 also stores Operating System 355. These software components may be loaded from a non-transient Computer Readable Storage Medium 395 into Treadmill Power Station Memory 350 of the computing device using a drive mechanism (not shown) associated with a non-transient Computer Readable Storage Medium 395, such as a floppy disc, tape, DVD/CD-ROM drive, memory card, or other like storage medium. In some embodiments, software components may also or instead be loaded via a mechanism other than a drive mechanism and Computer Readable Storage Medium 395 (e.g., via Network Interface 330).

[0032] The computing device 300 may also comprise hardware supported input modalities, Input 345, such as, for example, a touchscreen, a keyboard, a mouse, a trackball, a stylus, a microphone, accelerometer(s), compass(es), RF receivers (to the extent not part of the Network Interface 330), and a camera, all in conjunction with corresponding routines.

[0033] Treadmill Power Station 300 may also comprise or communicate via Bus 320 with a datastore utilized by Treadmill Power Station 300. In various embodiments, Bus 320 may comprise a storage area network (“SAN”), a high speed serial bus, and/or via other suitable communication technology. In some embodiments, Treadmill Power Station 300 may communicate with the datastore via Network Interface 330. Treadmill Power Station 300 may, in some embodiments, include many more components than those shown in this Figure. However, it is not necessary that all of these (or other) generally conventional components be shown in order to disclose an illustrative embodiment.

[0034] Treadmill Power Station 300 is illustrated in FIG. 3 as comprising data groups for routines, such as routines for Client-Side Power Consumption Monitor Routine 360 and Client-Side Remote Control Power Switch Routine 365. Additional data groups for routines, such as for a webserver and web browser, may also be present on and executed by Treadmill Power Station 300. Webserver and browser routines may provide an interface for interacting with the other computing devices illustrated in FIG. 1 (all which may serve and respond to data and information in the form of webpages and html documents or files). The browsers and webservers are meant to illustrate user-interface and user-interface enabling routines generally, and may be replaced by equivalent routines for serving and rendering information to and in a user interface in a computing device (whether in a web browser or in, for example, a mobile device application).