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.