Re: FTDI IR Blaster not working

[Jasper M. <jas...@gm...>]

Bengt:
> The first time it is "normal"; it is essentially inherent in the
> Arduino, that resets when a serial connection is made. The workaround is
> to connect ASAP, and then leave it.
How do I connect to it ASAP ... and then leave it?

Alec:
> If I understand it correctly, you have so far inspected the irsend logs.
Have you checked the lircd logs? Raise the lircd loglevel, restart it and
look for lircd in syslog. There is something rotten here...
The pastebin is from starting lircd as (approximation from memory)
sudo lircd --loglevel=TRACE2 --logfile=/some/file
So fairly certain the info in pastebin is lircd daemon log with the highest
log level
The irsend entry is from syslog.
 What else can I give you?

Cheers

On 27 April 2016 at 22:50, Alec Leamas <lea...@gm...> wrote:

>
>
> On 27/04/16 11:01, Jasper wrote:
>
>> I am using the master branch... switching and rebuilding...
>>   Nope. No difference. Damn... back to master 8)
>> And with today’s updates in master it took more goes to get the
>> fill_string
>> timeout, but this could just be luck.
>>
> So: build/install looks OK (you are loading the correct libs...), changing
> branch -> no difference.
>
>>
>> A note of comparison with homebrew serial: gers takes absolutely ages to
>> send the command, near a second or so, whereas serial is instant.
>>
>> Cheers,
>>
>> Jasper
>>
>
> As I said, the timeout message is from fill_string() in lib/lirc_client.c.
> Seemingly, the socket is opened OK but there is no data from lircd,
> probably after sending the LIRC_SEND command packet.
>
> If I understand it correctly, you have so far inspected the irsend logs.
> Have you checked the lircd logs? Raise the lircd loglevel, restart it and
> look for lircd in syslog. There is something rotten here...
>
>
> Cheers!
>
> --alec
>
>