I'm finally getting into using my IRToy to capture/repeat some signals. I've run everything below on both firmwares v22 and v24, and under Windows (10 x64 pro) and Raspbian Linux (4.4.9, armhf). Behavior is exactly the same in both places.
I'm using the pyirtoy Python3 library to capture and repeat infrared signals. This goes perfectly fine provided I don't write out the captured signal to a file. If I repeat the signal from memory, the IRToy will play back the signal just fine.
If I instead run my other python script which just plays the file from a stored file, the IRToy will error out and crash the script.
Can anyone help me debug this? I can't understand what is happening to make it error when reading a file, but it has no problems transmitting a code from memory.
I seem to have noticed a bug in the Play/Record application from the USB IR Toy v22 software package (Windows build, running under Windows 8.1 Pro x64) which does not appear to respect the speed the user sets for the port. The -s flag is supposed to set the baud rate, but the program only ever prints the speed as 115200bps regardless. I don't know if this is just a display issue, or if it simply doesn't respect the speed you set.
An unrelated request would be some help with either compiling the Play/Record application for ARM (Raspberry Pi in specific), or having someone who has it compiled for ARM already give me a copy to use. In my attempt to compile for ARM, I downloaded CodeBlocks and various GNU ARM toolchain binary packages for Windows. I was not successful in getting CodeBlocks to compile for ARM under Windows. I also tried eMIDE (a CodeBlocks-based embedded systems IDE), but it does not (amazingly enough) understand CodeBlocks Project files and I have no idea how to build a project manually.
I'd really like to be able to continue using this app, especially on my Pi.
