The macro handler isn’t able to read the human-readable output that shows up on the console, and I don’t think the accelerometer modules have a get_status() method that would expose data in the printer object that macros could see. You might take a look at this and see if you could use it to implement a resonance testing script instead of a macro.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Read ACCELEROMETER_QUERY response in macro | 22 | 233 | June 28, 2025 | |
| TEST_RESONANCES AXIS=X Lost communication with MCU 'pico' | 3 | 749 | June 27, 2025 | |
| ADXL345 Stops working after being connected for a few seconds | 10 | 1667 | June 27, 2025 | |
| Unable to obtain 'adxl345_status' | 4 | 741 | June 27, 2025 | |
| Accelerometers query works but crashes on resonance test | 2 | 115 | December 31, 2024 |