Comments on: Calculating Torque http://www.bsodmike.com/calculating-torque/ The ramblings of a Rolex enthusiast... Thu, 20 Nov 2008 23:36:33 +0000 http://wordpress.org/?v=2.5.1 By: Ian Patterson http://www.bsodmike.com/calculating-torque/#comment-27385 Ian Patterson Wed, 25 Jun 2008 15:16:50 +0000 http://www.bsodmike.com/calculating-torque/#comment-27385 My bad, they were wrong but the logic in my explanation is true since servos have less torque as you move further away from the servo. I notice that they have corrected the value to 0.0720... which is correct. My bad, they were wrong but the logic in my explanation is true since servos have less torque as you move further away from the servo. I notice that they have corrected the value to 0.0720… which is correct.

]]> By: Ian Patterson http://www.bsodmike.com/calculating-torque/#comment-27384 Ian Patterson Wed, 25 Jun 2008 15:11:20 +0000 http://www.bsodmike.com/calculating-torque/#comment-27384 I believe that you are looking at this the wrong way. The google conversion is correct. Just maybe not what you were looking for. They are giving you a conversion for oz*in to kg*cm NOT oz/in and kg/cm. They are a ratio representing a maximum value since it would have more potential torque closer to the servo. Hope that helps. I believe that you are looking at this the wrong way.

The google conversion is correct. Just maybe not what you were looking for. They are giving you a conversion for oz*in to kg*cm NOT oz/in and kg/cm. They are a ratio representing a maximum value since it would have more potential torque closer to the servo.

Hope that helps.

]]> By: bsodmike.com » Google Calculator Error… http://www.bsodmike.com/calculating-torque/#comment-2166 bsodmike.com » Google Calculator Error… Tue, 14 Nov 2006 22:00:21 +0000 http://www.bsodmike.com/calculating-torque/#comment-2166 [...] Even though I posted this a while back and even suggested Google correct this error, it is STILL showing the same mistake, [...] [...] Even though I posted this a while back and even suggested Google correct this error, it is STILL showing the same mistake, [...]

]]>