Add protocol 01 B5 (Samsung36?) to RM/KM?

[mdavej]

This protocol, listed in Rob's devices spreadsheet as device 0199 with fixed data 04 00 E0, appears to be in the radio shack 15-13x family of remotes. DecodeIR identifies it as Samsung36. I think it's the same as the protocol in THIS Samsung BD-P1000 upgrade.

[kupakai]

The following should work for Samsung36 in "protocols.ini" file to include it in RM:

Code: Select all

[Samsung36]
PID=01 B5
DevParms=Device Number:8=0,Sub Device:8=0,Param E:4=0
DeviceTranslator=Translator(lsb,0) Translator(lsb,1,8,8) Translator(lsb,2,4,16,0)
CmdParms=OBC
CmdTranslator=Translator(lsb,0)
DefaultCmd=00
CmdIndex=0
FixedData=20 00 00
Code.S3C80=43 8C 31 8B 12 8F 45 08 04 00 FA 02 CD 00 FA 00 E5 77 6F 08 CF 08 B4 E4 06 07 60 07 F0 05 0C 04 10 07 10 06 10 05 0A F8 20 10 E6 25 11 8D 01 61
Code.HCS08=20 15 22 48 31 87 45 08 04 00 FA 02 E1 00 FA 00 F9 77 6F 08 CF 08 C8 4E 63 64 33 64 B6 62 62 B7 62 AE 04 39 64 39 63 39 62 5B F8 3C A9 6E 11 7D CC FF 7A

I've labeled the three parameters as "Device", "Sub Device", and "Param E" based on John's Samsung36 irp file (would there be a better label for the last parameter "E"?). I've also included a version for HCS08 remotes based on the S3F80 version in 15-135 extract. I don't have a device using this protocol so I can't real test it, but I've checked it with CaptureIR and it decodes back as Samsung36 so it should work (it's also a pretty straight forward port from the original code).

I think Greg maintains protocols.ini, so until the protocol is included in an update, you can add the above code in your copy of protocols.ini if you need it.

There is another executor for Samsung36 in this thread which is smaller than the one from UEI, but it seems a little more confusing since it divides the 20 fixed data bits into four 5 bit pieces and there doesn't seem to be a way to change the last 5 bits.

[mr_d_p_gumby]

I've also included a version for HCS08 remotes based on the S3F80 version in 15-135 extract.

There is an official HCS08 version in the URC-8305:

Code: Select all

20 15 22 48 31 8F 45 08 04 00 F9 02 E1 00 F9 00 F9 77 83 08 CE 08 C8 4E 63 64 33 64 B6 62 62 B7 62 AE 04 39 64 39 63 39 62 5B F8 3C A9 6E 11 7D CC FF 7A

I've written executors for the SST/6805 & P8/740, but I don't have access to them at the moment.

I'm also adding this to the next version of KM, so I have the same question as to what to label parameter 'E'.

[mdavej]

Thanks, kupakai and gumby. Works perfectly in the 13x and 100. I don't have an HCS08 to test.

[mr_d_p_gumby]

Here's the 6805-RC version that should also work for the SST (JP1.1) remotes:

Code: Select all

Code.6805-RC16/18=11 24 31 20 10 8F 45 08 04 01 7B 70 00 7B 7C 3B \
                  CB 00 44 66 64 AE 5D F6 43 E7 01 5A 74 74 74 74 \
                  A6 04 69 02 69 01 79 4A 26 F8 3C 66 A6 11 B7_78 \
                  CC 01 C4

I haven't had time to debug the P8/740 version, so that's it for now.

[Zibri]

There is also another one:

Protocol 01b5 (samsung36)
Fixed data: 0C 58 00

[Zibri]

About code 0199, I have a question.

Exmaple: remote key "0" should be:

protocol = Samsung36, device = 32, subdevice = 0, obc = 11, misc = E=7

But in IR.EXE I read that the HEx Function for key "0" is "hex command" D0 and EFC 140.


Oh.. nevermind, I answer myself: it's the reverse Bits are just reversed.

[Zibri]

Please help:

How to translate:

Protocol 01b5 (samsung36)
Fixed data: 0C 58 00

from hex/ofc in ir.exe to a pronto learning code?

I can do that with the "0199" code but I can't find a way with the 1195 code.

The only difference in IR.exe is that fixed data is: 0C 58 00 for 1195 code instead of 04 00 E1 for 0199 code.

By the way, 1195 code is used in 2012 bluray products.

[mdavej]

That corresponds to device: 3, subdevice: 26, param E: 0

OBC isn't part of the fixed data.

What remote has DVD setup code 1195? I can't find it in any of our databases. Where's this fixed data coming from?

[Zibri]

The fixed data is coming from an upgrade wav I decoded

The device is Samsung BD-E8900 which uses protocol samsung36 and fixed data 0C 58 00

Samsung BD-D5500 uses Samsung36 protocol and fixed data: 04 00 E1

[mdavej]

Got it. I wondered how you were doing all of this without a cable or remote or the correct software (RM). RM calculates the correct fixed data for you. That's how I answered your question.

So 1195 isn't actually in any remote yet.

[Zibri]

How did you get the device and subdevice from 0C 58 00 ??

[Zibri]

If you need it, 1195 is defined as:

Code: Select all

B5 00 B2 FE F9 0C 58 00 01 81 41 C1 21 A1 61 E1 
11 91 A3 63 89 29 A0 E9 19 59 99 D9 05 45 39 79 
43 C5 

And 0199 is defined as:

Code: Select all

B5 00 B6 FE E9 04 00 E1 D0 40 C0 20 A0 60 E0 10 
90 50 88 B0 00 70 B8 D4 18 98 D8 58 38 28 C8 48 
A8 4C

Both use 01 B5 protocol which is:

Code: Select all

43 8C 31 8B 12 8F 45 08 04 00 FA 02 CD 00 FA 00 
E5 77 6F 08 CF 08 B4 E4 06 07 60 07 F0 05 0C 04 
10 07 10 06 10 05 0A F8 20 10 E6 25 11 8D 01 61 

[mdavej]

How did you get the device and subdevice from 0C 58 00 ??

Thanks for the code. Please hold onto that and post a complete RMDU later.

Looks like I made an error. The fixed data should be 48 26 00. I misread 0C as C0, hence the 03 for the first byte.

I got it by trial and error in RM. The algorithm is built in to RM, but I don't know what it is. Maybe someone with a better understanding of the protocol.ini entry or RM itself would know.

[Zibri]

No.. wait.

I already have fixed data!

I need the device and subdevice so I can generate pronto codes.

So:

1195 is: 0C 58 00 device? subdevice? e=?
0199 is: 04 00 E1 device? subdevice? e=?

(and how do you get the reverse mapping?)

Oh I think I got it..
it's reversed bits again..

So
1195 should be device 48 subdevice 26 E=0
0199 should be devide 32 subdevice 00 E=7 (but that gives 04 00 E0 while in the upgrade it is 04 00 E1)