Confused by ID-000D protocol

[JohnL88]

I recently set up 6 devices in RM and each worked out fine. The final piece of equipment was an old TV made by Fisher. When I learned the codes on my Balboa JP1 remote, they were identified as protocol ID-000D and several different devices for (1,2,5, and 6) in IR.exe. I’ve looked at every related post and have tried just about everything (i.e. AWAI protocol, subtract 1 from device number, NEC1, etc.). I would normal just learn the keys (works fine) but I am then maxing out with just the TV. I recently (after MANY hours) have come to the realization I will never figure it out. Is there someone out there that can possibly help? Below are the learned codes from IR.exe:


# Device Key Protocol Device SubDev OBC Hex

1 TV Power ID-000D 6 52 69 73
2 TV Mute ID-000D 5 84 6A 97
3 TV CH+ ID-000D 6 82 5A 224
4 TV tv/vid ID-000D 1 77 A6 255
5 TV 3 ID-000D 2 45 A5 231
6 TV 1 ID-000D 2 53 A9 71
7 TV 2 ID-000D 2 77 A6 255
8 TV 4 ID-000D 6 44 65 233
9 TV 5 ID-000D 2 83 9A 222
10 TV 6 ID-000D 2 51 99 198
11 TV 7 ID-000D 2 75 96 126
12 TV 8 ID-000D 2 43 95 102
13 TV 9 ID-000D 6 76 66 1
14 TV 0 ID-000D 2 85 AA 95
15 TV exit ID-000D 6 52 69 73
16 TV VOL+ Unknown 42.328 KHz Signal
17 TV VOL- Unknown 42.328 KHz Signal
18 TV CH- Unknown 42.328 KHz Signal

ANY suggestions would be greatly appreciated,

John

[gfb107]

When having problems with learned signal decodes, it is best to post the saved IR file. Always remember to post links to any files you upload and need help with.

[johnsfine]

Edit: I wrote the message below on a machine where I didn't have a current protocols.ini, so I didn't realize it includes AKAI (incorrectly). I haven't checked carefully yet, but I assume the errors in AKAI in protocols.ini match those in KM, so the instructions about transforming the device number and using EFC instead of OBC, that I wrote for KM in that other thread should work for RM. Hopefully we can clean some of this up soon.

Parts of my original message below are still correct:

I’ve looked at every related post and have tried just about everything (i.e. AWAI protocol, subtract 1 from device number, NEC1, etc.).

It was AKAI not AIWA. I assume RM doesn't include AKAI yet. Sorry about that. It should be easy to add to protocols.ini but I never got around to it and I don't have the data for that on the computer where I am now.

Also (if you use KM) it is not "subtract 1" from the device number. The device number would need to be translated as described in this post:
https://www.hifi-remote.com/forums/viewt ... 4442#p24442

But if someone added AKAI to protocols.ini, there would be no need to manipulate the device number that way, because we should not duplicate KM's error, that makes that manipulation necessary.

When having problems with learned signal decodes, it is best to post the saved IR file.

In this case there's no need for that. The decodes are fine. The problem is there is no AKAI entry in protocols.ini

Greg, the RM thing I forgot how to do and need to research is: One of the three device bits goes into the hex command rather than into the fixed data. I forget what you put in protocols.ini to say a hex cmd bit comes from device data rather than from OBC etc.

[gfb107]

Greg, the RM thing I forgot how to do and need to research is: One of the three device bits goes into the hex command rather than into the fixed data. I forget what you put in protocols.ini to say a hex cmd bit comes from device data rather than from OBC etc.

Use TranslatorFromDev(...) instead of Translator(...)

[JohnL88]

I am still trying to create an RM file for the TV mentioned above. I think I have tried just about everything. I have even resorted to trial & error (continually changing the device number and praying it will work). I've finally just about given up.

As suggested by gfb107 above, I have posted the IR file at:

https://www.hifi-remote.com/forums/dload ... le_id=1235

I'm really justed trying to take the "learned" TV commands and create a RM file. Any help would be greatly appreciated.

John

[johnsfine]

I modified Akai in RemoteMaster to make it simple to get from Learned signal decodes to an RM upgrade. But that change is just in the source code of RM at SourceForge, not yet in the released version.

