Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1181991" data-attributes="member: 82144">The high level specifications are available here:<a href="http://download.microsoft.com/download/0/7/E/07EF37BB-33EA-4454-856A-7D663BC109DF/Windows-Media-Center-RC-IR-Collection-Green-Button-Specification-03-08-2011-V2.pdf" target="_blank">http://download.microsoft.com/download/0/7/E/07EF37BB-33EA-4454-856A-7D663BC109DF/Windows-Media-Center-RC-IR-Collection-Green-Button-Specification-03-08-2011-V2.pdf</a>The supported configurations (eg. how many receivers, transmitters etc.), learn distance, receive distance, receiver carrier frequency range, LED behaviour etc. are all specified.For receiving, each button-press is passed to software as a generic series of times (durations of pulses and spaces), plus the carrier frequency. From this, the software must decide which button was pressed. In other words, the end-user software is responsible for protocol support.For transmitting, the software sets the carrier frequency and provides the series of times (identical to receive format - durations of pulses and spaces).The transceiver and/or it's driver handles waking the PC. For that, only certain protocols (RC-6 and quattro pulse) and commands are supported, but the transceiver has a &quot;boot-loader mode&quot; which enables limited configurability even for that.Personally I think the design is quite well thought out, though the clarity of the specification could be improved.</blockquote>

[QUOTE="mm1352000, post: 1181991, member: 82144"] The high level specifications are available here: [URL]http://download.microsoft.com/download/0/7/E/07EF37BB-33EA-4454-856A-7D663BC109DF/Windows-Media-Center-RC-IR-Collection-Green-Button-Specification-03-08-2011-V2.pdf[/URL] The supported configurations (eg. how many receivers, transmitters etc.), learn distance, receive distance, receiver carrier frequency range, LED behaviour etc. are all specified. For receiving, each button-press is passed to software as a generic series of times (durations of pulses and spaces), plus the carrier frequency. From this, the software must decide which button was pressed. In other words, the end-user software is responsible for protocol support. For transmitting, the software sets the carrier frequency and provides the series of times (identical to receive format - durations of pulses and spaces). The transceiver and/or it's driver handles waking the PC. For that, only certain protocols (RC-6 and quattro pulse) and commands are supported, but the transceiver has a "boot-loader mode" which enables limited configurability even for that. Personally I think the design is quite well thought out, though the clarity of the specification could be improved. [/QUOTE]

Verification