We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Custom ESP32-S3 board
Custom Gauge.S board
[ 123][I][esp32-hal-ledc.c:166] ledcAttachChannel(): LEDC attached to pin 10 (channel 0, resolution 8) [ 1791][I][esp32-hal-ledc.c:166] ledcAttachChannel(): LEDC attached to pin 3 (channel 1, resolution 14)
v3.2.0
PlatformIO
W11
80mhz
yes
Default
When setting different resolutions on different channels, second one called disrupts duty resolution calculation and frequency.
Basically I set first one to pin 10 to control backlight LED at 500hz frequency and 8 bit resolution.
Then I use 400Hz PWM output on 14 bit resolution.
After second one is setup the first one goes from very well working to 29 Hz at ~1% duty cycle (measured with scope).
not relevant
Got scope trace but its not very interesting.
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Board
Custom ESP32-S3 board
Device Description
Custom Gauge.S board
Hardware Configuration
Version
v3.2.0
IDE Name
PlatformIO
Operating System
W11
Flash frequency
80mhz
PSRAM enabled
yes
Upload speed
Default
Description
When setting different resolutions on different channels, second one called disrupts duty resolution calculation and frequency.
Basically I set first one to pin 10 to control backlight LED at 500hz frequency and 8 bit resolution.
Then I use 400Hz PWM output on 14 bit resolution.
After second one is setup the first one goes from very well working to 29 Hz at ~1% duty cycle (measured with scope).
Sketch
not relevant
Debug Message
Other Steps to Reproduce
No response
I have checked existing issues, online documentation and the Troubleshooting Guide
The text was updated successfully, but these errors were encountered: