KIR Infrared Tx.ino - Revision history

AnalysIR at 18:44, 10 December 2019

2019-12-10T18:44:50Z

← Older revision		Revision as of 11:44, 10 December 2019
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_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_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).		* ''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, instead of 36 bits. This is because MSRC6 36 bit 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).
	* ''KIR_sendNEC'' - here we use the IRremote function sendNEC to send the NEC signal. You could of course just use the IRremote function directly in the code. As most NEC signals are 32 bits, we avoid passing the bit count values with each signal defined and thus save Flash and SRAM elsewhere in the firmware. However, there are many signals used that are variants of NEC and you could customise this ~~funtion~~ for your own variants.		* ''KIR_sendNEC'' - here we use the IRremote function sendNEC to send the NEC signal. You could of course just use the IRremote function directly in the code. As most NEC signals are 32 bits, we avoid passing the bit count values with each signal defined and thus save Flash and SRAM elsewhere in the firmware. However, there are many signals used that are variants of NEC and you could customise this function for your own variants.
	* ''KIR_sendSamsung'' - Here we use the IRremote function to send the ~~samsung~~ signal, but only pass 8 ~~biits~~ instead of 32. This results in savings of Flash and SRAM elsewhere in the firmware where the signals are defined. (8 bits vs 32 bits). This is made ~~possibleby~~ the nature of this particular Samsung device & may need to be adjusted for other Samsung devices.		* ''KIR_sendSamsung'' - Here we use the IRremote function to send the Samsung signal, but only pass 8 bits instead of 32. This results in savings of Flash and SRAM elsewhere in the firmware where the signals are defined. (8 bits vs 32 bits). This is made possible by the nature of this particular Samsung device & may need to be adjusted for other Samsung devices.
	* ''KIR_mark'' - ~~Thsi~~ is an improved mark function, which makes use of KIR_sigTime to ensure there are no extra delays introduced into the signal due to code execution time etc. ''Note the carrier is left ON on exit and needs to be turned off with a space at the end of the signal.''		* ''KIR_mark'' - This is an improved mark function, which makes use of KIR_sigTime to ensure there are no extra delays introduced into the signal due to code execution time or Arduino timer granularity etc. ''Note the carrier is left ON on exit and needs to be turned off with a space at the end of the signal.''
	* ''KIR_space'' - ~~Thsi~~ is an improved space function, which makes use of KIR_sigTime to ensure there are no extra delays introduced into the signal due to code execution time etc.		* ''KIR_space'' - This is an improved space function, which makes use of KIR_sigTime to ensure there are no extra delays introduced into the signal due to code execution time or Arduino timer granularity etc.

AnalysIR at 11:32, 11 November 2019

2019-11-11T11:32:43Z

← Older revision		Revision as of 04:32, 11 November 2019
Line 11:		Line 11:
	* ''KIR_mark'' - Thsi is an improved mark function, which makes use of KIR_sigTime to ensure there are no extra delays introduced into the signal due to code execution time etc. ''Note the carrier is left ON on exit and needs to be turned off with a space at the end of the signal.''		* ''KIR_mark'' - Thsi is an improved mark function, which makes use of KIR_sigTime to ensure there are no extra delays introduced into the signal due to code execution time etc. ''Note the carrier is left ON on exit and needs to be turned off with a space at the end of the signal.''
	* ''KIR_space'' - Thsi is an improved space function, which makes use of KIR_sigTime to ensure there are no extra delays introduced into the signal due to code execution time etc.		* ''KIR_space'' - Thsi is an improved space function, which makes use of KIR_sigTime to ensure there are no extra delays introduced into the signal due to code execution time etc.
	* ''KIR_MacroX'' - Although we are not using macros within this reference firmware, we do show how to define macros(commented out), for use within KontroLIR. Macros will typically involve sending a series of different signals and protocols with defined timing gaps between each signal. You are free to name the macros as you wish, but we suggest sticking to our naming convention or something very similar to identify them as macros.

AnalysIR at 18:00, 9 October 2019

2019-10-09T18:00:17Z

