Main.ArduinoXbeeShield History

Hide minor edits - Show changes to markup

June 04, 2010, at 11:48 AM by Equipo Traduccion -
Changed lines 51-53 from:
to:
Changed line 55 from:
to:
Changed line 65 from:
to:
June 04, 2010, at 11:42 AM by Equipo Traduccion -
June 04, 2010, at 11:42 AM by Equipo Traduccion -
Changed lines 70-71 from:

Here are a couple more useful commands for configuring the Xbee module (you'll need to prepend AT to these too).

to:

Aquí hay unos cuantos comandos útiles más para configurar el módulo Xbee (necesitarás anteponer AT a estos también).

Changed lines 73-74 from:
to:
Changed line 78 from:
to:
Changed line 82 from:
to:
Changed line 86 from:
to:
Changed lines 92-93 from:

For more details on configuring the Xbee module, see the product manual from MaxStream.

to:

Para más detalles sobre configurar el módulo Xbee, ver el manual de producto de MaxStream.

June 04, 2010, at 11:36 AM by Equipo Traduccion -
Changed lines 31-37 from:

De nuevo, este Again, this address matching will only happen between modules on the same network and channel. If two modules are on different networks or channels, they can't communicate regardless of their addresses.

Configuration

Here are some of the more useful parameters for configuring your Xbee module. For step-by-step instructions on reading and writing them, see the guide to the Xbee shield. Make sure to prepend AT to the parameter name when sending a command to the module (e.g. to read the ID parameter, you should send the command ATID).

to:

De nuevo, esta correspondencia de direcciones solo sucederá entre módulos en la misma red y canal. Si dos módulos están en diferentes redes o canales, no podrán comunicarse sea cual sea sus direcciones.

Configuración

Aquí hay algunos de los parámetros más útiles para configurar tu módulo Xbee. Para unas instrucciones paso-a-paso sobre leerlas y escribirlas, ver la guía para la Xbee shield. Asegúrate de poner AT delante de cada nombre de parámetro cuando envíes un comando a el módulo (e.g. para leer el parámetro ID, deberías enviar ATID).

Changed lines 38-41 from:
to:
Changed line 43 from:
to:
Changed line 47 from:
to:
Changed line 50 from:
to:
Changed lines 58-61 from:
to:
Changed line 63 from:
to:
Changed lines 68-69 from:

Note: although the valid and default values in the table above are written with a prefix of "0x" (to indicate that they are hexadecimal numbers), the module will not include the "0x" when reporting the value of a parameter, and you should omit it when setting values.

to:

Nota: a pesar de que los valores por defecto y válidos de arriba están escritos con el prefijo "0x" (para indicar que son números decimales), el módulo no incluye el "0x" cuando reporta el valor de un parámetro, y tu debes omitirlo cuando establezcas valores.

June 04, 2010, at 11:22 AM by Equipo Traduccion -
Changed lines 28-31 from:
  • If a module's DH is 0 and its DL is less than 0xFFFF (i.e. 16 bits), data transmitted by that module will be received by any module whose 16-bit address MY parameter equals DL.
  • If DH is 0 and DL equals 0xFFFF, the module's transmissions will be received by all modules.
  • If DH is non-zero or DL is greater than 0xFFFF, the transmission will only be received by the module whose serial number equals the transmitting module's destination address (i.e. whose SH equals the transmitting module's DH and whose SL equals its DL).
to:
  • Si el DH de un módulo es 0 y su DL es menor de 0xFFF (e.g. 16 bits), los datos transmitidos por ese módulo serán recibidos por cualquier módulo cuyos 16 bits de dirección del parámetro MY sea igual al DL.
  • Si el DH es 0 y el DL es igual a 0xFFFF, las transmisiones del módulo serán recibidas por todos los módulos.
  • Si el DH no es cero o el DL es mayor de 0xFFFF, la transmisión solo será recibida por el módulo cuyo número de serie sea igual a la dirección de destino del módulo transmisor (e.g. cuyos SH es igual al DH del módulo transmisor y cuyo SL sea igual a su DL).

De nuevo, este

June 04, 2010, at 11:16 AM by Equipo Traduccion -
Changed line 28 from:

There are multiple parameters that need to be configured correctly for two modules to talk to each other (although with the default settings, all modules should be able to talk to each other). They need to be on the same network, as set by the ID parameter (see "Configuration" below for more details on the parameters). The modules need to be on the same channel, as set by the CH parameter. Finally, a module's destination address (DH and DL parameters) determine which modules on its network and channel will receive the data it transmits. This can happen in a few ways:

to:
June 04, 2010, at 11:16 AM by Equipo Traduccion -
Changed lines 3-26 from:

Overview

The Xbee shield allows an Arduino board to communicate wirelessly using Zigbee. It is based on the Xbee module from MaxStream. The module can communicate up to 100 feet indoors or 300 feet outdoors (with line-of-sight). It can be used as a serial/usb replacement or you can put it into a command mode and configure it for a variety of broadcast and mesh networking options. The shields breaks out each of the Xbee's pins to a through-hole solder pad. It also provides female pin headers for use of digital pins 2 to 7 and the analog inputs, which are covered by the shield (digital pins 8 to 13 are not obstructed by the shield, so you can use the headers on the board itself).

The Xbee shield was created in collaboration with Libelium, who developed it for use in their SquidBee motes (used for creating sensor networks).

Schematic

XbeeShieldSchematic.pdf (Eagle schematics and board layouts available from the Libelium SquidBee wiki download page.)

Jumper Settings

The Xbee shield has two jumpers (the small removable plastic sleeves that each fit onto two of the three pins labelled Xbee/USB). These determine how the Xbee's serial communication connects to the serial communication between the microcontroller (ATmega8 or ATmega168) and FTDI USB-to-serial chip on the Arduino board.

With the jumpers in the Xbee position (i.e. on the two pins towards the interior of the board), the DOUT pin of the Xbee module is connected to the RX pin of the microcontroller; and DIN is connected to TX. Note that the RX and TX pins of the microcontroller are still connected to the TX and RX pins (respectively) of the FTDI chip - data sent from the microcontroller will be transmitted to the computer via USB as well as being sent wirelessly by the Xbee module. The microcontroller, however, will only be able to receive data from the Xbee module, not over USB from the computer.

With the jumpers in the USB position (i.e. on the two pins nearest the edge of the board), the DOUT pin the Xbee module is connected to the RX pin of the FTDI chip, and DIN on the Xbee module is connected to the TX pin of the FTDI chip. This means that the Xbee module can communicate directly with the computer - however, this only works if the microcontroller has been removed from the Arduino board. If the microcontroller is left in the Arduino board, it will be able to talk to the computer normally via USB, but neither the computer nor the microcontroller will be able to talk to the Xbee module.

Networking

The Arduino XBee shield can be used with different XBee modules. The instructions below are for the XBee 802.15.4 modules.

Addressing

to:

Introducción

La Xbee shield permite a una placa Arduino comunicarse de forma inalámbrica usando Zigbee. Está basada en el módulo Xbee de MaxStream. El módulo puede comunicarse hasta 100ft (30 metros) en interior o 300ft (90 metros) al aire libre (en visión directa). Puede ser usado como reemplazo del puerto serie/usb o puedes ponerlo en modo de comandos y configurarlo para una variedad de opciones de redes broadcast o malladas. La shield tiene pistas desde cada pin del Xbee hasta un orificio de soldar. También provee conectores hembra para usar los pines digitales desde 2 hasta 7 y las entradas analógicas, las cuales están cubiertas por la shield (los pines digitales de 8 a 13 no están cubiertos por la placa, así que puedes usar los conectores de la placa directamente).

La Xbee shiel fue creada en colaboración con Libelium, quienes la desarrollaron para usarlo en sus SquidBee motes (usados para crear redes de sensores).

Esquema

XbeeShieldSchematic.pdf (los esquemas Eagle de la placa están disponibles en la página de descarga de la wiki de SquidBee de Libelium.)

Configuración de los jumpers

La Xbee shield tiene dos jumpers (las pequeñas fundas de plásticos que están sobre los tres pines etiquetados como Xbee/USB). Estos determinan como se conecta la comunicación serie del Xbee entre el microcontrolador (Atmega8 o ATmega168) y el chip serie FTDI de la placa Arduino.

Con los jumpers en la posición Xbee (e.g. en los dos pines más cercanos al interior de la placa), el pin DOUT de el módulo Xbee está conectado al pin RX del microcontrolador; y el pin DIN está conectado a TX. Notar que los pines RX y TX del microcontrolador están todavía conectados a los pines TX y RX (respectivamente) del chip FTDI - los datos enviados desde el microcontrolador serán transmitidos al ordenador vía USB y a la vez enviados de forma inalámbrica por el módulo Xbee. El microcontrolador, sin embargo, solo será capaz de recibir datos desde el módulo Xbee, no desde el USB del ordenador.

Con los jumpers en la posición USB (e.g. en los dos pines más cercanos al borde de la placa), el pin DOUT del módulo Xbee está conectado al pin RX del pin del chip FTDI, y el DIN del módulo Xbee está conectado al pin TX del el chip FTDI. Esto significa que el módulo Xbee puede comunicarse directamente con el ordenador - sin embargo, esto solo funciona si el microcontrolador ha sido quitado de la placa Arduino. Si el microcontrolador se deja en la placa Arduino, solo será capaz de comunicarse con el ordenador vía USB, pero ni el ordenador ni el microcontrolador podrán comunicarse con el módulo Xbee.

Redes

La Arduino XBee shield puede ser usada con diferentes módulos XBee. Las instrucciones a continuación son para los módulos XBee 802.15.4.

Direccionamiento

Hay múltiples parámetros que necesitan ser configurados correctamente para que dos módulos puedan comunicarse entre ellos (de todos modos con la configuración por defecto, todos los módulos deberían ser capaces de hablar unos con otros). Necesitan estar en la misma red, definida por el parámetro ID (ver "Configuración" a continuación para más detalles sobre los parámetros). Los módulos necesitan estar en el mismo canal, definido por el parámetro CH. Finalmente, la dirección de destino de un módulo (parámetros DH y DL) determina que módulo en esa red y canal recibirá los datos transmitidos. Esto puede suceder de las siguientes formas:

August 15, 2009, at 01:55 PM by David A. Mellis -
Changed lines 23-24 from:

The Arduino XBee shield can be used with different XBee modules. The instructions below are for the XBee 802.15.4 modules.

to:

The Arduino XBee shield can be used with different XBee modules. The instructions below are for the XBee 802.15.4 modules.

August 15, 2009, at 01:54 PM by David A. Mellis -
Changed lines 21-22 from:

Addressing

to:

Networking

The Arduino XBee shield can be used with different XBee modules. The instructions below are for the XBee 802.15.4 modules.

Addressing

Changed lines 33-34 from:

Configuration

to:

Configuration

Changed lines 92-93 from:

For more details on configuring the Xbee module, see the product manual from MaxStream.

to:

For more details on configuring the Xbee module, see the product manual from MaxStream.

August 16, 2007, at 12:45 AM by David A. Mellis -
Deleted lines 2-5:

Schematic

XbeeShieldSchematic.pdf (Eagle schematics and board layouts available from the Libelium SquidBee wiki download page.)

Added lines 9-12:

Schematic

XbeeShieldSchematic.pdf (Eagle schematics and board layouts available from the Libelium SquidBee wiki download page.)

August 16, 2007, at 12:44 AM by David A. Mellis -
Added lines 11-12:

The Xbee shield was created in collaboration with Libelium, who developed it for use in their SquidBee motes (used for creating sensor networks).

August 16, 2007, at 12:35 AM by David A. Mellis -
Changed lines 5-6 from:

XbeeShieldSchematic.pdf

to:

XbeeShieldSchematic.pdf (Eagle schematics and board layouts available from the Libelium SquidBee wiki download page.)

August 16, 2007, at 12:27 AM by David A. Mellis -
Changed line 72 from:
to:
August 16, 2007, at 12:27 AM by David A. Mellis -
Added lines 71-74:
August 16, 2007, at 12:26 AM by David A. Mellis -
Changed lines 79-80 from:
to:
August 16, 2007, at 12:25 AM by David A. Mellis -
Added lines 64-80:
August 16, 2007, at 12:17 AM by David A. Mellis -
Changed lines 5-6 from:
to:

XbeeShieldSchematic.pdf

August 16, 2007, at 12:16 AM by David A. Mellis -
Changed lines 5-6 from:

XbeeShieldSchematic.jpg

to:
August 16, 2007, at 12:14 AM by David A. Mellis -
Added lines 62-63:

Note: although the valid and default values in the table above are written with a prefix of "0x" (to indicate that they are hexadecimal numbers), the module will not include the "0x" when reporting the value of a parameter, and you should omit it when setting values.

August 16, 2007, at 12:12 AM by David A. Mellis -
Changed lines 40-43 from:
to:
Added lines 56-59:
August 16, 2007, at 12:11 AM by David A. Mellis -
Changed line 21 from:

There are multiple parameters that need to be configured correctly for two modules to talk to each other (although with the default settings, all modules should be able to talk to each other). They need to be on the same network, as set by the ID parameter (see "Configuration" below for more details on the parameters). They need to be on the same channel, as set by the CH parameter. Finally, a module's destination address (DH and DL parameters) determine which modules on its network and channel will receive the data it transmits. This can happen in a few ways:

to:

There are multiple parameters that need to be configured correctly for two modules to talk to each other (although with the default settings, all modules should be able to talk to each other). They need to be on the same network, as set by the ID parameter (see "Configuration" below for more details on the parameters). The modules need to be on the same channel, as set by the CH parameter. Finally, a module's destination address (DH and DL parameters) determine which modules on its network and channel will receive the data it transmits. This can happen in a few ways:

August 16, 2007, at 12:10 AM by David A. Mellis -
Changed line 21 from:

There are multiple parameters that need to be configured correctly for two modules to talk to each other (although with the default settings, all modules should be able to talk to each other). They need to be on the same network, as set by the ID parameter. They need to be on the same channel, as set by the CH parameter. Finally, a module's destination address (DH and DL parameters) determine which modules on its network and channel will receive the data it transmits. This can happen in a few ways:

to:

There are multiple parameters that need to be configured correctly for two modules to talk to each other (although with the default settings, all modules should be able to talk to each other). They need to be on the same network, as set by the ID parameter (see "Configuration" below for more details on the parameters). They need to be on the same channel, as set by the CH parameter. Finally, a module's destination address (DH and DL parameters) determine which modules on its network and channel will receive the data it transmits. This can happen in a few ways:

August 16, 2007, at 12:05 AM by David A. Mellis -
Changed line 37 from:
to:
Changed line 53 from:
to:
August 15, 2007, at 11:58 PM by David A. Mellis -
Changed lines 9-10 from:

The Xbee shield allows an Arduino board to communicate wirelessly using Zigbee. It is based on the Xbee module from MaxStream. The module can communicate up to 100 feet indoors or 300 feet outdoors (with line-of-sight). It can be used as a serial/usb replacement or you can put it into a command mode and configure it for a variety of broadcast and mesh networking options. The shield also provides female pin headers for easy use of digital pins 2 to 7 and the analog inputs (digital pins 8 to 13 are not covered by the shield).

to:

The Xbee shield allows an Arduino board to communicate wirelessly using Zigbee. It is based on the Xbee module from MaxStream. The module can communicate up to 100 feet indoors or 300 feet outdoors (with line-of-sight). It can be used as a serial/usb replacement or you can put it into a command mode and configure it for a variety of broadcast and mesh networking options. The shields breaks out each of the Xbee's pins to a through-hole solder pad. It also provides female pin headers for use of digital pins 2 to 7 and the analog inputs, which are covered by the shield (digital pins 8 to 13 are not obstructed by the shield, so you can use the headers on the board itself).

August 15, 2007, at 11:56 PM by David A. Mellis -
Changed lines 9-10 from:

