When planning a new project I needed to tackle how to remote trigger a Canon DSLR camera. So I started with looking at the options and landed on using an infrared link to the camera. Things didn’t quite go as I expected.
In Part 1 I described the hardware components and the functionality of the LED clock. This this part, I’ll explore the software required to implement the functionality and seamlessly manage the different user interfaces.
I wanted a create a simple project to test a few ideas and still be useful in its own right. Walking through my local IKEA store, I saw a really inexpensive analog clock (Rusch) and decided that it would provide the right vehicle for what I had in mind.
With all the preparations completed, Umote can finally take shape for this application. The final product can be broken down into four major subsystems that need to be made and integrated in their final form – IR interface hardware, Enclosure, Power Supply, and Switches and Control Wiring.
Having sorted out the concepts of what needed to be implemented, the next step was to write the software that would drive the basic building blocks of the remote control – switches, IR receiver, IR transmitter and LEDs.
Having tested the prototype software with my own domestic remotes, I needed to set up and test the device with the Foxtel remote control. IRLib was not recognising the protocol as one of the ‘standard’ types it has built in, so I needed to do some research. This turned out to be the real learning experience on this project.