-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
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
Timer period unable to set to microseconds #2792
Comments
This question is more appropriate for the forum. What board are you using? The pyboard timers can go all the way to 1/42 MHz granularity (or 1/84 MHz depending on the timer). Can you provide some code? Here's some code for the pyboard that uses microsecond granularity: |
Oh, my bad, will use the forum in the future, thanks. I am trying to use the ESP12e board. The code I am attempting to use is: from machine import Timer And this virtual timer works but with only ms granularity. I realise the timing at these levels is not accurate but being able to set in us would provide for smooth fading. Is it currently possible to implement hardware timers on the esp8266? |
Thanks for switching to forum. Closing. |
When allocate_display_bus_or_raise was factored out, the assignment of the bus's Python type was lost. Restore it. This would have affected displays of any type other than RGBMatrix, when they were created dynamically. Boards with displays configured in flash were unaffected. Closes: micropython#2792
Is there a reason why timer periods are measured in milliseconds while the timers on the pyboard are in microseconds? Is there a way to get sub-ms granularity with the timers? I am trying to implement AC phase control with a triac and the millisecond limitation is essentially limiting my output to only 10 discrete steps.
Apologies if the answer can be found here already, or if this is a newbie question- I have been searching all day to no avail.
The text was updated successfully, but these errors were encountered: