Closed KevinOConnor closed 5 months ago
I think this change is good for code quality.
About the maximum_mcu_duration
I personally only use it together with pwm_tool
, but I can imagine that people might use it for something safety related. At the same time, they could just use pwm_tool
instead, even if it is not actually a tool, so it is probably just fine.
Over the last few years the
output_pin
module has gained a handful of options that have made it harder to maintain the the low-level backend code. This PR simplifies the output_pin module. The main changes are:static_value
parameter is deprecated. This option has little impact - it only saves a few bytes in the micro-controller. Going forward it is simple enough to just not specify it.maximum_mcu_duration
parameter is deprecated. Thepwm_tool
module is a better choice for tools that require this capability. It should be straight forward for users to change their configs from[output_pin mypin]
to[pwm_tool mypin]
.SET_PIN CYCLE_TIME=x
g-code command for[output_pin mypin]
config sections has been removed. Users can convert to a new[pwm_cycle_time mypin]
config as a replacement. This change is setup to take effect immediately (no deprecation period).This is the last PR as part of the
pwm_tool
series of changes (eg, #6369, #6410, #6420).@Cirromulus - fyi.
-Kevin