The gibberish may have been due to a bad .bin file... I seem to have re-done them and they all seem to work now... The remote was a DISHnetwork remote that seemed to "studder" the first time you pushed a button.. so in other words, when i would go and press "1" on the remote it would end up making sat_000, sat_001 and sometimes even sat_002. But i did it again and got the full string from sat_003 and played that one back and it worked.. however, 000 did not and caused the gibberish there-after.
I've also bumped the 256 to 1024 as some of the IR commands are pretty long. I think the largest one i could see was in the 700-range so i made it 1024 just in case :o)
Ok i did some tests and this is what i came up with:
-If i blast with the same .bin files (sat_000.bin, sat_000.bin, etc...) it never gives the gibberish errors.
-if i blast with different .bin files (sat_000.bin, sat_003.bin, etc...) then it DOES give me gibberish after the 3rd .bin blast. So in other words, the 4th .bin blast is where it does the gibberish. And that is constant no matter what _0xx number order i use in the .bat file)
[quote author="jamz"]I run the files and and it works fine with the latest rec and play app v.082, using firmware V112. If the problem don't disappear it could be something else.
[quote author="ian"]THanks for the update. Could you please upload the group of files and .bat from the video that cause the issue if it continues. I really want to reproduce the error so I can see what the IR TRoy is doing with a debugger running.[/quote]
I'm still stumped by #1, I've never encountered this before. I can only guess there is a setting in your serial port that isn't right until you open teraterm. Have you tried the IR Toy with WinLIRC? It might setup the port in a different way.
#2 I think we have a handle on now. There was extra data send back to the app after transmitting in the most recent firmware. You can find a test firmware at the above link that doesn't have this, it might fix this issue.
Do you have any .bin files you try to transmit that give you problems every time? I'll try to debug with those too.[/quote]
I know its odd but as the videos show, if i start out doing the irtoy.exe and try to execute a bin file, it just stays on the 115xxx and thats it. Only when i do the teraterm program and hit the "v" then close it out does the irtoy.exe work.
If the new firmware works to solve the gibberish after so many IR blasts then awesome. Ive already wrote a script to do the teraterm the first time my program runs so thats not really a big deal but it would be nice not to have to do that first in order to use the ir toy.
As for the WinLIRC, i could never get it working (although i don't recall doing the teraterm for that program first then trying WinLIRC) may be the same issue... Even so, i would have to re-transmit all the remotes i recored in the IRToy program to WinLIRC-code, correct? That program wont use a .bin file as far as i know...
As for any .bin files... well they seem to all work if i do one then unplug the IRtoy then plug it back in and do another.. They all blast just fine... just not when i try to blast more than 5 or so.
It seems that i am still having a problem. Heres what it does:
1) when i call a command like this (irtoy.exe -d COM10 -f sat_000.bin -p -a 0 -b 256) it goes just fine. I ALWAYS have to run teraterm before i can ever use the IRToy. After doing a "V" in teraterm, i close it and i can send out another command.
2) After awhile if its not used then using it results in it not being able to find it again and gibberish characters again OR a few commands being called with a pause in between each one (-v) and about the 5th one it gets crazy and does the gibberish. (see last video for this example)
I will do my best to capture this so you can better understand it. I just dont understand whats going on with it and why i (1) have to use teraterm to "enable" it to work and (2) why its messing up after a period of not being used and/ or between IR blasts.