Deploying to gh-pages from @ Klipper3d/klipper@d9daeb0803 🚀
This commit is contained in:
KevinOConnor
@@ -919,6 +919,13 @@
|
||||
[bltouch]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#smart_effector" class="md-nav__link">
|
||||
[smart_effector]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
@@ -2776,6 +2783,13 @@
|
||||
[bltouch]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#smart_effector" class="md-nav__link">
|
||||
[smart_effector]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
@@ -4288,10 +4302,10 @@ max_temp:
|
||||
<div class="highlight"><pre><span></span><code>[screws_tilt_adjust]
|
||||
#screw1:
|
||||
# The (X, Y) coordinate of the first bed leveling screw. This is a
|
||||
# position to command the nozzle to that is directly above the bed
|
||||
# screw (or as close as possible while still being above the bed).
|
||||
# This is the base screw used in calculations. This parameter must
|
||||
# be provided.
|
||||
# position to command the nozzle to so that the probe is directly
|
||||
# above the bed screw (or as close as possible while still being
|
||||
# above the bed). This is the base screw used in calculations. This
|
||||
# parameter must be provided.
|
||||
#screw1_name:
|
||||
# An arbitrary name for the given screw. This name is displayed when
|
||||
# the helper script runs. The default is to use a name based upon
|
||||
@@ -4694,8 +4708,8 @@ cs_pin:
|
||||
# for more details on using this feature.
|
||||
#min_freq: 5
|
||||
# Minimum frequency to test for resonances. The default is 5 Hz.
|
||||
#max_freq: 120
|
||||
# Maximum frequency to test for resonances. The default is 120 Hz.
|
||||
#max_freq: 133.33
|
||||
# Maximum frequency to test for resonances. The default is 133.33 Hz.
|
||||
#accel_per_hz: 75
|
||||
# This parameter is used to determine which acceleration to use to
|
||||
# test a specific frequency: accel = accel_per_hz * freq. Higher the
|
||||
@@ -4853,6 +4867,53 @@ control_pin:
|
||||
# See the "probe" section for information on these parameters.
|
||||
</code></pre></div>
|
||||
|
||||
<h3 id="smart_effector">[smart_effector]<a class="headerlink" href="#smart_effector" title="Permanent link">¶</a></h3>
|
||||
<p>The "Smart Effector" from Duet3d implements a Z probe using a force sensor. One may define this section instead of <code>[probe]</code> to enable the Smart Effector specific features. This also enables <a href="G-Codes.html#smart_effector">runtime commands</a> to adjust the parameters of the Smart Effector at run time.</p>
|
||||
<div class="highlight"><pre><span></span><code>[smart_effector]
|
||||
pin:
|
||||
# Pin connected to the Smart Effector Z Probe output pin (pin 5). Note that
|
||||
# pullup resistor on the board is generally not required. However, if the
|
||||
# output pin is connected to the board pin with a pullup resistor, that
|
||||
# resistor must be high value (e.g. 10K Ohm or more). Some boards have a low
|
||||
# value pullup resistor on the Z probe input, which will likely result in an
|
||||
# always-triggered probe state. In this case, connect the Smart Effector to
|
||||
# a different pin on the board. This parameter is required.
|
||||
#control_pin:
|
||||
# Pin connected to the Smart Effector control input pin (pin 7). If provided,
|
||||
# Smart Effector sensitivity programming commands become available.
|
||||
#probe_accel:
|
||||
# If set, limits the acceleration of the probing moves (in mm/sec^2).
|
||||
# A sudden large acceleration at the beginning of the probing move may
|
||||
# cause spurious probe triggering, especially if the hotend is heavy.
|
||||
# To prevent that, it may be necessary to reduce the acceleration of
|
||||
# the probing moves via this parameter.
|
||||
#recovery_time: 0.4
|
||||
# A delay between the travel moves and the probing moves in seconds. A fast
|
||||
# travel move prior to probing may result in a spurious probe triggering.
|
||||
# This may cause 'Probe triggered prior to movement' errors if no delay
|
||||
# is set. Value 0 disables the recovery delay.
|
||||
# Default value is 0.4.
|
||||
#x_offset:
|
||||
#y_offset:
|
||||
# Should be left unset (or set to 0).
|
||||
z_offset:
|
||||
# Trigger height of the probe. Start with -0.1 (mm), and adjust later using
|
||||
# `PROBE_CALIBRATE` command. This parameter must be provided.
|
||||
#speed:
|
||||
# Speed (in mm/s) of the Z axis when probing. It is recommended to start
|
||||
# with the probing speed of 20 mm/s and adjust it as necessary to improve
|
||||
# the accuracy and repeatability of the probe triggering.
|
||||
#samples:
|
||||
#sample_retract_dist:
|
||||
#samples_result:
|
||||
#samples_tolerance:
|
||||
#samples_tolerance_retries:
|
||||
#activate_gcode:
|
||||
#deactivate_gcode:
|
||||
#deactivate_on_each_sample:
|
||||
# See the "probe" section for more information on the parameters above.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="_16">額外的步進電機和擠出機<a class="headerlink" href="#_16" title="Permanent link">¶</a></h2>
|
||||
<h3 id="stepper_z1">[stepper_z1]<a class="headerlink" href="#stepper_z1" title="Permanent link">¶</a></h3>
|
||||
<p>多步進軸。在XYZ機型打印機上，控制給定軸的步進器可能具有額外的配置塊，這些配置塊定義了應該與主步進器一起步進的步進器。可以使用從 1 開始的數字後綴定義任意數量的部分（例如，“stepper_z1”、“stepper_z2”等）。</p>
|
||||
@@ -5390,32 +5451,43 @@ pin:
|
||||
#tachometer_pin:
|
||||
#tachometer_ppr:
|
||||
#tachometer_poll_interval:
|
||||
# 以上參數的說明見“fan”部分。
|
||||
# See the "fan" section for a description of the above parameters.
|
||||
#sensor_type:
|
||||
#sensor_pin:
|
||||
#control:
|
||||
#pid_Kp:
|
||||
#pid_Ki:
|
||||
#pid_Kd:
|
||||
#pid_deriv_time:
|
||||
#max_delta:
|
||||
#min_temp:
|
||||
#max_temp:
|
||||
# 有關上述參數的說明，請參見“擠出機”部分。
|
||||
#target_temp：40.0
|
||||
# 將成為目標溫度的溫度（以攝氏度為單位）。
|
||||
# 默認為40度。
|
||||
# See the "extruder" section for a description of the above parameters.
|
||||
#pid_Kp:
|
||||
#pid_Ki:
|
||||
#pid_Kd:
|
||||
# The proportional (pid_Kp), integral (pid_Ki), and derivative
|
||||
# (pid_Kd) settings for the PID feedback control system. Klipper
|
||||
# evaluates the PID settings with the following general formula:
|
||||
# fan_pwm = max_power - (Kp*e + Ki*integral(e) - Kd*derivative(e)) / 255
|
||||
# Where "e" is "target_temperature - measured_temperature" and
|
||||
# "fan_pwm" is the requested fan rate with 0.0 being full off and
|
||||
# 1.0 being full on. The pid_Kp, pid_Ki, and pid_Kd parameters must
|
||||
# be provided when the PID control algorithm is enabled.
|
||||
#pid_deriv_time: 2.0
|
||||
# A time value (in seconds) over which temperature measurements will
|
||||
# be smoothed when using the PID control algorithm. This may reduce
|
||||
# the impact of measurement noise. The default is 2 seconds.
|
||||
#target_temp: 40.0
|
||||
# A temperature (in Celsius) that will be the target temperature.
|
||||
# The default is 40 degrees.
|
||||
#max_speed: 1.0
|
||||
# 風扇轉速（表示為 0.0 到 1.0 之間的值）
|
||||
# 將在傳感器溫度超過設定值時設置為。
|
||||
# 默認為 1.0。
|
||||
#min_speed：0.3
|
||||
# 最小風扇速度（表示為 0.0 到 1.0 的值）
|
||||
# 風扇將設置為 PID 溫度風扇。
|
||||
# 默認為 0.3。
|
||||
#gcode_id：
|
||||
# 如果設置，溫度將在 M105 查詢中使用
|
||||
# 給定 id。默認不通過 M105 上報溫度。
|
||||
# The fan speed (expressed as a value from 0.0 to 1.0) that the fan
|
||||
# will be set to when the sensor temperature exceeds the set value.
|
||||
# The default is 1.0.
|
||||
#min_speed: 0.3
|
||||
# The minimum fan speed (expressed as a value from 0.0 to 1.0) that
|
||||
# the fan will be set to for PID temperature fans.
|
||||
# The default is 0.3.
|
||||
#gcode_id:
|
||||
# If set, the temperature will be reported in M105 queries using the
|
||||
# given id. The default is to not report the temperature via M105.
|
||||
</code></pre></div>
|
||||
|
||||
<h3 id="fan_generic">[fan_generic]<a class="headerlink" href="#fan_generic" title="Permanent link">¶</a></h3>
|
||||
@@ -5463,7 +5535,7 @@ pin:
|
||||
|
||||
<h3 id="neopixel">[neopixel]<a class="headerlink" href="#neopixel" title="Permanent link">¶</a></h3>
|
||||
<p>Neopixel (aka WS2812) LED support (one may define any number of sections with a "neopixel" prefix). See the <a href="G-Codes.html#led">command reference</a> for more information.</p>
|
||||
<p>Note that the <a href="RPi_microcontroller.html">linux mcu</a> implementation does not currently support directly connected neopixels.</p>
|
||||
<p>Note that the <a href="RPi_microcontroller.html">linux mcu</a> implementation does not currently support directly connected neopixels. The current design using the Linux kernel interface does not allow this scenario because the kernel GPIO interface is not fast enough to provide the required pulse rates.</p>
|
||||
<div class="highlight"><pre><span></span><code>[neopixel my_neopixel]
|
||||
pin:
|
||||
# The pin connected to the neopixel. This parameter must be
|
||||
@@ -5474,8 +5546,9 @@ pin:
|
||||
# Neopixel is connected to the pin).
|
||||
#color_order: GRB
|
||||
# Set the pixel order required by the LED hardware (using a string
|
||||
# containing the letters R, G, B, W with W optional). The default is
|
||||
# GRB.
|
||||
# containing the letters R, G, B, W with W optional). Alternatively,
|
||||
# this may be a comma separated list of pixel orders - one for each
|
||||
# LED in the chain. The default is GRB.
|
||||
#initial_RED: 0.0
|
||||
#initial_GREEN: 0.0
|
||||
#initial_BLUE: 0.0
|
||||
|
||||
Reference in New Issue
Block a user