If you have learned signals that don't get decoded when you look at them in IR.exe, post your file to the Diagnosis Area then post your question here (including a link to the file).
You're not doing anything wrong. That custom protocol is for a remote with an S3F80 processor. Your 10820 has an HCS08 processor. A compatible version of the protocol will need to be written for you. Only a few people know how to do that. I'm not one of them.
EDIT: There already is a HCS08 version (thanks, Mike):
Could you post the working IR file. I didn't have the tools nor the knowledge to properly test the 10820 version 9 months ago, but I do now.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
It appears to have something to do with AUX2 (where I had it assigned). When I assign this to another device, it worked great. Or, I believe, even if I push another device first (and have it assigned to AUX2), it then seemed to work??
Thanks for the responses, it helped me experiment elsewhere - I'm back up again.
I got another of these remotes, but it seems to have different ir codes for certain keys. I have uploaded the learned set from the new remote here. The new codes are under "TV" and the old set are under "VCR". The keys that are different are rew, ff, page+, page-, up, down, left, right.
Would someone decode the new set please? Thanks very much.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
TV Rew 0110110 54
TV FWD 0111110 62
TV CH+ 0111001 57
TV CH- 0111101 61
TV 2 0011001 25
TV 4 0001110 14
TV 6 0000001 01
TV 8 0011010 26
I don't usually work at the 0 and 1s level, but this is the way the codes read. Please check the binary to decimal translation, but I "think" I've got it right.
It appears that the protocol is MSB, If these are supposed to be read from MSB then these would be your OBCs.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Those are the codes I found in the link above. I downloaded a file called "usb remote 2". I'm wondering if you provided the correct link?
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
That's the right file, but notice that the Gap info is different on the orig VCR learns versus the new TV learns. So I think they left the codes the same but changed the protocol on us.
Good call Dave, I didn't notice the itty bitty change in the frequency timings. Apparently this device is very, very picky on the timings. I'm going to have to inspect these codes with my Widget, but first need to go over to where I have decent wifi!
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
ok, the good news is that your protocol upgrade works perfectly
the bad news is that there was a bit of operator stupidity ( ) on my part, and it turns out that the original protocol actually works. turns out that the usb receiver received those ir signals perfectly but was sending out a different set of keystrokes than the original receiver. this confused my plugin which didn't recognize the new set of keystrokes.
However, there is a big green button on the remote discussed above which looks to trigger the home screen of Windows Media Center. I haven't seen any learned code from that button. It would be great if I could get it!
According to your other post you have a 15-2104, which is a learning remote, so why don't you learn the missing button and either read out the info or post the IR file for one of us to look at.
Rob www.hifi-remote.com Please don't PM me with remote questions, post them in the forums so all the experts can help!