lost of conenction with mcu?
VC 500 -corexy - during my two first true rpint , I got twice the same behavior after soem time I got a mcu lost coennction?Any idea what's the possible reason? Adding note I use a rpi4 with a dedicacte raspbery certified power supply and it 's conenct trhough usb
5 Replies
her ethe last line of the klipep rlog I do'nt see somethign particular: mcu_task_avg=0.000039 mcu_task_stddev=0.000042 bytes_write=22581855 bytes_read=5344297 bytes_retransmit=43 bytes_invalid=0 send_seq=428732 receive_seq=428731 retransmit_seq=428732 srtt=0.000 rttvar=0.000 rto=0.100 ready_bytes=0 upcoming_bytes=2774 freq=63999644 adj=63999846 Octopus_V1.1_F446: temp=31.5 EBB42_v1.2_T0: temp=31.6 raspberry_pi: temp=28.7 heater_bed: target=60 temp=45.4 pwm=0.000 beacon: mcu_awake=0.000 mcu_task_avg=0.000000 mcu_task_stddev=0.000000 bytes_write=190231 bytes_read=8527112 bytes_retransmit=0 bytes_invalid=0 send_seq=27315 receive_seq=27315 retransmit_seq=0 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=31999469 adj=31999560 coil_temp=30.2 refs=0 mcu_temp=32.48 supply_voltage=3.027 sysload=0.23 cputime=10789.510 memavail=3263140 print_time=21822.213 buffer_time=0.000 print_stall=0 extruder: target=220 temp=220.4 pwm=0.357
Double check your usb cable to the toolhead, make sure it is well zip-tied in place.
Mr Pomme I also have a 500 and kept randomly getting this even though I had put 4 zip ties and tightened them as much as I dared. The usb cable provided in the kit has a fair bit of extra slack that I had tucked in the electronics enclosure. I ended up pulling about 2-3 inches of slack out of the enclosure and worked it up close the hotend. I then used it to make a small half loop that is sticking out of the sheathing. I then put a zip tie above and below that half loop and have not had the issue since. It is very frustrating, and this was the only thing that worked for me.
I think I will add some hotglue into the conenctors perhaps it sjould help 😄
hors perhaps it's a fuckign bad idea 😄