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" <aman@...>
To: <winlirc-list@...>
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
> winlirc-list@...
> https://lists.sourceforge.net/lists/listinfo/winlirc-list
|