TECHNICAL FIELD

[0001] This disclosure generally relates to motion control, and more specifically, to estimation of inertias and friction coefficients for use as parameters in a motion control system.

BACKGROUND

[0002] Many automation applications employ motion control systems to control machine position and speed. Such motion control systems typically include one or more motors or similar actuating devices operating under the guidance of a controller, which sends position and speed control instructions to the motor in accordance with a user-defined control algorithm. Some motion control systems operate in a closed-loop configuration, whereby the controller instructs the motor to move to a target position or to transition to a target velocity (a desired state) and receives feedback information indicating an actual state of the motor. The controller monitors the feedback information to determine whether the motor has reached the target position or velocity, and adjusts the control signal to correct errors between the actual state and the desired state.

[0003] Designers of motion control systems seek to achieve an optimal trade-off between motion speed and system stability. For example, if the controller commands the motor to transition a mechanical component to a target position at a high torque, the machine may initially close the distance between the current position and the desired position at high speed (and thus in a time- efficient manner), but is likely to overshoot the desired position because of the high torque. Consequently, the controller must apply a corrective signal to bring the machine back to the desired position. It may take several such iterations before the motion system converges on the desired position, resulting in undesired machine oscillations. Conversely, instructing the motor to move at a lower torque may increase the accuracy of the initial state transition and reduce or eliminate machine oscillation, but will increase the amount of time required to place the machine in the desired position. Ideally, the controller gain coefficients should be selected to optimize the trade-off between speed of the state transition and system stability. The process of selecting suitable gain coefficients for the controller is known as tuning.

[0004] The response of a controlled mechanical system to a signal from a controller having a given set of controller gain coefficients depends on physical characteristics of the mechanical system, including the inertia and friction.

Inertia represents the resistance of the motion system to acceleration or deceleration. Friction is a resistive force resulting from the sliding contact between physical components of the system, such as the contact between the rotor and the shaft. The system's total friction can be modeled as a combination of its Coulomb friction and viscous friction. FIG. 1 is a simplified model 100 of a system's combined Coulomb and viscous friction as a function of is speed. The system's Coulomb friction has a relatively constant magnitude represented by the magnitude of the friction just as the system begins moving from a state of rest. Coulomb friction can be represented by point 102a when the system is moving in the forward direction, and point 102b when moving in the reverse direction. The viscous friction, which represents a frictional force which may be a function of lubrication between moving parts of the system, has a magnitude that typically increases with the magnitude of the speed, and is represented by the slopes 104a and 104b in the simplified model 100.

[0005] Accurate estimates for the inertia and friction of a controlled mechanical system can simplify the tuning process and improve performance of the system. However, identifying accurate values for these parameters for a given mechanical system can be difficult. In some cases, the inertia is estimated using manual calculations based on the rated motor data and physical data (weight, dimensions, etc.) of the components comprising the load. Such calculations can be cumbersome and time consuming, and may not yield accurate values for these important parameters.

SUMMARY

[0006] One or more embodiments of the present disclosure relate to systems and methods for automatically estimating the inertia, viscous friction coefficient, and Coulomb friction coefficient for controlled mechanical systems. To this end, an inertia and friction estimation system can instruct a controller to send a torque control signal to a motor, where the torque control signal varies continuously over time. This torque control signal can be controlled based on a testing sequence defined in the inertia and friction estimation system. In one or more embodiments, the testing sequence can specify that the torque control signal will increase gradually at a defined rate of increase, causing the motor to accelerate. In response to the velocity of the motion system satisfying a defined criterion, the torque control signal will then gradually decrease, causing the motor to decelerate to a rest state.

[0007] During these acceleration and deceleration phases, the inertia estimation system measures and records the velocity of the motor over time in response to the torque control signal. The estimation system can then determine an estimated inertia, an estimated viscous friction coefficient, and an estimated Coulomb friction coefficient for the mechanical system based on the time-varying torque signal and the measured velocity curve. These estimated inertia and friction coefficients can be used by the system designer in connection with determining suitable control parameters for the motion system. For example, the estimated inertia and/or the friction coefficients can be used by the controller to facilitate identification of appropriate controller gains for the system.

BRIEF DESCRIPTION OF THE DRAWINGS

[0008] FIG. 1 is a simplified model of a system's combined Coulomb and viscous friction as a function of is speed.

[0009] FIG. 2 is a simplified diagram of a closed-loop motion control architecture.

[0010] FIG. 3 is a block diagram of an example inertia and friction estimation system capable of generating estimated values of a mechanical system's inertia, viscous friction coefficient, and Coulomb friction coefficient.

[0011] FIG. 4 is a block diagram illustrating the inputs and outputs associated with an inertia and friction estimation system.

[0012] FIG. 5 is a diagram illustrating interactions between an inertia and friction estimation system and a motion control system during an example testing sequence.

[0013] FIG. 6 is a graph of an example torque command signal u(t) and a graph of a corresponding velocity feedback v(t) plotted over time. [0014] FIG. 7 is a block diagram depicting an inertia and friction estimation system that provides inertia and friction coefficient estimates to a motion controller.

[0015] FIG. 8 is a diagram of an architecture in which an inertia and friction estimation system operates as an independent component that is separate from a motion controller.

[0016] FIG. 9 is a diagram illustrating an example motion control tuning application that utilizes the estimated inertia and friction coefficients generated by an inertia and friction estimation system.

[0017] FIG. 10 is a flowchart of an example methodology for estimating an inertia, a Coulomb friction coefficient, and a viscous friction coefficient for a controlled mechanical system.

[0018] FIG. 1 1A and 1 1 B are flowcharts of an example methodology for executing a testing sequence on a motion system in order to estimate the inertia, viscous friction, and Coulomb friction of the system.

[0019] FIG. 12 is a block diagram representing an exemplary networked or distributed computing environment for implementing one or more

embodiments described herein.

[0020] FIG. 13 is a block diagram representing an exemplary computing system or operating environment for implementing one or more embodiments described herein.

DETAILED DESCRIPTION

[0021] Systems and methods described herein relate to techniques for generating estimated inertia, viscous friction coefficient, and Coulomb friction coefficient for controlled mechanical systems. One or more embodiments of the present disclosure can estimate these parameters in a substantially automated fashion by running the mechanical system through a testing sequence to be defined in more detail herein. Results of this testing sequence can be used to generate accurate inertia, viscous friction coefficient, and Coulomb friction coefficient estimates for the system. These estimated parameters can subsequently be used to facilitate simplified and accurate tuning and control of the motion system. [0022] FIG. 2 is a simplified diagram of a closed-loop motion control architecture. Controller 202 is programmed to control motor 204, which drives mechanical load 206. Controller 202, motor 204, and load 206 comprise the primary components of an exemplary motion control system. In an example application, load 206 can represent an axis of a single- or multi-axis robot or positioning system. In such applications, controller 202 sends control signal 208 instructing the motor 204 to move the load 106 to a desired position at a desired speed. The control signal 208 can be provided directly to the motor 204, or to a motor drive (not shown) that controls the power delivered to the motor 204 (and consequently the speed and direction of the motor). Feedback signal 210 indicates a current state (e.g., position, velocity, etc.) of the motor 204 and/or load 206 in substantially real-time. In servo-driven systems, feedback signal 210 can be generated, for example, by an encoder or resolver (not shown) that tracks an absolute or relative position of the motor. In sensorless systems lacking a velocity sensor, the feedback signal can be provided by a

speed/position estimator. During a move operation, the controller monitors feedback signal 210 to ensure that the load 206 has accurately reached the target position. The controller 202 compares the actual position of the load as indicated by the feedback signal 210 with the target position, and adjusts the control signal 208 as needed to reduce or eliminate error between the actual and target positions.

[0023] In another example application, load 206 can represent a spinning load (e.g., a pump, a washing machine, a centrifuge, etc.) driven by motor 204, in which controller 202 controls the rotational velocity of the load. In this example, controller 202 provides an instruction to motor 204 (via control signal 208) to transition from a first velocity to a second velocity, and makes necessary adjustments to the control signal 208 based on feedback signal 210. It is to be appreciated that the parameter estimation techniques of the present application are not limited to use with the example types of motion control systems described above, but rather are applicable for substantially any type of motion control application.

[0024] The control signal output generated by the controller 202 in response to an error between the desired position or velocity and the target position or velocity (as reported by the feedback signal 210) depends on the gain coefficients for the control loop. Design engineers must often employ a trial-and- error approach to identifying suitable gain coefficients (i.e. tuning the control loop), since suitable gain selection depends on physical characteristics of the mechanical system being controlled. For example, mechanical systems with a high inertia (resistance to acceleration or deceleration) may require relatively high initial torque to initiate a move to a new position or velocity, particularly if the application requires rapid convergence on the target position/velocity. However, high torque commands increase the possibility of overshoot, necessitating a reverse correction to bring the system back to the target. Non-optimal gain settings can result in undesired mechanical oscillations as the system performs multiple corrective iterations before settling on the target position or velocity. Such oscillations can introduce instability, cause system delays, and consume excessive power as a result of the additional work required to bring the system to a stable state. The friction of the motor and other moving parts can also affect how the mechanical system responds to a given control signal, and is therefore a factor to be considered when tuning the control system.

[0025] Control system tuning can be simplified if accurate estimates of the mechanical system's inertia and friction coefficients are known. Knowledge of these parameters can also improve performance of the controlled system during operation. For example, accurate estimates of a mechanical system's Coulomb and viscous friction coefficients can assist an engineer in designing the control system to more effectively compensate for these factors. However, identifying accurate inertia and friction coefficients for a mechanical system can be difficult. Accordingly, one or more embodiments of the present disclosure provide a technique for accurately estimating a controlled mechanical system's inertia, viscous friction coefficient, and Coulomb friction coefficient in a substantially automated fashion.

[0026] FIG. 3 is a block diagram of an example inertia and friction estimation system capable of generating estimated values of a mechanical system's inertia, viscous friction coefficient, and Coulomb friction coefficient. Inertia and friction estimation system 302 can include a torque command generator 304, a velocity monitoring component 306, a coefficient estimation component 308, an interface component 312, one or more processors 314, and memory 316. In various embodiments, one or more of the torque command generator 304, velocity monitoring component 306, coefficient estimation component 308, interface component 312, the one or more processors 314, and memory 318 can be electrically and/or communicatively coupled to one another to perform one or more of the functions of the inertia and friction estimation system 302. In some embodiments, components 304, 306, 308, and 312 can comprise software instructions stored on memory 316 and executed by processor(s) 314. The inertia and friction estimation system 302 may also interact with other hardware and/or software components not depicted in FIG. 3. For example, processor(s) 314 may interact with one or more external user interface device, such as a keyboard, a mouse, a display monitor, a

touchscreen, or other such interface devices.

[0027] Interface component 312 can be configured to receive user input and to render output to the user in any suitable format (e.g., visual, audio, tactile, etc.). User input can be, for example, user-entered parameters used by the inertia and friction estimation system 302 when executing an estimation sequence (to be described in more detail below). Torque command generator 304 can be configured to output a torque control command that various continuously over time according to a defined testing sequence. Velocity monitoring component 306 can receive velocity data for the mechanical system for use in calculating the inertia and friction coefficients. In some embodiments, the velocity monitoring component 306 can measure and record the velocity of the motor over time in response to the applied torque control command generated by the torque command generator 304. Alternatively, the velocity monitoring component 306 can receive the measured velocity data from separate measuring instrumentation.

[0028] Coefficient estimation component 308 can be configured to generate estimates of the inertia, viscous friction coefficient, and Coulomb friction coefficient of a motion system. The coefficient estimation component 308 determines these estimated parameters based on the time-varying torque command generated by torque command generator 304 and the measured velocity curve acquired by the velocity monitoring component 306, according to a model to be described in more detail below. The one or more processors 314 can perform one or more of the functions described herein with reference to the systems and/or methods disclosed. Memory 316 can be a computer-readable storage medium storing computer-executable instructions and/or information for performing the functions described herein with reference to the systems and/or methods disclosed.

[0029] The inertia and friction estimation system 302 can generate estimates for a mechanical system's inertia and friction coefficients by running the system through a testing sequence and calculating the estimates based on the results. FIG. 4 is a block diagram illustrating the inputs and outputs associated with inertia and friction estimation system 302. Inertia and friction estimation system 302 can generate a torque command signal 410 (e.g., an analog voltage signal such as a 0-10VDC signal, an analog current signal such as a 4-20mA signal, a digital signal, a software instruction, or any other suitable type of control signal), which instructs a motor driving the motion system to rotate in a specified direction at a given torque. Rather than issuing one or more constant torque commands that transition between constant torque values in sudden steps (resulting in a step-shaped torque output), inertia and friction estimation system 302 can control torque command signal 4 0 such that the torque value varies continuously over time between a maximum and minimum torque value. Inertia and friction estimation system 302 controls the torque value issued via torque command signal 410 in accordance with a testing sequence having user-defined parameters, as will be discussed in more detail below.

[0030] The motion system will accelerate or decelerate in accordance with the torque command signal 4 0 issued by inertia and friction estimation system 302, and velocity feedback 404 from the motion control system is provided to the estimation system 302. Velocity feedback 404 represents the velocity of the motion system over time in response to application of torque command signal 410. In an example testing sequence, inertia and friction estimation system 302 can control torque command signal 410 as a function of the velocity feedback 404 and one or more user-defined setpoints. The user-defined setpoints can include torque limits 406 defining the upper and lower bounds of the torque command signal 410, and velocity limits 408 defining checkpoint velocity valves used to control the torque command signal 410 and generate the estimates.

[0031] Upon completion of the testing sequence, inertia and friction estimation system 302 generates estimates of the motion system's inertia 412, viscous friction coefficient 414, and Coulomb friction coefficient 416. Inertia and friction estimation system 302 determines these estimates based on the torque command signal 410 that was issued to the motion system and the

corresponding velocity feedback 404. In one or more embodiments, inertia and friction estimation system 302 can integrate selected portions of the torque curve (corresponding to torque command signal 410) and the velocity curve

(corresponding to velocity feedback 404) over time, and calculate the inertia estimate 412, viscous friction estimate 414, and Coulomb friction estimate 416 as functions of these integrals.

[0032] FIG. 5 is a diagram illustrating interactions between inertia and friction estimation system 302 and a motion control system during an example testing sequence. In this example, motion system 524 comprises a motor 526, which responds to control signaling 520 provided by controller 518. Motor 526 is used to drive a load (not shown), such as a positioning axis, a rotational component of a machine, or other motor-driven load. Controller 518 also monitors feedback 522, which provides substantially real-time state data for the motor 526 (e.g., position, speed, etc.). In some scenarios, controller 518 may be a hardware controller, such as a programmable logic controller, motor drive, or other type of hardware controller. Controller 518 may also be a system-on-chip or other type of silicon-based or microchip controller in some implementations.

