Systems and methods for automatic configuration and automatic calibration of continuously variable transmissions and bicycles having continuously variable transmissions

Information

  • Patent Grant
  • 12145690
  • Patent Number
    12,145,690
  • Date Filed
    Tuesday, June 6, 2023
    a year ago
  • Date Issued
    Tuesday, November 19, 2024
    a month ago
Abstract
A continuously variable transmission on a bicycle may be automatically configured with little or no assistance from a user. Optical scanning devices, RFIDs, and other information capturing technology can communicate with a controller. The controller may then perform a portion or all of a configuration process. In operation, a controller may determine that calibration is needed. A calibration process may be initiated and performed with little or no user interaction. A calibration process may account for a load, a power source, or an environment.
Description
SUMMARY

Embodiments disclosed herein may be integrated with an automatic ratio adjusting system or may otherwise extend the functionality of an automatic ratio adjusting system. The ratio adjusting system may be used to change the transmission ratio over a range of transmission ratios. Systems and methods disclosed herein may ensure the entire range is available.


Systems disclosed herein may be communicatively coupled via a controller area network (CAN). Communicative coupling may involve a wireless or wired connection, and may involve continuous communication or discontinuous communication for the purpose of sending and receiving information from any of several components.


In one broad respect, an auto-configuration system may include a controller area network (CAN) with a system controller communicatively coupled to sensors and a CVT controller. At start up, the system controller sends a mutually pre-defined packet over the CAN bus to the CVT controller which stores information about components.


In another broad respect, embodiments disclosed herein may be directed to a system and method for determining a physical configuration of a bicycle and for determining an operational configuration of the bicycle. A user aligns components of the bicycle within a virtual overlay depicted on a screen. A picture of the rear gear is used to determine the number of rear gear teeth, the rear gear size, and other rear gear information. A picture of the rear wheel is used to determine the rear wheel diameter and the relationship in size between the rear wheel and the rear gear. A picture of the front gear is used to determine the number of front gear teeth and the front gear size. A picture of the entire bicycle is used to determine physical properties of the bicycle, the chain length, and other metric information, which is used to determine operational parameters of the bicycle.


Calibration may use an adaptive algorithm, including identifying a polynomial or other equation, and using empirical data. A first polynomial may characterize the performance of a CVT under a first load, and a second polynomial may characterize the performance of a CVT under a second load. In other settings, a single polynomial may characterize the performance of a CVT and values for different variables within the polynomial may be changed to characterize the performance of the CVT under different loads.


In one embodiment, a system for automatic calibration of a bicycle includes a first controller having a first processor and a first memory storing a first set of instructions executable by the first processor and adapted to: initiate a camera function; determine if a first image of a first component of the bicycle exists; if an image of the first component of the bicycle exists, determine a physical characteristic of the first component. The system also includes a second set of instructions adapted to control one or more of a continuously variable transmission and an electric motor based on the physical characteristic of the first component. The first component can include a gear. The system can include an overlay on a display coupled to the first processor adapted to aid a user in determining if the first image of the first component is correlated with the overlay. In some embodiments, the first controller is part of a smart phone, a personal data assistant, or a tablet. The system can include a second controller having a second processor and a second memory, wherein the second set of instructions is at least in part stored on the second memory and executed by the second processor. The first controller can be a portable computing device. The second controller can be coupled to the bicycle. The first controller can be further adapted to: determine if a second image of a second component of the bicycle exists; and determine a physical characteristic of the second component, wherein the second processor is adapted to control one or more of the continuously variable transmission and the electric motor based on one or more of the physical characteristic of the first component and the physical characteristic of the second component. In one embodiment, the first component is a first gear and the second component is a second gear, and the first set of instructions are executable to determine a gear ratio based on the first gear and the second gear. In another embodiment, the first component is a first gear and the second component is a second gear, and the second set of instructions are executable to determine a gear ratio based on the first gear and the second gear. In a further embodiment, the first component is a first gear and the second component is a wheel, and the first set of instructions are executable to determine a motor speed based on the first gear and the wheel.


A system for automatic calibration of a bicycle is provided. The system includes a first computer adapted to determine a first set of operating parameters of the bicycle, and communicate the first set of operating parameters to a second computer. The second computer has a set of instructions to: determine a first characteristic of a first component; and control a continuously variable transmission based on the first component and the first set of operating parameters. In one embodiment, the first set of operating parameters are associated with a road bicycle. Control of the continuously variable transmission based on the first component and the first set of operating parameters includes optimizing the continuously variable transmission for a rider on substantially paved roads. In another embodiment, the system includes an electric motor and the first set of operating parameters are associated with a road bicycle. Control of the continuously variable transmission based on the first component and the first set of operating parameters includes optimizing the continuously variable transmission and the electric motor for a rider on substantially paved roads. In a further embodiment, the first set of operating parameters are associated with a mountain bicycle, and control of the continuously variable transmission based on the first component and the first set of operating parameters includes optimizing the continuously variable transmission for a rider on unpaved routes. In still a further embodiment, the system includes an electric motor and the first set of operating parameters are associated with a mountain bicycle. Control of the continuously variable transmission based on the first component and the first set of operating parameters includes optimizing the continuously variable transmission and the electric motor for a rider on unpaved routes. In yet another embodiment, the first set of operating parameters are associated with a commercial bicycle, and control of the continuously variable transmission based on the first component and the first set of operating parameters includes optimizing the continuously variable transmission for a rider transporting heavy items. In yet a further embodiment, the system includes an electric motor, and the first set of operating parameters are associated with a commercial bicycle. Control of the continuously variable transmission based on the first component and the first set of operating parameters includes optimizing the continuously variable transmission and the electric motor for a rider transporting heavy items. In some embodiments, determining the first characteristic of the first component includes determining one of a gear size, a gear tooth count, a wheel size, a chain length, a gear ratio, a frame size, a length of a frame member and a seat height.


A method for automatic calibration of a bicycle can include determining a frame size of the bicycle; determining a wheel size for the bicycle; determining a front gear size for the bicycle; determining a rear gear size for the bicycle; determining an operating range for a continuously variable transmission based on the frame size, wheel size, front gear size or rear gear size for the bicycle; and communicating a set of instructions for controlling a continuously variable transmission (CVT) based on the determined operating range. The wheel size can correspond to a mountain bike, and the set of instructions can be executable to control a CVT under mountain biking conditions. The set of instructions can be communicated to a continuously variable transmission controller. The set of instructions can be communicated to a bike controller. A first portion of the set of instructions can be communicated to a continuously variable transmission controller and a second portion of the set of instructions can be communicated to a CVT controller. The first portion of the set of instructions can consist of instructions for adjusting a continuously variable transmission. The first portion of the set of instructions can be for calculating a continuously variable transmission ratio. The first portion of the set of instructions can be for looking up a continuously variable transmission ratio in a data structure stored in memory. The first portion of the set of instructions can be for looking up a continuously variable transmission ratio in a table stored in memory. The second portion of the set of instructions can be instructions for adjusting a continuously variable transmission. The second portion of the set of instructions can be for calculating a continuously variable transmission ratio. The second portion of the set of instructions can be for looking up a continuously variable transmission ratio in a data structure stored in memory. The second portion of the set of instructions can be for looking up a continuously variable transmission ratio in a table stored in memory. The second portion of the set of instructions can further include instructions for controlling an electric motor.


A method for configuring a bicycle can include: communicating, at startup by a continuously variable transmission controller, a first packet of information to a bike controller, the packet of information containing one or more operating parameters for a continuously variable transmission; and communicating, at startup by a continuously variable transmission controller, a first packet of information to a bike controller, the packet of information containing one or more operating parameters for a continuously variable transmission.


A method for configuring a bicycle can include presenting a display via a graphical user interface (GUI); receiving, via the GUI, one or more user inputs; and operating the bicycle according to a set of parameters based on the one or more user inputs. At least one user input can correspond to a cadence. At least one user input can correspond to a gear ratio. At least one user input can correspond to a desired riding performance. At least one user input can correspond to a distance. At least one user input can correspond to a bicycle speed. At least one user input can correspond to a load. Operating the bicycle according to a set of parameters can include determining an algorithm for operating the bicycle. Operating the bicycle according to a set of parameters based on the one or more user inputs can include: operating the bicycle according to a first algorithm; determining a second algorithm based on the set of parameters; and replacing the first algorithm with the second algorithm. The set of parameters can include information about one or more components on the bicycle. The one or more components can include one or more of a continuously variable transmission, an electric motor, a rear gear, a front gear, a chain length, and a physical configuration of the bicycle. The method can further include communicating the second algorithm to a server. Operating the bicycle according to a set of parameters based on the one or more user inputs can include operating the bicycle according to a first algorithm; determining a second algorithm based on the one or more user inputs; and replacing the first algorithm with the second algorithm. The one or more user inputs comprises an operating mode or a target cadence.


A method for determining an operating range for a continuously variable transmission (CVT) on a bicycle can include determining a first ratio point from a first wheel speed; adjusting a continuously variable transmission ratio at a predetermined rate to a first physical limit; and calculating, based on a time needed to reach the first physical limit from the first ratio point, a second physical limit of the continuously variable transmission. The first physical limit can be full underdrive. The first physical limit can be full overdrive. Adjusting a continuously variable transmission ratio at a predetermined rate can include changing the tilt angle of a ball planetary type CVT at a predetermined rate. Adjusting a continuously variable transmission ratio at a predetermined rate can include changing a beta angle of a first stator relative to a second stator of a ball planetary type CVT at a predetermined rate. The predetermined rate can be linear. Determining a first ratio point can be based on an encoder position.


A method of controlling a continuously variable transmission (CVT) can include operating the CVT according to an open loop process under a first set of operating conditions; and operating the CVT according to a closed loop process under a second set of operating conditions. The first set of operating conditions can include low load conditions. The second set of operating conditions can include high load conditions. The second set of operating conditions can include high pedal rotational speed conditions. The second set of operating conditions can include high pedal rotational speed conditions in excess of 80 revolutions per minute. The second set of operating conditions can include high pedal rotational speed conditions in excess of 90 revolutions per minute. The second set of operating conditions can include high pedal rotational speed conditions in excess of 100 revolutions per minute. The second set of operating conditions can include high pedal rotational speed conditions in excess of 110 revolutions per minute.


A method of controlling a continuously variable transmission (CVT) can include operating the CVT according to a first polynomial under a first set of operating conditions; and operating the CVT according to a second polynomial under a second set of operating conditions. The first set of operating conditions can include low load conditions. The second set of operating conditions can include high load conditions. The second set of operating conditions can include high pedal rotational speed conditions. The second set of operating conditions can include high pedal rotational speed conditions in excess of 80 revolutions per minute. The second set of operating conditions can include high pedal rotational speed conditions in excess of 90 revolutions per minute. The second set of operating conditions can include high pedal rotational speed conditions in excess of 100 revolutions per minute. The second set of operating conditions can include high pedal rotational speed conditions in excess of 110 revolutions per minute.


A method of controlling a continuously variable transmission includes: during a ride, operating a continuously variable transmission according to a first algorithm; storing, by the controller in a memory, data for the bicycle over a predetermined time period, wherein the data includes a predicted distance associated with a rear wheel speed and a cadence in accordance with the first algorithm; if the rear wheel speed and the cadence remain substantially constant over the predetermined time period: determining the actual distance covered during the predetermined time period; and determining a second algorithm based on the actual distance covered; and operating the continuously variable transmission according to the second algorithm. Determining the actual distance covered can include comparing a first set of GPS coordinates from a beginning of a data set with a second set of GPS coordinates from an end of the data set. Determining the actual distance covered can include comparing the rear wheel speed over time to a set of GPS coordinates.


A method of configuring a controller for a continuously variable transmission on a bicycle can include the steps of: establishing a first configuration setting; monitoring a set of riding data to determine when a steady state speed is maintained for a specified period of time; recording said riding data until the earlier of a second specified period or until the riding data deviates by a predetermined amount from the steady state speed; identifying a control set of data by comparing a first set of GPS data at the beginning of the recorded data to a second set of GPS data at the end of the recorded data; comparing the recorded data against the control set of data to develop an error value; and establishing a second configuration setting for the controller based on the error value. The method can further include requesting and receiving an input of information from a user; and correlating the information received from the user with a set of stored data to establish the first configuration setting. The information that is provided in the input of information step can include one or more of the following; bicycle model, tire size, front chain ring teeth, rear cog teeth, bicycle size and serial number. The riding data can include one or more of wheel speed, pedal cadence, expected bicycle speed, bicycle position and continuously variable transmission ratio. The steps of monitoring, recording, identifying, comparing and establishing a second configuration setting can be repeated until the error value is within a specified tolerance. The controller can repeat the steps of monitoring, recording, identifying, comparing and establishing a second configuration setting periodically to monitor the configuration setting and ensure it remains within the specified tolerance. The period of time between monitoring the configuration setting can be no more than one month. The period of time between monitoring the configuration setting can be no more than one week. The process to monitor the configuration setting of the controller can occur every time the bicycle remains at a steady state, meaning speed and cadence are within the defined tolerance, for more than 30 seconds.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a schematic diagram of a bicycle configuration system, illustrating variations and steps in a bicycle configuration process according to one embodiment of the present disclosure.



FIG. 2 is a simplified view of a bicycle, illustrating typical mounting locations for various features according to one embodiment of the present disclosure.



FIG. 3A is a flow diagram, illustrating variations and steps in a CVT control process according to one embodiment of the present disclosure.



FIG. 3B is a schematic diagram, illustrating steps and variations in a CVT control scheme according to one embodiment of the present disclosure.



FIG. 4 is a diagram, illustrating a method for enabling a user to capture information without manually entering each piece of information according to one embodiment of the present disclosure.



FIG. 5A is a diagram, illustrating transmission ratio over time according to one embodiment of the present disclosure.



FIG. 5B is a diagram of transmission ratio relative to time, illustrating a control scheme using open loop and closed loop control schemes under different conditions according to one embodiment of the present disclosure.





DETAILED DESCRIPTION

As defined herein, the term configuration refers to any process for ensuring a controller “knows” the system in which it is operating. Configuration may involve any process in which a controller is communicatively coupled to components and is able to communicate using a communication protocol or control scheme according to a control preference available to or preferred by a user. The system may include just the CVT, may include a drive train including the CVT, or may include a bicycle having a CVT or a bicycle having a drive train with a CVT. A drive train may include a chain, belt or other power transmitting element between one or more power sources and one or more power loads.


Steps in a configuration process may be performed at one or more levels in the production or assembly of a bicycle or the delivery of a bicycle to an end user. Although certain preferred embodiments may be described herein, it should be noted that an original equipment manufacturer (OEM) may perform part or all of a configuration process, a dealer or other entity in the sales chain may perform part or all of a configuration process, and an end user may perform part or all of a configuration process.



FIG. 1 is a schematic diagram of a bicycle configuration system, further illustrating variations and steps in a bicycle configuration process. As depicted in FIG. 1, components are manufactured by an OEM 105, a bicycle or kit is assembled by vendor 110, and the bicycle is obtained (either by sale or by rental) or the kit is assembled by end user 115.


