Today I’m having a hard time print a quite easy ( but 3+h long ) part.
I have tried to print 4 times, three of which ( attempt 1,2 and 4 ) resulted in error with lost communication.
It sound strange to me as I have used this printer quite a lot ( for an amateur user ) and only had those problems very rare times.
Usually whn this happened I also had notification of low voltage from the pi, so it wasn’t that unexpected.
Yesterday I’ve printed the same part with no problems, and today has gone as said before.
The real difference I’m seeing is that in previos time I had a lost communication, a simple firmware restart would fix the problem ( I mean I had to remove the part from plate, but a part this no other need ), while today the firmware retart does not work.
I have to physically shutdown the printer to make it works again.
I will add that there are no error in messages, dmesg, syslog and daemon.log.
Also removing the USB cable and reattaching does not lead to usual dmesg lines ( that you can see when an usb cable is removed and attached again ).
It almost seems that the firmware/hardware is completelly stuck.
I’ve gone through the KB but nothing seems to attach to my case.
Hello hcet14 and thanks for you reply !
Print three was the only one that ended with no issue.
I add that also print 5 failed. They all fail almost the same height.
The print 11.5cm height. Printe attempt 1,2,4,and 5 all failed between 5 and 6 cm ( but not exactly the same ) layer.
The only thing I’ve noticed is that the “bytes_retransmit” value, start to increase ( heavily ) and then I get:
Timeout with MCU 'mcu' (eventtime=8930.111857)
Transition to shutdown state: Lost communication with MCU 'mcu'
It’s not really easy to check for voltage as it happens in 1.5-2h so I have to find a way to keep history of measurement during time.
Any ideas ?
Problem is how to collect information for >1h without remaining for all time until the problems appears looking the multimeter
I’m thinking to build an esp8266 iot device with a voltage divider and to send information to homeassistant or writing to sdcard for later analyis, but probably you’re right: it could be easily to simply try to change power supply and try.
Yesterday I have completed a succesfull print without any issue.
Just before printing I have opened th electronic bay, to get a couple of wire to monitor voltage, and gived a very nice clean to everything.
The fan was very dirty with a lot of dust, so maybe the problem was the board temperature.
Worth checking in case of problems…
I took a different approach.
I took an ESP8266 and attached a voltage divider, with two resistor, and an output to the analog pin.
Few lines of code and I have sent data, via mqtt, to my homeassistant instance.
From ther is simply a matter of adding the entity and the recorder… but thank a lot !
