The latest version of the book is P5.0, released about 6 years ago. If you've bought a PDF of the book and would like to update it to this version (for free), visit your home page.
By default this page displays the errata for the latest version of the book. If you have a previous version, select it here:
If you've found a new error, please submit it.
- Reported in: P5.0 (12-Apr-14)
PDF page: 14
The function definition shows markup tags < and > instead of symbols < and >--James CaisterMaik Schmidt says: Thanks for pointing this out. It'll be fixed in the second edition.
- Reported in: P5.0 (24-Jun-15)
PDF page: 16
- Reported in: P5.0 (06-Jul-14)
PDF page: 20
"Make absolutely sure that you’re using pin 13! If you connect the LED to any other pin, it will probably be destroyed. The reason is that pin 13 has an internal resistor that the other pins don’t have (you’ll learn more about this in Chapter 3, Building Binary Dice,on page 43)."
The above quotation from page 20 (PDF) is incorrect. The last Arduino version to have a series resistor between the microcontroller and pin 13 was the NG. On all newer versions Diecimila, Duemilanove, Uno, etc.) pin 13 is connected directly to the microcontroller. This incorrect explanation is repeated on page 47. (Reference: schematics for all Arduino boards available at arduino.cc) --John Gotthardt
- Reported in: P4.0 (26-Jul-13)
Paper page: 44
The image of the items needed for the "binary dice" project has a 6 in it twice, once for the resistor, and once for the wires. The reason I noticed this, is I was looking for a picture of the (optional) number 9, "tilt sensor", as I am not sure what one looks like.
I am still not sure what it looks like, so please add a link to an image of one would be greatly appreciated.--Jason Zimmer
- Reported in: P4.0 (25-Oct-12)
Paper page: 69
#48837: The phrase "For a binary die" should be "For a binary dice".--Michel Graciano
The above erratum cannot be correct. The text should either be "For binary dice" (plural) or "For a binary die" (singular).
The erratum says that this was corrected in v.4.0.
- Reported in: P5.0 (12-Jun-14)
PDF page: 93
In method Telegraph::output_symbol() at the end of the function there should be a delay(length) so that there is a gap between the output pin going low and the next time it goes high at the start of the next dit or dah. (I found this bug by inspection of the code in the pdf, not through running the code.)--Anon
- Reported in: P1.0 (31-Mar-20)
PDF page: 253
Hi , while the sending data is " 0 1 0 0 1 1 0 1" u r saying sir: " We chose odd parity for our data , and because there are 4 bits set to 1 in 01001101 , the parity bit is 0 " . I think there is a mistake and parity bit should be "1" if we chose it as an odd parity , because when we send the data with parity bit , we have to count 1s in data that has to include parity bit , too in order to control. Here , if we chose odd parity , - while our data is 01001101 -the sending data would be 010011011-we have to choose parity as 1 - , now we can count 1s and it is 5 - including our last bit , parity bit , as well - .--Berat Can