Hi there. Trying to start up a more ambitious project with a friend involving relay of information from custom devices to and from a computer (via RF) running a web service of sorts. However we want to start small and the first order of business is just getting a mcu talking to a computer via RF.
I’m fairly new to embedded systems and electronics, and can’t say I know a world about RF, but I know enough to get around and be dangerous. I’ve successfully worked with C and writing custom firmware for an ARM prototype board and was able to grudge may way through it pretty well and accomplish everything I wanted.
Really what we need advice on is what technology choices we should make. We’re trying to way cost vs. flexibility and programming effort. Essentially for the first test we’d love to just exchange data between a computer and an RF device, and that could be as simple as possible. However the future direction of what we’re trying to accomplish involves the need for more sophisticated data transfer protocols, and potentially larger amounts of data/files.
I’m wondering if anyone out there with more experience can lend some guidance. It seems like the lower cost RF solutions will provided the most flexibility since the data protocol essentially would be crafted by hand by us, but also be the most work to implement (and I’m not really sure we need that kind of flexibility). Serial communications should be sufficient for the time being. Range is not a huge factor, the further the better, but 40m should be plenty for now.
Essentially the goal would be to have a transceiver hooked up to a computer somehow talking to the computer through some sort of custom driver (the least amount of “ground-up” work we have to do for now, the better). It should be able to poll for devices (the mcu with RF) in its proximity and attempt to establish a communications with them. From here there would be a set routine to transmit and receive data. The computer would be hooked up to a web service relaying the data (doesn’t fully relate to the topic other than context).
Can anyone offer some suggestions that would would point us in the right direction? We don’t want to spend a ton on the RF technology, but at the same token we don’t want to have to spend tons of time hand coding all of our protocols and transmition/error checking routines, also polling and broadcast, etc. Looking for a good balance of price vs. immediate utility. Smaller form factors are preferrable.
Thanks,
-Mike