I had decided to revisit this project and am glad to see people active on this thread (somewhat). The plan was to use the LM2902 chip and as seen in the picture posted earlier by me, would use the leftmost pin on the side of the 'dash' on the chip as Pin # 1. I went ahead and soldered the wires as instructed to pins yellow-->Pin#1, White-->Pin#4, Black-->Pin#11 and Orange-->Pin#14.
[Pl. see attachment below - its an illustration of the assumed pin numbers on this illusive LM2902 :o . The EXTRAs are there in case this pin number selection fails; I would then reverse the setup which if need be will document.]
I then proceeded to following these steps
to check/update the firmware on the XBee modules since I hadn't touched this project for some time.
The following issue came about:[Advisory:This is a tangential issue but does relate to the Tweet-a-Watt setup because this issue relating to XBee could arise in someone else' setup as it did in mine :) ]
Having followed the above steps
, selecting version 10ED
. and after doing a "write", one of my XBees is now refusing to respond. There is no blinking green light and X-CTU is complaining about failure to enter command mode for this specific XBee module. This is the message I get:Failed to enter command mode
Check connections and try again.
Failed steps taken to troubleshoot:
1. I tried reinstalling the FTDI cable driver from windows
2. I uninstalled the windows' version of the driver and downloaded one from FTDI Friends. That did not solve the problem.
3. With the FTDI cable connected and XBee module inserted in to the XBee Adapter
that I built using these instructions
, I tried to do a reset by connecting the GND and RST pins; it did not resolve the problem - how can I confirm that its been reset..?
I tried testing connectivity with the second XBee module that comes included in the Tweet-a-watt kit, and it seems to communicates fine with X-CTU. I didnt update its firmware and its at 10EC at the moment.
Could the problem be with the XBee module and loading the latest firmware (10ED) updating it from its prior (10EC version). Please help on a way forward..thank you.