Evaluating a robotic project!

[Joker94]

Hi every one

what i am interested in hearing is what do you guys think about when selecting a 'main' project. not a side project but one that you spend years on.

I am not short of side projects and have a big list of robotic ideas that may be possible but out of the lists i cant evaluate what project will be better suited.

do you have a process you go through every time you want to start a new project e.g. flow charts, comparison charts, list of pros and cons etc.

in short, what made you decide to go with a current or past project?

Cheers

Joker04

[Metal Slug 2]

With my projects, I just try to add a new sensor and/or component/device each time I build something.

Essentially right now all I'm trying to do is get as much experience with as many different types of hardware as possible. (main project)

I basically have a mental list of all the sensors I've used in projects, and all the ones I still need to work with.

I will also use two sensors that can work together to produce better results.  For example, a temperature compensated ultrasonic rangefinder.

[Joker94]

so you have started with a basic robotic base and are working from there?

not a bad idea, gives many possibilities.

[Metal Slug 2]

Ya.  Rather than choosing a project and buying the required things for it, I choose a sensor and think of projects to make with it.

[Joker94]

A good view, i'll keep that in mind.

[Tommy]

in short, what made you decide to go with a current or past project?

for me it's all about application, spot a problem, find an answer. if no answer is available, that's the project.


Tommy

[macdad-]

With my projects, I just try to add a new sensor and/or component/device each time I build something.

I'll second that, new components/methods/programs are always a good reason to build a robot, with those new components comes possible new applications that go beyond the actual prototype.

I'm still working on a Lego Mindstorms project that uses a Master/Slave setup(Which I haven't attempted before) with the RCX as the Master and Datalogger, while the Scout, as the Slave, works as navigation

[voyager2]

@Macdad- you have a SCOUT!
I always thought I was the only one with one still!

@Joker
It's good to gather lots of ideas from other projects then combine your results in one big project.
Kind of like Admins ERP.
You can try new ideas, discover new things.
Its good to try out new things, if it doesn't work then you can do something else.
Find something that has never been done before, or do a new take on something that's common!
Like Tommy said, fine an unresolved problem and fix it!

[z.s.tar.gz]

When I pick a main project it usually goes like this:

What would I like? (this is the toughest part because it usually involves seeing a picture or something online)
Can I build it? (This is usually a quick mental recap of what materials and tools I can get a hold of)
How am I going to make it? (This is the real tough part. I usually mull it over mentally for a week or two before drawing up any designs)
Where am I going to get the money/tools/materials from? (This is mainly a matter of looking up prices and modifying my plans accordingly.)

After that I start on the project. Of course most of that is just thinking but I hope it helps out a bit as far as a reasonable way to approach a new big project.

[Joker94]

very good points you make z.s.tar.gz

[krockhouse]

My first robot was a turret but now that I got my hands on an irobot will be attaching the turret to the irobot.  From there I can make it wireless, add a camera, sensors, ipod application, mapping, etc.  So you do not have to by any means start with the base mobile robot you can start with building an arm or turret or what have you.