X Homing issue after Sonic Pad Resonance Test

I bought a sonic pad for my Ender-3 v3 SE. Everything seemed to be going well. I was able to do a super-fast print of an X-axis holder for the vibration sensor and did the calibration. But then I realized the model I used had the sensor facing the opposite way. Not knowing if that would affect anything, I decided to do another resonance test.

Homing for the test caused intense vibration and the nozzle never got to the point where it could trigger.

Steps taken:

  • Factory reset sonic pad, and re-flashed printer firmware. initial self test failed with the same behavior.
  • Flashed printer/screen Marlin software from Creality, 1.6.6. The printhead moves almost the entire axis, but never hits the trigger.
  • attempted at various belt tensions from tightest to when it starts to skip.
  • Inspected X stepper motor cable. No obvious signs of wear or breakage
  • Inspected board. Everything is still hot glued in place, and no glue or filament strings are on the board.
  • When still in klipper mode, homed Y just fine.

I’ve engaged support, but they haven’t gotten back to me. The best info I can find for this model is that it’s either a faulty stepper motor, faulty wiring, or faulty board.

Any other possible issues to check would be appreciated, or any ideas for how to limit the scope of the problem further.

Check the wiring to your end stops. The test can vibrate things loose. Most newer systems use an active (NC) until depressed to provide a more reliable and repeatable stop location.

  • Inspected X stepper motor cable. No obvious signs of wear or breakage
  • Inspected board. Everything is still hot glued in place, and no glue or filament strings are on the board.

Is the end-stop cable somewhere else that I’m not seeing? The print head cable has remained firmly in place, but I have not unscrewed it to visually inspect individual cables.

Some end-stops have led to showing an active state.
See the working end stops if they have this type of indicator. If so, activate it and watch, then see if the non-working stop reacts the same.

All end-stops report as open