← Older revision		Revision as of 11:00, 9 October 2019
Line 9:		Line 9:
	* ''KIR_sendNEC'' - here we use the IRremote function sendNEC to send the NEC signal. You could of course just use the IRremote function directly in the code. As most NEC signals are 32 bits, we avoid passing the bit count values with each signal defined and thus save Flash and SRAM elsewhere in the firmware. However, there are many signals used that are variants of NEC and you could customise this funtion for your own variants.		* ''KIR_sendNEC'' - here we use the IRremote function sendNEC to send the NEC signal. You could of course just use the IRremote function directly in the code. As most NEC signals are 32 bits, we avoid passing the bit count values with each signal defined and thus save Flash and SRAM elsewhere in the firmware. However, there are many signals used that are variants of NEC and you could customise this funtion for your own variants.
	* ''KIR_sendSamsung'' - Here we use the IRremote function to send the samsung signal, but only pass 8 biits instead of 32. This results in savings of Flash and SRAM elsewhere in the firmware where the signals are defined. (8 bits vs 32 bits). This is made possibleby the nature of this particular Samsung device & may need to be adjusted for other Samsung devices.		* ''KIR_sendSamsung'' - Here we use the IRremote function to send the samsung signal, but only pass 8 biits instead of 32. This results in savings of Flash and SRAM elsewhere in the firmware where the signals are defined. (8 bits vs 32 bits). This is made possibleby the nature of this particular Samsung device & may need to be adjusted for other Samsung devices.
	* ''KIR_mark'' - Thsi is an improved mark function, which makes use of KIR_sigTime to ensure there are no extra delays introduced into the signal due to code execution time etc. Note the carrier is left ON on exit and ~~need~~ to be turned off with a space at the end of the signal.		* ''KIR_mark'' - Thsi is an improved mark function, which makes use of KIR_sigTime to ensure there are no extra delays introduced into the signal due to code execution time etc. ''Note the carrier is left ON on exit and needs to be turned off with a space at the end of the signal.''
	* ''KIR_space'' - Thsi is an improved space function, which makes use of KIR_sigTime to ensure there are no extra delays introduced into the signal due to code execution time etc.		* ''KIR_space'' - Thsi is an improved space function, which makes use of KIR_sigTime to ensure there are no extra delays introduced into the signal due to code execution time etc.
	* ''KIR_MacroX'' - Although we are not using macros within this reference firmware, we do show how to define macros(commented out), for use within KontroLIR. Macros will typically involve sending a series of different signals and protocols with defined timing gaps between each signal. You are free to name the macros as you wish, but we suggest sticking to our naming convention or something very similar to identify them as macros.		* ''KIR_MacroX'' - Although we are not using macros within this reference firmware, we do show how to define macros(commented out), for use within KontroLIR. Macros will typically involve sending a series of different signals and protocols with defined timing gaps between each signal. You are free to name the macros as you wish, but we suggest sticking to our naming convention or something very similar to identify them as macros.

AnalysIR at 17:57, 9 October 2019

2019-10-09T17:57:31Z

← Older revision		Revision as of 10:57, 9 October 2019
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_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_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).		* ''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).
	* ''KIR_sendNEC'' - here we use the IRremote function sendNEC to send the NEC signal. You could of course just use the IRremote function directly in the code. As most NEC signals are 32 bits, we avoid passing the bit count values with each signal defined and thus save Flash and SRAM elsewhere in the firmware. However, there are many signals used that are variants of NEC and you could customise this funtion for your own variants.		* ''KIR_sendNEC'' - here we use the IRremote function sendNEC to send the NEC signal. You could of course just use the IRremote function directly in the code. As most NEC signals are 32 bits, we avoid passing the bit count values with each signal defined and thus save Flash and SRAM elsewhere in the firmware. However, there are many signals used that are variants of NEC and you could customise this funtion for your own variants.
			* ''KIR_sendSamsung'' - Here we use the IRremote function to send the samsung signal, but only pass 8 biits instead of 32. This results in savings of Flash and SRAM elsewhere in the firmware where the signals are defined. (8 bits vs 32 bits). This is made possibleby the nature of this particular Samsung device & may need to be adjusted for other Samsung devices.
			* ''KIR_mark'' - Thsi is an improved mark function, which makes use of KIR_sigTime to ensure there are no extra delays introduced into the signal due to code execution time etc. Note the carrier is left ON on exit and need to be turned off with a space at the end of the signal.
			* ''KIR_space'' - Thsi is an improved space function, which makes use of KIR_sigTime to ensure there are no extra delays introduced into the signal due to code execution time etc.
			* ''KIR_MacroX'' - Although we are not using macros within this reference firmware, we do show how to define macros(commented out), for use within KontroLIR. Macros will typically involve sending a series of different signals and protocols with defined timing gaps between each signal. You are free to name the macros as you wish, but we suggest sticking to our naming convention or something very similar to identify them as macros.

AnalysIR at 17:45, 9 October 2019

2019-10-09T17:45:06Z

← Older revision		Revision as of 10:45, 9 October 2019
Line 7:		Line 7:
	* ''KIR_sendRC6'' - here we extend the IRremote function sendRC6 to manage the toggle bit of the RC6 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).		* 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).
			* ''KIR_sendNEC'' - here we use the IRremote function sendNEC to send the NEC signal. You could of course just use the IRremote function directly in the code. As most NEC signals are 32 bits, we avoid passing the bit count values with each signal defined and thus save Flash and SRAM elsewhere in the firmware. However, there are many signals used that are variants of NEC and you could customise this funtion for your own variants.

AnalysIR at 17:40, 9 October 2019

2019-10-09T17:40:20Z

← Older revision		Revision as of 10:40, 9 October 2019
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_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_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).

AnalysIR: Created page with "'''''> KontroLIR Home > back''''' This file contains functions related to sendin I..."

2019-10-09T17:33:34Z

Created page with "'''''> KontroLIR Home > back''''' This file contains functions related to sendin I..."

New page

'''''> [[KontroLIR - Arduino compatible IR remote control|KontroLIR Home]] > [[Customizing the KontroLIR Firmware|back]]'''''

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

'''''> [[KontroLIR - Arduino compatible IR remote control|KontroLIR Home]] > [[Customizing the KontroLIR Firmware|back]]'''''