At OEM 105, the component may be manufactured according to desired specifications 122. Configuration information from OEM 105 may be stored at configuration server 130 or communicated to user profile server 135, vendor server 125, or device 116. A configuration process may include step 106 of OEM 105 adding a label with configuration information on the label. In addition to information such as part number or serial number, other information may be added. For example, if the component is manufactured to fulfill a customer order, information about the end user 115 may be included, such as a preferred language, units, or the like. Configuration information may be received or otherwise obtained from configuration server 130.


A configuration process may include step 111, in which information is sent from OEM 105 to configuration server 130. Information sent to configuration server 130 may include information including compatibility information relative to other components manufactured by other OEMs 105. Information from other OEMs 105 may include inertia information from a wheel or tire OEM; weight, inertia, center of gravity or other properties of a frame from a frame OEM; wheel dropout angle, depth or other metrics information from a frame OEM, and the like.


Components (e.g., frames, wheels, rims, gears, electric motors, transmissions, etc.) from various OEMs 105 may be obtained by vendor or other entity 110 during the production of a bicycle. A configuration process may include step 107, in which a label may be read to get information. Machine-readable optical labels may be used to communicate configuration information. A QR code™ is one example of a matrix barcode that contains information about the item to which it is attached. A vendor or other entity 110 in the supply chain may use an imaging device to scan the optical label and determine or verify the country of manufacture (country of origin) for a component, assembly or bicycle. Information stored in either a central computer or a computer controlled by the entity may be used to configure the bicycle. For example, if a bicycle dealer in Germany scans an optical label, information about the bicycle may be presented in German and any units may be metric, whereas if a bicycle dealer in the United States were to scan the same optical label, information about the bicycle may be presented in English and any units may be standard, whereas if a bicycle dealer in England were to scan the same optical label, information may be presented in English and any units may be imperial.


A configuration process may include step 112, in which setup information is retrieved by entity 110 from configuration server 130. In some embodiments, entity 110 may have an imaging device to scan an optical label, a radio-frequency identification (RFID) reader to identify a tag, or some other technology to determine information about a component, subassembly, assembly or bicycle. For example, in some embodiments, a QR code or other optical label may include serial number information, part number information, country of origin (manufacture), vendor information, dealer information, user information, or the like. With this information, configuration of a bicycle may be performed by entity 110.


In some embodiments, a bicycle may utilize a system controller and a CVT controller. Configuration information may be analyzed by vendor server 125 to determine which CVT controller is a best match for the system controller. Or, if there is a particular CVT controller running a certain version of firmware, configuration server 130 may provide information about what system controller should be used or is preferred, a preferred setup sequence, or the like. In some embodiments, configuration server 130 may contain instructions for configuration that can be loaded onto a system controller or a CVT controller independent of the other, such that an end user can trigger or request a final connection between the two controllers and the controllers immediately communicate with each other.


In some embodiments, configuration information read from a label is analyzed to select what configuration information is retrieved from configuration server 130. For example, entity 110 may have information about a preferred system controller configurable to communicate with any of several different CVT controllers available, with each CVT controller using a different communication protocol (including different versions of the same protocol). If a label is scanned and it is determined that a particular CVT controller is to be used with the preferred system controller, embodiments may retrieve the appropriate software from configuration server 130.


A configuration process may include step 113, in which information may be obtained by end user 115 from vendor server 125. Information stored on vendor server 125 may include information about an end user for whom the bicycle is intended, a jurisdiction or geographic area in which the bicycle is to be used, or the like. In some embodiments, information about a geographic area in which the bicycle is to be used includes instructions that the system controller or CVT controller will execute to operate according to particular laws or regulations. For example, if a particular municipality has a maximum bicycle speed, execution of the instructions may control the CVT in a way that optimizes the CVT at speeds less than the maximum speed. In some embodiments, vender server 125 may communicate with OEM 105, device 116, user profile server 135, or configuration server 130 to obtain configuration information, reconcile information or settings, and communicate configuration information to a CVT controller or a system controller.


A configuration process may include step 114, in which information may be obtained from user profile server 135. End user 115 may have set up a profile that is stored in user profile server 135. If end user 115 purchases a new bicycle or rents a bicycle having a system controller or a CVT controller, fields in the user profile may be analyzed to control operation of the CVT according to user preferences. For example, end user 115 may prefer smoother acceleration instead of quick acceleration, or may want more motor assistance on a rental bike than on a bike owned by end user 115. In any case, a user profile stored on user profile server 135 may store this information in various fields and provide the information to a vendor 110 either at a time of purchase (or rental) or some other point of time. End user 115 may navigate through a series of steps to capture information, may be presented a limited number of options, or may use other means to capture information, discussed below.


In addition to the above information, a configuration process may include determining or obtaining other information about the system being configured. FIG. 2 depicts a simplified view of a bicycle, illustrating typical mounting locations for wheel speed sensor 201, chain speed sensor 202, bicycle speed sensor 203, system controller 204, pedal speed sensor 205, CVT controller 206 and torque sensor 207 on bicycle 200. However, different vendors may use different sensors mounted in different locations on the bicycle. Pedal speed sensors are one example of a sensor that may vary according to the vendor with respect to location, orientation, signal parameters such as frequency, etc. Also, CVT controller 206 may be positioned at the rear wheel axle or at the bottom bracket. Embodiments may determine what sensors are available, where the sensors are positioned and other information, and configure the bicycle accordingly.


Various bicycles and control systems may need to know different information in order to automatically configure for a particular component, subassembly, assembly, drive train, bicycle, environment, rider, manufacturer or intermediary. Not all information is required for each scenario. FIG. 3A depicts a flow diagram, illustrating variations and steps in a CVT control process.


Example 1: As shown in FIG. 3A, a CVT control method 300 may include step 302 of getting a target cadence (e.g., from system controller 204) and step 306 of adjusting the transmission ratio using system controller 204 or CVT controller 206 (see FIG. 3B).


Example 2: As shown in FIG. 3A, a CVT control process 300 may include step 302 of getting a target cadence (e.g., from system controller 204), step 304 of calculating user power and step 306 of adjusting the transmission ratio using system controller 204 or CVT controller 206.


Example 3: As shown in FIG. 3A, a CVT control process 300 may include step 301 of getting a target bike speed (e.g., from bicycle speed sensor 203), step 302 of getting a target cadence (e.g., from system controller 204), step 304 of calculating user power and step 306 of adjusting the transmission ratio using system controller 204 or CVT controller 206.


Example 4: As shown in FIG. 3A, a CVT control process 300 may include step 301 of getting a target bike speed (e.g., from bicycle speed sensor 203), step 302 of getting a target cadence (e.g., from system controller 204), step 304 of calculating user power, step 305 of getting external power input (e.g., from system controller 204 or from sensors associated with the external power source) and step 306 of adjusting the transmission ratio using system controller 204 or CVT controller 206.


Example 5: As shown in FIG. 3A, a CVT control process 300 may include step 301 of getting a target bike speed (e.g., from bicycle speed sensor 203), step 302 of getting a target cadence (e.g., from system controller 204), step 304 of calculating user power, step 305 of getting external power input (e.g., from system controller 204 or from sensors associated with the external power source), step 308 of determining external power limits (e.g., battery capability, maximum power capacity, available power capacity, power capacity allowed by rules or environment) and step 306 of adjusting the transmission ratio using system controller 204 or CVT controller 206.


Example 6: As shown in FIG. 3A, a CVT control process 300 may include step 301 of getting a target bike speed (e.g., from bicycle speed sensor 203), step 302 of getting a target cadence (e.g., from system controller 204), step 304 of calculating user power, step 305 of getting external power input (e.g., from system controller 204 or from sensors associated with the external power source), step 308 of determining external power limits (e.g., battery capability, maximum power capacity, available power capacity, power capacity allowed by rules or environment), step 309 of adjusting the external power and step 306 of adjusting the transmission ratio using system controller 204 or CVT controller 206.



FIG. 3B depicts a schematic diagram, illustrating steps and variations in a CVT control scheme.


Example 1: As shown in FIG. 3B, a CVT control process 350 may include step 302 of getting a target cadence (e.g., from system controller 204), step 307 of determining an actual cadence (e.g., from pedal speed sensor 205), step 310A of determining a transmission ratio, step 312A of determining a target transmission ratio, and step 314A of adjusting the transmission ratio. Steps 310A, 312A and 314A may be performed by CVT controller 206 or system controller 204 in communication with CVT controller 206.


Example 2: As shown in FIG. 3B, a CVT control process 350 may include step 302 of getting a target cadence (e.g., from system controller 204), step 307 of determining an actual cadence (e.g., from pedal speed sensor 205), step 310B of determining a encoder position, step 312B of determining a target encoder position, and step 314B of adjusting the encoder position. Steps 310B, 312B and 314B may be performed by CVT controller 206 or system controller 204 in communication with CVT controller 206.


Example 3: As shown in FIG. 3B, a CVT control process 350 may include step 302 of getting a target cadence (e.g., from system controller 204), step 307 of determining an actual cadence (e.g., from pedal speed sensor 205), steps 305A of determining a motor output torque and step 305B of determining a motor output speed, step 310A of determining a transmission ratio, step 312A of determining a target transmission ratio, and step 314A of adjusting the transmission ratio. Steps 310A, 312A and 314A may be performed by CVT controller 206 or system controller 204 in communication with CVT controller 206.


Example 4: As shown in FIG. 3B, a CVT control process 350 may include step 302 of getting a target cadence (e.g., from system controller 204), step 307 of determining an actual cadence (e.g., from pedal speed sensor 205), steps 305A of determining a motor output torque and step 305B of determining a motor output speed, step 310B of determining a encoder position, step 312B of determining a target encoder position, and step 314B of adjusting the encoder position. Steps 310B, 312B and 314B may be performed by CVT controller 206 or system controller 204 in communication with CVT controller 206.


In addition to these examples and other variations, a manufacturer may want systems in a preferred warranty configuration, a user might want several different bikes to be configured such that they all have approximately the same feel, local laws and regulations may also dictate how a bicycle can be configured (particularly if the bicycle is an e-bike or otherwise has external (non-human) power applied in lieu of or in addition to user pedal input), etc.


A configuration system determines what information is going to be used to control a CVT. Furthermore, a configuration system may also establish what controller, software or combination will be managing the control of the CVT.


In some embodiments, configuration instructions may establish that a CVT controller may receive only specific instructions for changing a tilt angle for the CVT, and a system controller communicatively coupled to the CVT controller will receive, determine or otherwise obtain information and forward information to the CVT controller necessary to adjust the CVT. For example, in a simplest scenario, a system controller may obtain pedal speed (“cadence”) information indicating the number of revolutions per minute (RPM) of the pedals. If the cadence is higher than a predetermined cadence, the system controller sends information to the CVT controller indicating a desired CVT setting (e.g., set transmission ratio to 1:1) or a desired change in a CVT setting (e.g., increase tilt angle by 2 degrees).


In other embodiments, configuration instructions may establish that the system controller may perform a portion of the calculations and sending a signal to the CVT controller, with the CVT controller calculating, referencing table lookups, or otherwise determining only the signals or processes needed to adjust the CVT based on the signal received from the system controller. The CVT controller adjusts the transmission ratio for the CVT based on the signal received from the system controller. For example, the system controller may determine the present pedal speed and signal that information to the CVT controller, along with a direction to adjust the CVT transmission ratio to achieve a desired pedal speed or to increase/decrease the pedal speed by a certain number of RPMs. Upon receiving the information, the CVT controller calculates, references a table lookup, or otherwise determines what tilt angle or encoder position is needed to achieve the desired pedal speed, and adjusts the CVT accordingly.


In other embodiments, information is provided by the system controller to the CVT controller, and the CVT controller determines how to achieve a desired transmission ratio, a desired change in transmission ratio, an output speed, a desired change in output speed, or the like. The system controller may determine the present wheel speed and a desired wheel speed and signal the information to the CVT controller, which calculates, uses lookup tables, or otherwise determines a necessary tilt angle and adjusts the CVT accordingly. For example, a system controller may determine bicycle speed and pass the information to the CVT controller. The CVT controller may have stored in memory the number of teeth on a front gear, the number of teeth on a rear gear, and a circumference of a rear wheel. Then, if a user wants to pedal at a selected pedal RPM (including a pedal RPM range), the CVT controller may determine the pedal RPM based on the bicycle speed (received from the system controller) and the gear ratio between the front gear and the rear gear (stored in local memory), and can then adjust the CVT transmission ratio accordingly. Those of skill in the art will appreciate that the CVT controller might know the number of teeth on the front gear and the number of teeth on the rear gear, or might know the ratio between the front gear and the rear gear.


The number, type, or position of sensors may differ among bicycle frames and components. Furthermore, in some embodiments, one or more sensors may communicate directly with the CVT controller. The CVT controller may communicate with the system controller and also may receive signals associated with pedal speed (RPM), pedal torque, chain speed, or the like, directly from the sensor(s). For example, in systems having multiple gears, the CVT controller may receive a signal indicating chain position (indicating in which gear the chain is engaged). In these scenarios, a system controller may receive chain position information and send the CVT controller the information necessary to adjust the CVT. The system controller may receive information on chain position and either send the information directly to the CVT controller or determine a gear ratio (corresponding to the ratio of the front gear to the rear gear) and send the gear ratio to the CVT controller. In some embodiments, a sensor may be integrated into the CVT controller, including integration in a wiring harness. In other embodiments, the CVT controller may receive chain position information either directly from the sensors or from the system controller and determine the gear ratio. The CVT controller may then determine an appropriate transmission ratio based on the gear ratio.


The foregoing describes various systems implementing system controllers and CVT controllers. A process for establishing these control schemes may be set up by a user in various ways, discussed below.


A process for configuring a bicycle control system by an OEM may involve communicatively coupling a CVT controller, a system controller, or both to an OEM server or other computer. If the OEM is producing a finished bicycle, the OEM server or computer may provide additional information to the CVT controller or the system controller. Information provided to the CVT controller may include gear ratio, the number of teeth on a front gear, the number of teeth on a rear gear, the number of front gears, the number of rear gears, a chain length, or the like. Information provided to a system controller or CVT controller may also include control information, including closed loop control parameters, open loop control parameters, parameters for switching between closed loop and open loop control, calibration parameters including triggers for initiating calibration, calibration steps, and triggers for ceasing calibration. In some embodiments, triggers may include operating conditions. Operating conditions may include information such as pedal RPM, pedal torque, the presence of a load, etc. As an example, a controller may detect or receive signals indicating a user is applying a large torque or there is a high pedal speed but slow vehicle movement. The controller may determine that this is a high (or heavy) load. The CVT may then determine that the CVT should be operating in a closed loop. If the pedal speed or torque decreases or the vehicle speed increases, the controller may determine the bicycle is operating with a lighter load and may switch to an open loop process.


In some embodiments, once the system controller or CVT controller is powered up by the user, execution of a set of instructions enables the system controller or CVT controller to begin operation in either closed loop or open loop control, according to one or more parameters. The system controller or CVT controller may communicate with an OEM server or other computer to set up or configure a controller area network (CAN), including initializing communications between sensors and the CVT controller or system controller and ensuring communication compatibility between the system controller and the CVT controller. Ensuring communication compatibility between the system controller and the CVT controller may include establishing a rate of communication between the CVT controller and the system controller, whether communications are to be push type (automatically provided) communications or whether they should be prompted. For example, if the system controller performs all calculations and directs the CVT controller to adjust the tilt angle to reach a desired tilt angle, the CVT controller may automatically provide the system controller with information about the tilt angle in response to a command to change the tilt angle.


