From 70e53cb0800c47bb75d3c11764cfb7c41e6cc801 Mon Sep 17 00:00:00 2001 From: Kevin O'Connor Date: Tue, 11 Apr 2017 12:36:29 -0400 Subject: [PATCH] docs: Update Firmware_Commands with recent end stop changes Signed-off-by: Kevin O'Connor --- docs/Firmware_Commands.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/Firmware_Commands.md b/docs/Firmware_Commands.md index d6ad2d8f..52249d88 100644 --- a/docs/Firmware_Commands.md +++ b/docs/Firmware_Commands.md @@ -179,15 +179,15 @@ This section lists some commonly used config commands. ticks since the last step. It is used as a check on the maximum stepper velocity that a stepper may have before stopping. -* config_end_stop oid=%c pin=%c pull_up=%c stepper_oid=%c : This +* config_end_stop oid=%c pin=%c pull_up=%c stepper_count=%c : This command creates an internal "endstop" object. It is used to specify the endstop pins and to enable "homing" operations (see the end_stop_home command below). The command will configure the specified pin in digital input mode. The 'pull_up' parameter determines whether hardware provided pullup resistors for the pin - (if available) will be enabled. The 'stepper_oid' parameter - specifies the oid of an associated stepper for the given endstop - - it is used during homing operations. + (if available) will be enabled. The 'stepper_count' parameter + specifies the maximum number of steppers that this endstop may need + to halt during a homing operation (see end_stop_home below). Common commands ===============