The Xbee shield allows an Arduino board to communicate wirelessly using Zigbee. It is based on the Xbee module from MaxStream. The module can communicate up to 100 feet indoors or 300 feet outdoors (with line-of-sight). It can be used as a serial/usb replacement or you can put it into a command mode and configure it for a variety of broadcast and mesh networking options.

to:

The Xbee shield allows an Arduino board to communicate wirelessly using Zigbee. It is based on the Xbee module from MaxStream. The module can communicate up to 100 feet indoors or 300 feet outdoors (with line-of-sight). It can be used as a serial/usb replacement or you can put it into a command mode and configure it for a variety of broadcast and mesh networking options. The shield also provides female pin headers for easy use of digital pins 2 to 7 and the analog inputs (digital pins 8 to 13 are not covered by the shield).

August 15, 2007, at 11:55 PM by David A. Mellis -
Changed line 21 from:

There are multiple parameters that need to be configured correctly for two modules to talk to each other (although with the default settings, all modules should be able to talk to each other). They need to be on the same network, as set by the ID parameter. They need to be on the same channel, as set by the CH parameter. Finally, a module's destination address (DH and DL parameters) determine which modules will receive the data it transmits. This can happen in a few ways:

to:

There are multiple parameters that need to be configured correctly for two modules to talk to each other (although with the default settings, all modules should be able to talk to each other). They need to be on the same network, as set by the ID parameter. They need to be on the same channel, as set by the CH parameter. Finally, a module's destination address (DH and DL parameters) determine which modules on its network and channel will receive the data it transmits. This can happen in a few ways:

Changed line 23 from:
  • If DH is 0 and DL equals 0xFFFF, the module's transmissions will be received by all modules on the same network and channel.
to:
  • If DH is 0 and DL equals 0xFFFF, the module's transmissions will be received by all modules.
Changed lines 25-26 from:
to:

Again, this address matching will only happen between modules on the same network and channel. If two modules are on different networks or channels, they can't communicate regardless of their addresses.

August 15, 2007, at 11:42 PM by David A. Mellis -
Changed lines 21-22 from:

There are multiple parameters that need to be configured correctly for two modules to talk to each other (although with the default settings, all modules should be able to talk to each other). They need to be on the same network, as set by the ID parameter. They need to be on the same channel, as set by the CH parameter. Finally, a module's destination address (DH and DL parameters) determine which modules will receive the data it transmits. This can happen in a couple of ways. If a module's DH is 0 and its DL is less than 0xFFFF (i.e. 16 bits), data transmitted by that module will be received by any module whose 16-bit address MY parameter equals DL. If DH is 0 and DL equals 0xFFFF, the module's transmissions will be received by all modules on the same network and channel. If DH is non-zero or DL is greater than 0xFFFF, the transmission will only be received by the module whose serial number equals the transmitting module's destination address (i.e. whose SH equals the transmitting module's DH and whose SL equals its DL).

to:

There are multiple parameters that need to be configured correctly for two modules to talk to each other (although with the default settings, all modules should be able to talk to each other). They need to be on the same network, as set by the ID parameter. They need to be on the same channel, as set by the CH parameter. Finally, a module's destination address (DH and DL parameters) determine which modules will receive the data it transmits. This can happen in a few ways:

  • If a module's DH is 0 and its DL is less than 0xFFFF (i.e. 16 bits), data transmitted by that module will be received by any module whose 16-bit address MY parameter equals DL.
  • If DH is 0 and DL equals 0xFFFF, the module's transmissions will be received by all modules on the same network and channel.
  • If DH is non-zero or DL is greater than 0xFFFF, the transmission will only be received by the module whose serial number equals the transmitting module's destination address (i.e. whose SH equals the transmitting module's DH and whose SL equals its DL).
August 15, 2007, at 11:41 PM by David A. Mellis -
Changed lines 21-22 from:

