winlirc-list Mailing List for WinLIRC

Hi!
Now my Winlirc works.
I have a special problem with a learning remote. I tried to teach this 
remote the codes of my TV and of my sat-receiver. But the cursor keys 
were not learned correctly.
My idea: If Winlirc learns the keys, analyses it, and sends them to my 
learning remote in teaching modus, my remote would have a better program.
But this did not work too, because Winlirc could not analyse the codes. 
If I have a look in raw mode, I get alternating high and low numbers for 
the pulses.
Is Winlirc able to understand such codes?

-- 
                                Mit freundlichen Gruessen

                                      Wolfgang Wienke

I have a custom made reseiver/transmiter in COM1
I also have a winfast xp deluxe PCI tuner with an infrared receiver in =
COM2
I had them both connected and I was using a winlirc client made in VB to =
control my amplifier, my satelite receiver and the winfast PVR program. =
Until now I beleived that the commands sent by the trasmiter where =
received by the winfast receiver and so I could control Winfast PVR. =
Yesterday I removed the Winfast receiver from COM2 because I wanted to =
use it for something else. And what I found was that Winfast PVR was =
still receiving the commands from my VB application allthough the =
winfast infrared receiver was not connected.
How is this done. Is winfast PVR listening to the TCP port of winLIRC or =
does intersept the com port ?=20
I also tried the following. I close winLIRC server and trid to send =
command to WINFAST. Nothing happened. I loaded again and it was working. =
So I must conclude that Winfast PVR is listening to winLIRC. Is this =
documented anywhere ?

Hi,

I need help. My Pioneer receiver VSX-D608 is missing the remote and I need 
to set it's digital input. The files on the archive work with the basic 
functions but none of them carry the setup button.

Can anybody help capturing those codes?


Thanks in advance!

Robert 

Hi,
I want to use winlirc with a laptop with build-in IR-receiver.
Till now, it doesn't work.
Is this unpossible, if the receiver is not listed in the winlirc 
hardware list? (its listed as a winbond IR-Receiver)
I also want to use winlirc on a PC. If I buy an USB-IR-receiver, will it 
work?
A there other programs, which will work with the winbond or an 
USB-IR-receiver?
Do I need a spezial remote, or schould every remote do?

-- 
                                Mit freundlichen Gruessen

                                      Wolfgang Wienke

Hello again,

Since WinLirc will not work with my laptop's built-in IRDA receiver, I
am looking at buying an external one. Now the WinLirc web site
mentions IRDA receivers connected to the serial port, but I can only
find USB ones in the shops. Will WinLirc work with a IRDA receiver
conencted to my laptop via USB ?

Thanks a lot
Antoine

On 4/26/06, Jim Paris <ji...@jt...> wrote:
> > oh ok, thanks. Any alternative ? Do you know of a software that would work
> > with my IRDA ?
>
> I personally haven't played with any IrDA stuff, but a quick Google
> search shows
>   http://www.pcremotecontrol.com/irda.html
> which might have some useful information.
>
> -jim
>

After building and troubleshooting my IR hardware, I was driving myself
crazy trying to get WinLirc to sucessfully work with my remote. Sometimes I
could get a key to learn, but it would barely have more successes than
faults. After analyzing, bet I could get is very intermittent operation. I
was on the verge of tossing my homebrew IR hardware and trying to find a
commercial product when U decided to give it one last try on the actual
machine this project would be running on. BAM, all worked perfectly. My
development PC is a Dual Core AMD 64 bit cpu running Windows XP 64 bit
edition. I guess the OS figures 32 bit software couldn't be that important
and wont give it the necessary cpu attention for WinLirc to work correctly.

For development purposes, I wrote a Stay on Top windows program with buttons
that mirror my remote that emulates WinLirc. This approach is working well.
It's very remote specific, but anyone that wants it is welcome to the code.
It's done with Borland Cbuilder 2006 and currently mirrors a Weemote dV
setup for Sony. It's nothing fancy, but I'll be glad to share...

Hi all,
I need use winlirc with my pinnacle pctv dvb remote controle.
Please i need help
Sorry for using a very bad english but I'm also french

_________________________________________________________________
MSN Messenger : discutez en direct avec vos amis ! 
http://www.msn.fr/msger/default.asp

Hey guys,

 

I'm doing some work with Infrared and the Iguanaworks IR transmitter in C#
using some concepts from Winlirc.

 

http://www.hanselman.com/blog/PerformanceOfSystemIOPortsVersusUnmanagedSeria
lPortCode.aspx

I've been unable to push this thing fast enough.I can't get a full 96 cycles
(the 2400us header) out of it on a 3gHz P4 under no load. 

 

Is this just a "my very fast machine isn't fast enough" issue? That's
surprising, as the CPU isn't working.am I i/o port bound?

 

I'm using EscapeCommFunction and according to a number of profilers, that's
all my system is doing! 

 

Thoughts? 

 

Scott Hanselman

 

I've found a bug in Winlirc 0.6.5 that deals with tranismitting codes on the Tx line.  In summary, the data buffer used to send the carrier signal is incorrect, so the carrier signal that gets sent is not consistent.  The problem stems from an integer buffer (32 bit) that gets filled with an 8 bit value (0x12 or 0x55).  For my particular case, I was using a frequency greater than 48000 hz so the buffer value was 0x55.  Because the buffer is integer size but the COM port functions transmit bytes, the output on the serial port would be 0x55, 0x00, 0x00, 0x00 instead of a constant 0x55, 0x55, 0x55, 0x55.  Needless to say, the output carrier signal was wrong and my target device didn't recognize the signal.
 
Fixing the bug is fairly simple, either change the buffer size to a character size or change the routine that fills the buffer from 0x55 to 0x55555555.  For my testing, I chose the second option.  With the change, my Scientific Atlanta Explorer 2000 box (actually 2100) now recognizes the signal without problem.
 
I have seen messages about others having problems with the Scientific Atlanta boxes, though this bug likely affect any box with a high frequency (>48000 hz) carrier (it will likely affect slower speed remotes too, though the impact is less of a problem).   After this change, these boxes can easily be controlled with a simple transmitter (LED, resistor) connected to the TX line.  This should be a great help to those with MythTv or GBPVR.
 
BTW, I initially tried using the DTR approach, though the highest frequency I could generate was about 10K below what I needed (~45k vs. ~56k).  It's quite possible this problem is limited to XP and the task sharing time-slice resolution.
 
Once these changes are made, the Explorer_2000.cfg file can be used to control a Scienific Atlanta Explorer 2000 or 2100 box, though you'll need to modify the .cfg file and add the following line:
 
frequency    56000
 
I suspect the other Scientific Atlanta configuration files will need the same change.
 
Ron Fries
 
 
 
 
 
 
 
 
 
 


Check out AOL.com today. Breaking news, video search, pictures, email and IM. All on demand. Always Free.
________________________________________________________________________
Check out AOL.com today. Breaking news, video search, pictures, email and IM. All on demand. Always Free.

 I've found a bug in Winlirc 0.6.5 that deals with tranismitting codes on the Tx line.  In summary, the data buffer used to send the carrier signal is incorrect, so the carrier signal that gets sent is not consistent.  The problem stems from an integer buffer (32 bit) that gets filled with an 8 bit value (0x12 or 0x55).  For my particular case, I was using a frequency greater than 48000 hz so the buffer value was 0x55.  Because the buffer is integer size but the COM port functions transmit bytes, the output on the serial port would be 0x55, 0x00, 0x00, 0x00 instead of a constant 0x55, 0x55, 0x55, 0x55.  Needless to say, the output carrier signal was wrong and my target device didn't recognize the signal.
 
Fixing the bug is fairly simple, either change the buffer size to a character size or change the routine that fills the buffer from 0x55 to 0x55555555.  For my testing, I chose the second option.  With the change, my Scientific Atlanta Explorer 2000 box (actually 2100) now recognizes the signal without problem.
 
I have seen messages about others having problems with the Scientific Atlanta boxes, though this bug likely affect any box with a high frequency (>48000 hz) carrier (it will likely affect slower speed remotes too, though the impact is less of a problem).   After this change, these boxes can easily be controlled with a simple transmitter (LED, resistor) connected to the TX line.  This should be a great help to those with MythTv or GBPVR.
 
BTW, I initially tried using the DTR approach, though the highest frequency I could generate was about 10K below what I needed (~45k vs. ~56k).  It's quite possible this problem is limited to XP and the task sharing time-slice resolution.
 
Once these changes are made, the Explorer_2000.cfg file can be used to control a Scienific Atlanta Explorer 2000 or 2100 box, though you'll need to modify the .cfg file and add the following line:
 
frequency    56000
 
I suspect the other Scientific Atlanta configuration files will need the same change.
 
Ron Fries
 
 
 
 
 
 
 
 
 
 
________________________________________________________________________
Check out AOL.com today. Breaking news, video search, pictures, email and IM. All on demand. Always Free.

