Yes, I've looked at that. The thing I wanted to do differently was to be able to save codes and play them back without having to know the protocol. His code has the raw mode if it can't id the protocol, which is similar to what I'm doing, but he is using 50uS resolution for recording codes. I'd need to mess around with more devices to see if that is always enough precision. Also I'm not understanding where he is saving the codes, or in what form. Could somebody explain that? On reading through his code again, it makes me wonder if I really need to store times that are so big. The longest signal pulse I've seen in the start or middle of a code is about 10ms. Anything longer is always at the end, and it's when the carrier is turned off. I suppose I could just always leave a big-ish delay after sending any code and not worry about storing the longer times. Using 50uS resolution and up to just 12mS times in the code can get the times down to 8 bits each, or up to 15 codes in eeprom. I don't think 15 codes would be enough, though. I can't think of a way to shrink the codes more than that without just giving up more resolution? Any ideas? I'm really thinking I'll need external storage of some kind. Any suggestions on that?