Add support to IOIOLib and IOIO firmware to send infrared codes#25
Open
lanthaler wants to merge 1 commit into
Open
Add support to IOIOLib and IOIO firmware to send infrared codes#25lanthaler wants to merge 1 commit into
lanthaler wants to merge 1 commit into
Conversation
…onto format There's still a small bug in ir.c which required me to hardcode the carrier frequency. As soon as I use the one that's stored in ir_buffer, I get a duty cycle that's not 50% anymore. I couldn't find why the calculated pulse-width changed. The Pronto format is documented, e.g., here: http://www.remotecentral.com/features/irdisp1.htm
ytai
force-pushed
the
master
branch
2 times, most recently
from
cc5f5f2 to
5f0bf44
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request adds the ability to send arbitrary infrared codes that are encoded in the Pronto format
There's still a small bug in ir.c which required me to hardcode the carrier frequency. As soon as I use the one that's stored in ir_buffer, I get a duty cycle that's not 50% anymore. I couldn't find why the calculated pulse-width changed.
This is not the most efficient implementation, but I think a lot of people might be interested in it nevertheless. Things that should be improved:
pulse_widthmicroseconds instead of toggling the IR-LED output in a loopFeel free to fork this PR and improve the things I listed above.