Subject:
|
Re: motor ports
|
Newsgroups:
|
lugnet.robotics.handyboard
|
Date:
|
Wed, 13 Jan 1999 12:47:11 GMT
|
Original-From:
|
fthompson9@#SayNoToSpam#aol.com
|
Viewed:
|
1122 times
|
| |
|
|
Russell,
Just a suggestion from experience. Before you invest a lot of time
developing hardware to expand the capability of the Handy Board, I suggest you
write the program. Just "stub out" the motors you don't have with dummy
subroutines, or for more accurate timing, remap those calls to the existing
motor ports. Your goal is to see if the program that you write can control
all the motors in your design in a timely maner. I call this the easy part
since you should already have everything you need for it (the Handy Board, and
IC). I once built a Z-80 robot controller whith hardware to implement the
full 256 I/O ports. I then wrote software to control the speed of two drive
wheels using pulse width modulation. I didn't have much of a hardware timer
(just a free running hardware clock), so my control program used 75% of the
CPU time just controling those two motors. I didn't have enough time for the
big job of planning what those motors were to do (where the robot goes). I
have since learned PIC programming.
Hope this saves time
Pherd
|
|
1 Message in This Thread:
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
