-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mini Remote Control: No signal sent is valid? #52
Comments
I tried simplifying, with this code...
And all I get is this kind of output:
I tried with not only the Adafruit Mini Remote as well as the remote of my cable box, as well as the remote for a small video projector. All three appear to have the same experience, with no pulses over 6 in length and a majority just being 1 pulse long. Looking at the code, it is expecting a minimum of 10 pulses. Which does not appear to ever happen with any of these remotes. |
Ok, I had a second CPX that is running CircuitPython 3.x :-) I placed this code in it...
And I get this when pressing up, down, left, right, up, down, left, and right:
This is very consistent. So it appears this works on an ancient version of CircuitPython, but not the current version. It appears, that in the last 2 or 3 years some change has borked the functionality of this library. |
Tried going to CircuitPython 7.0-RC1 but that opened up a whole other problem that I will raise after getting this working in 6.x. |
Thanks for filing an issue for this! I'm going to move it to the core repo since it seems dependent on CP version. |
I tested the last script on CP 7.0.0-rc.1 and it worked correctly - no errors. |
@DavePutz On 7.0.0-rc.1 I am getting a weird blink seqence on the Circuit Playground Express. Yellow flash of all the Neopixels and then two red flashes of all the neopixels, a pause and repeat of the red flashes. |
@eat-sleep-code Those are the new status blinks for 7. The yellow flashes are the wait for safe mode on start up. The double red flashes indicate that the code.py ended due to an exception. The exception backtrace will show on the serial output. |
I am moving this to the 7.x.x milestone since the bug was already present in 6.3.0. |
This is still not resolved as of 7.1.0-beta.3 |
I tried this with 3.x, 4.x, 5.x, and 6.x, and the last The 5.x bundle ... AND, @lstein just fixed this yesterday with #51, which I didn't see until just now. Moving this issue back to the library. |
@eat-sleep-code please try the latest 4.1.3 library version as of a few minutes ago: https://github.com/adafruit/Adafruit_CircuitPython_IRRemote/releases/latest |
Are you still using the Mini Remote Control? I don't have one: I tested it with a similar inexpensive remote control I got in an Arduino clone parts kit years ago. |
I ran the provided test script using : start @eat-sleep-code - is it possible that you have some infrared interference in your environment? |
@tannewt
I am tinkering with parts from an old AdaBox -- a Circuit Playground Express and Mini Remote Control [Product ID: 389].
I installed CircuitPython 6.3.0 on the Circuit Playground Express. I also created a lib folder on the CPE and dropped the adafruit_irremote.mpy from Bundle for Version 6.x in it.
I then placed this code into a code.py file on it:
When I press the UP button (shown here pressed several times), this is the output.
Not once did I appear to receive a valid code.
I am not sure what is incorrect with my code -- for the most part it is pretty close to the example provided on the IR Test with Remote page.
The text was updated successfully, but these errors were encountered: