Barf wrote:I tried the GIT Lirc (master branch) and the included IrToy driver for sending. Slammed 100 irsend commands (without delay, with full debugging turned on) to it -- no problems. Not even being root was necessary. (Full debugging (--loglevel=10) is not really resource friendly either...)

Thanks for the heads-up and good to hear it's working for you.

I tried a build from the latest sources, but despite using the same conf file as before it doesn't work. I don't get errors, the toy lights up as normal when trying to send a command, but nothing happens with the device that I'm trying to control.It always worked in the past with the same device and conf file, be it only for 5-6 times of course.

Did you did anything special when building the latest sources or are doing so when running/using lirc in order to make it work with the toy?

First of all, start with --loglevel=10 and either --nodaemon or a logfile, and look for errors. If that does not give a clue, I would use IrScrutinizer (on a PC, Linux or Windows) to capture known good signals for your device. Capture all (or some) the commands, and try to transmit them from the Scrutinizer, all using the 'toy. If that works, generate a lirc configuration file agaiin with the Scrutinizer, and try it with your Lirc setup. If that still does not work, file a bug report at http://sourceforge.net/p/lirc/tickets/ giving as many details as possible.

Judged by the number of issues reported in the forum and the different work-arounds provided (increase process priority, using a USB reset tool, etc.) I personally think it all comes down to either a hardware design flawed or unstable USB firmware. Too bad both don't get any attention any more.

As an experiment to isolate the problem. let me suggest that you try it out with IrScrutinizer (version 1.1.1). It has a completely different driver. You can import your Lirc configuration, and send it through the 'Toy, for example, 100 times in a row.

I had the same errors where connection to usb device fails after number of sent IR signals. I use IrDroid USB stick which is based on irtoy. Nothing worked for me in Raspberry Pi 3. But I finally fixed it, the solution is not trivial and was found here: https://gist.github.com/bullshit/918d74 ... nt-1815751

Basically I took the lircd sources 0.9.4d and updated manually plugins/irtoy.c file, the deal was to increase timeouts: