The schematic layout of the MINI in Figure 1-10 shows the OLD MINI but the connection example picture Figur 1-11 shows the NEW MINI with different pins for reset and ground (pins 3 and 4 from above on the left side).

So these Figures do not match wich makes the things a bit difficult.

Please check if I am right and change the Figure 1-10 in the next issues of the book.

Note from the Author or Editor:
Correct. The photo is correct, and shows the new mini. We should use this schematic in Figure 1-10: http://arduino.cc/en/uploads/Main/arduino_mini04_pinout.png

// after a quarter of a second, turn the LED on:

to:

// after a half of a second, turn the LED on:

Thanks to Shigeru Kobayashi for catching this.
-------------

**** CHAPTER TWO ****

// after a quarter of a second, turn the LED on:

to:

// after a half of a second, turn the LED on:

Thanks to Shigeru Kobayashi for catching this.
-------------

**** CHAPTER TWO ****

On page 51, in the Synchronous Serial Communication diagram, the third pin on the master chip is labeled Master Out Slave Out. It should be labeled Master Out Slave In.

On page 51, in the Synchronous Serial Communication diagram, the third pin on the master chip is labeled Master Out Slave Out. It should be labeled Master In Slave Out.
-------------

On page 51, in the Synchronous Serial Communication diagram, the third pin on the master chip is labeled Master Out Slave Out. It should be labeled Master In Slave Out.
-------------

The book says to add a loop in setup() in the Arduino program to send a carriage return every 300 ms. ( Serial.print('\r', BYTE); ). However, the Processing code is set up to do myPort.bufferUntil(linefeed). So a serial event never occurs since the Arduino is sending a carriage return instead of a linefeed. The program just sits there.

I replaced the Arduino line mentioned above with Serial.print(10, BYTE); and now it appears to be working.

(Really enjoying the book, btw!!)

Note from the Author or Editor:
change Serial.print('\r', BYTE); to Serial.print('\n', BYTE);

Ok, so there has been some talk in the errata on the updated RovingNetworks based BlueSmirf module replacing the older version of the module that the book was written for. I found that the default baud rate of the new module is actually 115.2K and not 9600, so the code that references 9600 would then need to change. Also, the default passcode for my module was "1234".

I found the PINCODE (ie, passcode) at http://www.sparkfun.com/datasheets/RF/RN_BlueportII-ref-guide.pdf

The reference to the new baud rate at http://www.lynxmotion.com/images/html/build125.htm (and also talks about different passcodes as well).

I'm not running the Monski program at the moment, but just got a connection going on Windows Vista using Putty at 115.2kbps and after changing my Arduino code to set serial output rate to 115.2 also, so I feel this has been sufficiently confirmed for me.

Note from the Author or Editor:
I need to re-write this section because of Sparkfun's change. See http://www.makingthingstalk.com/chapter2/76/ for a beginning, and Brian, let me know if you want a total re-write or not.

In the paragraph that defines a switch, the last sentence reads, "Objects attached to a hub don't get to see messages that aren't addressed to them." It should read, "Objects attached to a SWITCH don't get to see...."

Hubs blindly pass on all data, whereas switches do not.

Note from the Author or Editor:
Correct, make this change.

Changed: "Between 2 and 4 10-kilohm resistors" to "One 1-kilohm resistor"
Changed: "84N2322" to "58K5001"
-------------

Changed: "Between 2 and 4 10-kilohm resistors" to "One 1-kilohm resistor"
Changed: "84N2322" to "58K5001"
-------------

Added the following note:

You may need a
higher value depending on the
resistance range of your force
sensing resistors and the weight
of your cat. If a 1K resistor
doesn’t give you good values,
try a 4.7K or a 10K resistor.
-------------

Added the following note:

You may need a
higher value depending on the
resistance range of your force
sensing resistors and the weight
of your cat. If a 1K resistor
doesn’t give you good values,
try a 4.7K or a 10K resistor.
-------------

if (prevSensorValue >= threshold) {

To:

if (prevSensorValue > threshold) {

Thanks to Shigeru Kobayashi for catching this.
-------------

**** CHAPTER FOUR ****

if (prevSensorValue >= threshold) {

To:

if (prevSensorValue > threshold) {

Thanks to Shigeru Kobayashi for catching this.
-------------

**** CHAPTER FOUR ****

Please change:

HOST: www.oreillynet.com^M^J^M^^J

To:

HOST: www.oreillynet.com^M^J^M^J

Note from the Author or Editor:
Correct. Make this change.

Please change:

HOST: www.oreillynet.com^M^J^M^^J

To:

HOST: www.oreillynet.com^M^J^M^J

one minute
to:
two minutes
-------------

one minute
to:
two minutes
-------------

one minute
to:
two minutes
-------------

one minute
to:
two minutes
-------------

-------------

-------------

to 'client'.

**** CHAPTER FIVE ****

to 'client'.

**** CHAPTER FIVE ****

to 'To XPort Reset pin'.
-------------

to 'To XPort Reset pin'.
-------------

// if you got anything other than a C, try again:
deviceConnect()

to

// if you got anything other than a C,
// disconnect and let the user re-connect:
status = disconnected;

-------------

// if you got anything other than a C, try again:
deviceConnect()

to

// if you got anything other than a C,
// disconnect and let the user re-connect:
status = disconnected;

-------------

-------------

-------------

The pong server has an error. The delayCounter variable should be a long, not a float, and it should be initialized in the setup() not before. For an update, see http://www.makingthingstalk.com/chapter5/35/

This error is also on pages 167, where the variable should be initialized, and page 389, where the code is copied inthe index.

The pong server code had an error. The delayCounter variable should be a long, not a float, and it should be initialized in the setup() not before. For an update, see http://www.makingthingstalk.com/chapter5/35/
-------------

The pong server code had an error. The delayCounter variable should be a long, not a float, and it should be initialized in the setup() not before. For an update, see http://www.makingthingstalk.com/chapter5/35/
-------------

-------------

-------------

-------------

**** CHAPTER SIX ****

-------------

**** CHAPTER SIX ****

The symbol of TIP120 is incorrect; E (emitter) and C (collector) should be swapped. The photographs of the breadboard layout are correct, however.

Note from the Author or Editor:
Correct. Arrowhead should be on the lower line (the emitter) not the upper line (the collector)

The symbol of TIP120 is incorrect; E (emitter) and C (collector) should be swapped. The photographs of the breadboard layout are correct, however.

Remove "(you set it to 5 using the IT command shown earlier)."

Please change "two XBee radios" to "three XBee radios"

Note from the Author or Editor:
Correct. Make the change.

Please change "two XBee radios" to "three XBee radios"

Change "replacing the println() statement" to "replacing the print() statement".

Note from the Author or Editor:
Correct. Make this change.

Change "replacing the println() statement" to "replacing the print() statement".

Please delete the word geosynchronous.

Note from the Author or Editor:
I couldn't find a reliable source that says they're not, but I found a number of cranky websites that say they're not. So for safety's sake, delete it.

From Makezine.com user Andrew (Note: this may apply to cell signals as well):

Correction to GPS mention
There's a bit of an error in the way the first paragraph explains how GPS works.

GPS doesn't determine position by measuring signal strength and using rules about signal strength over distance. GPS calculates the distances to the satellites by using the travel time of the signal from satellite to receiver and the speed of light, and then triangulates in the _four_ dimensions of space-time.

This requires insanely accurate clocks, compensations for inaccuracies they can't control, corrections for relativistic effects from the speed the satellites are going (slows their clocks, an effect of special relativity) and their higher position in the gravity well of earth (speeds up their clocks, an effect of general relativity), and average ionospheric delay of the signal.

Still the same base principle to determine position - get distances and triangulate - but it uses a different method to get the distances than is described.

Note from the Author or Editor:
Change paragraph 2 to read:

"For example, a GPS receiver determines its position on
the surface of the planet by measuring the travel time of the
received radio signals from several satellites.
Similarly, mobile phone location systems measure
the signal strength of the phone at several cell towers.
Sonar and infrared ranging sensors work by sending out
an acoustic signal (sonar) or an infrared signal (IR rangers)
and measuring the strength of that signal when it’s
reflected off the target."

Please delete the word geosynchronous.

In some cases, you may get a value that is three or below. Three will cause a divide by 0 error, and values below three will give a negative result. So you may want to change these lines:

int range = (6787 / (sensorValue - 3)) - 4;

Serial.println(range, DEC); // print the sensor value
delay(10); // wait 10 milliseconds
// before the next loop

to:

if (sensorValue> 3) {

int range = (6787 / (sensorValue - 3)) - 4;

Serial.println(range, DEC); // print the sensor value
delay(10); // wait 10 milliseconds
// before the next loop
}

Note that this example also appears on page 403.

Note from the Author or Editor:
Correct. Make this change in both locations.

-------------

int range = (6787 / (sensorValue - 3)) - 4;
Serial.println(range, DEC); // print the sensor value
delay(10); // wait 10 milliseconds
// before the next loop

to:

if (sensorValue> 3) {
int range = (6787 / (sensorValue - 3)) - 4;
Serial.println(range, DEC); // print the sensor value
delay(10); // wait 10 milliseconds
// before the next loop
}
-------------

-------------

int range = (6787 / (sensorValue - 3)) - 4;
Serial.println(range, DEC); // print the sensor value
delay(10); // wait 10 milliseconds
// before the next loop

to:

if (sensorValue> 3) {
int range = (6787 / (sensorValue - 3)) - 4;
Serial.println(range, DEC); // print the sensor value
delay(10); // wait 10 milliseconds
// before the next loop
}
-------------

The figure 8-2 specifies a 100 uF capacitor but the parts list specifies a 10 uF capacitor. Might not create a major problem aside from confusion (10 uF is probably right)

Note from the Author or Editor:
Correct. Change both to 10uF

Please change:

relationship between signal strength and distance would be a logarithmic curve.

to:

relationship between signal strength and distance would be an inverse-square curve.

Note from the Author or Editor:
Correct, make the change.

Please change:

relationship between signal strength and distance would be a logarithmic curve.

to:

relationship between signal strength and distance would be an inverse-square curve.

PDF book line: myCamera = new Capture(this, myCam, width, height, 30);

should be in constructor format

Capture(parent, width, height)
Capture(parent, width, height, fps)
Capture(parent, width, height, name, )
Capture(parent, width, height, name, fps)

correct line: myCamera = new Capture(this, width, height, myCam ,30);

Note from the Author or Editor:
Correct. Change

myCamera = new Capture(this, myCam, width, height, 30);

to

new Capture(this, width, height, myCam ,30);


I submitted this correction before, but apparently it did not go through.

Please change:

Call it env.php:

To:

Call it 09_env.php:

Note from the Author or Editor:
Shouldn't be called that. We don't use the numbers for names elsewhere in the text. But we should edit the output on page 327. Anywhere that reads "09_env.php", change to "env.php".

Please change:

Call it env.php:

To:

Call it 09_env.php:

Change "LD1117-V33" to "LD1117-33V".

Note from the Author or Editor:
Correct. Make this change.

Change "LD1117-V33" to "LD1117-33V".

Change the code from:

for (note = 0; note < 127; note ++) {

to:

for (note =30; note <= 90, note++) {

Note from the Author or Editor:
Correct, please make this change

Please change 0x45 to 0x70

Note from the Author or Editor:
Correct, please make this change

Remove the connection between pin 5 of the MIDI jack and the RX pin of the Arduino. Replace it with a connection from pin 5 of the MIDI jack to the Arduino TX pin.

Note from the Author or Editor:
Correct, we should make this change. But this change has been reported before.

Please change "less than 127" to "less than 128"

Note from the Author or Editor:
Correct, please make this change

Please change:
if (myString != null) {
sensorValue = int(trim(myString));
drawGraph(); // call this method instead of println()
}

to:

if (myString != null) {
// get the sensor value. You may need to change the
// formula to scale for your own sensors:
sensorValue = int(trim(myString)) / 2 - 100;
// println(sensorValue);
drawGraph(); // call this method instead of println()
}

Note from the Author or Editor:
Change to

if (myString != null) {
// get the sensor value. You may need to change the
// formula to scale for your own sensors:
sensorValue = int(trim(myString));
// println(sensorValue);
drawGraph(); // call this method instead of println()
}

The code listing here was not complete for the AIRNow web page scraper. For the full listing, see http://www.makingthingstalk.com/look-ma-no-computer/42/
-------------

The code listing here was not complete for the AIRNow web page scraper. For the full listing, see http://www.makingthingstalk.com/look-ma-no-computer/42/
-------------

The code listing here is not complete for the AIRNow web page scraper. For the full listing, see http://www.makingthingstalk.com/look-ma-no-computer/42/

// if you got anything other than a C, try again:
deviceConnect()
to
// if you got anything other than a C,
// disconnect and let the user re-connect:
status = disconnected;
-------------

The pong server code had an error. The delayCounter variable should be a long, not a float, and it should be initialized in the setup() not before. For an update, see http://www.makingthingstalk.com/chapter5/35/
-------------

// if you got anything other than a C, try again:
deviceConnect()
to
// if you got anything other than a C,
// disconnect and let the user re-connect:
status = disconnected;
-------------

The pong server code had an error. The delayCounter variable should be a long, not a float, and it should be initialized in the setup() not before. For an update, see http://www.makingthingstalk.com/chapter5/35/
-------------

int range = (6787 / (sensorValue - 3)) - 4;
Serial.println(range, DEC); // print the sensor value
delay(10); // wait 10 milliseconds
// before the next loop

to:

if (sensorValue> 3) {
int range = (6787 / (sensorValue - 3)) - 4;
Serial.println(range, DEC); // print the sensor value
delay(10); // wait 10 milliseconds
// before the next loop
}
-------------

int range = (6787 / (sensorValue - 3)) - 4;
Serial.println(range, DEC); // print the sensor value
delay(10); // wait 10 milliseconds
// before the next loop

to:

if (sensorValue> 3) {
int range = (6787 / (sensorValue - 3)) - 4;
Serial.println(range, DEC); // print the sensor value
delay(10); // wait 10 milliseconds
// before the next loop
}
-------------