Make a Raspberry Pi-Controlled Robot

Very detailed and practical book. A huge help to a newbie like me.

The author explained his goal in creating the robot, provided enough detail to follow along, provided enough background to understand his design choices, and provided enough breadth that you don't have to build his exact robot. If you would like to have fun building a robot, this might be the perfect book for you. I expected that if this book could explain building a robot well, it would be boring. I was wrong.

Amazing book with very practical examples to run with.

I wanted very much to like this book, but I just can't... When an author takes on the endevour of teaching the reader about something, they take on the responsibility to do so accurately. This is especially true on technical subject. Unfortunately, this book falls way short. At first I thought the author just wasn't a hardware guy. I've run into this in the past. My freshman year, I had a EE-Digital Design professor that didn't truly understand the analog the digital world is built on. He could quote the "rules" of EE-DD off the top of his head, but didn't know why they existed or how to tweak them to his use. I thought this after reading things like saying that there's the hall effect sensor is "nothing more than a simple switch". Yes, you can purchase a Hall Effect SWITCH, but the author shows a phidgets 1108 Hall Effect SENSOR - an analog device. Even a simple look at the phidgets page for the part shows it is "provides a voltage output that is proportional to the applied magnetic field." So no, it is NOT "nothing more than a simple switch". He also writes that he sees little use for such a device on a rover "outside a certain small niche of applications". The most common use for the device is rotational speed encoding... like used when trying to keep 2 motors running at the same speed to make a rover go in a straight line. Maybe the author should have look at Make:Sensors on the subject which even mentions speed encoding and talks about how to read it as an analog device. Then a page later or so, he tells about pull up/down resistors. He fairly accurately describes their use and floating inputs, but then writes that we can "do the same in code". The code simply enables the hardware pull up/down resistors that's built into the RPi. There's no software that can fix a floating input. The next page we hit the use of a "reed switch" where how shows a micro-switch. A reed switch is a magnetic switch like those used in burgular alarm systems. Two or three reeds are in a glass capsule with inert gas that switches when in proximity to a magnet. Just in case I was just used to common terms, I searched and could find no reference to a microswitch being called a reed switch. Then I started looking at the code snippets included in the book. Basic generally accepted software constructs like using a constant for pin assignment aren't there. So if we want to change a GPIO pin, we'd need to change it in every line of code that uses it. And if you mix multiple segments, suppose that the same pin for different sensors, we need to fix this BEFORE trying to incorporate it. This severely limits the reusability of the code. So while I wanted to like this book, I just couldn't. I couldn't even finish it. I'm actually a bit sorry I bought it. Maybe I'm expecting too much, but if you're teaching a technical subject, please research - at least the simple things, which this book doesn't.

This is a good book in many ways. The most important thing I got out of this book is the idea that building a decent sized autonomous robot is not a forbidding task. And, indeed, I've started converting an old pedal car into an autonomous vehicle using many of the ideas from this book. Kudos to the author for that kick in the pants! However, this book does not present a cut-and-dried set of instructions. You must be ready to read between the lines in order to get the most out of it. Not necessarily a bad thing but it's when I started doing it myself that I noticed the little things left unexplained. Given that I think anyone high school age and over should be able to do this on their own and what a marvelous project for a younger child and adult to share! And, as a professional and hobby software developer of long repute, I feel I must point out that the code examples are of fairly poor quality. They get the job done but certainly are not the best examples of how to do so! Take it as a challenge to refactor the code to be more efficient and you will be rewarded with developing good coding skills! In summation, if you have any interest in graduating up from tiny toy robots to something substantial than ignore any negative reviews and use this book as one of your guides. A lot of good ideas in here and they should not be ignored because of a few flaws.

Book is great really like some of the ideas

the idea is great. but i think for beginner, the quickiest way to get the hardware is to buy them. i bought makeblock for this purpose.

Great book

It's an interesting book that follows one substantial project through from beginning to end. There's useful information in it that helps with the electronics background. There's a section on programming. It looks a bit mediocre. You'd be better off learning programming with a proper textbook.

I'm having fun with this one. It's easy to read/follow and personable. Something you don't get in a tech book. What til you see my rover!

The book is one of the better attempts to produce a simple - focused 'how-to' guide for the Raspberry Pi. It should be noted that the author is very much an enthusiast and as such the information provided on the fundamentals is limited to that which is required to meet the stated goal of the projec - building a 4wheeled rover. Donat's style is well suited to the communication of the basics while highlighting the potential for broader modification and experimentation. I was impressed with the numerous and succint references to other texts and handbooks - an essential element fpr anyone trying to navigate the vast amount of material in this domain. In short - the mechanical design is a bit ropey - but the electronic design is functional, fit-for-purpose and well described.

Exactly what you would expect. Thanks!

Too basic to be any value. Waste of money.