Technika LCD22-218

[roberthunt]

You should also notice that most functions are grouped together with other similar functions, the prime example being the numeric buttons that all appear together and in order. When you find the play button, for example, you will probably find that pause, rewind, etc are all next to it in the OBC list.

In fact they map 1:1 to the order on the remote (see the picture below). Every single EFC I discovered maps to a button on the remote, here is the final list of all the functions:

Code: Select all

OBC	EFC	Function

000	181	Standby/Power
001	185	Mute
002	183	ATV Mode
003	187	DVB Mode
004	180	DVD Mode
005	184	iPod Mode
006	182	1
007	186	2
008	053	3
009	057	4
010	055	5
011	059	6
012	052	7
013	056	8
014	054	9
015	058	0
016	117	"-/--"
017	121	Previous Viewed Channel
018	119	Teletext / Play/Pause
019	123	Teletext Hold / Previous Track or Chapter
020	116	Teletext Reveal / Next Track or Chapter
021	120	Teletext Index / Chapter Select
022	118	Teletext Display Size / Stop
023	122	Teletext Subpage / Fast Rewind
024	245	Fast Forward
025	249	Frame Step Forward
026	247	DVB Favourite List / DVD Disc Title
027	251	DVB Remove Favourite / DVD Disc Menu
028	244	DVB Add Favourite / DVD Zoom
029	248	DVB Select Nicam / DVD Eject
030	246	DVB Subtitles / DVD Subtitles
031	250	DVB Language / DVD Audio Select
064	165	DVB EPG Guide / DVD Repeat
065	169	DVB Channel Info / DVD A-B Playback
067	171	Channel Up / Up Arrow
069	168	OSD Menu
070	166	Volume Down / Left Arrow
071	170	Channel List / Select or OK
072	037	Volume Up / Right Arrow
074	039	Channel Down / Down Arrow
075	043	OSD Exit
076	036	Source Menu
077	040	Display
078	038	iPod Menu
079	042	PC Mode Auto Adjust
080	101	Channel Up
081	105	Channel Down
082	103	Volume Up
083	107	Volume Down
084	100	Channel List / Select or OK / iPod OSD
085	104	Aspect Ratio
086	102	Sleep Mode Timer
087	106	Cycle Picture Modes
088	229	Decrease Sub Bass
089	233	Increase Sub Bass
090	231	Cycle Sound Modes
091	235	Red Button
092	228	Green Button
093	232	Yellow Button / DVD Angle
094	230	Blue Button / DVD Chapter Intro

OBC	EFC	Function

128	189	Standby/Power
129	193	Mute
130	191	ATV Mode
131	195	DVB Mode
132	188	DVD Mode
133	192	iPod Mode
134	190	1
135	194	2
136	061	3
137	065	4
138	063	5
139	067	6
140	060	7
141	064	8
142	062	9
143	066	0
144	125	"-/--"
145	129	Previous Viewed Channel
146	127	Teletext / Play/Pause
147	131	Teletext Hold / Previous Track or Chapter
148	124	Teletext Reveal / Next Track or Chapter
149	128	Teletext Index / Chapter Select
150	126	Teletext Display Size / Stop
151	130	Teletext Subpage / Fast Rewind
152	253	Fast Forward
153	001	Frame Step Forward
154	255	DVB Favourite List / DVD Disc Title
155	003	DVB Remove Favourite / DVD Disc Menu
156	252	DVB Add Favourite / DVD Zoom
157	000	DVB Select Nicam / DVD Eject
158	254	DVB Subtitles / DVD Subtitles
159	002	DVB Language / DVD Audio Select
192	173	DVB EPG Guide / DVD Repeat
193	177	DVB Channel Info / DVD A-B Playback
195	179	Channel Up / Up Arrow
197	176	OSD Menu
198	174	Volume Down / Left Arrow
199	178	Channel List / Select or OK
200	045	Volume Up / Right Arrow
202	047	Channel Down / Down Arrow
203	051	OSD Exit
204	044	Source Menu
205	048	Display
206	046	iPod Menu
207	050	PC Mode Auto Adjust
208	109	Channel Up
209	113	Channel Down
210	111	Volume Up
211	115	Volume Down
212	108	Channel List / Select or OK / iPod OSD
213	112	Aspect Ratio
214	110	Sleep Mode Timer
215	114	Cycle Picture Modes
216	237	Decrease Sub Bass
217	241	Increase Sub Bass
218	239	Cycle Sound Modes
219	243	Red Button
220	236	Green Button
221	240	Yellow Button / DVD Angle
222	238	Blue Button / DVD Chapter Intro

