PDA

View Full Version : Missing something about repeating events



levyshay
October 13th, 2002, 12:55 PM
I can now clearly see that all of the buttons I was trying to get to repeat send one valid IR code and then repeat some other and different code, usually 010000000000 or 020000000000.
Hi, You get this code because your remote is sending just one pulse to indicate repeat.

Is this common with remotes? Do people have ways of making Girder handle this? I can come up with a few but they seem pretty complicated since the repeat code is always the same. Is it possible it's something with my IR receiver? Anyone seen this before?
Yes, It's common, I have a suggestion, and it is complicated, My suggestion is to make to commands for each key you want to have repeat on, and when the first key is pressed it'll enable the repeat command for this key with a timeout.
Example:
Volume Up:(mostly needed repeat)

Multicommand-Volume up on 1st press (Triggered by volume up key)
+Do Volume up.
+Alarmtimer: Enable VolumeUpRepeat. (On timeout disable)

Multicommand-Volume up on repeat (Triggered by repeat key - 010000..)
+Do Volume up.
+Alarmtimer: Restart timer (Add more time)

I assume you don't need repeat for most buttons, I didn't have repeat with my receiver (UIRT2) and my remote, eventually I've fixed it, and then I noticed I need repeat only for volume related commands.

I read somewhere that COM port speed settings sometimes help and I've been tinkering with the IR plugin settings in Girder with no luck.
TIA
In your situation changing COM port speed wouldn't help, but what can defiantly help is trying to change a remote, since you use a universal remote you might find a code for it which will solve it.
Most remotes transmit code only once, and then just a pulse for repeat, so that's why you get 01000000 or 020000000 (It's probably a pulse count) I've succeeded finding a remote that transmits the same first code pressed when it's being hold also.

Good Luck,
Shay Levy.

Francois
October 13th, 2002, 12:55 PM
Have you tried the event logger plug-in? It will tell you which events Girder is seeing and you can configure it to tell you when they occur.

good luck!

cntr_ice_junkie
October 13th, 2002, 12:55 PM
Somehow, I'm missing something about being able to repeat events from a remote.

I've got Girder 3.2.4 and I've tried messing with buttonmode 1.22 and I think 1.3. Neither have the "repeat" option for "on first press" in the buttonmode plugin settings which I saw mentioned in some other threads -- is this the problem? I've made first press, on release, and while held down, all refer to the same event in an attempt to get it to repeat quickly and the best I get is two events (one for push and one for release I guess).

Sometimes I don't see the green/yellow light flickering in the bottom right of Girder which means I'm using a button that I guess isn't allowing for repeating so I switch and try a different remote button. Sometimes I see the light flickering like crazy but I still only get two events. Does that mean that my remote is sending different codes for the "held" position -- is there anyway I can debug that to be sure? I't would be cool if Girder had a brief input log so one could see the times and codes input to Girder.

I've tried tinkering with anti-repeat times and the buttonmode settings to get it to work, no dice-- can anyone tell me how they achieve this and ways to debug this?

cntr_ice_junkie
October 13th, 2002, 12:55 PM
Francois,

Good recommendation -- thank you very much as I didn't know about that plugin. I'll try it out and will hopefully be able to verify that I am injecting the remote codes that I expect. I'm pretty sure I'm alright there but I'll report back after I try this tonight.

Thanks again.

cntr_ice_junkie
October 13th, 2002, 12:55 PM
Well, that plugin in really helped, I can now clearly see that all of the buttons I was trying to get to repeat send one valid IR code and then repeat some other and different code, usually 010000000000 or 020000000000. I have a IR receiver hooked up to the COM port (it's actually the one that comes with the MyHD HDTV PCI card). It's seemed to do all of the tricks I've asked it to do so far. In addition I'm using a Sony RM-AV3000 as my learning/universal remote. I have also tried over 5 original remotes and they seem to do similiar things.

Is this common with remotes? Do people have ways of making Girder handle this? I can come up with a few but they seem pretty complicated since the repeat code is always the same. Is it possible it's something with my IR receiver? Anyone seen this before?

I read somewhere that COM port speed settings sometimes help and I've been tinkering with the IR plugin settings in Girder with no luck.

TIA

cntr_ice_junkie
October 13th, 2002, 12:55 PM
Shay,

Thanks a bunch, I got it working pretty much as you described. I didn't know what Alarmtimer was but figured it was a plugin and got a little confused when I couldn't dowload it, took a second to realize it was included. I should really check out what more of what the default plugins can do.

The only problem I had was I was getting the button repeated too much when trying to do a single press. So on the first event I start two timers, the first enables the repeat group in 300ms, the second disables it in 400ms. Then the repeat group adds (or I guess really resets) the second timer to 150ms after receiving each repeat button press. Seems to work like a champ, thanks again. And to repeat, thanks again
:P hardy har har....

Mandark
October 14th, 2002, 01:44 AM
Somehow, I'm missing something about being able to repeat events from a remote.

I've got Girder 3.2.4 and I've tried messing with buttonmode 1.22 and I think 1.3. Neither have the "repeat" option for "on first press" in the buttonmode plugin settings which I saw mentioned in some other threads -- is this the problem

hi there!
the "repeat" option for "on first press" is only available in buttonmode 1.2.2. you can get it here:
http://www.prism.gatech.edu/~gtg385b/other%20shit/ButtonMode122.zip
unfortunately it is only for girder 3.1. the buttonmode available for girder 3.2 is version 1.3, which doesn't have the feature (despite the higher version number). my guess is, that 1.3 is a conversion of 1.2, which didnt have the feature either.
somebody has to convert buttonmode 1.2.2 to girder 3.2 to get this useful feature for girder 3.2. unfortunately my programming skills are close to zero. :oops:
-mandark