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

[stottle]

Ok, Ronny, let's see what we've got here.

But unfortunately it isn't working.

When I load the plugin and then add the action Transmit IR and then click the button Learn an IR code, I do what is mentioned in the message window.
Then I get a pronto code, for example:

Code: Select all

0000 0073 0000 0018 0148 00A2 0016 0012 0017 0012 0016 0012 0017 0012 0016 0014 0016 0012 0016 0014 0016 0012 0016 003B 0017 003B 0016 003B 0016 0017 003B 0016 0014 0016 003B 0016 0012 0017 003B 0016 003B 0016 003B 0016 003D 0014 05CD 0148 0051 0016 0E4E 2710

Everytime I do this for the same button, the code isn't the same.
If I click the button test, my tv isn't respondig at all. I've done this for 2 remote controls. Both aren't working.

First off, don't expect the learned pronto code to be the same each time, even for the same button press. They are often different, but the same button should still decode to the same event.

Here are some general troubleshooting tips for the transmit functionality (I'll see if I can put this in a FAQ somewhere).
1) Make sure the device has blasters attached. Run the GetDeviceInfo action, which will print some info about the device to the log. The output should look something like this: "2 Transmitters (1 attached), does have learn capability". If it says (0 attached), you need to plug in a transmitter.
2) Before you learn a command, collect the IR code normally just by pointing the remote at the receiver and hitting the desired button. You should see get an event with whatever EG thinks the code is (MceRemote.Unknown.0x00beef (some random hex #) or MceRemote.[Nec or SIRC or some other decode type].0x00beef). This is useful to see if the code is working once it is learned. Some remotes will produce multiple events for a single button press, this is not a problem.
3) Now, go ahead and learn the IR Code (click the learn button, hold the remote a few inches from the IR Receiver, and hit the remote button. Once IR Code is received, the dialog will close automatically. Note - press the button normally, don't hold it down - the program waits for 1/4 second of "silence" as the end of the IR Code, so holding down the button will look like a really long code.
4) Put the IR Transmitter (the little light on the end of the wire) in front of the MCE Receiver (not the device you want to control). Hit the Test button (or run the action if you've already accepted it). The blaster I have will flash when it transmits, so you can tell it is doing something. When it transmits, the EG should log the IR code based on the learn. Compare the Test code with the regular code you found from step 2.

Post the results of these steps, and I will see what I can do to help out.

When I now press a button at my MCE remote, it isn't recognized as for example:

Code: Select all

MceRemote.Green

You mean MceRemote.Mce.Green, right?

Code: Select all

MceRemote.Green

but as (multiple presses):

Code: Select all

MceRemote.Unknown.5593BFB96E0
MceRemote.Unknown.AB27FFF2DC0987AF570
MceRemote.SIRC15.0000
MceRemote.Unknown.AB26FFF2DC0987AFD70
MceRemote.Unknown.AB267FF2DC0987EBD60
MceRemote.Unknown.AB27FFF29C0987AF970
MceRemote.Unknown.AB27FFF2DC0987EBD70
MceRemote.Unknown.2A2FFFFCA7EBD7C
MceRemote.Unknown.2AC987FCB70

I'm not sure what to make of this. This looks like a separate issue than the learn problem above. Can you answer some questions that will help me isolate what is going on? First off, is this temporary, or does it continue until something else happens (like restarting EG)?
Does the problem go away if you disable and then re-enable the plugin?
Does the problem go away if you restart the service (don't bother if restarting the plugin fixes it)?

Thanks,
Brett

[Ronny]

First off, don't expect the learned pronto code to be the same each time, even for the same button press. They are often different, but the same button should still decode to the same event.

Okay, I now know that!

Here are some general troubleshooting tips for the transmit functionality (I'll see if I can put this in a FAQ somewhere).
1) Make sure the device has blasters attached. Run the GetDeviceInfo action, which will print some info about the device to the log. The output should look something like this: "2 Transmitters (1 attached), does have learn capability". If it says (0 attached), you need to plug in a transmitter.

Code: Select all

2 Transmitters (1 attached), does have learn capability

Is what I get, so this works.

2) Before you learn a command, collect the IR code normally just by pointing the remote at the receiver and hitting the desired button. You should see get an event with whatever EG thinks the code is (MceRemote.Unknown.0x00beef (some random hex #) or MceRemote.[Nec or SIRC or some other decode type].0x00beef). This is useful to see if the code is working once it is learned. Some remotes will produce multiple events for a single button press, this is not a problem.

The standby button of my TV remote control (pressed 6 times):

Code: Select all

MceRemote.Unknown.5FAAEFC
MceRemote.Unknown.5FD54FBFFF8
MceRemote.Unknown.5FAAEFC
MceRemote.Unknown.5FD54FBFFF8
MceRemote.Unknown.5FAAEFC
MceRemote.Unknown.5FD54FBFFF8

When I press the button 1 time, nothing shows up in the log. When I press it for the second time, 2 lines show up. How can this happen? This is every time the same with this remote.
I've also tested with the remote of my audio receiver:

Code: Select all

MceRemote.Unknown.2FB5755575EFBEAC
MceRemote.Unknown.2FB5755571EFBEAC
MceRemote.Unknown.2FB5755575EFBEAC

Sometimes I get this, 1 line for each press.
And sometimes this (the same button!):

Code: Select all

MceRemote.Unknown.5EFBEAC
MceRemote.Unknown.5F7DDAAAEA8
MceRemote.Unknown.15DF7DFA8
MceRemote.Unknown.5F7DDAAAEA8
MceRemote.Unknown.15DF7DFE8
MceRemote.Unknown.5F7DDAAAEA8
MceRemote.Unknown.15DF7DFA8
MceRemote.Unknown.5F7DDAAAEA8

And now there are 2 lines for each press. But this isn't a problem I think? Because what you mentioned: "Some remotes will produce multiple events for a single button press, this is not a problem"

3) Now, go ahead and learn the IR Code (click the learn button, hold the remote a few inches from the IR Receiver, and hit the remote button. Once IR Code is received, the dialog will close automatically. Note - press the button normally, don't hold it down - the program waits for 1/4 second of "silence" as the end of the IR Code, so holding down the button will look like a really long code.

This is what I get, when learning the standby button of my receivers remote control:

Code: Select all

0000 0073 0000 001F 0038 0014 0038 0016 0012 0014 0038 0016 0012 0012 0014 0014 0012 0014 0038 0016 0038 0014 0038 0016 0012 0012 0014 0014 0012 0038 0016 0012 0014 0012 0016 0036 0016 0012 0014 0038 0016 0012 0014 0038 0014 0014 0014 0038 0014 0038 0014 0014 0014 0036 0014 0014 0012 0014 0038 0014 003A 0014 0038 0014 0E4E 2710

4) Put the IR Transmitter (the little light on the end of the wire) in front of the MCE Receiver (not the device you want to control). Hit the Test button (or run the action if you've already accepted it). The blaster I have will flash when it transmits, so you can tell it is doing something. When it transmits, the EG should log the IR code based on the learn. Compare the Test code with the regular code you found from step 2.

I've done this. The blaster transmits, the led flashes. The receiver receives, the led in the receiver flashes too. But the log doesn't show anything of receiving. Just this:

Code: Select all

Microsoft MCE Remote - Vista/Win7: Transmit IR: 0000 0073 0000 001F 0038 0014 0038 0016 0012 0014 0038 0016 0012 0012 0014 0014 0012 0014 0038 0016 0038 0014 0038 0016 0012 0012 0014 0014 0012 0038 0016 0012 0014 0012 0016 0036 0016 0012 0014 0038 0016 0012 0014 0038 0014 0014 0014 0038 0014 0038 0014 0014 0014 0036 0014 0014 0012 0014 0038 0014 003A 0014 0038 0014 0E4E 2710

You mean MceRemote.Mce.Green, right?

I mean MceRemote.Green, that is what I get with the "old" plugin (Microsoft MCE remote plugin).

I'm not sure what to make of this. This looks like a separate issue than the learn problem above. Can you answer some questions that will help me isolate what is going on? First off, is this temporary, or does it continue until something else happens (like restarting EG)?

This is always the same. Since I added the new plugin, the green button (and all the others) aren't recognized as MceRemote.Green ed. But just as hex numbers. Like these:

Code: Select all

MceRemote.Unknown.AB27FFF2DC0985EBD70
MceRemote.Unknown.AB267FF2DC0987AFD70
MceRemote.Unknown.AB267DF2DC0987EBD70
MceRemote.Unknown.AB27FFF2DC0987AFD70

I assume that they still are recognized as something like MceRemote.Green etc?

Does the problem go away if you disable and then re-enable the plugin?

No. It's still the same.

Does the problem go away if you restart the service (don't bother if restarting the plugin fixes it)?

How do I do this? I only know how to uninstall and reinstall the service. (this doesn't change anything)


I hope this is all you asked for.
I really appreciate it a lot, that you do this for us!
Thanks a lot for you help!
I hope you can solve the problem with my tests.

If I have to test something else, I would like to help!

[stottle]

Ok, the first thing that strikes me in your reply is that MceRemote.Green part. I thought you meant that the plugin (my version, not the original) registered the correct events, but stopped registering correct events after you tried to learn an IR code. Now it sounds like my version NEVER provided the correct result, it just output Unknown from the get-go. Is this correct?

If so, all that means is that your device is outputting different codes than EG's IrDecoder is used to (FYI, the old plugin had its own decoder, it didn't use EG's). So I need to see what your Mce Remote sequence looks like. Please learn the Mce "green" code, and post the pronto code it outputs. I can turn that into a set of on/off times and test the decoder to see whats going on.

As for the pronto codes from the other devices, I can try those on my end and see if I can figure out why they aren't producing events.

Send me the pronto code for Mce green when you get a chance.

Thanks,
Brett

[Ronny]

Ok, the first thing that strikes me in your reply is that MceRemote.Green part. I thought you meant that the plugin (my version, not the original) registered the correct events, but stopped registering correct events after you tried to learn an IR code. Now it sounds like my version NEVER provided the correct result, it just output Unknown from the get-go. Is this correct?

That's exactly what I meant. With the old plugin it was always like: MceRemote.Green
But this never showed up with the new plugin.
So the buttons aren't recognized. This isn't only for the green one, this was an example. This is for all the buttons on my remote.

This is the pronto of the MCE green button:

Code: Select all

0000 0073 0000 001D 000E 0010 0010 0010 0010 0010 0010 0020 0010 000E 0010 0010 0010 0010 0010 0010 0020 000E 0010 0010 0010 0010 0010 0020 001F 0020 0031 001F 0010 0010 0010 0010 0010 0010 0010 0010 000E 0010 0010 0010 0010 0010 0010 0010 0010 000E 0010 0010 0020 0010 0010 0010 0020 0010 0010 000E 0E4E 2710

Thanks for you help!

[stottle]

Ronny,

Got it. I'll take a look.

Brett

[stottle]

Ronny,

The code you sent for the MceRemote's green button doesn't look like a valid code. That is, I looked at the decoders in the original plugin and they wouldn't decode it either. All of the decoders assume a longer than usual 1st pulse, which your sequence doesn't have. Can you try using new batteries in the remote and see if that helps?

I also tried your Receiver code as a learned IR. When I blast it back into the Mce receiver, EG posts:
MceRemote.Unknown.2FB57555710FB2AC
you said you got
MceRemote.Unknown.2FB5755575EFBEAC

So it seams like it was learned properly [edit - not exact, but much closer than you were getting]. Is it possible that your blaster is dirty, or oriented funny?

I'll keep looking, these are just the first things I could think of.

Brett

[Ronny]

Ronny,

The code you sent for the MceRemote's green button doesn't look like a valid code. That is, I looked at the decoders in the original plugin and they wouldn't decode it either. All of the decoders assume a longer than usual 1st pulse, which your sequence doesn't have. Can you try using new batteries in the remote and see if that helps?

I also tried your Receiver code as a learned IR. When I blast it back into the Mce receiver, EG posts:
MceRemote.Unknown.2FB57555710FB2AC
you said you got
MceRemote.Unknown.2FB5755575EFBEAC

So it seams like it was learned properly [edit - not exact, but much closer than you were getting]. Is it possible that your blaster is dirty, or oriented funny?

I'll keep looking, these are just the first things I could think of.

Brett

If I use the "old" plugin, everything works fine.
So I don't think the batteries are low. Or the receiver is dirty of oriented funny.
When learning the green button, it didn't learned the first time.
The message box dissapeares after a few seconds, with other remotes this is a shorter time.
I don't know why this takes so long.
This is the new pronto (longer than the one before?!):

Code: Select all

0000 0073 0000 0059 0061 0020 0010 0010 0010 0010 000E 0020 0010 0020 002F 0020 0010 0010 0010 0010 0010 000E 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 001F 0020 0020 0010 0010 0010 0010 001F 0010 0010 0010 09B9 0061 0020 0010 0010 0010 000E 0010 0020 0010 0010 0010 0010 0010 0010 0010 0010 001F 0010 0010 0010 0010 0010 0010 001F 0020 0010 0010 0010 0010 001F 0020 0020 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 000E 0010 0010 0010 0010 0010 001F 0010 0010 0010 0010 0010 0010 0010 000E 0020 0010 0010 0010 0010 000E 0010 0020 0010 0020 002F 0020 0010 0010 0010 0010 0010 000E 0010 0010 0010 0010 0010 0010 0010 0010 000E 0010 0010 001F 0020 0020 0010 0010 0010 0010 001F 0010 0010 0010 09B9 0061 0020 0010 0010 0010 000E 0010 0020 0010 0020 002F 0010 0010 0010 0010 0010 001F 0010 0010 0010 0010 0010 0010 001F 0020 0010 0010 0010 0010 001F 0020 0020 0010 0010 0010 000E 0002 0E4E 2710

Is this the good one?

[stottle]

I've put a new version out in the 1st post.

I was adding an IR transmit test action, which led to finding a bug in the code.

For those that are interested (I think this explains the issues that have been reported), here are the bug details:
The IR device outputs 100 bytes (plus a header) as a "data chunk." Often several chunks need to be combined into a single IR code, which I do in the EG plugin. So each chunk needs to be passed from the service to the plugin. I'm still not sure why, but if I write one chunk at a time from the service (using asynchronous WriteFile calls), the python plugin will occasionally read multiple chunks as a single read. I didn't expect this, so before this last fix, I would strip the header and process everything else as IR code data. When two or more chunks were combined, this would put header data in the middle of the IR code and cause it not to be recognized. The plugin now catches this condition correctly.

So what's in the new version? A new action for testing IR blasting. This function transmits the MceRemote.mce.Num1 code. So if you are having trouble with blasting, please try this action with the blaster pointed at the Mce Receiver. Of course, the bug fix is also included.

Brett

[stottle]

Did the new version fix the problems people were having with the plugin (Ronny, jitterjames, chaos945)?

Brett

[Ronny]

Did the new version fix the problems people were having with the plugin (Ronny, jitterjames, chaos945)?

Brett

I have a very busy week, so I didn't have the time yet to fully test it.
But what I've tested so far, doesn't work. I didn't find the code for the num1 button either.

What I've tested:
-learning a button of several remote controls
The pronto is being generated, but when I press the test button, the corresponding device isn't responding at all.
Maybe I've this weekend some more time to test more. But I don't think there is much left to test. (Only the learning function is edited I think?)

Thanks for the help.

Ronny

[jitterjames]

I will test it this morning and get back to you.

[stottle]

But what I've tested so far, doesn't work. I didn't find the code for the num1 button either.

I'm trying to isolate where the issue is. So I created a new action you can add to a macro "Test IR Transmit Capability". If you run this action, it will transmit the RC6 Num1 code, with no learning involved. The code (raw on off times) is hardcoded in the service. This idea is to run this action with the Blaster pointed at the Mce Receiver. It completely cuts out any problems people might have with learning and makes sure the blaster transmits properly.

In order for this new version to work, you need to replace the MceRemote_Vista directory with the new version from the 1st post, then open up the config for MceRemote_Vista and select "uninstall" followed by "install".

Brett

[Ronny]

I already thought something like that. I have tested that, but without any result. So I thought I was wrong.

When I run "Test IR Transmit Capability" the led on the blaster isn't blinking and the receiver receives nothing at all.

By the way, with the new plugin loaded (not only the latest version, but all versions), the led of the receiver sometimes blinks. This wasn't the case before.

[stottle]

When I run "Test IR Transmit Capability" the led on the blaster isn't blinking and the receiver receives nothing at all.

Well, I know it doesn't help you yet, but that tells me the problem is in the service code talking to the device. I will need to get out a new version with some more debugging information to try to get to the bottom of this. Your OVU4120 is different hardware than I have, so it looks like the code is hitting something on your system that I didn't see in testing. Thanks for being patient.

For those who had problems where it transmitted but wasn't working properly, I would still like to know if this helps.

Brett

[jitterjames]

Did the new version fix the problems people were having with the plugin (Ronny, jitterjames, chaos945)?

Brett

It doesn't seem any better for me. Everything works fine as long as I don't try to trigger a blast using the mce remote, which causes it to freeze for about 10sec, then it blasts (like from a buffer sometimes it'll store multiple events) and generates a bunch of unknown codes...

I don't know if this is different, but I noticed that I can trigger a blast using the mce receiver as long as I am using some other remote, like the one from my dvd player and not the mce remote.

Every time I generated a blast by any method I am still getting weird events generated in the log but this is probably something to do with my particular receiver and it's cheapo parts generating stray electrical fields or something when generating the blast.