Hauppauge HVR 1600 remote control?

[Ioky]

I just got a Hauppauge HVR 1600 model 1199. It seem working well? (doesn't use it long enough to say how well it actually is.)

However, My problem is the remote Control come with the Card, it doesn't seem working at all. I just wonder how can I make it work.

I have no knowledge on IR remote under Linux, so.

Thanks.

[uMuppet]

What does the remote look like? Can you post a pic somewhere?

[Ioky]

http://lirc.sourceforge.net/remotes/hauppauge/PVR-350.jpg

I try to use mode2, it say "error oepn" /dev/lirc, no such file or directory.

any idea?

Thanks

[sniperbob]

Last I searched around, the driver for the card supports all the video functions, but the infared port on the card is not supported yet.

I wasted an evening or two trying to force drivers to work for it with lirc, ended up giving up and just ordering a serial port IR receiver, hope to get it in the mail shortly. Generic serial IR units are much better supported.

[psuprogrammer]

ended up giving up and just ordering a serial port IR receiver, hope to get it in the mail shortly. Generic serial IR units are much better supported.

Can you post a few links to well supported serial IR units?
I'm looking for something easy to setup.

I've been working on this 1600 remote for several hours today and am lost.

[sniperbob]

If you search for "mythtv blaster" or something of the sort, you can come across several commercial offerings.

I would point you in a more specific direction - but I didnt end up buying one, I ordered parts and am making my own - so I don't know any more than you.

[appsmanster]

At least I am not the only one having issues with the remote. As much as I love Ubuntu, running on everything I can, an easier temporary solution would be Knoppmyth or Mythdora. I am still trying to get the remote to work with Mythbuntu. When I got my HVR-1600 card I decided to try Knoppmyth as I had some experience with it. Got needed drivers from V4L/DVB and it all worked. Tried Mythdora and it worked. But I like Ubuntu. Still working on Mythbuntu. Its just another learning curve. So I am now running Mythdora as primary and Mythbuntu as secondary. Once the remote issue is done and I will figure this out, I will switch to it. I know its not the thing to point out in this forum but looking at what works in one will help to figure out what to change in the other.

[humdrim]

Did you do something specific to get your remote working with knoppmyth, as it's not working for me I'm stuck at the same setup as with mythbuntu. I don't know if it's the placement of the port that's grounding it to the computer case or something else. Your input would be well appreciated. Thanks.

I even tried the ir_kbd_i2c workaround from mark lord found here http://rtr.ca/hvr1600/. The problem with that was that my r/c port is not seen as an input device so I couldn't use that.

[Weidbrewer]

I have the same card, but mine came with a different remote. I am actually trying to use that remote on a different frontend, but am not having much luck setting it up. Here is the remote that mine came with:

http://www.mythtv.org/w/images/b/b2/MCE-Remote-2-v1069.jpg

That picture is from the MythTV wiki. I am running Mythbuntu 8.10, and the install section simply says:

Ubuntu 8.10

Ubuntu 8.10 ("Intrepid Ibex") has out of the box kernel modules for the MCE remotes. All that is required is to install lirc (as noted above), and follow the prompts.

Lirc is installed...but I don't know where to go next. What are the other steps to get this remote to work.

Again, for clarification, this remote and USB IR sensor are being used independently of the tuner card. Thanks for any help.

[MythAaron]

I have a 1600 with Ioki's remote and it works fine here.

I'll throw this out there since this where I was tripped up. Make sure the IR blaster/receiver is plugged ALL THE WAY into the card. The plug will go so far, then it will "click" into place.

[Weidbrewer]

I installed Mythbuntu-Control Center and installed the remote from there...so far so good. I'm having some play-back troubles (another thread) so I can't test the FF, RW, etc yet. However, what I've tried worked.

[dealcorn]

Within Mythbuntu Control Center, what selections worked for remote name and IR transmitter? HVR-1600 is not listed as a selection and the IR transmitter is not obvious.

[uMuppet]

Try Windows Media Centre (new) for both

[Weidbrewer]

That's exactly what I used. Popped "new version" in, and I was good to go.

[fermulator]

So .. does anyone have the remote working in Ubuntu 9.04?

I'm a complete newb with this TV Tuner and IR Remote Control stuff.

I tried lirc, but there's no explicit options for the HVR-1600, and the gnome-lirc-properties window doesn't show it either.

[Weidbrewer]

The main thing is that there isn't an entry for that remote itself, but it uses one of the two MCE entries (The newer one, I believe.) Try them both and one should work out of the box. I'm still running 8.10 on most of my boxes, but there was one that I briefly had on 9.04 (there were graphics card issues, so I had to revert.)

[tmkt]

the grey remote used to work for me with 9.04..then I upgraded to 9.10..and can't get it to work...going to try the media centre option next.

[JMcFly]

My HVR-1600 came with the grey remote (not the MCE remote), and it works when I set 9.04 for HVR-1300's remote. You will hear a definitely click when the plug is inserted all of the way, its a little tougher than a normal stereo plug to insert due to how close it can be to the case frame.

But, I cant figure out how to set the red, green, yellow and blue buttons on the remote to key presses in Myth. I'd like to set one to 100% fill (for when an analog source is broadcast in letterbox), but I cant find a line in the Myth frontend key menu to set that or cycle through the fill levels?

[tmkt]

No go using the windows MCE...went back to Ubuntu 9.04..working great again....using Hauppauge TV Card setting

[telseth]

I just upgraded to 9.10 and have been using the grey hauppauge hvr 1600 remote happily. Now it doesn't work. It doesn't create /dev/lirc0 and doesn't use the correct lirc_i2c module (it is trying to use lirc_mceusb2, which is wrong) anyone know how to fix this? I cannot downgrade to 9.04 and my wife won't run this thing without a remote.

[tacman2k]

I am having the same problem.

I was able to use my remote control and IR blaster using this tutorial:

http://www.blushingpenguin.com/mark/blog/?p=24


Unfortunately lirc0.8.5 does not compile with the current kernel.

I tried booting into the old jaunty kernel (2.6.29) but it does not boot up.

LIRC 0.8.6 is out now and compiles with the new kernel for Karmic, but I have not found a patch for it.

I tried contacting the guy who made the tutorial, but so far no response.

I would like to get this remote working.


Im considering getting a new remote if I can't. Any suggestions?

[bsntech]

I just built a new box with 64-bit on it and finished setting stuff up today. The remote worked for me as well using 9.04 Jaunty, but now in 9.10 Karmic with all of the updates as of today, it is not working.

I opened a bug for this as I hope it will be fixed soon. I don't want to have to put my old PVR-150 card in just to use it for the remote - but heck, it may not even work in Karmic either!

https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/454371

[telseth]

Yeah, I had to throw my old PVR-250 back in there. Lucky I didn't toss it.

[bsntech]

This does suck - why all of a sudden did 9.10 break the HVR-1600 and WinTV-Go Plus IR receivers/transmitters?

I've ordered an HVR-1250 to put in this computer so I have two digital cards since I'm Finding that I'm recording everything on the digital OTA now - and will eventually get rid of our basic cable and save $15 a month. So, now I'm going to have three TV tuner cards in the system when only two are used for capture.

Add this on top of an add-in USB PCI card that I'm going to have to put in now because of either a hardware or software bug in Ubuntu causing the MCP78S chipset USB ports to not work after an intermittent period of time or unless they are plugged in prior to Ubuntu booting up. I just got this ECS GF8200A motherboard with a built-in GeForce 8200 video card to make use of VDPAU - and now I've got more problems to circumvent.

Also the GeForce 8200 card with 512 MB shared memory works very well with VDPAU and the 180.x.36 nVidia drivers in Ubuntu. There is a little bit of tearing, but it isn't all that terrible on 720p and 1080p broadcasts. I have the VDPAU profiles setup accordingly:

< (less than) W: 1080 H: 720 - Use Advanced 2x deinterlacer
>= (greater than or equal to) W: 0 H: 720 - Use Temporal 2x deinterlacer

Order is important with the above.

[gordon ottershaw]

Hello All,

After about a week of reading forum posts, the Hvr-1600 model 1199 grey remote finally generates output to a terminal window using the irw command.

No luck at all getting a working channel changing script or blaster function. The only good news is that I know for a fact that the hardware works because I configured all of it in XP before I tried to run Mythbuntu. IF its any consolation, Hauppauge's software is only marginally better than linux. I just took out the XP hard drive and installed a new drive to load Mythbuntu. BTW the IR Blaster has a red led that flashes when it is working(at least on this unit). So IF the driver EVER starts working, I'll be able to see it.

The remote still won't change channels on my Motorola 2244 cable box, but at least it does something.

Configuring the Blaster should not be this difficult. Isn't the Hvr-1600 a popular card?

[resolost]

how were you able to get the remote to work in irw?

[Indi.N]

The breakage of the lirc_i2c module happens at a kernel >= 2.6.28, where 0.8.4a (old default 9.04 package) is no longer usable, due to i2c changes in the kernel mainline.
I've been following this issue for several months as I moved to a >= 2.6.30 kernel quite a while back for various other reasons. The actual IR sensor driver resides in cx18_i2c, which is part of the V4L-DVB subsystem.



It seems that there has been a flurry of changes surrounding i2c drivers in both the kernel, in lirc, and in the v4l-dvb code, but I was surprised to find that I could avoid the nonfunctional lirc_i2c/i2c_dev issues by running ir-kbd-i2c instead.

I have not tried 9.10, and all the shiny new (more) up to date packages, so it might be worth trying a modprobe ir-kbd-i2c and checking your dmesg etc.

The following worked for me:


1. Get a 2.6.31 kernel loaded (possible a 2.6.30 would work; have not tried)http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.31.5/ (http://kernel.ubuntu.com/%7Ekernel-ppa/mainline/v2.6.31.5/)

or do whatever you prefer to update your kernel.
Reboot

2. Get the latest version of v4l-dvbhg clone http://linuxtv.org/hg/v4l-dvb
cd v4l-dvb
make
make install

I should note that to get a full compilation of all the v4l modules, I needed to go comment out some entries for a firedtv module (in a makefile) that was failing to build. I've not pulled any updates for a few days so perhaps that is fixed? YMMV with code pulled from live repos.

3. Get 0.8.6 lirc source installed.http://prdownloads.sourceforge.net/lirc/lirc-0.8.6.tar.bz2
I have 0.8.6 installed via apt, and you should too.

If you're going to be running setup.sh (yes you probably will) you're going to want to edit it to change line 338 to " echo ./configure --prefix=/usr \\" >>$START so that you don't end up with the complied version ending up in the lirc default (/usr/local).


When you configure LIRC, you will want to choose "Linux input layer (/dev/input/
eventX)" (indicated by driver:devinput). Complete the build process via the script, make, sudo make install etc..


So, go ahead and load ir-kbd-i2c and check it out.



indi@indulgent:~$sudo modprobe ir-kbd-i2c
Nov 3 21:10:45 indulgent kernel: [ ] input: i2c IR (CX23418 Z8F0811 Hauppau as /devices/virtual/input/input7
Nov 3 21:10:45 indulgent kernel: [ ] ir-kbd-i2c: i2c IR (CX23418 Z8F0811 Hauppau detected at i2c-0/0-0071/ir0 [cx18 i2c driver #0-0]
indi@indulgent:/etc/lirc$ cat /proc/bus/input/devices | grep -A6 "i2c IR"
N: Name="i2c IR (CX23418 Z8F0811 Hauppau"
P: Phys=i2c-0/0-0071/ir0
S: Sysfs=/devices/virtual/input/input6
U: Uniq=
H: Handlers=kbd event6
B: EV=100003
B: KEY=10..
Note the device node - /devices/virtual/input/input6
Stop lircd if you've got it running (sudo /etc/init.d/lirc stop, whatever)



indi@indulgent:sudo lircd -n --device=/dev/input/event6 --output=/var/run/lirc/lircd
lircd-0.8.6[]: lircd(devinput) ready, using /var/run/lirc/lircd
lircd-0.8.6[]: accepted new client on /var/run/lirc/lircd
lircd-0.8.6[]: initializing '/dev/input/event6'
indi@indulgent:~$irw
0000000080010161 00 Go HVR-1100
Well, that would be mostly working.

I changed my /etc/lirc/hardware.conf a little, and by adding ir-kbd-i2c to the lirc list of modules you get it to load on restart.

REMOTE_MODULES="ir-kbd-i2c"
REMOTE_DEVICE="/dev/input/event6"
Notes: ir-kbd-i2c does not autoload (by previous design to prevent device conflicts), I seem to get incorrectly identified as a 1100, but I don't care, it works. I did end up re-tweaking my ~/.lircrc slightly and modified the /usr/share/lirc/extras/more_remotes/hauppauge/lircd.conf.hauppauge a bit too. I have not tried 9.10, but imagine that a similar process should work out, as the kernel versions/lirc/v4l stuff should all be similar.

[dealcorn]

When I run the command make in step 2, I get the error:

dea@e5300:~/v4l-dvb$ make
make -C /home/dea/v4l-dvb/v4l
make[1]: Entering directory `/home/dea/v4l-dvb/v4l'
creating symbolic links...
make -C firmware prep
make[2]: Entering directory `/home/dea/v4l-dvb/v4l/firmware'
make[2]: Leaving directory `/home/dea/v4l-dvb/v4l/firmware'
make -C firmware
make[2]: Entering directory `/home/dea/v4l-dvb/v4l/firmware'
make[2]: Nothing to be done for `default'.
make[2]: Leaving directory `/home/dea/v4l-dvb/v4l/firmware'
Kernel build directory is /lib/modules/2.6.28-11-generic/build
make -C /lib/modules/2.6.28-11-generic/build SUBDIRS=/home/dea/v4l-dvb/v4l modules
make: Entering an unknown directory
make: *** /lib/modules/2.6.28-11-generic/build: No such file or directory. Stop.
make: Leaving an unknown directory
make[1]: *** [default] Error 2
make[1]: Leaving directory `/home/dea/v4l-dvb/v4l'
make: *** [all] Error 2

Am I in the correct Kernel build directory and how do I configure it properly?