aboutsummaryrefslogtreecommitdiffstats
path: root/docs/G-Codes.md
diff options
context:
space:
mode:
authorDmitry Butyugin <dmbutyugin@google.com>2021-01-29 20:47:10 +0100
committerKevinOConnor <kevin@koconnor.net>2021-02-02 14:13:24 -0500
commita8b282d67a085714b3dab02fbc6afacd7351ae29 (patch)
tree403852adf33bfd537559139435841b47927b4f7c /docs/G-Codes.md
parent0fb2449be035efe729d587a3257ac9a9fe8178bc (diff)
downloadkutter-a8b282d67a085714b3dab02fbc6afacd7351ae29.tar.gz
kutter-a8b282d67a085714b3dab02fbc6afacd7351ae29.tar.xz
kutter-a8b282d67a085714b3dab02fbc6afacd7351ae29.zip
resonance_tester: Disable input shaping for resonance testing
Signed-off-by: Dmitry Butyugin <dmbutyugin@google.com>
Diffstat (limited to 'docs/G-Codes.md')
-rw-r--r--docs/G-Codes.md15
1 files changed, 9 insertions, 6 deletions
diff --git a/docs/G-Codes.md b/docs/G-Codes.md
index c6f99658..c656c416 100644
--- a/docs/G-Codes.md
+++ b/docs/G-Codes.md
@@ -728,12 +728,15 @@ is enabled (also see the
all enabled accelerometer chips.
- `TEST_RESONANCES AXIS=<axis> OUTPUT=<resonances,raw_data>
[NAME=<name>] [FREQ_START=<min_freq>] [FREQ_END=<max_freq>]
- [HZ_PER_SEC=<hz_per_sec>]`: Runs the resonance test in all
- configured probe points for the requested axis (X or Y) and measures
- the acceleration using the accelerometer chips configured for the
- respective axis. `OUTPUT` parameter is a comma-separated list of
- which outputs will be written. If `raw_data` is requested, then the
- raw accelerometer data is written into a file or a series of files
+ [HZ_PER_SEC=<hz_per_sec>] [INPUT_SHAPING=[<0:1>]]`: Runs the resonance
+ test in all configured probe points for the requested axis (X or Y)
+ and measures the acceleration using the accelerometer chips configured
+ for the respective axis. If `INPUT_SHAPING=0` or not set (default),
+ disables input shaping for the resonance testing, because it is not valid
+ to run the resonance testing with the input shaper enabled.
+ `OUTPUT` parameter is a comma-separated list of which outputs will be
+ written. If `raw_data` is requested, then the raw accelerometer data
+ is written into a file or a series of files
`/tmp/raw_data_<axis>_[<point>_]<name>.csv` with (`<point>_` part of
the name generated only if more than 1 probe point is configured).
If `resonances` is specified, the frequency response is calculated