[Errno 16] Device or resource busy 'devbtt-octopus-11'
The last three prints have failed with this error, the MCU becomes unavailable.
Nothing has changed hardware wise. I made sure the RPi is connected though it's own power source (5V 20W) when it happened the first time. Also the RPi is sitting at it's lazy back all the time with 10 - 15% CPU usage and 30% RAM.
The only difference is that now I am printing PLA. But I can't imagine a connection, bed and extrusion temps are lower.
RPi temp: 48°C, Toolboard 33°C, Octopus 37°C.
What should I look for?
8 Replies
sounds like the PI is waiting on something. Seems unlikely that it is waiting on the octopus. What kind of SD card are you using?
noble-gold•2y ago
it's a CM4, using eMMC
also I had like 40 prints in this configuration already.
oh there is something I made different, but I can't imagine how that would be the cause: this happens since I started printing PLA earlier today. Because it's old and not very good I experimented with some settings, for example raised acceleration ( within the bounds of input shaping recommendations to 6000) from 4000.
noble-gold•2y ago
oh, terminal says:
noble-gold•2y ago
noble-gold•2y ago
hm, now I am getting "Communication timeout during homing x"
happened again after disconnecting webcam and touchscreen to be sure:
receive_seq=14640 retransmit_seq=0 srtt=0.001 rttvar=0.000 rto=0.025 ready_bytes=0 stalled_bytes=1950 freq=63999199 adj=63999461 Octopus: temp=36.3 raspberry_pi: temp=46.7 heater_bed: target=65 temp=64.7 pwm=0.476 toolboard: temp=31.8 sysload=0.17 cputime=90.505 memavail=681196 print_time=2260.980 buffer_time=1.299 print_stall=0 extruder: target=238 temp=237.9 pwm=0.428
b'stepcompress o=8 i=0 c=3 a=0: Invalid sequence'
Exception in flush_handler
Traceback (most recent call last):
File "/home/pi/klipper/klippy/toolhead.py", line 393, in _flush_handler
self.flush_step_generation()
File "/home/pi/klipper/klippy/toolhead.py", line 338, in flush_step_generation
self.move_queue.flush()
File "/home/pi/klipper/klippy/toolhead.py", line 176, in flush
self.toolhead._process_moves(queue[:flush_count])
File "/home/pi/klipper/klippy/toolhead.py", line 334, in _process_moves
self._update_move_time(next_move_time)
File "/home/pi/klipper/klippy/toolhead.py", line 287, in _update_move_time
sg(sg_flush_time)
File "/home/pi/klipper/klippy/stepper.py", line 226, in generate_steps
raise error("Internal error in stepcompress")
stepper.error: Internal error in stepcompress
Stats 1544.6: gcodein=0 mcu: mcu_awake=0.005 mcu_task_avg=0.000009
noble-gold•2y ago
the whole log
looking at https://klipper.discourse.group/t/error-internal-error-in-mcu-mcu-stepcompress/2702 gave me the idea to look further up until i saw:
Timeout with MCU 'toolboard' (eventtime=1542.578776) Transition to shutdown state: Lost communication with MCU 'toolboard'
Klipper
Error: Internal error in MCU 'mcu' stepcompress
Attempted to print this model on my Geeetech A10 with BMG extruder and ran into this error. I am on a pretty recent version of Klipper v0.10.0-319-g3e0c0e9c. After doing lots of googling, reading the github issues and searching this forum - I have not found a solution. My suspicion is this might be a bug? I was able to print a calibration cube w...
noble-gold•2y ago
read through that thread, thanks. seems I have to spent more time searching for hardware / connection issues