Hijack v59: IR translations in config.ini

Okay, hijack v59 is now out.

This version of Empeg addons now includes built-in IR translations, configurable entirely by using Emplode to edit config.ini. No more user app's, boot menus, ioctls, whatever..

Just install v59, use the "Button Codes Display" screen to figure out the data sent for each button of your non-Empeg remote control, use the same feature to figure out the corresponding empeg codes (from the Kenwood or Rio remotes), and then enter the data into config.ini using Emplode. Sync, and voila.. all should be well.

Or at least that's what happens when I use it here.

Full instructions at the website: http://rtr.ca/empeg/

-ml

The FAQ now links your page, under the Car Installation section where steering wheel remotes are discussed.

Ooops.. v60 allows comments after the IR codes in config.ini,
but also has a bug that causes all but the first translation to be ignored.

This is fixed in v61, along with the bug that prevented access to the Fader pop-up when using short-knob presses.

v61 is out now!

-ml

PS: Calvin, what did you have for lunch?

Cool beans!

Calvin

Okay v62 is out.

This version has some fixes for the long-knob-press function (switching sources), to keep the hijack menu from getting confused. Also new is "clear screen before reboot", cuz my new Rio Mk2a didn't do that when downloading a new kernel!

I'm outa here. See you folks whenever (Comdex?)

-ml

Lamp rubbing time: can we map one key on the 'foreign' remote to a sequence of 'native' keys? I found an old DVD remote with myriad of keys that is 'heard' by empeg. I would like to bind some left over keys to 'macros', eg. 'menu/ok', '4', 'menu/ok' (= visuals menu).

Ok, the knob button press fader bug is fixed but now I'm getting a fader as an option on the home personality. Is this right? I don't recall the original functionality.

Calvin

now I'm getting a fader as an option on the home personality. Is this right?

Yes, for 2.0b3 this is expected. They intend to remove it on a future release. I thought they had in an interim beta5 that you guys haven't seen yet, but I guess I was wrong.

Sir Mark, Unbelievable!

But a couple of things.
I can't get it to work on my Mark I. Aside from the other remote not working it also disables the mapped keys on the Empeg remote as well.

Two, will I be able to use more than one remote by mapping all the remotes codes into config?

>But a couple of things.
>I can't get it to work on my Mark I.
>Aside from the other remote not working it also disables
>the mapped keys on the Empeg remote as well.

Huh? Oh well. Email me and I'll look at it in a few weeks (maybe sooner).

>Two, will I be able to use more than one remote
>by mapping all the remotes codes into config?

Yup. That's the idea! Works for me.

-ml

>Lamp rubbing time: can we map one key on the 'foreign' remote
>to a sequence of 'native' keys?

Yes, just not in the current release. I want this "macro" capability too, but just ran out of time to implement it today (heck, just getting the IR stuff out today was unexpected).

I fully plan to implement macros when I'm next near my Empeg (a week or few...)

Cheers

>Aside from the other remote not working it also disables
>the mapped keys on the Empeg remote as well.

Maybe you have the syntax reversed? The correct format is:

[ir_translate]
;newremote:oldremote comment

Exactly. It was reversed. Let me try it again.

So I can use more than just one remote, right?

All hail Sir Mark. For services to the In Car Entertainment empeg World.

A monumental effort, 62 releases in a few short weeks. You deserve a holiday!

That was what it was.

Sir Mark. You are my idol!

Thanks! Have fun on vacation!

>So I can use more than just one remote, right?

Right! (Yes!) (Oui!) (Si, signore) ...

You are my KING! I have wanted the IR remapping feature for so long. Thankyou!!!

I can now use my Alpine remote with my Empeg. I have an Alpine CVA-1000 in my truck. I use the Empeg as a second unit there. I switch the Alpine remote to NAV and work the Empeg. Flip it back to work the Audio. I can still use the Rio remote. I also use the Empeg in my Mountaineer as my main audio source. A complete setup now that I have radio. I can now leave my Rio remote in that vehicle(less chance of loosing it.)

Of course, if I loose it now, who cares. Pick up any other remote and reprogram.


THANK YOU>!!!!

Hello Mister Hyper Mark,

I found a little bug from millions of features with V62! If I have the Empeg in the Tuner Mode, then the Reboot does not work. This means I have to put out the device from the mounting and then back.

Maybe someone can confirm that.

Thanks!

great stuff !
I am currently thinking about if it would be possible to interface a whole IR keyboard (not to emulate a remote control rather than emulating a "real" keyboard) ?

bobo

Is there any way i can use this to reconfigure the buttons on my original remote ?
I want to reprogram my Kenwood remote on my MK1.
especially change the 1 to work as hush.

>Is there any way i can use this to reconfigure the buttons on my original remote ?

Yes, the usual method for IR translations in hijack will work for the "original" remotes as well.


>I want to reprogram my Kenwood remote on my MK1.
>especially change the 1 to work as hush.

That would be trickier.. hush is a "press and hold" function, isn't it?
My IR translate stuff has not (yet) got the smarts to implement "press-and-hold" translations yet. Maybe by Christmas.. (big job).

But multi-key macros are currently being tested here...

-ml

>thinking about if it would be possible to interface a whole IR keyboard

Yes, this is very possible. But it would also require including console support in the kernel, and implementing a text-mode framebuffer driver (not too hard, most of the code is already in hijack).

If I had an IR keyboard here, it would probably appear as a hijack feature in very short order..

-ml

>I found a little bug from millions of features with V62!
>If I have the Empeg in the Tuner Mode, then the Reboot does not work.

I think I see the bug .. forgot to mask interrupts when rebooting in v62.

I'll fix it (hopefully) in the next version.

Cheers

-ml

Thanks!

What sort of IR keyboard could be supported?
Do they run IrDA or something else? Seems like most
have a mouse-function as well.

http://www.casco.com/861ir.htm
This for instance, looks small and cheap (can it be bought in europe?). Any other suggestions?

Marius (Escort Cab + Mark II)

Or... if everything else fails... Support for this device?
http://www.tekram.com/Hot_Products.asp?Product=IR-660
Unfortunately requires 9V, but gives ethernet-connection in return, and is supported by Linux-IrDA

Marius

The Casco should work now. It is on 38Khz freq. The Empeg uses fuzzy logic for the text entry when searching. So the keyboard needs nothing special. When naming things, you would have to remap the keys(using the macros) to get exactly what you want. It should work.

By the looks of it the Tekram unit might require further additions to the Empeg software.

Sooo... What you say is that the keyboard(s) use the same consumer-IR protocol as the remotes? Like a normal remote control with a lot of buttons?

Does this apply to all such keyboards (the casco one does not seem to be available in Denmark)? All such keyboards with 38kHz Frequency? I seem to recall a recent posting about the remote protocol being "RC 5" or something like that, and that everything else is screened. Or is this just referring the 38kHz frequency?

If "we" find a keyboard that is suitable and affordable, I'll buy a couple and mail one to mlord.

Marius (Escort Cab + Mark II)

The Empeg has two types of Infrared reception. One is used to accept command from remotes. Any remote that operates in the 38-40Khz range should be seen by the Empeg. And therefore with Hijack should be able to be used. The Empeg also has a IRda port. At this time this is not used(by most). The IRda port will allow two way communication. So any device that uses this port will have to have additonal software installed to send the commands on to the player app.

Now I am not the expert on this, but that is the way I think it all works. Someone chime in if that is not all correct.

http://empeg.comms.net/php/showflat.php?Cat=&Board=empeg_general&Number=45036&page=1&view=collapsed&sb=5&o=&fpart=all

This thread was what worried me... But now, I see that it is possible with some more work... :-) I don't think we can get hold of a proper IrDA keyboard, not the "normal" IrDA standard anyway.

Marius (Escort Cab + Mark II)

I wouldn't be too discouraged by that thread.. If I had an IR keyboard here that was compatible with the Empeg's IR sensor, then the RC5 "hurdle" would not really be an issue. At present, though, I have no such beast. I might look for one over Christmas, though.. we'll see.

-ml

I'm actually having quite a lot of trouble finding somewhere to buy one... I found *one* shop in norway, they only had a 56kHz version, and one in Switzerland, withouth any info about the frequency...

Marius (Escort Cab + Mark II)

I tried to get some IR codes from a generic keyboard i had laying around in June, but i quickly realized i was in over my head after using Franks trace_ir program. The empeg did see the keyboard though. When i get home i'll dig it out and post some specs if it would help.