Fix some spellings
This commit is contained in:
parent
adcb87f0db
commit
93305a2d5e
@ -100,7 +100,7 @@
|
|||||||
/// check if pin is an output
|
/// check if pin is an output
|
||||||
#define _GET_OUTPUT(IO)
|
#define _GET_OUTPUT(IO)
|
||||||
|
|
||||||
/// check if pin is an timer
|
/// check if pin is a timer
|
||||||
#define _GET_TIMER(IO)
|
#define _GET_TIMER(IO)
|
||||||
|
|
||||||
/// Read a pin wrapper
|
/// Read a pin wrapper
|
||||||
@ -124,7 +124,7 @@
|
|||||||
/// check if pin is an output wrapper
|
/// check if pin is an output wrapper
|
||||||
#define GET_OUTPUT(IO) _GET_OUTPUT(IO)
|
#define GET_OUTPUT(IO) _GET_OUTPUT(IO)
|
||||||
|
|
||||||
/// check if pin is an timer wrapper
|
/// check if pin is a timer (wrapper)
|
||||||
#define GET_TIMER(IO) _GET_TIMER(IO)
|
#define GET_TIMER(IO) _GET_TIMER(IO)
|
||||||
|
|
||||||
// Shorthand
|
// Shorthand
|
||||||
|
@ -102,7 +102,7 @@ bool useable_hardware_PWM(pin_t pin);
|
|||||||
// hg42: we cannot use USEABLE_HARDWARE_PWM because it uses a function that cannot be used statically
|
// hg42: we cannot use USEABLE_HARDWARE_PWM because it uses a function that cannot be used statically
|
||||||
// hg42: instead use PWM bit from the #define
|
// hg42: instead use PWM bit from the #define
|
||||||
|
|
||||||
/// check if pin is an timer
|
/// check if pin is a timer
|
||||||
#define _GET_TIMER(IO) TRUE // could be LPC1768_PIN_PWM(IO), but there
|
#define _GET_TIMER(IO) TRUE // could be LPC1768_PIN_PWM(IO), but there
|
||||||
// hg42: could be this:
|
// hg42: could be this:
|
||||||
// #define _GET_TIMER(IO) LPC1768_PIN_PWM(IO)
|
// #define _GET_TIMER(IO) LPC1768_PIN_PWM(IO)
|
||||||
@ -132,7 +132,7 @@ bool useable_hardware_PWM(pin_t pin);
|
|||||||
/// check if pin is an output wrapper
|
/// check if pin is an output wrapper
|
||||||
#define GET_OUTPUT(IO) _GET_OUTPUT(IO)
|
#define GET_OUTPUT(IO) _GET_OUTPUT(IO)
|
||||||
|
|
||||||
/// check if pin is an timer wrapper
|
/// check if pin is a timer (wrapper)
|
||||||
#define GET_TIMER(IO) _GET_TIMER(IO)
|
#define GET_TIMER(IO) _GET_TIMER(IO)
|
||||||
|
|
||||||
// Shorthand
|
// Shorthand
|
||||||
|
@ -205,12 +205,12 @@ class TMC26XStepper {
|
|||||||
* The more regurlarly you call this function the better. In both senses of 'regularly': Calling it as often as
|
* The more regurlarly you call this function the better. In both senses of 'regularly': Calling it as often as
|
||||||
* possible is not a bad idea and if you even manage that the intervals you call this function are not too irregular helps too.
|
* possible is not a bad idea and if you even manage that the intervals you call this function are not too irregular helps too.
|
||||||
*
|
*
|
||||||
* You can call this routine even if you know that the motor is not miving. It introduces just a very small penalty in your code.
|
* You can call this routine even if you know that the motor is not moving. It introduces just a very small penalty in your code.
|
||||||
* You must not call isMoving() to determine if you need to call this function, since taht is done internally already and only
|
* You must not call isMoving() to determine if you need to call this function, since taht is done internally already and only
|
||||||
* slows down you code.
|
* slows down you code.
|
||||||
*
|
*
|
||||||
* How often you call this function directly influences your top miving speed for the motor. It may be a good idea to call this
|
* How often you call this function directly influences your top moving speed for the motor. It may be a good idea to call this
|
||||||
* from an timer overflow interrupt to ensure proper calling.
|
* from a timer overflow interrupt to ensure proper calling.
|
||||||
* \sa step()
|
* \sa step()
|
||||||
*/
|
*/
|
||||||
char move(void);
|
char move(void);
|
||||||
|
Loading…
Reference in New Issue
Block a user