Interesting -- I've been playing with a pair of series 2 radios, and only looking at the series 2 documentation. I'll have to check out the series 1 information. Thanks for the tip.
For this kind of application (N-many devices, added to the network in random order), do you think ZigBee/Xbee is still the way to go? I see what you are saying about collision detection -- I was hoping Xbee/ZigBee would manage a lot of that for me.
If I could use the traditional coordinator/router/node star or tree of a ZigBee network, I would get the collision management for free -- it's just that I can't know which node will be the node that gets turned on first to start the network. Also, in this app, if two random nodes are turned on in a random room, they should find each other and start exchanging information. Does this still sound like a series 1 use case? Thanks!
Hi, in my application, I'd like to be able to have two devices create an ad-hoc network and start chatting back and forth. In a traditional XBee/ZigBee setup, you need to pre-designate one device as a coordinator and the others as routers or end nodes. I'd like any device to be able to be the coordinator as it may not know in advance if it will be the only device or the first device on the network or in the mesh.
Does anyone have experience programming Xbees like this? My idea is to make all Xbees coordinators, but if anyone could point me to some examples of how to initiate sessions in an 'all coordinator' network, that would be awesome.
Great post, thanks for sharing. I'm looking forward to trying this with an MMA3671L, which is 3-axis. I'm sort of unclear how you derived your constants (xy_max and xy_min). Were these part of the specification for your chip, or did you derive these experimentally by just tilting the board around and looking at outputs on serial? Thanks!