Robotics Books

1/3 or more of this book was commented Java source code. The other 1/3 was a really bad version of The Catcher in the Rye writing style about what someone wishes to do with his robots one day. There was little to no technical content about robots or programming for that matter. I was very disappointed with this book. Had I browsed through it at the bookstore I would have never spent a dime on it.

There's not a lot of detailed technical information but the book does a good job of listing a range of ideas and sources for building Linux robots. As an expert-level Linux Administrator, a decent C and Python programmer who is familiar with Java and as a budding roboticist, I found the book very useful.

I have this book and it has more than enough information to build a very capable robot that makes most of those that you can buy a toy.
Using free (as in free beer) software from the internet you can make a robot that can be anything that you want with just a little thought. The information is supplied in sections starting from some basic knowedge you can create a robot a piece at a time. The information covers movement - internal networking between indivual control modules to internet networking of the robot, to having the robot figure out where in the world or house it is and how does it get to where it needs to be. All the source code for the software is in the book and available from the authors site. It is a great starting place for a very potent robot.

Building Robots has become a fascination to a lot of people, including Mr. Newman, the author of this book. His robots are a long ways from C3PO. He basically build a robot mounted on wheels that has an awful lot of electronics. But then again he is including a lot of features in his design.

There are lot of ways to implement the controller. In this case he uses a small size but standard PC motherboard. On this board he runs a Linux operating system. In spite of the title, this is not really a book on how to use Linux to control robots. He just happens to use Linux for his robot because it is cheaper than Windows.

Most of the programming information he gives is the form of Java progrms that will handle the various devices (such as vision) that he wants built into his robots. In fact, much of the book, too much in fact, is given over to code. The code is available on line, reprinting it here in the book is pretty boring reading.

The book is a good introduction on how to design and build a robot using standard components. Here's how you can get started.

It is fare to say Mr. Newman is very competent programming and using Linux. The one star rating has more to do with content and publishing rather than a knock on Mr. Newman. It was obvious he was under time constraints and that this was his first book. He spends more time talking about features that are not working yet or that he wants to implement, than the process to build the robot in his book. The majority of the book is short descriptions without depth. The title and the table of contents are very unreflective of the text contained in the book. The book has 155 pages of "content" and 120 pages of Appendix. The code in the 119 pages of Appendix A while well written could have been included on a CD and much more detail added to the book. It reads, looks and is a rush job. It is clear Mr. Newman has skills and a firm grasp of Robotics and Linux. It is also very clear that this TAB book is a bust. I returned the book. If you are looking for an in-depth Linux and Robotics book then you are much better off with Open-Source Robotics and Process Control Cookbook: Designing and Building Robust, Dependable Real-time Systems
By Lewin Edwards. I bought this at the same time I bought Mr. Newman's book. I also own Lewin Edwards first book.
Embedded System Design on a Shoestring
I consider both of Lewin Edwards works mentioned above as must have books.

I am a professional consultant doing software for embedded processors. I have no affiliation with Myke Predko, the publisher, Microchip, or anyone else. Also, I am not getting paid for this. I got this book because I thought it would be handy to have a reference that had the assembly instructions for the PIC processor that I was using in one small book.

I have already purchased and reviewed Myke's other book "Programming & Customizing PICmicro Microcontrollers."

Here's what I learned:

1. I found the portable and fold-up type instructions sheet (yes, one sheet) that came with Microchip's MPLAB-ICD to be easier to use than Myke's book for the purposes of writing code. I could find the instruction faster in this sheet than I could in Myke's book. Searching for an item on one sheet is faster than paging through a book. Also, I can make the same comments about the data-sheets. It was easier to print these out and reference them than it was to look through the book.

2. When I did use Myke's book, I found myself checking it against the Microchip data sheet for confirmation. I found spelling errors with some of the assembly instructions listed in the book (the 2nd bcf command on page 32 and the btfsc command on page 33 are prime examples.)

3. Each instruction is explained in great detail. He included how the status bits are affected for commands that affect these bits. This is good because you don't have to search for this information in the data sheets. However, when I am in the midst of writing a code, I don't want to think anymore than I have to. I don't want to go think through complex boolean expressions that I'll forget in a few seconds right after I understand them. The example below illustrates this by comparing Myke's approach with Microchip's approach.

For the addwf f,d command,

Microchip says in their instruction set summary "Add the contents of the W register with register f. If d is 0, the result is stored in the W register. if d is 1, the result is stored back in the register f." It also tells me which flags are affected. If I want to know how the flags are affected, I just look up the status register info. in the data sheet - simple.

In his book, Myke writes:

if (d==1)
Reg = Reg + w
else
w = Reg + w
endif
c = (Reg+w)
> 0x0FF
Z = ((Reg + w)&
0x0FF) == 0
DC = ((Reg & 0x0F)
+ (w& 0x0F)
> 0x0F

The size of the book limits how this command is presented.
Still, the status bits could have been explained separately as the explanation is applicable to all instructions that affect the C, Z, and DC bits of the status register. Doing this would make the command easier to read.

4. I found myself using this book less and less when searching for specific assembly commands. For the purposes of programming, all the information I need is in the Microchip data sheets.

5. Chapters 11 (Useful Code Snippets,) 12 (16 Bit Numbers,) and
chapter 14 (Application Debugging Checklist.) are very useful - especially the first two.

Myke's "Programming & Customizing PICmicro Microcontrollers" book is worth buying. However, I am uncertain about recomending this book. Most of the information it contains can be found in the Microchip data sheets. If you like having the handy code snippets, the 16 bit numbers code, the debugging checklist, and other miscellaneous information handy then I recommend it.

Well I managed to wade through the muddle at the beginning about different compilers how fast etc and came to the nitty grits of using the IDE and compiler. What a shambles. AS a retired Raytheon Engineer in computer memories this was nonsense to me. In his own mind Mike I am sure knows his stuff but the way he goes about it is not planned. He should have been more explicit on the family tree when setting up the IDE and the Hi-Lite compiler. Start with a simple program let us all know what each line means. Also in one sentence tell us all that the Tristate register is programmed to either transmit or receive data and the ordinary port can be programmed to send or receive all or selected bits.A better buy is the CD one can buy from the UK which has on the CD the IDE , Compiler and excellent tutorial down to the nitties. I tried to contact Mike but Nada reply.

There's a lot of great information in this companion to Myke's "Programming and Customizing PICmicro Microcontrollers".

But it's inexcusable to repeat the poor organization, spelling, and accuracy of that book. That book began, "Though may (sic) name is on the cover of this book...". Okay, it's a typo and we all know what he meant. But in this "reference work", errors still abound. To cite just one example, some of the pin-out diagrams on page 12 are wrong. "Hey Myke, we're using this information to solder circuits here. Can someone check this stuff before it gets printed!"

Much of the content originates with the source book, but the choice of what is included is odd. For example, using the index, one can easily find wiring diagrams and code to connect LCD panels. But looking up some common programming commands requires going to broad information categories, rather than indexing all of the reserved words.

This book is still extremely useful and the Author is VERY knowledgeable. But he also frustrates his readers. For the same reasons that carpenters say "Measure twice, cut once" this book could have benefited from more careful planning and proofing.

This is a good book with a dabble of info on just about everything. I have only begun to make use of its potential. Keep in mind it is a pocket reference, so it's geared toward people who are already along their way knowing PICs fairly well. If you fall into that category this book is worth its cost without a doubt.

It would greatly help this book if it had tabs or some other way to help you index into the book. For example, if I want to look up an instruction, I open the book somewhere near the front 1/4 and spin the pages until I see the tables for the instruction set. Ah, but then I have to make sure I'm looking at the correct instruction set (low, mid, 17xx, 18xx) by going to the first page of the table to see its heading (the editor should emphasize on each page to which instruction set we are looking at. I have had to add mini Post-It(TM) notes to each section to help me index faster.

Coverage of the instruction sets are lacking (one page should be dedicated to each instruction and examples for the use of that instruction should be given). Don't make me turn the book side-ways. Put separation lines between each instruction if you can't put each instruction on a separate page.

I think the author should think more about what kind of information people would reference most. My feeling is that they would reference the instruction set and details about the instruction set the most. So that is where he should spend the most time getting a good format.

Where would I go to look for IC pin identification? The data sheet of course; not this book. Where would I go to see examples of how to hook up an LCD. Perhaps to the Programming and Customizing" book, but not in a reference book.

One last comment about the size and shape. I would rather see a book that's 6"x4" and 1/4" deep rather than 3"x2" and 1" deep. The current size and shape require multiple pages to cover topics, make indexing into the book harder because there are more pages to spin through, and the book doesn't stay open unless you turn it over. (how can I refer to the text and type on my PC at the same time if the book is face down?)

I, personally, am going to look on the web for a better reference document that is easier to use. I wish one could get their money back for books that don't meet your expectations. I usually get books through inter-library loan and check it out to see it's good enough to purchase. I guess I should have done that with this book.

Ask yourselves a question: what makes a being a person? If you don't like that question, consider another: what defines life and how do we know that it is present in creatures other than ourselves? These are just two of many questions theologian and computer scientist Anne Foerst ponders in this interesting and provocative book. "God in the Machine" considers what it means to be human, to have a soul, and to connect to God. Foerst is one of several scholars seeking to explore possibilities for a trans-human future in which robots and humans co-exist, or perhaps robots and humans merge into a new species of cyborgs. With a background in theology she is less interested in questions of what defines a legal person than what defines a new form of life. And what is the connection of that life to God. She notes that building these new life forms--robots--make us co-creators with God in what could be the advance of a new species. She suggests building robots may be best perceived as a type of prayer.

"God in the Machine" offers a breathless consideration of five major themes in cybernetics and theology. The first is the age-old quest to create life. From Golems to Frankenstein's creature this has been a dream of humanity. Second, Foerst explores the idea of embodied science, and then moves on to embodied intelligence, the fundamental attribute of robotic research. From there she investigates the nature of community and what it means to be a person within the context of larger systems. Finally, she seeks to link these ideas into a final chapter on the relationship of humans and robots in community.

This is an interesting, provocative, and sometimes frustrating work. Foerst writes well, but her illustrations are sometimes poorly drawn and not as fully explained as I would like. She also dispensed with notes in favor of a bibliography for each chapter, which meant that the sources for quotes are sometimes difficult to discern.

As a former student of Dr. Foerst, I was somewhat predisposed to the material that is presented in this book, perhaps more so than the average reader.

This book is well written which promotes the speed at which one finishes it; but is clearly written for a popular audience. As far as a criticism, I believe that this particular volume introduces more questions then it answers. The positive side of that remark is the number of splendid conversations that the book sparks. I have had many an intellectual discussion of science, philosophy and theology with friends and colleagues as the result of just some of those unanswered questions found in the book.

I would recommend this book.

My only request of Dr. Foerst is that another volume on this topic is written that dives more deeply into some of material introduced in this first book.

As a former student of Dr. Foerst, I was somewhat predisposed to the material that is presented in this book, perhaps more so than the average reader.

This book is well written which promotes the speed at which one finishes it; but is clearly written for a popular audience. As far as a criticism, I believe that this particular volume introduces more questions then it answers. The positive side of that remark is the number of splendid conversations that the book sparks. I have had many an intellectual discussion of science, philosophy and theology with friends and colleagues as the result of just some of those unanswered questions found in the book.

I would recommend this book.

My only request of Dr. Foerst is that another volume on this topic is written that dives more deeply into some of material introduced in this first book.

Those readers who have no religious beliefs but yet are interested in or working in the field of artificial intelligence may think that this book would not be very interesting or important, or possibly an apology for a particular religious worldview. When beginning the book this attitude will be reinforced somewhat, since it takes a while for the author to develop her main themes. Once she does however the book is fascinating, and her discussion of some of the issues in artificial intelligence is highly original and insightful. Considering the environment in which she worked it is refreshing to learn that the author was taken seriously, in spite of her overt expression of her religious beliefs. The only minus to the book is that the author concentrates her attention on robotics, which is a very narrow field of artificial intelligence at the present time. Machines can be intelligent to various degrees without looking like humanoids and without interacting with the environment in the manner that the author describes in great detail in the book. Indeed, these machines are more than just the "machines that sit on the desk" to quote the author. No, they cannot move in the world as humans do, but their abilities to perform tasks in a way that cannot be done by humans attests to their cognitive abilities.

Along with those who work in the field, the author has developed a deep appreciation of the magnificence of the human machine. She encapsulates her view of humanity not according to the usual classification, but according to human capabilities. Humans can tell stories ("homo narrans"), can stand upright ("homo erectus"), can use technology to change the world ("homo faber"), can engage in creativity ("homo ludens"), and can hold to religious beliefs ("homo religiosus"). There are of course other machines, biological and otherwise, that can do some of these things, but the human machine is unique in being able to do all of them, and then with a relatively low energy requirement. This of course does not make the human machine superior to the others, and in fact humans cannot compete at all with some of the machines of today in certain tasks. Those who build robots though insist on replicating the idiosyncrasies of the human machine, even though these robots may not be useful in any practical sense. The author's goal in the book is to try and understand why the building of these robots has been such an intense activity in the last half-century.

It is clear that many do not find the prospect of humanoid robots very pleasant at all. Hollywood movies, with their depiction of machines bent on the annihilation of humankind, are both an expression and cause of this anxiety. But stories of non-human entities possessing high degrees of intelligence have also pervaded our myths and stories long before the invention of film. As an example she describes the myth of the "golem" coming from Jewish mysticism. Interestingly, in some stories, golems are made from clay and constructed through words and numbers. Their purpose is to assist in the understanding of the world, a mythos or paradigm that definitely intersects with the one in artificial intelligence.

More interesting in her discussion of "rebuilding ourselves" is the reminder of a peculiar phenomenon that takes place in the artificial intelligence community, indeed in the scientific research community as a whole. This regards the "demystification" or diminishing of awe when a scientific explanation is found for a particular human capability. Indeed, it seems that every time an advance is made in artificial intelligence, such as a machine beating the best backgammon or chess player in the world, it eventually gets dismissed as being merely the result of a sophisticated program, and not as an example of true intelligence.

The author of course is not free of biases, as no one can be, whether they are in the scientific profession or not. Her intellectual honesty though is refreshing, and she is unashamed of her devout religious beliefs. She correctly recognizes that there are many in the scientific community who occupy both laboratories and churches, and make significant contributions to science. Whether they are scientists who sometimes practice religion or religionists who sometimes engage in scientific research is perhaps left to debate. But the author believes that these individuals, along with all the rest of humanity, clearly benefit and learn from social interactions, and that such interactions are even absolutely necessary for true intelligence to arise. Sometimes though these interactions go awry, and result in devastating conflict, this occurring primarily because of a diminution in respect for differences or of parties not being in the same physical space. The acceptance of humanoid robots she argues will therefore depend on whether their differences can be respected and whether they can interact with us in the same physical space. These robots can be viewed therefore as a gauge on how far we have advanced in our acceptance and respect for others. Certainly this is a good reason for the creation of these machines if none other can be found. But many other reasons can be found.....

The title of Ms. Foerst's book brings together two of humankind's greatest fears and desires: God and artificial intelligence. But despite such lofty goals, the text is mostly a rather mundane recollection of her days in the MIT AI lab during the 90s. These stories, such as accounts of the way humans emotionally responded to the faces of machines, are only occasionally marginally interesting. However, to her credit, she provides a more humanist perspective on human/robot interactions than a more technically focused writer would have.

The real problem with the book is when it actually tries to fulfill the lofty goals towards the end. This has the unfortunate result of taking the reader on a mixed up journey into human/robot and human/human interactions culminating in the conclusion that the path to world peace is for everyone to treat everyone else with the same friendly curiosity with which they treat robots. No joke...if you would just be nice to everyone, and everyone else would do the same, then we'd have world peace. It's that simple! And luckily, because of robots, we now understand this fact.

Clearly the argument has slightly more depth than my above characterization, but that is the general conclusion. And the reader is just left wondering at the end if there was something more valuable we could learn from robots.

Also, if you're curious, she is theologically quite liberal. So within the context of the book, God is more clockmaker than the God of the Bible.

While there is no one good definition of "robot", I would state as a minimum requirement that it interacts with its environment. Of the ten LEGO constructs in this book, only two - the Climber and Beetle - would qualify as robots. Of the eight remaining ones, six have no sensor inputs at all, and four have only one motor. These vehicles basically move forward or back, with no provision for turning, without major modifications.

That was the main disappointment: the book being more Technic than Mindstorms. A much better title would be, "The LEGO Technic and Mindstorms Idea Book". For many of these projects, a Technic battery pack could substitute for the RCX - and some of these look they were designed that way, with the RCX used to make them Mindstorms. Plus, this book has little material about programming (except for an NQC programming language appendix). Robotics is about both hardware and software, and that is the very spirit of LEGO Mindstorms.

There is also an overuse of obscure, exotic LEGO parts, such as the Slizer ones for the Legosaurus, and not all these projects can be built with the standard RIS kit. The Legosaurus motor mounting will not work as shown (one 24 tooth gear on top of another needs 6 1/2 plate spacing). I solved this problem by moving the motor to the rear end of the drive shaft.

I know this is an "Idea Book", and most of the fun comes with improvising, and improving the basic design. From a purely non-robotic LEGO Technic point of view, most of these designs are great. But if you want good Mindstorms books, try instead "Jin Sato's LEGO Mindstorms" or anything by Dave Baum.

this is a very basic book, if you are just starting with MindStorms or if you are 12 years old, then you'll like it. Hackers, dont think about getting it.

This book is a very good resource for learning the mechanical aspects of Mindstorms robots. The book provides step-by-step detail for several robot creations, with a range of complexities.

PROS: Detailed building plans and programs. Building tips to help you understand the principals behind the design. Joe Nagata: just go to his web site to see his LEGO creations and you'll know you're in good hands. Some really inventive creations, like the "water skater," a wheeled 'bot that propels itself using the same motion that a skater would use.

CONS: You'll need more parts than come with the standard Mindstorms kit. The book doesn't seem to be laid out correctly -the instructions for the current frame are adjacent to the next frame. Once you figure it out, it's not a problem. Some of the models didn't work very well as built - this is actually a PRO if you like to learn by troubleshooting.

Perhaps I'm spoiled by Dave Baum's great books but I found this book very frustrating. Some of the bots are interesting but I was unable to build most of them because they require extra parts that don't come in the Lego Mindstorms RIS. That'd be OK if the book told you what extra part syou need but I'd get 70% done and find myself short 6 #3 elbows (or whatever). True, he lists the needed parts before each bot, but he doesn't tell you which ones aren't part of the RIS. Baum does. Also, the pictures in the book lack contrast so it is hard to see details and the "steps" aren't specific. Buy the Baum books instead.

Joe Nagata's Lego Mindstorms Idea Book is a completely "user friendly" tutorial and "how to" guide book to making working robots. Profusely illustrated with more than 250 original CAD drawings and offering summaries of engineering principles and programming code, readers are easily able to understand how each robot works. Each robot building project includes a parts list as well as step-by-step instructions for their creation. Joe Nagata's Lego Mindstorms Idea Book is strongly recommended for anyone of any age or background who has ever watched an episode of "Robot Wars" and wanted to get in on the fun!

I bought this book thinking it would tell me how to program my own robot, and maybe how to make one from scratch. It just tells you a little bit of the basics, them moves on how to build the robot on his site. But it is an excellent book if you can afford his kit and dont want to move on to anything very advanced.

Dummies books are almost always spot-on in their usefulness. I say almost only because some titles do go stale as technology advances. I need to update some of the titles in my library. But I digress. Mr. Arrick does a good job of introducing the concept of kit robotics to the curious. Focusing on a specific kit platform called the ARobot, we are led through it's simple construction then add-on projects. If you're ready to attempt a simple robot, this book is an excellent choice.

Totally cool book!!!!! This is the first book related to robotics that I ever read. It's what got me hooked on robotics. I'd recommend this to any robotics beginner. Packed with helpfull information, this book is a no-questions-asked must-get!!!!!

I have been into the hobby of robotics for many years now and have to say that "THIS BOOK IS USELESS TO ANYONE HOPING TO BEGIN OR IMPROVE THEIR ROBOTICS SKILL SET". I was given this book as a gift for my birthday and have to admit it was a wasted gift. The first half (3rd actually) of the book is based on pure beginner how to and info, fine. Through out the basic discussion of gear ratios , batteries and electronics are references to the Arobot kit and how it is mentioned later. In the second half (3rd actually) of the book, where Roger starts the high level discussion on robotics, all you do is construct the $235 - $318 robot kit that he sells on his web page. The most helpful information in the whole book came from the list of 10's section (the last 3rd) found in all dummies books. If it weren't a gift I would have gotten my money back.

This book pretty easy to understand. Most others I looked at were too focused on one area or didn't show me how to actually get a real robot. I was reluctant to spend the money needed to buy a robot but finally did and it's awesome. I've added the light sensor and the camera with the movable head so far. This is my new hobby and its cool!

TD
Go Wranglers!

well-known book. but it is bad printing quality. i think it is photocopied not original book!!!!!

The book is written in a very clear and readable way. All topics explanations and examples are simple to understand.

I love this book, and together with Katsuhiko Ogata's Modern Control Systems Engineering, makes an excellent reference for control systems study at undergraduate level.

This book has only one thing I can say positive about it: It has a good appendix section that revises matrix theory. As far as the actual bulk of the text goes, well, just read my review title. It does not adequately cover the "intuitive" aspects of computer control, and Ogata has a habit of implying many things but not explaining them - for example, he uses the word "filter" interchangebly with the word "difference equation" which is very dangerous when you do not elaborate on the use of digital filters for signals. Most of the text is mathematical modelling with nothing included to help the undergraduate intuitively or qualitatively understand WHY computer controls work the way they do. In addition, many of the mathematical workings included do not have adequate detail in the steps in order to help students understand what he is doing. The text is very academic, very analytical, yet quite incomplete. Writing about computer control algorithms, should be left to people who understand computers best - computer engineers. It should NOT be done by mechanical engineers, because this is what happens...

This book was the major reference for our course of Digital Control, but a lot of things are not well explained. Starting by Z-transforms: the book doesn't even mention the regions of convergence (ROC), there in no topic about Fourier series/transform (I had to buy Signals & Systems by Oppenheim to completely understand z-transforms) and the topics about Discretization methods of analogic controllers (Euler, Tustin, etc.) is a joke. The discrete PID controllers are also not well explained. If you are in need of a well rounded book about discrete control, Ogata is a nice option - and expensive, but if you need something more deep, don't buy it.

One of the best books written on digital control, by an autjority in the field of controls. I found this book simple to understand even with no experience in digital control. Each chapter has lots of worked examples and practice problems, enough to get you comfortable with the chapter concepts. Its worth every penny...

This book was the text for one of my intro to programming courses. I had no choice. You do. Run while you can.

I had to read this book for an introductory programming class and didn't find it at all helpful when going on to Java. It wasn't worth the time I spent working with it. You'd be better off just beginning the object-oriented language you're interested in. If you want my advice, try Beginning Java Objects by Jacquie Barker instead.

This book is meant for the earliest of beginning programmers. If you have any programming experience whatsoever, even with macros, the information in this book will seem extrememly remedial. Also, some of the terms used aren't even real C++ code, so you'll have to adjust your thinking just a little when you move on. Finally, the price is pretty steep for the amount of information you get. I would probably only recommend this book for someone needing a very, very, VERY gentle intro to programming.

This book reminds me of the older LOGO programming language. You have a small "robot" that explores his world. You tell him how to move and what to do. The only reason this is good is that it helps you think of object oriented programming. (The robot is considered an object). There are also special editions of the book in case you want to specifically move to C++ or Java later. Basically, the book is a good start. If you have any programming experience - skip it. Otherwise, it will get you in the rate frame of mind to move toward OOP.

With the use of this book and associated software, one can master the C++ or Java language in no time at all! It uses the analagy of a Robot, and the simple classes that operate it. Due to the fact that it has simple classes, time is not wasted trying to remember the many classes and their functions, and the reader immediatly begins programming the Robot. The Karel++ language has the Syntax of C++, and is Object Oriented (just like Java and C++). This is a must buy for anyone getting into programming, or just learning OOP (Object Oriented Programming)!

This book was a delight to read. The author has an engaging style that leads you forward to further discovery. As others have noted, some of the detail is lacking. I don't know if that's necessarily a minus-- a circuit diagram alone leads to further research and discovery; providing a PCB layout and parts list would stymie further research. The projects are very ambitious and, though I might not use the components discussed in my Robosapien, I learned quite a bit about available, inexpensive technologies that I'll enjoy as an electronics enthusiast. I was a bit put off by the author's Mac evangelism, a religion that I respect but don't gravitate towards, but that's a minor quibble. Buy this from a third-party seller at remainder prices and it will be well worth your money. I bought a new copy that came in under a ten spot after shipping. I look forward to checking out some of the author's other books. The alternative Robosapien book makes a better all-in-one guide, but you can get both from third-party sellers for less than the cost of one from A.

On the positive side, Prochnow's candid writing style makes this book very entertaining to read. Most of the projects (but not all) are interesting too including replacing Robosapien's feet with a tank tread based traction system, turning him into an alarm clock or using him as a virtual wall for your roomba. Some seem silly and out-of-place however like the chapter on dressing up Robosapien in paper clothes. On the negative side, the author assumes the reader already possesses a basic working knowledge of electronics and schematic diagrams and as such completion steps for many projects are overly simplistic without the hand holding that most beginners would need.

Why? because I was expectin something else, but first of all, I didn't expect that you have to open/make a hole in your Robosapiens to modify it, so forget it! i will not damage my Robot.

The majority of "The Offical Robosapien Hacker's Guide" is the 11 chapters dedicated to 11 hacks. Some hacks require an additional investment of up to several hundred dollars, while other hacks require small circuits to be built. The author provides circuit diagrams WITHOUT explanations and details of the parts needed, but fails to provide any fundamental Electrical Engineering knowledge. EE 101 students will not have much trouble, but the typical person buying the Robosapien initially as a toy will. My two favorite parts of the book: 1) The $10 WowWee Rebate (expires 12/31/06) towards purchase of a WowWee robot. 2) The chapter dedicated to the disassembly of Robosapien where the author guides you on minimal disassembly for maximum internal exposure. While the author is highly knowledgable in electronics, he is vague and lacks the ability or patience to explain areas in details. The information and presentation of that information is no better than what I would expect to find on someones personal website who was sharing it for fun and not financial gain.

Here are a dozen hacks which you can perform with Robosapien to make it more capable and attractive than it already is: a guide which packs in instructions on how to control your robot with either Mac or PC, and which provides insights into how Robosapien functions and how its uses can be expanded. Robot designer Mark Tilden's interview enhances one of the most in-depth Robosapien references in print.

As an experienced rocketeer (I participated in the TARC competition last year), I cannot recommend this book highly enough!
The 50 projects are very well thought out and clearly stated.
It will take the rocketeer to the next level of their expertise. I especially enjoyed the 70 pages devoted to creating your own flight computer. Not only do these pages show you how to make a simple computer, but also explain how to create even more complex computer systems.
It is true that some of the information can be found free on the internet, but this book provides a well-organized collection of activities that are SAFE and reliable.
As President of my high school Rocketry Club, I am highly suggesting that all my members read this book. 50 Model Rocket Projects is an invaluable resource for anyone who wants to learn rocketry or who knows rocketry but wants to expand their knowledge.

AN EXCELLENT RESOURCE!!!

I am a rocketeer and I have really enjoyed all of the "evil genius" series, so this was a huge disappointment to me. To say this book is for complete rocket beginners is giving it too much credit. This book is not even a good introduction for a rocketeer that has never launched a rocket in their life. There is absolutely nothing about mid or high power rocketry. For instance the only discussion of igniters is on the Estes/ quest type igniter and how to correctly insert them into an Estes rocket motor. The book claims to describe making a hydrogen fuel rocket which is basically filling a plastic pipette with hydrogen and oxygen and igniting it. By the way, you need a tesla coil to ignite the mixture. I'm sure every budding rocketeer has a tesla coil lying around. There is absolutely nothing in this book that can't be found on the internet for free! Do your self a favor, if you are new to rocketry get the Handbook of Model Rocketry (NAR Official Handbook) by Harry Stine. Harry Stine's (father of model rocketry) book has everything this book has and much more. This book assumes you are a child that will hurt yourself and has great advice like never aim rockets at people, or making a rocket engine in irresponsible. I found the other books in the evil genius series challenging and thought provoking. This book is just pretentious and pedantic.

This is an excellent place for the young evil genius to start thinking about rockets - with one exception.

First the exception. The first project is 'Making Black Powder.' DON'T. Black Powder is extremely sensitive. The slightest spark from a buildup of static electricity and you no longer have black powder, just a boom. Too many people have been killed by black powder to play with it. DON't, just DON't. On the next page he starts talking about commercially available rocket engines. Start here.

The book is a combination of descriptive information along with detailed projects. Perhaps the Evil Genius should start with a couple of kit rockets (such as the FREE model rocket you can order), but then this book will move him along to the next step. If nothing else, the armchair rocketeer will find the book to be fascinating reading.

Despite its peculiar title, this book is worthwhile for those who wish to get more out of model rocketry than your average kit-builder. Welcome emphasis is placed on building parts from "scratch" as an alternative to simply buying "off-the-shelf". This approach to the hobby serves as an excellent transitional step from model rocketry to amateur experimental rocketry (AER), for those who later wish to pursue the ultimate in scratch-built rocketry. This book encourages the reader to explore beyond the conventional, through projects such as a self-made wind tunnel, launch controller, rail launcher, rocket cameras, flight computer, apogee sensors and other sensor projects. Details tend to be minimal, although this is likely intentional, leaving the reader to gain more benefits (and rewards) from the projects by using their own resourcefulness. A couple of nice touches to the book are the numerous historical accounts relating to various aspects of rocketry, and the emphasis placed on the importance of math to the rocketry hobby.

