KIR Infrared Tx.ino: Difference between revisions

Revision as of 09:40, 9 October 2019

This file contains functions related to sendin IR signals either directly or with IRremote or a mix of both.

KIR_sendRAW_Flash - supports sending RAW IR signals from FLASH. Refer to file KIR_RAW_Signals for the storage format and the examples used in Mode5. We also make use of KIR_sigTime to keep track of the elapsed time of each mark/space for improved performance.
KIR_sendRC5 - here we extend the IRremote function sendRC5 to manage the toggle bit of the RC5 signal using toggleFlag.
KIR_sendRC6 - here we extend the IRremote function sendRC6 to manage the toggle bit of the RC6 signal using toggleFlag.
KIR_sendMSRC6 - Here we implement full support for sending Microsoft MCE RC6 signals. This function shows how to implement a full protocol not supported by IRremote and making use of our approach with KIR_sigTime for more accurate/better performance. You may also note that we only pass an 8 bit value to this function. This is because MSRC6 signals can be created from a unique 8 bit value and we build the full 36 bit value from that 8 bits within the function. This results in Flash and SRAM savings elsewhere in the firmware (using 8 bits instead of 36+ bits per defined signal).

@@ Line 6: / Line 6: @@
 * ''KIR_sendRC5'' - here we extend the IRremote function sendRC5 to manage the toggle bit of the RC5 signal using toggleFlag.
 * ''KIR_sendRC6'' - here we extend the IRremote function sendRC6 to manage the toggle bit of the RC6 signal using toggleFlag.
-* KIR_sendMSRC6 - Here  we implement full support for sending Microsoft MCE RC6 signals. This function shows how to implement a full protocol not supported by
+* KIR_sendMSRC6 - Here  we implement full support for sending Microsoft MCE RC6 signals. This function shows how to implement a full protocol not supported by IRremote and making use of our approach with KIR_sigTime for more accurate/better performance. You may also note that we only pass an 8 bit value to this function. This is because MSRC6 signals can be created from a unique 8 bit value and we build the full 36 bit value from that 8 bits within the function. This results in Flash and SRAM savings elsewhere in the firmware (using 8 bits instead of 36+ bits per defined signal).