Timing Manager Tutorial#112
Conversation
codecubepi
left a comment
There was a problem hiding this comment.
Hey @Known4225 , excellent start!
Please review my feedback with @elsevers .
There was a problem hiding this comment.
A comment from @elsevers ... do we have the original SVG for this image somewhere? Likely a request for @npetersen2
codecubepi
left a comment
There was a problem hiding this comment.
Thanks for the first round of changes @Known4225 . Here are a few more things I caught.
| ``` | ||
|
|
||
| The ADC time to acquire refers to how long between the trigger for the ADC to start sampling to when it was complete.\ | ||
| The ADC time since done is the "staleness" of the data, it refers to how long ago the ADC reported done. This may be useful when controlling a motor with careful timing considerations. |
There was a problem hiding this comment.
Two things:
- Write this as a deliberate step that a user should take (i.e., program your code onto the AMDC and measure the sensor acquisition timing using the newly created
ctrl sensor timingcommand). - Move it down into the
Sensor Timingsubsection. I suggest that you start theSensor Timingsubsection by telling the user to do two things:- Run
ctrl sensor timingto obtain sensor acquisition timing information - Run
ctrl stats printto obtain run time and loop time
- Run
|
Change requests per 12/19 meeting with @elsevers 1. Initial timing diagrams in
|
|
@Known4225, I have made edits to the tutorial in #123. Let's get these merged in and then have you address this feedback. We're getting close! |
…orial Edit timing manager tutorial
Add additional edits from Eric
elsevers
left a comment
There was a problem hiding this comment.
Looks great! let's get this merged.



This PR closes #100.
This Timing & Sensors tutorial expands upon the VSI tutorial and enables the ADC sensor to observe the effects of the timing manager. Users will learn how certain tuning parameters (mainly the User Event Ratio and the PWM frequency) can affect the loop time of their control tasks.