This is my successfull story with WinLirc and Dscaler.

First problem was to get a working IR TX/RX system since I had difficulties
getting a proper IR IC.

I had an old and broken Philips VHS-VCR complete with remote. The solution
was simple. I desoldered the IR IC from the VCR, bought the remaining
electronics (which are far easier to find) and build the little system
following the basic schematics http://www.lirc.org/images/schematics.gif

WinLirc had no problem finding the serial receiver, agetting usefull signals
from it saving a working .conf file.

Second problem was to let DScaler receive WinLirc signals. Well,
WinLirc_to_DScaler was the solution (http://www.tfm.ro). It gets the
messages from WinLirc and sends them as keyboard shortcuts to DScaler.

Now everything works and it costs only a bunch of Euros. Cheap and working
:-)

Contact me via email if you need more details on the hardware-software
(maybe the working winlirc .conf file and the Winlirc_to_Dscaler
configuration file).

   Roberto

-- 
Echte DSL-Flatrate dauerhaft für 0,- Euro*!
"Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl

oh ok, thanks. Any alternative ? Do you know of a software that would work
with my IRDA ?

On 4/26/06, Jim Paris <ji...@jt...> wrote:
>
> > My laptop has a built-in receiver, so first of all can WinLirc
> > work with this ?
>
> No, sorry, the laptop's IRDA will not work.
>
> -jim
>

> My laptop has a built-in receiver, so first of all can WinLirc
> work with this ?

No, sorry, the laptop's IRDA will not work.

-jim

Hello,

I am having trouble getting Winlirc to work with my laptop. All I can find
as documentation seem to indicate how to set it up to work with an EXTERNAL
IR receiver. My laptop has a built-in receiver, so first of all can WinLirc
work with this ?

If yes :
- Which COM port should I choose in the config screen ? I Guess "the COM
port of the receiver", but where do I find this out ?
- Also, should I choose RX device or DCD device ?

Thanks for your answers, or for pointing me to a forum / site where I can
find them.

Another idea is that the mpeg playback is consuming too much cpu power so
the timing looses accuracy when decoding the received signals.


> --- Ursprüngliche Nachricht ---
> Von: "Tomer Sivilya" <si...@gm...>
> An: "win...@li..."
> <win...@li...>
> Betreff: [WinLIRC] Winlirc doesn't work while playing mpeg file
> Datum: Thu, 23 Feb 2006 15:30:48 +0200
> 
> Hi,
> 
> I got a wierd situation where the winlirc works perfectly with my
> serial IRBlaster and controlling my STB of my sattelite TV.
> 
> However, once I have any MPEG file running (playing) the winlirc will
> flash in blue (as if sending a signal) but nothing really happening on
> the STB.
> 
> I use win XP Pro SP2. I assume it got something to do with a codec or
> something of that sort...
> 
> Thanks for any help...
> 
> Tomer.
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> language
> that extends applications into web and mobile media. Attend the live
> webcast
> and join the prime developer group breaking into this new coding
> territory!

-- 
Telefonieren Sie schon oder sparen Sie noch?
NEU: GMX Phone_Flat http://www.gmx.net/de/go/telefonie

Hi Tomer,

I would recommend to temporarily disable WinLIRC and to use a port monitor
such as "portmon" from the sysinternals site while playing that mpeg file.
Maybe your player or codec is accessing the serial port for some reason?!

Cheers,
Hartwig

> --- Ursprüngliche Nachricht ---
> Von: "Tomer Sivilya" <si...@gm...>
> An: "win...@li..."
> <win...@li...>
> Betreff: [WinLIRC] Winlirc doesn't work while playing mpeg file
> Datum: Thu, 23 Feb 2006 15:30:48 +0200
> 
> Hi,
> 
> I got a wierd situation where the winlirc works perfectly with my
> serial IRBlaster and controlling my STB of my sattelite TV.
> 
> However, once I have any MPEG file running (playing) the winlirc will
> flash in blue (as if sending a signal) but nothing really happening on
> the STB.
> 
> I use win XP Pro SP2. I assume it got something to do with a codec or
> something of that sort...
> 
> Thanks for any help...
> 
> Tomer.
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> language
> that extends applications into web and mobile media. Attend the live
> webcast
> and join the prime developer group breaking into this new coding
> territory!

-- 
Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko!
Satte Provisionen für GMX Partner: http://www.gmx.net/de/go/partner