[roberthunt]

Okay I managed to create an upgrade under the URC-7555 but because the key layout on that remote differs from mine it wasn't that easy to see what I was mapping. The good news is that the functions I mapped works perfectly and I was able to control the power, volume, channels and numbers.

How would I go about creating a remote definition for the URC-1660? I assume I could base it on the URC-7555 to some extent.

Thanks

[vickyg2003]

Robert, please remember to post your upgrade. There is NOTHING like this TV built into any UEI remotes at this time, so this will be very helpful to other Technika TV owners.

[vickyg2003]

A good place to start on your quest for a graphical interface for your remote would be to start with this thread.
http://www.hifi-remote.com/forums/viewtopic.php?t=8229

[WagonMaster]

Hi Robert and welcome to the JP1 forums!

I recently took over maintenance of the RDF/map/image files from Nils Ekberg and I'm in the process of getting a new release ready.

Okay I managed to create an upgrade under the URC-7555 but because the key layout on that remote differs from mine it wasn't that easy to see what I was mapping.

As you've seen, what you need is a proper image and map file for your remote to use with RemoteMaster (RM). Are you up to making a map file for it (using 'Map This!' (Windows-based, free) software)? If not, I can eventually make an attempt at it, but I might need you to describe the buttons which I cannot read or figure out from the remote's image.

If you do decide to make a map, please read this post about making maps for RM first. You should rotate your image into the "portrait" orientation, of course, and it should probably be resized according to that thread I linked to. It's really not too hard to make a map, actually. In fact, just a couple days ago, someone new created a map file for an entire (Dreambox) keyboard with virtually no problems at all.

If you or I can somehow make a proper map file for it, I'll gladly include it and your rotated/resized image in the next release.

As for the RDF, it makes sense to use the existing (with the v1.28 zip file of all RDFs) RDF with the '10751075' signature as your baseline. However, since the existing '10751075' RDF has been altered (but not yet released with the new set), I've uploaded the '10751075' RDF from the upcoming release in the "Diagnosis Area" for you to download and use as you best can. We really need someone to eventually assist you in determining the details about this remote (e.g. setup codes and protocol IDs that are stored in the remote) to generate a truly correct RDF, but that can wait for later.

Holler if you have any questions.... Good luck!

Regards,
Bill

[roberthunt]

Thanks for the helpful information, I have just started working on the map for this remote and I have a good photo of it. I'll move on to the RDF afterwards and let you know how I get on.

[WagonMaster]

Sounds great, Robert! Don't hesitate to holler for help on either the map or RDF. As you can see, there are a bunch of helpful experts here to "lean on" when needed.

Bill

[roberthunt]

I managed to create the map fairly easily, had a few problems getting the program to run on a 64-bit Windows 7 system but that's expected from a program designed in 1995. I labelled all of the keys with logical names and modified a couple of lines in the RDF file to get it into RemoteMaster.

The map is available in the files section: http://www.hifi-remote.com/forums/dload ... le_id=7560

This is the bit where I get stuck because my understanding is not yet deep enough to know what things I need to be changing in the RDF file. I am assuming a lot of the hard work was done initially when the URC-7555 RDF was created.

I created a few macros on my remote that make use of most of the keys and when I download the remote and view the macros in IR.exe I see the keys listed, a lot of them are correct such as the numbers and transport controls (play/pause etc.) but others such as the Sky+ specific ones (Box Office, TV Guide, Services etc.) appear as functions that are not part of my remote.

What is the next step?

Thanks

[WagonMaster]

I've checked out your map/image files with "Map This!" and they look and work great -- nice job! Assuming you have no objection, I'll include these files in the next release.

As for the RDF, first fix the "ImageMap=URC-7555.map" line to instead point to your new map file, if you haven't already done so.

Next, you'll need to fix up (add, remove, or modify) any of the assignments ('button-name=button-code') in the "[Buttons]" section. I'm hoping that someone with more experience and/or imagination than I have will jump in here and make a suggestion for the best user-friendly way to do that. (The way I'd do it is not at all user-friendly. ). I suppose you could do some manual keymoves using the '994' code and then inspect them under 'IR.exe' to get the button codes, but I'm not sure if that's the most efficient way to get the button codes.

As you might expect, the button names used in the map file need to match the names used in the RDF's "[Buttons]" section. In cases where that's not practical, the button code should be pre-pended to the map file's button name, but don't worry about that because I don't think your remote has any such cases.

Some of those other settings will be hard to know if they're correct or not. That's where one of the experts will have to jump in and assist.

Bill

[vickyg2003]

You don't want to remove buttons. This 2 device remote is really a 5 device remote. Any buttons that don't exist on the remote, are still there for use in macros. The other devices can be set up to control 3 more pieces of equipment.

Typically these two remotes will be combined into 1 rdf since they are the same internally.

[3FG]

Caveat: I'm no expert and the following is not imaginative. However, one task is to identify the button numbers so that they can be correctly labeled in the buttons section. As WagonMaster said, a way to do this is to manually (from the remote itself) do keymoves of each unknown button onto another known button. Use the first set of 994 instructions in mdavej's compilation to carry out the keymoves.

After downloading into IR, go to the Keymoves tab where you'll find the actual button code in the column labeled Hex Cmd. For example, if you keymove the Power button onto some other button, the Hex Cmd would be $03 **Key Code. Of course, you don't need to keymove the commonly named buttons, like vol +/-, mute, digits, etc. , because those buttons will already be correctly identified.

Under [buttons] in the RDF file, change the name associated with a key code to e.g. Box Office. If a key has the same function but a different name than is standard in RDF files, consider describing that. For example, if the Back Up button causes the TV or Cable box to revert to the previously selected channel, then describe that key as "prev ch":Back_Up. That will help make upgrade files to be more easily converted. But I don't know which names are actually standard.

ETA: The file RDFspec_R004.pdf, which is included in the IR.exe distribution, has good and importnant information. It does include a list of the standard Generic Names, and the rationale for using them.

[roberthunt]

Okay, thanks for the info, had a bit of a read through the RDF and the RDFspec_R004.pdf. I think I can handle the key mappings part, I'll have a play around with that shortly.

Back to a point raised by vickyg2003, would it be best for me to add support for the URC-1660 to the already existing RDF for the URC-7555 as they share the same signature? If I did that what would happen when I get to things such as Learning because the URC-7555 supports that and the URC-1660 does not. The alternative would be to create a copy of the RDF with the same signature but only for the URC-1660.

UPDATE:

I think I've got all of the key addresses now.

Code: Select all

BUTTON              ADDRESS

Power           =   $03
TV Device       =   $01
SAT Device      =   $11
TV Guide        =   $2d
Box Office      =   $2c
Services        =   $22
Interactive     =   $23
Volume Up       =   $04
Volume Down     =   $05
Channel Up      =   $06
Channel Down    =   $07
Up Arrow        =   $31
Down arrow      =   $32
Left Arrow      =   $33
Right Arrow     =   $34
Select          =   $35
Mute            =   $08
Back Up         =   $2b
Info            =   $29
Teletext        =   $13
Teletext Off    =   $14
Aspect Ratio    =   $24
Help            =   $2a
Rewind          =   $0b
Play            =   $0c
Fast Forward    =   $0d
Stop            =   $0e
Pause           =   $0f
Record          =   $10
Red             =   $25
Green           =   $26
Yellow          =   $27
Blue            =   $28
1               =   $15
2               =   $16
3               =   $17
4               =   $19
5               =   $1a
6               =   $1b
7               =   $1c
8               =   $1d
9               =   $1e
0               =   $1f
Magic           =   $02
TV/SAT          =   $21 

[mr_d_p_gumby]

The alternative would be to create a copy of the RDF with the same signature but only for the URC-1660.

That would be a good choice if the names of the buttons on your remote are different from the URC-7555. If the button names were the same (or a subset), then a common RDF would work. (There is no mechanism for the RDF to display a different set of button names for each remote in a common RDF.)

[vickyg2003]

Back to a point raised by vickyg2003, would it be best for me to add support for the URC-1660 to the already existing RDF for the URC-7555 as they share the same signature? If I did that what would happen when I get to things such as Learning because the URC-7555 supports that and the URC-1660 does not. The alternative would be to create a copy of the RDF with the same signature but only for the URC-1660.

Typically these are put together in the same RDF.

Learning:
Although the remote won't learn, you can copy a learned signal from another remote and it will send the signal. I do this all the time, when I help people with protocols. I copy their learns to my nonlearning atlas and shoot the signals at my widget. The learning memory can also be used for upgrade overflow.

Phantom Devices:
Although your remote only contains 2 device buttons, you can access the other 3 devices via the phantom VCR=$09, DVD=$0a, and Amp $12 buttons.

[roberthunt]

(There is no mechanism for the RDF to display a different set of button names for each remote in a common RDF.

In that case I think it makes sense for it to be a separate RDF, whilst the URC-1660 shares the same signature as the URC-7555 some keys have differing names because the URC-1660 is a remote for a very specific device (Sky Satellite Boxes).