docs: Todo updates
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
This commit is contained in:
parent
98ce7dc465
commit
93bd19a8c2
46
docs/Todo.md
46
docs/Todo.md
|
@ -17,12 +17,27 @@ Host user interaction
|
||||||
highlight an error (one has to look in the terminal tab to find the
|
highlight an error (one has to look in the terminal tab to find the
|
||||||
error) and errors written to the log can be non-obvious to a user.
|
error) and errors written to the log can be non-obvious to a user.
|
||||||
|
|
||||||
* Route errors from the host C code to the main log file.
|
* Implement timeouts on homing. The host currently waits forever if
|
||||||
|
an endstop is not hit during a homing operation.
|
||||||
|
|
||||||
* Support clearing MCU shutdown events from the host without having to
|
* Improve startup:
|
||||||
restart the firmware.
|
|
||||||
|
|
||||||
* Provide startup scripts so that Klippy can startup at system bootup.
|
* Provide startup scripts so that Klippy can startup at system
|
||||||
|
bootup.
|
||||||
|
|
||||||
|
* Possibly rework the startup order of Klippy communication with
|
||||||
|
octoprint and the mcu. Currently Klippy only starts communication
|
||||||
|
with Octoprint after it connects with the firmware. However, this
|
||||||
|
limits the ability for Klippy to communicate connection errors to
|
||||||
|
the user. It also makes it difficult for Klippy to reconnect to the
|
||||||
|
firmware and/or restart the firmware if it needs to.
|
||||||
|
|
||||||
|
* Support clearing MCU shutdown events from the host without having
|
||||||
|
to restart the firmware.
|
||||||
|
|
||||||
|
* Allow loading of a new config without having to restart the mcu.
|
||||||
|
|
||||||
|
* Improve gcode interface:
|
||||||
|
|
||||||
* Support ASCII based commands in addition to common gcode
|
* Support ASCII based commands in addition to common gcode
|
||||||
commands. It would be useful to support high-level commands such as
|
commands. It would be useful to support high-level commands such as
|
||||||
|
@ -37,26 +52,23 @@ Host user interaction
|
||||||
can issue commands that potentially move the head past
|
can issue commands that potentially move the head past
|
||||||
position_min/position_max.
|
position_min/position_max.
|
||||||
|
|
||||||
* Implement timeouts on homing. The host currently waits forever if
|
* Improve logging:
|
||||||
an endstop is not hit during a homing operation.
|
|
||||||
|
|
||||||
* Allow loading of a new config without having to restart the mcu.
|
* Route errors from the host C code to the main log file.
|
||||||
|
|
||||||
* Possibly rework the startup order of Klippy communication with
|
|
||||||
octoprint and the mcu. Currently Klippy only starts communication
|
|
||||||
with Octoprint after it connects with the firmware. However, this
|
|
||||||
limits the ability for Klippy to communicate connection errors to
|
|
||||||
the user. It also makes it difficult for Klippy to reconnect to the
|
|
||||||
firmware and/or restart the firmware if it needs to.
|
|
||||||
|
|
||||||
* Automatically roll Klippy log files. The default log file should
|
* Automatically roll Klippy log files. The default log file should
|
||||||
have the current date in the log file name.
|
have the current date in the log file name.
|
||||||
|
|
||||||
* Report the Klippy git version in log file.
|
* Report the Klippy git version in log file. Log the contents of the
|
||||||
|
config file at startup.
|
||||||
|
|
||||||
* Possibly collate and report the statistics messages in the log in a
|
* Possibly collate and report the statistics messages in the log in a
|
||||||
more friendly way.
|
more friendly way.
|
||||||
|
|
||||||
|
* Possibly support a mechanism for the host to limit maximum velocity
|
||||||
|
so that the mcu is never requested to step at a higher rate than it
|
||||||
|
can support.
|
||||||
|
|
||||||
Safety features
|
Safety features
|
||||||
===============
|
===============
|
||||||
|
|
||||||
|
@ -77,6 +89,8 @@ Safety features
|
||||||
can be useful to detect a sensor failure (eg, thermistor short) that
|
can be useful to detect a sensor failure (eg, thermistor short) that
|
||||||
could otherwise cause the PID to command excessive heating.
|
could otherwise cause the PID to command excessive heating.
|
||||||
|
|
||||||
|
* Verify the endstop is no longer triggered after retraction.
|
||||||
|
|
||||||
* Possibly implement host based checking on the ratio between extrude
|
* Possibly implement host based checking on the ratio between extrude
|
||||||
amount and head movement.
|
amount and head movement.
|
||||||
* Enforce acceleration and speed limits on extruder stepper motor.
|
* Enforce acceleration and speed limits on extruder stepper motor.
|
||||||
|
@ -100,8 +114,6 @@ Documentation
|
||||||
* Document the kinematic formulas in Klippy. Document how acceleration
|
* Document the kinematic formulas in Klippy. Document how acceleration
|
||||||
and jerk limits are enforced.
|
and jerk limits are enforced.
|
||||||
|
|
||||||
* Document the host/firmware communication protocol.
|
|
||||||
|
|
||||||
* Document how one can tune the pressure advance setting.
|
* Document how one can tune the pressure advance setting.
|
||||||
|
|
||||||
Hardware features
|
Hardware features
|
||||||
|
|
Loading…
Reference in New Issue