New way to get MCE Remote signals in EG (for Vista/Win7)

[stottle]

Thanks for the links, I will take a look.

Brett

[civic5zigen]

I think the only receivers that have a 2nd detector are the ones that can blast. It doesn't look like yours does.
Brett

Is this answer directed to me? if so, may I know which model of the MCE remote are you using for my reference? Did you saw my reply on my attempts to try the pronto codes?

[stottle]

I think the only receivers that have a 2nd detector are the ones that can blast. It doesn't look like yours does.
Brett

Is this answer directed to me? if so, may I know which model of the MCE remote are you using for my reference? Did you saw my reply on my attempts to try the pronto codes?

No, that was directed at cgmark.

I'm confused as to how you are seeing blaster output in the EG log [that is, it looks like you have the transmit action in the log, but with IR events mixed in. Is the blaster attached to the TV, so that the MCE IR receiver doesn't detect it? Or are you somehow blasting into the MCE IR receiver. Can you describe your physical setup a little better? Also, you are not having the same problem Ronny had.

Brett

[civic5zigen]

Sorry for the confusion, below is the remote that I am using. Only one blaster is connected to the port 1 of the MCE receiver.



1. I am following your steps on page 13. First I point the Sony remote to the MCE receiver and hit the "menu" button. The IR event logged in EG is "MceRemote.SIRC12.00E0" and it is consistent everytime.

2. I add the MceRemote Transmitter as action in EG and press the learn button. Point the Sony remtoe to MCE receiver at close distance to and successfully completed the learn process.

3. I point the blaster to the MCE receiver, and hit the "test" button in EG to verify the learned IR code. Unfortunately it does not reproduce the same IR code of "MceRemote.SIRC12.00E0". Moreover, each test will produce not just one but several IR events in EG log like below...

Microsoft MCE Remote - Vista/Win7: Transmit IR: 0000 006C 0000 0051 005E 0015 0017 0017 0017 0015 0017 0017 0017 0015 0017 0017 002E 0017 002E 0017 002E 0017 0015 0017 0017 0017 0015 0017 0017 03F5 005C 0017 0015 0017 0017 0017 0015 0017 0017 0017 0015 0017 0028 001D 0024 0021 001D 0028 0015 0017 0017 0017 0015 0017 0017 03F5 0017 069F 0006 06B0 000F 06A4 005E 0017 0015 0017 0017 0017 0015 0017 0015 0017 0017 0017 002E 0017 002E 0017 002E 0017 0015 0017 0017 0015 0017 0017 0017 03F3 005E 0015 0017 0017 0017 0015 0017 0015 0017 0017 0017 0015 0030 0015 0030 0015 0030 0015 0017 0017 0017 0015 0017 0017 0017 03F3 005E 0015 0017 0017 0015 0017 0017 0015 0017 0017 0017 0015 0030 0015 0030 0015 0030 0015 0017 0017 0017 0015 0017 0017 0015 03F5 005E 0015 0017 0015 0017 0017 0017 0015 0017 0017 0017 0015 0030 0015 0030 0015 0030 0015 0017 0017 0017 0015 0017 0015 0017 0EFE
MceRemote.SIRC12.00E0
MceRemote.Unknown.15CE3A48
MceRemote.Unknown.53EFF8
MceRemote.Unknown.10203F40

4. Also I've point the blaster to the Sony TV and test the result. The Sony TV is not responsive to any of the learned IR codes.

[stottle]

@civic5zigen

It looks like from a hardware perspective, everything is working fine. That is, you can receive and transmit codes just fine. The problem seems to be in the learn function, and honestly, if the blast is sending the expected MceRemote.SIRC12.00E0 code (which is received from the real remote as well as the blast), that is working ok. The problem appears to be the extra pulses which are not understood.

One strange thing, I tried your code and only received two events - the MceRemote.SIRC12.00E0 one and one like MceRemote.Unknown.53EFF8. Do you have the transmit action triggered twice? The only other thought I had was reflections of the IR signal that are picked up as well. Is that possible?

That is a little beside the point. I'm wondering if the problem (like cgmark suggested) is that the receiver can detect a different frequency, but doesn't transmit at different frequencies. Not sure, but this is something that will take some work.

Brett

[stottle]

Ok, I tried mucking around with the code you posted until it was just the SIRC12.00E0. Here's the code I ended up with:

Code: Select all

0000 006C 0000 000D 005E 0015 0017 0017 0017 0015 0017 0017 0017 0015 0017 0017 002E 0017 002E 0017 002E 0017 0015 0017 0017 0017 0015 0017 0017 0EFE

See if that works for blasting. On my system that gives just the SIRC12.00E0 on both the MCE receiver and a USB-UIRT.

Brett

[civic5zigen]

Stottle,

Ive tried your hex code, while TV still unresponsive but the log in EG definitely improved. First, it only produce one IR event each time I press the test button. However, the IR event are still inconsistent and only produce the desire code occasionally like below