As usual, I'm on the wrong computer to grab a trial version of that, so I'll give you a correct upgrade tomorrow morning if no one else does first.

BTW Greg, I decided to let the user mix device numbers to the extent that this protocol executor accidentally lets them. So that needed the new ParmInitializer rather than just TranslatorFromDev.

[johnsfine]

I guess I had this confused with some other recent situation in which we had already confirmed that the ID-000D decodes were correct and the issue was the difference between the decodes and the support in KM/RM.

Now that I look at the learned signals posted above, I see the decodes are wrong. I don't believe I've seen this protocol before (Is Jon lurking here?).

I'll need a little more checking to see whether there is more structure present than seems to be, and to see if an existing UEI protocol covers it. But it looks like it would be simple to duplicate in PB.

Meanwhile, how accurate is the association of functions to buttons (especially the digits) in that file of learned signals? Is the signal learned on TV:1 actually the original '1' signal, etc.?

Knowing a few contiguous digits in correct sequence helps to resolve some ambiguity in investigating a new protocol.

[johnsfine]

More issues. You probably need to relearn some of these.

1) Every command is either one or two frames long. Maybe that's what they really are. But more likely it means the press of the original remote button during learning was too short. Read some other threads on good learning technique.

2) The signal learned on the RCVR:last key looks like it is the same protocol as the others but mislearned due to weak batteries in the original remote and it is the last one of these in the list, so you probably learned it after the others, so the batteries in your original remote are probably too weak now for decent learning.

[johnsfine]

Any other protocol experts lurking may want to know I think the IRP notation for this is:

{42.3K,3000,msb}<1,-3,1,-7|1,-7,1,-3>(F:5,1,-27)+

Notice there are two opposite bursts per bit and only 5 bits.

Edit: Does anyone know anything about UEI's protocol 0083? At first glance, that seems to be this.

Edit2: Now I'm looking at TV/0159 (which uses pid-0083) and seems to be this code-set. Rob's cross reference list for that shows brands: Fisher , Sanyo and Sears. That adds further support to my guess that I've found it. If I understand Rob's devices.xls right that setup code is in the URC-9800 but a 9810 is not the same and doesn't have this setup code built-in (though it's easily added by JP1).

Edit3: I adjusted DecodeIr to recognise this protocol and to generate EFC numbers compatible with pid-0083. I then compared all the learned signals to TV/0159 and it matches perfectly except for the learned TV:exit button, which is actually the power button.

[johnsfine]

I might as well release DecodeIr and maybe RM support for this, now that I've done the research. But it's such a limited protocol I assume it will never appear in any other setup code, though more people might have TVs that need TV/0159 with learning JP1 remotes that don't include TV/0159.

So I don't know whether to call the protocol (in the decodes and RM) "pid-0083" or Fisher or "TV-0159".

I don't like "Fisher" because most Fisher TV's don't use this and if someone finds another TV that uses it, it's as likely to by Sanyo as Fisher.

I prefer just calling the protocol "TV-0159" because I'm sure no other setup code would ever need this protocol. (I have notes on the rmy809 and rmtv303 remotes that say this setup code is TV/0078 in those models. But those setup codes seem to be all messed up and it isn't a different code set, just a different number for the same code set).

So any experts who don't want a protocol given the same name as a setup code, speak up now.

[The Robman]

How about pid-0083?

And you're right about the Sony Tivo remote setup codes, they were given new numbers to match up with something else (I forget what) so they have no relation to UEI code numbers.

[johnsfine]

I built that RM upgrade. (I named the protocol pid-0083 as Rob voted).

To use it, you must have the following not_yet_official version of RM's protocols.ini

http://john.fine.home.comcast.net/ir/protocols.ini

Once you have that you can use the TV-0159 upgrade from:

https://www.hifi-remote.com/forums/dload ... le_id=1237

[jon_armstrong]

John, I'm just now reading this thread. Is there a link for the new version of DecodeIR.dll?

[Mark Pierson]

It's right here Jon...

[johnsfine]

John, I'm just now reading this thread.

That's fine. I didn't end up needing help, but you might want to add the irp notation for this on the line for pid-0083 in your comparison matrix file (pid numbers to meanings).