| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Rename this function to make it more clear why it is called.
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
|
|
|
|
|
|
|
|
|
| |
There is no harm in enabling flushing for a little longer than
necessary. In contrast, a slight rounding issue causing a message to
not get flushed properly could result in an error. So, extend the
flushing time slightly to avoid potential issues.
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
|
|
|
|
|
|
|
| |
References to pins.error are not valid as the pins module is not
imported. Reported by @Piezoid.
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
|
|
|
|
|
|
|
| |
Implement the maximum_mcu_duration config parameter along with its
associated queue flushing.
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
|
|
|
|
|
|
|
|
|
|
| |
Call toolhead.note_kinematic_activity() on each pin update to ensure
that those updates will be flushed properly.
This fixes "Timer too close" errors on SET_PIN commands that are
issued when the toolhead is idle.
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
|
|
The output_pin module is only capable of updating an output pin at
most once every 100ms. Add a new pwm_tool module that is capable of
queuing updates in the micro-controller and thus allowing for much
higher update rates.
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
|