[0033] In the illustrated example, inertia and friction estimation system 302 is depicted as a separate element from controller 518 for clarity. For such configurations, and friction estimation system 302 can exchange data with controller 518 or other elements of the motion system 524 via any suitable communications means, including but not limited to wired or wireless networking, hardwired data links, or other communication means. In other embodiments, inertia and friction estimation system 302 can be an integrated component of controller 518. For example, inertia and friction estimation system 302 can be a functional component of the controller's operating system and/or control software executed by one or more processors residing on the controller 518. Inertia and friction estimation system 302 can also be a hardware component residing within controller 518, such as a circuit board or integrated circuit, that exchanges data with other functional elements of the controller 518. Other suitable

implementations of inertia and friction estimation system 302 are within the scope of certain embodiments of the present disclosure. [0034] Prior to testing, one or more user-defined parameters 512 are provided to inertia and friction estimation system 302 via interface component 312. These parameters can include a maximum torque Umax and a minimum torque Umin defining upper and lower limits on the torque command signal to be generated by torque command generator 304. In some embodiments, the estimation system 302 may only require the maximum torque Umax to be defined by the user, and can use the magnitude of the defined maximum torque as a limiting value for both the forward and reverse directions. In other embodiments, estimation system 302 may accept values for both Umax and Umin, allowing for different torque setpoints for the forward and reverse directions, respectively. The values selected for Umax and Umin can

correspond to the expected operational limits of the motion system 524, thereby allowing the inertia and friction coefficients to be determined based on characteristics of the motion system 524 over the system's entire torque profile. User-defined parameters 512 can also include a maximum velocity Vmax and a minimum velocity Vmin, which represent critical velocities used to define stages of the test sequence, as will be described in more detail below. It is to be understood that the defined maximum and minimum velocities do not necessarily correspond to the maximum and minimum operating velocities of the motor, or the maximum and minimum velocities that the motor will achieve during the testing sequence, but rather define key checkpoint velocities that, when reached during the testing sequence, will trigger a new phase of the testing sequence.

[0035] Interface component 312 provides torque command generator 304 with the user-defined parameters 512. When testing is initiated, torque command generator 304 outputs a torque command signal 410 to the motion system 524. Torque command signal 410 is represented as u(t), since the torque command generator 304 will vary the torque command continuously over time. In the configuration depicted in FIG. 5, estimation system 302 sends torque command signal 410 to controller 518, which in turn instructs the motor 526 (via control signaling 520) to rotate in the indicated direction at the indicated torque. As the motor is rotating, velocity monitoring component 306 reads velocity feedback 404 from controller 518 (which itself measures the velocity of the motor 526 via feedback 522). The measured velocity feedback 404 over time is represented as v t). As testing proceeds, torque command generator 304 can vary the torque command signal 410 in accordance with a predefined testing sequence, wherein phases of the testing sequence are triggered by the velocity feedback 404 relative to the user-defined parameters 512.

[0036] An example testing sequence is now explained with reference to FIG. 6, which illustrates an example torque command signal u(t) and

corresponding velocity feedback v(t) graphed over time. As shown on torque graph 602, the torque command signal u(t) is bounded by Umax and Umin. Velocity parameters Vmax and Vmin, shown on velocity graph 604, will determine phase transitions of the testing sequence. The values of Umax, Umin, Vmax, and Vmin can be defined by the user prior to testing (e.g., as user-defined parameters 512 of FIG. 5). In general, the estimation system 302 will apply a continuous torque signal that accelerates and then decelerates the motion system according to a defined sequence, obtain the continuously measured velocity of the motion system in response to the applied toque signal, and calculate the inertia ratio, Coulomb friction coefficient, and viscous friction coefficient of the motion system based on the torque signal, the velocity feedback data, and a calculation model that will be described in more detail below.

[0037] In the example illustrated in FIG. 6, when testing begins at time t = 0, the applied torque signal u(t) and the motor velocity v(t) axe both initially zero when the testing begins at time t = 0. However, in some scenarios the testing sequence may begin at a time when the speed of the motion system is non-zero. That is, the motion system does not necessarily need to be at rest when the testing sequence begins.

[0038] When the testing sequence begins at time t = 0, the torque command generator 304 applies a positive ramp torque, causing the motion system to accelerate. As shown in FIG. 6, the torque command signal u(t)is increased continuously at a substantially constant rate beginning at time t = 0. In one or more embodiments, the rate at which torque command signal is increased (that is, the slope of u(t)) can be configured as a user-defined parameter of the estimation system 302 (e.g., via interface component 312). During this first phase of the testing sequence, the torque command signal u(t) continues to increase until either the velocity of the motion system v t) reaches Vmax, or the torque command signal u(t) reaches Umax. In the illustrated example, the torque command signal reaches Umax just prior to the velocity of the motion system reaching Vmax. Accordingly, the torque command generator 304 holds the torque command signal at Umax while the velocity of the motion system continues to increase in response to the applied torque command signal. When the velocity v(t) reaches Vmax at time t = tc, the estimation system begins the second phase of the testing sequence. In some embodiments, if velocity v{t) does not reach Vmax within a defined timeout period after torque command signal has reached Umax (e.g., if Vmax was inadvertently set higher than the physical velocity limit of the motion system), the estimation system 302 can initiate a suitable timeout handling routine. This timeout handling routine may involve, for example, aborting the testing sequence and displaying an error message via interface component 312.

[0039] When the velocity v(t) reaches Vmax at time t = tc, the torque command generator 304 begins the second phase of the testing sequence by ramping the torque command signal u(t) downward toward Umin, causing the motion system to decelerate. Similar to the first phase of the test, the rate at which the torque command signal u(t) is decreased can be set by the user in one or more embodiments. As the torque command u(t) is decreased, the motor will continue to accelerate for a brief time (between time t = tc to td), though at a decreasing rate of acceleration, until the value of the torque command u(t) becomes less than the friction force of the motion system, at which time the motor will begin to decelerate (at time t = td). Since the motor was still accelerating when the velocity v(t) reached Vmax at time t = tc, the velocity will continue past Vmax for some time after the torque command begins decreasing, as shown in FIG. 6.

[0040] For this second phase of the test sequence, the torque command generator 304 will continue ramping down the torque command signal u(t) until either the torque command signal reaches Umin, or the velocity of the motion system v(t) decelerates to Vmin. In the illustrated example, the torque command signal u(t) decreases to Umin before the velocity v(t) reaches Vmin. Accordingly, the torque command generator 304 holds the torque command signal at Umin while the velocity continues to decelerate toward Vmin. As in the first phase of the testing sequence, the estimator system may be configured to initiate an error handling routine if the velocity v(t) does not decelerate to Vmin within a define time period after the torque command signal begins decreasing. Since Umin is set to be less than zero in this example sequence, the torque command signal u(t) decreases to zero at time t = td and continues decreasing as a negative torque value of increasing magnitude until Umin is reached. This negative torque value causes the motion system to decelerate at a faster rate relative to the acceleration of the first phase.

[0041] When the velocity of the motion system v t) reaches Vmin at time t = tf, the torque command generator 304 begins ramping the torque command signal back to zero, allowing the motion system to coast to a resting state as indicated by the tapering end of the v(t) curve in FIG. 6. At this point, the estimation system 302 has the data required to calculate estimates for the inertia and friction coefficients for the mechanical system.

[0042] The testing sequence described above in connection with FIG. 6 is only intended to represent an example, non-limiting testing sequence. It is to be understood that any suitable testing sequence that continuously varies the torque command (t) over time and measures a corresponding velocity profile v(t) for the motion system is within the scope of certain embodiments of this disclosure. For example, although the foregoing example describes the torque command u t) as changing direction in response to the velocity v(t) reaching the respective velocity checkpoints, some test sequences may include phases in which the torque command (t) only changes its rate of increase or decrease when the velocity checkpoint is reached, without altering the direction of the torque command (e.g., an increasing torque command may continue to increase in response to v(t) reaching a phase checkpoint, but at a slower rate).

[0043] As the foregoing testing sequence is performed, the inertia and friction estimation system 402 records both the torque command signal (t) generated by torque command generator 304 and the corresponding motor velocity v t) read by the velocity monitoring component 306. These torque and velocity curves characterize the motion system 524 such that accurate estimates of the inertia, Coulomb friction coefficient, and viscous friction coefficient can be determined based on the curves. In one or more embodiments, after the testing sequence described above has been executed and the data representing u(t) and v(t) has been obtained, the coefficient estimation component 308 calculates estimates of J B _v , and B _c based on integrals of u(t) and v(t) over specific time ranges of the testing sequnce. The following illustrates an example technique for leveraging integrals of u(t) and v(t) to derive estimates for the inertia and friction coefficients for a motion system.

[0044] A motion system can be described by the differential equation:

[0045] Jv(t) = -B _v v(t) - B _c sign{v(tj) + u(t) (1 )

[0046] where J is the inertia, B _c is the Coulomb friction coefficient, B _v is the viscous friction coefficient, u(t) is the torque command signal, v{t) is the corresponding velocity of the motion system in response to the torque signal u(t) (e.g. , u(t) and u(t) described above in connection with FIGs. 5 and 6), and

( 1, x > 0

[0047] signix) = \ 0, x = 0 (2)

{-l, x < 0

[0048] Referring to the torque and velocity graphs 602 and 604 in FIG. 6, the time period during which the torque command signal is positive (from time t = 0 to td) is designated as an acceleration stage, and the time period during which the torque command signal is negative (from time t = td until the motion system decelerates to a resting state) is designated as a deceleration stage.

[0049] For the purposes of determining estimates of the inertia and friction coefficients, the coefficient estimation component 308 designates multiple periods within the acceleration and deceleration stages with respect to the predefined velocity checkpoints Vmin and Vmax. In particular, since the system will be solving for three variables (J, B _v , and B _c ), the coefficient estimation component 308 designates at least three periods within the acceleration and deceleration stages in order to solve for J B _v , and B _c based on equation (1 ) above. In the present example, only three periods are designated. However, in some embodiments the coefficient estimation component 308 can be configured to designate more than three periods.

[0050] To determine the first and second periods, the coefficient estimation component 308 first determines the portion of the acceleration stage during which the velocity is between Vmin and Vmax. This portion of the acceleration stage is represented in FIG. 6 as the period between time t = ta and tc. The coefficient estimation component 308 then divides this portion of the acceleration stage into two periods. In the example curves in FIG. 6, the first period derived in this manner is the duration between time t = ta and tb, and the second period is the duration between time t = tb and tc. Any suitable criteria can be used to select a transition time tb between the first and second periods, provided time t = tb is a point in time between times t = ta and tc. For example, some embodiments of the estimation system may be configured to define time t = tb as the midway point between time t = ta (the time at which the velocity of the motion system reached Vmin) and time t = tc (the time at which the velocity reached Vmax). In another example embodiment, the estimation system may be configured to determine the time at which the velocity of the motion system reaches the middle point between Vmax and Vmin during the acceleration stage, and designate this time to be time t = tb. Other techniques for selecting time t = tb are also within the scope of one or more embodiments of this disclosure.

[0051] The third period is defined as the portion of the deceleration stage during which the velocity of the motion system is between Vmax and Vmin. In the example curves of FIG. 6, this third period is represented as the period between time t = te and tf. This period is not divided, but instead is maintained as a single period.

[0052] After the test data has been collected and the three periods described above have been identified, the coefficient estimation component 308 generates estimates of J, B _v , and B _c according to the following procedure. First, the coefficient estimation component 308 integrates both sides of equation (1 ) above for each of the three designated time periods. For the first time period (time t = ta to tb), integrating both sides of equation (1) yields:

[0053] J(y(t _b ) - v _. t _o )) = -B _v v{t)dt - B _c {t _b - t _a ) + / ^tfc u(t)dt (3)

[0054] For the second time period (time t = tb to tc), integrating both sides of equation (1 ) yields:

[0055] }{v{t _c ) - = -B _v f^ v(t)dt - B _c (t _c - t _b ) + f* _b ^c u(f)dt (4)

[0056] For the third time period (time t = te to tf), integrating both sides of equation (1 ) yields:

[0057] ; ( (t _f ) - v(t _e )) = ~B _V Q v(t)dt - B _c (t _f - t _e ) + ^u{t)dt (5)

[0058] Equations (3), (4), and (5) can be represented in simplified form by making the following substitutions:

[0059] Av _x = v(t _b ) - v{t _a ) (6)

[0060] Av ₂ = v(t _c ) - v(t _b ) (7) [0061] Av = v{tf) - v(t _e ) (8)

[0063] V ₂ = j£ v(t)dt (10)

[0064] (1 1 )

[0071] In FIG. 6, the integrals V _1t V ₂ , and V ₃ given by equations (9)-(1 1 ) above represent the corresponding shaded regions under the velocity curve v(t) for each of the three periods defined above. Likewise, the integrals Ui, U _2l and U ₃ given by equations (15)-(17) above represent the corresponding shaded regions under the torque curve (t) for the three periods. The coefficient estimation component 308 determines estimates for the inertia J, Coulomb friction coefficient B _c , and viscous friction coefficient B _v as a function of these integrals, as described below.

[0072] The values Av _t , Av ₂ , and Av ₃ given by equations (6), (7), and (8) represent the change in velocity of the motion system between the beginning and end of each of the three periods, respectively. The values At _x , At ₂ , and At ₃ given by equations (12), (13), and (14), represent the durations of each of the three periods.

[0073] Substituting the terms given by equations (6)-(17) into equations (3)-(5) yields the following:

[0074] Av + V _X B _V + At ₁ B _c = U _t (18)

[0075] AvJ + V ₂ B _V + At ₂ B _c = U ₂ (19)

[0076] Av- + V ₃ B _V + At ₃ B _c = U ₃ (20)

[0077] Since equations (18)-(20) are linear algebraic equations with full rank, any method can be used to solve for J, B _v , and B _c . Accordingly, the coefficient estimation component 308 can be configured to solve equations (18)- (20) for a given set of test data representing u(t) and v(t) using any suitable method. For example, in one or more embodiments the coefficient estimation component 308 can be configured to solve equations (18)-(20) using a matrix solution. In such embodiments, equations (18)-(20) can be arranged in matrix form:

[0078] Ax = b (21)

[0079] where

[0081] b = u ₂ (23) r / i

[0082] x - B _v (24)

IB

[0083] Coefficient estimation component 308 can solve equations (22)- (24) for J, B _v , and B _c using the solution

[0084] x = A ^~x b (25)

[0085] where A ^{~ l} is the inverse matrix of A, thereby obtaining estimates for J, B _v , and B _c .

[0086] As noted above, although the example embodiments described above designate three time periods over which to integrate u(t) and v t) in order to yield three equations (3), (4), and (5) (represented in alternate form as equations (18), (19), and (20)), some embodiments of the estimation system can designate more than three periods, yielding a corresponding number of equations which can be solved for J, B _v , and B _c . If coefficient estimation component 308 is configured to obtain more than three equations based on designation of more than three time periods, such embodiments of the coefficient estimation component 308 can apply a least square error method to solve for J, By, and B _c as an alternative to the matrix solution described above.

[0087] Equations (21)-(25) are example formulas for calculating estimated inertia and friction coefficients for a motion system based on continuous torque and velocity data. However, it is to be appreciated that any suitable formula for calculating these parameters through integration of a continuous torque signal and a corresponding velocity curve are within the scope of certain embodiments of this disclosure. [0088] Moreover, although the examples described above perform integration on the torque command signal (t) issued by the motion controller to estimate values for J, B _v , and S _c , some embodiments of estimation system 302 may be configured to use an actual torque measurement for the integration instead of or in addition to the issued torque command signal. In a variation of such an embodiment, the estimation system can be configured to determine the deviation of the actual (measured or estimated) torque of the motion system from the issued torque command signal, and take this deviation into consideration when estimating J, B _v , and B _c .

[0089] FIG. 7 is a block diagram depicting generation of inertia and friction coefficients by inertia and friction estimation system 302 according to one or more embodiments of the present disclosure. In general, the inertia and friction estimation system 302 generates estimates of the inertia J, viscous friction coefficient B _v , and Coulomb friction coefficient B _c for a motion system according to the following procedure. First, the estimation system 302 executes the testing sequence described above in connection with FIGs. 5 and 6 in order to obtain data representing toque and velocity curves u(t) and v(t). Torque command generator 304 and velocity monitoring component provide the data for u(t) and v(t) to the coefficient estimation component 308. Next, the coefficient estimation component 308 can select the three (or more) time periods corresponding to the portions of the torque and velocity curves that will be used as the basis for analysis. For example, the coefficient estimation component 308 can identify the acceleration and deceleration stages of the velocity curve, identify the portion of the acceleration stage during which the velocity is between Vmin and Vmax, and divide this time segment into two time segments to yield the first two periods. The third period can be identified as the portion of the deceleration stage during which the velocity is between Vmax and Vmin. The coefficient estimation component 308 then analyzes the torque and velocity data to determine the integrals, velocity differences, and time durations represented by equations (6)-(17) based on the three selected time periods, and generates equations (18), (19), and (20) using these values. The coefficient estimation component 308 then solves these equations for J, B _c , and B _v (e.g., using a matrix solution or other technique) in order to yield estimates of the inertia and friction coefficients, which are then output by the estimation system 302. [0090] In various embodiments, inertia and friction estimation system 302 can output the estimated inertia and friction coefficients in accordance with the requirements of a particular application in which the system operates. For example, as illustrated in FIG. 7, estimation system 302 may provide the estimates of J, B _v , and B _c to a motion controller 714, which can use the inertia and friction coefficient estimates to facilitate tuning one or more gain coefficients. In addition or alternatively, estimation system 302 may output the estimated values of J, B _v , and B _c to a display device (e.g., via interface component 312) so that the values can be viewed and entered manually into a separate motion control or tuning application. Accurate estimates of the motion system's inertia and friction coefficients can simplify the tuning process and facilitate accurate parameter tuning, resulting in precise and energy-efficient machine motion. Moreover, since the estimation system estimates the inertia and friction coefficients based on data collected over the motion system's entire torque profile (rather than extrapolating based on the system's response to one or more constant torque commands), the inertia and friction coefficient estimates derived by the estimation system 302 are more likely to be accurate over the full operational range of the motion system.

[0091] While the preceding examples have described the estimation system 302 as outputting the torque command u(t) and receiving the velocity feedback v(t) via the motion controller (e.g., controller 518 of FIG. 5), either as a separate component operating through the controller or as an integrated component of the controller, other configurations are within the scope of certain embodiments of this disclosure. For example, FIG. 8 illustrates an architecture in which inertia and friction estimation system 302 operates as an independent component that is separate from motion controller 802. In this example architecture, estimation system 302 is capable of generating its own torque command signal independently of controller 802. A motor 804 being tested and controlled can receive its torque command signal 808 from either controller 802 or estimation system 302 depending on the state of switch 812. The velocity feedback 8 0 from the motor 804 can be provided to both the controller 802 and estimation system 302. During the testing sequence, switch 812 can be set to convey the torque command signal u(t) generated by the estimation system 302 rather than controller 802. Testing can proceed as described in previous examples, such that estimation system 302 generates estimated values for the inertia J and friction coefficients B _c and B _v for the motion system. Estimation system 302 can then provide the estimated values for J, B ₀ , and B _v to the controller 802, which can use these values to determine suitable controller gain coefficients or other control parameters. Once the controller parameters have been set, switch 812 can be transitioned to connect the motor 804 to the torque command signal 808 genrated by controller 802 rather than estimation system 302, , and normal operation of the motion system can be carried out using the controller gain coefficients derived based on J, B _c , and B _v .

[0092] FIG. 9 illustrates an example motion control tuning application that utilizes the estimated inertia and friction coefficients generated by the estimation system 302. In this example, a tuning application 904 is used to tune the controller gains for controller 906, where the controller 906 controls operation of a motor-driven motion system (not shown). Estimation system 302 can generate estimates of the motion system's inertia J, viscous friction coefficient B _v , and Coulomb friction coefficient B _c using the techniques described above.

Specifically, estimation system 302 instructs controller 906 to send a continuous torque command to the motion system's motor, where the torque command varies continuously over time according to a predefined testing sequence.

Alternatively, for embodiments in which estimation system 302 operates independently of controller 906 (as in the example configuration depicted in FIG. 8), the estimation system 302 can generate and send its own continuous torque command to the motion system. The testing sequence can include acceleration and deceleration stages, during which the estimation system 302 monitors and records the velocity of the motion system in response to the applied torque command. At the conclusion of the testing sequence, estimation system 302 can calculate estimates of J, B _c , and B _v based at least in part on selected integrals of the time-varying torque command signal and the corresponding time- varying motion system velocity (e.g., based on equations (18), (19), and (20)).

[0093] Estimation system 302 can then provide the estimated inertia and friction coefficient values to the tuning application 904. Alternatively, estimation system 302 can render the values of J, B _c , and B _v on a user interface, allowing a user to manually enter the estimated inertia and friction coefficients into the tuning application 904. Knowledge of J, B _c , and B _v can allow the tuning application 904 to generate suitable estimates for one or more controller gains 912 based on the mechanical properties of the motion system represented by the estimated inertia and friction coefficients. Tuning application 904 can generate suitable values for controller gains 912 as a function of the inertia J, viscous friction coefficient B _v , and Coulomb friction coefficient B _c , as well as control system bandwidth (e.g., crossover frequency) 914, which can be manually adjusted by the user via interface 916 to achieve desired motion characteristics.

[0094] In typical applications, the inertia and friction estimation system described herein can be used to generate reliable estimates of a motion system's inertia J, viscous friction coefficient B _v , and Coulomb friction coefficient B _c during initial deployment of a motion control system, prior to normal operation. Specifically, the estimation system can be used in connection with configuring and tuning the controller parameters (e.g., controller gain coefficients) prior to runtime. Once set, these parameters typically remain fixed after system startup, unless it is decided to re-tune the system at a later time. However, in some embodiments, the estimation system can be configured to automatically recalculate values for J, B _c , and B _v periodically or continuously during normal closed-loop operation of the motion system. In such embodiments, the estimation system can monitor the torque command output signals issued by the controller in accordance with the user-defined control routines that execute during normal runtime operation (as opposed to the testing sequence described above), as well as the velocity of the motion system during acceleration and deceleration in response to these torque command signals. Using this runtime data, the estimation system can perform the integrations described above - either periodically, continuously, or semi-continuously - to generate updated estimates of J, B _& and B _v . Using such configurations, controller gains that are based on estimates of J, B _c , and B _v can be dynamically adjusted during normal operation, substantially in real-time, to compensate for gradual changes to the motion system's mechanical properties (e.g., as a result of mechanical wear and tear, changes to the load seen by a motor, addition or erosion of lubricants used in the motion system, etc.).

[0095] In the examples illustrated in FIGs. 5, 7, and 9, inertia and friction estimation system 302 is depicted as a separate element from the motion controller. For such configurations, any of components 304, 306, or 308 can exchange data with the controller or other elements of the motion system via any suitable communications means, including but not limited to wired or wireless networking, hardwired data links, or other such communication means. In other embodiments, one or more of components 304, 306, or 308 can be integrated components of a motion controller (e.g., an industrial controller such as a programmable logic controller, a system-on-chip or other type of microcontroller, etc.) For example, one or more of components 304, 306, or 308 can be functional components of the controller's operating system and/or control software executed by one or more processors residing on the controller.

Components 304, 306, or 308 can also be hardware components residing within the controller, such as a circuit board or integrated circuit, that exchanges data with other functional elements of the controller. In some embodiments, inertia and friction estimation system 302 may also be an integrated sub-system of a motor drive (e.g., a variable frequency drive or other motor drive). Other suitable implementations are also within the scope of certain embodiments of this disclosure.

[0096] Inertia and friction estimation system 302 can be used in connection with substantially any type of motion control application, including but not limited to conveyor control systems, industrial robots, washing machines, centrifuges, pumps, material handling systems, automotive systems, or other such motion control applications.

[0097] FIGS. 10-11 illustrate various methodologies in accordance with certain disclosed aspects. While, for purposes of simplicity of explanation, the methodologies are shown and described as a series of acts, it is to be understood and appreciated that the disclosed aspects are not limited by the order of acts, as some acts may occur in different orders and/or concurrently with other acts from that shown and described herein. For example, those skilled in the art will understand and appreciate that a methodology can alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all illustrated acts may be required to implement a methodology in accordance with certain disclosed aspects.

Additionally, it is to be further appreciated that the methodologies disclosed hereinafter and throughout this disclosure are capable of being stored on an article of manufacture to facilitate transporting and transferring such

methodologies to computers.

[0098] FIG. 10 illustrates an example methodology 1000 for estimating an inertia, a Coulomb friction coefficient, and a viscous friction coefficient for a controlled mechanical system. Initially, at 1002, a continuous torque command signal u(t) is sent to a controller of a motion system, where torque command signal (t) varies over time between defined maximum and minimum torque setpoints. In one or more embodiments, the torque command signal u(t) can accord to a predefined testing sequence, such that the output of u(t) depends on the phase of the testing sequence and the response of the mechanical system relative to one or more user-defined setpoints. The test sequence can comprise both acceleration and deceleration stages, corresponding to increasing and decreasing motor speeds, respectively.

[0099] At 1004, the velocity v(t) of the motion system in response to the torque command signal u t) is recorded. Thus, upon completion of the testing sequence, data curves for both the applied torque command signal u(t) and the resultant motion system velocity v t) are obtained for the duration of the test sequence.

[00100] At 1006, estimates for at least one of the inertia, the viscous friction coefficient, or the Coulomb friction coefficient of the motion system are calculated based on integrals of the torque curve u(t) and the velocity curve v(t). In one or more embodiments, three time periods within the duration of the test sequence can be selected, and equations defining a relationship between the inertia, Coulomb friction coefficient, and viscous friction coefficient can be obtained based on integrals of the torque and velocity curves over the three time segments (e.g., using equations (18), (19), and (20) above, or other suitable equations). The three equations can then be solved for the inertia, Coulomb friction coefficient, and viscous friction coefficient to obtain estimates of those three parameters. At 1008, one or more parameters for the motion system are set as a function of the estimated inertia and/or friction coefficients calculated at step 1006. In a non-limiting example, one or more controller gain coefficients can be set based on the estimated inertia and/or friction coefficients calculated according to steps 1002-1006. [00101] FIG. 1 1A illustrates a first part of an example methodology 1 100A for executing a testing sequence on a motion system in order to estimate the inertia, viscous friction coefficient, and Coulomb friction coefficient of the system. Initially, at 1 102, a determination is made regarding whether a torque command signal sent to a motion system (e.g., a torque command signal sent to a controller that controls the speed and/or position of a motion system) is greater than or equal to an upper torque limit Umax. In one or more embodiments, this upper torque limit can be a user-defined limit provided via a user interface. If the torque command signal is not greater than or equal to Umax, the methodology proceeds to step 1 104, where the torque command signal u(t) is continuously increased, and the velocity v(t) of the motion system in response to the applied torque command signal is recorded.

[00102] At 1 108, a determination is made regarding whether the velocity of the motion system is greater than or equal to a velocity checkpoint value Vmax. In one or more embodiments, this checkpoint value may be set by a user via a user interface. If the velocity is not greater than or equal to Vmax, the methodology returns to step 1 102, where it is again determined whether the torque command signal is greater than or equal to Umax. Steps 1 102, 1 104, and 1 108 are repeated continuously until either the torque command signal reaches Umax at step 1 102, or the velocity of the motion system reaches Vmax at step 1 108. If the torque command signal reaches Umax at step 1 102 before the velocity reaches Vmax, the methodology moves to step 1 106, where the torque command signal is held constant while the motion system continues to accelerate. In one or more embodiments, if the velocity does not reach Vmax at step 1 108 within a defined time period, an appropriate error handling routine may be executed (e.g., the methodology may halt the testing sequence and output an error message to an interface display).

[00103] When the velocity of the motion system reaches Vmax at step 1 108, the methodology proceeds to step 1 1 10, where a determination is made regarding whether the torque command signal is less than or equal to a lower torque limit Umin. As with Umax, this lower torque limit may be set by a user via a user interface. In some scenarios, the lower torque limit Umin may be less than zero. If the torque command signal is not less than or equal to Umin at step 1 1 10, the methodology moves to step 1 1 12, where the torque command signal to the motion system is continuously decreased, and the velocity of the motion system in response to the torque command signal continues to be recorded.

[00104] As the torque command signal continues decreasing, a

determination is made at step 1 116 regarding whether the velocity of the motion system has decreased to a value less than or equal to another velocity checkpoint value Vmin, which is set to be less than checkpoint value Vmax. If the velocity is not less than or equal to Vmin, the methodology returns to step 1 1 10, where a determination is again made regarding whether the torque command signal is less than or equal to Umin. Steps 1 110, 1 1 12, and 1 1 16 are repeated continuously until either the torque command signal becomes less than or equal to Umin at step 1 1 10, or the velocity of the motion system becomes less than or equal to Vmin at step 1 1 16.

[00105] If the torque command signal becomes less than or equal to Umin at step 1 1 10 before the velocity of the motion system becomes less than or equal to Vmin, the methodology moves to step 1 1 14, where the torque command signal is held constant while the motion system continues to decelerate. The torque command signal continues to be held constant until the velocity becomes less than or equal to Vmin at step 1 1 16.

[00106] The second part of the example methodology 1100B continues in FIG. 1 1 B. At the end of the test sequence described by methodology 1 100A, the system has a record of data describing the time-varying torque command signal u(t) sent to the motion system during the testing sequence, as well as measured velocity v{t) of the motion system over time in response to the applied torque command signal. At 1 118, the torque and velocity curves u(t) and v t are integrated over three time periods selected based on the values of the velocity checkpoints Vmax and Vmin. For example, in one or more embodiments, the time segment beginning at the time when the velocity of the motion system first reaches Vmin during acceleration and ending at a time before the velocity first reaches Vmax can be designated as the first time period, and the time segment beginning at the end of the first time period and ending at a time when the velocity first reaches Vmax during acceleration can be designated as the second time period. The third time period can be designated as the time segment beginning when the velocity of the decelerating motion system returns to Vmax and ending when the velocity returns to Vmin. These designated time periods are only intended to be exemplary, and it is to be appreciated that other criteria for selected three time segments over which to integrate the torque and velocity curves are within the scope of one or more embodiments of this disclosure. Six integral results are derived at step 1 1 18 - three integral results U _x , U ₂ , and U ₃ derived by integrating the torque curve over the respective three time periods, and three integral results V V ₂ , and V ₃ derived by integrating the velocity curve over the respective three time periods.

[00107] At 1 120, three equations are generated based on the integral results obtained at step 1 118, where each of the three equations define a relationship between inertia J, Coulomb friction coefficient B _c , and viscous friction coefficient B _v . For example, the equations can be derived by substituting the integrals U _x , U ₂ , U ₃ , V _x , V ₂ , and V ₃ into equations (18), (19), and (20) described above.

[00108] At 1122, the three equations generated at step 1 120 are solved to obtain estimates of J, B _c , and B _v . For example, the three equations can be solved using a matrix solution, based on equations (21 )-(25) above. However, other suitable techniques can be used to solve for the three variables without departing from the scope of one or more embodiments of this disclosure. At 1 124, the estimates of J, B _c , and B _v derived at step 1 122 are output, either to a display device, to the motion control system, or to another external system that uses the estimated inertia and friction coefficients in connection with designing or tuning the motion system.

EXEMPLARY NETWORKED AND DISTRIBUTED ENVIRONMENTS

[00109] One of ordinary skill in the art can appreciate that the various embodiments described herein can be implemented in connection with any computer or other client or server device, which can be deployed as part of a computer network or in a distributed computing environment, and can be connected to any kind of data store where media may be found. In this regard, the various embodiments of the video editing system described herein can be implemented in any computer system or environment having any number of memory or storage units (e.g., memory 316 of FIG. 3), and any number of applications and processes occurring across any number of storage units. This includes, but is not limited to, an environment with server computers and client computers deployed in a network environment or a distributed computing environment, having remote or local storage. For example, with reference to FIG. 3, the torque command generator 304, velocity monitoring component 306, coefficient estimation component 308, and interface component 312 can be stored on a single memory 316 associated with a single device, or can be distributed among multiple memories associated with respective multiple devices. Similarly, torque command generator 304, velocity monitoring component 306, coefficient estimation component 308, and interface component 312 can be executed by a single processor 314, or by multiple distributed processors associated with multiple devices.

[00110] Distributed computing provides sharing of computer resources and services by communicative exchange among computing devices and systems. These resources and services include the exchange of information, cache storage and disk storage for objects. These resources and services can also include the sharing of processing power across multiple processing units for load balancing, expansion of resources, specialization of processing, and the like. Distributed computing takes advantage of network connectivity, allowing clients to leverage their collective power to benefit the entire enterprise. In this regard, a variety of devices may have applications, objects or resources that may participate in the various embodiments of this disclosure.

[00111] FIG. 12 provides a schematic diagram of an exemplary networked or distributed computing environment. The distributed computing environment includes computing objects 1210, 1212, etc. and computing objects or devices 1220, 1222, 1224, 1226, 1228, etc., which may include programs, methods, data stores, programmable logic, etc., as represented by applications 1230, 1232, 1234, 1236, 1238. It can be appreciated that computing objects 1210, 1212, etc. and computing objects or devices 1220, 1222, 1224, 1226, 1228, etc. may comprise different devices, such as personal digital assistants (PDAs), audio/video devices, mobile phones, MP3 players, personal computers, laptops, tablets, etc., where embodiments of the inertia estimator described herein may reside on or interact with such devices.

[00112] Each computing object 1210, 1212, etc. and computing objects or devices 1220, 1222, 1224, 1226, 1228, etc. can communicate with one or more other computing objects 1210, 1212, etc. and computing objects or devices 1220, 1222, 1224, 1226, 1228, etc. by way of the communications network 1240, either directly or indirectly. Even though illustrated as a single element in FIG. 12, communications network 1240 may comprise other computing objects and computing devices that provide services to the system of FIG. 12, and/or may represent multiple interconnected networks, which are not shown. Each computing object 1210, 1212, etc. or computing objects or devices 1220, 1222, 1224, 1226, 1228, etc. can also contain an application, such as applications 1230, 1232, 1234, 1236, 1238 (e.g., inertia and friction estimation system 302 or components thereof), that might make use of an API, or other object, software, firmware and/or hardware, suitable for communication with or implementation of various embodiments of this disclosure.

[00113] There are a variety of systems, components, and network configurations that support distributed computing environments. For example, computing systems can be connected together by wired or wireless systems, by local networks or widely distributed networks. Currently, many networks are coupled to the Internet, which provides an infrastructure for widely distributed computing and encompasses many different networks, though any suitable network infrastructure can be used for exemplary communications made incident to the systems as described in various embodiments herein.

[00114] Thus, a host of network topologies and network infrastructures, such as client/server, peer-to-peer, or hybrid architectures, can be utilized. The "client" is a member of a class or group that uses the services of another class or group. A client can be a computer process, e.g., roughly a set of instructions or tasks, that requests a service provided by another program or process. A client process may utilize the requested service without having to "know" all working details about the other program or the service itself.

[00115] In a client/server architecture, particularly a networked system, a client can be a computer that accesses shared network resources provided by another computer, e.g. , a server. In the illustration of FIG. 12, as a non-limiting example, computing objects or devices 1220, 1222, 1224, 1226, 1228, etc. can be thought of as clients and computing objects 1210, 1212, etc. can be thought of as servers where computing objects 1210, 1212, etc. provide data services, such as receiving data from client computing objects or devices 1220, 1222, 1224, 1226, 1228, etc., storing of data, processing of data, transmitting data to client computing objects or devices 1220, 1222, 1224, 1226, 1228, etc., although any computer can be considered a client, a server, or both, depending on the circumstances. Any of these computing devices may be processing data, or requesting transaction services or tasks that may implicate the techniques for systems as described herein for one or more embodiments.

[00116] A server is typically a remote computer system accessible over a remote or local network, such as the Internet or wireless network infrastructures. The client process may be active in a first computer system, and the server process may be active in a second computer system, communicating with one another over a communications medium, thus providing distributed functionality and allowing multiple clients to take advantage of the information-gathering capabilities of the server. Any software objects utilized pursuant to the techniques described herein can be provided standalone, or distributed across multiple computing devices or objects.

[00117] In a network environment in which the communications

network/bus 1240 is the Internet, for example, the computing objects 1210, 1212, etc. can be Web servers, file servers, media servers, etc. with which the client computing objects or devices 1220, 1222, 1224, 1226, 1228, etc.

communicate via any of a number of known protocols, such as the hypertext transfer protocol (HTTP). Computing objects 1210, 1212, etc. may also serve as client computing objects or devices 1220, 1222, 1224, 1226, 1228, etc., as may be characteristic of a distributed computing environment.

EXEMPLARY COMPUTING DEVICE

[00118] As mentioned, advantageously, the techniques described herein can be applied to any suitable device. It is to be understood, therefore, that handheld, portable and other computing devices and computing objects of all kinds are contemplated for use in connection with the various embodiments. Accordingly, the below computer described below in FIG. 13 is but one example of a computing device. Additionally, a suitable server can include one or more aspects of the below computer, such as a media server or other media management server components.

[00119] Although not required, embodiments can partly be implemented via an operating system, for use by a developer of services for a device or object, and/or included within application software that operates to perform one or more functional aspects of the various embodiments described herein. Software may be described in the general context of computer executable instructions, such as program modules, being executed by one or more computers, such as client workstations, servers or other devices. Those skilled in the art will appreciate that computer systems have a variety of configurations and protocols that can be used to communicate data, and thus, no particular configuration or protocol is to be considered limiting.

[00120] FIG. 13 thus illustrates an example of a suitable computing system environment 1300 in which one or aspects of the embodiments described herein can be implemented, although as made clear above, the computing system environment 1300 is only one example of a suitable computing environment and is not intended to suggest any limitation as to scope of use or functionality.