Hi,

I got a wierd situation where the winlirc works perfectly with my
serial IRBlaster and controlling my STB of my sattelite TV.

However, once I have any MPEG file running (playing) the winlirc will
flash in blue (as if sending a signal) but nothing really happening on
the STB.

I use win XP Pro SP2. I assume it got something to do with a codec or
something of that sort...

Thanks for any help...

Tomer.

I bought a Packard bell remote from tekgems.
That brought me to WinLirc. I looked in the archives and saw the post =
about Autohotkeys and took a look around and thought it looked alot like =
autoit V2.
I didn't study it much but did see some interesting things.
Alas prior to coming here I knew enough about autoIt that I was intent =
on using that to expand upon winlirc.

I/you will  have to use the beta version of AutoIt to realize the power =
of what we want to achieve. It grows monthly.

In the \beta\examples folder is a script to toggle between beta and =
release versions.

Note: the SciTe editor will use the release version help file unless you =
move the beta help files to that directory.

=20
Release version
http://www.autoitscript.com/autoit3/downloads.php


Beta version: Needed for these scripts
http://www.autoitscript.com/autoit3/files/beta/autoit/autoit-v3.1.1.105-b=
eta-Setup.exe

SciTe editor/IDE
http://www.autoitscript.com/autoit3/scite/downloads.php

Help forum
http://www.autoitscript.com/forum/index.php?

By connecting AutoHotkey to WinLIRC, you can assign a macro to each of =
the
buttons on your remote control.  Such macros can automate virtually =
anything
by sending keystrokes and mouse clicks to windows of your choice.

To experiment with this client without having to read much of anything,
follow these steps:
1) Download and install AutoHotkey from =
http://www.autohotkey.com/download/
   (1592 KB and a very fast install).
2) Download the WinLIRC client script (11 KB) from
   http://www.autohotkey.com/docs/scripts/WinLIRC.ahk
3) With WinLIRC running, launch the script above by double-clicking it.
4) Press some buttons on your remote control. The script will briefly
   display the name of each button in a small window.

If everything works okay, browse the examples in the script and set up a =
few
of your buttons.

To read more about the client without downloading it, see
http://www.autohotkey.com/docs/scripts/WinLIRC.htm

Since this client is new, feedback about it is appreciated.  Feel free =
to
reply to the mailing list or e-mail su...@au...

More about AutoHotkey: It's an open-source utility that specializes in
automation and hotkeys for keyboard, mouse, and joystick.  It can also
expand abbreviations as you type them. For example, typing "btw" can
automatically produce "by the way".

Regards,
Chris

<html><div style='background-color:'><P>Dear all:</P>
<P>i am new to winlirc, but have to rush my project in three days, so i 
turn to you for some help, thanks very much</P>
<P>now i have got the code for a sony TV by running winlirc after building 
the receiver and transmitter. What i want to do is to send the code out 
from my another program with the transmitter, i don't want to write the 
code unrelated with sending out code into it to make the&nbsp;program slow 
down.I have read some of the codes in winlirc, can you give me some hint 
about what classes are related with sending out code with the transmitter? 
do i need to write the Cserver into the program? thanks</P>
<P>Also i am not familiar with the threads program, is it necessary for me 
to use it if only want to send the code out? in fact, i don't want to use 
it because my another program already too complex, i worry i cannot make 
the threads running without disturbing.</P>
<P>thanks</P>
<P>Nice day ahead</P>
<P>cheers<BR></P><BR><BR><BR>
<DIV>
<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
<IMG height=12 src="http://graphics.hotmail.com/emrose.gif" 
width=12><EM><FONT face="Verdana, Geneva, Arial, Sans-serif" 
color=#ff0099>Shirley</FONT></EM><IMG height=12 
src="http://graphics.hotmail.com/emrose.gif" width=12></P>
<P><FONT color=#ff0099 size=5></FONT>&nbsp;</P>
<P><FONT color=#ff9900></FONT>&nbsp;</P></DIV></div><br clear=all><hr>使用世
界上最大的电子邮件系统―   <a 
href="http://g.msn.com/8HMACNCN/2749??PS=47575" target="_top">MSN Hotmail 
</a> Get 2 months FREE*. </html>

All,

I have winlirc. I have the receiver and transmitter from irblaster.info. 
I understand there are 2 units from
irblaster.info - one for using with windows and one for using with 
linux. I am using the one for windows.
I think it is on the TX pin versus the DTR pin.

I did the learn remote. Everything seemed to be going fine. (using a 2 
gig laptop and Win XP).
I sent the first command code using "transmit VIZIO av 1" and the TV 
change to AV...
Fantastic.

However, If I send send the command, wait a couple seconds and send the 
command again...
sometimes it works sometimes it doesnt. I have not gotten past 40 
successful sends/receives.
I need this to be 100%.

I have re-learned and re-learned. I have chosen anywhere from 2 as the 
eps to 70. Seems to not
make a difference... I can set there with the TV remote all day and not 
get a miss....

Below is my file...

I am not running anything else on my laptop at this time. no DVD... 
nothing..

Help is most appreciated.

Jerry

-------------------------
#
# this config file was automatically generated
# using WinLIRC 0.6.5 (LIRC 0.6.1pre3) on Wed Aug 24 09:00:07 2005
#
# contributed by
#
# brand:             VIZIO
# model:
# supported devices:
#

begin remote

 name  VIZIO
 bits           16
 flags SPACE_ENC
 eps             2
 aeps          100

 header       9088  4363
 one           675   441
 zero          675  1566
 ptrail        675
 repeat       9089  2127
 pre_data_bits   16
 pre_data       0xDF20
 gap          39775
 toggle_bit      0


     begin codes
         rgb                      0x000000000000E619
         av                       0x000000000000758A
     end codes

end remote

test first one failed.

The 3100 is very hard to control through lirc; I guess it is the same with 
WinLirc. In order to get it to control my 3100 using lirc on 2.4 kernel, I 
had to tweak every single button independantly. I created a special config 
where each button was defined in a separate remote control definition with 
tweaked header/one/zero values. This was on 2.4 kernel and that's the only 
way I could get it to work reliablebly. When I upgraded to 2.6 kernel, even 
the tweaking did not work. What I ended up doing is having linux send 
commands through the serial port to a microcontroler who blasts IR to the 
3100.


----- Original Message ----- 
From: "Aman Singer" <am...@as...>
To: <win...@li...>
Sent: Wednesday, July 06, 2005 7:51 PM
Subject: [WinLIRC] WinLirc, blind users, and Bell express VU remote


> Hi, all.
> Sorry to disturb, but I have three questions, if I may ask them.
> First, I am totally blind. I'm wondering if, through WinLirc, I can just
> enter keys on the keyboard and use the keyboard as a remote control. That
> is, I want to enter numbers by hand and just have those sent through the 
> IR
> blaster to the box I'm trying to control. Is this possible, or must I 
> click
> on a pictured remote on the screen? I know this could be easily found out 
> by
> using the program, but I don't yet have the IR blaster to test with and
> would like to know before buying it whether I can use it.
> Secondly, I'm trying to get Winlirc, an IR transmitter, and a Bell
> Express View 3100 unit to work together. The below instructions file came
> from the remotes page on lirc.org. The WinLirc page says that WL supports
> many of the features of Lirc configuration files. Would the file below be
> supported, if I may ask?
> Finally, does anyone here use the Bell Express Vu 3100/dish network
> 301 receiver? I've heard things about shortening the repeat rate, and 
> would
> like to talk to someone who's been through the hoops.
> Thanks in advance.
> Aman Singer
>
> # This file was painstakenly created manually using raw codes intrerpreted
> # and converted from a Pronto ccf file.  I always meant to add more 
> buttons
> to
> # it, but I know now I never will.  It currently controls the number keys,
> the
> # power button, the cancel button and the up key.  Therefore, it should 
> have
> # enough for controlling most popular PVR software.
> # If anyone really needs more buttons, email me and I might be motivated 
> to
> # update it.
> #
> # contributed by: kjones95 (at) cogeco (dot) ca
> # brand:   Echostar 301, Dishnet various and Bell ExpressVu 3100
> # model no. of remote control:  Don't know
> # devices being controlled by this remote: See above
> #
> # manually converted to regular config file using echostar/DBS (CB)
> #
> # Updated by chris (at) cnpbagwell (dot) com to include missing
> # remote buttons.  The previous missing "select" button is important
> # to speed up channel changing.
> #
>
> begin remote
>
> name 3100
> bits           16
> flags SPACE_ENC
> eps            30
> aeps          100
>
> header        400  6100
> one           400  1700
> zero          400  2800
> ptrail        400
> gap          6200
> min_repeat      4
> toggle_bit      0
>
> frequency    56000
>
> begin codes
> power                     0x0000000000000800
> 1                        0x0000000000001000
> 2                        0x0000000000001400
> 3                        0x0000000000001800
> 4                        0x0000000000002000
> 5                        0x0000000000002400
> 6                        0x0000000000002800
> 7                        0x0000000000003000
> 8                        0x0000000000003400
> 9                        0x0000000000003800
> select                   0x0000000000004000
> 0                        0x0000000000004400
> cancel                   0x0000000000004800
> guide                    0x0000000000005000
> cancel2                  0x0000000000005800
> right                    0x0000000000006000
> up                       0x0000000000006800
> left                     0x0000000000007000
> down                     0x0000000000007800
> sys_info                 0x0000000000009000
> *                        0x0000000000009800
> end codes
>
> end remote
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> ____________________________________________________
> This message was sent to the WinLIRC mailing list
> win...@li...
> https://lists.sourceforge.net/lists/listinfo/winlirc-list 

