Hello. I am using a triple z system. When I use a probe as an endstop, everything is fine. However, if I configure 3 endstops (mechanical switches) and send z_tilt_adjust, it goes to the shutdown state and raises the errors ‘!! Unable to obtain ‘trsync_state’ response’ and ‘Timer too close’. Only ch…

It appears the log file you’ve attached here has been modified. There’s not much we can do without the full unmodified log file. As mentioned at Unable to obtain 'trsync_state' response · Issue #4436 · KevinOConnor/klipper · GitHub , you’ll need to recreate the issue with the pristine software and…

Sorry for the wrong one. It’s here: klippy.log (89.6 KB)

I get the same issue. The last lines in the console in fluid are: 16:56:49 // Klipper state: Ready 16:56:54 File opened:Adapter_Hemera_v2_remix_0.2mm_PLA_ENDER3_1h57m.gcode Size:5004545 16:56:54 File selected 16:56:54 // Unknown command:"M486" 16:59:19 // Klipper state: Shutdown 16:59:20 !! Unable…

I have done some bugfinding using git bisect to see which commit introduces the bug. I got this response: 983951443cf14fe2985585c2c2eb20efe526411d is the first bad commit commit 983951443cf14fe2985585c2c2eb20efe526411d Author: Kevin O'Connor <kevin@koconnor.net> Date: Mon Feb 15 16:02:40 2021 -0…

I think I have reproduced @LordTimmeh ’s claim above on my printer. I went back (firmware and host) to 98395144 (my log files labeled “trial 6”) and it failed on pass 2, point 5 (of 7) of the Z_TILT_ADJUST. klippy.log.reproducible-Z-tilt-trsync-error-6.log (490.7 KB) moonraker.log.reproducible-Z-t…

I then went back (firmware and host) to e1f7748e (my log files labeled “trial 7”) and it worked (full Z_TILT_ADJUST). klippy.log.reproducible-Z-tilt-trsync-error-7.log (352.9 KB) moonraker.log.reproducible-Z-tilt-trsync-error-7.log (24.6 KB) CPU-uptime.log.reproducible-Z-tilt-trsync-error-7.log (…

I performed further tests as follows: Switched Pi only to e1f7748 (trial 9) - WORKED Switched Pi only to 98395 (trial 10) - FAILED Switched Pi only to e1f7748 (trial 11) - WORKED I had a theory that it might be consuming some data structure, so I added an additional point to the set of Z tilt poi…

Thanks. I will try to analyze the logs in the coming days. If you have a workaround (eg, git checkout e1f7748e) then I recommend sticking with that until this can be tracked down. -Kevin

Will do. I’m definitely working/not blocked now. (TY to LordTimmey for the bisection research.) I’m also more than happy to test any ideas, theories, or code such that will help you get to the bottom of this. (I was once competent at C/C++, now a little rusty.) I doubt any additional log files wil…

This issue looks like it is due to a 32bit timer rollover problem caused by an omission in the new trsync homing code. Hopefully it is now fixed (commit f2421005). Thanks. -Kevin

Unable to obtain 'trsync_state' response

General Discussion

Topic		Replies	Views
Unable to obtain 'trsync_state' response - reproducible case General Discussion	4	1169	September 4, 2021
! TMC 'stepper_y' reports error: DRV_STATUS: 801f5000 s2vsa=1 stealth=1 CSACTUAL=31 stst=1 General Discussion	47	19766	June 16, 2024
Z Tilt Check Without Klipper Auto Adjusting? General Discussion	45	1305	July 31, 2024
Z_Tilt Issue, z fine, z1 going up to probe General Discussion	5	117	November 11, 2024
Configurable timeout Features	26	2587	March 27, 2024

Unable to obtain 'trsync_state' response

Related topics