Settings of built-in devices

[TiceRex]

Hi,

I have a question about RMIR/RMDU:
Is there any way to tell the settings (protocol, key maps, etc.) for a built-in device for any remote?

I can see a long list of built-in devices in the RDF under the [SetupCodes] section. How to tell their initial settings?

Regards, TiceRex

[mathdon]

Unfortunately no. RMIR can only read and interpret data in the user memory of the remote, what for historical reasons we call the E2 or EEPROM area, though in all modern remotes this is a dedicated part of the flash memory of the remote. This contains the full data for all installed upgrades but not for built-in devices. Even for those assigned to the various device buttons, it only contains their setup codes.

[The Robman]

Are you interested in any particular setup codes?

[TiceRex]

Thank you for the answers!

I'm still struggling with URC-7935 (using WDTV remote configuration) and Vero 4k (custom lirc setup).

These are the official, built-in setup codes for this scenario in the remote: 4440, 5077, 5245, 4666, 4170, 5645. None of them works perfectly, so I just would like to know if any of these contain any hints or differences on timing of NEC protocol.

EDIT: Sorry, I mixed it up. The list above is for the Kodi (native OSMC/Vero) devices, not the ones intended to be used with WDTV.
EDIT2: This is the only one device offered for the WDTV setup: 2558

(See my previous post on the same problem: http://www.hifi-remote.com/forums/viewt ... p?t=103027)

Regards, TiceRex

[TiceRex]

Update:

The built-in device 2558 works much better than the one I assembled.
Unfortunately it is missing some of the key functions/buttons I need.

Maybe somebody can help me, what could be wrong with these settings in RMDU:

Code: Select all

Protocol: NEC1
Protocol ID: 00 5A
Device: 132
Sub Device: 121
specialRecordKey: (empty)
NEC2 for repeat group: unchecked
send 2X then dittos: unchecked
Fixed Data: 20 DE 61

There must be some difference in the timings. At least I can't think of anything else.
The problem occurs on all buttons, not just with the repeating ones.

[The Robman]

CBL/2558 is NEC1 132.121, but you are right, there is a slight difference, the fixed data is "A0 DE 61" rather than "20 DE 61", which basically means that bit7 (the leftmost bit) of the control byte is set.

I am not aware of that bit controlling anything, and I can't think of a way to get RMIR or RM to let you set it. Even if you edit the raw data in either the RMDU or RMIR files and change the fixed data from "20 DE 61" to "A0 DE 61", if you open the file using RMIR, it will change it back.

The best that I can suggest for now is that you use the built-in setup code and program any missing buttons using keymoves.

[zaphod7501]

Just jumping in here because I had a WDTV live until it died, but there are a number of upgrade files for the device in the file section. I don't remember any problems using one of them. I can't check any of them anymore.

[The Robman]

TiceRex, looking into this further, I do see that we have many upgrades for the WDTV in the file section, and they're all almost identical. They all use NEC1 132.121, the only difference is that some have more button codes than others. The following file is one with a complete list of button codes:

http://www.hifi-remote.com/forums/dload ... e_id=10234

Try this and see if it works your WDTV without issue.

[TiceRex]

Thank you for the replies!

I've downloaded and tried all the files for the WDTV remote from the files section. They all contain more or less the same configuration and key assignments. All fail the very same way. Besides, I've tried several other JP1 remotes to the same result.

I think the problem lies deeper than that: it's hard to harmonize the protocol settings (and timings) in RMIR and lirc. In this sense I tend to think it's the fault of lirc (or Vero), not of the remotes (as we discussed it in the other thread above).

I'm kind of desperate, that's why I'm asking the very same question several times.

[mdavej]

Correct me if I'm wrong. But I thought lirc was designed to use any arbitrary IR as an input, which was simply mapped to computer keystrokes or commands. So there is no need to use the same protocol as the original device used. You can use any protocol you want.

[TiceRex]

mdavej
Exactly. I tried other protocols also (RC5, RC6) with the same result.
I've also replaced the IR receiver in the Vero unit (as it was suggested in the other thread), no improvements.

Now I dig myself into the kernel settings to get rid of lirc altogether, but it's still work in progress...

[mdavej]

Here's the official UEI upgrade for 2558:
http://www.hifi-remote.com/forums/dload ... e_id=26976

[pH7_jp1]

TiceRex

I have been watching and reading and I am not sure, but I think the following are correct:

You are trying to control a Vero 4k + device using your URC-7935.
You do not own an actual WDTV Live media player.

If the above assumptions are correct, then I think it's possible that people here could offer more useful solutions.

[TiceRex]

pH7_jp1
Yes, this is exactly the scenario.

I'm using the WDTV setup simply because once I had a WDTV, and I'm used to its keycodes, etc.

[The Robman]

Correct me if I'm wrong. But I thought lirc was designed to use any arbitrary IR as an input, which was simply mapped to computer keystrokes or commands. So there is no need to use the same protocol as the original device used. You can use any protocol you want.

mdavej
Exactly. I tried other protocols also (RC5, RC6) with the same result.
I've also replaced the IR receiver in the Vero unit (as it was suggested in the other thread), no improvements.
Now I dig myself into the kernel settings to get rid of lirc altogether, but it's still work in progress...

TiceRex
I have been watching and reading and I am not sure, but I think the following are correct:

You are trying to control a Vero 4k + device using your URC-7935.
You do not own an actual WDTV Live media player.

If the above assumptions are correct, then I think it's possible that people here could offer more useful solutions.

pH7_jp1
Yes, this is exactly the scenario.

I'm using the WDTV setup simply because once I had a WDTV, and I'm used to its keycodes, etc.

The above exchange has clarified so much. I'm in IT and when we're gathering requirements for a new project, the business often gives us requirements in the form of solutions (like "add a new button to this screen") and we have to push back and ask "why?" in order to get to the true requirement, because the solution that they're proposing might not be the best solution.

In this case, TiceRex was asking us to help him get his WDTV to work, whereas in fact, he doesn't even own a WDTV anymore, he just wants to use the WDTV upgrade to control something else.