You cannot upload a patch to the empeg, you need a full kernel for that. The patch is for recompiling a new kernel. Grab the kernel-image from my site, unpack it using winzip and upload it to the empeg; that should be sufficient...

Frank van Gestel

Thanks Frank

Technoweenie
12 GB Blue / Red MK2

My idea was to use add_timer in the case a code is received that should be translated. When the second code arrives, the timer is checked for expiration. This would allow a second parameter in the config file to set the delay time.

Was this idea ever realised? The Volume Control on the pioneer remote is still somewhat slow. Not a major PITA, but a small one.

Not from the config file, no. I haven't got 1.02 by hand right now, but I will create a 1.03 version next week. You could set the delay in the patch file and recompile the kernel though. I think I set it to 200ms. Has anyone tried the patch, changed the timeout and recompiled?

Frank van Gestel

I haven't got 1.02 by hand right now, but I will create a 1.03 version next week.

This is the second time I have seen someone act as if 1.03 is out. Did I miss something?

This is the second time I have seen someone act as if 1.03 is out. Did I miss something?

Heh, no, Frank's just jumping the gun. He's an alpha tester, you see, and he's currently got his hot little hands on one of the 1.03 releases.

I don't think any of us got any sort of expected timetable on 1.03 final, so Frank's probably being optimistic about when the rest of the world would need the 1.03 version.


___________
Tony Fabris

So, I've picked up the CD-SR80.... and I'd like to know how to determine what codes it sends... My only real IR hardware is my Palm (Kyocera 6035 Phone)... Omniremote. Is this enough?

Thanks,
Douglas.

(Now my car radio runs Linux, and my cellphone runs PalmOS... what next?)

If it sends IR codes that the empeg can understand, you can "read" the values with Frank's IR-Trace program. It writes the Decimal code to the Terminal (STDERR, right?), or you can use a shell script and Blitecho (also Frank's) to write the Decimal codes to the empeg display. Once you know the codes, you can remap them to the empeg's remote buttons with Frank's IR-Hack Kernel (He's been busy, hasn't he? ).
That is, only if the IR Freqs are compatible.
I've done this same thing with my remote, so if you need help, let us know!
Jason

_~= Dearing =~_
"WAY too happy about having #99."

Okay, I'm doing this the hard way... But I'll have the codes for the SR80 shortly. (Talk about pulling yourself up by your bootstraps... I used to know how to use Linux. Evidently I forgot.)
-
Douglas

I have a cd-sr77 and franks kernal which maps only 5 buttons could some one either give a complete moron guide to compiling a kernal what ever that means with extra buttons or map one for me and i can then upload it to me empeg.

Thanks

I didn't know there was such a limit on IR_Trans? Do you mean that your empeg_irCodes (Or whatever file is being cat'ted to /dev/ir) only contains 5 remappings? It's my understanding that you can remap any codes you want, one per "OEM Remote" button. All you need is to write more lines to the IRCodes file. How many buttons does the SR77 have?


_~= Dearing =~_
"WAY too happy about having #99."

Paul,
didn't you receive my email? I'll put a new kernel up this weekend...

Frank van Gestel

Thanks frank you are a hero i got an email but couldn't find any words in it but i am a computing moron

I've gotten things going, and now need real help.

First: IRdump is giving me output I can't translate. See below. How does one map from this data to the codes shown above? Second: I can't get the empeg to respond to IR other than directly and closely in front of the receptor. This is with the two car remotes, and my home receiver remote (something I know has perfect batteries and great range.) I've never really used the remote before, but I can't imagine any wheel remote position working... Any ideas/suggestions?

Many thanks,
DM.

empeg:/empeg/bin# irdumpex (Kenwood Volume Up)
>80493add<
>c0000169<
>8001614c<
>c000025f<
>800bd019<
>c00001df<
>800055c8<
>c0000141<
>80001467<
>c000019e<


empeg:/empeg/bin# irdumpex (Pioneer SR80 Volume up)
>80ac8038<
>c0000091<
>8008f9b6<
>c000009a<
>800c3368<
>c000007d<
>801ed0c7<
>c00000a4<

I'm not familiar with IRDump, but is it returning the "Raw Mode" signals? If so, try not using Raw Mode, and just get a single Decimal value for each button press.

_~= Dearing =~_
"WAY too happy about having #99."

I've made two new 1.03 kernels : one which has default codes from lars (wire) for the cd-sr70 and one for the cd-sr77, with default codes from paul (thinfourth). It's got multiple timers, so you can set a timeout per code. Default timeout=100ms. syntax of inputfile:

# comment line; required; do not delete

[old code]:[new code]:[repeat interval in ms]

[old code]:[new code]:[repeat interval in ms]

[old code]:[new code]:[repeat interval in ms]

[old code]:[new code]:[repeat interval in ms]

etc..

kernels can be found here
I will try to setup a more complete package in the near future...

Frank van Gestel

frank,
I have REALLY fallen behiond on this. Am i to take it that the timing issues are now resolved?

What about a complete idiots guide to setting up the keys propoerly, for those of us that are to thick/have no time to figure this all out.

I appreciate all of your work on this, i was one of the original people bitchign about it. I have been enjoying that remote now for some time, and i just wante dto also say , thanks.

timing issues should be solved. You can create different timeouts for different buttons, which is kind of funny: set up 100ms for volume up and 10 seconds for volume down.
I've created a 1.03beta3 subdir on my site with a modified readme, which should be sufficient to get you going... It also explains what the default button mapping is...

Frank van Gestel

Excellent frank it works like a dream

Thanks as always for your brilliance

timing issues should be solved. You can create different timeouts for different button

Thanks Frank, much apreciated.

frank, i have some problems.

In the first rev which i had.. i think it was 1.02 i could use it ok, teh timing was fast for the next/previous button.

Now that i installed the 1.03 patched kernel, it is only accepting one button hit per like.. 2 mins. I installed it as you ahd it... is this a timing issue? I sorta thought it might be a low battery, so i replaced it, but it wasn't that.

FWIW same thing happened in version , but not as frequently. It seems like the more it plays the more confused it gets. I have no probs with the stock remote.
Any thoughts>?

nothing?

kindof busy...
Reply tomorrow. First sleep...

Frank van Gestel

thanks, when youg et a chance, just curious. could it have corrupted some sort of a data file ncessary duiring the upgrade?

Well, it seems I have been sleeping more than one day
I will patch the beta6 source and include the source patch, maybe I'm doing something stupid with the timers...
Are you using the kernel with or without the empeg_ircodes file?
The default kernel without the empeg_ircodes should provide you with a default button-mapping.
I've tried the empeg_ircodes file with 15 mappings for my home-remote without problems...


Frank van Gestel

Thanks Frank for your ongoing efforts, I look forward to your new patch too. I have been without my remote for three days now and it's killing me ha ha.

Technoweenie
12 GB Blue / Red MK2

i am using the 1.03 as it was in default config. It is just strange because this problem was present from teh word go, but just no where near like in the 1.03 kernel. i honestly can only get about push every 2 mins or so right now.. i wonder if something got hatcheted in my upgrade, maybe i will redo it.. thanks for your help..

Wait a few days for my new kernel; the 1.03b6 IR-code has significantly changed and timers aren't necessary anymore. I've got my universal remote to simulate a pioneer remote, so I know now why the timer hack wasn't workable.

Frank van Gestel

wow , thanks frank, you rule, as usual./

why not just wait till 1.03 final next week :)