There are multiple parameters that need to be configured correctly for two modules to talk to each other (although with the default settings, all modules should be able to talk to each other). They need to be on the same network, as set by the ID parameter. They need to be on the same channel, as set by the CH parameter. Finally, a module's destination address (DH and DL parameters) determine which modules will receive the data it transmits. This can happen in a couple of ways. If a module's DH is 0 and its DL is less than 0xFFFF (i.e. 16 bits), data transmitted by that module will be received by any module whose 16-bit address MY parameter equals DL. If DH is 0 and DL equals 0xFFFF, the module's transmissions will be received by all modules on the same network and channel. If DH is non-zero or DL is greater than 0xFFFF, the transmission will only be received by the module whose serial number equals the transmitting module's destination address (i.e. whose SH equals the transmitting module's DH and whose SL"' equals its DL''').

to:

There are multiple parameters that need to be configured correctly for two modules to talk to each other (although with the default settings, all modules should be able to talk to each other). They need to be on the same network, as set by the ID parameter. They need to be on the same channel, as set by the CH parameter. Finally, a module's destination address (DH and DL parameters) determine which modules will receive the data it transmits. This can happen in a couple of ways. If a module's DH is 0 and its DL is less than 0xFFFF (i.e. 16 bits), data transmitted by that module will be received by any module whose 16-bit address MY parameter equals DL. If DH is 0 and DL equals 0xFFFF, the module's transmissions will be received by all modules on the same network and channel. If DH is non-zero or DL is greater than 0xFFFF, the transmission will only be received by the module whose serial number equals the transmitting module's destination address (i.e. whose SH equals the transmitting module's DH and whose SL equals its DL).

August 15, 2007, at 11:41 PM by David A. Mellis -
Changed lines 21-22 from:

There are multiple parameters that need to be configured correctly for two modules to talk to each other (although with the default settings, all modules should be able to talk to each other). They need to be on the same network, as set by the ID parameter. They need to be on the same channel, as set by the CH parameter. Finally, a module's destination address (DH and DL parameters) determine which modules will receive the data it transmits. This can happen in a couple of ways. If a module's DH is 0 and its DL is less than 0xFFFF (i.e. 16 bits), data transmitted by that module will be received by any module whose 16-bit address MY parameter equals DL. If DH is 0 and DL equals 0xFFFF, the module's transmissions will be received by all modules on the same network and channel. If DH is non-zero or DL is greater than 0xFFFF, the transmission will only be received by the module whose serial number equals the transmitting module's destination address (i.e. whose SH equals the transmitting module's DH and whose SL" equals its DL').

to:

There are multiple parameters that need to be configured correctly for two modules to talk to each other (although with the default settings, all modules should be able to talk to each other). They need to be on the same network, as set by the ID parameter. They need to be on the same channel, as set by the CH parameter. Finally, a module's destination address (DH and DL parameters) determine which modules will receive the data it transmits. This can happen in a couple of ways. If a module's DH is 0 and its DL is less than 0xFFFF (i.e. 16 bits), data transmitted by that module will be received by any module whose 16-bit address MY parameter equals DL. If DH is 0 and DL equals 0xFFFF, the module's transmissions will be received by all modules on the same network and channel. If DH is non-zero or DL is greater than 0xFFFF, the transmission will only be received by the module whose serial number equals the transmitting module's destination address (i.e. whose SH equals the transmitting module's DH and whose SL"' equals its DL''').

August 15, 2007, at 11:39 PM by David A. Mellis -
Changed lines 21-22 from:

There are multiple parameters that need to be configured correctly for two modules to talk to each other (although with the default settings, all modules should be able to talk to each other). They need to be on the same network, as set by the ID parameter. They need to be on the same channel, as set by the CH parameter. Finally, a module's destination address (DH and DL parameters) determine which modules will receive the data it transmits.

to:

There are multiple parameters that need to be configured correctly for two modules to talk to each other (although with the default settings, all modules should be able to talk to each other). They need to be on the same network, as set by the ID parameter. They need to be on the same channel, as set by the CH parameter. Finally, a module's destination address (DH and DL parameters) determine which modules will receive the data it transmits. This can happen in a couple of ways. If a module's DH is 0 and its DL is less than 0xFFFF (i.e. 16 bits), data transmitted by that module will be received by any module whose 16-bit address MY parameter equals DL. If DH is 0 and DL equals 0xFFFF, the module's transmissions will be received by all modules on the same network and channel. If DH is non-zero or DL is greater than 0xFFFF, the transmission will only be received by the module whose serial number equals the transmitting module's destination address (i.e. whose SH equals the transmitting module's DH and whose SL" equals its DL').

August 15, 2007, at 11:32 PM by David A. Mellis -
Added lines 19-22:

Addressing

There are multiple parameters that need to be configured correctly for two modules to talk to each other (although with the default settings, all modules should be able to talk to each other). They need to be on the same network, as set by the ID parameter. They need to be on the same channel, as set by the CH parameter. Finally, a module's destination address (DH and DL parameters) determine which modules will receive the data it transmits.

Changed lines 25-26 from:

Here are some of the more useful commands for configuring your Xbee module. For step-by-step instructions on using these commands, see the guide to the Xbee shield. When you use these commands, prepend AT to them (e.g. to use the ID command, you should type ATID).

to:

Here are some of the more useful parameters for configuring your Xbee module. For step-by-step instructions on reading and writing them, see the guide to the Xbee shield. Make sure to prepend AT to the parameter name when sending a command to the module (e.g. to read the ID parameter, you should send the command ATID).

