From 4a8aece6a7f2ae5cbaa2ac283f0a82a0a613ac3d Mon Sep 17 00:00:00 2001 From: Kevin O'Connor Date: Thu, 3 Mar 2022 22:20:27 -0500 Subject: [PATCH] docs: Note g-code output is not intented to be parsed in G-Codes.md Signed-off-by: Kevin O'Connor --- docs/G-Codes.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/G-Codes.md b/docs/G-Codes.md index cc9f9ae6..2beaed00 100644 --- a/docs/G-Codes.md +++ b/docs/G-Codes.md @@ -42,7 +42,10 @@ Klipper's goal is to support the G-Code commands produced by common 3rd party software (eg, OctoPrint, Printrun, Slic3r, Cura, etc.) in their standard configurations. It is not a goal to support every possible G-Code command. Instead, Klipper prefers human readable -["extended G-Code commands"](#additional-commands). +["extended G-Code commands"](#additional-commands). Similarly, the +G-Code terminal output is only intended to be human readable - see the +[API Server document](API_Server.md) if controlling Klipper from +external software. If one requires a less common G-Code command then it may be possible to implement it with a custom