Sometimes the article editor becomes like a wild stallion that needs to be soothed, and usually in those cases it's because something was inside there it didn't like. I'd be happy to work with you on your next update to make sure everything goes perfectly. Please feel free to email me the code of your next update, or the HTML you were using for your current one.
My article will contain comprehensive and "enough to start-over" knowledge of the following parts of robotics. At the end of this series, the follower will be able to boast off his first AI Robot.
Choosing the type of automation control
Selection of hardware
selection of programming language
Preparing basic tools for our practicals
Codding of the base framework for any type of robot
Operating some output devices through our computer
Testing our systems for the first time
Interfacing relays and switches with computer in GUI
GUI interfacing of a servo motor with the Computer
GUI interfacing of simple DC variable speed motor
Measuring physical quantities
Measurement of room temperature on Computer
Measuring distance with SONAR
Measuring speeds of motors
Measuring angle between two physical links
Learning some very powerful tools for our robot
Interfacing a camera for measuring distance of objects
Speech synthesize/recognition system for the robots
Combining the knowledge; Creating our first robot
Designing/programming of a simple 4DOF Robotic arm
Detecting colored balls in sight and changing them to computer language
Teaching the system to detect faces, respond to voice commands and pick demanded balls.
I have taught two of my fellows the same things. One of them made a humanoid robot, ROBOx. 4feet tall ROBOx was able to walk, talk and interact with things placed around it.
I need feed back to start writing
Its a long, very long article because its intended to contain very basic knowledge for beginners, will be posted in many parts gradually in a couple of weeks. In order to start writing this series, i need to be sure that people will accept it on code project; some parts of the project may not include any code at all (Robot arm design) and may not get accepted by community. I don't want to end up in disappointment after a week or more that moderators just rejected the idea of writing the article on wrong place.
Not all articles need code in them. I have a few without code, and it doesn't make them any less worthwhile. As long as the articles are comprehensive and easy to follow, I reckon you'll have a pretty captive audience, and I would love to see it.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
Why is common sense not common?
Never argue with an idiot. They will drag you down to their level where they are an expert.
Sometimes it takes a lot of work to be lazy
Please stand in front of my pistol, smile and wait for the flash - JSOP 2012
I'm writing my very first article on this site, and having trouble with editing/writing properly, becouse every time I hit enter key it afects on first row of text (in this case the Introduction title).
I'm using opera browser, tried with IE with same results. Is there something I'm doing incorrectly?
Do you have a link to your article? Please send me the HTML of the original article as well and I'd be happy to take care of it.
Generally speaking though, if you're going to hit the Enter key it is better to do so in the HTML side of the WYSIWYG button, as in the preview pane things can get funky (it's adding an <br /> to the underbelly, and pending what part you're editing, that might get funky).