MCU 'mcu' shutdown: Timer too close still present #124
Comments
|
working :) |
|
I also have this issue! occurs after running a macro and when its starts to compile the data. Also having issues where it just errors out compiling the csv to png. 11:12:46 PM |
|
I ran into this during a few different operations. I reniced klippy to -7, and later put the klippy process into a cpuset sheild, and that seems to keep it safe enough |
Mhmm not sure to understand how you did this? Did you directly modify the Klipper files? |
|
For testing, at runtime: For a more permanent soloution: Create/edit systemd dropin to set default cpu affinity Move klippy service other CPUs Note: My klipper host service is named 'klippy' and not 'klipper' ( 'klipper' is way more common ) |
|
Note that a process cannot decrease it's own "niceness", so setting negative values requires some kind of privileged thing. In this case, it is the service manager. There are a few differences between the two setups, one uses cpusets, the other affinity, but in this configuration, they should have almost identical effects. |
|
On a 4c cortex a-53, with top at 1.4G, I compiled klipper during an input shaper run, and saw klippy using 60%+ between the two cores, and the compiler ran the other two cores into the wall. This is with the |
|
Hello everyone, could you update to v4.0.2 that is now out and let me know if this error is now fixed? |
|
klippy (34).log |
|
Same error since updating to v4. During the testing, the CPU is around 35%, RAM between 45% and 70% |
this trick didnt worked for me |
|
Renicing didn't work on my setup either. The shutdown doesn't seem to have a clear pattern. Sometimes it occurs between 30-60 hz, sometimes when 120 is reached. Couldn't get one measurement to finish. |
|
I Run my klipper on a Pi4b 8GB. I am also using a Pi cam3. Are you guys using any cameras ? |
|
im running on orange pi zero 3 with logitech webcam |
|
I have a noname Webcam added, as well as a Fystec Hotkey board, but I removed them both for testing and it didn't change. The only other MCU that is running is the interface for the ADXL345 which is directly connected to the Raspi. |
|
Hello 19:37 MCU 'mcu' shutdown: Timer too close |
|
I am getting the same "timer to close". Running Manta M5P with CB1 on a Ender 5 Pro/Merc 1.1 adxl in EBB42 on tool head. It runs fine for belts and inputshaper. But errors out when trying to create vibrations profile |
|
Small update. Managed to run through COMPARE_BELTS_RESPONSES without mcu shutdown. I lowered my mycrosteps to reduce the load. lowered from 32 to 16. |
All of mine are already at 16 and I got a MCU shutdown about 30 seconds into trying to run it, 3 times in a row. When this current print finishes I will attempt to run it again, If I get a different result I will post it here. |
try 8 |
|
ye even with that its still really unreliable. it works 1 time out of 5 |
I double checked today and I am running 4.1.0 and still having an issue. But only with |
|
Same here on fly-gemini v3, no camera but I have klipper screen and extender connected. Will try w/o later. Edit: I've experimented with (in my case) BTW. I found this post on official klipper forum
|
|
I get timer too close sometimes too. FWIW, Manta M8P V2 with CB1. Temperatures stay below ~46C. I have also had issues where the vibrations test (400mm/s, 200mm size, 2500mm/s^2 accel) will usually run fine but I get a timeout error as it's crunching the data after the motion part of the test. I looked for the timeout value in the code but I can't seem to find it. I think it's likely the CB1. I'm thinking it will help... I have a CB2 ordered from BTT but who knows when they'll decide to send it from China. Looks like it's in stock now but they don't seem to be in any hurry to get it boxed up and shipped. :( |
|
I switch from gemini v3 to skr pico + orangepi zero 2, update the 'niceness' following @Laikulo suggestions and it seems to be working now (done about 8 vibration profiles and no issue) |
|
I was getting these errors as well when trying to run this test hot. but found that turning off the heaters was enough to let it complete |
|
Hello all, I've done a bit of diagnostics on this issue and was able to reproduce it on one of my machines (now equipped with a CB1 that I just bought for the occasion). What I've found is that it happens when the SOC start to get very hot and get above the throttling temperature, which is by default at 60 degrees in the latest Raspbian images I found, but it's also set to 70 degrees sometime on some other images. I think that when the SOC starts to throttle, all cores (and their running process) are slowed down to avoid overheating, this doesn't affect S&T much, but causes problems for Klipper, which expects very precise timing. So my current solutions that fixed it on my machine are:
On my side I'm still looking for a solid solution to reduce the computing power needed for S&T... Or a solution that would avoid throttling the Klipper core and only S&T or... whatever. If anyone here has an idea, I'm totally open! |
Hopefully thats not too much off topic: This is just something that worked for me and I don't know, if it works for you...I am using M8P V2 with CB1 and an EBB SB2209 in a Voron R2.4 build and also had After the following steps, the 1. Shorten the CAN bus cableI had loops of it lying around in the electronics compartment, as I thought I might need the 2. Shorten the can0 interfaces txqueuelen to 128As stated in the klipper documentation. For this my 3. Give klipper some special priorities and nice valuesFor this I used For good measure I didn't just restart the klipper service, but the whole printer ... 4. Deactivate
|
|
I dont know but no have problem with this work fine :) can, sb2209 no problem and last update klipper fix many things.... |
|
hello, after updating everything I could and doing a lot of tests I'm in the same situation as @pylorak. Have you suggestions how fix it? Or found the root cause ? |
|
Hello all, I just updated the So basically, you can add in your @pylorak and @zavax (and anyone else who wants to try), can you try with lower values like 10, 5 and 2? Also, please clean your klippy.log before each measurement and send them to me. I want to look at the RAM and CPU usage for each chunking value. Hopefully, a lower value will make it work: if that's the case, I will lower the default. |
|
Ok, I've updated the default value to 2 for everyone, as in my own tests this was the value that gave the best performance in terms of RAM usage, and I didn't see any downside. So if you just update the |
|
Hello @Frix-x moonraker-chunk 2.log |
|
Thanks @zavax for your testings! So it appears that in your case it fail every time due to RAM usage and limits... Can you tell me the result of this command: |
|
swapon --show |
|
free -h |
|
Ok, can you try to increase swap to 1G or create a new temporary swap like this: sudo dd if=/dev/zero of=/home/pi/temp_swap bs=1M count=1024
sudo chmod 600 /home/pi/temp_swap
sudo mkswap /home/pi/temp_swap
sudo swapon /home/pi/temp_swapThen validate that it's active with Finally you can deactivate and remove this temporary swap like this to clean up: sudo swapoff /home/pi/temp_swap
sudo rm /home/pi/temp_swap |
|
It's a good news! I followed your instructions and it works, I tested it twice. Now I need to increase the SWAP permanently on the BTT Pi. Does anyone know how to do this? I know how to do it on Raspberry, but here it seems different. |
|
I may have spoken too soon, 2 other failures :( |
|
log with the 1.5Go swap and test failed |
|
I'm abroad, I will be able to test in appr. 1 week. |
It could be that the RAM wasn't cleared or the SWAP was already full. I discovered that the OS cache objects in RAM when writing them to the disk, which can gradually increase its usage.
Haha, I got you covered in my last commit to this branch. In fact, that's exactly why I wanted you to try the swap command manually: there's now a new setting in # temporary_swap_size: 0
# This allows to specify the size in MB of an additional temporary swap file that will be dynamically
# created on the system to avoid running out of memory. This should help mitigating Klipper Timer
# Too Close errors that can occur on low-end devices with little RAM like the CB1 when processing
# large measurements. If you want to use this setting, be sure to have enough disk space available
# in your home folder, and a value like 512 or 1024 (MB) should be enough in most cases.To get this up and running, you'll also need to run an additional install script called 'install_swap_access.sh' from the root folder of Shake&Tune to get access to this feature. It'll add a special sudoers.d file that'll let your user run the few swap management commands required (just those commands, so it's pretty safe) without root password from within Shake&Tune directly. Just so you know, this script will be run automatically as part of the installation process on new installations. However, for existing users who want to use this new feature, they will need to run it once manually and reboot the Pi. |
|
Hello, I tested the last ttc-fix branch today. The first run works, I relaunched once and result error Timer too close |
|
Hi @Frix-x, |
|
I was having the MCU shutdown: Timer too close errors as well and ran across this article. I shutdown the service mentioned and have not had the error since. I do use klipperscreen, for those that do, this may help: https://klipper.discourse.group/t/recent-klipperscreen-commits-break-klipper-on-buster/5370 |
|
Hello everybody, I got a lot of positive feedback from the testers and apparently it runs much better now for most people. Even those with the problematic CB1 when properly cooled! Also, I discussed with @zavax using PMs and he was able to run it multiple times but still sometimes with TTC errors when run immediately after. So at the moment it's not clear if it's still a S&T issue or something else for him... But the good thing is that he managed to get a graph now, whereas he couldn't get it even once in the previous version. @pylorak it's very strange because on your side I can't link the TTC error to anything specific during the run: everything looks normal as we can see on the following graph (chunk at 2)... So I'm not sure if it's S&T related or something else. Can you take a look at akashrpatel's suggestion?
Actually, I thought there were more and more reports of this since the "bulk sensor" mechanism was merged into Klipper, but it also collides with this Klipperscreen update. So it might be due to that as well and it's a good thing to check! |
|
Hello @Frix-x, The only clue I have right now is that belt comparison and axis shaper run perfectly fine without any TTC. Only the vibrations profile (CREATE_VIBRATIONS_PROFILE) has the problem. How is collecting the data for the vibrations profile different from the other S&T commands? I still hypothesize that the cause of the problem lies in that difference somewhere. Let me know if you need me to do any experiments, or any other way I can help figure this out.
Is it possible that users who report success with the latest code are not testing CREATE_VIBRATIONS_PROFILE? Because AXES_SHAPER_CALIBRATION for example works for me too. The problem is with CREATE_VIBRATIONS_PROFILE. |
|
@Frix-x : Sorry for getting back to you this late, had a lot of work and some unrelated failures on my V0. Now I had time to fix the machine and updated to the latest ttx-fix version. Out of 10 runs, I had one TTC shutdown, but that could be anything. In checking the logs I couldn't find any real peaks for the memory. I'll keep an eye on this and try to check out newer versions of the TTC-Fix branch. If I find any problems, I'll report back. Thanks again for your great work on this project! Best regards, |
|
@lord-of-shred and others who report success with the latest code.
If you weren't before, please test CREATE_VIBRATIONS_PROFILE. |
Sorry, hadn't had my coffee yet.
I had one run of the CREATE_VIBRATIONS_PROFILE with chunk size 5. |
|
@lord-of-shred i tested AXES_SHAPER_CALIBRATION |
|
Hello everyone, Just to let you know: I've moved the recent temporary swap file addition to its own branch, The first steps of the |
|
Hi @Frix-x, I have been running into this issue as well, do you need any additional testers? I see that the ttc-fix branch was merged to develop, I am seeing TTC errors on the main branch every other run so I'd be willing to try develop and report back my results here. |
|
Hello @aeleos ! |
|
Hi @Frix-x I have tested both the develop and swap-hack branches and had issues with both. On the develop branch, I am still seeing timer too close errors, I don't see any major difference between the main branch and develop. For the swap-hack branch, I made sure to run the install script and I see the file created in /etc/sudoers.d. I made sure to reboot, however I am getting an error that seems that one of the commands is still prompting for the sudo password. This is the error
I took a look at the swap_manager.py file, it seems that the error is related to the fact that you are running Edit: I am currently testing running with the swap enabled, I will report back if that improved anything. |
|
Got a crash here on develop branch. well, it at least has a chance of completion now i guess
|
|
I experienced the same issue also during probing/homing (QGL/meshing), where almost every print would trigger an 'MCU timer too close' error. After removing the configuration for Shaketune, I can finally print smoothly and without any issues! :) |
K-Shake&Tune module branch
Version
v4.0.1-0-g69ad2283
Describe the bug and expected behavior
i belive problem appeared after first axis check
``
BatchBulkHelper batch callback error
Traceback (most recent call last):
File "/home/klipper/klipper/klippy/mcu.py", line 71, in _do_send
return xh.get_response(cmds, self._cmd_queue, minclock, reqclock)
File "/home/klipper/klipper/klippy/serialhdl.py", line 327, in get_response
raise error("Unable to obtain '%s' response" % (self.name,))
serialhdl.error: Unable to obtain 'sensor_bulk_status' response
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/klipper/klipper/klippy/extras/bulk_sensor.py", line 72, in _proc_batch
msg = self.batch_cb(eventtime)
File "/home/klipper/klipper/klippy/extras/adxl345.py", line 294, in _process_batch
samples = self.ffreader.pull_samples()
File "/home/klipper/klipper/klippy/extras/bulk_sensor.py", line 270, in pull_samples
self._update_clock()
File "/home/klipper/klipper/klippy/extras/bulk_sensor.py", line 242, in _update_clock
params = self.query_status_cmd.send([self.oid])
File "/home/klipper/klipper/klippy/mcu.py", line 75, in send
return self._do_send([self._cmd.encode(data)], minclock, reqclock)
File "/home/klipper/klipper/klippy/mcu.py", line 73, in _do_send
raise self._error(str(e))
gcode.CommandError: Unable to obtain 'sensor_bulk_status' response
BatchBulkHelper stop callback error
Traceback (most recent call last):
File "/home/klipper/klipper/klippy/mcu.py", line 71, in _do_send
return xh.get_response(cmds, self._cmd_queue, minclock, reqclock)
File "/home/klipper/klipper/klippy/serialhdl.py", line 327, in get_response
raise error("Unable to obtain '%s' response" % (self.name,))
serialhdl.error: Unable to obtain 'sensor_bulk_status' response
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/klipper/klipper/klippy/extras/bulk_sensor.py", line 72, in _proc_batch
msg = self.batch_cb(eventtime)
File "/home/klipper/klipper/klippy/extras/adxl345.py", line 294, in _process_batch
samples = self.ffreader.pull_samples()
File "/home/klipper/klipper/klippy/extras/bulk_sensor.py", line 270, in pull_samples
self._update_clock()
File "/home/klipper/klipper/klippy/extras/bulk_sensor.py", line 242, in _update_clock
params = self.query_status_cmd.send([self.oid])
File "/home/klipper/klipper/klippy/mcu.py", line 75, in send
return self._do_send([self._cmd.encode(data)], minclock, reqclock)
File "/home/klipper/klipper/klippy/mcu.py", line 73, in _do_send
raise self._error(str(e))
gcode.CommandError: Unable to obtain 'sensor_bulk_status' response
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/klipper/klipper/klippy/mcu.py", line 71, in _do_send
return xh.get_response(cmds, self._cmd_queue, minclock, reqclock)
File "/home/klipper/klipper/klippy/serialhdl.py", line 327, in get_response
raise error("Unable to obtain '%s' response" % (self.name,))
serialhdl.error: Unable to obtain 'spi_transfer_response' response
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/klipper/klipper/klippy/extras/bulk_sensor.py", line 62, in _stop
self.stop_cb()
File "/home/klipper/klipper/klippy/extras/adxl345.py", line 289, in _finish_measurements
self.set_reg(REG_POWER_CTL, 0x00)
File "/home/klipper/klipper/klippy/extras/adxl345.py", line 232, in set_reg
stored_val = self.read_reg(reg)
File "/home/klipper/klipper/klippy/extras/adxl345.py", line 227, in read_reg
params = self.spi.spi_transfer([reg | REG_MOD_READ, 0x00])
File "/home/klipper/klipper/klippy/extras/bus.py", line 98, in spi_transfer
return self.spi_transfer_cmd.send([self.oid, data],
File "/home/klipper/klipper/klippy/mcu.py", line 75, in send
return self._do_send([self._cmd.encode(data)], minclock, reqclock)
File "/home/klipper/klipper/klippy/mcu.py", line 73, in _do_send
raise self._error(str(e))
``
after that i decided to run test again, but new error appeared. idk if thats related
`Internal error on command:"_COMPARE_BELTS_RESPONSES"
Traceback (most recent call last):
File "/home/klipper/klipper/klippy/gcode.py", line 211, in _process_commands
handler(gcmd)
File "/home/klipper/klipper/klippy/gcode.py", line 137, in
func = lambda params: origfunc(self._get_extended_params(params))
File "/home/klipper/klipper/klippy/extras/shaketune/shaketune.py", line 148, in cmd_COMPARE_BELTS_RESPONSES
compare_belts_responses(gcmd, self._pconfig, st_process)
File "/home/klipper/klipper/klippy/extras/shaketune/commands/compare_belts_responses.py", line 105, in compare_belts_responses
vibrate_axis(toolhead, gcode, config['direction'], min_freq, max_freq, hz_per_sec, accel_per_hz)
File "/home/klipper/klipper/klippy/extras/shaketune/helpers/resonance_test.py", line 48, in vibrate_axis
toolhead.move([X, Y, Z, E], max_v)
File "/home/klipper/klipper/klippy/toolhead.py", line 473, in move
self.lookahead.add_move(move)
File "/home/klipper/klipper/klippy/toolhead.py", line 187, in add_move
self.flush(lazy=True)
File "/home/klipper/klipper/klippy/toolhead.py", line 176, in flush
self.toolhead._process_moves(queue[:flush_count])
File "/home/klipper/klipper/klippy/toolhead.py", line 362, in _process_moves
self._advance_move_time(next_move_time)
File "/home/klipper/klipper/klippy/toolhead.py", line 320, in _advance_move_time
self._advance_flush_time(flush_time)
File "/home/klipper/klipper/klippy/toolhead.py", line 300, in _advance_flush_time
sg(sg_flush_time)
File "/home/klipper/klipper/klippy/stepper.py", line 228, in generate_steps
raise error("Internal error in stepcompress")
stepper.error: Internal error in stepcompress
Internal error on command:"_COMPARE_BELTS_RESPONSES"
Internal error on command:"COMPARE_BELTS_RESPONSES"
Traceback (most recent call last):
File "/home/klipper/klipper/klippy/gcode.py", line 211, in _process_commands
handler(gcmd)
File "/home/klipper/klipper/klippy/gcode.py", line 137, in
func = lambda params: origfunc(self._get_extended_params(params))
File "/home/klipper/klipper/klippy/extras/gcode_macro.py", line 189, in cmd
self.template.run_gcode_from_command(kwparams)
File "/home/klipper/klipper/klippy/extras/gcode_macro.py", line 68, in run_gcode_from_command
self.gcode.run_script_from_command(self.render(context))
File "/home/klipper/klipper/klippy/gcode.py", line 226, in run_script_from_command
self._process_commands(script.split('\n'), need_ack=False)
File "/home/klipper/klipper/klippy/gcode.py", line 211, in _process_commands
handler(gcmd)
File "/home/klipper/klipper/klippy/gcode.py", line 137, in
func = lambda params: origfunc(self._get_extended_params(params))
File "/home/klipper/klipper/klippy/extras/shaketune/shaketune.py", line 148, in cmd_COMPARE_BELTS_RESPONSES
compare_belts_responses(gcmd, self._pconfig, st_process)
File "/home/klipper/klipper/klippy/extras/shaketune/commands/compare_belts_responses.py", line 105, in compare_belts_responses
vibrate_axis(toolhead, gcode, config['direction'], min_freq, max_freq, hz_per_sec, accel_per_hz)
File "/home/klipper/klipper/klippy/extras/shaketune/helpers/resonance_test.py", line 48, in vibrate_axis
toolhead.move([X, Y, Z, E], max_v)
File "/home/klipper/klipper/klippy/toolhead.py", line 473, in move
self.lookahead.add_move(move)
File "/home/klipper/klipper/klippy/toolhead.py", line 187, in add_move
self.flush(lazy=True)
File "/home/klipper/klipper/klippy/toolhead.py", line 176, in flush
self.toolhead._process_moves(queue[:flush_count])
File "/home/klipper/klipper/klippy/toolhead.py", line 362, in _process_moves
self._advance_move_time(next_move_time)
File "/home/klipper/klipper/klippy/toolhead.py", line 320, in _advance_move_time
self._advance_flush_time(flush_time)
File "/home/klipper/klipper/klippy/toolhead.py", line 300, in _advance_flush_time
sg(sg_flush_time)
File "/home/klipper/klipper/klippy/stepper.py", line 228, in generate_steps
raise error("Internal error in stepcompress")
stepper.error: Internal error in stepcompress
Internal error on command:"COMPARE_BELTS_RESPONSES"
Internal Error on WebRequest: gcode/script
Traceback (most recent call last):
File "/home/klipper/klipper/klippy/webhooks.py", line 256, in _process_request
func(web_request)
File "/home/klipper/klipper/klippy/webhooks.py", line 436, in _handle_script
self.gcode.run_script(web_request.get_str('script'))
File "/home/klipper/klipper/klippy/gcode.py", line 229, in run_script
self._process_commands(script.split('\n'), need_ack=False)
File "/home/klipper/klipper/klippy/gcode.py", line 211, in _process_commands
handler(gcmd)
File "/home/klipper/klipper/klippy/gcode.py", line 137, in
func = lambda params: origfunc(self._get_extended_params(params))
File "/home/klipper/klipper/klippy/extras/gcode_macro.py", line 189, in cmd
self.template.run_gcode_from_command(kwparams)
File "/home/klipper/klipper/klippy/extras/gcode_macro.py", line 68, in run_gcode_from_command
self.gcode.run_script_from_command(self.render(context))
File "/home/klipper/klipper/klippy/gcode.py", line 226, in run_script_from_command
self._process_commands(script.split('\n'), need_ack=False)
File "/home/klipper/klipper/klippy/gcode.py", line 211, in _process_commands
handler(gcmd)
File "/home/klipper/klipper/klippy/gcode.py", line 137, in
func = lambda params: origfunc(self._get_extended_params(params))
File "/home/klipper/klipper/klippy/extras/shaketune/shaketune.py", line 148, in cmd_COMPARE_BELTS_RESPONSES
compare_belts_responses(gcmd, self._pconfig, st_process)
File "/home/klipper/klipper/klippy/extras/shaketune/commands/compare_belts_responses.py", line 105, in compare_belts_responses
vibrate_axis(toolhead, gcode, config['direction'], min_freq, max_freq, hz_per_sec, accel_per_hz)
File "/home/klipper/klipper/klippy/extras/shaketune/helpers/resonance_test.py", line 48, in vibrate_axis
toolhead.move([X, Y, Z, E], max_v)
File "/home/klipper/klipper/klippy/toolhead.py", line 473, in move
self.lookahead.add_move(move)
File "/home/klipper/klipper/klippy/toolhead.py", line 187, in add_move
self.flush(lazy=True)
File "/home/klipper/klipper/klippy/toolhead.py", line 176, in flush
self.toolhead._process_moves(queue[:flush_count])
File "/home/klipper/klipper/klippy/toolhead.py", line 362, in _process_moves
self._advance_move_time(next_move_time)
File "/home/klipper/klipper/klippy/toolhead.py", line 320, in _advance_move_time
self._advance_flush_time(flush_time)
File "/home/klipper/klipper/klippy/toolhead.py", line 300, in _advance_flush_time
sg(sg_flush_time)
File "/home/klipper/klipper/klippy/stepper.py", line 228, in generate_steps
raise error("Internal error in stepcompress")
stepper.error: Internal error in stepcompress
Stats 96145.0: gcodein=0 mcu: mcu_awake=0.117 mcu_task_avg=0.000005 mcu_task_stddev=0.000003 bytes_write=155027 bytes_read=57210 bytes_retransmit=0 bytes_invalid=0 send_seq=4091 receive_seq=4091 retransmit_seq=0 srtt=0.002 rttvar=0.000 rto=0.025 ready_bytes=17 upcoming_bytes=0 freq=168003344 TH0: mcu_awake=0.773 mcu_task_avg=0.000028 mcu_task_stddev=0.000030 bytes_write=10084 bytes_read=549769 bytes_retransmit=0 bytes_invalid=52 send_seq=984 receive_seq=984 retransmit_seq=0 srtt=0.001 rttvar=0.001 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=12000117 adj=11999778 TH1: mcu_awake=0.002 mcu_task_avg=0.000012 mcu_task_stddev=0.000019 bytes_write=1863 bytes_read=12075 bytes_retransmit=0 bytes_invalid=0 send_seq=224 receive_seq=224 retransmit_seq=0 srtt=0.002 rttvar=0.001 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=12000165 adj=12000114 TH2: mcu_awake=0.002 mcu_task_avg=0.000011 mcu_task_stddev=0.000010 bytes_write=1887 bytes_read=12059 bytes_retransmit=0 bytes_invalid=0 send_seq=225 receive_seq=225 retransmit_seq=0 srtt=0.002 rttvar=0.001 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=64000435 adj=63998482 Arduino_MEGA: mcu_awake=0.068 mcu_task_avg=0.000216 mcu_task_stddev=0.000086 bytes_write=1815 bytes_read=50172 bytes_retransmit=9 bytes_invalid=6 send_seq=189 receive_seq=189 retransmit_seq=2 srtt=0.004 rttvar=0.001 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=15882018 adj=15881628 TH0_temp: temp=36.3 TH1_temp: temp=37.1 TH2_temp: temp=37.8 OrangePi_temp: temp=53.5 Driver_Z0: temp=42.4 Driver_Z1: temp=57.8 Driver_Z2: temp=63.4 Driver_Z3: temp=57.4 Driver_A: temp=56.5 Driver_B: temp=54.4 Motor_Z0: temp=42.9 Motor_Z1: temp=49.6 Motor_Z2: temp=38.6 Motor_Z3: temp=46.4 chamber: temp=31.2 heater_bed: target=60 temp=60.1 pwm=0.206 sysload=0.86 cputime=249.610 memavail=382288 print_time=73.119 buffer_time=2.310 print_stall=0 extruder: target=150 temp=149.5 pwm=0.316 extruder1: target=0 temp=30.2 pwm=0.000 extruder2: target=0 temp=28.9 pwm=0.000
BatchBulkHelper batch callback error
Traceback (most recent call last):
File "/home/klipper/klipper/klippy/mcu.py", line 71, in _do_send
return xh.get_response(cmds, self._cmd_queue, minclock, reqclock)
File "/home/klipper/klipper/klippy/serialhdl.py", line 327, in get_response
raise error("Unable to obtain '%s' response" % (self.name,))
serialhdl.error: Unable to obtain 'sensor_bulk_status' response
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/klipper/klipper/klippy/extras/bulk_sensor.py", line 72, in _proc_batch
msg = self.batch_cb(eventtime)
File "/home/klipper/klipper/klippy/extras/adxl345.py", line 294, in _process_batch
samples = self.ffreader.pull_samples()
File "/home/klipper/klipper/klippy/extras/bulk_sensor.py", line 270, in pull_samples
self._update_clock()
File "/home/klipper/klipper/klippy/extras/bulk_sensor.py", line 242, in _update_clock
params = self.query_status_cmd.send([self.oid])
File "/home/klipper/klipper/klippy/mcu.py", line 75, in send
return self._do_send([self._cmd.encode(data)], minclock, reqclock)
File "/home/klipper/klipper/klippy/mcu.py", line 73, in _do_send
raise self._error(str(e))
gcode.CommandError: Unable to obtain 'sensor_bulk_status' response
BatchBulkHelper stop callback error
Traceback (most recent call last):
File "/home/klipper/klipper/klippy/mcu.py", line 71, in _do_send
return xh.get_response(cmds, self._cmd_queue, minclock, reqclock)
File "/home/klipper/klipper/klippy/serialhdl.py", line 327, in get_response
raise error("Unable to obtain '%s' response" % (self.name,))
serialhdl.error: Unable to obtain 'sensor_bulk_status' response
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/klipper/klipper/klippy/extras/bulk_sensor.py", line 72, in _proc_batch
msg = self.batch_cb(eventtime)
File "/home/klipper/klipper/klippy/extras/adxl345.py", line 294, in _process_batch
samples = self.ffreader.pull_samples()
File "/home/klipper/klipper/klippy/extras/bulk_sensor.py", line 270, in pull_samples
self._update_clock()
File "/home/klipper/klipper/klippy/extras/bulk_sensor.py", line 242, in _update_clock
params = self.query_status_cmd.send([self.oid])
File "/home/klipper/klipper/klippy/mcu.py", line 75, in send
return self._do_send([self._cmd.encode(data)], minclock, reqclock)
File "/home/klipper/klipper/klippy/mcu.py", line 73, in _do_send
raise self._error(str(e))
gcode.CommandError: Unable to obtain 'sensor_bulk_status' response
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/klipper/klipper/klippy/mcu.py", line 71, in _do_send
return xh.get_response(cmds, self._cmd_queue, minclock, reqclock)
File "/home/klipper/klipper/klippy/serialhdl.py", line 327, in get_response
raise error("Unable to obtain '%s' response" % (self.name,))
serialhdl.error: Unable to obtain 'spi_transfer_response' response
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/klipper/klipper/klippy/extras/bulk_sensor.py", line 62, in _stop
self.stop_cb()
File "/home/klipper/klipper/klippy/extras/adxl345.py", line 289, in _finish_measurements
self.set_reg(REG_POWER_CTL, 0x00)
File "/home/klipper/klipper/klippy/extras/adxl345.py", line 232, in set_reg
stored_val = self.read_reg(reg)
File "/home/klipper/klipper/klippy/extras/adxl345.py", line 227, in read_reg
params = self.spi.spi_transfer([reg | REG_MOD_READ, 0x00])
File "/home/klipper/klipper/klippy/extras/bus.py", line 98, in spi_transfer
return self.spi_transfer_cmd.send([self.oid, data],
File "/home/klipper/klipper/klippy/mcu.py", line 75, in send
return self._do_send([self._cmd.encode(data)], minclock, reqclock)
File "/home/klipper/klipper/klippy/mcu.py", line 73, in _do_send
raise self._error(str(e))
gcode.CommandError: Unable to obtain 'spi_transfer_response' response
Stats 96146.0: gcodein=0 mcu: mcu_awake=0.117 mcu_task_avg=0.000005 mcu_task_stddev=0.000003 bytes_write=155192 bytes_read=57477 bytes_retransmit=0 bytes_invalid=0 send_seq=4098 receive_seq=4098 retransmit_seq=0 srtt=0.001 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=168003292 TH0: mcu_awake=0.773 mcu_task_avg=0.000028 mcu_task_stddev=0.000030 bytes_write=10180 bytes_read=549991 bytes_retransmit=0 bytes_invalid=52 send_seq=994 receive_seq=994 retransmit_seq=0 srtt=0.001 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=12000118 adj=11999845 TH1: mcu_awake=0.002 mcu_task_avg=0.000012 mcu_task_stddev=0.000019 bytes_write=1869 bytes_read=12207 bytes_retransmit=0 bytes_invalid=0 send_seq=225 receive_seq=225 retransmit_seq=0 srtt=0.001 rttvar=0.001 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=12000159 adj=12000072 TH2: mcu_awake=0.002 mcu_task_avg=0.000011 mcu_task_stddev=0.000010 bytes_write=1893 bytes_read=12191 bytes_retransmit=0 bytes_invalid=0 send_seq=226 receive_seq=226 retransmit_seq=0 srtt=0.002 rttvar=0.001 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=64000440 adj=63998868 Arduino_MEGA: mcu_awake=0.068 mcu_task_avg=0.000216 mcu_task_stddev=0.000086 bytes_write=1821 bytes_read=50860 bytes_retransmit=9 bytes_invalid=6 send_seq=190 receive_seq=190 retransmit_seq=2 srtt=0.004 rttvar=0.001 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=15882018 adj=15881703 TH0_temp: temp=35.9 TH1_temp: temp=37.3 TH2_temp: temp=37.7 OrangePi_temp: temp=54.5 Driver_Z0: temp=42.1 Driver_Z1: temp=57.4 Driver_Z2: temp=61.4 Driver_Z3: temp=55.9 Driver_A: temp=54.6 Driver_B: temp=53.3 Motor_Z0: temp=43.2 Motor_Z1: temp=49.7 Motor_Z2: temp=38.2 Motor_Z3: temp=46.6 chamber: temp=31.2 heater_bed: target=60 temp=60.0 pwm=0.000 sysload=0.86 cputime=249.774 memavail=375532 print_time=73.119 buffer_time=1.310 print_stall=0 extruder: target=150 temp=148.5 pwm=0.000 extruder1: target=0 temp=30.5 pwm=0.000 extruder2: target=0 temp=28.9 pwm=0.000
b'stepcompress o=13 i=0 c=6 a=0: Invalid sequence'
Exception in flush_handler
Traceback (most recent call last):
File "/home/klipper/klipper/klippy/toolhead.py", line 435, in _flush_handler
self._flush_lookahead()
File "/home/klipper/klipper/klippy/toolhead.py", line 365, in _flush_lookahead
self.lookahead.flush()
File "/home/klipper/klipper/klippy/toolhead.py", line 176, in flush
self.toolhead._process_moves(queue[:flush_count])
File "/home/klipper/klipper/klippy/toolhead.py", line 362, in _process_moves
self._advance_move_time(next_move_time)
File "/home/klipper/klipper/klippy/toolhead.py", line 320, in _advance_move_time
self._advance_flush_time(flush_time)
File "/home/klipper/klipper/klippy/toolhead.py", line 300, in _advance_flush_time
sg(sg_flush_time)
File "/home/klipper/klipper/klippy/stepper.py", line 228, in generate_steps
raise error("Internal error in stepcompress")`
Additional information and klippy.log
No response
The text was updated successfully, but these errors were encountered: