sascha_hemi/pycom-documentation
1
0
Fork 0
mirror of https://github.com/sascha-hemi/pycom-documentation.git synced 2026-03-21 17:06:17 +01:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #254 from DG12/publish

Browse Source 
time.ticks_diff : correct argument order to  new, old ( issue #253)
This commit is contained in:
gijsio
2020-07-27 12:22:55 +02:00
committed by GitHub
parent 921d18aac9 3559add5a9
commit 47121c30d4
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
content/firmwareapi/micropython/utime.md
View File

@@ -67,7 +67,7 @@ Just like `ticks_ms` above, but in microseconds.
Same as `ticks_us`, but faster.
#### utime.ticks\_diff(old, new)
#### utime.ticks\_diff(new, old)
Measure period between consecutive calls to `ticks_ms()`, `ticks_us()`, or `ticks_cpu()`. The value returned by these functions may wrap around at any time, so directly subtracting them is not supported. `ticks_diff()` should be used instead. "old" value should actually precede "new" value in time, or result is undefined. This function should not be used to measure arbitrarily long periods of time (because `ticks_*()` functions wrap around and usually would have short period). The expected usage pattern is implementing event polling with timeout:
@@ -76,7 +76,7 @@ Measure period between consecutive calls to `ticks_ms()`, `ticks_us()`, or `tick
# Wait for GPIO pin to be asserted, but at most 500us
start = time.ticks_us()
while pin.value() == 0:
if time.ticks_diff(start, time.ticks_us()) > 500:
if time.ticks_diff(time.ticks_us(), start) > 500:
raise TimeoutError
```