Surviving bots

Hi all,
What I have in mind is that, say
I have a small robot which is programmable and can
move around ……
Now this robot is connected to an electrical outlet
(i.e. to which we connect many of our electronic
appliance) and gets itself recharge (i.e. recharges
its battery on which it runs)
Or it takes a good sun bath and gets tanned and
recharges itself (solar energy)
(Energy source can be anything taken in any form and
converted into electrical energy form)
And after it is fully charged it will explore other
energy sources (i.e. another electrical outlet in
house) keeping in mind its previous energy source, its
path so that if it doesn’t find new energy source it
can still go back to its previous non exhaustive
energy source.

I would like to give you one example here.
Some times it so happens that while making a movie
director keep in mind an actor and according to his
talent frames a good role in movie.

Whereas a movie is said to be a good movie if director
has a good character role first and an actor is said
to be a good actor if he enacting and doing justice to
the role.

Same way we don’t want to make software (role) for one
particular robot (actor)
But to make software which will be used by many
different robot.

This software won’t be just simulation software.
We will make it and also do a test drive on say few of
the robots, although frankly I don’t have any
programmable robot and I suppose not many of us will
be it having either, I will need some volunteer having
robots to do test drive of our software, else we will
have to make a robot our self to test it.

To begin with we will make software by using java and
may be C/C++ if at all needed
Now about the software say we will make few of the
basic non hardware classes
We will call them softbot 
Example (just a fair idea)
Interface Robot
{	
	….etc
}
Class Robotmodel implements Robot
{
	….etc
}
And hardware related API’s, classes on java or C/C++
etc or in assembly language
We call them hardbots
Example, say (just a fair idea)
% emu-survbots
> set_lcd_number (unsigned) 111
> refresh_display
> set_motor 0 FORWARD 3
> set_motor 0 BRAKE 7
> play_system_sound queued sound 0
....etc
& ROM call 3: 0x1FF2 (12319, 111, 12290)
& ROM call 0: 0x27C8
& ROM call 3: 0x1A4E (8192, 1, 3)
& ROM call 3: 0x1A4E (8192, 3, 7)
& ROM call 2: 0x299A (16388, 0)
	……..etc

now hardbots is dependent on hardware (robots), where
as softbot is not at all dependent on hardbot or
hardware(robots)
softbot(platform independent) and hardbot(processor
dependent) has to be modular, reusable, modifiable all
the time

all we will have to do is make softbot run on
hardware(robots) using hardbot for that particular
hardwear(robot)

Now with this input I think we should start with
execution after through planning and discussion with
everyone on softbot and hardbot development

I also did my home work i.e.  Visiting few of the
sites and getting more info related to our project we
might get good help on these sites

General Info/classification/history
http://www.cis.unisa.edu.au/~cisdm/papers/iagents/IntelligentAgentsInternet.html
An open source code software developed considering a
particular hardware(robot) in mind, unlike ours.
http://dudley.wellesley.edu/~anderson/robots/lejos/index.html
Programming for robots /projects on robots etc
http://www.oopic.com/
Open source code software for robot simulator
http://playerstage.sourceforge.net/

REMINDER ...
Guys those who have not send me their sourceforge id 
pleasse send it to me so that i can add you to the
project

Thanks and Regards
Arun Kumar

=====


__________________________________________________
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More
http://faith.yahoo.com