Hi, all.
	Sorry to disturb, but I have three questions, if I may ask them.
First, I am totally blind. I'm wondering if, through WinLirc, I can just
enter keys on the keyboard and use the keyboard as a remote control. That
is, I want to enter numbers by hand and just have those sent through the IR
blaster to the box I'm trying to control. Is this possible, or must I click
on a pictured remote on the screen? I know this could be easily found out by
using the program, but I don't yet have the IR blaster to test with and
would like to know before buying it whether I can use it.
	Secondly, I'm trying to get Winlirc, an IR transmitter, and a Bell
Express View 3100 unit to work together. The below instructions file came
from the remotes page on lirc.org. The WinLirc page says that WL supports
many of the features of Lirc configuration files. Would the file below be
supported, if I may ask?
	Finally, does anyone here use the Bell Express Vu 3100/dish network
301 receiver? I've heard things about shortening the repeat rate, and would
like to talk to someone who's been through the hoops.
	Thanks in advance.
	Aman Singer 
   
# This file was painstakenly created manually using raw codes intrerpreted
# and converted from a Pronto ccf file.  I always meant to add more buttons
to
# it, but I know now I never will.  It currently controls the number keys,
the
# power button, the cancel button and the up key.  Therefore, it should have
# enough for controlling most popular PVR software.
# If anyone really needs more buttons, email me and I might be motivated to
# update it.
#
# contributed by: kjones95 (at) cogeco (dot) ca
# brand:   Echostar 301, Dishnet various and Bell ExpressVu 3100
# model no. of remote control:  Don't know
# devices being controlled by this remote: See above
#
# manually converted to regular config file using echostar/DBS (CB)
#
# Updated by chris (at) cnpbagwell (dot) com to include missing
# remote buttons.  The previous missing "select" button is important
# to speed up channel changing.
#

begin remote

name 3100
bits           16
flags SPACE_ENC
eps            30
aeps          100

header        400  6100
one           400  1700
zero          400  2800
ptrail        400
gap          6200
min_repeat      4
toggle_bit      0

frequency    56000

begin codes
power                     0x0000000000000800
1                        0x0000000000001000
2                        0x0000000000001400
3                        0x0000000000001800
4                        0x0000000000002000
5                        0x0000000000002400
6                        0x0000000000002800
7                        0x0000000000003000
8                        0x0000000000003400
9                        0x0000000000003800
select                   0x0000000000004000
0                        0x0000000000004400
cancel                   0x0000000000004800
guide                    0x0000000000005000
cancel2                  0x0000000000005800
right                    0x0000000000006000
up                       0x0000000000006800
left                     0x0000000000007000
down                     0x0000000000007800
sys_info                 0x0000000000009000
*                        0x0000000000009800
end codes

end remote

> I recently bought an airstar2 pci tv-card which is bundled with a simple
> ir-receiver and remote for winlirc. all just worked fine until some days
> ago the receiver didn't work anymore (it did receive nothing). so got
> myself a "TSOP 1728" ir-diode and replaced the old one. now winlirc
> receives again as it reports a lot of things when clicking on "raw
> codes" and pressing some of the remotes keys. but it does not seem to
> recognize the key codes. i reloaded the configuration file which is on
> the tv-cards cd but things still did not work. i also tried to relearn
> the codes by winlircs learning function but it complains about an
> inconsistent signal.
> what am i doing wrong?

The new IR module might have slightly different response
characteristics, which would be why your old config file might not
work.  You could try adjusting some of the timings in your config file
based on what you see in raw codes (adjust the gap, pulse widths,
etc). See also http://winlirc.sourceforge.net/debug.html for more.

-jim