Initial setup may be completed by the OEM through an implemented bike identification (ID) on a drive system electronic control unit (ECU). In step 122, OEM 105 may receive configuration information in the form of specifications and feedback from configuration server 130, or may receive configuration information from vendor server 125 in step 109. Either at vendor 110 or end user 115, a controller unit then provides a handshake and configures the system according to according to one or more predefined settings provided by OEM 105 and stored in a bike ID library on configuration server 130.


In one embodiment, an auto-configuration system may include a controller area network (CAN) with a system controller communicatively coupled to sensors and a CVT controller. At start up, the system controller sends a mutually pre-defined packet over the CAN bus to the CVT controller which stores information about components. The number of teeth on a front gear (Tf), the number of teeth on a rear gear (Tr), and the rear wheel circumference (Cw) may be included in the information. The CVT controller initializes a variable for each Tf, Tr and Cw from non-volatile memory, then when the CVT controller receives the mutually defined pack from the system controller, it updates the variables in volatile memory.


In one embodiment, an auto-configuration system may include a controller coupled to a plurality of sensors and further communicatively coupled to a GPS or other distance sensor. The sensors may include a CAN, a Wp (Pedal Speed Sensor), a We (Gear or Cog Speed sensor), a Ww (Wheel Speed Sensor), and a GPS or other distance sensor. At start up, the system controller and the CVT controller load default parameters. A set of steps or subroutines are then performed by a set of computer instructions stored in memory and executable by the controller.


Calculation of a wheel circumference may be performed as follows. The system controller transmits a mutually pre-defined packet to a CVT controller with the variable DISTANCE set to zero and clears a distance counter. When the CVT controller receives the packet with the variable DISTANCE set to zero, it clears a counter for Output Speed Ring (OSR) counts (e.g. 6 pulses per rev (ppr), OSR_ppr) and begins accumulating OSR counts until the system controller sends the mutually pre-defined packet to the CVT with the variable DISTANCE set to a non-zero value. On receiving a non-zero value the CVT will compute the wheel circumference (Cw) then store the value in a variable in non-volatile memory.


Once the distance is known (such as by riding a known distance, using GPS or some other means), the wheel circumference may be calculated as:

Cw=DISTANCE/(OSR_pulses/OSR_ppr)  (Equation 1)

whereby the wheel circumference is calculated based on output speed ring (OSR) pulses divided by OSR Pulses per revolution. This calculation and method can be repeated for a short duration to get a quick estimate shortly after power up, then a longer distance can be used to refine the value.


In some scenarios, a CVT controller may function knowing only the ratio of Tf:Tr. This ratio can be discovered by the system controller, which then transmits a mutually pre-defined packet to the CVT controller with the variable PEDAL_REVOLUTIONS to zero and clears a variable PEDAL_REV counter. When a controller receives the packet with the variable PEDAL_REVOLUTIONS set to zero, it clears a counter for the variable INPUT_SPEED_RING_COUNTS (e.g. 12 pulses per rev, ISR_ppr) and begins accumulating input speed ring (ISR) counts until the system controller sends the mutually pre-defined packet to the controller with the variable PEDAL_REVOLUTIONS set to a non-zero value. Upon receiving a non-zero value, the controller will compute the ratio Tf:Tr, then store the value in a variable in non-volatile memory. The equation:

Tf:Tr ratio=PEDAL_REVOLUTIONS/(ISR_pulses/ISR_ppr)  (Equation 2)

may be used to determine the ratio of Tf to Tr.


In some embodiments, on initial startup, a user enters the make and model of the bicycle. The controller may compare the information about make and model to a database and determine a default configuration based on the determination. In some embodiments, the determination involves identifying a preferred configuration for that specific bicycle. In other embodiments, determination of a default configuration involves determining a make and model similar to the make and model entered by the user.


In one embodiment, a drive system manufacturer integrates a bootloader function into their system.


In some bicycles, there may be an external power source such as an electric motor or a small engine, or some other variation which increases the amount of information needed. Embodiments may obtain or determine information about the state of operation of electric components. In a configuration process, information about the operating parameters of the external power source may be stored in a configuration server, an OEM server, or a vendor server. During the bicycle production process or a control configuration process, part or all of this information may be installed on a system controller or a CVT controller. The system controller or CVT controller may receive information regarding a preferred power range and configure a plurality of operating modes, taking into account the preferred power range. During operation of the bicycle in any of the operating modes, the CVT controller or the system controller can monitor the individual components, the interaction between two components, or the bicycle as a whole and provide feedback to OEM 105 or entity 110 for future bicycle production.


For some users, bicycles or environments, entering the make and model for a bicycle will be easy. However, if the user is not familiar with what to look for or where to look for information, this task can be more daunting. For example, if a user is unfamiliar with bicycles or bicycle components, they may be unsure of the exact make and model. Compounding this is issues with language and branding across different regions. For example, a bicycle may be referred to by a first name in a first country and a second name in a second country. If a user in the second country doesn't recognize that the two bicycles are actually the same bicycle but with different names, the user might enter the wrong make and model, might need to perform iterations to determine the correct make and model, or might become frustrated and not purchase the bicycle.


In some embodiments, end user 115 is presented a limited number of options for configuring a bicycle. For example, instead of asking end user 115 to enter the number of teeth, embodiments may prompt the user to determine if the front gear has 54, 58 or 60 teeth. A method for configuring a bicycle may include a configuration storing possible values for CVT controllers, system controllers, and other components. For example, a front gear on a mountain bike typically has fewer teeth (and is smaller) than a front gear on a road bike. Thus, a controller on a mountain bike might provide end user front gear teeth options that are below a predetermined number (e.g., less than 48) while the same controller mounted on a road bike might provide end user 115 front gear teeth options that are above a predetermined number (e.g., greater than 49). In this manner, embodiments assist end user 115 in configuring the bicycle in a way that reduces the possibility for errors while still allowing end user 115 to participate in the configuration process. Other examples of bicycles include commercial bicycles which may have a large storage container to allow a user to transport cargo, passengers or other heavy items (and may actually have three or more wheels), recumbent bicycles, and other variations.


In other embodiments, a system controller or CVT controller may be communicatively coupled to a device capable of scanning an optical label. For example, in some embodiments, an application running on an imaging device or a smart phone or other user device may be used to read the optical label and provide the necessary information to the CVT controller, the system controller or both.


In some embodiments, end user 115 may use existing technology in the form of a camera feature commonly found on smartphones and other devices to capture information about the physical configuration of a bicycle and use that information to operationally configure the bicycle. FIG. 4 depicts a diagram, illustrating a method for enabling a user to capture information without manually entering each piece of information.


In step 401, a user opens an application on a user device, such as but not limited to a smart phone, a personal data assistant, a tablet, or any other appropriate electronic device. The application may be stored on the smartphone or may be an agent operating on the smartphone that communicates with an application running on a server that is configured to perform some or all of the processing.


In step 402, the application prompts the user to take pictures of the bicycle physical configuration. The application may determine which component(s) is (are) being captured in an image or may separate the process into steps 402a-402d.


In step 402a, the application prompts the user to take a picture of the rear gear. The application may provide information such as a picture or graphic of where the rear gear is located, what angle the camera should be relative to the rear gear, or otherwise assist the user in capturing the best image of the rear gear.


In step 402b, the application prompts the user to take a picture of the rear wheel. The application may provide information such as a picture or graphic of where the rear wheel is located, what angle the camera should be relative to the rear wheel, or otherwise assist the user in capturing the best image of the rear wheel.


In step 402c, the application prompts the user to take a picture of the front gear. The application may provide information such as a picture or graphic of where the front gear is located, what angle the camera should be relative to the front gear, or otherwise assist the user in capturing the best image of the front gear.


In step 402d, the application prompts the user to take a picture of the bicycle. The application may provide information such as what angle the camera should be relative to the rear gear, or otherwise assist the user in capturing the best image of the rear gear.


In a further step, the application may prompt the user to take a picture of the front gear and rear gear. The application may provide information (e.g., what angle the camera should be aimed) to assist the user in capturing the best image of the front gear and the rear gear.


In step 403, the information captured by the images is analyzed either by execution of a set of instructions installed on the smart phone, stored in memory on a controller associated with the bicycle or a CVT on the bicycle communicatively coupled to the smart phone, or by a server communicatively coupled to the smart phone. Analysis of the images determines physical parameters of the bicycle. For example, regarding the image of the rear gear or the front gear, a set of instructions may superimpose an overlay correlated with a gear having a selected number of overlay teeth on the image of the gear. If the gear teeth are not detectable due to the overlay teeth covering them or in proximity, the analysis may conclude that the number of gear teeth is the same as the number of overlay teeth. Hence, the number of gear teeth for the front gear or the rear gear can be determined. Similarly, the overlay may be used to determine the gear size or other information. In some embodiments, a set of instructions may be executed to determine two teeth on the gear. Knowing the arc angle between the two teeth and the radius of the gear, the number of teeth may be calculated. In some embodiments, a profile of a tooth may be compared against existing tooth designs to determine a manufacturer of the gear. If the manufacturer of the gear is known, a gear from the manufacturer's catalog may be determined.


In step 404, the configuration information is communicated to a controller (system or CVT) or a user profile server 135. User profile server may remain communicatively coupled to user device 116 to ensure any configuration is accurate and complete.


In a similar way, the size of the rear wheel, the crank arm length, and other bicycle physical configuration information may be determined. In some embodiments, the step of determining bicycle physical configuration information may be performed by executing a set of instructions on a smartphone, by a server communicatively coupled to the smartphone, or some combination.


Information captured by the smartphone may be sent to one or more computing devices. For example, FIG. 1 shows step 132 in which information from the user device 116, such as a smartphone, is used to create user profile 113, step 142 in which information from the smartphone is sent to vendor computer 125, and step 152 in which information from the smartphone is sent to configuration server 130. The information may be used to calibrate a bicycle for end user 115 or may provide feedback to OEM 105 for future bicycle production.


Auto-Calibration


The systems and methods described above may be useful for configuring a bicycle with little or no involvement by the end user. Over time, however, the operating speed, the power source or the power load may cause slip or otherwise bias the CVT into an unwanted state in which slipping and other negative effects may occur. To avoid these problems or provide an improved rider experience, CVTs may be calibrated. Calibration for a CVT typically involves finding the mechanical limits of the shift system and therefore the ratio limits for the continuously variable transmission.


In one embodiment, a user may ride the bicycle and the CVT may be calibrated by adjusting the transmission ratio from full underdrive (FUD) to full over drive (FOD) and back to FUD. The wheel circumference may be calculated, and a range and transmission ratio may be calculated based on values for the top and bottom ratings. In other embodiments, calibration may involve only a portion of the full range. For example, for safety reasons, having a rider pedal in FOD may be undesirable due to health concerns for the rider or the route along which the bicycle would be ridden to perform the calibration. In these cases, calibration may be performed over the bottom half of the range. The calibration may start with the CVT at FUD and ridden until the CVT is determined to be operating at 1:1. For the bottom half of the range, the CVT will be verified against empirical test data. Above 1:1, the bicycle may be calibrated against a theoretical set of data, a range may be extrapolated, or the like. If the rider actually adjusts the bicycle to FOD, embodiments may then perform calibration between FOD and 1:1 or between FOD and FUD to develop empirical data.


In other embodiments, calibration may include correcting for various loads in a CVT. FIG. 5A depicts a diagram, illustrating transmission ratio over time. A CVT may operate at a first ratio 501 for a time 505. A CVT controller may receive an instruction to adjust a transmission ratio or may determine a desired transmission ratio 502. A command may be sent by the CVT controller to an encoder to initiate an adjustment toward the desired transmission ratio. However, a load applied to the transmission may affect the transmission ratio. As illustrated in FIG. 5A, actual transmission ratio 502 may never equal target transmission ratio 504. Embodiments may correct for the load applied in various ways.


A control scheme may include closed loop and open loop algorithms. FIG. 5B depicts a diagram of transmission ratio relative to time, illustrating a control scheme using open loop and closed loop control schemes under different conditions. The CVT may be operating at a first ratio 501 for time 505. A CVT controller may receive an instruction to adjust a transmission ratio or may determine a desired transmission ratio 503. A command may be sent by the CVT controller to an encoder to initiate an adjustment toward the desired transmission ratio according to a closed loop algorithm. Using the closed loop algorithm over time 506, the controller is able to accurately adjust the CVT so the actual transmission rate 503 is equal to desired ratio 504. The CVT controller may then switch to an open loop control scheme for time 407.


A closed loop algorithm may ensure the transmission ratio is adjusted according to a desired rate 506, occurs over a desired time 506, or some other parameter. Operating according to a closed loop algorithm may require more (battery) power to receive sensor information, perform the necessary calculations, and communicate between controllers to adjust the CVT. Accordingly, a closed loop control system may require more sensors, a larger battery, more memory, a faster processor, or the like. Operating according to an open loop control scheme may be less accurate. However, an open loop control scheme will generally require less information (from fewer sensors), and may be more tolerant to variations in bicycle performance (e.g., a person pedaling, then coasting). Some embodiments may utilize both a closed loop and an open loop control scheme. When a command is given to adjust the transmission ratio, the control system may operate according to a closed loop control scheme. Once the CVT reaches the desired a desired transmission ratio, the control scheme may switch back to an open loop control algorithm. The closed loop control scheme may be initiated whenever a load is detected, when cadence is above (or below) a threshold, or the like. In some embodiments, the determination of whether to use a closed loop or an open loop control scheme may occur during manufacturing or configuration. For example, if a system controller is going to be used on a racing bike, a closed loop scheme may be used, whereas the same controller being used on a beach cruiser may operate according to an open loop system. There are advantages to operating according to either closed loop or open loop control schemes. For example, a closed loop control scheme may be more accurate. In some embodiments, when a command is given (either by a system controller or a CVT controller) to adjust a CVT to a desired transmission ratio, the control scheme operates according to a closed loop algorithm.


In some embodiments, calibration may include determining a polynomial or other function representing a transmission performance parameter. For example, a polynomial may be determined for transmission ratio relative to applied loads. A CVT may operate under a control scheme based on a first polynomial. If a controller determines a load on the CVT, the controller may determine a new polynomial. In a simple scenario, determining a load on the CVT may be achieved by determining an input speed and input torque for a rider. In other scenarios, determining a load on a CVT may be achieved by determining an input speed and torque produced by a rider and an input speed and torque produced by a motor or a motor torque and motor current.


Calibration may employ an adaptive algorithm that uses available inputs to discover the shift system mechanical limits during normal operation and with as few interruptions to normal use as possible. On initial startup, the make and model of the bike and a default configuration setting is established and stored in memory. Over the course of a ride, a CVT controller, a system controller constantly stores data for a period of time (e.g., 30 seconds, 1 minute, etc.) for certain inputs. If the rear wheel speed and cadence demanded is constant for more than a certain period of time (say 30 seconds) then the computer continues to record data in that dataset until the rear wheel speed changes by more than a preset amount (say 5 RPM) at that point the computer considers the dataset and calibrates for the beginning of the dataset and the end and adjusts the configuration settings according to any mismatch of the configured output. In some embodiments, the calibration is performed using GPS coordinates, such as adjusting a setting according to a mismatched data of a calculated output from the GPS setting.


