Reply to thread

Message: <blockquote data-quote="SteveV" data-source="post: 30169" data-attributes="member: 15481">Ok, a couple of things; you may be doing most or all of these but we need to start some place and the begining is as good a place to start as any. First, you'll only see 2 entries per button in the UIRTUSB-tuner.xml file *if* your stb remote transmits toggle format codes such as RC5 or RC6. Toggle code formats like Philips RC5, RC6, and similar, only toggle the code on alternate key presses. The toggle does not occur on repeats when you press and hold the key. In other words; press and release the "1" button and the remote will transmit code "1a". Press and hold the same button and the remote will xmit code "1b" (the toggled version of 1a) for as long as the button is held down. Press the same key a third time and the remote will transmit code "1a". The USBUIRT teaching function asks you to learn each button twice. if both codes match, we make the assumption that we're not using a toggle code format. However, there are a couple of potential problems with this assumption. Let assume you're teaching the "1" button on your remote. Consider what might happen if you successfully teach the first code but inadvertantly tap, rather than hold, the button for the second learn. The USBUIRT would ignore the second code because the ir stream was too short. As such you would need to press and hold the button a third time. Since toggle codes only happen on alternate button presses, you would have taught the same code twice and only one entry would show up for the "1" button in the UIRTUSB-tuner.xml file. When teaching the USBUIRT it important that you your remote is 1-2" away from the USBUIRT *and* that you press AND hold the key you are teaching *until* you receive the confirmation message box that the code was learned properly. Tapping or pressing the buttons rapidly *might* result in the capture of a code but it will very likely not work properly. So, I'd ask that you go through the learn process again for each code, pressing and holding each key until you receive a confirmation message. When you have gone through the entire process examine the UIRTUSB-tuner.xml file to see whether you've learned one or two codes per button. If you're seeing 2 entires for some codes and 1 enrty for others we'll need to determine why that's happening before proceeding further. Once you've gotten all of that sorted out you can begin testing whether it works propely with your stb. If it's still unreliable, the "Inter-command delay ms" value (the amount of time to wait between digits) and/or the "Command repeat count" (the amount of times the same ir code is sent) may need to be increased. Hope this helps, Steve</blockquote>

Verification