Support for series2

[GoogleCodeExporter]

What version of the product are you using? On what operating system?
I am using version 360 on linux

Please provide any additional information below.
Do you plan to integrate series2 functions also?

Original issue reported on code.google.com by karl.dri...@gmail.com on 1 Jun 2010 at 10:44

[GoogleCodeExporter]

Currently I don't have any series 2 radios.

I have had a couple of requests for series 2 support, any donations to help me 
get my 
hands on a pair of series 2 radios would be very much appreciated.

I hope to get a pair and start development within a month.

Original comment by g@attie.co.uk on 1 Jun 2010 at 10:49

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

You can try some api compatible with series 2 using digimesh firmware on your 
series 1 radios.

Original comment by wsart...@gmail.com on 14 Apr 2011 at 10:20

[GoogleCodeExporter]

Hi Both,

I am now in a position to implement this properly (final year of Uni is VERY 
tough!).

Karl:
* did you have any issues with your previous enhancements?
* did you try the AT commands with the series 2.5 XBee units? A brief look at 
the datasheets indicate that they are virtually 100% compatible.

Initially I am only going to implement the following API commands:
* 0x10  ZigBee Transmit Request
* 0x8B  ZigBee Transmit Status
* 0x90  ZigBee Recieve Packet

I hope this is acceptable to you both.

Original comment by attie@attie.co.uk on 18 Apr 2011 at 4:50

[GoogleCodeExporter]

It'll be perfectly.

Actually I'm porting all my C code to python as python-xbee has series 2 
already implemented.

I'll only use the 0x10 function.

Original comment by wsart...@gmail.com on 18 Apr 2011 at 5:27

[GoogleCodeExporter]

Hi again both,

I have now implemented support for series 2 radios! (though only the 3 packet 
types mentioned previously).
See the latest commit for info and sample code.

Please be aware:
* you must configure one of your XBees as a Coordinator.
* you must use an API firmware
* you must use API mode 2 (with escape characters)

If you have any issues, please feel free to let me know!
Attie

Original comment by attie@attie.co.uk on 18 Apr 2011 at 7:17

• Changed state: Fixed

[GoogleCodeExporter]

Hi,

I updated my library with your latest version (485) and so far it sems to
work correctly,
Thanks for adding these commands.

Original comment by karl.dri...@gmail.com on 20 Apr 2011 at 10:39