Device Freezes When I Select

When you are navigating around the screen if you hit SELECT and the device appears to quit working it probably means that you did not change the default output pin in IRLibProtocols/IRLibSAMD21.h. The default output pin on IRLib for Feather M0 boards is pin 9 but that pin is used to control the TFT display. If you fail to change this default, it messes up the display. See the configuration section on how to change the default to pin 12 which is how we wired the device.

Cannot Recognize My IR Device

When you are capturing IR codes from your TV, DVR etc. remote there is a chance that the dongle_dump sketch will not recognize it. IRLib supports 11 of the most popular protocols most of which have multiple variants within the protocol that are supported. There is a possibility that your device does not use one of our supported protocols. We will be happy to work with you to try to support your device. Note that IR controlled air conditioners are especially difficult to support and we cannot assist you with that. They use extremely long sequences of pulses that are difficult to decode and store.

Another possibility is that your device uses 57 kHz modulation rather than the typical 38 kHz or variations that range from 36-40 kHz. Even though your TSOP has been built to handle 38 kHz, it should be able to decode anything from 36-40 kHz. But it will not handle 57 kHz. If your device is a cable box or DVR try using the cable codes provided in the sample sketch. My cable box is 57 kHz. It was used by cable boxes built by Scientific-Atlanta, Cisco, Motorola, and Technicolor on cable systems managed by the former company BrightHouse Cable which is now owned by Spectrum Cable. There is only one other 57 kHz protocol that we know of and it is extremely rare. You could purchase a TSOP device capable of reading 57 kHz signals or a TSMP58000 device which is used to detect the frequency of a signal. Details on the use of these alternate devices are available in the IRLib documentation and in the tutorial on the IR transmitter and receiver board.

There are detailed instructions in the IRLib documentation on how to implement your own protocols but that is a very advanced topic. We are committed to working with you to try to support your device. You will need to edit the dongle_dump sketch at the second from the bottom line which says:

myDecoder.dumpResults(false); //Now print results. Use false for less detail

Change the false to true and capture the signal again. The serial monitor will print out a more detailed analysis of your signals. You can email that to me at [email protected] and I will do what I can to assist you.

One other possibility is that your remote does not use infrared signals. Some remotes for example on DirecTV satellite boxes have an option of using either infrared or some sort of RF or Bluetooth wireless system. You can typically reconfigure your satellite box and your remote to use IR signals instead of RF signals. Check out your DirecTV support websites or do a Google search to learn how to convert your remote and your satellite box from RF into IR.

Unfortunately some remote controls do not have an infrared option and we will not be able to control those devices at all. For example if you are using a PlayStation 4 as a media player it does not use infrared.

Other Issues

Make sure that you have downloaded the latest libraries for the and board updates for the Feather M0 BLE and the 2.4" TFT display. Double check your wiring and reread the documentation. If you get really stuck contact me at [email protected] and I will do I can to help.

Final Thoughts

Normally when writing tutorials for the Adafruit Learning System, the projects might be built by hundreds of users and trying to support them individually would be beyond my capabilities. But I understand that this particular device is not going to be used by a lot of people. For those that will use it, it has the potential to have a great impact in their independence and ability to overcome their handicaps. The device has been a lifesaver for me literally. I used the Bluetooth switch control to communicate with doctors and nurses when I could not speak well on a ventilator in the hospital. All of the Fusion 360 design work, all of the programming, and all of the writing of this tutorial including everything the videos was done with the assistance of this Ultimate Remote and dictation software Dragon NaturallySpeaking. That should illustrate how important this device is to people like me. That's why I'm so willing to work with you to customize the device and get the most use of it possible. Even if you do not need any assistance or support, drop me an email at [email protected] and let me know how you use this device. Also drop by the Facebook page for assistance if needed on this or other assistive technology issues. I would love to hear from you.

This guide was first published on Sep 23, 2019. It was last updated on Mar 08, 2024.

This page (Troubleshooting) was last updated on Mar 08, 2024.

Text editor powered by tinymce.