Show Posts
Pages: 1 ... 3 4 [5]
61  Forum 2005-2010 (read only) / Interfacing / Finding out when xbee associates on: January 11, 2010, 06:44:15 pm
According to the manual I thought you could find out from the coordinator when an Xbee end device powers up and associates; the coordinator is supposed to get a Modem status response. It doesn't happen. I'm using ZNet software. Anybody managed to make this work?

Naw, I think I misread that - nobody tells anybody anything when that happens. However, for those that are interested, now that I mentioned it, what I'm going to do is have the coordinator look at the 16-bit address of anybody talking to it and if the talker is not in the comm map then a new node discovery has to be initiated so we know all about him.
62  Forum 2005-2010 (read only) / Interfacing / Re: XBee addressing problem on: November 23, 2009, 04:41:42 pm
Sometimes X-ctu will appear to write but does not - easy to check by reading after writing.
If it won't write, it may be due to the fact that the device is set to api mode with escape off or on and you are not setting those on the X-ctu
panel. I.e. you must write with X-ctu set to the same parameters as the device. Try variations until it works.

D0 can be set high/low by toggling the pull-up resistors with a command. Check Xbee manual.
63  Forum 2005-2010 (read only) / Interfacing / Re: newbie   xbee problem on: November 20, 2009, 04:34:42 pm
Your version numbers don't sound right.
What does the back of the chips say - e.g. XB24-Bxxx what is the xxx?
64  Forum 2005-2010 (read only) / Interfacing / Trying to find XBP24-Bxx Xbee chips on: November 19, 2009, 12:21:52 pm
Anyone have a supplier for these?
They are the 60 mW with chip antenna. Can't drill through concrete with the 2mW units I got now.
65  Forum 2005-2010 (read only) / Interfacing / Re: xbee module failed on: November 19, 2009, 12:19:50 pm
If you programmed it somehow to go to sleep, you could ground pin 9 (to pin 10) and see if it wakes up. Other than that, do it while X-CTU is in charge and see if it responds.
66  Forum 2005-2010 (read only) / Interfacing / Re: XBee issues on: November 13, 2009, 04:57:40 pm
I first made sure the associate led's blink at the appropriate rate - without that there is nothing. Coordinator: 2/sec, end device 4/sec.
Now his library does not get a return for the first command and the (expected) error return for the second (due to the bug.) My home-brew sensor board's led stopped working - have to check that now.

I'm testing with his RemoteAtCommand.pde, then I'll progress to the Series2_IOSamples.pde once that's totally clean.
67  Forum 2005-2010 (read only) / Interfacing / Re: XBee issues on: November 13, 2009, 03:37:32 pm
We are both dealing with the same problem - except I have the coordinator on an arduino and the end device on a little sensor board I built. As soon as Andrew lets me know he fixed the bug he had in his library I will try listening on the coordinator for beeps from the sensor using his API libraries. I can let you know.
68  Forum 2005-2010 (read only) / Interfacing / Re: XBee issues on: November 13, 2009, 02:53:29 pm
I solved my x-ctu problems as follows:
a)if your device is set to sleep, then ground pin 9 to pin 10; this was outlined elsewhere and prevents the xbee from sleeping while being programmed.
b) if the chip is already in api mode you must have api enabled; if it is using escaping, you must have escape enabled.
c) if the chip is not using api and you program to use api, then you must clear api before writing, then set api enable before reading it; if api escape is programmed, make sure api escape is set, otherwise it must be off.
69  Forum 2005-2010 (read only) / Interfacing / Re: XBee issues on: November 12, 2009, 07:45:07 pm
I'd like to interject here - chris is having similar problems to mine with X-CTU; you are right in using XB24-B for series 2, but I think I damaged my end device when just connecting 3.3, gnd and sensor (off for now) to D0 (you are using D1). I am trying to track down what to do with the din/dout pins. Digi says to connect them (to what?) but then they say idle pins need not be connected.
70  Forum 2005-2010 (read only) / Interfacing / Connections to sensor-only xbee on: November 12, 2009, 12:13:33 pm
I'm having some serious problems with X-CTU and an Xbee chip that is supposed to operate as a sensor only. Its board connects only ground, vcc and d0, and led/resistor to ad5. I am wondering what to do with din and dout - the manual does not specify anything.
After successfully flashing the chip with X-CTU it started acting up on its board (assoc led flashes randomly and varies depending on hand proximity.) It seems to communicate using Andrew Rapp's library, but X-CTU will not recognize it anymore. I checked for any board shorts or opens.
71  Forum 2005-2010 (read only) / Interfacing / Re: XbeePro shield blowing Xbee chip on: September 11, 2009, 05:47:52 pm
Thanks - it looks like this might be a cloned board (I'm going to visit the reseller tomorrow) and it's not providing what the usual Xbee shield provides. Beware of clones!
72  Forum 2005-2010 (read only) / Interfacing / XbeePro shield blowing Xbee chip on: September 11, 2009, 01:52:17 pm
Hi - I got an XbeePro shield for the Arduino and it seems to have blown the Xbee chip; I notice the Arduino (328) sends 5V up the din/dout lines into the Xbee. I don't think that is supported by an Xbee Series 2.
Anybody seen this problem before?
73  Forum 2005-2010 (read only) / Bar Sport / Re: Netduino on: January 21, 2011, 06:29:54 pm
Dont forget ... no EEPROM on netduino.
Pages: 1 ... 3 4 [5]