Electronics ppl.
anishma...@gmail.com
have more or less been determined .
We would also need some COE/IT ppl. (Some of them are expert
programmers)
On the electronics front, we should start work ASAP. For that we need
to clearly define the following(discuss in the next meeting) :
Since the robot is going to do a multitude of tasks, more than one
controller may (would) be required.
> As far as the image processing goes a product called EBOX II from microsoft should take care of it.
For the rest of the robot, there are going to be many things that need
to be controlled. i.e
> Motor Control (Both D.C. and Stepper). Better if the motion of robot is feedback based (optocouplers!).
> Interfacing various sensors (temp sensors, LDR's , touch sensors,distance rangers)
> Processing feedback from the above on the host controller.
>Some elementary form of AI (COE/IT ppl please elaborate)
> Wireless data transfer
Analog circuits required:
> Wireless Audio/Video (bidirectional)
> Amplifier circuitry for all sensors discussed earlier
...Add anything i may be missing
All the work is to be divided in modules and only the required amount
of interdependence between modules required, should be allowed.
for eg. the ppl designing all motor control circuitry should define a
protocol in which they would communicate with the host controller so
the ppl designing the host controller would know the format in which
the data is to be sent to the concerned module.
Work should be divided b/w all the group members and progress dicussed
in meetings held once/twice a week.
The pace of contribution from mechanical ppl is going to be very
critical!
Also try not to involve too many ppl in the project at an initial stage
as co-ordinating b/w different groups would be a problem