Documented code missing from library.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. attempt to declare a 16bit XBee Address
e.g.:
XBeeAddress16 remoteAddress = XBeeAddress16(int 0x12, int 0x34);

What is the expected output? What do you see instead?
This fails to compile with error
'XBeeAddress16' does not name a type
On checking through the XBee.h file I can see that the declaration has been 
commented out.
On checking further in the .cpp file, the only mention of XBeeAddress16
is in a section that has been commented out, ending in the comment:
// THIS IS WRONG

Is this likely to be fixed sometime soon, or do I need to work on it myself? 
While I am an experienced programmer, C is not my native language, so I will 
probably go for a kludge solution rather than your otherwise quite elegant 
library.

What version of the product are you using? On what operating system?
Arduino Uno R3
XBee Series 1
XBee-Arduino-0.3.zip,  downloaded three days ago.

I want to use 16 bit addressing as I have an n-sensor network each containing a 
bare xBee along with the sensor. I need to have local feedback on each sensor 
board. Thus my logic looks like:

SensorBoard: send sensor data to coordinator every nnn milliseconds

Coordinator (XBEE + Arduino): decode sensor data and display data for each 
sensor locally. Send decoded data back to remote sensor for display at that 
station.

Sensorboard: display decoded data as a local feedback that the correct message 
got through. Basically, I am using the RATCommand to fire a 7-segment LED. 
attached to pins 4,5,7 (not needed by the sensor array)

While I could use 64bit addressing, it would seriously hamper the size of the 
sensor net I can use as I would run out of memory quite quickly if I store 64 
bit addresses in the Arduino.

Original issue reported on code.google.com by gr...@swiftdsl.com.au on 20 May 2012 at 12:10

[GoogleCodeExporter]

Oops. I read further and discovered the other issue raised on this that was 
closed. 
My only excuse is that I am new to google code & only did a search on open 
issues (the default)before raising mine.

Not being familiar with C, I did not know about the declaration for 16bit 
integer variables. Once I used uint16_t things started working.

It might be a good idea to place a note to this effect in the documentation to 
save others the trouble.

Original comment by gr...@swiftdsl.com.au on 20 May 2012 at 10:02

[GoogleCodeExporter]

Original comment by andrew.rapp@gmail.com on 2 Feb 2014 at 7:00

• Changed state: Invalid