August 15, 2007, at 11:14 PM by David A. Mellis -
Changed line 39 from:
to:
August 15, 2007, at 11:13 PM by David A. Mellis -
Changed line 34 from:
to:
August 15, 2007, at 11:07 PM by David A. Mellis -
Changed line 39 from:
to:
August 15, 2007, at 11:06 PM by David A. Mellis -
Changed line 45 from:
to:
August 15, 2007, at 11:06 PM by David A. Mellis -
Changed line 45 from:
to:
August 15, 2007, at 11:04 PM by David A. Mellis -
Changed line 45 from:
to:
August 15, 2007, at 11:02 PM by David A. Mellis -
Changed line 45 from:
to:
August 15, 2007, at 11:00 PM by David A. Mellis -
Changed lines 46-47 from:
to:
August 15, 2007, at 10:57 PM by David A. Mellis -
Changed line 41 from:
to:
August 15, 2007, at 10:55 PM by David A. Mellis -
Changed line 30 from:
to:
Changed line 38 from:
to:
Added lines 40-43:
August 15, 2007, at 10:52 PM by David A. Mellis -
Changed line 38 from:
to:
August 15, 2007, at 10:51 PM by David A. Mellis -
Added line 38:
Deleted line 39:
August 15, 2007, at 10:49 PM by David A. Mellis -
Changed line 41 from:
to:
August 15, 2007, at 10:45 PM by David A. Mellis -
Changed line 37 from:
to:
Added lines 40-43:
August 15, 2007, at 10:31 PM by David A. Mellis -
Changed line 36 from:
to:
August 15, 2007, at 10:29 PM by David A. Mellis -
Added lines 36-39:
August 15, 2007, at 09:43 PM by David A. Mellis -
Changed lines 26-27 from:
to:
Changed line 31 from:
to:
August 15, 2007, at 09:42 PM by David A. Mellis -
Changed lines 36-37 from:
to:
August 15, 2007, at 09:42 PM by David A. Mellis -
Changed lines 23-26 from:
CommandDescriptionValid ValuesDefault Value
IDThe network ID of the Xbee module. In most cases, a module will communicate with other modules that share the same network ID.0 - FFFF3332
BDThe baud rate used for serial communication with the Arduino board or computer.0 = 1200 bps
1 = 2400
2 = 4800
3 = 9600
4 = 19200
5 = 38400
6 = 57600
7 = 115200
3 (9600 baud)
to:
August 15, 2007, at 09:40 PM by David A. Mellis -
Changed lines 25-26 from:
BDThe baud rate used for serial communication with the Arduino board or computer.0 = 1200 bps
1 = 2400
2 = 4800 \\ 3 = 9600 \\ 4 = 19200 \\ 5 = 38400 \\ 6 = 57600 \\ 7 = 115200
3 (9600 baud)
to:
BDThe baud rate used for serial communication with the Arduino board or computer.0 = 1200 bps
1 = 2400
2 = 4800
3 = 9600
4 = 19200
5 = 38400
6 = 57600
7 = 115200
3 (9600 baud)
August 15, 2007, at 09:40 PM by David A. Mellis -
August 15, 2007, at 09:40 PM by David A. Mellis -
Changed lines 21-22 from:

Here are some of the more useful commands for configuring your Xbee module. For step-by-step instructions on using these commands, see the guide to the Xbee shield. When you use these commands, prepend AT to them (e.g. to
use the ID command, you should type ATID).

to:

Here are some of the more useful commands for configuring your Xbee module. For step-by-step instructions on using these commands, see the guide to the Xbee shield. When you use these commands, prepend AT to them (e.g. to use the ID command, you should type ATID).

Changed lines 25-26 from:
BDThe baud rate used for serial communication with the Arduino board or computer.0 = 1200 bps >>? 1 = 2400 \\ 2 = 4800 \\ 3 = 9600 \\ 4 = 19200 \\ 5 = 38400 \\ 6 = 57600 \\ 7 = 1152003 (9600 baud)
to:
BDThe baud rate used for serial communication with the Arduino board or computer.0 = 1200 bps
1 = 2400
2 = 4800 \\ 3 = 9600 \\ 4 = 19200 \\ 5 = 38400 \\ 6 = 57600 \\ 7 = 115200
3 (9600 baud)
August 15, 2007, at 09:39 PM by David A. Mellis -
Changed lines 21-22 from:

Here are some of the more useful commands for configuring your Xbee module. For step-by-step instructions on using these commands, see the guide to the Xbee shield. When you use these commands, prepend AT to them (e.g. to use the ID command, you should type ATID).

to:

Here are some of the more useful commands for configuring your Xbee module. For step-by-step instructions on using these commands, see the guide to the Xbee shield. When you use these commands, prepend AT to them (e.g. to
use the ID command, you should type ATID).

Changed lines 25-26 from:
BDThe baud rate used for serial communication with the Arduino board or computer.0 = 1200 bps \\ 1 = 2400 \\ 2 = 4800 \\ 3 = 9600 \\ 4 = 19200 \\ 5 = 38400 \\ 6 = 57600 \\ 7 = 1152003 (9600 baud)
to:
BDThe baud rate used for serial communication with the Arduino board or computer.0 = 1200 bps >>? 1 = 2400 \\ 2 = 4800 \\ 3 = 9600 \\ 4 = 19200 \\ 5 = 38400 \\ 6 = 57600 \\ 7 = 1152003 (9600 baud)
August 15, 2007, at 09:39 PM by David A. Mellis -
Changed lines 25-26 from:
BDThe baud rate used for serial communication with the Arduino board or computer.0 = 1200 bps, 1 = 2400, 2 = 4800, 3 = 9600, 4 = 19200, 5 = 38400, 6 = 57600, 7 = 1152003 (9600 baud)
to:
BDThe baud rate used for serial communication with the Arduino board or computer.0 = 1200 bps \\ 1 = 2400 \\ 2 = 4800 \\ 3 = 9600 \\ 4 = 19200 \\ 5 = 38400 \\ 6 = 57600 \\ 7 = 1152003 (9600 baud)
August 15, 2007, at 09:38 PM by David A. Mellis -
Changed lines 24-25 from:
IDThe network ID of the Xbee module. In most cases, a module will communicate with other modules that share the same network ID.0 - FFFF3332
to:
IDThe network ID of the Xbee module. In most cases, a module will communicate with other modules that share the same network ID.0 - FFFF3332
BDThe baud rate used for serial communication with the Arduino board or computer.0 = 1200 bps, 1 = 2400, 2 = 4800, 3 = 9600, 4 = 19200, 5 = 38400, 6 = 57600, 7 = 1152003 (9600 baud)
August 15, 2007, at 09:35 PM by David A. Mellis -
Changed lines 24-25 from:
IDThe network ID of the Xbee module. In most cases, a module will communicate with other modules that share the same network ID.0 - FFFF3332.)
to:
IDThe network ID of the Xbee module. In most cases, a module will communicate with other modules that share the same network ID.0 - FFFF3332
August 15, 2007, at 09:35 PM by David A. Mellis -
Changed line 23 from:
CommandDescriptionValid ValuesDefault Value
to:
CommandDescriptionValid ValuesDefault Value
August 15, 2007, at 09:35 PM by David A. Mellis -
Changed lines 23-25 from:

