On Sat, 9 Jul 2005 07:20:26 -0700
Paul Miller <paul@...> wrote:
> When you load the driver in debug mode, does it print anything=20
> interesting to syslog?
After looking at things more carefully, I've found that setting mgradient
to 1000 eliminates NW, NE, SW, SE.. which is what I was after. However, I
still find this thing difficult to control.
mdeadzone seems to slow the response time, before codes are parsed into
directions, but what I think I need is some way to just make it less..
The norb definitely seems to be made for mouse use. Without constant
feedback, it seems impossible to know when you'd "strayed" off the centre
(W-E centre) point. When holding the remote with my right hand, I
invariably end up triggering East when trying for an North. When holding
with my left, I get West sometimes, when going for North.
I don't get these problems when pushing South. South is always there. I
suspect that the way the remote is crafted, means that your hand sits in a
certain spot when holding it, and therefore N is effected by holding
pressure, and S is not. A person needs to hold the remote, so that their
hand (and thumb) are approaching it from below it, if the intention is to
use the entire remote.. and not just the norb.
I think what is required, in order to make the norb usable, is that the W
and E directions must be shortened on the upwards side.. or perhaps
shifted overall. A parameter to "shift" the W-E "down" or "up" would be
quite neat, and probably fix the issue. While I can't see how someone
would hold the remote above centre (as many likely hold it below centre),
I suppose it is still possible.
I'm not sure if shortening the W/E responsiveness would be fine on its
own, as it may get more difficult to trigger those movements.
=46rom the code, it looks like (in order to "shorten" W/E triggers), W/E
would have to be restricted by some number. For example, any W/E movement
would have to be under/over -36/36, or else they would shunt to N/S
movements. That would effectively widen N/S movements, but it might be
helpful to simple create a unresponsive section (other than just
(-)46/(-)46 in that area under -36 W / over 36 E.
I'm not sure if you know what I mean here, so I'll stop now. ;)
> On Friday 08 July 2005 6:51 pm, Brad Barnett wrote:
> > I've been using the ATI Remote Wonder II, but the centre control
> > annoys me. There's something odd about it, I seem to have a hard
> > time controlling things via it.
> > Has anyone else run into this problem? Specifically, sometimes
> > "up" simply stops working, and occasionally switching "aux" modes
> > seems to help. When "up" stops working, I usually end up with
> > up-left or up-right coming out of the remote.
> > I've played with mgradient and mdeadzone, but nothing I attempt
> > seems to completely fix the problem.
> > I notice this in the source:
> > * c. The mouse norb is much more sensitive than on the rw1. It
> > emulates * a joystick-like controller with the second byte
> > representing the x-axis * and the third, the y-axis. Treated as
> > signed integers, these axes range * approximately as follows:
> > *
> > * x: (left) -46 ... 46 (right) (0xd2..0x2e)
> > * y: (up) -46 ... 46 (down) (0xd2..0x2e)
> > *
> > * NB these values do not correspond to the pressure with which
> > the mouse * norb is pushed in a given direction, but rather
> > seems to indicate the * duration for which a given direction is
> > held.
> > *
> > * These are normalized to 8 cardinal directions for easy
> > configuration via * lircd.conf. The normalization can be fined
> > tuned with the mdeadzone and * mgradient parameters as described
> > below.
> > *
> > * d. The interrupt rate of the mouse vs. the normal keys is
> > different. *
> > * mouse: ~27Hz (37ms between interrupts)
> > * keys: ~10Hz (100ms between interrupts)
> > *
> > * This means that the normal gap mechanism for lircd won't work
> > as * expected; is emit_updown>0 if you can get away with it. */
> > Does anyone have any suggestions to fine tune the mouse "norb"?=20
> > I'm just using this for MythTV, so I really only want
> > up/down/left/right to work. It would be great if I could get rid of
> > all angled codes, and just increase the 4 primary directions to
> > fill the empty space.
> > Also, I have a Motorola DSR315, Starchoice branded satellite
> > receiver. I'm currently using the remote codes from lirc.org,
> > specifically:
> > # brand: Motorola
> > # model no. of remote control: IRC442 (PN: 487008-001)
> > # devices being controlled by this remote: Motorola (DSR305SC)
> > StarChoice receiver, IBM T40 (237372U) laptop #
> > Does anyone have any codes for the above, but using alternate
> > remote codes? I have two receivers, and would like to control both
> > via one IR Blaster.
> > Thanks!
> > -------------------------------------------------------
> > This SF.Net email is sponsored by the 'Do More With Dual!' webinar
> > happening July 14 at 8am PDT/11am EDT. We invite you to explore the
> > latest in dual core and dual graphics technology at this free one
> > hour event hosted by HP, AMD, and NVIDIA. To register visit
> > http://www.hp.com/go/dualwebinar