In another embodiment, a calibration system may compare information received from one or more sensors and compare the information with predicted values stored in memory. A bicycle may have sensors for pedal torque, pedal speed, chain speed, chain position, wheel speed and bicycle speed. A calibration system may receive and compare values for pedal speed, wheel speed and bicycle speed to determine a predicted pedal torque. If the predicted pedal torque value differs from an actual torque value by a threshold amount, calibration may be initiated. A chain speed sensor, a wheel speed sensor, and the ratio Tf:Tr may be used to determine pedal speed. A chain speed sensor may employ a magnetized chain component or a magnet embedded with a chain, and a sensor capable of detecting the magnet as it passes by each rotation. An advantage to using a chain speed sensor is that the sensor may be positioned anywhere along the chain path, and can be positioned away from the wheel hubs and pedals. Other types of sensors, including optical sensors capable of detecting variations in chain dimensions or optical cues, are possible.


A method of configuring a controller for a continuously variable transmission on a bicycle may include establishing a first configuration setting, monitoring a set of riding data to determine when a steady state speed is maintained for a specified period of time, recording the riding data until the earlier of a second specified period or until the riding data deviates by a predetermined amount from the steady state speed, identifying a control set of data by comparing a first set of GPS data at the beginning of the recorded data to a second set of GPS data at the end of the recorded data, comparing the recorded data against the control set of data to develop an error value, and establishing a second configuration setting for the controller based on the error value. In some embodiments, the method may include requesting and receiving an input of information from a user, and correlating the information received from the user with a set of stored data to establish the first configuration setting. In some embodiments, the information that is provided in the input of information step comprises one or more of the following; bicycle model, tire size, the number of front chain ring teeth, the number of rear cog teeth, bicycle size and serial number. In some embodiments, the riding data can include one or more of wheel speed, pedal cadence, expected bicycle speed, bicycle position and continuously variable transmission ratio. In some embodiments, the steps of monitoring, recording, identifying, comparing and establishing a second configuration setting are repeated until the error value is within a specified tolerance. In some embodiments, the process is repeated to monitor the configuration setting and ensure it remains within the specified tolerance. The process may be repeated periodically or when the bike senses certain conditions, such as a flat (or relatively flat) profile. In some embodiments, the period of time between monitoring the configuration setting is no more than one month. In some embodiments, the period of time between monitoring the configuration setting is no more than one week. In some embodiments, the process to monitor the configuration setting of the controller occurs every time the bicycle remains at a steady state, meaning speed and cadence are within the defined tolerance, for more than 30 seconds.


Calibration may include determining how to calibrate the bicycle. For example, calibration may involve sweeping the entire range of a ball planetary type CVT or may involve sweeping a smaller range.


Calibration may include a bicycle periodically executing a process to determine if calibration is necessary. Execution of a calibration process is performed without user intervention. A controller may use the transmission ratio to calculate an expected user pedal speed, and compare the expected user pedal speed with a user pedal speed associated with the transmission ratio sored in memory. If the calculated user pedal speed differs from the user pedal speed stored in memory by a selected threshold, a calibration process may be initiated. Referring to FIG. 1, in step 155, information about a calibration process may be communicated from a bicycle owned or rented by end user 115 to user profile server 135 or configuration server 130. Configuration server 130 may aggregate information from a set of end users having the same bicycle, CVT, or other component and provide feedback 122 to OEM 105 for incorporation into future manufacturing or configuration processes.

Claims
  • 1. A method for automatically configuring a control system on a bicycle, comprising: receiving, by a control system, a first set of first operating parameters for a ball-planetary continuously variable transmission (CVT), the first set of first operating parameters for the CVT being based on component data associated with components on the bicycle;receiving, by the control system, a second set of second operating parameters for a rider preference, the second set of second operating parameters being received from user inputs and/or from a stored user profile; andconfiguring the CVT and/or an electric motor cooperating with the CVT to operate according to configuration parameters, the configuration parameters being based on the first set of first operating parameters and the second set of second operating parameters, the configuration parameters defining how the CVT and/or electric motor responds to input parameters from bicycle sensors on the bicycle during a ride.
  • 2. The method of claim 1, wherein the first set of first operating parameters is received from a server, a vendor computer or a third-party computing device.
  • 3. The method of claim 1, wherein the second set of second operating parameters is received from a server, a vendor computer or a third-party computing device.
  • 4. The method of claim 1, wherein the second set of second operating parameters for the rider preference includes information about a geographic area or jurisdiction.
  • 5. The method of claim 1, wherein the first set of first operating parameters for the CVT include information selecting an algorithm for operating the CVT.
  • 6. The method of claim 1, wherein the second set of second operating parameters for a rider preference include selections based on user inputs.
  • 7. The method of claim 6, wherein the user inputs includes a target cadence.
  • 8. A system, comprising: a control system configured to receive a first set of first operating parameters for a ball-planetary continuously variable transmission (CVT), the first set of first operating parameters for the CVT being based on component data associated with components on the bicycle, and configured to receive a second set of second operating parameters for a rider preference, the second set of second operating parameters being received from user inputs and/or from a stored user profile; anda configuration server operative to configure a CVT and/or an electric motor cooperating with the CVT to operate according to configuration parameters, the configuration parameters being based on the first set of first operating parameters and the second set of second operating parameters, the configuration parameters defining how the CVT and/or the electric motor responds to input parameters from bicycle sensors on the bicycle during a ride.
  • 9. The system of claim 8, wherein the control system receives the first set of first operating parameters from a server, a vendor computer or a third-party computing device.
  • 10. The system of claim 8, wherein the control system receives the second set of second operating parameters from a server, a vendor computer or a third-party computing device.
  • 11. The system of claim 8, wherein the second set of second operating parameters for the rider preference includes information about a geographic area or jurisdiction.
  • 12. The system of claim 8, wherein the first set of first operating parameters for the CVT include information selecting an algorithm for operating the CVT.
  • 13. The system of claim 8, wherein the second set of second operating parameters for a rider preference include selections based on user inputs.
  • 14. The system of claim 13, wherein the user inputs includes a target cadence.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 17/129,564 filed Dec. 21, 2020, which is a divisional of U.S. patent application Ser. No. 16/034,659, filed Jul. 13, 2018, now U.S. Pat. No. 10,875,603, which is a continuation of U.S. patent application Ser. No. 15/172,031, filed Jun. 2, 2016, now U.S. Pat. No. 10,023,266, which claims priority under 35 U.S.C. § 119(e) to U.S. Provisional Patent Application No. 62/334,947, filed May 11, 2016, and to U.S. Provisional Patent Application No. 62/344,325, filed Jun. 1, 2016. The disclosures of all of the above-referenced prior applications, publications, and patents are considered part of the disclosure of this application, and are incorporated by reference herein in their entirety. Continuously variable transmissions (CVTs) are being used ever more increasingly in systems in which shift shock, gear collisions, and other mechanical events are known to occur. In particular, continuously variable transmissions are gaining popularity for cyclists because they provide a continuous range of transmission ratios, are easy to use, require little or no maintenance, and have increased reliability over geared transmissions. In ball planetary type CVTs, power may be transferred between components via a traction fluid. The use of a traction fluid avoids issues with geared transmissions. In particular, CVTs such as those described in U.S. Pat. Nos. 7,011,600, 7,238,136, 7,198,585, 7,250,018, 7,166,056, 7,235,031, 7,169,076, 7,288,042, 7,396,209, 8,066,614, 7,731,615, 7,651,437, 7,727,108, 7,686,729, 8,267,829, 7,238,137, 7,036,620, 7,238,138, 7,232,395, 7,125,297, 8,469,853, 8,628,443 and 7,322,901 provide smooth acceleration and deceleration by eliminating the undesirable mechanical events associated with geared transmissions. Some CVTs may employ electronic mechanisms for automatically adjusting the transmission ratio. To improve the performance and accuracy of these mechanisms, configuration and calibration may be performed at setup, at selected intervals, when a component is replaced, etc. Presently, configuration information is entered manually, and calibration may be performed on an ad hoc basis, such as when manually initiated by a user of a bicycle. The steps needed to configure a bicycle may seem relatively easy. For example, experienced cyclists are generally aware that the number of teeth on a front gear is usually stamped onto the gear itself. Furthermore, experienced cyclists may know the number of teeth on a gear based on their experience of handling gears, interacting with the gear manufacturer, or by previous trial and error. However, for people not familiar with the different components on a bicycle, this process is prone to errors and frustration. For example, even if the number of teeth is stamped on a gear, a person with little or no experience with bicycles might not know to look for a number stamped on the gear or might not know where to find it. Or, the user might manually count the number of teeth. This can be frustrating, the user might not be physically able to perform the task, and errors can occur. Furthermore, if the person makes a mistake and enters the wrong number, the person might not know there is an error or might not know how to correct the error.

