R. Geoffrey Newbury wrote:
On Thu, 24 Nov 2005 10:16:35 -0500, Len Reed wrote:
Steve Adeff wrote:
This is what I did:
Silverstone LC16M-S
Speaking of the remote...I assume that the IR receiver is limited to the
IR codes that the Silverstone remote can send. (Contrast: a homebrew
LIRC serial remote, which can handle almost anything.) Is that true?
Are you using this for your remote control?
I have the Silverstone LC11-M case. It uses the iMon Median VFD and iMon
PAD IR.
I can tell you that the IR receiver does not appear to be limited in any
way on its reception of IR signals.
Very interesting. My ati wonder USB receiver (from a "Lola" x10 system)
seems only to get its own codes.
I happened to be fighting with my lirc setup, and getting no response. I
had mode2 running, when I used the TV remote to change the volume of the
TV, which was not hooked up to mythtv. And I was suprised to see output on
the monitor! A quick check showed that the IR receiver/mode2 combo could
handle a couple of the various remotes lying around. And my lirc setup was
fine: my Silverstone remote had dead batteries! I'm buying some more
batteries today so I can check out the remaining orphan remotes.
I'd be interested in knowing what you find out.
BTW I think that this could provide a means of mapping/determining the key
codes of any remote. No that you can do much with that, unless you have a
'learning' remote which you can program at the byte level or for example,
a Hewlett Packard calculator with IR output, which can be programmed at
the byte level, or for another example, a bluetooth enabled cell phone
which has a Java JVM in it, and a Java program to present the choices.....
I'm interested in getting arbitrary signals for two reasons:
1. determine codes from the various remotes, as you say. (I can now do
that with a homebrew receiver, but it needs a real -- not USB -- serial
port and those are rare these days. Also, my receiver, built from the
low-end of what's on lirc.org, is not really suited to production use.)
2. Allow use of the *best* remote from my home theatre system. If I can
process any code, I can pick the remote based solely on size and keypad
arrangement. (Many remote controls seems to have be designed for use by
some species other than H. sapiens.) Also, when the most-pressed keys
wear out, I can replace it without having to buy an expense matching
replacement.
My plan is to capture the IR codes at the computer and then translate
and retransmit (over a real serial port use LIRC and wires to small IR
diodes) to the various equipment. This allows me to use an Athlon-64
running Linux to control things, rather than a so-called Universal remote.
Consider the following as an example. If I switch to "DVD" then one
button labeled DVD on the remote could cause all of the following to happen:
a. switch HT amp to DVD audio input
b. raise volume on amp to compensate for lower input (skip if already in
DVD mode).
c. switch TV input to DVD
d. set TV aspect ratio
e. turn off TV's built-in speakers (which I may use for simple viewing,
e.g., the news, instead of the surround sound system).
Subsequent presses of FF, REW, pause, etc. would be translated and
passed on to the DVD player. Pressing another button would reconfigure
everything for mythtv.
Much of the above can be done without so elaborate a scheme, but no
univeral remote is going to allow the flexibilty that this will. The
end result is a system where the complexity is hidden inside LIRC setup
and perl srcripts inside the HT computer, and a single remote provides a
simple, consistent, and powerful control point.
_______________________________________________
mythtv-users mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
