X10 remote (mapping question) (1 Viewer)

[j1nx]

Correction: The Power button also don't work with the ATI file??

I think this is a driver issue, because it always worked as a "ALT+F4" combination.

Anyway, with the driver from the link in the setup it doesn't so another useless button!

 

[captainspanky]

mPod -

That pastebin thing doesn't allow enough chars to put it all in there... so I put the files up onto a geocities webspace... If there's any trouble getting them let me know and I can email them.

http://www.geocities.com/diablomadman/MediaPortal_Firefly_Keys.log
http://www.geocities.com/diablomadman/firefly.jpg
http://www.geocities.com/diablomadman/Other_X10.xml

The jpg is taken from the snapstream site for now. When I get my hands on a digicam I'll take anotehr shot w/o that little arrow.

For the keys file, I went left to right across the rows and down the remote. I opened up the .log file and edited out all the non-x10 key stuff.

For any other Firefly users out there who want to use my Firefly setup until mPod does his thing, you can

1. grab the Other_X10.xml file, put it into Mediaportal\InputDeviceMappings\Custom,

2. Rename the file so that its Other X10.xml (remove the "_"... geocities wo't allow spaces and i'm too lazy to find another webspace when this is handy)

3. Go to the X10 Remote tab from the Remote section of the configuration / Setup Mediaportal utility and choose the 'other' radio button.

4. Ok to save and you should be good to go.

Glad I can actually contribute something. Let me know if you need anything else. I'll get a replacement photo going in the next couple of days and update it.

 

[CoolHammer]

j1nx, do you use drivers that came with your remote. If you do i suggest to try drivers that link on configure app points to. That driver is "general x10" driver. I managed to remap all ATI rw1 buttons with that driver.

CoolHammer

 

[j1nx]

j1nx, do you use drivers that came with your remote. If you do i suggest to try drivers that link on configure app points to. That driver is "general x10" driver. I managed to remap all ATI rw1 buttons with that driver.

CoolHammer

I use the drivers linked from the setup page (Mostly all other drivers out there even work with the same x10net.exe file anyway)

Normally i used the drivers from "the mouseremote" software from marmitek.

Now i have only the reccommended drivers installed. Maybe the power button is just broken, i have to test it somehow, but for now; Don't fix if it aint broken.

 

[j1nx]

mpod, how is it going?

I saw a lot of activity on the input device mapping, but didn't saw my marmicrap remote appearing in the remote setup.

Is it still planned to included or not?

 

[mPod]

still on the list

 

[j1nx]

still on the list

OK, First things first.

success, you all doing a great job finishing up 0.2 final. SVN is already as stable as hell, tried to crash it yesterday, but didn't succeed.

You guys are getting there

 

[NLS]

mPod I'll do that for you (now)

EDIT: AH! Just saw the second page.
I replied to the last post of the first page.

Anyway, I have a few notes on the Marmitek (that I also have).

1) Power button does send a signal.

2) ALL buttons send a signal (even those that "shouldn't" like "TV" that yes switches to TV but first sends a signal).

3) S is shift and gives many of the buttons a second mapping

4) All mappings have an "up", "down" and "repeat" signal, at least in Girder.

I'll now do the thing with the dummy X10 file and get back to you. I hope we can add a "Marmitek" in the X10 list in some future SVN.

I tried to map the "hand" and "AV" myself in configuration.exe, but they don't work. (I hear the wav but nothing happens)

 

[j1nx]

3) S is shift and gives many of the buttons a second mapping

You are kidding? If this is true, more doors open in front of me :lol:

 

[NLS]

doors? hmmm not really

see my next post