|
|
 | | Re: Motor Speeds
|
| (...) Now this is starting to make sense. We use -100 to +100, but it does seem silly to have a resolution of 201. Much more logical that the routine converts to steps of lesser resolution, and 7 speeds certainly seem reasonable. (28 years ago, 23-Feb-97, to lugnet.robotics.handyboard)
| | | | | Re:
|
| (...) Looking at lib_hb.c: void motor(int m, int speed) { if (speed>100) speed=100; if (speed<-100) speed=-100; if (speed >= 0) _set_motor(m, 0, (speed + 3) / 14); else _set_motor(m, 1, (-speed + 3) / 14); } Keith (28 years ago, 23-Feb-97, to lugnet.robotics.handyboard)
| | | | | Re: More Motor Speeds
|
| (...) Either I'm confused or we're talking two different animals. Our pcode_hb.s19 that came with the Gleason Handyboard, allows variable motor speeds from motor(0,-100) to motor(0,100) with great and fine control. In our first test we converted (...) (28 years ago, 23-Feb-97, to lugnet.robotics.handyboard)
| | | | | Re: More Motor Speeds
|
| (...) You will have to rewrite the code in the interrupt functions. It isn't "hard" but it does require that you understand what IC is using the various timers for. The best documentation for that is the PCode itself. I don't believe you can use the (...) (28 years ago, 23-Feb-97, to lugnet.robotics.handyboard)
| | | | | Re: More Motor Speeds
|
| (...) ???? 7 speeds??? We use the IC that comes with the Gleason Associates Handyboard where motor(0,100) runs motor 0 full speed ahead motor(1,-33) runs motor 1 backwards at 1/3 speed where speeds vary from 1 to 100 in either direction. Can't you (...) (28 years ago, 23-Feb-97, to lugnet.robotics.handyboard)
|
|