Neither is the computing system environment 1300 be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the exemplary computing system environment 1300.

[00121] With reference to FIG. 13, an exemplary computing device for implementing one or more embodiments in the form of a computer 1310 is depicted. Components of computer 1310 may include, but are not limited to, a processing unit 1320, a system memory 1330, and a system bus 1322 that couples various system components including the system memory to the processing unit 1320. Processing unit 1320 may, for example, perform functions associated with processor(s) 314 of estimation system 302, while system memory 1330 may perform functions associated with memory 316.

[00122] Computer 1310 typically includes a variety of computer readable media and can be any available media that can be accessed by computer 1310. The system memory 1330 may include computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) and/or random access memory (RAM). By way of example, and not limitation, system memory 1330 may also include an operating system, application programs, other program modules, and program data.

[00123] A user can enter commands and information into the computer 1310 through input devices 1340, non-limiting examples of which can include a keyboard, keypad, a pointing device, a mouse, stylus, touchpad, touchscreen, trackball, motion detector, camera, microphone, joystick, game pad, scanner, or any other device that allows the user to interact with computer 1310. A monitor or other type of display device is also connected to the system bus 1322 via an interface, such as output interface 1350. In addition to a monitor, computers can also include other peripheral output devices such as speakers and a printer, which may be connected through output interface 1350. In one or more embodiments, input devices 1340 can provide user input to interface component 312, while output interface 1350 can receive information relating to operations of the inertia and friction estimation system 302 from interface component 312.

[00124] The computer 1310 may operate in a networked or distributed environment using logical connections to one or more other remote computers, such as remote computer 1370. The remote computer 1370 may be a personal computer, a server, a router, a network PC, a peer device or other common network node, or any other remote media consumption or transmission device, and may include any or all of the elements described above relative to the computer 1310. The logical connections depicted in FIG. 13 include a network 1372, such local area network (LAN) or a wide area network (WAN), but may also include other networks/buses e.g., cellular networks.

[00125] As mentioned above, while exemplary embodiments have been described in connection with various computing devices and network

architectures, the underlying concepts may be applied to any network system and any computing device or system in which it is desirable to publish or consume media in a flexible way.

[00126] Also, there are multiple ways to implement the same or similar functionality, e.g., an appropriate API, tool kit, driver code, operating system, control, standalone or downloadable software object, etc. which enables applications and services to take advantage of the techniques described herein. Thus, embodiments herein are contemplated from the standpoint of an API (or other software object), as well as from a software or hardware object that implements one or more aspects described herein. Thus, various embodiments described herein can have aspects that are wholly in hardware, partly in hardware and partly in software, as well as in software.

[00127] The word "exemplary" is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the aspects disclosed herein are not limited by such examples. In addition, any aspect or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms "includes," "has," "contains," and other similar words are used in either the detailed description or the claims, for the avoidance of doubt, such terms are intended to be inclusive in a manner similar to the term "comprising" as an open transition word without precluding any additional or other elements.

[00128] Computing devices typically include a variety of media, which can include computer-readable storage media (e.g., memory 316) and/or

communications media, in which these two terms are used herein differently from one another as follows. Computer-readable storage media can be any available storage media that can be accessed by the computer, is typically of a non-transitory nature, and can include both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer-readable storage media can be implemented in connection with any method or technology for storage of information such as computer-readable instructions, program modules, structured data, or unstructured data. Computer- readable storage media can include, but are not limited to, RAM, ROM,

EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or other tangible and/or non-transitory media which can be used to store desired information. Computer-readable storage media can be accessed by one or more local or remote computing devices, e.g., via access requests, queries or other data retrieval protocols, for a variety of operations with respect to the information stored by the medium.

[00129] On the other hand, communications media typically embody computer-readable instructions, data structures, program modules or other structured or unstructured data in a data signal such as a modulated data signal, e.g., a carrier wave or other transport mechanism, and includes any information delivery or transport media. The term "modulated data signal" or signals refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in one or more signals. By way of example, and not limitation, communication media include wired media, such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.

[00130] As mentioned, the various techniques described herein may be implemented in connection with hardware or software or, where appropriate, with a combination of both. As used herein, the terms "component," "system" and the like are likewise intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on computer and the computer can be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers. Further, a "device" can come in the form of specially designed hardware;

generalized hardware made specialized by the execution of software thereon that enables the hardware to perform specific function (e.g., coding and/or decoding); software stored on a computer readable medium; or a combination thereof.

[00131] The aforementioned systems have been described with respect to interaction between several components. It can be appreciated that such systems and components can include those components or specified subcomponents, some of the specified components or sub-components, and/or additional components, and according to various permutations and combinations of the foregoing. Sub-components can also be implemented as components communicatively coupled to other components rather than included within parent components (hierarchical). Additionally, it is to be noted that one or more components may be combined into a single component providing aggregate functionality or divided into several separate sub-components, and that any one or more middle layers, such as a management layer, may be provided to communicatively couple to such sub-components in order to provide integrated functionality. Any components described herein may also interact with one or more other components not specifically described herein but generally known by those of skill in the art. [00132] In order to provide for or aid in the numerous inferences described herein (e.g. inferring audio segments), components described herein can examine the entirety or a subset of the data to which it is granted access and can provide for reasoning about or infer states of the system, environment, etc. from a set of observations as captured via events and/or data. Inference can be employed to identify a specific context or action, or can generate a probability distribution over states, for example. The

inference can be probabilistic - that is, the computation of a probability distribution over states of interest based on a consideration of data and events. Inference can also refer to techniques employed for composing higher-level events from a set of events and/or data.

[00133] Such inference can result in the construction of new events or actions from a set of observed events and/or stored event data, whether or not the events are correlated in close temporal proximity, and whether the events and data come from one or several event and data sources. Various classification (explicitly and/or implicitly trained) schemes and/or systems (e.g., support vector machines, neural networks, expert systems, Bayesian belief networks, fuzzy logic, data fusion engines, etc.) can be employed in connection with performing automatic and/or inferred action in connection with the claimed subject matter.

[00134] A classifier can map an input attribute vector, x = (x1 , x2, x3, x4, xn), to a confidence that the input belongs to a class, as by f(x) =

confidence(class). Such classification can employ a probabilistic and/or statistical-based analysis (e.g., factoring into the analysis utilities and costs) to prognose or infer an action that a user desires to be automatically performed. A support vector machine (SVM) is an example of a classifier that can be employed. The SVM operates by finding a hyper-surface in the space of possible inputs, where the hyper-surface attempts to split the triggering criteria from the non-triggering events. Intuitively, this makes the classification correct for testing data that is near, but not identical to training data. Other directed and undirected model classification approaches include, e.g., naive Bayes, Bayesian networks, decision trees, neural networks, fuzzy logic models, and probabilistic classification models providing different patterns of independence can be employed. Classification as used herein also is inclusive of statistical regression that is utilized to develop models of priority.

[00135] In view of the exemplary systems described above, methodologies that may be implemented in accordance with the described subject matter will be better appreciated with reference to the flowcharts of the various figures (e.g., FIGs. 10 and 1 1). While for purposes of simplicity of explanation, the methodologies are shown and described as a series of blocks, it is to be understood and appreciated that the claimed subject matter is not limited by the order of the blocks, as some blocks may occur in different orders and/or concurrently with other blocks from what is depicted and described herein. Where non-sequential, or branched, flow is illustrated via flowchart, it can be appreciated that various other branches, flow paths, and orders of the blocks, may be implemented which achieve the same or a similar result. Moreover, not all illustrated blocks may be required to implement the methodologies described hereinafter.