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

Implement changing PWM frequency #13

Closed
tdicola opened this Issue Oct 14, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@tdicola

tdicola commented Oct 14, 2016

Right now the PWM objects just let you change duty cycle with the duty function (0-255, 8 bit values). However it would be handy to also support changing the frequency with the freq function which takes in a frequency in hertz for the PWM signal to use. This is similar to the behavior in the ESP8266 port (IIRC there is a limitation that the frequency is global across all PWM output, so it's not the end of the world if we need a similar limitation vs. trying to have a mess of timers for each PWM output).

@tannewt tannewt added the enhancement label Oct 17, 2016

@tannewt tannewt modified the milestone: Beta Nov 30, 2016

@tannewt tannewt modified the milestones: 1.0, Beta Dec 7, 2016

@tannewt

This comment has been minimized.

Show comment
Hide comment
@tannewt

tannewt Feb 1, 2017

Collaborator

Fixed in e3f9ee8. You can now set a fixed frequency in the constructor which on SAMD will allow multiple PWMOuts to share the same timer or set variable_frequency to claim a whole timer and be able to change the frequency after construction.

Collaborator

tannewt commented Feb 1, 2017

Fixed in e3f9ee8. You can now set a fixed frequency in the constructor which on SAMD will allow multiple PWMOuts to share the same timer or set variable_frequency to claim a whole timer and be able to change the frequency after construction.

@tannewt tannewt closed this Feb 1, 2017

@ladyada ladyada referenced this issue Feb 22, 2018

Closed

CircuitPython Quick Start Unification #635

16 of 16 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment