Forgot your password?
No account? Register one!
May 6, 2010
Tutorial - Nest Protect Teardown |
about 3 months ago
I think the light sensor might be the Avago APDS-9300, or a close cousin
Product WRL-09097 |
about 4 years ago
3) The DM (“Digimesh”) firmware is different from the DP (“point-to-multipoint”) firmware that ships with the XBees. While there is a slight curve to learning the new DM parameter set, I believe it will make things easier in the end, because you don’t need routers: the radios find the best way to route the data without you having to explicitly program it. The only added overhead is you need to address to the 64bit address of the destination node, no big deal.
4) The packets send IO data in an 0x92 frame, which is not described in the XBee Pro 900 manual. You DO need the XBP 900 manual to learn about Digimesh AT commands though! And you need the NEW manual linked above for the latest firmware that supports Analog inputs. I found the 0x92 frame info in the Xbee Pro ZB Manual 90000976_C rev 3/2009, found elsewhere on SFE:
Hi - Just a few notes on configuring these:
1) The units that shipped from SFE didn’t have analog capabilities, and the product manual posted here is old (2008). However, this is easily remedied by updating the firmware up to 8044. Get the manual for the newest firmware (and the newest firmware itself) at Digi:
2) I run OS X, but the Windows-only X-CTU software (from Digi) is really really useful. The software has to have the firmware of your XBee in its own library in order for you to change the XBee’s parameters. In my case, even the firmware that shipped with my XBees was not available on my downloaded version of X-CTU, so I had to fetch it. For whatever reason, I could not use X-CTU’s “Download from Web” option to work on my windows virtual machine running X-CTU, so had to download the zip file from Digi and read it into X-CTU before I could play with the parameters of the XBees. Not hard, but not immediately obvious either.
No public wish lists :(