ir200l and channels 160-169

[keith_marrocco]

I discovered last week that a seldom-used group of channels will not tune properly on my PVR350 with an IR200L pointed at a Dish 301 receiver. They end up on channel 10 instead of, say, channel 168. This happened four times in a row. I also have a 150 using the built-in blaster pointed at another Dish 301 receiver. I am running 1.08 on a system with Intel Celeron D, XP and 1G memory (a.k.a. "The Cheat".)

The day after my recordings failed I tried again. I tried to record four programs on 168. I again got channel 10 four times.

Live TV tuned to 168 correctly. I isolated live TV to the 150 and (priority?) recordings to the 350.

I started the GBPVR configuration utility and made various adjustments to the repeat count and delay. 168 tunes to 10.

I connected a TV to the CATV-out of the tuner and tried 168. The tuner showed receiving channels "1...6" and fails to 10 because there isn't a 16 in our lineup. (Which I'd guessed, but this just confirmed it.)

I tried making more adjustments to the delay and repeat values. 168 yields 16 which goes to 10.

122 goes to channel 122.

268 goes to channel 268.

I pointed a digital camera at the IR200L emitter. I entered 168. It went "Blink Blink ...". I entered 122. It went "Blink Blink Blink".

I raised and lowered and gently massaged repeat counts and delays. No effect.

I went through channels and isolated the problem to only 16X channels.

I looked at the log files. There were no obvious errors. I saw a reference to the IR200L.EXE. I tried running IRL200L.EXE from the command prompt. It entered test mode. It crashed. I tried running it from a DOS prompt. It entered test mode. It crashed. I tried running it from a DOS prompt with 168 as a parameter. It entered test mode. It crashed.

AppName: ir200l.exe AppVer: 0.0.0.0 ModName: as_ir200l.dll
ModVer: 0.0.0.0 Offset: 000031fc

I laid down on my side on the floor. I moved my legs as though I were running. I went around in circles in this position saying, "Wooo wooo wooo wooo. Wooo wooo wooo wooo." It didn't help. 168 still stops after the 6 and tunes to 10. 122 tunes to 122. Other channels tune as expected.

I love GBPVR as a replacement for my ShowStopper ReplayTV, and the money that would have gone into a competing commercial product will eventually end up as a donation for Sub to cover me and a friend I converted GBPVR. This isn't a slam. It isn't even terribly important, because I almost never record from those channels. The Cheat is not dead and tunes to all other channels correctly as far as I can tell. But there's something happening other than what should be happening, and I'm not going to be able to sleep until I figure out why and correct it.

Help?

K.

[sub]

I'd say it has either learnt the code for key '6' incorrectly, or you need to tweak the intercode delay or repeat count.

I looked at the log files. There were no obvious errors. I saw a reference to the IR200L.EXE. I tried running IRL200L.EXE from the command prompt. It entered test mode. It crashed. I tried running it from a DOS prompt. It entered test mode. It crashed. I tried running it from a DOS prompt with 168 as a parameter. It entered test mode. It crashed.

This isnt intended to be run manually. You didnt supply the many commandline parameters it needed.

[keith_marrocco]

Ok, thank you very, very much for the response.

I was able to replicate the issue across 26X and 6xx channels, which leads me to believe the suggestion about training is the issue. After a 6 is issued no further attempts are made to send additional digits for a given channel. I have had repeats of 2 through 8 and delays from 200 through 800 ms with no change in the behavior of the 6's. I've also moved the emitter back and forth from an inch to a foot and a half from the receiver. I'm going to try getting HIP going to see if the issue persists with it as well.

Thanks,

Keith

[keith_marrocco]

I tried with HEremote, shut down all GBPVR processes, and manually trained all the digits, and The Cheat still fails to send any digit following a 6. The tuner works fine when an actual remote is pointed at it. I'm suspecting something deeper than just poor training of digits. There was a thread a ways back that I think mentioned something about installing and disabling the drivers; may try kicking The Cheat by trying that next.

Keith