AIRWidget and IRScope Operating Instructions - Revision history

The Robman at 00:15, 23 November 2025

2025-11-23T00:15:44Z

← Older revision		Revision as of 00:15, 23 November 2025
Line 6:		Line 6:
	=APPLICATION SOFTWARE=		=APPLICATION SOFTWARE=
	A software bundle for '''IRScope''' ('''IRScope v3.05''') can be downloaded at		A software bundle for '''IRScope''' ('''IRScope v3.05''') can be downloaded at
	[~~http~~://www.hifi-remote.com/forums/dload.php?action=file&file_id=26615 IRScope] , from which you can extract these files:		[https://www.hifi-remote.com/forums/dload.php?action=file&file_id=26615 IRScope] , from which you can extract these files:

	# DecodeIR.dll ............................. Application extension		# DecodeIR.dll ............................. Application extension
Line 262:		Line 262:
	(1) '''Arduino IDE 1.8.13 or 1.8.19'''. This is a sort of “do it all” software tool that can be used to create, edit, debug, compile, and upload sketches to an Arduino product, such as the '''Nano'''. We use it only to upload the sketch. It is possible you already have it installed in your PC. If so, skip to paragraph (2). If not, search for it online and follow the instructions given for downloading and installing it.		(1) '''Arduino IDE 1.8.13 or 1.8.19'''. This is a sort of “do it all” software tool that can be used to create, edit, debug, compile, and upload sketches to an Arduino product, such as the '''Nano'''. We use it only to upload the sketch. It is possible you already have it installed in your PC. If so, skip to paragraph (2). If not, search for it online and follow the instructions given for downloading and installing it.

	(2) '''AIRWidget v1.00'''. This is the sketch you must upload into the Nano using the IDE. With the IDE installed, go [~~http~~://www.hifi-remote.com/forums/dload.php?action=file&file_id=26621 HERE] to get started. Download the '''AIRWidget''' sketch and use '''IDE''' to upload it to the '''Nano'''. Click on Tools to drop down a menu box, and make sure the following selections are listed.		(2) '''AIRWidget v1.00'''. This is the sketch you must upload into the Nano using the IDE. With the IDE installed, go [https://www.hifi-remote.com/forums/dload.php?action=file&file_id=26621 HERE] to get started. Download the '''AIRWidget''' sketch and use '''IDE''' to upload it to the '''Nano'''. Click on Tools to drop down a menu box, and make sure the following selections are listed.

	[[File:AWFig14b.PNG\|frame\|50px\|center]]		[[File:AWFig14b.PNG\|frame\|50px\|center]]

	(3) '''IRScope v3.05'''. This is the program you must install in your PC.		(3) '''IRScope v3.05'''. This is the program you must install in your PC.
	::Go [~~http~~://www.hifi-remote.com/forums/dload.php?action=file&file_id=26615 HERE]		::Go [https://www.hifi-remote.com/forums/dload.php?action=file&file_id=26615 HERE]
	::Click on the '''Download''' button.		::Click on the '''Download''' button.
	::Click on the '''Extract''' all button.		::Click on the '''Extract''' all button.

The Robman: 29 revisions imported

2025-11-02T18:52:56Z

29 revisions imported

← Older revision	Revision as of 18:52, 2 November 2025
(No difference)

Mdavej: /* BUILDING AN AIRWIDGET */

2023-03-10T19:24:53Z

BUILDING AN AIRWIDGET

← Older revision		Revision as of 19:24, 10 March 2023
Line 252:		Line 252:

	A smaller '''AIRWidget''' can be built using a Mini Solderless Breadboard (Figure 14). These are sold as single units or in packs of five to eight units by Sparkfun, Adafruit, Pololu, Amazon, eBay, and other internet sources.		A smaller '''AIRWidget''' can be built using a Mini Solderless Breadboard (Figure 14). These are sold as single units or in packs of five to eight units by Sparkfun, Adafruit, Pololu, Amazon, eBay, and other internet sources.

	[[File:AWFig14.jpg\|~~frame~~\|upright=.5\|center\|\|Figure 14. AIRWidget Built on Mini Solderless Breadboard]]		[[File:AWFig14.jpg\|thumb\|upright=7\|center\| Figure 14. AIRWidget Built on Mini Solderless Breadboard]]

	Note that two of the wire jumpers are located beneath the Nano. If you want to put the '''AIRWidget''' in a box you will find several sources of small plastic boxes on the internet, usually sold in small bunches. You will have to use one that has inside dimensions of at least 1.5 " x 1.9" x .75" height. Most mini's have hooks on two sides for linking multiple units together. You can reduce the overall length and width another 0.1" if you have trouble fitting it within a box by cutting these off or filing them down.		Note that two of the wire jumpers are located beneath the Nano. If you want to put the '''AIRWidget''' in a box you will find several sources of small plastic boxes on the internet, usually sold in small bunches. You will have to use one that has inside dimensions of at least 1.5 " x 1.9" x .75" height. Most mini's have hooks on two sides for linking multiple units together. You can reduce the overall length and width another 0.1" if you have trouble fitting it within a box by cutting these off or filing them down.

Mdavej: /* BUILDING AN AIRWIDGET */

2023-03-10T19:13:01Z

BUILDING AN AIRWIDGET

← Older revision		Revision as of 19:13, 10 March 2023
Line 253:		Line 253:
	A smaller '''AIRWidget''' can be built using a Mini Solderless Breadboard (Figure 14). These are sold as single units or in packs of five to eight units by Sparkfun, Adafruit, Pololu, Amazon, eBay, and other internet sources.		A smaller '''AIRWidget''' can be built using a Mini Solderless Breadboard (Figure 14). These are sold as single units or in packs of five to eight units by Sparkfun, Adafruit, Pololu, Amazon, eBay, and other internet sources.

	[[File:AWFig14.jpg\|frame\|~~50px~~\|center\|\|Figure 14. AIRWidget Built on Mini Solderless Breadboard]]		[[File:AWFig14.jpg\|frame\|upright=.5\|center\|\|Figure 14. AIRWidget Built on Mini Solderless Breadboard]]

	Note that two of the wire jumpers are located beneath the Nano. If you want to put the '''AIRWidget''' in a box you will find several sources of small plastic boxes on the internet, usually sold in small bunches. You will have to use one that has inside dimensions of at least 1.5 " x 1.9" x .75" height. Most mini's have hooks on two sides for linking multiple units together. You can reduce the overall length and width another 0.1" if you have trouble fitting it within a box by cutting these off or filing them down.		Note that two of the wire jumpers are located beneath the Nano. If you want to put the '''AIRWidget''' in a box you will find several sources of small plastic boxes on the internet, usually sold in small bunches. You will have to use one that has inside dimensions of at least 1.5 " x 1.9" x .75" height. Most mini's have hooks on two sides for linking multiple units together. You can reduce the overall length and width another 0.1" if you have trouble fitting it within a box by cutting these off or filing them down.

Mdavej at 16:38, 8 March 2023

2023-03-08T16:38:50Z

Show changes

Mdavej at 16:23, 8 March 2023

2023-03-08T16:23:58Z

Mdavej at 16:18, 8 March 2023

2023-03-08T16:18:29Z

Show changes

Mdavej: /* THE MAIN WINDOW */

2023-03-08T16:14:00Z

THE MAIN WINDOW

← Older revision		Revision as of 16:14, 8 March 2023
Line 24:		Line 24:
	=THE MAIN WINDOW=		=THE MAIN WINDOW=
	After plugging in your '''AIRWidget''' and opening '''IRScope''' the operating window will		After plugging in your '''AIRWidget''' and opening '''IRScope''' the operating window will
	look something like Figure 2 below. It contains all of the AIRWidget controls, and will remain on your screen as long as your recording session is active. The large blank area in the center is the decode area. It will list all the signals you capture, and also those you retrieve from previously saved records.		look something like Figure 2 below. It contains all of the '''AIRWidget''' controls, and will remain on your screen as long as your recording session is active. The large blank area in the center is the decode area. It will list all the signals you capture, and also those you retrieve from previously saved records.
	[[File:AWFig2.jpg\|frame\|50px\|center\|Figure 2. Default Main Window]]		[[File:AWFig2.jpg\|frame\|50px\|center\|Figure 2. Default Main Window]]

Mdavej: /* THE MAIN WINDOW */

2023-03-07T21:02:51Z

THE MAIN WINDOW

← Older revision		Revision as of 21:02, 7 March 2023
Line 53:		Line 53:
	:For saving, exporting, or deleting a recording, moving it up or down in the list, adding notes, etc., select (highlight) the target decode entry by single-clicking anywhere on it. Deselect that one by selecting another one. Or deselect all of them by clicking in a blank area.		:For saving, exporting, or deleting a recording, moving it up or down in the list, adding notes, etc., select (highlight) the target decode entry by single-clicking anywhere on it. Deselect that one by selecting another one. Or deselect all of them by clicking in a blank area.

	:<u>'''Start, End, and Error'''</u> This data is used mainly by Forum experts when debugging decoding problems, and so is not of much use to the typical user. You might prefer to make better use of screen space and keep the display simple by sliding those three columns beyond the right edge of the main window, out of sight. Some of the illustrations in these instructions may appear that way.		:<u>'''Start, End, and Error'''</u> .... This data is used mainly by Forum experts when debugging decoding problems, and so is not of much use to the typical user. You might prefer to make better use of screen space and keep the display simple by sliding those three columns beyond the right edge of the main window, out of sight. Some of the illustrations in these instructions may appear that way.

	:<u>'''Add/Edit Note'''</u> .... Used to open a Decode Note Editor box for adding or modifying a comment in the Note column for a signal you have selected (highlighted) in the decode panel. Very handy for keeping track of signal source identity, such as brand and model of device controlled, remote used, button pressed, etc.		:<u>'''Add/Edit Note'''</u> .... Used to open a Decode Note Editor box for adding or modifying a comment in the Note column for a signal you have selected (highlighted) in the decode panel. Very handy for keeping track of signal source identity, such as brand and model of device controlled, remote used, button pressed, etc.
Line 80:		Line 80:
	:<u>'''Show waveform'''</u> .... Checked by default, provides a Waveform Display of each new captured signal.		:<u>'''Show waveform'''</u> .... Checked by default, provides a Waveform Display of each new captured signal.

	:<u>'''Menu Bar'''</u> Right below the title bar of the main window is a menu bar with five drop-down menus, File, Edit, Export, Advanced, and Help. There are so many sophisticated features within these menus that rather than try to explain them all here I suggest you experiment with them to explore your needs and preferences.		:<u>'''Menu Bar'''</u> .... Right below the title bar of the main window is a menu bar with five drop-down menus, File, Edit, Export, Advanced, and Help. There are so many sophisticated features within these menus that rather than try to explain them all here I suggest you experiment with them to explore your needs and preferences.

	=THE WAVEFORM DISPLAY=		=THE WAVEFORM DISPLAY=

Mdavej: /* THE MAIN WINDOW */

2023-03-07T21:01:22Z

THE MAIN WINDOW

← Older revision		Revision as of 16:23, 8 March 2023
Line 98:		Line 98:
	[[File:AWFig6.jpg\|frame\|50px\|center]]		[[File:AWFig6.jpg\|frame\|50px\|center]]
	<div style="text-align: center;">		<div style="text-align: center;">
	'''Fixed Resolution''' shows captured data at a resolution of 400µs per pixel:		'''Fixed Resolution''' shows captured data at a resolution of '''400µs''' per pixel:
	[[File:AWWv1.jpg\|frame\|50px\|center]]		[[File:AWWv1.jpg\|frame\|50px\|center]]

Line 112:		Line 112:
	[[File:AWWv4.jpg\|frame\|50px\|center]]		[[File:AWWv4.jpg\|frame\|50px\|center]]

	The waveform display in Figure 4 depicts the demodulated carrier, drawn to a precise scale of 20µs per pixel. Waveform timing starts on the second line at time 0 (the moment the remote began transmitting), and increases from left to right across successive rows as you move down the screen. Numbers down the left side (11860, 23720, 35580, 47440, etc.) show the time in µs at that point in the waveform. Raised portions of the waveform are periods when the carrier is turned ON, and lower (baseline) portions are periods when it is turned OFF. Numbers beneath the baseline (2400, 600, 1200, 600, etc.) are carrier ON and OFF times in µs, and numbers above the baseline within the raised portions (96, 48, 24, 48, etc.) are the number of carrier cycles (infrared pulses) that were counted by the '''AIRWidget''' during those ON bursts.		The waveform display in Figure 4 depicts the demodulated carrier, drawn to a precise scale of '''20µs''' per pixel. Waveform timing starts on the second line at time 0 (the moment the remote began transmitting), and increases from left to right across successive rows as you move down the screen. Numbers down the left side (11860, 23720, 35580, 47440, etc.) show the time in µs at that point in the waveform. Raised portions of the waveform are periods when the carrier is turned ON, and lower (baseline) portions are periods when it is turned OFF. Numbers beneath the baseline (2400, 600, 1200, 600, etc.) are carrier ON and OFF times in µs, and numbers above the baseline within the raised portions (96, 48, 24, 48, etc.) are the number of carrier cycles (infrared pulses) that were counted by the '''AIRWidget''' during those ON bursts.

	Each time you capture a record a new waveform is displayed, always in the upper left area of the screen at default size, stacked on top of those previously recorded, and a new decode line is added in numerical order in the decode area of the window. If the recording is of a macro it will be shown as a single waveform display with the actual time of separation between commands. But each command of a macro will be listed separately in the main window with its own individual carrier frequency, protocol identity, and decoding, as if they were recorded separately.		Each time you capture a record a new waveform is displayed, always in the upper left area of the screen at default size, stacked on top of those previously recorded, and a new decode line is added in numerical order in the decode area of the window. If the recording is of a macro it will be shown as a single waveform display with the actual time of separation between commands. But each command of a macro will be listed separately in the main window with its own individual carrier frequency, protocol identity, and decoding, as if they were recorded separately.
Line 148:		Line 148:
	[[File:AWWv6.jpg\|frame\|50px\|center]]		[[File:AWWv6.jpg\|frame\|50px\|center]]

	You'll notice that the amount of time shown in each horizontal line increased from ~~11860µs~~ to 23180µs, enough to show a complete frame on one line. But resolution remains unchanged from the default value of 20µs per pixel.		You'll notice that the amount of time shown in each horizontal line increased from '''11860µ'''s to '''23180µs''', enough to show a complete frame on one line. But resolution remains unchanged from the default value of '''20µs''' per pixel.

	Clicking anywhere on a waveform display pops up the '''IRScope''' Config box showing the present resolution.		Clicking anywhere on a waveform display pops up the '''IRScope''' Config box showing the present resolution.
Line 162:		Line 162:
	[[File:AWWv9.jpg\|frame\|50px\|center]]		[[File:AWWv9.jpg\|frame\|50px\|center]]

	Zooming in to a resolution of 15µs or more makes it much easier to read the on and off times.		Zooming in to a resolution of '''15µs''' or more makes it much easier to read the on and off times.
	[[File:AWWv10.jpg\|frame\|50px\|center]]		[[File:AWWv10.jpg\|frame\|50px\|center]]

Line 168:		Line 168:
	[[File:AWWv11.jpg\|frame\|50px\|center]]		[[File:AWWv11.jpg\|frame\|50px\|center]]

	Since there is no carrier, no frequency value is shown at the beginning of the thumbnail, and a "0" is placed in the Frequency column of the decode entry. Let's zoom out to 120µs per pixel so things are not so spread out.		Since there is no carrier, no frequency value is shown at the beginning of the thumbnail, and a "0" is placed in the Frequency column of the decode entry. Let's zoom out to '''120µs''' per pixel so things are not so spread out.
	[[File:AWWv12.jpg\|frame\|50px\|center]]		[[File:AWWv12.jpg\|frame\|50px\|center]]

	Now you can see clearly that one frame of the signal has six single pulses, separated by two different spaces, 11.3ms and 7.~~7ms~~. Let's zoom in as far as we can go (1µs per pixel) to look at a pulse in greater detail.		Now you can see clearly that one frame of the signal has six single pulses, separated by two different spaces, '''11.3ms''' and '''7.7m'''s. Let's zoom in as far as we can go ('''1µs''' per pixel) to look at a pulse in greater detail.
	[[File:AWWv13.jpg\|frame\|50px\|center]]		[[File:AWWv13.jpg\|frame\|50px\|center]]

	The waveform now shows each pulse has a width of exactly 100µs, but that's misleading. Since the Widget only reports the number of pulses it sees every 100µs and doesn't measure them, we can't tell what the actual pulse width is. We know only that it is a single pulse whose width is 100µs or less. (Examining these pulses with an oscilloscope would show them to be actually about 75µs wide.)		The waveform now shows each pulse has a width of exactly '''100µs''', but that's misleading. Since the Widget only reports the number of pulses it sees every '''100µs''' and doesn't measure them, we can't tell what the actual pulse width is. We know only that it is a single pulse whose width is '''100µs''' or less. (Examining these pulses with an oscilloscope would show them to be actually about '''75µs''' wide.)
	=WORKING WITH MACROS=		=WORKING WITH MACROS=
	Capturing a macro is not much different from capturing an individual command. The main thing to remember is to set the Capture Duration to a value greater than the macro duration. Here's an example of a typical macro for which I made an initial test capture with a duration setting of 10,000 ms.		Capturing a macro is not much different from capturing an individual command. The main thing to remember is to set the Capture Duration to a value greater than the macro duration. Here's an example of a typical macro for which I made an initial test capture with a duration setting of '''10,000 ms'''.

	[[File:AWFig7.jpg\|frame\|50px\|center\|Figure 7. 10-Second Capture of Macro Containing Four Commands]]		[[File:AWFig7.jpg\|frame\|50px\|center\|Figure 7. 10-Second Capture of Macro Containing Four Commands]]
Line 207:		Line 207:
	::<u>'''a. Summation Method'''</u> This method is a no-brainer. Just add all the ON and OFF time values below the line from the first point of interest, '''A''', to the second point of interest, '''D'''. The only drawback is there can be a LOT of numbers to add (77 in this case), and avoiding a mistake is tedious work.		::<u>'''a. Summation Method'''</u> This method is a no-brainer. Just add all the ON and OFF time values below the line from the first point of interest, '''A''', to the second point of interest, '''D'''. The only drawback is there can be a LOT of numbers to add (77 in this case), and avoiding a mistake is tedious work.

	::<u>'''b. Ruler Method'''</u> Using an ordinary 12-inch plastic ruler, measure the length of an empty line, such as the one beginning at '''2573620'''. (On my screen it's 7.3 inches long) Then determine the time represented by that line length by subtracting the starting time of one line from the starting time of the next one. For example, '''2632920µs''' - '''2621060µs''' = '''11860µs'''. Now divide 11860µs by 7.3 inches to get 1625µs per inch, which is the scale factor.		::<u>'''b. Ruler Method'''</u> Using an ordinary 12-inch plastic ruler, measure the length of an empty line, such as the one beginning at '''2573620'''. (On my screen it's 7.3 inches long) Then determine the time represented by that line length by subtracting the starting time of one line from the starting time of the next one. For example, '''2632920µs''' - '''2621060µs''' = '''11860µs'''. Now divide '''11860µs''' by '''7.3 inches''' to get '''1625µs''' per inch, which is the scale factor.

	::Note that the entire command is contained on nine full lines plus two partial lines. Measure the distance from A to the end of the first partial line (on my screen it's '''0.9''' inch x '''1625µs''' /inch = '''1463µs''') and from the beginning of the last partial line to D (on my screen it's '''1.3''' inches x '''1625µs''' /inch = '''2113µs'''). So the total length of the command is ['''9''' x '''11860'''] + '''1463''' + '''2113''' = '''110316µs''', or simply '''110ms'''.		::Note that the entire command is contained on nine full lines plus two partial lines. Measure the distance from A to the end of the first partial line (on my screen it's '''0.9''' inch x '''1625µs''' /inch = '''1463µs''') and from the beginning of the last partial line to D (on my screen it's '''1.3''' inches x '''1625µs''' /inch = '''2113µs'''). So the total length of the command is ['''9''' x '''11860'''] + '''1463''' + '''2113''' = '''110316µs''', or simply '''110ms'''.
Line 221:		Line 221:
	[[File:AWFig11.png\|frame\|50px\|center\|Figure 11. Second Point of Interest Aligned Near Start of Line 2658320]]		[[File:AWFig11.png\|frame\|50px\|center\|Figure 11. Second Point of Interest Aligned Near Start of Line 2658320]]

	::In Figure 11 we were able to place the second point of interest fairly close to the start of a line, so we'll say the command ends at about '''2658320µs'''. (NOTE: The point is actually a little beyond the start of the line, about half the width of one of those '''610µs''' OFF times in the line above. If that bothers you, just add '''300µs''' to the ending time, making it 2658620µs. instead of '''2658320µs'''.)		::In Figure 11 we were able to place the second point of interest fairly close to the start of a line, so we'll say the command ends at about '''2658320µs'''. (NOTE: The point is actually a little beyond the start of the line, about half the width of one of those '''610µs''' OFF times in the line above. If that bothers you, just add '''300µs''' to the ending time, making it '''2658620µs'''. instead of '''2658320µs'''.)

	::Subtracting '''2548240µs''' from '''2658320µs''' (or '''2658620µs''') gives 110ms as the length of the command. This method may give an error of as much as 1ms because of the difficulty of placing events precisely at the start of a line, but that amount of error is negligible when working with infrared signals.		::Subtracting '''2548240µs''' from '''2658320µs''' (or '''2658620µs''') gives 110ms as the length of the command. This method may give an error of as much as 1ms because of the difficulty of placing events precisely at the start of a line, but that amount of error is negligible when working with infrared signals.

← Older revision		Revision as of 21:01, 7 March 2023
Line 29:		Line 29:
	The appearance may vary slightly depending on which Windows operating system you are using, as well as some of the configuration changes you may have made during your previous session. The registry has keys that preserve many configuration changes from one session to the next so you can save your preferences. To reset everything to default, run Regedit and delete the IRScope folder at HKEY_CURRENT_USER / Software / UEIC.		The appearance may vary slightly depending on which Windows operating system you are using, as well as some of the configuration changes you may have made during your previous session. The registry has keys that preserve many configuration changes from one session to the next so you can save your preferences. To reset everything to default, run Regedit and delete the IRScope folder at HKEY_CURRENT_USER / Software / UEIC.

	<u>'''Port'''</u> .... This must be set to the virtual COM port your '''AIRWidget''' is connected to. There are two ways to set it, manual and automatic. If you drop down the Advanced tab menu and check the AutoLocate Widget option, then each time you open IRScope the computer will search through all the ports to find the '''AIRWidget''', and automatically select that port. It indicates this by greying out the Port box, as shown in Figure 2, and you can't change it. If you un-check the AutoLocate Widget option, then each time you open IRScope the Port box will be highlighted, letting you know that the port number shown may or may not be correct. If you get a port error message when you try to make a capture, drop down the list of COM ports and manually select the one that Device Manager says you are connected to.		:<u>'''Port'''</u> .... This must be set to the virtual COM port your '''AIRWidget''' is connected to. There are two ways to set it, manual and automatic. If you drop down the Advanced tab menu and check the AutoLocate Widget option, then each time you open IRScope the computer will search through all the ports to find the '''AIRWidget''', and automatically select that port. It indicates this by greying out the Port box, as shown in Figure 2, and you can't change it. If you un-check the AutoLocate Widget option, then each time you open IRScope the Port box will be highlighted, letting you know that the port number shown may or may not be correct. If you get a port error message when you try to make a capture, drop down the list of COM ports and manually select the one that Device Manager says you are connected to.

	<u>'''Capture Duration'''</u> .... Shows the total length of a recording in milliseconds, starting when the '''AIRWidget''' detects the beginning of a signal from your remote. The entry in this box must be a number between 500 and 15000 (1/2 second to 15 seconds). The default value of 700 milliseconds is fine for capturing typical individual buttons, but should be increased to capture a macro containing several commands.		:<u>'''Capture Duration'''</u> .... Shows the total length of a recording in milliseconds, starting when the '''AIRWidget''' detects the beginning of a signal from your remote. The entry in this box must be a number between 500 and 15000 (1/2 second to 15 seconds). The default value of 700 milliseconds is fine for capturing typical individual buttons, but should be increased to capture a macro containing several commands.

	<u>'''Hardware and Mode'''</u> .... <span style="color:red">'''When using the AIRWidget this must be set on Arduino Widget'''.</span>		:<u>'''Hardware and Mode'''</u> .... <span style="color:red">'''When using the AIRWidget this must be set on Arduino Widget'''.</span>

	<u>'''View button'''</u> .... Used to select a previously saved file for viewing.		:<u>'''View button'''</u> .... Used to select a previously saved file for viewing.

	<u>'''Import button'''</u> .... Used to import Pronto and UEI Learned formats and also Timing Lists of the form displayed by the Times Summary of the Learned Signals tab of IR.exe or by the new Summary facility of this program. The Pronto import can handle both raw and pre-defined Pronto formats other than format 8000. Imported signals are displayed exactly as if they had been captured with the '''AIRWidget'''.		:<u>'''Import button'''</u> .... Used to import Pronto and UEI Learned formats and also Timing Lists of the form displayed by the Times Summary of the Learned Signals tab of IR.exe or by the new Summary facility of this program. The Pronto import can handle both raw and pre-defined Pronto formats other than format 8000. Imported signals are displayed exactly as if they had been captured with the '''AIRWidget'''.

	<u>'''Capture button'''</u> .... Prepares the system to collect data. When you are all set-up and ready to record a signal, place your remote so that its LED emitter is within a few inches of the sensor end of the '''AIRWidget'''. Click on Capture, then press a remote button to transmit a signal. If you wait longer than five seconds before pressing a remote button, the capture will time-out with an error message. Otherwise, captured data will appear at the end of the Capture Duration. The default configuration is for the program to output an audible beep when you click on Capture, and again if it times out in five seconds. If you don't like the beeps, click on Advanced and check the Suppress Beeps option. A flashing white indicator on the '''AIRWidget''' tells you when it detects infrared signals. If the indicator is on constantly, you may be in an area of too high ambient illumination. Avoid bright lights or direct sunlight where you use the '''AIRWidget'''.		:<u>'''Capture button'''</u> .... Prepares the system to collect data. When you are all set-up and ready to record a signal, place your remote so that its LED emitter is within a few inches of the sensor end of the '''AIRWidget'''. Click on Capture, then press a remote button to transmit a signal. If you wait longer than five seconds before pressing a remote button, the capture will time-out with an error message. Otherwise, captured data will appear at the end of the Capture Duration. The default configuration is for the program to output an audible beep when you click on Capture, and again if it times out in five seconds. If you don't like the beeps, click on Advanced and check the Suppress Beeps option. A flashing white indicator on the '''AIRWidget''' tells you when it detects infrared signals. If the indicator is on constantly, you may be in an area of too high ambient illumination. Avoid bright lights or direct sunlight where you use the '''AIRWidget'''.

	<u>'''Decode area'''</u> .... This area shows a list of all the signals you have captured. Most of the column headings are self-explanatory, and the column widths are completely adjustable. If there is a sub-device, its number appears following a decimal point in the Device column. Comments in the Misc column describe repetition characteristics of a signal. No Repeat means the signal consisted of only one full frame. +N copies means the signal consisted of the initial frame followed by N identical copies. +N dittos means the signal consisted of the initial frame followed by N ditto frames. These terms are defined as follows:		:<u>'''Decode area'''</u> .... This area shows a list of all the signals you have captured. Most of the column headings are self-explanatory, and the column widths are completely adjustable. If there is a sub-device, its number appears following a decimal point in the Device column. Comments in the Misc column describe repetition characteristics of a signal. No Repeat means the signal consisted of only one full frame. +N copies means the signal consisted of the initial frame followed by N identical copies. +N dittos means the signal consisted of the initial frame followed by N ditto frames. These terms are defined as follows:

	:A "signal" is a message or command that causes a device to do something. A macro is a collection of two or more signals to the same or different devices.		::A "signal" is a message or command that causes a device to do something. A macro is a collection of two or more signals to the same or different devices.

	:Signals are made up of one or more "frames". Sometimes frames are repeated as long as a button is held down. Many remotes are programmed to repeat frames two or three times for redundancy, even if a button is barely tapped.		::Signals are made up of one or more "frames". Sometimes frames are repeated as long as a button is held down. Many remotes are programmed to repeat frames two or three times for redundancy, even if a button is barely tapped.

	:Full frames often have an initial starting burst (usually distinctively long) and a final OFF time long enough to clearly indicate separation between frames. Within the frame are a series of bursts and spaces that encode address bits, data bits, etc.		::Full frames often have an initial starting burst (usually distinctively long) and a final OFF time long enough to clearly indicate separation between frames. Within the frame are a series of bursts and spaces that encode address bits, data bits, etc.

	:Ditto frames consist of only a starting and ending burst. They are used primarily to indicate that a button is being held down, such as might be done when increasing or decreasing audio volume.		::Ditto frames consist of only a starting and ending burst. They are used primarily to indicate that a button is being held down, such as might be done when increasing or decreasing audio volume.

	For saving, exporting, or deleting a recording, moving it up or down in the list, adding notes, etc., select (highlight) the target decode entry by single-clicking anywhere on it. Deselect that one by selecting another one. Or deselect all of them by clicking in a blank area.		:For saving, exporting, or deleting a recording, moving it up or down in the list, adding notes, etc., select (highlight) the target decode entry by single-clicking anywhere on it. Deselect that one by selecting another one. Or deselect all of them by clicking in a blank area.

	<u>'''Start, End, and Error'''</u> This data is used mainly by Forum experts when debugging decoding problems, and so is not of much use to the typical user. You might prefer to make better use of screen space and keep the display simple by sliding those three columns beyond the right edge of the main window, out of sight. Some of the illustrations in these instructions may appear that way.		:<u>'''Start, End, and Error'''</u> This data is used mainly by Forum experts when debugging decoding problems, and so is not of much use to the typical user. You might prefer to make better use of screen space and keep the display simple by sliding those three columns beyond the right edge of the main window, out of sight. Some of the illustrations in these instructions may appear that way.

	<u>'''Add/Edit Note'''</u> .... Used to open a Decode Note Editor box for adding or modifying a comment in the Note column for a signal you have selected (highlighted) in the decode panel. Very handy for keeping track of signal source identity, such as brand and model of device controlled, remote used, button pressed, etc.		:<u>'''Add/Edit Note'''</u> .... Used to open a Decode Note Editor box for adding or modifying a comment in the Note column for a signal you have selected (highlighted) in the decode panel. Very handy for keeping track of signal source identity, such as brand and model of device controlled, remote used, button pressed, etc.

	<u>'''Save As'''</u> .... Used to save a recording you have selected (highlighted) in the decode area. If you select more than one recording they will be saved as a single file but with each signal clearly separated.		:<u>'''Save As'''</u> .... Used to save a recording you have selected (highlighted) in the decode area. If you select more than one recording they will be saved as a single file but with each signal clearly separated.

	<u>'''Save All As'''</u> .... A faster and easier way to save the entire list of recordings in the decode area as a single file without having to first select them all individually.		:<u>'''Save All As'''</u> .... A faster and easier way to save the entire list of recordings in the decode area as a single file without having to first select them all individually.

	<u>'''Export'''</u> .... Used to export decoded signals. The format depends on the selection in Export Mode under the Export drop-down menu, and can be either Pronto, UEI Learned, or Lintronic (a format used by the Beoworld community). The Pronto export is in the raw Pronto format, but can be generated from either the signal data or from its decode, as required. Exports are appended to a file called ExportedUEI.txt, ExportedPronto.txt or ExportedLintronic.txt, as appropriate, and the file is created if it does not exist. By default these files are created in the folder containing IRScope.exe but this can be changed with the Set Export Output Folder selection in the File drop-down menu.		:<u>'''Export'''</u> .... Used to export decoded signals. The format depends on the selection in Export Mode under the Export drop-down menu, and can be either Pronto, UEI Learned, or Lintronic (a format used by the Beoworld community). The Pronto export is in the raw Pronto format, but can be generated from either the signal data or from its decode, as required. Exports are appended to a file called ExportedUEI.txt, ExportedPronto.txt or ExportedLintronic.txt, as appropriate, and the file is created if it does not exist. By default these files are created in the folder containing IRScope.exe but this can be changed with the Set Export Output Folder selection in the File drop-down menu.

	<u>'''Up, Down, and Delete'''</u> .... Used to change the order of items in the decode area, or delete them entirely. Deleting a decode entry automatically deletes its waveform display.		:<u>'''Up, Down, and Delete'''</u> .... Used to change the order of items in the decode area, or delete them entirely. Deleting a decode entry automatically deletes its waveform display.

	<u>'''Signal structure'''</u> .... Shows additional information about a signal that is selected in the decode area.		:<u>'''Signal structure'''</u> .... Shows additional information about a signal that is selected in the decode area.

	<u>'''IRP Form'''</u> .... Presents a signal in IRP form when it is selected in the Decode Panel. The IRP representation is made independently of the decode operation, so an IRP form can sometimes be determined for signals that cannot be decoded by DecodeIR, and vice versa.		:<u>'''IRP Form'''</u> .... Presents a signal in IRP form when it is selected in the Decode Panel. The IRP representation is made independently of the decode operation, so an IRP form can sometimes be determined for signals that cannot be decoded by DecodeIR, and vice versa.

	<u>'''Summary'''</u> .... Opens a Summary display box like the one shown in Figure 3.		:<u>'''Summary'''</u> .... Opens a Summary display box like the one shown in Figure 3.
	[[File:AWFig3.jpg\|frame\|50px\|center\|Figure 3. Summary Display]]		[[File:AWFig3.jpg\|frame\|50px\|center\|Figure 3. Summary Display]]

	In addition to decoded parameters, the Summary display includes two forms of timing for a signal, the raw timings as used in the waveform display, and analyzed timings in which repeats have been identified and timings averaged over supposedly identical bursts. To see all timing data, either scroll horizontally with the slider at the bottom, or check the Wrap to window box and scroll vertically with the slider at the right edge. The Summary display can be saved in either Rich Text Format (.rtf) or as a plain text file (.txt).		:In addition to decoded parameters, the Summary display includes two forms of timing for a signal, the raw timings as used in the waveform display, and analyzed timings in which repeats have been identified and timings averaged over supposedly identical bursts. To see all timing data, either scroll horizontally with the slider at the bottom, or check the Wrap to window box and scroll vertically with the slider at the right edge. The Summary display can be saved in either Rich Text Format (.rtf) or as a plain text file (.txt).

	Clear .... Clears all entries in the decode area and their corresponding waveform displays. Does not delete any previously saved files.		:<u>'''Clear'''</u> .... Clears all entries in the decode area and their corresponding waveform displays. Does not delete any previously saved files.

	Clear before capture .... Check this box to automatically clear the previous decode data and waveform each time you click on the Capture button to make a new recording.		:<u>'''Clear before capture'''</u> .... Check this box to automatically clear the previous decode data and waveform each time you click on the Capture button to make a new recording.

	Show waveform .... Checked by default, provides a Waveform Display of each new captured signal.		:<u>'''Show waveform'''</u> .... Checked by default, provides a Waveform Display of each new captured signal.

	Menu Bar Right below the title bar of the main window is a menu bar with five drop-down menus, File, Edit, Export, Advanced, and Help. There are so many sophisticated features within these menus that rather than try to explain them all here I suggest you experiment with them to explore your needs and preferences.		:<u>'''Menu Bar'''</u> Right below the title bar of the main window is a menu bar with five drop-down menus, File, Edit, Export, Advanced, and Help. There are so many sophisticated features within these menus that rather than try to explain them all here I suggest you experiment with them to explore your needs and preferences.

	=THE WAVEFORM DISPLAY=		=THE WAVEFORM DISPLAY=