XBEE Click

How does it work?

XBee Click is based on the XB24CZ7PIS-004, a low-power Digi XBee® RF module from Digi International, providing wireless connectivity to end-point devices in ZigBee mesh networks. The transceiver chipset of the XB24CZ7PIS-004 is based on the Ember Silicon Labs EM357 SoC with an RF data rate of 250kbps (serial up to 1Mbps) and advanced configuration options available via simple AT or API commands. It also supports low-power sleeping nodes and has an outdoor RF line-of-sight range of up to 1.2km (urban range of up to 60m) in a combination of coverage, data redundancy, and data reliability. The XB24CZ7PIS-004 module has worldwide acceptance. Operating at a frequency of 2.4GHz, it allows its application in the US, Canada, Europe, Australia, and Japan. The ZigBee module also supports various levels of security configured depending on the application’s needs.

This Click board™ comes with a configurable host interface allowing communication with MCU using the chosen interface. The XB24CZ7PIS-004 can communicate with MCU using the UART interface with commonly used UART RX, TX, and hardware flow control pins UART CTS and RTS (Clear to Send and Ready to Send) or using the SPI interface (XBee module will work as an SPI-slave only). The module can be configured locally through serial commands (AT or API) or remotely through remote API commands to set or read any network device’s configuration settings. In the case of the SPI interface, the users can use it to configure the module and write the library by themselves.

XBee Click is associated with many other features. An active-low reset signal routed on the RST pin of the mikroBUS™ socket activates a hardware reset of the system, while the A/D pin routed on the INT pin of the mikroBUS™ socket represents a type of interrupt whose function can be selected by positioning an onboard SMD jumper to an appropriate position labeled as SRQ or ATT. SRQ position is a “Data terminal ready” function used to tell the XBee module that the host MCU is ready to communicate, while the ATT position (SPI Attention) represents an indicator for the SPI interface whenever the XBee module has data for the host MCU.

Alongside firmware updates, it supports commissioning, and LED behaviors; a commissioning pushbutton marked as COMMI combined with an ASSOC LED provides various simple functions to aid in deploying devices in a network, such as a device wake-up, broadcast transmission, and more. On the other side, the yellow ASSOC LED indicates the device’s network status and diagnostics information. If the LED is constantly on, it means that the module is not connected to the network, while the case of standard flashing of the LED represents the normal operating mode.

This Click board™ can be operated only with a 3.3V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. However, the Click board™ comes equipped with a library containing functions and an example code that can be used, as a reference, for further development.

Specifications

Pinout diagram

This table shows how the pinout on XBEE Click corresponds to the pinout on the mikroBUS™ socket (the latter shown in the two middle columns).

Notes	Pin					Pin	Notes
UART RTS	RTS	1	AN	PWM	16	CTS	UART CTS
Reset	RST	2	RST	INT	15	A/S	SPI Attention/Sleep Control Line
SPI Chip Select	CS	3	CS	RX	14	TX	UART TX
SPI Clock	SCK	4	SCK	TX	13	RX	UART RX
SPI Data OUT	SDO	5	MISO	SCL	12	NC
SPI Data IN	SDI	6	MOSI	SDA	11	NC
Power Supply	3.3V	7	3.3V	5V	10	NC
Ground	GND	8	GND	GND	9	GND	Ground

Onboard settings and indicators

XBEE Click electrical specifications

Software Support

We provide a library for the XBEE Click as well as a demo application (example), developed using MIKROE compilers. The demo can run on all the main MIKROE development boards.

Package can be downloaded/installed directly from NECTO Studio Package Manager (recommended), downloaded from our LibStock™ or found on MIKROE github account.

Library Description

This library contains API for XBEE Click driver.

Key functions

• xbee_get_serial_number This function sends a get serial number command.

• xbee_set_device_name This function sets the device name (node identifier).

• xbee_set_destination_address This function sets the destination address high and low bytes.

Example Description

This example demonstrates the use of an XBEE Click by showing the communication between the two click boards configured in transparent mode.

void application_task ( void ) 
 { 
 #ifdef DEMO_APP_TRANSMITTER 
     xbee_generic_write( &xbee, DEMO_TEXT_MESSAGE, strlen( DEMO_TEXT_MESSAGE ) ); 
     log_printf( &logger, "%s", ( char * ) DEMO_TEXT_MESSAGE ); 
     Delay_ms ( 1000 );
     Delay_ms ( 1000 );
     Delay_ms ( 1000 );  
 #else 
     xbee_process( ); 
     if ( app_buf_len > 0 )  
     { 
         log_printf( &logger, "%s", app_buf ); 
         xbee_clear_app_buf(  ); 
     } 
 #endif 
 }

The full application code, and ready to use projects can be installed directly from NECTO Studio Package Manager (recommended), downloaded from our LibStock™ or found on MIKROE github account.

Other MIKROE Libraries used in the example:

• MikroSDK.Board
• MikroSDK.Log
• Click.XBEE

Additional notes and informations

Depending on the development board you are using, you may need USB UART click, USB UART 2 Click or RS232 Click to connect to your PC, for development systems with no UART to USB interface available on the board. UART terminal is available in all MIKROE compilers.

mikroSDK

This Click board™ is supported with mikroSDK – MIKROE Software Development Kit. To ensure proper operation of mikroSDK compliant Click board™ demo applications, mikroSDK should be downloaded from the LibStock and installed for the compiler you are using.

For more information about mikroSDK, visit the official page.