Newsgroups: comp.robotics
Path: brunix!sgiblab!swrinde!cs.utexas.edu!utnut!torn!newshub.ccs.yorku.ca!newshub.ariel.cs.yorku.ca!cs911225
From: cs911225@ariel.cs.yorku.ca (KEN E WILLMOTT)
Subject: Re: infrared remote protocol
Message-ID: <CnJ40q.LyF@ariel.cs.yorku.ca>
Keywords: infrared ir remote protocol
Sender: news@ariel.cs.yorku.ca
Organization: York University, Dept. of Computer Science
References: <Cn0vFB.Ir2@ariel.cs.yorku.ca> <Cn9Lu7.A87@armory.com> <2n7hd2$4rk@usenet.rpi.edu>
Date: Thu, 31 Mar 1994 12:29:13 GMT
Lines: 19

In article <2n7hd2$4rk@usenet.rpi.edu> reinej@rpi.edu writes:
>The best way to see the "code" that an Infrared Remote Control
>sends is to attatch an IR LED to an oscilliscope and set the triggering
>correctly.  
>			jtr
>

That's one of many ways to do it. I use a hexdump from a test program
running on my HC11. Remember, you have to do more than just "see" it,
you need to use a graticule or something to measure the time values.
Also, if your scope doesn't have memory, the display is a bit hard
to read, as you have to keep pushing the button.

However, the whole thrust of my posting (which is coming along just
fine, having increased from 2 to 5 protocols in size), is how to
interpret the codes, once you have examined them.

	-Ken

