Troubleshooting Actisys IR200L controller

[rob762]

Hi folks,
Is there any official troubleshooting guide for infra red remote control of an external cable/tuner box from Sage Recorder?
I have previously had the remote control functioning perfectly but at a certain point, it just stopped working.

My set up is a Gigabyte Pentium 4 motherboard (socket 478) using a Hauppauge PVR-350 (PAL version) tuner card and Windows XP professional + SP1, and Sage Recorder 1.3.8

Since the problem started, I've rebuilt the PC from "scratch" (including reinstallation of Hauppauge drivers etc) replaced the IR-200L transceiver, tried the IR on a different serial port, tried a different motherboard, tried controlling different devices from different remotes, tried the newer beta Sage Recorder, ad naseum.

All I am left with is being able to "learn" remote codes through Sage Recorder, apparently successfully, but when it comes to sending commands to the cable or tuner box, they simply do not react.

Please let me know, from a support perspective, if there are any common problems that people have when trying to fix their remote controlling.

Thanks.

[SHS]

did put IR-200L in front of box?.

[rob762]

Hi SHS,
Yes everything is lined up properly. It was working perfectly until a certain point, then it just stopped working.
Suspecting a software glitch or corruption, I fully blanked out the PC (formatted hard disks etc) and started from fresh in the hope that the "problem" went away: it didn't.

[dkardatzke]

Make sure you didn't install any of the Actisys software when you started fresh. Also when you test each channel number in SageRecorder, does it send the right code and do you see the channel number appearing on your cable box?

[Narflex]

Also, check to see if the lights inside the Actisys blink when its supposed to be transmitting the codes, they should.

[rob762]

Thanks for the suggestions,
* I definitely haven't installed any drivers for the Actisys (I double-checked that no "Infrared device" is listed in the Hardware Device listing)
* After "teaching" sagerecorder the digits, trying the Test on each digit (with the Actisys pointed directly at the cable box) gets no reaction from the box at all. The box is otherwise responding to IR remotes (my original remote plus my "all in one" learning remote)
* The Actisys unit I have is fully enclosed (black casing) with a IR window that appears opaque - where should I look for flashing lights?
* FYI: I have two new Actisys IR200L units that I bought from Frey about 3 weeks ago, all my testing has been with one of these
* One thing I've noticed when adding a new "remote" into Sage Recorder, the "Carrier" reported seems to vary from time to time as does the "bitrate" ... sometimes the bitrate is around the 500s, other times it's 480s or 470s.

Around the rest of these boards, I've seen suggestions about different methods to use when "teaching" the remote codes (tap, tap button instead of a single long press) - I'll try a few different things tonight.

[Narflex]

Let us know how it goes....you should see the blinky lights through the opaque window.

[Mark Lamutt]

Rob, why don't you upload your .IR file that is created so we can take a look at it. You'll need to rename the extension to .TXT from .IR so the board will accept it.

[rob762]

Hiyas,

I've tried teaching Sage Recorder my remote controller codes a few times, using both the "hold down button" and "tap tap tap" method

I see dim red blinking lights from inside the Actisys when I "test" each learnt button in Sage.

Unfortunately, the TV box doesn't react to any codes sent by the Actisys. I have tried pointing it at the box from different angles, but it's just not reacting at all.

I have attached my DGTEC.ir file (renamed .txt)

I would really love to get my remote controller working again!

[SHS]

Here something you can try using a Diff REMOTE and Deivce like VCR,TV, anything that has Remote with 0thur9 on it to see if will change the channel on that device if that dosen't work that most likely there something wrong with IR-200L you have.

The only thing that maybe worng with you ir file is the word SEL which I take it that it = 0
Maybe try edit this
DGTEC 38004 468 1 600 800 SEL
to
DGTEC 38004 468 1 600 800
and change
SEL 683
to
0 683
maybe that will work

[rob762]

Thanks SHS,
The "SEL" is indeed a button on my remote called SEL ... it's the "enter" button to confirm the one-digit channel selection (that's why there's no zero)

I have tried other devices and other remotes and tried to learn and replay other remote codes (I've tried my Digital TV box, my Cable TV box and my TV's remote codes) but nothing's working.

I do have an ace up my sleeve ... a spare brand-new Actisys still in it's wrapping ... I'll open it and try everything again with this new(er) Actisys IR200L

I am fast running out of ideas !!

But then again, the tough problems are the most fun to solve.

PS: in case anyone is wondering about the little hamster graphic I use with my posts ... it's to tempt all these cats in here!!

[SHS]

Just wondering but you install Intel Application Accelerator and Intel Chipset Software Installation Utility?.
In bios on that Gigabyte motherboard is com port set to auto or did apply a com port address to it by the way what model number on this board?.

[SHS]

In your bios dbl check thing over
Onboard Serial Port 1: Set to 3F8/IRQ4 that for COM1

Onboard Serial Port 2: Set to 2F8/IRQ3 that for COM2

If one of the COM PORT is set to
2F8/IRQ4 COM3
or
2E8/IRQ3 COM4
Then it is IRQ sharing which is very bad with Serial Port which can cause the IR-200L not work rigth in this case nor well it work rigth with USB to Serial Converter at lease the one I have dosen't work "Manhattan USB to Serial Converter (Model: UC232A)".

Also check
UART Mode Select: Set Normal Mode

[Narflex]

What's the details on your cable box?

Also, teach them a couple times again and post the IR files for each time, I want to look at the variance between them please.

[rob762]

OK I've checked the BIOS, the UART is "normal mode",
COM1: 3F8 IRQ 4
COM2: 2F8 IRQ 3
... i.e. the COM ports aren't set to "Auto"
My O/S is Windows XP with SP1
The motherboard is Gigabyte GA-8IEXP
I usually install the Intel INF / Chipset utility (it provides a driver for the SMBUS controller and others) and I install the driver supplied from the Gigabyte website for the integrated NIC, I also install the driver for my Leadtek A180 (Geforce 4) video card

My primary external tuner is my DGTEC Digital TV tuner (made for Australian DVB-T digital TV)

I'll teach it a few times, maybe twice in succession without rebooting and then two more times, each with a power-off / power-on reboot. I'll then post my IR files.

Stay tuned!

[rob762]

Here's the results of 4 remote learning sessions.

DGTEC1 & DGTEC2 performed one after the other without reboot
DGTEC3 performed after a power-off/power-on reboot
DGTEC4 performed after a power-off/power-on reboot

The DGTEC remains unresponsive to Actisys IR transmissions across all 4 of the learning files

[Narflex]

You're definitely getting consistent results for learning. The codes should be correct.

Another thought....have you tried moving the Actisys further away from your cable box (try a few feet)? If its too close, you can saturate the signal and that'll cause it to fail too. You wouldn't believe how many times I fell victim to that due to working in a cramped area.

[rob762]

Yes I have tried close-up (10cm) medium range (1m) and far-away (3m, 4m) infrared transmitting to the DGTEC box, no reaction at any time. My original remote and my "learning" remote all work at each of these distances.

I'm out of ideas now!

[Narflex]

Have you tried teaching the Actisys with the learning remote instead of the cable box remote? There's been instances where I've seen that work better.

[rob762]

Hi Narflex/Jeffrey
Thanks for the suggestion, yes I have tried teaching the remote using my "learning remote" in the past.
I haven't tried it recently, as I thought the original remote would be "better" somehow.
I'll run through another IR testing cycle using my universal remote and I'll report on my findings.
Rob.