GBPVR, Winlirc, and hauppauge 350 remote

[brickhouse]

Thanks for the digit.exe unfortunatly I got the following error when I ran it-

$cmd2=""&cmdline[4]
$cmd2=""&^error

most likely something I have set up wrong but figured I best see what you say first. If anything I am understanding the .exe changer alot better.
:o

Any special location I should have the digit.exe file sitting? Currently I have everything in the winlirc directory. I don't imagine it matters but best to ask.

[pBS]

sounds like its running so must be sitting right place..
just add a 4th param...it was supposed to see if you had one or not but i guess that's not working.. it could be anything...

scratch that..i found a bug...was passing params in wrong order...lol [it was late]
here's one that should work...the original way....sorry about that...

remember: you'll have to "learn" the STB remote cuz those are the ones you'll be sending..
so both controlling remote and sending remote will have to be defined in same winlirc config file...
[that's why have to specify remote name]

[brickhouse]

Well after a fews days away from working on this I finally got back to it and from what I can tell is I had a mis-spelling in the parameters. I finally figured out by running digits.exe from a command line. Once I got it to work from there I knew it should work from with in GBPVR, and it did.

For other members/beginners this is what I ended up with:

In the GBPVR config.xml under the capture source I selected .exe plugin for the channel changer and in the settings I had the following:

executable: c:\winlirc\digits.exe

Parameters: {channel} transmit.exe dish

Zero padded and 3 digits both checked

(Dish is the name of the winlirc config I needed for the STB)

All the executables and winlirc files were in the winlirc directory. Winlirc.exe also needs to be running all the time so I put a short cut in the startup menu in windows.

The IR balster hardware is the exact setup as what winlirc has for an example on thier website.

For testing to see if the IR was tranmitting I used pBS's trick of watching the IR tranmitter in a video camera, yes you can see it flash when it transmits.

Thanks for the digits.exe and all the other info pBS.

[stefan]

Glad to hear you got it sorted

[-Oz-]

just gonna add something i learned with my serial IR receiver hookup. My problem was the serial port on my MSI K8NGM2-FID motherboard wasn't putting out enough voltage. Thus there wasn't enough voltage shift and winlirc couldn't see it. Thus I hooked up the power parts to the powersupply 5V and ground directly and ran just one wire over to the serial header. Also cut out a few of the parts too. I'll write a detailed tutorial as I make this IR setup for my second HTPC.

[pBS]

excellent.. i was amazed at how simple it is to make, given the right parts..

and while winlirc works, i like the stability of IR Assistant but both have pretty much all features i need..

but now i just use my MCE blaster with the 2 outputs..i got all this working while i was waiting for my MCE remote to arrive! lol [only a couple days]

usually less than 10$ for parts for the whole thing...

[flyswatta]

Thanks guys, this really helped me out. I finally got it working with (one) minor adjustment:

Parameters: {channel} transmit.exe dish 2

I added a 2 to repeat 2 times. Once I did that, then it was rock solid on changing channels.

Also I figured out a workaround for sending sub-channels, I substituted a '9' for a dash (I don't have any channels on that tuner that use a 9) in my remote winlirc config. Then I changed the source channel in GBPVR to have the '9' in it. For example, I want to tune to HD channel 4-1, I changed the source channel to 491. .exe changer sends it to digits.exe as 491, digits sends 491 to transmit.exe, transmit.exe telnets to winlirc and sends 491. Winlirc sends the codes for 4, dash, 1. (winlircs code for a 9 is really a dash), so it sends 4-1 to the receiver.

Thanks for all of the help!!

[stefan]

Well done