Microsoft MCE Remote - Vista/Win7: Transmit IR: 0000 006C 0000 000D 005E 0015 0017 0017 0017 0015 0017 0017 0017 0015 0017 0017 002E 0017 002E 0017 002E 0017 0015 0017 0017 0017 0015 0017 0017 0EFE
MceRemote.Unknown.12E41F80
Microsoft MCE Remote - Vista/Win7: Transmit IR: 0000 006C 0000 000D 005E 0015 0017 0017 0017 0015 0017 0017 0017 0015 0017 0017 002E 0017 002E 0017 002E 0017 0015 0017 0017 0017 0015 0017 0017 0EFE
MceRemote.SIRC12.00E0
Microsoft MCE Remote - Vista/Win7: Transmit IR: 0000 006C 0000 000D 005E 0015 0017 0017 0017 0015 0017 0017 0017 0015 0017 0017 002E 0017 002E 0017 002E 0017 0015 0017 0017 0017 0015 0017 0017 0EFE
MceRemote.SIRC12.0060
Microsoft MCE Remote - Vista/Win7: Transmit IR: 0000 006C 0000 000D 005E 0015 0017 0017 0017 0015 0017 0017 0017 0015 0017 0017 002E 0017 002E 0017 002E 0017 0015 0017 0017 0017 0015 0017 0017 0EFE
MceRemote.SIRC12.00E0

What is more interesting though, is that I discover EG will log IR event even when the MCE blaster is not pointed directly to MCE receiver. In fact, I cover up the blaster with my palm completely, and EG still log the event when I press the ÔÇ£testÔÇØ button. It only stop logging when I unplug the blaster from the receiver.

[ebiel]

Stottle,

I just want to thank you for your great work! I used eventghost w/ an MCE remote on WinXP but after moving to Win7 my setup did not work anymore - until I installed your MCE remote Vista/Win7 plugin. Now, it works like a charm Your work is very much appreciated!

[EricJD]

I've been getting lots of involuntary double button presses when using this plugin. Is there a way to fix that?

[copota]

First, I'd like to thank the dev for this plugin.

Now, I'm not sure if I'm on the right track, but I've been having problems getting the "Jump if long press" action to work.

I posted a topic in the General support section, http://www.eventghost.org/forum/viewtop ... f=2&t=2422, though I think the problem might be related to the MCE plugin.

I'm using Win 7 x64 with the latest release of EG, and most everything works great with this plugin, except the jump function.

I installed EventGhost on a WinXP Virtual Machine, and tested the Jump action, and it worked as expected, which leads me to believe there's a conflict occurring with the win7 plugin. Or maybe it just has no support for long presses?

Any advice is appreciated. Thanks.

[stottle]

I've been getting lots of involuntary double button presses when using this plugin. Is there a way to fix that?

The plugin just passes the on/off pulse durations to EG for decoding. For the MCE remote codes, you should be getting MCE events without doubles. If you are using a different remote, the problem lies in the EG decoder which may not have a decoding algorithm for a particular brand.

Brett

[stottle]

First, I'd like to thank the dev for this plugin.

Now, I'm not sure if I'm on the right track, but I've been having problems getting the "Jump if long press" action to work.

I posted a topic in the General support section, http://www.eventghost.org/forum/viewtop ... f=2&t=2422, though I think the problem might be related to the MCE plugin.

I'm using Win 7 x64 with the latest release of EG, and most everything works great with this plugin, except the jump function.

I installed EventGhost on a WinXP Virtual Machine, and tested the Jump action, and it worked as expected, which leads me to believe there's a conflict occurring with the win7 plugin. Or maybe it just has no support for long presses?

Any advice is appreciated. Thanks.

The Win7 plugin works fine with longpresses. I would test with some other events, ideally one that you know is sent repeatedly, like left or right button on the MCE remote.

Brett

[copota]

ideally one that you know is sent repeatedly

That must be the problem. I figured any button from any remote would work with the long press action.

I tested it with other buttons and they appeared to work, for instance the mce FF and volume buttons, which worked fine, though the number buttons did not.

Yet, on my old original xbox remote, I tested most the buttons and most worked, even the number buttons.

So, I'm assuming that not all buttons will work with the long press action?

Anyhow, thanks for the input, and your fantastic work

[EricJD]

I've been getting lots of involuntary double button presses when using this plugin. Is there a way to fix that?

The plugin just passes the on/off pulse durations to EG for decoding. For the MCE remote codes, you should be getting MCE events without doubles. If you are using a different remote, the problem lies in the EG decoder which may not have a decoding algorithm for a particular brand.

Brett

I'm using a standard HP Media Center remote..

[cubii]

Thanks for this Plugin, works like a charm! with my hp mce receiver clone from Ebay (China) even blasting!