Comes pre-assembled at very good prices. Its not as good of an RF performer as the CC2520, but looks very useful for hobbyist use…
(Just use it with a real processor, not a PIC ;))
Digi’s XBees are very popular. Standard firmware does a lot of common functions such as A/D sampling-transmission, digital I/O remote via wireless, UART/serial port extension via wireless, etc. Eliminates a lot of coding.
Ya, but the microchip module is only $10.
I keep thinking of buying it, but I just have something against premade modules in general. I’m going to buy a couple of cc2500’s and experiment with dipole loops on some PCB’s to see how well it works. If I manage to get anything out of it, it means cheap 2.4Ghz xmt/rcv. Otherwise I’ll spring for the chip antenna’s a supporting passives.
I’m currently trying to get SimpliciTI working with my EZ430-RF2500 modules, but it looks like they haven’t updated the SimpliciTI distributable for the latest CCE, and I get a bunch of crap in the project.
TheDirty:
Ya, but the microchip module is only $10.I keep thinking of buying it, but I just have something against premade modules in general. I’m going to buy a couple of cc2500’s and experiment with dipole loops on some PCB’s to see how well it works. If I manage to get anything out of it, it means cheap 2.4Ghz xmt/rcv. Otherwise I’ll spring for the chip antenna’s a supporting passives.
I’m currently trying to get SimpliciTI working with my EZ430-RF2500 modules, but it looks like they haven’t updated the SimpliciTI distributable for the latest CCE, and I get a bunch of crap in the project.
$10 complete with zero firmware, nada, no application.
XBee is $19 and odds are you may need to write no new code for many kinds of apps. And if you do, the Hayes modem-like UART based API is there as is a binary mode API if you choose.
But, well, as you wish!
Some people don’t actually want to use Zigbee, since there may be special requirements in how to operate the MAC and scheduling.
The microchip module is a good deal for those who want to operate at a lower level.
You sure about that? I see a MiWi stack from AN1066 and a zigbee stack (AN1232).stevech:
$10 complete with zero firmware, nada, no application.
I’m not staying XBees suck or anything but it seems that Microchip has some firmware for the device. At $10 each, it may well be worth checking them out.
I have no stake in Digi/Xbee. But do note that all of the modules I know of have an option for you to get an SDK and compiler and muck about adding your code to theirs. The downsides of this are that it's quite complicated in that environment, they all have a task scheduler of some sort that if you foul up the timing the MAC stops working right, and some need expensive compilers. Jennic's is free/open and uses an odd but open CPU. Atmel's 15.4 stack is a problem with the demise of Meshnetics. Digi's 15.4 stack for the Freescale has a C SDK for that stack, but you have to buy a $3K compiler. Digi's stack for the Ember series 2 is probably locked up with Ember and their ZigBee-only arrangement (closed). The TI based modules are like the Freescale modules: semi-open, compiler $ needed.theatrus:
Some people don’t actually want to use Zigbee, since there may be special requirements in how to operate the MAC and scheduling.The microchip module is a good deal for those who want to operate at a lower level.
This is why it’s best to work through a coprocessor connected to the '15.4 radio with MAC, via a UART or I2C or some such physical API.
I understand that Microchip has no viable market presence in 802.15.4 with module makers so you are starting with bare metal, e.g., you will try to build a boat starting with standing trees for wood.
If I’m mistaken on the above, please advise.
That was all Greek to me. I’m opposed to using XBee’s for the same reason I’m not using an Arduino. Yes, it’s easier, but that’s not what I’m looking for.
I’m new at this, but I’m trying to work with SimpliciTI and the CC2500. It looks like I might be getting CC1101 chips, though.
TI’s CCE is free and limits me to 16k which is fine for now. It will hold the SimpliciTI stack and a decent amount of extra code. If I need more I’ll see about porting it to Crossworks.
I have my own point to point network code that I wrote for the cheap RF modules, which is not sophisticated, but it’s easily portable and I’ve moved it to 2 uC’s already. So if I want something even simpler, that will do.
Would you like clarification? Not sure what's confusing.TheDirty:
That was all Greek to me. .
Philba:
You sure about that? I see a MiWi stack from AN1066 and a zigbee stack (AN1232).stevech:
$10 complete with zero firmware, nada, no application.I’m not staying XBees suck or anything but it seems that Microchip has some firmware for the device. At $10 each, it may well be worth checking them out.
I just bought some XBee modules to get started with a hack that I would like to be wireless. The simplicity of the XBee is a major selling point but it also drives up the price in a big way.
I would love to take a closer look at the MicroChip modules. The price is very good.
The AN1066 document is very interesting. I prefer AVR but I am sure the code could be rewritten. Table 10 on page 36 lists the memory requirements. If the PIC code density translates pretty much to the same size on AVR then it should be able to run on a ATMega168 or 328.
They don’t give memory requirements for the full ZigBee stack unfortunately. But the mini stack should be fine for what I want to do.
I don’t have any of the modules yet but I would certainly be interested in porting that stack.
Does your app need ZigBee rather than either serial port emulation or peer-to-peer networking using MAC addresses?
ZigBee is optional and most applicable if you intend to do routed network meshing with variable routes.
This is true for any of the 15 or so OEM modules on the market.
If you’re making a product, don’t forget about Type Certification for FCC Part 15 in the US, and the vastly different regulations in Japan, France and other countries.
If you aren’t making a product for volume production, a $20 ready-to-use, type certified module is usually most prudent. Some vendors of these are Digi (XBee), Jennic, Aerocomm, RFM, ST, Helicomm, OKI, Panasonic, CEL (calif), etc.
(meshnetics is kaput, partially assimilated into Atmel).
Chip makers like TI, ST, Ember, Atmel, Microchip often sell dev or demo kits, but these aren’t comparable to the product-ready OEM modules as above, with full firmware API, some via the serial port, and with Type Certifications in several countries.