Closed 101100 closed 10 years ago
I'm thinking that "series" isn't the best property to differentiate different API behavior. It depends much more on the firmware/supported standard, and in principle, any other non-xbee device that implements one of the supported standards should be compatible with the respective api behavior.
Then again, in 99% of the cases people use xbees series 1 or 2 with default firmware, and after all, the module has xbee in it...
Is the serial communications protocol a standard, or just he wireless protocol? My understanding was that the ZigBee standard was about the wireless signals (and the same with 802.15.4). Is the serial protocol a direct mapping of that?
You are right. It is not the wireless standard, but rather the module firmware. It however also seems that all (Digi?) modules have the same API as far as the format of the frames goes, just some modules support different subsets of frame types (while sometimes providing same functionality with different frame types). I differentiated between "802.15.4", "ZNet" and "ZigBee" as Digi's API frames utility does: http://ftp1.digi.com/support/utilities/digi_apiframes2.htm
Thanks for the resource. I think I'll stick with 802.15.4
versus ZigBee
and Znet
(which is an older version of ZigBee
as far as I can tell).
Fixed in #5
Also allowAlso pass module type into xbee-api in case it is used in the future.series: 1
/series: 2
option to set type.