John Bailey / XBeeApi

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.

Last commit 06 Jul 2014 by John Bailey

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.

Last commit 05 Jul 2014 by John Bailey

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"

Last commit 06 Jul 2014 by John Bailey

Settings/Status

Import programXBeeApiSimpleATCmdsExample

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

Last commit 31 Mar 2014 by John Bailey

Import programXBeeApiRemoteATCmdsExample

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

Last commit 13 Jul 2014 by John Bailey

Receive

Import programXBeeApiSimpleReceiveExample

Simple example of using XBeeApi to receive data packets via wireless

Last commit 08 Jul 2014 by John Bailey

Import programXBeeApiReceiveCallbackExample

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

Last commit 08 Jul 2014 by John Bailey

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

Last commit 08 Jul 2014 by John Bailey

Remote I/O

Import programXBeeApiRemoteIOExample

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

Last commit 28 Jul 2014 by John Bailey

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.

Files at this revision

API Documentation at this revision

Revision 10:0d084d0253a7, committed 2014-01-31

Comitter:
johnb
Date:
Fri Jan 31 09:29:28 2014 +0000
Parent:
9:ba90e9efd68b
Child:
11:bfcf1356027b
Commit message:
Update getDataPtr() to support fragmented buffers

Changed in this revision

Base/XBeeApiFrame.cpp Show annotated file Show diff for this revision Revisions of this file
Base/XBeeApiFrame.hpp Show annotated file Show diff for this revision Revisions of this file
Base/XBeeDevice.cpp Show annotated file Show diff for this revision Revisions of this file 
--- a/Base/XBeeApiFrame.cpp	Fri Jan 31 02:20:02 2014 +0000
+++ b/Base/XBeeApiFrame.cpp	Fri Jan 31 09:29:28 2014 +0000
@@ -36,9 +36,10 @@
     return m_apiId;
 }
         
-const uint8_t* XBeeApiFrame::getDataPtr( void ) const
+void XBeeApiFrame::getDataPtr( const uint16_t p_start, const uint8_t**  p_buff, uint16_t* const p_len ) const
 {
-    return m_data;
+    *p_len = m_dataLen;
+    (*p_buff) = m_data;
 }
 
 XBeeApiFrameDecoder::XBeeApiFrameDecoder() : m_device( NULL )

--- a/Base/XBeeApiFrame.hpp	Fri Jan 31 02:20:02 2014 +0000
+++ b/Base/XBeeApiFrame.hpp	Fri Jan 31 09:29:28 2014 +0000
@@ -96,8 +96,26 @@
         /** Retrieve the API identifier for this frame */
         XBeeApiIdentifier_e getApiId( void ) const;
         
-        /** Return a pointer to the API-specific data (i.e. that which follows the API identifier in the frame */
-        const uint8_t*      getDataPtr( void ) const;
+        /** Retrieve a pointer to the API-specific data (i.e. that which follows the API identifier in 
+            the frame).  In *total*, getDataPtr will return sufficient data to match getCmdLen(), however
+            it may be done in chunks using p_start and *p_len to control the fragmentation process.  
+            For example:
+            
+                getCmdLen() == 5;
+                getDataPtr( 0, &b, &l );
+                l == 2; b[0] == 'a'; b[1] == 'b'; 
+                getDataPtr( 2, &b, &l );
+                l == 1; b[2] == 'c';
+                getDataPtr( 3, &b, &l );
+                l == 2; b[0] == 'd'; b[1] == 'e';
+            
+            \param[in]  p_start The start point within the buffer.  It is only meaningful to use a non-zero
+                                value in the case that a previous call to getDataPtr did not return a buffer
+                                of length getCmdLen(), in which case p_start should be set to be the next
+                                byte that is required.
+            \param[out] p_buff  Pointer to a pointer to receive the buffer pointer 
+            \param[out] p_len   Pointer to receive the length of the data pointed to by *p_buff */
+        void getDataPtr( const uint16_t p_start, const uint8_t**  p_buff, uint16_t* const p_len ) const;
 };
 
 /* Forward declare this as XBeeDevice is dependent upon XBeeApiFrameDecoder */

--- a/Base/XBeeDevice.cpp	Fri Jan 31 02:20:02 2014 +0000
+++ b/Base/XBeeDevice.cpp	Fri Jan 31 09:29:28 2014 +0000
@@ -199,6 +199,7 @@
     uint16_t len;
     uint16_t i;
     const uint8_t* cmdData;
+    uint16_t written = 0;
  
 #if defined  XBEEAPI_CONFIG_USING_RTOS
     m_ifMutex.lock();
@@ -211,14 +212,23 @@
     xbeeWrite((uint8_t)(len & 0xFF));
 
     sum += xbeeWrite((uint8_t)p_cmd->getApiId());
-
-    cmdData = p_cmd->getDataPtr();
+    len--;
 
-    for( i = 0;
-         i < (len-1);
-         i++ )
+    /* While data still to go out */
+    while( written < len ) 
     {
-        sum += xbeeWrite(cmdData[i]);
+        uint16_t buffer_len;     
+        
+        /* Get the next chunk of data from the frame object */
+        p_cmd->getDataPtr( written, &cmdData, &buffer_len );
+
+        /* Write the buffer to the XBee */
+        for( i = 0;
+             i < buffer_len;
+             ++i,++written )
+        {
+            sum += xbeeWrite(cmdData[i]);
+        }
     }
      
     /* Checksum is 0xFF - summation of bytes (excluding delimiter and length) */