Reply to thread

Message: <blockquote data-quote="and-81" data-source="post: 197359" data-attributes="member: 11844">Update:I've got my test rig running with the latest version of the code and here are the results.Using the first pronto code that you supplied:This is the exact code I put into the software.  It translates it into the time code format when it blasts:Here is what the pronto saw when I blasted to it:Compare that directly with the original Pronto code and it is not much different.If you convert that into the time code format for comparison:Now adjust to a 50 microsecond accuracy (this is as precise as the MCE device can get) ...Original:Pronto learned:So if we adjust those numbers above into the actual 50 microsecond quantized coding you'll see that to the MCE IR device they are the same.The only differences are the slight change in the carrier frequency (006C = 38.380 Khz, 006A = 39.105 Khz) and the final silence (-7500 and -2350).The carrier frequency difference shouldn't be a problem.  Unless your TV is extremely sensitive to carrier frequency, which some very old devices seem to be.And the silence at the end of the code is irrelevant because it is a silence, not a pulse.  It is the absence of any signal and seeing as there is no following signal it cannot have an effect.  Basically, the final silence cannot effect the IR receiver so it makes no difference what number you put there.  Silence in between pulses of course is measured by the receiver, but the final silence stretches on to infinity (or until another IR command is sent, whichever comes first).Now, I have been making small changes to this part of the code over the last few days, so it could be that I've fixed whatever the specific problem was for you.  So try the new version and see how you go.  Making sure to re-learn all the IR commands in question.If it still doesn't work then I think it is one of the following problems:1. MCE Device incompatibility.Maybe your MCE device is different to mine.If this is true then things get harder from here.2. Receiver peculiarity.Maybe your TV is very old or has a very picky IR receiver.3. IR bud placement.You don't have the bud placed correctly, with the adhesive paper cover removed.Read the MS guide I linked in the previous post and make sure you have this correct.  If not, fix and repeat.4. IR light interference. You have sunlight, a plasma screen tv, or some other kind of Infrared light source causing interference in either the learning or blasting of the IR command.5. Bad voodoo.Seek witchdoctor for immediate removal of curse.While I wait for a Private Message from you, or until I release a new test version for everyone I will continue to experiment with the IR Carrier Frequency code to see if I can make that more accurate.  It could be that the MCE device is just not accurate enough in it's blasting, or it could be that I have a small arithmetic error in there.If I can't improve the Carrier Frequency handling and you still have problems then we may end up putting it down to the MCE device is just not good enough/accurate enough for your device.  Which is possible.  The MCE device is not perfect and costs a lot less than a Pronto...  But let's not give up just yet.Cheers,</blockquote>

Verification