Posted: Mon Sep 03, 2007 4:10 pm
Andrew,
Without realizing it, I gave you an excellent example of why I recommend staying away from IR until JP1xTEST says the interface is working. I said maybe you should try a manufacturer's reset. That was a stupid suggestion, and has nothing to do with your problem. A manufacturer's reset restores a section of memory that has become corrupted and is causing malfunction of a remote. By contrast, the JP1xTEST program just checks to see if the remote can grunt out a primitive acknowledgement to a serial communication interogation. That's the beauty of it. It doesn't care if the remote has become stuffed with nonsense. It just sends it a single character and wants a simple "yes" or No" answer. This may sound like I'm splitting hairs, but there's a big difference between performance and communication. Fortunately, the portion of memory dedicated to serial communications is not in the area that sometimes needs a manufacturer's reset. So stick with JP1xTEST until it gives you an OK.
Tommy
Without realizing it, I gave you an excellent example of why I recommend staying away from IR until JP1xTEST says the interface is working. I said maybe you should try a manufacturer's reset. That was a stupid suggestion, and has nothing to do with your problem. A manufacturer's reset restores a section of memory that has become corrupted and is causing malfunction of a remote. By contrast, the JP1xTEST program just checks to see if the remote can grunt out a primitive acknowledgement to a serial communication interogation. That's the beauty of it. It doesn't care if the remote has become stuffed with nonsense. It just sends it a single character and wants a simple "yes" or No" answer. This may sound like I'm splitting hairs, but there's a big difference between performance and communication. Fortunately, the portion of memory dedicated to serial communications is not in the area that sometimes needs a manufacturer's reset. So stick with JP1xTEST until it gives you an OK.
Tommy