donphillipe wrote:I have a new URC8810w and for VCR, I used code 0000 for my Symphonic SE436D VCR.
Somewhere I thought I read that in certain situations, code 0000 could cause a problem. I could be wrong. I am often wrong. Ignore me.
donphillipe wrote:Async9:803-961:78.75..DD.FF
Test the learned signals to see if they actually control the equipment, and let us know. Async codes, Gap codes, pretty much anything that looks red or strange on the learn tab page of IR usually prompts me to turn off the computer, crack open a cold beer, and watch something interesting on cable tv.
JohnSFine, Jon, Rob [in fact, insert any name except mine here] are really the ones to address those weird codes. Sometimes, weird codes can be the result of weak batteries in the OEM or the learning remote. Sometimes, weird codes can be the result of decodeIR.dll not having seen that protocol before. Sometimes, weird codes are the result of user technique during the learning process. If we are seeing codes, it is probably not a version problem, but just to be on the safe side, check and make sure all the tools you are using are the current versions.
So what do we do now? Well, while waiting for expert advice, perhaps it would not hurt to get some fresh batteries, and then review the learning process. Make sure the remotes are on a flat table, 2 inches apart, head to head, in a room with no other source of IR. Press and release the learning remote button. wait for the flashy lights. press the OEM button and hold it for several seconds, until the learning remote flashes that it is done learning the signal.
If this does not solve the problem, I could introduce you to the protocol builder spreadsheet.
_______________
Got JP1?
-Steve