-
The type of board you are using.Other - please specify below The boards name or FQBN (e.g. esp8266:esp8266:d1_mini:eesz=4M3M,xtal=80) for unspecified board.Raspberry Pi Pico (RP2040) The board manager URL used for unspecified board.https://github.com/earlephilhower/arduino-pico/releases/download/global/package_rp2040_index.json What IDE are you using?Arduino IDE What IR protocol are you using?Other - please specify below Pin(s) used for IR-receive, if not default.GPIO 19 Example(s) you have checked while hunting the bug.
Example(s) to reproduce the issue.
The library version you are working with.
What are the steps to reproduce this issue?
What happens?The IR LED keeps ON whenever it should be OFF. While using the example may not look that obvious, but if you use a real project with buttons, you can see the IR LED is still on when no buttons is pressed. Funny enough, the code sent by the RP2040 still being valid. For example, if I send 110000111, I'll receive 110000111 (although I'm not sure if this is because of the second repeat or because of some black magic) The serial output which indicates the error happened.N/AWhat were you expecting to happen?The IR LED should be OFF when it's not being in use, and then turn ON/Blink when we send any code. In the case of the built-in example, the LED should be off by a second, then blink rapidly almost like half a second, then off again by a second, and so on. In the case of a hypothetical example of a remote, it should be OFF until we press a button and send a code, where it should blink rapidly until we release the button and the code is sent correctly. Additional context.I'm using a Raspberry Pi Pico (V1 from Raspberry itself, running RP2040 with NO wireless capacity. i.e. the original Pi Pico). For the Framework/Board I'm using Final checklist for the bug report.
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
Thanks for confirming, that the software works well 😀 . |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, but I just tested it using the latest zip from master, and it stills power on the LED when I use PWM (which is enabled by default in RP2040 and I'd want to use). Reading the code from the commit it seems that you just implemented it for the non-PWM method. Am I correct? |
Beta Was this translation helpful? Give feedback.
-
|
I think the problem is in disableSendPWMByTimer, where its content should be: void disableSendPWMByTimer() {
# if defined(USE_RP2040_NATIVE_COMMANDS)
pwm_set_chan_level(sSliceNumberForSendPWM, sChannelNumberForSendPWM, 100); // this sets output also to LOW
# else
# if defined(IR_SEND_PIN)
# if defined(USE_ACTIVE_LOW_OUTPUT_FOR_SEND_PIN)
analogWrite(IR_SEND_PIN, 255); // analogWrite(255) sets pin HIGH
# else
analogWrite(IR_SEND_PIN, 0); // analogWrite(0) disables PWM and sets pin LOW
#endif
# else
# if defined(USE_ACTIVE_LOW_OUTPUT_FOR_SEND_PIN)
analogWrite(IrSender.sendPin, 255); // analogWrite(255) sets pin HIGH
# else
analogWrite(IrSender.sendPin, 0); // analogWrite(0) disables PWM and sets pin LOW
# endif
# endif
# endif
}(I don't use |
Beta Was this translation helpful? Give feedback.
-
|
You were correct! 👍 |
Beta Was this translation helpful? Give feedback.
-
|
Now it's working correctly! Thanks! |
Beta Was this translation helpful? Give feedback.
You were correct! 👍
I just added support also for the "PWM" part 😀 (and tested it with a Nano Connect).
Maybe you want to test it again?