In SX Microcontrollers, SX/B Compiler and SX-Key Tool, George Herzog wrote:

More thoughts... Just for starter, the Sony 12bit code is more easily handled than longer codes with more bits. As I said about, this one is very much explored on the internet so Google can locate useful information.  Part of the challenge is that the SX and BasicStamp handle and store data as 8bit words, so capture and processing of longer sequences requires more handling.  Usually there are three tasks in the program - recognize a header, recognize a data stream including key identity and device address being sent to, and recognize end of transmission.  Of course, if the device address is NOT to your SX, it can ignore the rest. In many cases, merely recognizing the header portion with exclude a lot of devices that have longer and shorter headers.

Personally, I strongly suggest buying a Universal Remote for research and testing that is sold as a replacement device. This should be one that you have to configure yourself from a list of 100 or so device rather than a 'smart' device that learns protocol from transmission from another device.  By getting yourself a separate device, you can select a code that is ignored by all your home devices and you can have something to really build a home remote control system on.

Not all BasicStamps are useful as their speed may be too slow for proper capture and handling of IR sequences.  A 50Mhz SX will offer you a lot more opportunitity than a 4Mhz as you can tune the device to be more precise in recognition of code.  That does mean that the receiver will be more 'power thirsty', but that really is a non-issue as it is the transmitter that is battery dependent.  The receiver will often tie into a wall wart and power something else, like a relay board.

---------- End of Message ----------


You can view the post on-line at:
http://forums.parallax.com/forums/default.aspx?f=7&p=1&m=360428#m362817

Need assistance? Send an email to the Forum Administrator at forumadmin@parallax.com

The Parallax Forums are powered by dotNetBB Forums, copyright 2002-2009 (http://www.dotNetBB.com)