Sounds good. So, lets work through slowly.You've probably tried all this already but...
What about the coordinator id?
Have you tried each funnel separately & verified it works.
What sensor/data are you transmitting?
I have had multiple xbees working for ages, but with a different microcontroller
I see no reason why they wouldn't work as its only powering the xbee & providing breakout of the pins. The issue I have yet to resolve with this piece is powering multiple sensors on each node, but that's another story.
Have you tried contacting the maker of the Funnel?
Ok, I have to ask - why do you need to use the Funnel?
Apart from the fact you have them.
Maybe you could use some of the Tweet-a Watt stuff. She has multiple xbees & Arduino running, so there might be code & circuits that would be of use in your project
hum, we shouldn't talk about funne's documentation... :)
i actually need the funnel as input and output:
- one will be use more as a controller with accelerometer and different sensors
- the other one is used to control servos and lights
the body resistance sensing was just to check if everything is working.
I will probably end up by using this:
i got 2 and it seems promising, but for now i would really love to deal it with the funnel.
I seen that there is a file called "multipoint" in the xbee section of the fio's examples, so maybe...
I think the main point here is that you are using the XBEE's as a serial line replacement. In this setup I believe they will pair in a point to point network. As a (wired) serial line cannot have multiple clients, I don't think you will be able to get this working in this manner.
Is there a specific reason why you are using the funnel boards instead of the analog inputs on the XBEE itself?
basically once you manage to set up the receiver as controller and both senders as routers tied to the senders PAN ID, they will send to the receiver independently. since you are not synchronizing them, the packets will collide.
this means both senders will send at the same time (chances are the sending will overlap) and the receiver will not be able to process both packets simultaneously and probably drop both. the only solution to this is to send a sync pulse from the receiver with an index for example, forcing the two senders to wait for a free time slot. this will slow you down, especially if you have large data packets or fast sending rates.
and if you add more senders the time-slots will get more and more sparse and the transmission rate slower.
have a look at this paper: Eirik Renton, Collecting Sensor Data for Active Music
Masters Thesis in Microelectronic Systems, UNIVERSITY OF OSLO Department of Informatics, June 2009
Hmm that's interesting jasch.
I have had multiple Mk1 Xbees running with a MakeController for a couple of years now, never noticed any problem with dropped packets. But their use is not heavily time critical either.