ID (Valid Range: 0 - FFFF. Default value: 3332.)
The network ID of the Xbee module. In most cases, a module will communicate with other modules that share the same network ID.

to:
CommandDescriptionValid ValuesDefault Value
IDThe network ID of the Xbee module. In most cases, a module will communicate with other modules that share the same network ID.0 - FFFF3332.)
August 15, 2007, at 09:33 PM by David A. Mellis -
Changed lines 23-24 from:

ID - The network ID of the Xbee module. In most cases, a module will communicate with other modules that share the same network ID. Range: 0 - 0xFFFF. Default value: 3332.

to:

ID (Valid Range: 0 - FFFF. Default value: 3332.)
The network ID of the Xbee module. In most cases, a module will communicate with other modules that share the same network ID.

August 15, 2007, at 09:32 PM by David A. Mellis -
Changed lines 21-24 from:

Here are some of the more useful commands for configuring your Xbee module. For step-by-step instructions on using these commands, see the guide to the Xbee shield.

to:

Here are some of the more useful commands for configuring your Xbee module. For step-by-step instructions on using these commands, see the guide to the Xbee shield. When you use these commands, prepend AT to them (e.g. to use the ID command, you should type ATID).

ID - The network ID of the Xbee module. In most cases, a module will communicate with other modules that share the same network ID. Range: 0 - 0xFFFF. Default value: 3332.

August 15, 2007, at 09:26 PM by David A. Mellis -
Added lines 21-24:

Here are some of the more useful commands for configuring your Xbee module. For step-by-step instructions on using these commands, see the guide to the Xbee shield.

August 15, 2007, at 08:44 PM by David A. Mellis -
Deleted lines 20-54:

You can configure the Xbee module from the code running on the Arduino board or from software on the computer. To configure it from the Arduino board, you'll need to have the jumpers in the Xbee position. To configure it from the computer, you'll need to have the jumpers in the USB configuration and have removed the microncontroller from your Arduino board.

To get the module into configuration mode, you need to send it three plus signs: + and there needs to be at least a second before and after when you send no other character to the module. Note that this includes newlines or carriage return characters. Thus, if you're trying to configure the module from the computer, you need to make sure your terminal software is configured to send characters as you type them, without waiting for you to press enter. Otherwise, it will send the plus signs immediately followed by a newline (i.e. you won't get the needed one second delay after the +++). If you successfully enter configuration mode, the module will send back the two characters 'OK', followed by a carriage return. In a terminal, this will look like this (where the +++ was typed by you, and the OK returned by the module):

+++OK

Once in configuration mode, you can send AT commands to the module. Command strings have the form ATxx (where xx is the name of a setting). To read the current value of the setting, send the command string followed by a carriage return. To write a new value to the setting, send the command string, immediately followed by the new setting (with no spaces or newlines in-between), followed by a carriage return. For example, to read the network ID of the module (which determines which other Xbee modules it will communicate with), go into command mode and then type:

ATID

followed by a carriage return (i.e. pressing enter from within a terminal program). You should see:

3332

(the default ID of the module) or whatever value the ID was last set to.

To change the network ID of the module, type:

ATID3331

and press enter. You should get back:

OK

Now, check that the setting has taken effect by again asking for the ID:

ATID

(and pressing enter). You should see:

3331

August 15, 2007, at 08:43 PM by David A. Mellis -
Changed lines 37-38 from:
to:

To change the network ID of the module, type:

ATID3331

and press enter. You should get back:

OK

Now, check that the setting has taken effect by again asking for the ID:

ATID

(and pressing enter). You should see:

3331

August 15, 2007, at 08:41 PM by David A. Mellis -
Changed lines 23-26 from:

In either case, to get the module into configuration mode, you need to send it three plus signs: + and there needs to be at least a second before and after when you send no other character to the module. Note that this includes newlines or carriage return characters. Thus, if you're trying to configure the module from the computer, you need to make sure your terminal software is configured to send characters as you type them, without waiting for you to press enter. Otherwise, it will send the plus signs immediately followed by a newline (i.e. you won't get the needed one second delay after the +++). If you successfully enter configuration mode, the module will send back the two characters 'OK', followed by a carriage return.

Once in configuration mode, you can send AT commands to the module. Command strings have the form ATxx (where xx is the name of a setting). To read the current value of the setting, send the command string followed by a carriage return. To write a new value to the setting, send the command string, immediately followed by the new setting (with no spaces or newlines in-between), followed by a carriage return.

to:

To get the module into configuration mode, you need to send it three plus signs: + and there needs to be at least a second before and after when you send no other character to the module. Note that this includes newlines or carriage return characters. Thus, if you're trying to configure the module from the computer, you need to make sure your terminal software is configured to send characters as you type them, without waiting for you to press enter. Otherwise, it will send the plus signs immediately followed by a newline (i.e. you won't get the needed one second delay after the +++). If you successfully enter configuration mode, the module will send back the two characters 'OK', followed by a carriage return. In a terminal, this will look like this (where the +++ was typed by you, and the OK returned by the module):

+++OK

Once in configuration mode, you can send AT commands to the module. Command strings have the form ATxx (where xx is the name of a setting). To read the current value of the setting, send the command string followed by a carriage return. To write a new value to the setting, send the command string, immediately followed by the new setting (with no spaces or newlines in-between), followed by a carriage return. For example, to read the network ID of the module (which determines which other Xbee modules it will communicate with), go into command mode and then type:

ATID

followed by a carriage return (i.e. pressing enter from within a terminal program). You should see:

3332

(the default ID of the module) or whatever value the ID was last set to.

August 15, 2007, at 08:34 PM by David A. Mellis -
Changed lines 21-23 from:

You can configure the Xbee module from a sketch running on the Arduino board, or from a terminal program running on the computer. [explain jumper settings needed]

For details on configuring the Xbee module, see the product manual from MaxStream.

to:

You can configure the Xbee module from the code running on the Arduino board or from software on the computer. To configure it from the Arduino board, you'll need to have the jumpers in the Xbee position. To configure it from the computer, you'll need to have the jumpers in the USB configuration and have removed the microncontroller from your Arduino board.

In either case, to get the module into configuration mode, you need to send it three plus signs: + and there needs to be at least a second before and after when you send no other character to the module. Note that this includes newlines or carriage return characters. Thus, if you're trying to configure the module from the computer, you need to make sure your terminal software is configured to send characters as you type them, without waiting for you to press enter. Otherwise, it will send the plus signs immediately followed by a newline (i.e. you won't get the needed one second delay after the +++). If you successfully enter configuration mode, the module will send back the two characters 'OK', followed by a carriage return.

Once in configuration mode, you can send AT commands to the module. Command strings have the form ATxx (where xx is the name of a setting). To read the current value of the setting, send the command string followed by a carriage return. To write a new value to the setting, send the command string, immediately followed by the new setting (with no spaces or newlines in-between), followed by a carriage return.

For more details on configuring the Xbee module, see the product manual from MaxStream.

August 15, 2007, at 08:21 PM by David A. Mellis -
Changed lines 9-10 from:

The Xbee shield allows an Arduino board to communicate wirelessly using Zigbee. It is based on the Xbee module from MaxStream. The module can communicate up to 100 feet indoors or 300 feet outdoors (with line-of-sight). It can be used as a serial/usb replacement or you can put it into a command mode and configure it.

to:

The Xbee shield allows an Arduino board to communicate wirelessly using Zigbee. It is based on the Xbee module from MaxStream. The module can communicate up to 100 feet indoors or 300 feet outdoors (with line-of-sight). It can be used as a serial/usb replacement or you can put it into a command mode and configure it for a variety of broadcast and mesh networking options.

August 15, 2007, at 08:20 PM by David A. Mellis -
Changed lines 5-6 from:
to:

XbeeShieldSchematic.jpg

August 15, 2007, at 08:19 PM by David A. Mellis -
Added lines 3-8:

Schematic

Overview

August 15, 2007, at 08:12 PM by David A. Mellis -
Added lines 9-12:

With the jumpers in the Xbee position (i.e. on the two pins towards the interior of the board), the DOUT pin of the Xbee module is connected to the RX pin of the microcontroller; and DIN is connected to TX. Note that the RX and TX pins of the microcontroller are still connected to the TX and RX pins (respectively) of the FTDI chip - data sent from the microcontroller will be transmitted to the computer via USB as well as being sent wirelessly by the Xbee module. The microcontroller, however, will only be able to receive data from the Xbee module, not over USB from the computer.

With the jumpers in the USB position (i.e. on the two pins nearest the edge of the board), the DOUT pin the Xbee module is connected to the RX pin of the FTDI chip, and DIN on the Xbee module is connected to the TX pin of the FTDI chip. This means that the Xbee module can communicate directly with the computer - however, this only works if the microcontroller has been removed from the Arduino board. If the microcontroller is left in the Arduino board, it will be able to talk to the computer normally via USB, but neither the computer nor the microcontroller will be able to talk to the Xbee module.

August 15, 2007, at 07:55 PM by David A. Mellis -
Changed lines 7-8 from:
to:

The Xbee shield has two jumpers (the small removable plastic sleeves that each fit onto two of the three pins labelled Xbee/USB). These determine how the Xbee's serial communication connects to the serial communication between the microcontroller (ATmega8 or ATmega168) and FTDI USB-to-serial chip on the Arduino board.

August 15, 2007, at 07:52 PM by David A. Mellis -
Changed lines 11-12 from:

You can configure the Xbee module from a sketch running on the Arduino board, or from a terminal program running on the computer.

to:

You can configure the Xbee module from a sketch running on the Arduino board, or from a terminal program running on the computer. [explain jumper settings needed]

August 15, 2007, at 07:51 PM by David A. Mellis -
Changed lines 5-13 from:
to:

Jumper Settings

Configuration

You can configure the Xbee module from a sketch running on the Arduino board, or from a terminal program running on the computer.

For details on configuring the Xbee module, see the product manual from MaxStream.

August 15, 2007, at 07:49 PM by David A. Mellis -
Added lines 1-5:

Xbee Shield

The Xbee shield allows an Arduino board to communicate wirelessly using Zigbee. It is based on the Xbee module from MaxStream. The module can communicate up to 100 feet indoors or 300 feet outdoors (with line-of-sight). It can be used as a serial/usb replacement or you can put it into a command mode and configure it.

Share