Re: Fwd: Receives only 1 input

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:

# IrScrutinizer parametric export
#
# Creating tool: IrScrutinizer version 1.4.1
# Creating user: bengt
# Creating date: Wed Jul 11 08:34:59 CEST 2018
# Encoding: WINDOWS-1252
#
# Manufacturer:
# Model:
# Displayname:
# Remotename:
#
begin remote
	# Protocol name: NEC2
	name		NET
	bits		32
	flags		SPACE_ENC|CONST_LENGTH
	eps		30
	aeps		100
	zero		564	564
	one		564	1692
	header		9024	4512
	ptrail		564
	gap		108000
	frequency	38400
	begin codes
		KEY_3	0x00000000409FC837
		KEY_4	0x00000000409F28D7
		KEY_5	0x00000000409FA857
		KEY_6	0x00000000409F6897
		KEY_7	0x00000000409FE817
		KEY_8	0x00000000409F18E7
		KEY_9	0x00000000409F9867
		KEY_0	0x00000000409F08F7
		KEY_OK	0x00000000409FF807
		KEY_UP	0x00000000409F00FF
		KEY_DOWN	0x00000000409F807F
		KEY_LEFT	0x00000000409FC03F
		KEY_RIGHT	0x00000000409F40BF
	end codes
end remote

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.

> Second point, now this is the weird part because it lacks some 
> consistency. It took a bit of time messing around but I've managed to 
> get a good test sample, tried to keep it short because usually logs are 
> so big.
> 
>     root@guiu-top /etc/lirc/lircd.conf.d # nano /etc/systemd/journald.conf
>     root@guiu-top /etc/lirc/lircd.conf.d # lircd --loglevel=trace2
>     root@guiu-top /etc/lirc/lircd.conf.d # irw
>     000000000000000b 00 KEY_OK NET
>     0000000000000001 00 KEY_1 NET
>     0000000000000001 00 KEY_1 NET
>     0000000000000001 01 KEY_1 NET
>     0000000000000001 00 KEY_1 NET
>     0000000000000001 01 KEY_1 NET
>     ^C
>     130 root@guiu-top /etc/lirc/lircd.conf.d # killall lircd 

Please do the check above. It may be the repeat model that is wrong.

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