3diy
/
klipper
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

config: Reword bltouch description in example-extras.cfg 

The pin_up_touch_mode_reports_triggered should be set to True on all
genuine BLTouch.

Expand the description for stow_on_each_sample and state the default.

Reword the set_output_mode option to be more similar to other
descriptions.

It is no longer necessary to warn about clones being not supported.

Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
This commit is contained in:
Kevin O'Connor 2020-04-02 09:03:40 -04:00
parent 6d2f3ef4f1
commit 7a67cb86d5
1 changed files with 16 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
config/example-extras.cfg
View File

@ -610,8 +610,7 @@
# not run any special G-Code commands on deactivation.
# BLTouch probe. One may define this section (instead of a probe
# section) to enable a BLTouch probe. (Note! This bltouch module may
# not work correctly with some BLTouch "clones"!) A virtual
# section) to enable a BLTouch probe. A virtual
# "probe:z_virtual_endstop" pin is also created (see the "probe"
# section above for the details).
#[bltouch]
@ -624,28 +623,27 @@
#pin_move_time: 0.675
# The amount of time (in seconds) to wait for the BLTouch pin to
# move up or down. The default is 0.675 seconds.
#stow_on_each_sample: True
# This determines if Klipper should command the pin to move up
# between each probe attempt when performing a multiple probe
# sequence. Setting this to False can allow for faster probing, but
# using this mode requires careful tuning of probing speed
# parameters. The default is True.
#pin_up_reports_not_triggered: True
# Set if the BLTouch consistently reports the probe in a "not
# triggered" state after a successful "pin_up" command. This should
# be True for a genuine BLTouch; some BLTouch clones may require
# False. The default is True.
# be True for all genuine BLTouch devices. The default is True.
#pin_up_touch_mode_reports_triggered: True
# Set if the BLTouch consistently reports a "triggered" state after
# the commands "pin_up" followed by "touch_mode". This should be
# True for a genuine BLTouch v2 and earlier; the BLTouch v3 and some
# BLTouch clones require False. The default is True.
#stow_on_each_sample: True
# If set to False, intermediate STOW/DEPLOY sequences on certain
# operations that use the probe multiple times will be omitted.
#set_ouput_mode: [Possible values: 5V, OD, or do not specify this
# parameter at all if you don't want a mode setting to be performed]
# A BLTouch Smart V3.0 or V3.1(+) supports selection of an output
# mode, 5V or OPEN DRAIN. If your controller board NEEDs 5V mode
# AND it is 5V tolerant on its input signal line, you can use this
# parameter. Note also that for a V3.1, it is possible to not specify
# this parameter at all and instead to manually use a "BLTOUCH_STORE
# MODE=" command to store the desired output mode permanently in the
# probes EEPROM (see the documentation for this command).
# True for all genuine BLTouch devices. The default is True.
#set_output_mode:
# Request a specific sensor pin output mode on the BLTouch V3.0 (and
# later). This setting should not be used on other types of probes.
# Set to "5V" to request a sensor pin output of 5 Volts (only use if
# the controller board needs 5V mode and is 5V tolerant on its input
# signal line). Set to "OD" to request the sensor pin output use
# open drain mode. The default is to not request an output mode.
#x_offset:
#y_offset:
#z_offset: