From 71063fe50099d8a196345d02d2fb0354dc0b0d25 Mon Sep 17 00:00:00 2001 From: Kevin O'Connor Date: Wed, 8 Aug 2018 13:49:46 -0400 Subject: [PATCH] docs: Warn about possible pin conflicts in benchmarks Signed-off-by: Kevin O'Connor --- docs/Debugging.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/Debugging.md b/docs/Debugging.md index 36a24e38..cc68d526 100644 --- a/docs/Debugging.md +++ b/docs/Debugging.md @@ -190,6 +190,11 @@ is not achievable in day-to-day use as Klipper needs to perform other tasks (eg, mcu/host communication, temperature reading, endstop checking) in any real-world usage. +In general, the pins for the benchmark tests are chosen to flash LEDs +or other innocuous pins. **Always verify that it is safe to drive the +configured pins prior to running a benchmark.** It is not recommended +to drive an actual stepper during a benchmark. + ## Step rate benchmark test ## The test is performed using the console.py tool (described above). The