Jeff-ss6qt posted a question about if we can detect the hardware. It turns out that we can! I posted the directions on my Discord server (discord.com/invite/NsjCvqwPAd) pinned in the #infrared channel and also in my GitHub tutorials on GPIO (github.com/jamisonderek/flipper-zero-tutorials/tree/main/gpio/ir_blaster).
If there is a new version released, you can update your Flipper Zero. First, look at the current commit hash (for example, at 4:00 in the video we see origin/release is at d1832d5e). If you then click the refresh circles next to the branch in the lower-left corner of VS Code, it will pull new updates. If the commit hash changes, then you have new updates. You may need to Ctrl+Shift+P, "Git: Stash Changes" before sync and "Git: Apply Stash..." if the files you edited have changed.
The code in the video describe is slightly different than the code in the video, since CZcams descriptions can't have less than signs! I recommend buying one of these from www.tindie.com/stores/tehrabbitt/items/ and adding it to your collection of GPIO devices for the Flipper Zero.
Thanks for sharing, Derek! Do you think it would be easy to add an option in the menu to disable/enable the firmware changes you made to support it? This way it can easily be disconnected to use the built-in IR transmitter when a slimmer profile flipper is desired (without requiring a reflash of the FW, of course).
Hi, yes it's possible (similar to how some of the unofficial firmware does it) but it is a much larger change. Jeff-ss6qt actually had another idea on detecting the device and automatically switching, which should result in a much smaller change. I'll post a pinned comment with more details.
I forgot to mention in the video, after you make the changes, you can switch the branch by clicking bottom left (and choose something like "dev" branch). When you get "Your local changes would be overwritten by checkout." click on "Migrate Changes" and type comment of "IR Blaster". This will end up "stashing" your change, switch branch, and then apply the stashed change. The new branch will have your changes!
Would it ever be possible to switch between the two IR devices dynamically? For example by having a pin detect when the IR blaster is connected. Or maybe manually with a toggle in the Infrared menu?
That's in interesting idea that I never thought of, but we can totally do that! If we configure PA7 in pull-up mode, we will read a "HIGH" when nothing is connected to the Flipper Zero. When we connect the IR Blaster, the resistance of the circuit changes and we will read a "LOW". I'll post a pinned comment with more details, thanks!
I just wanted to take a moment to thank you again for your comment. Because of your comment, Xtreme and RogueMaster now both include settings for automatically detecting an IR Blaster! If someone doesn't add it to official firmware by April, I'll submit a PR. If you are on Official firmware, here is the video I made for auto-detection. czcams.com/video/gRizmfNbIsM/video.html
Jeff-ss6qt posted a question about if we can detect the hardware. It turns out that we can! I posted the directions on my Discord server (discord.com/invite/NsjCvqwPAd) pinned in the #infrared channel and also in my GitHub tutorials on GPIO (github.com/jamisonderek/flipper-zero-tutorials/tree/main/gpio/ir_blaster).
If there is a new version released, you can update your Flipper Zero. First, look at the current commit hash (for example, at 4:00 in the video we see origin/release is at d1832d5e). If you then click the refresh circles next to the branch in the lower-left corner of VS Code, it will pull new updates. If the commit hash changes, then you have new updates. You may need to Ctrl+Shift+P, "Git: Stash Changes" before sync and "Git: Apply Stash..." if the files you edited have changed.
The code in the video describe is slightly different than the code in the video, since CZcams descriptions can't have less than signs!
I recommend buying one of these from www.tindie.com/stores/tehrabbitt/items/ and adding it to your collection of GPIO devices for the Flipper Zero.
Nice
Thanks. This week I added auto-detection for the IR Blaster module. 🎉
Thanks for sharing, Derek! Do you think it would be easy to add an option in the menu to disable/enable the firmware changes you made to support it? This way it can easily be disconnected to use the built-in IR transmitter when a slimmer profile flipper is desired (without requiring a reflash of the FW, of course).
Hi, yes it's possible (similar to how some of the unofficial firmware does it) but it is a much larger change. Jeff-ss6qt actually had another idea on detecting the device and automatically switching, which should result in a much smaller change. I'll post a pinned comment with more details.
I forgot to mention in the video, after you make the changes, you can switch the branch by clicking bottom left (and choose something like "dev" branch). When you get "Your local changes would be overwritten by checkout." click on "Migrate Changes" and type comment of "IR Blaster". This will end up "stashing" your change, switch branch, and then apply the stashed change. The new branch will have your changes!
Would it ever be possible to switch between the two IR devices dynamically? For example by having a pin detect when the IR blaster is connected. Or maybe manually with a toggle in the Infrared menu?
That's in interesting idea that I never thought of, but we can totally do that! If we configure PA7 in pull-up mode, we will read a "HIGH" when nothing is connected to the Flipper Zero. When we connect the IR Blaster, the resistance of the circuit changes and we will read a "LOW". I'll post a pinned comment with more details, thanks!
Awesome, it worked! Thanks again for the suggestion. I wrote up a tutorial at github.com/jamisonderek/flipper-zero-tutorials/tree/main/gpio/ir_blaster
I just wanted to take a moment to thank you again for your comment. Because of your comment, Xtreme and RogueMaster now both include settings for automatically detecting an IR Blaster! If someone doesn't add it to official firmware by April, I'll submit a PR. If you are on Official firmware, here is the video I made for auto-detection. czcams.com/video/gRizmfNbIsM/video.html
If you need help applying these changes, please post your questions on my Discord server - discord.com/invite/NsjCvqwPAd
does this work on traffic lights
I only test on my own equipment. My traffic light can be controlled all kinds of ways, it was upgraded from Netduino to Arduino Uno platform.
But I still need it
Too many scammer out there. I highly recommend buying from official store or meeting someone in person in public location that wants to sell theirs.