# Resonance HW only works after 1st attempt **URL:** \ **Category:** General Discussion\ **Created:** [January 8, 2025, 4:02pm UTC](https://klipper.discourse.group/t/resonance-hw-only-works-after-1st-attempt/21222 "2025-01-08T16:02:50Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![SoylentGeek](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/soylentgeek/32/14755_2.png) [@SoylentGeek](https://klipper.discourse.group/u/SoylentGeek)\ **Post date:** [January 8, 2025, 4:02pm UTC](https://klipper.discourse.group/t/resonance-hw-only-works-after-1st-attempt/21222/1 "2025-01-08T16:02:50Z")
### Basic Information: Printer Model: Tevo Tornado / Wanhao i3 MCU / Printerboard: MKS Gen L V2.1 Host / SBC: RPI4 klippy.log [klippy.zip](https://klipper.discourse.group/uploads/short-url/ctLfTeTUwWuBc1zzVrWxI1iXHii.zip) (2.9 MB) _Fill out above information and_ **_in all cases attach your_ `klippy.log` _file_** (use zip to compress it, if too big). _Pasting your_ `printer.cfg` _is **not** needed_ _ **Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there** _ ### Describe your issue: … I have on both my printers two BTT S2DW (one for X, one for Y) They are permanently installed so that I don’t need to fiddle every time I want to do a test. So, this is happening on both printers so I am assuming it’s a bug or perhaps I have something configured incorrectly. When I go to do my Resonance Testing, it fails the first time I run the command, the 2nd time it works great, then it goes to try and do Y, same thing. It goes though X just fine but the first time it attempts to start Y it fails. If I run it again, both axis will work perfectly. What have I done wrong? D ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [January 8, 2025, 6:51pm UTC](https://klipper.discourse.group/t/resonance-hw-only-works-after-1st-attempt/21222/2 "2025-01-08T18:51:08Z")
The attached log does not seem to contain any such event or I missed it. ---
**Author:** ![SoylentGeek](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/soylentgeek/32/14755_2.png) [@SoylentGeek](https://klipper.discourse.group/u/SoylentGeek)\ **Post date:** [January 14, 2025, 9:16pm UTC](https://klipper.discourse.group/t/resonance-hw-only-works-after-1st-attempt/21222/3 "2025-01-14T21:16:46Z")
Sorry for the late reply. I just tried it again after doing a complete re-wire of the printer just in case it was a physical issue. This is the error in the Console Invalid lis2dw id (got ff vs 44). 4:03 PM Invalid lis2dw id (got ff vs 44). This is generally indicative of connection problems (e.g. faulty wiring) or a faulty lis2dw chip. I attached a log that I captured right after the operation I did. [klippy.zip](https://klipper.discourse.group/uploads/short-url/8CIuB5gPuK1hKFT0OoNLhG6Z7ru.zip) (1.4 MB) It’s weird that it errors on first run of each axis, then, if you run it a 2nd time, it works. D ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [January 15, 2025, 12:21pm UTC](https://klipper.discourse.group/t/resonance-hw-only-works-after-1st-attempt/21222/4 "2025-01-15T12:21:49Z")
This is indeed strange. In fact there had been an issue with SPI connected hardware on RP2040 boards that would cause such issues, but: - This issue was only affecting hardware SPI but not software SPI - Has been resolved quite a while ago Not sure what could be causing this issue. If I find the time, I’ll try with an RP2040 based LIS2DW board on my side. ---
**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/64419bf2aac6639e6ef5cef200dcd456b0a01ac3.png) [@system](https://klipper.discourse.group/u/system)\ **Post date:** [March 16, 2025, 12:22pm UTC](https://klipper.discourse.group/t/resonance-hw-only-works-after-1st-attempt/21222/5 "2025-03-16T12:22:12Z")
Closed on March 16, 2025, 12:22pm UTC This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.