Reply to thread

Message

<blockquote data-quote="and-81" data-source="post: 197352" data-attributes="member: 11844">Pastill:I'm doing some investigations here.&nbsp; I have a Pronto that I am able to verify results with to.&nbsp; We'll get this sorted out for you I.IR Commands will always change slightly when you learn/transmit/re-learn them because at each step of the way there is a Digital to Analog / Analog to Digital conversion taking place.&nbsp; But the amount of difference you're seeing is too much...It is true that the IR transmitter buds that come with the MCE device are very weak.&nbsp; They have a very short range, and unless they are positioned ~100% accurately they will not&nbsp; function correctly.&nbsp; I can't say for sure why Microsoft and it's OEM partners decided to do this, but my best guess is that they didn't want transmitted signals feeding back into the receiver or influencing devices other than the intended receiver.&nbsp; Whatever the reason, it is deliberately a weak transmitter, there is no doubt about that.The little IR transmitter bugs need to placed directly onto the IR receiver of the device they are controlling, that's what the adhesive patch on the bud is for.Microsoft's page on setting up the IR buds shows how they need to be placed:<a href="http://www.microsoft.com/windowsxp/mediacenter/using/setup/settop.mspx" target="_blank">http://www.microsoft.com/windowsxp/mediacenter/using/setup/settop.mspx</a>I've made a number of small changes to the way the IR learning and blasting work now and will make it available in a new test copy of the IR Server Suite that I will release within the next few days.&nbsp; Before I release it I will try to ensure it is more accurate in it's IR blasting.&nbsp; In fact, if you send me a Private Message with your email address (preferably not a GMail address because Hotmail won't pass on the 2mb attachment to GMail, go figure) then I will send you a copy immediately and we can get this sorted out before I pass it on to the rest of the community.Cheers,</blockquote>

[QUOTE="and-81, post: 197352, member: 11844"] Pastill: I'm doing some investigations here. I have a Pronto that I am able to verify results with to. We'll get this sorted out for you I. IR Commands will always change slightly when you learn/transmit/re-learn them because at each step of the way there is a Digital to Analog / Analog to Digital conversion taking place. But the amount of difference you're seeing is too much... It is true that the IR transmitter buds that come with the MCE device are very weak. They have a very short range, and unless they are positioned ~100% accurately they will not function correctly. I can't say for sure why Microsoft and it's OEM partners decided to do this, but my best guess is that they didn't want transmitted signals feeding back into the receiver or influencing devices other than the intended receiver. Whatever the reason, it is deliberately a weak transmitter, there is no doubt about that. The little IR transmitter bugs need to placed directly onto the IR receiver of the device they are controlling, that's what the adhesive patch on the bud is for. Microsoft's page on setting up the IR buds shows how they need to be placed: [url]http://www.microsoft.com/windowsxp/mediacenter/using/setup/settop.mspx[/url] I've made a number of small changes to the way the IR learning and blasting work now and will make it available in a new test copy of the IR Server Suite that I will release within the next few days. Before I release it I will try to ensure it is more accurate in it's IR blasting. In fact, if you send me a Private Message with your email address (preferably not a GMail address because Hotmail won't pass on the 2mb attachment to GMail, go figure) then I will send you a copy immediately and we can get this sorted out before I pass it on to the rest of the community. Cheers, [/QUOTE]

Verification