 | | Re: Received my RIS 2.0 - the two motors run at different speed! :-(((
|
|
First of all, let me say that I very much appreciate your deep insight and your math formulas, which I have forgotten years ago. :) After further testing and measuring, I found that the difference is much larger - it actually deviates a good one (...) (24 years ago, 11-Jan-03, to lugnet.robotics)
|
| |
 | | Re: I2C device for the RCX
|
|
(...) high (...) frames (...) very (...) anyone (...) I (...) BrickOS (...) In the current release of BrickOS, the motors only get updated by the timer ISR every 2ms, so that probably explains why trying to twiddle the bits any faster than that (...) (24 years ago, 11-Jan-03, to lugnet.robotics)
|
| |
 | | Re: I2C device for the RCX
|
|
Steve is absolutely right and what he said is exactly what I'd recommend. When writing for loops, you can do the same test as Steve suggested: running the loop x 1000 times and then beep. Divide the stopwatch time by 1000 and you have the timing of (...) (24 years ago, 11-Jan-03, to lugnet.robotics)
|
| |
 | | Re: I2C device for the RCX
|
|
Steve, Very good suggestions! (...) Bastiaan v.Kesteren, I second Steve's recommendation, using loops for timing between command segments. You will not get very far using BrickOS msleep because of the 1ms minimum timing. Also, you may find the (...) (24 years ago, 11-Jan-03, to lugnet.robotics)
|
| |
 | | Re: Received my RIS 2.0 - the two motors run at different speed! :-(((
|
|
(...) Is it? Did you do the math or are your just guessing? There isn't enough information to figure the math from what you've told us... It depends on how wide your robot is and what units that triangle is in (feet? meters? miles?). But let's make (...) (24 years ago, 11-Jan-03, to lugnet.robotics)
|