Emulate URC7740

Infrared Transceiver
#35

Good work, guys. Even if it don’t work, we can compare the results.

The most important information for me is in here:

The original remote from IRDB shows the following values:

protocol: SIRC20
address: 5A 1C 00 00

Yours is showing

  • 1533.ir
protocol: SIRC
address: 00 00 00 00
  • Take2.ir
protocol: SIRC20
address: 3A 09 00 00

Let’s say the address is the field, to avoid devices nearby will get the commands. so the BD device will only listen to a specific address. We should take the known address: 5A 1C 00 00 and the new command:s from your remote together in one file.
I would also go with protocol: SIRC20 here.

As you, @emptythevoid, already found out, the 0533 (1533) code could be for the protocol. Is there a list or something?
I’d like to try change to the NEC protocol and compare the command: at buttons 1 2 3 4 5. If they are different, we maybe need to change to RAW dumps instead of parsed ones.

#36

Here’s the manual to the version of remote I have: https://www.urcsupport.com/wp-content/uploads/2020/11/urc7880_manual_en.pdf

You’ll notice that the manual doesn’t list any device codes, but it has preset buttons you can hold in that, presumably, do the same thing. That said, the fact that it accepts the codes I’ve put in from here Sony DVD codes for OneForAll universal remote controls suggest that the device code method does still work.

This silly page OFA Smart Control 8 (US) URC7880 – URC Support is able to give device codes (specific for this remote?) for various devices. I’ll try a few here in a bit. If you happen to look through this, let me know if there’s anything you want me to try. I’ll see if I can find a device code that returns NEC.

#37

First try lucky - device code 3519 (Hisense) is showing up as NEC (and turned on my Vizio TV, while I was testing it. I’ll get you the full capture.

#38

Interesting. The remote has a button that lets you switch devices (TV, set top box, blu ray, etc). It seems that you need a combination of the correct device chosen and the device code. What I mean is, the device code 3519 doesn’t even register if I try to program it to something other than TV on the remote. It does a slow blink instead of two fast ones. This is the same behavior I experienced trying to set up the 0533 code initially. This remote is weird.

Edit 1: I’ve made a folder of various captures (power button and 0-9) for various device codes. The files are named in this manner:

Device type as chosen by the remote_device code_protocol detected by Flipper

Edit 2: I’m just throwing all my notes here, instead of constantly updating this post: flipperzero/infrared/experimental_sony_unlock/README.md at main · emptythevoid/flipperzero · GitHub

1 Like
#39

Thanks! I’m going to review your notes. I greatly appreciate you sharing!

This is interesting. It seems as long as the protocol is SIRC or SIRC20 0189 is always the same command. In Samsung32 it appear to increment by 1.
DVD set up as code 1633, button 1 key magic 00189 = SIRC A:0x00 C:0x7F
DVD set up as code 1516, button 1 key magic 00189 = SIRC A:0x00 C:0x7F
DVD set up as code 4009, button 1 key magic 00189 = SIRC20 A:0x12FA C:0x7F
DVD set up as code 0864, button 1 key magic 00189 = SIRC20 A:0x0A7A C:0x7F
DVD set up as code 1033, button 1 key magic 00189 = SIRC A:0x00 C: 0x7F

DVD set up as code 0741, button 1 key magic 00189 = Samsung32 A:0x2D C:0x80

1 Like
#40

This is fun! Although I’d love it if we solve it.

I observed that, as well. Let me know what other data I can gather. I can do raw, too.

1 Like
#41

Guys, I’ve made a mistake.

The whole time I’ve thought ‘reverse’ means 01011 to 11010. But instead it means a logic inverse: 01011 to 10100.
Dammit, in all testcases the ‘false reversing’ worked, because for example 11110000 is reversed 00001111 in both calculations.

2 Likes
#42

how can I help now ?

2 Likes
#43

I’m about to write a protocol analyzer at the moment. Until than I have no further idea.
Except to correct the false reversing approach above. I’ll try this evening to create a new .ir file.

2 Likes
#44

As promised, the next try:

Filetype: IR library file
Version: 1
# 
name: POWER
type: parsed
protocol: SIRC20
address: 5A 1C 00 00
command: BA 00 00 00
# 
name: POWER
type: parsed
protocol: SIRC20
address: 5A 1C 00 00
command: FF 00 00 00
# 
name: POWER
type: parsed
protocol: SIRC20
address: 5A 1C 00 00
command: 5F 00 00 00
# 
name: POWER
type: parsed
protocol: SIRC20
address: 5A 1C 00 00
command: D3 00 00 00
# 
name: POWER
type: parsed
protocol: SIRC20
address: 5A 1C 00 00
command: 4F 00 00 00
#

I am pretty sure the address don’t need to be reversed. But I let this here for completeness.

The new calculation is:

        #sserdda = format(int(((bin(int('1'+btnaddr_arr[0], 16))[3:])[::-1]), 2),'X').zfill(2)
        #dnammoc = format(int(((bin(int('1'+btncomm_arr[0], 16))[3:])[::-1]), 2),'X').zfill(2)
        sserdda_bin = ''.join(['1' if i == '0' else '0' for i in bin(int(btnaddr_arr[0], 16))[2:].zfill(8)])
        sserdda = hex(int(sserdda_bin,2))[2:]
        dnammoc_bin = ''.join(['1' if i == '0' else '0' for i in bin(int(btncomm_arr[0], 16))[2:].zfill(8)])
        dnammoc = hex(int(dnammoc_bin,2))[2:]
2 Likes
#45

I’m still thinking about this. I’d like to get (what I guess is) a more compatible remote and a similar Sony unit to test here. My play money has been exhausted lately, so it may be a bit. I would love to be able to find these codes and make the .ir public - that would be a very practical (if slightly obscure) thing to have.

I’m open to other ideas, if someone thinks of something in the meantime.

@BTONO, what region are you actually in?

Edit: I have something coming in the mail.

1 Like
#46

I don’t think another remote is needed. The task is to understand the coding.

Within one protocol, we have 3 dimension:

  • The address - related to the device (type)
  • The command - related to the action
  • The button - Not relevant at all, but helpful, because we’ve had 9 tries per programming session.

Programming Sequence

  1. DVD + 0533 (Is DVD already related to the address? Is 0533 a internal code for the remote, or the address within the DVD address set?)
  2. 994 (seems to be a internal code)
  3. 1 + 00189 (Set 00189 to the button 1)
  4. 2 + 00255 (Set 00255 to the button 2)
  5. 3 + 00095 (Set 00095 to the button 3)
  6. 4 + 00221 (Set 00189 to the button 4)
  7. 5 + 00079 (Set 00189 to the button 5)

Alter the programming sequence

What happen If we press TV instead of DVD at 1.?
What happens to the signal, if we change step 1. to 0534?
What happens to the signal, if we change at step 3. 1 to 00001, 2 to 00002, 3 to 00127, 4 to 00128, 5 to 00256?

Hypothesis

With this information we can analyze the behavior and maybe get how the ‘AllForOne’ remotes will work, to build our own, compatible.

2 Likes
#47

I have some data, based on what you asked for.

Two different device codes with various “994” codes:

A small chart of different ‘994’ codes but only within the 1533 device:

Observations:

-Only certain Device Codes are allowed for what the remote is set to (TV, DVD, etc). Specifically, I cannot use the device code 1533 when the remote is set to TV. It only works when it’s set to DVD.

-As mentioned, my remote does not accept 0533 as a valid device ID for any device type. Given my research into different One-For-All remotes, I think this might be a region thing. The one I have is specifically for the US and it lacks 0533 according to Sony DVD codes for OneForAll universal remote controls We can speculate that we can use the protocol and address as identified by the OP, but this is not guaranteed (see further below)

-When entering the 994 codes (00189, 00255, etc) it does not appear to matter which button (1, 2, 3, etc) it’s assigned to. The same code can be assigned to multiple buttons.

-The Device code appears to set both the protocol,address space, and (default) layout of commands.

-The ‘994’ codes appear to modify and override the existing Device code (Device 0534, code 00189 is a different protocol and address and command than Device 1533, code 00189)

-However, it appears that the ‘994’ code can change the protocol (somewhat) and the address space, too (Device 1533, code 00004 seems to alter what would be SIRC20 to just SIRC, with a different address)

-There appears to be some overlap with some of the 994 codes (00256 and 00001 seem to both return the command 0x62)

2 Likes
#48

Also, I’ve not seen device code 1533 plus a 944 code change the protocol to something completely different, like NEC. So far, all my tests within device code 1533 are either SIRC20 or SIRC.

1 Like
#49

@BTONO Hey friend, if you’re still around, give this ir file a try.

https://raw.githubusercontent.com/emptythevoid/flipperzero/main/infrared/experimental_sony_unlock/Unlock_0533.ir

It looks almost exactly like the one I had with the other URC remote, except all the commands are SIRC20 address 3A 09 00 00

Edit: I looked over my notes. I think the codes are exactly the same as device code 1533

2nd Edit: when you’re testing these region unlocks, you’re testing it with a DVD, right? The unlock is only good for DVD playback. It has no effect on blu-ray discs.

1 Like
#50

I came across a post that suggests this hack only makes models from certain regions region free.

#51

I was suspecting this as well. I never did hear back what region OP is in. Do you have the link? Will be useful to add to my notes.

Edit: I think I found it.

1 Like
#52

I feel confident that I can report that this procedure does not work on the US (region 1) model. This is backed up by the website(s) that @jmr and I came across.
With the coding as indicated by the programming instructions, the US model does not even respond to anything at all. If I modify it to use the address of @BTONO 's remote, I can control the player, but the special buttons only result in the unit turning on at the end of the procedure.
I’d love to test this on a region 2 unit, but I think obtaining one would be prohibitive for me.

#53

This is a bummer.
Even if the way until this discovery was fun. Thank you guys for the nice working together at this experiment! Maybe one day someone else from another region will got us the proof.

1 Like
#54

Jeez I’ve missed a lot. Sorry I was swamped and now I’m away from home (California) for the next 2 weeks.
I’ll get back on it as soon as I come back.
If one of you is not too far out I can also consider sending the player if needed.
Thank you so much for your patience and work.

1 Like