|
|
Average Customer Rating: 
Programming Robot Controllers >
Customer Review #1:
 Robotics...Really?
Much of the book has little to actually do with building a robot. Or even interfacing a controller into a system. Much of the book takes you through using a LCD. Little is done with inputs from sensors or controlling motors. Although it is a good tool to learn C for the PIC. Its not the best for using with robotics.
Programming Robot Controllers >
Customer Review #2:
 no help at all
I have worked in electronic for 15 yrs, and still couldnt understand what he tried to explain about PIC. but he wrote a lot of books about PIC...
Programming Robot Controllers >
Customer Review #3:
 Fair, lacks on GOOD ROBOT APPLICATIONS.
Hello, i had this book for quite some time now.
lt;br />The title is very good, you buy it expeting to have a good sense of what controller programming for robots (the title) should be only to find your self with a lot of unnecessary (in my opinion) "stuff".
lt;br />
lt;br />In his introduction there is a part named "Prerequisites for this book", let me comment on that because í think its very important.
lt;br />
lt;br />"Programming Robot Controllers was written for robot developers with some experience in developing robots. I will not be going into detail explaing basic programming, electronics, or PC operation, but you will have to be familiar with these areas of study".
lt;br />
lt;br />Hes right, his code is written in C, so if you are still to learn Basic or C, you should go elsewhere.
lt;br />
lt;br />The code provided in his book is somehow simple and very understandable (again, you need to have some programming background).
lt;br />
lt;br />Chapter 1, chapter 2 and most of chapter 3 are a good reference of what a µicrochip PIC is, what is a compiler, and information regarding the latters subjects.
lt;br />
lt;br />The end of chapter 3 is a good, quick lesson on how to build an inexpensive programmer "El Chepo" (El barato, this i like since im from México).
lt;br />
lt;br />Chapter 4 is about how the microcontroller works, conneting it to the world.
lt;br />In this chapter he gives situation-code examples, very simple codes that you can get better explained (on Karl Williams books, or Gordon McComBs master piece) elsewhere.
lt;br />
lt;br />The one approach of programming that i really like was the one about odometry (chapter 4, page 307-313). Here he explains the problem with turns on robots and how you should compensate for them.
lt;br />
lt;br />On Chapter 5 the explains and gives examples on how the whole code works together.
lt;br />
lt;br />The rest can easily be left out of the book (pages 360-456).
lt;br />
lt;br />The book is good if you are not sure how some taks are done (on Pics µicros) and my overall "feeling" of is:
lt;br />You dont get what you might expect; i was thinking i might get some flow diagrams, no flow diagrams. But i did get some information that i use (the odometry lesson).
lt;br />
lt;br />It maybe good or bad, i can only say that i found better "Programming" on "Build you own combat Robot" by Pete miles, the books by Karl Williams and even from Gordon McComb, they have programs written in basic but you can adopt them to assambler or C, because the code is simple and they provide flow charts.
lt;br />
lt;br />Well, there it is.
lt;br />
lt;br />Mario Alberto Camarillo Ramos
|
|
