API for communicating with XBee devices.

Dependencies:   CircularBuffer FixedLengthList

Dependents:   XBeeApiTest XBeeApiSimpleATCmdsExample XBeeApiBroadcastExample XBeeApiBroadcastExampleRTOS ... more

Overview

XBeeApi is intended to be a library for providing a high-level API interface to the XBee - for example getChannel() and setChannel(2) methods rather than needing to send( "ATCH" ) and send( "ATCH 2" ) - and then de-code the responses.

See the notebook page here for a description of how the API works & some details on the various classes.

Features:

  • Support for transmission & reception of data packets
  • Support for reading & changing settings
  • Support for "Remote AT" interface to access settings & I/O channels on remote XBees
  • XBeeApi should work if you're using mbed-rtos, though it is not currently threadsafe. Take a look at the XBeeApiBroadcastExampleRTOS example if you're including mbed-rtos.

Example Programs

There are also example programs available:

Transmit

Import programXBeeApiSimpleBroadcastExample

Simple example of how to use XBeeApi - set up the XBee, configure P2P networking then transmit a frame.

Import programXBeeApiBroadcastExample

Example for XBeeAPI; a little more involved than XBeeApiSimpleBroadcastExample with report on failure to set up the XBee and on the transmit status of the message.

Import programXBeeApiBroadcastExampleRTOS

Example of using the XBeeApi library to broadcast a message, based on XBeeApiBroadcastExample. This example shows how to use the library when using mbed-rtos. Before compiling you must open "XbeeApi\Config\XBeeApiCfg.hpp" and change the '#if 0' to '#if 1' on the line above the comment reading "Use RTOS features to make XBeeApi threadsafe"

Settings/Status

Import programXBeeApiSimpleATCmdsExample

Simple example of using XBeeApi to send AT-style commands to the XBee

Import programXBeeApiRemoteATCmdsExample

Example of using the XBeeApi library to send AT commands to remote XBee devices in order to read/write settings

Receive

Import programXBeeApiSimpleReceiveExample

Simple example of using XBeeApi to receive data packets via wireless

Import programXBeeApiReceiveCallbackExample

Example of using the XBeeApi library to receive a message via a callback method

Import programXBeeApiReceiveCallbackExampleRTOS

Example of using the XBeeApi library to receive a message via a callback method. This example shows how to use the library when using mbed-rtos. See the comment at the top of main.cpp

Remote I/O

Import programXBeeApiRemoteIOExample

Example of using the XBeeApi library to read inputs on a remote XBee

If you have 2 mbed connected XBees available then you can use XBeeApiSimpleReceiveExample and XBeeApiSimpleBroadcastExample as a pair.

Note that this is still a work in progress! XBeeApiTodoList tracks some of the functionality still to be added.

Revision:
53:7b65422d7a32
Parent:
48:48397bedf95d
--- a/Base/XBeeDevice.hpp	Mon Jul 28 12:48:33 2014 +0000
+++ b/Base/XBeeDevice.hpp	Mon Jul 28 13:27:58 2014 +0000
@@ -145,7 +145,9 @@
    
      /** Represents the different types of addressing for XBee devices */
      typedef enum {
+         /** 16-bit addressing */
          XBEE_API_ADDR_TYPE_16BIT = 0,
+         /** 64-bit addressing */
          XBEE_API_ADDR_TYPE_64BIT = 1    
      } XBeeApiAddrType_t;
 
@@ -227,6 +229,9 @@
      */
      void setIgnoreBadChecksum( const bool p_shouldIgnore );
      
+     /** Retrieve the number of packets which have failed the checksum test (see setIgnoreBadChecksum() )
+         \returns Rolling counter of the number of failed checksum tests 
+     */
      uint16_t getBadChecksumCount( void ) const;
 
      /** Retrieve the number of bytes received from the serial data stream which have been discarded
@@ -244,6 +249,11 @@
 #endif
 
 #if defined XBEEAPI_CONFIG_USING_RTOS && defined XBEEAPI_CONFIG_RTOS_USE_DISPATCHER
+     /** Function used (when using the MBED RTOS) to set up a thread to dispatch received data outside 
+         of the interrupt context.  Handling received data within the interrupt context is likely to
+         result in problems due to limited stack availability.
+         Must be called once and once only (even if using multiple XBee devices)
+     */
      bool setupDispatchTask();
 #endif