diff options
author | Mikkel Schmidt <mikkel.schmidt@gmail.com> | 2022-05-24 01:56:58 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-05-23 19:56:58 -0400 |
commit | af38d708cb3fad993422b8cf6bf4880acda568a3 (patch) | |
tree | 4f91fad6a1379511f0975a0a934bc494a490278f /docs/G-Codes.md | |
parent | c7e0372c5de4680760721674dc86959dc5d239ec (diff) | |
download | kutter-af38d708cb3fad993422b8cf6bf4880acda568a3.tar.gz kutter-af38d708cb3fad993422b8cf6bf4880acda568a3.tar.xz kutter-af38d708cb3fad993422b8cf6bf4880acda568a3.zip |
adxl345: Support recording data from multiple ADXL345's in one run, and more. (#5224)
Add PROBE and CHIP to TEST_RESONANCES
Since it's possible to specify more than one chip
in TEST_RESONANCES the CHIP parameter has been
renamed to CHIPS
Signed-off-by: Mikkel Schmidt <mikkel.schmidt@gmail.com>
Diffstat (limited to 'docs/G-Codes.md')
-rw-r--r-- | docs/G-Codes.md | 19 |
1 files changed, 12 insertions, 7 deletions
diff --git a/docs/G-Codes.md b/docs/G-Codes.md index 4dcbe729..eedb84cc 100644 --- a/docs/G-Codes.md +++ b/docs/G-Codes.md @@ -896,23 +896,28 @@ all enabled accelerometer chips. #### TEST_RESONANCES `TEST_RESONANCES AXIS=<axis> OUTPUT=<resonances,raw_data> [NAME=<name>] [FREQ_START=<min_freq>] [FREQ_END=<max_freq>] -[HZ_PER_SEC=<hz_per_sec>] [INPUT_SHAPING=[<0:1>]]`: Runs the resonance +[HZ_PER_SEC=<hz_per_sec>] [CHIPS=<adxl345_chip_name>] +[POINT=x,y,z] [INPUT_SHAPING=[<0:1>]]`: Runs the resonance test in all configured probe points for the requested "axis" and measures the acceleration using the accelerometer chips configured for the respective axis. "axis" can either be X or Y, or specify an arbitrary direction as `AXIS=dx,dy`, where dx and dy are floating point numbers defining a direction vector (e.g. `AXIS=X`, `AXIS=Y`, or `AXIS=1,-1` to define a diagonal direction). Note that `AXIS=dx,dy` -and `AXIS=-dx,-dy` is equivalent. If `INPUT_SHAPING=0` or not set -(default), disables input shaping for the resonance testing, because +and `AXIS=-dx,-dy` is equivalent. `adxl345_chip_name` can be one or +more configured adxl345 chip,delimited with comma, for example +`CHIPS="adxl345, adxl345 rpi"`. Note that `adxl345` can be omitted from +named adxl345 chips. If POINT is specified it will override the point(s) +configured in `[resonance_tester]`. 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 -(across all probe points) and written into +`/tmp/raw_data_<axis>_[<chip_name>_][<point>_]<name>.csv` with +(`<point>_` part of the name generated only if more than 1 probe point +is configured or POINT is specified). If `resonances` is specified, the +frequency response is calculated (across all probe points) and written into `/tmp/resonances_<axis>_<name>.csv` file. If unset, OUTPUT defaults to `resonances`, and NAME defaults to the current time in "YYYYMMDD_HHMMSS" format. |