[ErikJ]

Al pretty much nails it. The whole modulation thing can be tricky for anyone who hasn't seen it before, so that's probably the big cause of confusion (ie, IR frequency != 40KHz).

However, it should be noted that nearly all (I think it's all) TV/Stereo remotes operate at 40KHz (it's actually just a shade off). Most off the shelf commercial IR sensors (ie, the kind you buy at Radio Shak) only look for this 40KHz signal, and filter everything else out. The way your TV, and your FIRST robot, know the difference between the signals is in the coding scheme used on top of that 40KHz carrier. So... if you go off and write your own code, yes, TV remotes could be a source of interference. Or, perhaps cooler, you could probably allow (for demo/debug purposes) the FIRST controller to use a TV remote as an input, provided you knew the coding scheme of the controller (you can find many of these online).

Something I haven't seen made mention of yet is multipath interference*. I worked on an IR project a few years ago and would get strong multipath interefence when I was transmitting near large metal objects (in this case, lockers at the HS we were working with at the time). I'm interested to see if this becomes an issue, especially as one or more robots approaches the beacon. I'm not sure if this will be a major issue (I suspect not, but it could be depending on robot geometry), but the fix should be simple enough if it is.

* multipath interference - in short, when you recieve a signal that has been reflected off a few objects before you receive it. for example, in a car radio you have a direct path (radio tower to you), and a ground bounce path (tower, ground, you) - mutliple paths, hence multipath interference. In our example, this means that robot reflecting IR waves from the beacon appears to be a source, potentially causing problems for your location algorithm.