jbollt wrote:I am helping a friend with JP1 and 15-2116. We are using the upgrade "Sony STR-K750P" from the Yahoo files.
I'm guessing you mean this file, from the Audio folder:
http://groups.yahoo.com/group/jp1/files ... DDW750.txt
jbollt wrote:I hope i did the link right!
Nope, but I fixed it. Read the sticky thread in the JP1-General forum for details on how to do the links.
jbollt wrote:Why does the learned command show up 3 times in IR???
That's usually an indication of a bad learn. By "bad learn" I don't mean that the learned button doesn't work, just that it's using up more memory than it needs to.
jbollt wrote:It is listed as #1 #2 and #3....all with the same info..and why the "or"
Sony 15 device 48 OBC 34 Hex Cmd 44 or 45 EFC 2240 or 232.
The fact that the info is the same tends to confirm that it's a bad learn. The "or" is because the Sony 12/15 protocol, as implemented by UEI, is a mini-combo protocol, so there are two possible EFCs for each OBC. When I loaded up the Sony STR-K750P upgrade into KM, I noticed that the device code1 was set to 48 and device code2 was set to 176. Your learned signal uses device code 48, so when you add this function to the KM file, you will need to either leave the byte2 column blank or set it to 0. The codes in this KM file have been entered in OBC format, so you should enter your code in OBC format also. So, in summary, you would add a new entry to the Functions sheet, enter OBC 34 and set byte2 to 0. You would then go to the Buttons sheet and assign it to an actual button.
jbollt wrote:I'm still not sure why we couldn't get this to work in KM as part of the upgrade.
My guess is that you either (1) entered an EFC rather than an OBC, (2) entered something other than zero in the byte2 column, or (3) forgot to actually assign it to a button.