The evil genius series of electronic hobbyist books tends to be a mixed bag of quality. Sad to say, this is not one of the better books in the series. It is way too elementary for any adult remotely interested in the science behind the hobby. For example, the chapter on rocket math is junior high school level and the chapter on the flight computer was woefully inadequate. The book is also short on explanations in general, and I found the illustrations to be lacking. If you want a really good book on model rockets, might I suggest the updated version of the "Handbook of Model Rocketry" by Stine and Stine. The senior Stine, G. Harry Stine, was a range safety officer at White Sands Missile Range who built and flew various model rockets in the 1950's and then devised a safety code for the activity based on his experience at the range. The instructions and diagrams are very clear, and the authors go the extra mile with technical details that are missing in Harper's book. The following is the table of contents for the Evil Genius book on rockets:

Chapter 1: History of Rocketry
Chapter 2: Rocket Science
Chapter 3: The Model Rocketeer's Workshop
Chapter 4: Model Rocket Stability
Chapter 5: Constructing Model Rockets
Chapter 6: Recovery Systems
Chapter 7: Launching Model Rockets
Chapter 8: Rocket Math
Chapter 9: Model Rocket Photography
Chapter 10: Model Rocket Movie Cameras
Chapter 11: Rocket Mail
Chapter 12: Introduction to the Flight Computer
Chapter 13: Educating with Model Rocketry
Chapter 14: Model Rocket Clubs
APPENDIX A: MODEL ROCKET SAFETY
APPENDIX B: INTERNATIONAL LISTING OF MODEL ROCKET CLUBS

