[Kasuo]

TV-Server Version: n/a
MediaPortal Version: 0.2.2.0
MediaPortal Skin: BlueTwo Wide
Windows Version: Windows XP Pro SP1
CPU Type: AMD Athlon64 3200+
HDD: Seagate 400gb 7200rpm Ultra ATA 100
Memory: 1.5gb DDR2
Motherboard: ASUS K8V Deluxe
Motherboard Chipset: Athlon64 759
Motherboard Bios:
Video Card: ATI Radeon 9800 SE
Video Card Driver:
Sound Card: Soundblaster Audigy Z2
Sound Card AC3:
Sound Card Driver:
1. TV Card: WinTV PCI-150-something (came with a MCE PC)
1. TV Card Type:
1. TV Card Driver:
MPEG2 Video Codec:
MPEG2 Audio Codec:
Satelite/CableTV Provider: Comcast
HTPC Case: Silverstone L10 Silver
Cooling: various fans
Power Supply: Standard 550W
Remote: MCE from TV-card kit
TV:
TV - HTPC Connection:

Sorry I left some information left undone - I can't exactly get to some of it right now.
I've got MP up and running except for 2 things - setting it to operate the STB (Motorola DCT-2244) and getting a multi-remote working with the PC. The later I'll worry about later - it'll be very easy, but I'm stuck at getting MP controlling the STB.
Since I'm using the MCE kit I recieved with a previous MCE PC (made by Microsoft, I believe), I've been working with the MCE Replacement and MyBlaster plugins, both with no success. I've decided to skip worrying about the MCE Replacement plugin as the MyBlaster plugin has actually gotten further.
Anyways, the MyBlaster plugin (I've actually tried 2 different versions of it now) regonizes the unit and allows me to let it learn the commands, but for some reason it is unable to correctly test what was inputed. I set the unit up so a MCE PC has no problems controlling the STB, yet the MyBlaster plugin cannot get it working.
Running with /DUMP does not return any errors at all, everything is placed in the right place (MyBlaster/Blaster.exe in the root MediaPortal folder, MyBlaster.dll installed in the Plugins/Process folder), the plugin has no issues learning the commands. I've noticed afew things, though -
1) Nothing is saved when the configuration program is closed. NOTHING!
2) Unable to test - nothing is being sent through ports 1 and 2 off of the reciever.
3) There are no returned or generated errors.
4) I know the receiver is working correctly - the remote operates MP.

I've already done a search through the forums, yet nothing has helped.

Can someone help me out?

EDIT: Submitted too early.

I have found this is MyBlaster.txt:
5/12/2007 11:45:15 AM Form1.LoadConfig: Collection was modified; enumeration operation may not execute.
5/12/2007 11:45:15 AM Device.FindDevice: \\?\usb#vid_045e&pid_006d#ms1ewako#{7951772d-cd50-49b7-b103-2baac494fc57}

It looks like this appeared each time I changed anything in the App.

[Spragleknas]

Hi, and welcome to the community!

I recommend you try and-81's MCE replacement plugin

See the "Hot plugins"-section.

Good luck!

[Kasuo]

Thank you for the quick reply.

I'm actually in the process of working with it - atleast it saves all of the information thus far.
Yet it seems it is having the same problem with testing - it seems it can't communicate with the IR ports on the receiver. I'm going to try a different set of drivers with the adapter to see if it'll help.
Instead of dirrectly testing to the STB, I've repositioned the IR blaster's end in front of the MCE Remote receiver, looking for any response on the unit.
Has anyone else had a similar problem?

[Kasuo]

Hate to double post, but the forums wouldn't let me edit my last post.

Problem has been solved - the drivers that we're being used were not functioning correctly. I had to manually edit the drivers to fix the issue.

[and-81]

Hey Kasuo,

Can you provide some more information on what you had to change?

That way maybe I can make sure your problem doesn't happen for others in the future ...

Cheers,

[Kasuo]

Sorry about the long wait - I've been busy trying to get MP up and running.

What I tried failed pretty quickly - it worked for abit, but now it won't.

I'm now back to the problem that the two ports on my MCE IR receiver will not operate. Every once in awhile, something is correctly sent through port 2, but it's rare. I should say Port 1 is a dud, while port 2 works occassionally when you start begging.

Back to the drawing board...

[and-81]

If you're trying to use the MCE Replacement Plugin make sure you have a read of the documentation. There are a couple of things that can catch out the new users.

I suggest you head over to the MCE Replacement Plugin sub-section and check out some of the How-To and other threads...

Just off the top of my head it sounds like you should try changing the "Blaster Manufacturer" setting and also try different blast speeds...

Good luck,

[Kasuo]

I'm using the MCE Replacement plugin, currently set to SMK, forced through port 2 at a low speed - this is the only configuration which gave a working IR blaster. It was perfect while setting up, but once I closed the configuration it went downhill.
If I go back into the configuration utility and test any of the captured IR commands (all of which tested correctly with my STB), nothing is sent through the port ('less I test several hundred times, then I'll see the IR blaster end light up and it'll work).

As for using MyBlaster, I gave up on that after the plugin wouldn't save anything - it was kinda wierd.

[Kasuo]

This is now getting very wierd - I just reinstalled the original drivers for my MCE receiver and now it'll work for alittle bit.
After about 15 or 20 minutes, or after you restart the system, it's necessary to unplug the receiver for a few seconds, then plug it back in. After about 20 minutes, the IR blaster ports stop working.

I've searched the forms for abit today and I've yet to find another having a similar issue.

Is there a utility that you guys would suggest to update/reinstall selected drivers at set time intervals?

[and-81]

hmmm,

Reinstalling the drivers every 20 minutes is not a solution, and even though I could probably write something to do that for you it wouldn't solve the problem 100%.

I just took another look a the system specs you posted and noticed that you're using Windows XP SP1. You really should use SP2, though that's probably got nothing to do with this problem..

But I also noticed that you're remote input is from a WinTV PCI-150. This is probably the cause. Unfortunately, if it is the cause then I won't be able to do anything to fix it until the release of my next plugin that I'm currently testing.

If I find/make something that might help you I'll let you know.

Cheers,