US Referenced Citations (1063)
Number Name Date Kind
225933 Kellogg Mar 1880 A
719595 Huss Feb 1903 A
721663 Brooke Mar 1903 A
1121210 Teckel Dec 1914 A
1175677 Barnes Mar 1916 A
1207985 Null Dec 1916 A
1380006 Nielsen May 1921 A
1390971 Samain Sep 1921 A
1558222 Beetow Oct 1925 A
1629092 Crockett May 1927 A
1629902 Arter May 1927 A
1686446 Gilman Oct 1928 A
1774254 Daukus Aug 1930 A
1793571 Vaughn Feb 1931 A
1847027 Thomsen Feb 1932 A
1850189 Weiss Mar 1932 A
1858696 Weiss May 1932 A
1865102 Hayes Jun 1932 A
1903228 Thomson Mar 1933 A
1947044 Gove Feb 1934 A
1978439 Sharpe Oct 1934 A
2030203 Gove Feb 1936 A
2060884 Madle Nov 1936 A
2086491 Dodge Jul 1937 A
2097631 Madle Nov 1937 A
2100629 Chilton Nov 1937 A
2109845 Madle Mar 1938 A
2112763 Cloudsley Mar 1938 A
2123008 Hayes Jul 1938 A
2131158 Almen Sep 1938 A
2134225 Christiansen Oct 1938 A
2152796 Erban Apr 1939 A
2196064 Erban Apr 1940 A
2209254 Ahnger Jul 1940 A
2259933 Holloway Oct 1941 A
2269434 Brooks Jan 1942 A
2314833 Keese Mar 1943 A
2325502 Auguste Jul 1943 A
RE22761 Wemp May 1946 E
2461258 Brooks Feb 1949 A
2469653 Kopp May 1949 A
2480968 Ronai Sep 1949 A
2553465 Monge May 1951 A
2563370 Reese Aug 1951 A
2586725 Schottler Feb 1952 A
2595367 Picanol May 1952 A
2596538 Dicke May 1952 A
2597849 Alfredeen May 1952 A
2675713 Acker Apr 1954 A
2696888 Chillson Dec 1954 A
2716357 Rennerfelt Aug 1955 A
2730904 Rennerfelt Jan 1956 A
2748614 Weisel Jun 1956 A
2868038 Billeter Jan 1959 A
2873911 Perrine Feb 1959 A
2874592 Oehrli Feb 1959 A
2883883 Chillson Apr 1959 A
2891213 Kern Jun 1959 A
2901924 Banker Sep 1959 A
2913932 Oehrli Nov 1959 A
2931234 Hayward Apr 1960 A
2931235 Hayward Apr 1960 A
2949800 Neuschotz Aug 1960 A
2959063 De Brie Perry Nov 1960 A
2959070 Flinn Nov 1960 A
2959972 Madson Nov 1960 A
2964959 Beck Dec 1960 A
2982154 Zapletal May 1961 A
3008061 Mims Nov 1961 A
3028778 Hayward Apr 1962 A
3035460 Guichard May 1962 A
3048056 Wolfram Aug 1962 A
3051020 Hartupee Aug 1962 A
3081641 Iseman Mar 1963 A
3086704 Hurtt Apr 1963 A
3087348 Kraus Apr 1963 A
3088704 Grady May 1963 A
3154957 Kashihara Nov 1964 A
3163050 Kraus Dec 1964 A
3176542 Monch Apr 1965 A
3184983 Kraus May 1965 A
3204476 Rouverol Sep 1965 A
3207248 Strom Sep 1965 A
3209606 Yamamoto Oct 1965 A
3211364 Wentling Oct 1965 A
3216283 General Nov 1965 A
3229538 Schottler Jan 1966 A
3237468 Schottler Mar 1966 A
3246531 Kashihara Apr 1966 A
3248960 Schottler May 1966 A
3273468 Allen Sep 1966 A
3277745 Harned Oct 1966 A
3280646 Lemieux Oct 1966 A
3283614 Hewko Nov 1966 A
3292443 Perruca Dec 1966 A
3340895 Osgood, Jr. Sep 1967 A
3407687 Hayashi Oct 1968 A
3413896 Wildhaber Dec 1968 A
3430504 Dickenbrock Mar 1969 A
3439563 Petty Apr 1969 A
3440895 Fellows Apr 1969 A
3464281 Azuma Sep 1969 A
3477315 Macks Nov 1969 A
3487726 Burnett Jan 1970 A
3487727 Gustafsson Jan 1970 A
3574289 Shelter Apr 1971 A
3581587 Dickenbrock Jun 1971 A
3588154 Voight Jun 1971 A
3661404 Bossaer May 1972 A
3695120 Titt Oct 1972 A
3707888 Schottler Jan 1973 A
3727473 Bayer Apr 1973 A
3727474 Fullerton Apr 1973 A
3736803 Horowitz Jun 1973 A
3743063 Blechschmidt Jul 1973 A
3745844 Schottler Jul 1973 A
3768715 Tout Oct 1973 A
3769849 Hagen Nov 1973 A
3800607 Zurcher Apr 1974 A
3802284 Sharpe Apr 1974 A
3810398 Kraus May 1974 A
3820416 Kraus Jun 1974 A
3837179 Barth Sep 1974 A
3866985 Whitehurst Feb 1975 A
3891235 Shelly Jun 1975 A
3934493 Hillyer Jan 1976 A
3954282 Hege May 1976 A
3984129 Hege Oct 1976 A
3987681 Keithley Oct 1976 A
3996807 Adams Dec 1976 A
4023442 Woods May 1977 A
4098146 McLarty Jul 1978 A
4103514 Grosse-Entrup Aug 1978 A
4159653 Koivunen Jul 1979 A
4169609 Zampedro Oct 1979 A
4177683 Moses Dec 1979 A
4227712 Dick Oct 1980 A
4314485 Adams Feb 1982 A
4345486 Olesen Aug 1982 A
4369667 Kemper Jan 1983 A
4382186 Denholm May 1983 A
4382188 Cronin May 1983 A
4391156 Tibbals, Jr. Jul 1983 A
4456233 Anton Jun 1984 A
4459873 Black Jul 1984 A
4464952 Stubbs Aug 1984 A
4468984 Castelli Sep 1984 A
4494524 Wagner Jan 1985 A
4496051 Ortner Jan 1985 A
4501172 Kraus Feb 1985 A
4515040 Takeuchi May 1985 A
4526255 Hennessey Jul 1985 A
4546673 Shigematsu Oct 1985 A
4560369 Hattori Dec 1985 A
4567781 Russ Feb 1986 A
4569670 McIntosh Feb 1986 A
4574649 Seol Mar 1986 A
4585429 Marier Apr 1986 A
4592247 Mutschler Jun 1986 A
4617838 Anderson Oct 1986 A
4628766 De Brie Perry Dec 1986 A
4630839 Seol Dec 1986 A
4631469 Tsuboi Dec 1986 A
4643048 Hattori Feb 1987 A
4651082 Kaneyuki Mar 1987 A
4663990 Itoh May 1987 A
4667525 Schottler May 1987 A
4700581 Tibbals, Jr. Oct 1987 A
4706518 Moroto Nov 1987 A
4713976 Wilkes Dec 1987 A
4717368 Yamaguchi Jan 1988 A
4735430 Tomkinson Apr 1988 A
4738164 Kaneyuki Apr 1988 A
4744261 Jacobson May 1988 A
4756211 Fellows Jul 1988 A
4781663 Reswick Nov 1988 A
4828422 Anthony May 1989 A
4838122 Takamiya Jun 1989 A
4838832 Schmitt Jun 1989 A
4856374 Kreuzer Aug 1989 A
4857035 Anderson Aug 1989 A
4869130 Wiecko Sep 1989 A
4881925 Hattori Nov 1989 A
4884473 Lew Dec 1989 A
4900046 Aranceta-Angoitia Feb 1990 A
4909101 Terry, Sr. Mar 1990 A
4918344 Chikamori Apr 1990 A
4961477 Sweeney Oct 1990 A
4964312 Kraus Oct 1990 A
4976170 Hayashi Dec 1990 A
5006093 Itoh Apr 1991 A
5020384 Kraus Jun 1991 A
5025685 Kobayashi Jun 1991 A
5033322 Nakano Jul 1991 A
5033571 Morimoto Jul 1991 A
5037361 Takahashi Aug 1991 A
5044214 Barber, Jr. Sep 1991 A
5059158 Bellio Oct 1991 A
5069655 Schievelbusch Dec 1991 A
5083982 Sato Jan 1992 A
5099710 Nakano Mar 1992 A
5121654 Fasce Jun 1992 A
5125677 Ogilvie Jun 1992 A
5138894 Kraus Aug 1992 A
5156412 Meguerditchian Oct 1992 A
5166879 Greene Nov 1992 A
5194052 Ueda Mar 1993 A
5230258 Nakano Jul 1993 A
5236211 Meguerditchian Aug 1993 A
5236403 Schievelbusch Aug 1993 A
5261858 Browning Nov 1993 A
5267920 Hibi Dec 1993 A
5269726 Swanson Dec 1993 A
5273501 Schievelbusch Dec 1993 A
5318486 Lutz Jun 1994 A
5319486 Vogel Jun 1994 A
5330396 Lohr Jul 1994 A
5355749 Obara Oct 1994 A
5356348 Bellio Oct 1994 A
5375865 Terry, Sr. Dec 1994 A
5379661 Nakano Jan 1995 A
5383000 Michaloski Jan 1995 A
5383677 Thomas Jan 1995 A
5387000 Sato Feb 1995 A
5401221 Fellows Mar 1995 A
5413540 Streib May 1995 A
5451070 Lindsay Sep 1995 A
5476019 Cheever Dec 1995 A
5489003 Ohyama Feb 1996 A
5508574 Vlock Apr 1996 A
5514047 Tibbles May 1996 A
5526261 Kallis Jun 1996 A
5531510 Yamane Jul 1996 A
5562564 Folino Oct 1996 A
5564998 Fellows Oct 1996 A
5577423 Mimura Nov 1996 A
5582489 Marzio Dec 1996 A
5584778 Machida Dec 1996 A
5601301 Liu Feb 1997 A
5607373 Ochiai Mar 1997 A
5645507 Hathaway Jul 1997 A
5651750 Imanishi Jul 1997 A
5664636 Ikuma Sep 1997 A
5669845 Muramoto Sep 1997 A
5669846 Moroto Sep 1997 A
5683322 Meyerle Nov 1997 A
5690346 Keskitalo Nov 1997 A
5701786 Kawakami Dec 1997 A
5720687 Bennett Feb 1998 A
D391824 Larson Mar 1998 S
D391825 Larson Mar 1998 S
5722502 Kubo Mar 1998 A
5746676 Kawase May 1998 A
5755303 Yamamoto May 1998 A
D396396 Larson Jul 1998 S
5799541 Arbeiter Sep 1998 A
5819864 Koike Oct 1998 A
5823052 Nobumoto Oct 1998 A
5823058 Arbeiter Oct 1998 A
5839083 Sugiyama Nov 1998 A
5846155 Taniguchi Dec 1998 A
5857387 Larson Jan 1999 A
5888160 Miyata Mar 1999 A
5895337 Fellows Apr 1999 A
5899827 Nakano May 1999 A
5902207 Sugihara May 1999 A
5964123 Arbeiter Oct 1999 A
5967933 Valdenaire Oct 1999 A
5976054 Yasuoka Nov 1999 A
5984826 Nakano Nov 1999 A
5995895 Watt Nov 1999 A
6000707 Miller Dec 1999 A
6003649 Fischer Dec 1999 A
6004239 Makino Dec 1999 A
6006151 Graf Dec 1999 A
6012538 Sonobe Jan 2000 A
6015359 Kunii Jan 2000 A
6019701 Mori Feb 2000 A
6029990 Busby Feb 2000 A
6042132 Suenaga Mar 2000 A
6045477 Schmidt Apr 2000 A
6045481 Kumagai Apr 2000 A
6047230 Spencer Apr 2000 A
6053833 Masaki Apr 2000 A
6053841 Koide Apr 2000 A
6054844 Frank Apr 2000 A
6056661 Schmidt May 2000 A
6066067 Greenwood May 2000 A
6071210 Kato Jun 2000 A
6074320 Miyata Jun 2000 A
6076846 Clardy Jun 2000 A
6079726 Busby Jun 2000 A
6083139 Deguchi Jul 2000 A
6085140 Choi Jul 2000 A
6085521 Folsom Jul 2000 A
6086506 Petersmann Jul 2000 A
6095940 Ai Aug 2000 A
6095945 Graf Aug 2000 A
6099431 Hoge Aug 2000 A
6101895 Yamane Aug 2000 A
6113513 Itoh Sep 2000 A
6119539 Papanicolaou Sep 2000 A
6119800 McComber Sep 2000 A
6125314 Graf Sep 2000 A
6146297 Kimura Nov 2000 A
6159126 Oshidari Dec 2000 A
6171210 Miyata Jan 2001 B1
6171212 Reuschel Jan 2001 B1
6174260 Tsukada Jan 2001 B1
6182000 Ohta Jan 2001 B1
6186922 Bursal Feb 2001 B1
6188945 Graf Feb 2001 B1
6203238 Otto Mar 2001 B1
6210297 Knight Apr 2001 B1
6217473 Ueda Apr 2001 B1
6217478 Vohmann Apr 2001 B1
6241636 Miller Jun 2001 B1
6243638 Abo Jun 2001 B1
6251038 Ishikawa Jun 2001 B1
6251043 Gierling Jun 2001 B1
6258003 Hirano Jul 2001 B1
6261200 Miyata Jul 2001 B1
6266931 Erickson Jul 2001 B1
6296593 Gotou Oct 2001 B1
6311113 Danz Oct 2001 B1
6312358 Goi Nov 2001 B1
6322475 Miller Nov 2001 B2
6325386 Shoge Dec 2001 B1
6340067 Fujiwara Jan 2002 B1
6356817 Abe Mar 2002 B1
6358174 Folsom Mar 2002 B1
6358178 Wittkopp Mar 2002 B1
6358183 Hughes Mar 2002 B1
6367833 Horiuchi Apr 2002 B1
6371878 Bowen Apr 2002 B1
6375412 Dial Apr 2002 B1
6390945 Young May 2002 B1
6390946 Hibi May 2002 B1
6406399 Ai Jun 2002 B1
6414401 Kuroda Jul 2002 B1
6419608 Miller Jul 2002 B1
6425838 Matsubara Jul 2002 B1
6434960 Rousseau Aug 2002 B1
6440035 Tsukada Aug 2002 B2
6440037 Takagi Aug 2002 B2
6449548 Jain Sep 2002 B1
6459978 Taniguchi Oct 2002 B2
6461268 Milner Oct 2002 B1
6470252 Tashiro Oct 2002 B2
6482094 Kefes Nov 2002 B2
6492785 Kasten Dec 2002 B1
6494805 Ooyama Dec 2002 B2
6499373 Van Cor Dec 2002 B2
6499958 Haugen Dec 2002 B2
6513405 Joachim Feb 2003 B1
6514175 Taniguchi Feb 2003 B2
6520878 Leclair Feb 2003 B1
6522965 Gierling Feb 2003 B1
6527662 Miyata Mar 2003 B2
6532890 Chen Mar 2003 B2
6551210 Miller Apr 2003 B2
6558285 Sieber May 2003 B1
6561941 Nakano May 2003 B2
6571920 Sturmer Jun 2003 B1
6575047 Reik Jun 2003 B2
6582151 Hopson Jun 2003 B2
6588296 Wessel Jul 2003 B2
6658338 Joe Dec 2003 B2
6659901 Sakai Dec 2003 B2
6672418 Makino Jan 2004 B1
6676559 Miller Jan 2004 B2
6679109 Gierling Jan 2004 B2
6681652 Auer Jan 2004 B2
6682432 Shinozuka Jan 2004 B1
6684143 Friedrich Jan 2004 B2
6689012 Miller Feb 2004 B2
6694241 Kim Feb 2004 B2
6718247 Graf Apr 2004 B1
6721637 Abe Apr 2004 B2
6723014 Shinso Apr 2004 B2
6723016 Sumi Apr 2004 B2
6805654 Nishii Oct 2004 B2
6808053 Kirkwood Oct 2004 B2
6839617 Mensler Jan 2005 B2
6849020 Sumi Feb 2005 B2
6859709 Joe Feb 2005 B2
6868949 Braford, Jr. Mar 2005 B2
6909953 Joe Jun 2005 B2
6931316 Joe Aug 2005 B2
6932739 Miyata Aug 2005 B2
6942593 Nishii Sep 2005 B2
6945903 Miller Sep 2005 B2
6949049 Miller Sep 2005 B2
6958029 Inoue Oct 2005 B2
6991575 Inoue Jan 2006 B2
6991579 Kobayashi Jan 2006 B2
6994189 Chen Feb 2006 B2
7000496 Wessel Feb 2006 B2
7004487 Matsumoto Feb 2006 B2
7011600 Miller Mar 2006 B2
7011601 Miller Mar 2006 B2
7011602 Makiyama Mar 2006 B2
7014591 Miller Mar 2006 B2
7029418 Taketsuna Apr 2006 B2
7032914 Miller Apr 2006 B2
7036620 Miller May 2006 B2
7044884 Miller May 2006 B2
7063195 Berhan Jun 2006 B2
7063640 Miller Jun 2006 B2
7074007 Miller Jul 2006 B2
7074154 Miller Jul 2006 B2
7074155 Miller Jul 2006 B2
7077777 Miyata Jul 2006 B2
7086979 Frenken Aug 2006 B2
7086981 Ali Aug 2006 B2
7094171 Inoue Aug 2006 B2
7111860 Grimaldos Sep 2006 B1
7112158 Miller Sep 2006 B2
7112159 Miller Sep 2006 B2
7125297 Miller Oct 2006 B2
7131930 Miller Nov 2006 B2
7140999 Miller Nov 2006 B2
7147586 Miller Dec 2006 B2
7153233 Miller Dec 2006 B2
7156770 Miller Jan 2007 B2
7160220 Shinojima Jan 2007 B2
7160222 Miller Jan 2007 B2
7163485 Miller Jan 2007 B2
7163486 Miller Jan 2007 B2
7163846 Sakai Jan 2007 B2
7166052 Miller Jan 2007 B2
7166056 Miller Jan 2007 B2
7166057 Miller Jan 2007 B2
7166058 Miller Jan 2007 B2
7169076 Miller Jan 2007 B2
7172529 Miller Feb 2007 B2
7175564 Miller Feb 2007 B2
7175565 Miller Feb 2007 B2
7175566 Miller Feb 2007 B2
7192381 Miller Mar 2007 B2
7197915 Luh Apr 2007 B2
7198582 Miller Apr 2007 B2
7198583 Miller Apr 2007 B2
7198584 Miller Apr 2007 B2
7198585 Miller Apr 2007 B2
7201693 Miller Apr 2007 B2
7201694 Miller Apr 2007 B2
7201695 Miller Apr 2007 B2
7204777 Miller Apr 2007 B2
7207918 Shimazu Apr 2007 B2
7214159 Miller May 2007 B2
7217215 Miller May 2007 B2
7217216 Inoue May 2007 B2
7217219 Miller May 2007 B2
7217220 Careau May 2007 B2
7226379 Ibamoto Jun 2007 B2
7232395 Miller Jun 2007 B2
7234873 Kato Jun 2007 B2
7235031 Miller Jun 2007 B2
7238136 Miller Jul 2007 B2
7238137 Miller Jul 2007 B2
7238138 Miller Jul 2007 B2
7238139 Roethler Jul 2007 B2
7246672 Shirai Jul 2007 B2
7250018 Miller Jul 2007 B2
7261663 Miller Aug 2007 B2
7275610 Kuang Oct 2007 B2
7285068 Hosoi Oct 2007 B2
7288042 Miller Oct 2007 B2
7288043 Shioiri Oct 2007 B2
7320660 Miller Jan 2008 B2
7322901 Miller Jan 2008 B2
7343236 Wilson Mar 2008 B2
7347801 Guenter Mar 2008 B2
7383748 Rankin Jun 2008 B2
7383749 Schaefer Jun 2008 B2
7384370 Miller Jun 2008 B2
7393300 Miller Jul 2008 B2
7393302 Miller Jul 2008 B2
7393303 Miller Jul 2008 B2
7395731 Miller Jul 2008 B2
7396209 Miller Jul 2008 B2
7402122 Miller Jul 2008 B2
7410443 Miller Aug 2008 B2
7419451 Miller Sep 2008 B2
7422541 Miller Sep 2008 B2
7422546 Miller Sep 2008 B2
7427253 Miller Sep 2008 B2
7431677 Miller Oct 2008 B2
7452297 Miller Nov 2008 B2
7455611 Miller Nov 2008 B2
7455617 Miller Nov 2008 B2
7462123 Miller Dec 2008 B2
7462127 Miller Dec 2008 B2
7470210 Miller Dec 2008 B2
7478885 Urabe Jan 2009 B2
7481736 Miller Jan 2009 B2
7510499 Miller Mar 2009 B2
7540818 Miller Jun 2009 B2
7547264 Usoro Jun 2009 B2
7574935 Rohs Aug 2009 B2
7591755 Petrzik Sep 2009 B2
7632203 Miller Dec 2009 B2
7651437 Miller Jan 2010 B2
7654928 Miller Feb 2010 B2
7670243 Miller Mar 2010 B2
7686729 Miller Mar 2010 B2
7717815 Tenberge May 2010 B2
7727101 Miller Jun 2010 B2
7727106 Maheu Jun 2010 B2
7727107 Miller Jun 2010 B2
7727108 Miller Jun 2010 B2
7727110 Miller Jun 2010 B2
7727115 Serkh Jun 2010 B2
7731300 Gerstenslager Jun 2010 B2
7731615 Miller Jun 2010 B2
7762919 Smithson Jul 2010 B2
7762920 Smithson Jul 2010 B2
7770674 Miles Aug 2010 B2
7785228 Smithson Aug 2010 B2
7828685 Miller Nov 2010 B2
7837592 Miller Nov 2010 B2
7871353 Nichols Jan 2011 B2
7882762 Armstrong Feb 2011 B2
7883442 Miller Feb 2011 B2
7885747 Miller Feb 2011 B2
7887032 Malone Feb 2011 B2
7909723 Triller Mar 2011 B2
7909727 Smithson Mar 2011 B2
7914029 Miller Mar 2011 B2
7959533 Nichols Jun 2011 B2
7963880 Smithson Jun 2011 B2
7967719 Smithson Jun 2011 B2
7976426 Smithson Jul 2011 B2
8066613 Smithson Nov 2011 B2
8066614 Miller Nov 2011 B2
8070635 Miller Dec 2011 B2
8087482 Miles Jan 2012 B2
8123653 Smithson Feb 2012 B2
8133149 Smithson Mar 2012 B2
8142323 Tsuchiya Mar 2012 B2
8167759 Pohl May 2012 B2
8171636 Smithson May 2012 B2
8197380 Heinzelmann Jun 2012 B2
8230961 Schneidewind Jul 2012 B2
8262536 Nichols Sep 2012 B2
8267829 Miller Sep 2012 B2
8313404 Carter Nov 2012 B2
8313405 Bazyn Nov 2012 B2
8317650 Nichols Nov 2012 B2
8317651 Lohr Nov 2012 B2
8321097 Vasiliotis Nov 2012 B2
8321103 Sakaue Nov 2012 B2
8342999 Miller Jan 2013 B2
8360917 Nichols Jan 2013 B2
8376889 Hoffman Feb 2013 B2
8376903 Pohl Feb 2013 B2
8382631 Hoffman Feb 2013 B2
8382637 Tange Feb 2013 B2
8393989 Pohl Mar 2013 B2
8398518 Nichols Mar 2013 B2
8447480 Usukura May 2013 B2
8469853 Miller Jun 2013 B2
8469856 Thomassy Jun 2013 B2
8480529 Pohl Jul 2013 B2
8496554 Pohl Jul 2013 B2
8506452 Pohl Aug 2013 B2
8512195 Lohr Aug 2013 B2
8517888 Brookins Aug 2013 B1
8535199 Lohr Sep 2013 B2
8550949 Miller Oct 2013 B2
8585528 Carter Nov 2013 B2
8585543 Davis Nov 2013 B1
8608609 Sherrill Dec 2013 B2
8622866 Bazyn Jan 2014 B2
8622871 Hoff Jan 2014 B2
8626409 Vasiliotis Jan 2014 B2
8628443 Miller Jan 2014 B2
8641572 Nichols Feb 2014 B2
8641577 Nichols Feb 2014 B2
8663050 Nichols Mar 2014 B2
8663052 Sich Mar 2014 B2
8678974 Lohr Mar 2014 B2
8682545 Jiang Mar 2014 B2
8688337 Takanami Apr 2014 B2
8708360 Miller Apr 2014 B2
8721485 Lohr May 2014 B2
8738255 Carter May 2014 B2
8776633 Armstrong Jul 2014 B2
8784248 Murakami Jul 2014 B2
8790214 Lohr Jul 2014 B2
8814739 Hamrin Aug 2014 B1
8818661 Keilers Aug 2014 B2
8827856 Younggren Sep 2014 B1
8827864 Durack Sep 2014 B2
8845485 Smithson Sep 2014 B2
8852050 Thomassy Oct 2014 B2
8870711 Pohl Oct 2014 B2
8870712 Steinborn Oct 2014 B2
8888643 Lohr Nov 2014 B2
8900085 Pohl Dec 2014 B2
8920021 Mertenat Dec 2014 B2
8920285 Smithson Dec 2014 B2
8924111 Fuller Dec 2014 B2
8956262 Tomomatsu Feb 2015 B2
8961363 Shiina Feb 2015 B2
8968152 Beaudoin Mar 2015 B2
8992376 Ogawa Mar 2015 B2
8996263 Quinn, Jr. Mar 2015 B2
9017207 Pohl Apr 2015 B2
9022889 Miller May 2015 B2
9046158 Miller Jun 2015 B2
9052000 Cooper Jun 2015 B2
9074674 Nichols Jul 2015 B2
9086145 Pohl Jul 2015 B2
9121464 Nichols Sep 2015 B2
9182018 Bazyn Nov 2015 B2
9239099 Carter Jan 2016 B2
9249880 Vasiliotis Feb 2016 B2
9273760 Pohl Mar 2016 B2
9279482 Nichols Mar 2016 B2
9291251 Lohr Mar 2016 B2
9328807 Carter May 2016 B2
9341246 Miller May 2016 B2
9360089 Lohr Jun 2016 B2
9365203 Keilers Jun 2016 B2
9371894 Carter Jun 2016 B2
9388896 Hibino Jul 2016 B2
9506562 Miller Nov 2016 B2
9528561 Nichols Dec 2016 B2
9541179 Cooper Jan 2017 B2
9574642 Pohl Feb 2017 B2
9574643 Pohl Feb 2017 B2
9611921 Thomassy Apr 2017 B2
9618100 Lohr Apr 2017 B2
9656672 Schieffelin May 2017 B2
9676391 Carter Jun 2017 B2
9677650 Nichols Jun 2017 B2
9683638 Kolstrup Jun 2017 B2
9683640 Lohr Jun 2017 B2
9709138 Miller Jul 2017 B2
9726282 Pohl Aug 2017 B2
9732848 Miller Aug 2017 B2
9739375 Vasiliotis Aug 2017 B2
9833201 Niederberger Dec 2017 B2
9845133 Craven Dec 2017 B2
9850993 Bazyn Dec 2017 B2
9869388 Pohl Jan 2018 B2
9878717 Keilers Jan 2018 B2
9878719 Carter Jan 2018 B2
9903450 Thomassy Feb 2018 B2
9909657 Uchino Mar 2018 B2
9920823 Nichols Mar 2018 B2
9945456 Nichols Apr 2018 B2
9950608 Miller Apr 2018 B2
9963199 Hancock May 2018 B2
9975557 Park May 2018 B2
10023266 Contello Jul 2018 B2
10036453 Smithson Jul 2018 B2
10047861 Thomassy Aug 2018 B2
10056811 Pohl Aug 2018 B2
10066712 Lohr Sep 2018 B2
10066713 Nichols Sep 2018 B2
10088026 Versteyhe Oct 2018 B2
10100927 Quinn, Jr. Oct 2018 B2
10197147 Lohr Feb 2019 B2
10208840 Nichols Feb 2019 B2
10252881 Hiltunen Apr 2019 B2
10253859 Schoolcraft Apr 2019 B2
10253880 Pohl Apr 2019 B2
10253881 Hamrin Apr 2019 B2
10260607 Carter Apr 2019 B2
10323732 Nichols Jun 2019 B2
10400872 Lohr Sep 2019 B2
10428915 Thomassy Oct 2019 B2
10428939 Miller Oct 2019 B2
10458526 Nichols Oct 2019 B2
10634224 Lohr Apr 2020 B2
10703372 Carter Jul 2020 B2
10704657 Thomassy Jul 2020 B2
10704687 Vasiliotis Jul 2020 B2
10711869 Miller Jul 2020 B2
10800421 Cho Oct 2020 B2
10920882 Thomassy Feb 2021 B2
10975916 Okada Apr 2021 B2
11174922 Nichols Nov 2021 B2
11530739 Nichols Dec 2022 B2
11624432 Schoolcraft Apr 2023 B2
20010008192 Morisawa Jul 2001 A1
20010023217 Miyagawa Sep 2001 A1
20010041644 Yasuoka Nov 2001 A1
20010044358 Taniguchi Nov 2001 A1
20010044361 Taniguchi Nov 2001 A1
20010046920 Sugihara Nov 2001 A1
20020017819 Chen Feb 2002 A1
20020019285 Henzler Feb 2002 A1
20020025875 Tsujioka Feb 2002 A1
20020028722 Sakai Mar 2002 A1
20020037786 Hirano Mar 2002 A1
20020045511 Geiberger Apr 2002 A1
20020049113 Watanabe Apr 2002 A1
20020117860 Man Aug 2002 A1
20020128107 Wakayama Sep 2002 A1
20020151401 Lemanski Oct 2002 A1
20020161503 Joe Oct 2002 A1
20020169051 Oshidari Nov 2002 A1
20020179348 Tamai Dec 2002 A1
20020189524 Chen Dec 2002 A1
20030015358 Abe Jan 2003 A1
20030015874 Abe Jan 2003 A1
20030022753 Mizuno Jan 2003 A1
20030027683 Grillenberger Feb 2003 A1
20030036456 Skrabs Feb 2003 A1
20030096674 Uno May 2003 A1
20030132051 Nishii Jul 2003 A1
20030135316 Kawamura Jul 2003 A1
20030144105 O'Hora Jul 2003 A1
20030151300 Goss Aug 2003 A1
20030160420 Fukuda Aug 2003 A1
20030181286 Miller Sep 2003 A1
20030216216 Inoue Nov 2003 A1
20030221892 Matsumoto Dec 2003 A1
20040038772 McIndoe Feb 2004 A1
20040051375 Uno Mar 2004 A1
20040058772 Inoue Mar 2004 A1
20040067816 Taketsuna Apr 2004 A1
20040082421 Wafzig Apr 2004 A1
20040087412 Mori May 2004 A1
20040092359 Imanishi May 2004 A1
20040119345 Takano Jun 2004 A1
20040171452 Miller Sep 2004 A1
20040171457 Fuller Sep 2004 A1
20040204283 Inoue Oct 2004 A1
20040224808 Miller Nov 2004 A1
20040231331 Iwanami Nov 2004 A1
20040254047 Frank Dec 2004 A1
20050037876 Unno Feb 2005 A1
20050037886 Lemanski Feb 2005 A1
20050064986 Ginglas Mar 2005 A1
20050073127 Miller Apr 2005 A1
20050079948 Miller Apr 2005 A1
20050085326 Miller Apr 2005 A1
20050085327 Miller Apr 2005 A1
20050085334 Miller Apr 2005 A1
20050085336 Miller Apr 2005 A1
20050085337 Miller Apr 2005 A1
20050085338 Miller Apr 2005 A1
20050085979 Carlson Apr 2005 A1
20050096176 Miller May 2005 A1
20050096179 Miller May 2005 A1
20050113202 Miller May 2005 A1
20050113210 Miller May 2005 A1
20050117983 Miller Jun 2005 A1
20050119086 Miller Jun 2005 A1
20050119087 Miller Jun 2005 A1
20050119090 Miller Jun 2005 A1
20050119093 Miller Jun 2005 A1
20050124453 Miller Jun 2005 A1
20050124456 Miller Jun 2005 A1
20050130784 Miller Jun 2005 A1
20050137046 Miller Jun 2005 A1
20050137051 Miller Jun 2005 A1
20050137052 Miller Jun 2005 A1
20050148422 Miller Jul 2005 A1
20050148423 Miller Jul 2005 A1
20050153808 Miller Jul 2005 A1
20050153809 Miller Jul 2005 A1
20050153810 Miller Jul 2005 A1
20050159265 Miller Jul 2005 A1
20050159266 Miller Jul 2005 A1
20050159267 Miller Jul 2005 A1
20050164819 Miller Jul 2005 A1
20050170927 Miller Aug 2005 A1
20050176544 Miller Aug 2005 A1
20050176545 Miller Aug 2005 A1
20050178893 Miller Aug 2005 A1
20050181905 Ali Aug 2005 A1
20050184580 Kuan Aug 2005 A1
20050197231 Miller Sep 2005 A1
20050209041 Miller Sep 2005 A1
20050227809 Bitzer Oct 2005 A1
20050229731 Parks Oct 2005 A1
20050233846 Green Oct 2005 A1
20050255957 Miller Nov 2005 A1
20060000684 Agner Jan 2006 A1
20060006008 Brunemann Jan 2006 A1
20060052204 Eckert Mar 2006 A1
20060054422 Dimsey Mar 2006 A1
20060084549 Smithson Apr 2006 A1
20060108956 Clark May 2006 A1
20060111212 Ai May 2006 A9
20060154775 Ali Jul 2006 A1
20060172829 Ishio Aug 2006 A1
20060180363 Uchisasai Aug 2006 A1
20060223667 Nakazeki Oct 2006 A1
20060234822 Morscheck Oct 2006 A1
20060234826 Moehlmann Oct 2006 A1
20060276299 Imanishi Dec 2006 A1
20070004552 Matsudaira Jan 2007 A1
20070004554 Hans Jan 2007 A1
20070004556 Rohs Jan 2007 A1
20070041823 Miller Feb 2007 A1
20070049450 Miller Mar 2007 A1
20070082770 Nihei Apr 2007 A1
20070099753 Matsui May 2007 A1
20070142161 Miller Jun 2007 A1
20070149342 Guenter Jun 2007 A1
20070155552 De Cloe Jul 2007 A1
20070155567 Miller Jul 2007 A1
20070155580 Nichols Jul 2007 A1
20070167274 Petrzik Jul 2007 A1
20070167275 Miller Jul 2007 A1
20070167276 Miller Jul 2007 A1
20070167277 Miller Jul 2007 A1
20070167278 Miller Jul 2007 A1
20070167279 Miller Jul 2007 A1
20070167280 Miller Jul 2007 A1
20070179013 Miller Aug 2007 A1
20070193391 Armstrong Aug 2007 A1
20070197337 Miller Aug 2007 A1
20070219048 Yamaguchi Sep 2007 A1
20070219696 Miller Sep 2007 A1
20070228687 Parker Oct 2007 A1
20070232423 Katou Oct 2007 A1
20070245846 Armstrong Oct 2007 A1
20070270265 Miller Nov 2007 A1
20070270266 Miller Nov 2007 A1
20070270267 Miller Nov 2007 A1
20070270268 Miller Nov 2007 A1
20070270269 Miller Nov 2007 A1
20070270270 Miller Nov 2007 A1
20070270271 Miller Nov 2007 A1
20070270272 Miller Nov 2007 A1
20070270278 Miller Nov 2007 A1
20070275809 Miller Nov 2007 A1
20070281819 Miller Dec 2007 A1
20070287578 Miller Dec 2007 A1
20070287579 Miller Dec 2007 A1
20070287580 Miller Dec 2007 A1
20080004008 Nicol Jan 2008 A1
20080009389 Jacobs Jan 2008 A1
20080032852 Smithson Feb 2008 A1
20080032853 Smithson Feb 2008 A1
20080032854 Smithson Feb 2008 A1
20080034585 Smithson Feb 2008 A1
20080034586 Smithson Feb 2008 A1
20080039269 Smithson Feb 2008 A1
20080039270 Smithson Feb 2008 A1
20080039271 Smithson Feb 2008 A1
20080039272 Smithson Feb 2008 A1
20080039273 Smithson Feb 2008 A1
20080039274 Smithson Feb 2008 A1
20080039275 Smithson Feb 2008 A1
20080039276 Smithson Feb 2008 A1
20080039277 Smithson Feb 2008 A1
20080040008 Smithson Feb 2008 A1
20080070729 Miller Mar 2008 A1
20080071436 Dube Mar 2008 A1
20080073136 Miller Mar 2008 A1
20080073137 Miller Mar 2008 A1
20080073467 Miller Mar 2008 A1
20080079236 Miller Apr 2008 A1
20080081715 Miller Apr 2008 A1
20080081728 Faulring Apr 2008 A1
20080085795 Miller Apr 2008 A1
20080085796 Miller Apr 2008 A1
20080085797 Miller Apr 2008 A1
20080085798 Miller Apr 2008 A1
20080121486 Miller May 2008 A1
20080121487 Miller May 2008 A1
20080125281 Miller May 2008 A1
20080125282 Miller May 2008 A1
20080132373 Miller Jun 2008 A1
20080132377 Miller Jun 2008 A1
20080139363 Williams Jun 2008 A1
20080141809 Miller Jun 2008 A1
20080141810 Miller Jun 2008 A1
20080146403 Miller Jun 2008 A1
20080146404 Miller Jun 2008 A1
20080149407 Shibata Jun 2008 A1
20080161151 Miller Jul 2008 A1
20080183358 Thomson Jul 2008 A1
20080188345 Miller Aug 2008 A1
20080200300 Smithson Aug 2008 A1
20080228362 Muller Sep 2008 A1
20080236319 Nichols Oct 2008 A1
20080248917 Nichols Oct 2008 A1
20080261771 Nichols Oct 2008 A1
20080284170 Cory Nov 2008 A1
20080305920 Nishii Dec 2008 A1
20090011907 Radow Jan 2009 A1
20090023545 Beaudoin Jan 2009 A1
20090055061 Zhu Feb 2009 A1
20090062062 Choi Mar 2009 A1
20090082169 Kolstrup Mar 2009 A1
20090107454 Hiyoshi Apr 2009 A1
20090132135 Quinn, Jr. May 2009 A1
20090164076 Vasiliotis Jun 2009 A1
20090189397 Miller Jul 2009 A1
20090221391 Bazyn Sep 2009 A1
20090251013 Vollmer Oct 2009 A1
20090280949 Lohr Nov 2009 A1
20090312145 Pohl Dec 2009 A1
20090318261 Tabata Dec 2009 A1
20100056322 Thomassy Mar 2010 A1
20100093479 Carter Apr 2010 A1
20100093480 Pohl Apr 2010 A1
20100093485 Pohl Apr 2010 A1
20100120577 Gu May 2010 A1
20100131164 Carter May 2010 A1
20100145573 Vasilescu Jun 2010 A1
20100181130 Chou Jul 2010 A1
20100198453 Dorogusker Aug 2010 A1
20100228405 Morgal Sep 2010 A1
20100264620 Miles Oct 2010 A1
20100267510 Nichols Oct 2010 A1
20100313614 Rzepecki Dec 2010 A1
20110034284 Pohl Feb 2011 A1
20110088503 Armstrong Apr 2011 A1
20110105274 Lohr May 2011 A1
20110127096 Schneidewind Jun 2011 A1
20110172050 Nichols Jul 2011 A1
20110178684 Umemoto Jul 2011 A1
20110184614 Keilers Jul 2011 A1
20110190093 Bishop Aug 2011 A1
20110218072 Lohr Sep 2011 A1
20110230297 Shiina Sep 2011 A1
20110237385 Andre Parise Sep 2011 A1
20110254673 Jean Oct 2011 A1
20110291507 Post Dec 2011 A1
20110319222 Ogawa Dec 2011 A1
20120029744 Yun Feb 2012 A1
20120035011 Menachem Feb 2012 A1
20120035015 Ogawa Feb 2012 A1
20120035016 Miller Feb 2012 A1
20120043841 Miller Feb 2012 A1
20120115667 Lohr May 2012 A1
20120130603 Simpson May 2012 A1
20120158229 Schaefer Jun 2012 A1
20120238386 Pohl Sep 2012 A1
20120239235 Voigtlaender Sep 2012 A1
20120258839 Smithson Oct 2012 A1
20120309579 Miller Dec 2012 A1
20130035200 Noji Feb 2013 A1
20130053211 Fukuda Feb 2013 A1
20130072340 Bazyn Mar 2013 A1
20130079191 Lohr Mar 2013 A1
20130080006 Vasiliotis Mar 2013 A1
20130095977 Smithson Apr 2013 A1
20130102434 Nichols Apr 2013 A1
20130106258 Miller May 2013 A1
20130139531 Pohl Jun 2013 A1
20130146406 Nichols Jun 2013 A1
20130152715 Pohl Jun 2013 A1
20130190123 Pohl Jul 2013 A1
20130190125 Nichols Jul 2013 A1
20130288844 Thomassy Oct 2013 A1
20130288848 Carter Oct 2013 A1
20130310214 Pohl Nov 2013 A1
20130324344 Pohl Dec 2013 A1
20130331218 Lohr Dec 2013 A1
20130337971 Kolstrup Dec 2013 A1
20140011619 Pohl Jan 2014 A1
20140011628 Lohr Jan 2014 A1
20140026697 Mori Jan 2014 A1
20140038771 Miller Feb 2014 A1
20140073470 Carter Mar 2014 A1
20140094339 Ogawa Apr 2014 A1
20140121922 Vasiliotis May 2014 A1
20140128195 Miller May 2014 A1
20140141919 Bazyn May 2014 A1
20140144260 Nichols May 2014 A1
20140148303 Nichols May 2014 A1
20140155220 Messier Jun 2014 A1
20140179479 Nichols Jun 2014 A1
20140206499 Lohr Jul 2014 A1
20140228163 Aratsu Aug 2014 A1
20140248988 Lohr Sep 2014 A1
20140257650 Carter Sep 2014 A1
20140274536 Versteyhe Sep 2014 A1
20140323260 Miller Oct 2014 A1
20140329637 Thomassy Nov 2014 A1
20140335991 Lohr Nov 2014 A1
20140365059 Keilers Dec 2014 A1
20150018154 Thomassy Jan 2015 A1
20150038285 Aratsu Feb 2015 A1
20150039195 Pohl Feb 2015 A1
20150051801 Quinn, Jr. Feb 2015 A1
20150072827 Lohr Mar 2015 A1
20150080165 Pohl Mar 2015 A1
20150219194 Winter Aug 2015 A1
20150226323 Pohl Aug 2015 A1
20150233473 Miller Aug 2015 A1
20150260284 Miller Sep 2015 A1
20150337928 Smithson Nov 2015 A1
20150345599 Ogawa Dec 2015 A1
20150360747 Baumgaertner Dec 2015 A1
20150369348 Nichols Dec 2015 A1
20150377305 Nichols Dec 2015 A1
20160003349 Kimura Jan 2016 A1
20160031526 Watarai Feb 2016 A1
20160039496 Hancock Feb 2016 A1
20160040763 Nichols Feb 2016 A1
20160061301 Bazyn Mar 2016 A1
20160075175 Biderman Mar 2016 A1
20160131231 Carter May 2016 A1
20160146342 Vasiliotis May 2016 A1
20160178037 Pohl Jun 2016 A1
20160186847 Nichols Jun 2016 A1
20160195177 Versteyhe Jul 2016 A1
20160201772 Lohr Jul 2016 A1
20160244063 Carter Aug 2016 A1
20160273627 Miller Sep 2016 A1
20160281825 Lohr Sep 2016 A1
20160290451 Lohr Oct 2016 A1
20160298740 Carter Oct 2016 A1
20160347411 Yamamoto Dec 2016 A1
20160362108 Keilers Dec 2016 A1
20160377153 Ajumobi Dec 2016 A1
20170072782 Miller Mar 2017 A1
20170082049 David Mar 2017 A1
20170102053 Nichols Apr 2017 A1
20170103053 Guerra Apr 2017 A1
20170106866 Schieffelin Apr 2017 A1
20170159812 Pohl Jun 2017 A1
20170163138 Pohl Jun 2017 A1
20170204948 Thomassy Jul 2017 A1
20170204969 Thomassy Jul 2017 A1
20170211696 Nassouri Jul 2017 A1
20170211698 Lohr Jul 2017 A1
20170225742 Hancock Aug 2017 A1
20170268638 Nichols Sep 2017 A1
20170274903 Carter Sep 2017 A1
20170276217 Nichols Sep 2017 A1
20170284519 Kolstrup Oct 2017 A1
20170284520 Lohr Oct 2017 A1
20170314655 Miller Nov 2017 A1
20170328470 Pohl Nov 2017 A1
20170335961 Hamrin Nov 2017 A1
20170343105 Vasiliotis Nov 2017 A1
20170364995 Yan Dec 2017 A1
20180036593 Ridgel Feb 2018 A1
20180066754 Miller Mar 2018 A1
20180106359 Kawakami Apr 2018 A1
20180119786 Mepham May 2018 A1
20180134750 Alkan May 2018 A1
20180148055 Carter May 2018 A1
20180148056 Keilers May 2018 A1
20180195586 Thomassy Jul 2018 A1
20180202527 Nichols Jul 2018 A1
20180221714 Anderson Aug 2018 A1
20180236867 Miller Aug 2018 A1
20180251190 Hancock Sep 2018 A1
20180306283 Engesather Oct 2018 A1
20180327060 De Jager Nov 2018 A1
20180347693 Thomassy Dec 2018 A1
20180372192 Lohr Dec 2018 A1
20190049004 Quinn, Jr. Feb 2019 A1
20190102858 Pivnick Apr 2019 A1
20190195321 Smithson Jun 2019 A1
20190277399 Guerin Sep 2019 A1
20190323582 Horak Oct 2019 A1
20200018384 Nichols Jan 2020 A1
Foreign Referenced Citations (354)
Number Date Country
118064 Dec 1926 CH
1047556 Dec 1990 CN
1054340 Sep 1991 CN
2245830 Jan 1997 CN
1157379 Aug 1997 CN
1167221 Dec 1997 CN
1178573 Apr 1998 CN
1178751 Apr 1998 CN
1204991 Jan 1999 CN
2320843 May 1999 CN
1281540 Jan 2001 CN
1283258 Feb 2001 CN
1297404 May 2001 CN
1300355 Jun 2001 CN
1412033 Apr 2003 CN
1434229 Aug 2003 CN
1474917 Feb 2004 CN
1483235 Mar 2004 CN
1555466 Dec 2004 CN
1568407 Jan 2005 CN
1654858 Aug 2005 CN
2714896 Aug 2005 CN
1736791 Feb 2006 CN
1791731 Jun 2006 CN
1847702 Oct 2006 CN
1860315 Nov 2006 CN
1896562 Jan 2007 CN
1940348 Apr 2007 CN
101016076 Aug 2007 CN
101166922 Apr 2008 CN
101312867 Nov 2008 CN
201777370 Mar 2011 CN
102165219 Aug 2011 CN
102287530 Dec 2011 CN
102947626 Feb 2013 CN
203358799 Dec 2013 CN
103857576 Jun 2014 CN
104648595 May 2015 CN
104854380 Aug 2015 CN
108501935 Sep 2018 CN
498701 May 1930 DE
866748 Feb 1953 DE
1165372 Mar 1964 DE
1171692 Jun 1964 DE
2021027 Dec 1970 DE
2136243 Feb 1972 DE
2310880 Sep 1974 DE
2436496 Feb 1975 DE
3940919 Jun 1991 DE
4120540 Nov 1992 DE
19851738 May 2000 DE
10155372 May 2003 DE
10261372 Jul 2003 DE
102009016869 Oct 2010 DE
102011016672 Oct 2012 DE
102012107360 Feb 2013 DE
102012107927 Feb 2013 DE
102012210842 Jan 2014 DE
102012212526 Jan 2014 DE
102012023551 Jun 2014 DE
102012222087 Jun 2014 DE
102013201101 Jul 2014 DE
102014007271 Dec 2014 DE
102013214169 Jan 2015 DE
102019121883 Sep 2020 DE
0432742 Jun 1991 EP
0528381 Feb 1993 EP
0528382 Feb 1993 EP
0635639 Jan 1995 EP
0638741 Feb 1995 EP
0831249 Mar 1998 EP
0832816 Apr 1998 EP
0877341 Nov 1998 EP
0976956 Feb 2000 EP
1010612 Jun 2000 EP
1136724 Sep 2001 EP
1188602 Mar 2002 EP
1251294 Oct 2002 EP
1362783 Nov 2003 EP
1366978 Dec 2003 EP
1433641 Jun 2004 EP
1452441 Sep 2004 EP
1518785 Mar 2005 EP
1624230 Feb 2006 EP
1811202 Jul 2007 EP
1850038 Oct 2007 EP
2261108 Dec 2010 EP
2338782 Jun 2011 EP
2464560 Jun 2012 EP
2602672 Jun 2013 EP
2620672 Jul 2013 EP
2357128 Aug 2014 EP
2893219 Jul 2015 EP
2927534 Oct 2015 EP
620375 Apr 1927 FR
2460427 Jan 1981 FR
2590638 May 1987 FR
2909938 Jun 2008 FR
2996276 Apr 2014 FR
3073479 May 2019 FR
391448 Apr 1933 GB
592320 Sep 1947 GB
772749 Apr 1957 GB
858710 Jan 1961 GB
906002 Sep 1962 GB
919430 Feb 1963 GB
1132473 Nov 1968 GB
1165545 Oct 1969 GB
1376057 Dec 1974 GB
2031822 Apr 1980 GB
2035481 Jun 1980 GB
2035482 Jun 1980 GB
2080452 Feb 1982 GB
38025315 Nov 1963 JP
413126 Feb 1966 JP
0422844 Feb 1967 JP
441098 Jan 1969 JP
46029087 Aug 1971 JP
47448 Jan 1972 JP
47962 Jan 1972 JP
47207 Jun 1972 JP
4720535 Jun 1972 JP
47001621 Aug 1972 JP
4700962 Nov 1972 JP
4729762 Nov 1972 JP
4854371 Jul 1973 JP
4912742 Mar 1974 JP
49013823 Apr 1974 JP
49041536 Nov 1974 JP
50114581 Sep 1975 JP
5125903 Aug 1976 JP
51150380 Dec 1976 JP
5235481 Mar 1977 JP
53048166 Jan 1978 JP
5350395 Apr 1978 JP
55135259 Oct 1980 JP
5624251 Mar 1981 JP
56047231 Apr 1981 JP
56101448 Aug 1981 JP
56127852 Oct 1981 JP
58065361 Apr 1983 JP
59069565 Apr 1984 JP
59144826 Aug 1984 JP
59190557 Oct 1984 JP
6073958 May 1985 JP
60247011 Dec 1985 JP
61031754 Feb 1986 JP
61053423 Mar 1986 JP
61173722 Oct 1986 JP
61270552 Nov 1986 JP
62075170 Apr 1987 JP
63125854 May 1988 JP
63219953 Sep 1988 JP
63160465 Oct 1988 JP
01210653 Aug 1989 JP
01039865 Nov 1989 JP
01286750 Nov 1989 JP
01308142 Dec 1989 JP
02130224 May 1990 JP
02157483 Jun 1990 JP
02271142 Jun 1990 JP
02182593 Jul 1990 JP
03149442 Jun 1991 JP
03223555 Oct 1991 JP
422843 Jan 1992 JP
470207 Mar 1992 JP
470962 Mar 1992 JP
479762 Mar 1992 JP
04166619 Jun 1992 JP
04272553 Sep 1992 JP
04327055 Nov 1992 JP
05087154 Apr 1993 JP
0650358 Feb 1994 JP
06050169 Feb 1994 JP
07042799 Feb 1995 JP
07133857 May 1995 JP
07139600 May 1995 JP
07259950 Oct 1995 JP
08135748 May 1996 JP
08170706 Jul 1996 JP
08247245 Sep 1996 JP
08270772 Oct 1996 JP
09024743 Jan 1997 JP
09089064 Mar 1997 JP
1078094 Mar 1998 JP
10061739 Mar 1998 JP
10089435 Apr 1998 JP
10115355 May 1998 JP
10115356 May 1998 JP
10194186 Jul 1998 JP
10225053 Aug 1998 JP
10511621 Nov 1998 JP
H10307964 Nov 1998 JP
11063130 Mar 1999 JP
11091411 Apr 1999 JP
11210850 Aug 1999 JP
11227669 Aug 1999 JP
11240481 Sep 1999 JP
11257479 Sep 1999 JP
11317653 Nov 1999 JP
2000006877 Jan 2000 JP
2000046135 Feb 2000 JP
2000177673 Jun 2000 JP
2001027298 Jan 2001 JP
2001071986 Mar 2001 JP
2001107827 Apr 2001 JP
2001165296 Jun 2001 JP
2001234999 Aug 2001 JP
2001328466 Nov 2001 JP
2001521109 Nov 2001 JP
2002147558 May 2002 JP
61144466 Sep 2002 JP
2002250421 Sep 2002 JP
2002291272 Oct 2002 JP
2002307956 Oct 2002 JP
2002533626 Oct 2002 JP
2002372114 Dec 2002 JP
2003028257 Jan 2003 JP
2003056662 Feb 2003 JP
2003507261 Feb 2003 JP
2003161357 Jun 2003 JP
2003194206 Jul 2003 JP
2003194207 Jul 2003 JP
2003524119 Aug 2003 JP
2003320987 Nov 2003 JP
2003336732 Nov 2003 JP
2004011834 Jan 2004 JP
2004038722 Feb 2004 JP
2004162652 Jun 2004 JP
2004189222 Jul 2004 JP
2004232776 Aug 2004 JP
2004526917 Sep 2004 JP
2004301251 Oct 2004 JP
2005003063 Jan 2005 JP
2005096537 Apr 2005 JP
2005188694 Jul 2005 JP
2005240928 Sep 2005 JP
2005312121 Nov 2005 JP
2006015025 Jan 2006 JP
2006283900 Oct 2006 JP
2006300241 Nov 2006 JP
2007085404 Apr 2007 JP
2007321931 Dec 2007 JP
2007535715 Dec 2007 JP
2008002687 Jan 2008 JP
2008014412 Jan 2008 JP
2008133896 Jun 2008 JP
4351361 Oct 2009 JP
2010069005 Apr 2010 JP
2010532454 Oct 2010 JP
2011178341 Sep 2011 JP
2012501418 Jan 2012 JP
2012506001 Mar 2012 JP
4913823 Apr 2012 JP
4941536 May 2012 JP
2012107725 Jun 2012 JP
2012121338 Jun 2012 JP
2012122568 Jun 2012 JP
2012211610 Nov 2012 JP
2012225390 Nov 2012 JP
2013521452 Jun 2013 JP
2013147245 Aug 2013 JP
5348166 Nov 2013 JP
5647231 Dec 2014 JP
5668205 Feb 2015 JP
2015505022 Feb 2015 JP
2015075148 Apr 2015 JP
2015227690 Dec 2015 JP
2015227691 Dec 2015 JP
5865361 Feb 2016 JP
5969565 Aug 2016 JP
6131754 May 2017 JP
6153423 Jun 2017 JP
6275170 Feb 2018 JP
2018025315 Feb 2018 JP
20020054126 Jul 2002 KR
20020071699 Sep 2002 KR
20080079274 Aug 2008 KR
20080081030 Sep 2008 KR
20130018976 Feb 2013 KR
101339282 Jan 2014 KR
98467 Jul 1961 NL
74007 Jan 1984 TW
175100 Dec 1991 TW
218909 Jan 1994 TW
227206 Jul 1994 TW
275872 May 1996 TW
294598 Jan 1997 TW
360184 Jun 1999 TW
366396 Aug 1999 TW
401496 Aug 2000 TW
510867 Nov 2002 TW
512211 Dec 2002 TW
582363 Apr 2004 TW
590955 Jun 2004 TW
225129 Dec 2004 TW
225912 Jan 2005 TW
235214 Jul 2005 TW
200637745 Nov 2006 TW
200741116 Nov 2007 TW
200821218 May 2008 TW
201339049 Oct 2013 TW
9908024 Feb 1999 WO
9920918 Apr 1999 WO
2000061388 Oct 2000 WO
0138758 May 2001 WO
2001073319 Oct 2001 WO
2002088573 Nov 2002 WO
2003086849 Oct 2003 WO
2003100294 Dec 2003 WO
2004079223 Sep 2004 WO
2005019669 Mar 2005 WO
2005083305 Sep 2005 WO
2005108825 Nov 2005 WO
2005111472 Nov 2005 WO
2006014617 Feb 2006 WO
2006047887 May 2006 WO
2006091503 Aug 2006 WO
2007061993 May 2007 WO
2007070167 Jun 2007 WO
2007077502 Jul 2007 WO
2008002457 Jan 2008 WO
2008057507 May 2008 WO
2008078047 Jul 2008 WO
2008095116 Aug 2008 WO
2008100792 Aug 2008 WO
2008101070 Aug 2008 WO
2008131353 Oct 2008 WO
2008154437 Dec 2008 WO
2009006481 Jan 2009 WO
2009148461 Dec 2009 WO
2009157920 Dec 2009 WO
2010017242 Feb 2010 WO
2010024809 Mar 2010 WO
2010044778 Apr 2010 WO
2010073036 Jul 2010 WO
2010094515 Aug 2010 WO
2010135407 Nov 2010 WO
2011064572 Jun 2011 WO
2011101991 Aug 2011 WO
2011109444 Sep 2011 WO
2011121743 Oct 2011 WO
2011124415 Oct 2011 WO
2011138175 Nov 2011 WO
2012030213 Mar 2012 WO
2013042226 Mar 2013 WO
2013112408 Aug 2013 WO
2014186732 Nov 2014 WO
2016022553 Feb 2016 WO
2016062461 Apr 2016 WO
2016079620 May 2016 WO
2016205639 Dec 2016 WO
2017056541 Apr 2017 WO
2017186911 Nov 2017 WO
Non-Patent Literature Citations (83)
Entry
Office Action dated Jan. 18, 2017 in U.S. Appl. No. 14/529,773.
Office Action dated Jan. 20, 2012 for U.S. Appl. No. 12/137,456.
Office Action dated Jan. 20, 2015 in U.S. Appl. No. 13/682,176.
Office Action dated Jul. 16, 2012 for U.S. Appl. No. 12/271,611.
Office Action dated Jul. 18, 2016 in U.S. Appl. No. 13/938,056.
Office Action dated Jul. 25, 2012 for European Patent Application No. 06816430.0.
Office Action dated Jul. 5, 2017 in U.S. Appl. No. 14/529,773.
Office Action dated Jul. 6, 2016 in U.S. Appl. No. 14/529,773.
Office Action dated Jun. 19, 2014 in U.S. Appl. No. 13/682,176.
Office Action dated Jun. 28, 2011 from Japanese Patent Application No. 2009-518168.
Office Action dated Jun. 8, 2018 in U.S. Appl. No. 14/839,567.
Office Action dated Mar. 14, 2012 for U.S. Appl. No. 12/137,480.
Office Action dated Mar. 18, 2010 from U.S. Appl. No. 12/137,464.
Office Action dated Mar. 5, 2015 in U.S. Appl. No. 14/541, 875.
Office Action dated May 17, 2002 for Chinese Patent Application No. 98812170.0.
Office Action dated May 17, 2012 for U.S. Appl. No. 12/159,688.
Office Action dated May 29, 2013 for Chinese Patent Application No. 200880116244.9.
Office Action dated Nov. 14, 2012 for U.S. Appl. No. 12/159,688.
Office Action dated Nov. 14, 2017 in U.S. Appl. No. 15/172,031, 5 pages.
Office Action dated Nov. 3, 2017 in U.S. Appl. No. 14/996,743, 10 pages.
Office Action dated Oct. 19, 2012 for Canadian Patent Application No. 2632751.
Office Action dated Sep. 14, 2010 for Japanese Patent Application No. 2007-278224.
Office Action dated Sep. 15, 2010 for U.S. Appl. No. 11/543,311.
Office Action dated Sep. 24, 2012 for Chinese Patent Application No. 200880116244.9.
Office Action dated Sep. 24, 2012 for Taiwanese Patent Application No. 095137289.
Office Action dated Sep. 28, 2005 for Japanese Patent Application No. 2001-540276.
Partial International Search Report for International Application No. PCT/US2008/052685 dated Sep. 2, 2008.
Preliminary Notice of First Office Action dated Jan. 14, 2014 for Taiwanese Patent Application No. 095137289.
Preliminary Notice of First Office Action dated Jun. 20, 2014 in Taiwanese U.S. Appl. No. 97/144,386.
Rejection Decision dated May 29, 2015 in Taiwanese U.S. Appl. No. 97/144,386.
Second Office Action dated Feb. 24, 2016 in Chinese Patent Application No. 201410145485.3.
Supplementary European Search Report dated Apr. 1, 2009, for European Application No. 04715691.4, filed Feb. 7, 2004.
Taiwan Search Report and Preliminary Notice of First Office Action dated Oct. 30, 2008 for Taiwanese Patent Application No. 094134761.
Thomassy, Fernand A., “An Engineering Approach to Simulating Traction EHL”, CVT—Hybrid International Conference Mecc/Maastricht/The Netherlands, Nov. 17-19, 2010, p. 97.
Chinese Office Action dated Aug. 26, 2013 for Chinese Patent Application No. 201110120716.1.
Chinese Office Action dated Dec. 24, 2012 for Chinese Patent Application No. 201110120717.6.
Chinese Office Action dated Jan. 22, 2010 for Chinese Patent Application No. 200680052833.6.
Chinese Office Action dated May 28, 2013 for Chinese Patent Application No. 201110120717.6.
Examination Report dated Dec. 17, 2020 in Indian Patent Application No. 201837029026, 7 pages.
Examination report dated Jul. 11, 2018 in Indian Patent Application No. 2060/KOLNP/2010.
Examination Report dated Mar. 2, 2017 in Indian Patent Application No. 2772/KOLNP/2008.
Examination Report dated Sep. 25, 2013 for European Patent Application No. 06816430.0.
First Office Action dated Sep. 2, 2015 in Chinese Patent Application No. 201410145485.3.
International Search Report and Written Opinion dated Apr. 16, 2008, for PCT Application No. PCT/US2007/023315.
International Search Report and Written Opinion dated Dec. 20, 2006 from International Patent Application No. PCT/US2006/033104, filed on Aug. 23, 2006.
International Search Report and Written Opinion dated Feb. 2, 2010 from International Patent Application No. PCT/US2008/068929, filed on Jan. 7, 2008.
International Search Report and Written Opinion dated Jan. 25, 2010 from International Patent Application No. PCT/US2009/052761, filed on Aug. 4, 2009.
International Search Report and Written Opinion dated Jul. 21, 2017 in PCT/US2017/032023.
International Search Report and Written Opinion dated Jul. 27, 2009 from International Patent Application No. PCT/US2008/079879, filed on Oct. 14, 2008.
International Search Report and Written Opinion dated Jun. 27, 2017 in PCT/US2016/063880.
International Search Report and Written Opinion dated May 16, 2007 from International Patent Application No. PCT/IB2006/054911, dated Dec. 18, 2006.
International Search Report and Written Opinion dated May 19, 2009 from International Patent Application No. PCT/US2008/083660, filed on Nov. 14, 2008.
International Search Report and Written Opinion dated May 8, 2020 in PCT/US2020/019446.
International Search Report and Written Opinion dated Nov. 13, 2009 from International Patent Application No. PCT/US2008/053951, filed on Feb. 14, 2008.
International Search Report dated May 16, 2007, for PCT Application No. PCT/IB2006/054911.
International Search Report dated Nov. 21, 2002, for PCT Application No. PCT/US02/13399, filed on Apr. 25, 2002.
International Search Report for International Application No. PCT/US04/15652 dated Aug. 26, 2005.
International Search Report for International Application No. PCT/US05/25539 dated Jun. 8, 2006.
International Search Report for International Application No. PCT/US07/14510 dated Sep. 23, 2008.
International Search Report for International Application No. PCT/US2006/041389 dated Sep. 24, 2007.
International Search Report for International Application No. PCT/US2006/044983 dated Jun. 13, 2008.
International Search Report for International Application No. PCT/US2008/053347 dated Jul. 18, 2008.
International Search Report for International application No. PCT/US2005/035164 dated Jun. 27, 2007.
International Search Report for International Application No. PCT/US2006/039166 dated Feb. 27, 2007.
International Search Report for International application No. PCT/US2009/035540 dated Aug. 6, 2009.
Invitation to Pay Additional Fees dated May 3, 2017 in PCT/US2016/063880.
Notice of Office Action dated Jun. 22, 2016 in Taiwan Patent Application No. 103129866.
Notification of Reasons for Rejection dated Oct. 6, 2020 in Japanese Patent Application No. 2018-536480, 21 pages.
Notification of Reexamination dated Aug. 29, 2013 for Chinese Patent Application No. 200680052833.6.
Notification of the First Office Action dated Jun. 26, 2019 in Chinese Patent Application No. 201680080281.3.
Notification of the Second Office Action dated Mar. 16, 2020 in Chinese Patent Application No. 201680080281.3, 15 pages.
Office Action dated Apr. 2, 2014 in U.S. Appl. No. 13/288,711.
Office Action dated Aug. 13, 2013 for Canadian Patent Application No. 2632751.
Office Action dated Aug. 20, 2010 for Chinese Patent Application No. 200680052482.9.
Office Action dated Aug. 23, 2006 from Japanese Patent Application No. 2000-517205.
Office Action dated Aug. 29, 2013 in U.S. Appl. No. 13/288,711.
Office Action dated Aug. 3, 2015 in U.S. Appl. No. 14/541,875.
Office Action dated Dec. 12, 2011 for U.S. Appl. No. 12/271,611.
Office Action dated Dec. 12, 2016 in U.S. Appl. No. 13/938,056.
Office Action dated Dec. 29, 2017 in U.S. Appl. No. 14/839,567.
Office Action dated Dec. 4, 2012 for Korean Patent Application No. 10-2008-7016716.
Office Action dated Feb. 17, 2010 from Japanese Patent Application No. 2009-294086.
Office Action dated Feb. 24, 2010 from Japanese Patent Application No. 2006-508892.
Related Publications (1)
Number Date Country
20240149976 A1 May 2024 US
Provisional Applications (2)
Number Date Country
62344325 Jun 2016 US
62334947 May 2016 US
Divisions (1)
Number Date Country
Parent 16034659 Jul 2018 US
Child 17129564 US
Continuations (2)
Number Date Country
Parent 17129564 Dec 2020 US
Child 18206561 US
Parent 15172031 Jun 2016 US
Child 16034659 US