TV not responding to upgrade device code on URC-6820 (JP1.2)

[mobidutch]

I have a URC-6820 that I want to use with a Samsung TX-P3075WH TV. The TV responds fine to built-in device code 0812.

According to the Devices spreadsheet, code 0812 uses the NECx2 protocol (00 5A), with Device number 7 and Sub device 7.

If I learn a button (e.g. Mute) from the TV's original remote and load it into IR, it indeed shows that the learned command uses the NECx2 protocol (7.7).

So...I created an upgrade device code 1812 (NECx2 7.7 - fixed data 31 FF FF) with my custom button layout. I know for sure I used the correct EFC/OBC/HEX codes, as the ones I entered are the same as those learned (I did not confuse e.g. EFC with OBC).

However, when I copy the upgrade device 1812 to IR, assign it to the TV button and upload it to the remote...the TV does not respond AT ALL to any buttons. Yet when I upload the new device code to a RS-2117 or URC-6131n, it works just fine. What could be going on with that URC-6820?? Any help appreciated!!!

[vickyg2003]

Hmm, this is strange. I KNOW there is a new RDF for the 6820_8820_10820 remote. I KNOW the official remote has some bad protocol information and doesn't address Keymap. What I don't know is where is the new RDF.

I believe that a bad protocols section in your RDF can cause problems with RM.

This is WAY OUTSIDE MY AREA OF UNDERSTANDING, but you can try making the following modifications to your 10631063 RDF to see if this is the root of your problem.

Try replacing your protocols section with this

[Protocols]
0000, 0002:5, 0006, 0007, 000A, 000C, 000D, 000E, 0011, 0013,
0014, 0015, 0018, 001A, 001B, 001C, 001D, 001E, 001F:8, 0021,
0022, 0027:new, 0029, 002A, 002D, 002F, 0032, 0034, 0039, 003A,
003D, 003F, 0045, 0046, 0056, 0058:2, 005A, 005B, 005C, 005D,
005E:2, 005F, 0060, 0061, 0065:2, 0067, 0068, 006A, 006E, 0073,
0078, 007E:3, 0083, 0087, 008D, 0092:3, 0093, 0098, 009C, 009E,
00A4, 00AF, 00B6, 00BE, 00C4, 00C9, 00CA, 00CD:2, 00CE, 00D0,
00D7, 00DB, 00DE, 00E2, 00E3, 00E7, 00E8, 00F0, 00F2, 00F5,
00F8:3, 00FC, 0103, 0109, 010C, 010E, 010F, 0111, 0114:2, 0115,
0117, 0118, 0119, 011A:2, 011B, 0125, 012A:2, 0161, 016D, 0174,
017E, 0182:2, 0184:2, 0186, 018B, 0190, 0194, 01A4

Also add this line to the [Settings]
KeyMap=$01F.5.1.1.0 (Standard;Alternate)

[johnsfine]

I can't guess the problem from the above description. I don't know why Vicky is guessing a problem in the protocols section of the RDF. Such a problem could cause your symptoms, but it wouldn't be one of my first ten guesses in this case.

I hope you saved a .ir file right before uploading to the 6820 to test. If not, do it over, save such a .ir file and retest (in case doing it over accidentally fixed something).

Then upload that .ir file to the Diagnosis area and post a URL for that file back to this thread.

Any expert looking at your .ir file should spot the problem without guessing.

If the upgrade in the .ir file is messed up, we probably we need to see the saved file of the upgrade (.txt if you used KM, .rmdu if you used RM) to try to figure out why it is messed up.

BTW, if I had to guess, my first guess would be an RDF problem such that IR.exe is confused about which button on the 6820 is TV. The most conclusive test for that is to manually (on the remote) set the setup code for TV to some built-in setup code, then download to IR.exe and see which device button has what setup code. But that's just one of many guesses.

[binky123]

Not sure if it was a typo but the fixed data is: NECx2 7.7 - fixed data 31 1F 1F. Remember to change the remote type to URC-6820/8820/10820 in KM or RM.

[mobidutch]

Thanks for the replies..much appreciated!

Vicky: Your protocols section was indeed different from the default RDF...in the default RDF a comma was missing between two sets of numbers.

Binky: You are correct..it was a typo. I meant 31 1F 1F.

All: With the corrected RDF, it still doesn't work. So per John's suggestion, I uploaded the IR file here.

Thanks!