Putting this kit together is a little bit tricky, but if it was too easy it wouldn't be as much fun. This would make a great gift for a begginer. I just bought another one for my niece.

This is an inexpensive kit. The parts in the kit are simple and low-cost. If you want to spend more on a kit you can buy the "Build Your Own Robot Kit" (available here at Amazon), but it also costs more. If you want to spend the least amount on a decent kit then I recommend the "Inventor's Handbook".

This product is so poorly done, it's hard to imagine that Bobbi Searle, anyone else, actually built this. The instructions are horrible. The material qualilty is abysmal. Even after several modifications and gluing and soldering (which are not supposed to be necesary) to get the thing to hold together, the final straw was that the motor is not powerful enough to operate the robot. I don't know who Bobbi Searle is, but I for one will know what name/author to avoid in the future. ABSOLUTELY DO NOT BUY THIS.

This is a great little kit, especially for youngsters. My son and I played with it for hours and he still loves to play with the little robot. The robot is easy to make but a little adult supervision will go a long way for very young kids. The parts are easy to assemble but it can be a little tricky for very young hands. Playing with the robot is great fun, but we had even more fun just putting the thing together. I would recommend this kit for all kids and even some begginer adults who would like to have a little fun with robots!

I bought this as a gift for my son and we spent the past
several hours building the robot kit that is contained. I
cannot express how disappointed both of us are!

First, the quality of the cardboard chassis and its scoring
was such that it delaminated when folded in compliance with
the construction instructions. Next, an important plastic
bolt in the kit was not long enough (by far) to actually work -
luckily I had a steel bolt in my basement that had the right
diameter and just the right length to actually complete the kit.
Next we encountered several annoying problems related to poor
instructions and impossible electrical connections (they actually
expect a tiny wire on a moving arm to stay in-place in a slit
in a copper sheet just by friction!)

Finally, when we got it all together, the motor was incapable
of propelling the device at over an unsteady snail's pace on
the smoothest of floors with the best of batteries. It was
incapable of any kind of real impact which would be needed to
trip its sensor switch and actually reverse the vehicle.