Re: Fwd: Receives only 1 input

Thanks, I'll try the IrScrutinizer tool, didn't know about, however it
should a be a little harder to setup since I'm running on a semi headless
setup.
But I took some mode2 reading if you want to check them out, I obviously
have no clue what these mean.
First was the sequence of keys OK - Up - Down: https://ptpb.pw/TC7B.txt
Second was the OK key two times: https://ptpb.pw/qiL0.txt
Both taken with brief one second presses.
Thanks, I'll try the scrutinizer as soon as next week.

On Wed, Jul 11, 2018 at 3:54 AM, Bengt Martensson <[email protected]>
wrote:

> On 07/10/18 21:29, Guilherme Furst Bittencourt wrote:
>
>>
>> ...
>> On Sun, Jul 8, 2018 at 6:31 AM, Bengt Martensson
>> Okay, so I'm not really sure what is going. I've tested with mode2 and
>> indeed it reads signals, though I'm not sure if correctly. For one, I was
>> never able to detect proper spacing with irrecord, always having to use raw
>> signals instead, no matter which remote even when it worked years back, I'm
>> not sure if its relevant but I didn't many people complaining about it
>> either.
>>
>
> Please try using IrScrutinizer instead of irrecord. Use /dev/lirc0 as
> capturing device. With that, you can capture your remote.
>
> But actually, I put your file thru IrScrutinizer, deleted the two first
> commands (as they were nonsensical), and exported as a lircd.conf. Got this:
>
> For the repeat problem, first find out exactly what the original remote
> sends. For this "Scrutinize signal" in IrScrutinizer, and shoot e.g. KEY_OK
> for about 1 second. You can also use mode2. Post the result.
>
>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot