And this leads to the final:
QuoteJan 02 00:36:34 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:36:34,563 INFO waitForHeatableObjectsStep Waiting for hotend-0 heatup: 33.8/190.0 (wait_tolerance: 0.0)
Jan 02 00:36:39 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:36:39,576 INFO waitForHeatableObjectsStep Waiting for hotend-0 heatup: 33.8/190.0 (wait_tolerance: 0.0)
Jan 02 00:36:44 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:36:44,593 INFO waitForHeatableObjectsStep Waiting for hotend-0 heatup: 33.8/190.0 (wait_tolerance: 0.0)
Jan 02 00:36:49 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:36:49,606 INFO waitForHeatableObjectsStep Waiting for hotend-0 heatup: 33.8/190.0 (wait_tolerance: 0.0)
Jan 02 00:36:49 ultimakersystem-ccbdd30008a5 python3[196]: 1970-01-02 00:36:49,921 WARNING systemUpdate Error during updating of the update version strings for release type 'stable'
Jan 02 00:36:49 ultimakersystem-ccbdd30008a5 python3[196]: 1970-01-02 00:36:49,924 INFO systemService Could not load/check whether there is a new firmware version for 'stable'
Jan 02 00:36:49 ultimakersystem-ccbdd30008a5 python3[196]: 1970-01-02 00:36:49,931 WARNING systemUpdate Error during updating of the update version strings for release type 'testing'
Jan 02 00:36:54 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:36:54,620 INFO waitForHeatableObjectsStep Waiting for hotend-0 heatup: 33.8/190.0 (wait_tolerance: 0.0)
Jan 02 00:36:59 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:36:59,637 INFO waitForHeatableObjectsStep Waiting for hotend-0 heatup: 33.8/190.0 (wait_tolerance: 0.0)
Jan 02 00:37:02 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:37:02,738 WARNING procedureStep WaitForHotendTemperatureStep("SET_HOTEND_TEMPERATURE_WAIT") takes too long too run, over 600 seconds
Jan 02 00:37:02 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:37:02,743 INFO faultHandler critical(<class 'griffin.printer.faultHandler.FaultHandler'>, Waiting for hotend temperature is taking too long, 41, {'display_hotend_nr': 1})
Jan 02 00:37:02 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:37:02,772 CRITICAL faultHandler added Fault: L:CRITICAL C:HOTEND_TEMPERATURE_TIMEOUT M:Waiting for hotend temperature is taking too long
Jan 02 00:37:02 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:37:02,774 INFO procedure Message: 'ABORT' for procedure 'PrintProcedure(key='PRINT')'
Jan 02 00:37:02 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:37:02,780 INFO procedure Abort message received for procedure PrintProcedure(key='PRINT')
Jan 02 00:37:02 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:37:02,782 INFO procedure Pass abort to PRINTING
Jan 02 00:37:02 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:37:02,783 INFO procedureStep Aborting step: PrintFileStep(key='PRINTING')
Jan 02 00:37:02 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:37:02,786 INFO printerStateProperty State change: printing -> error
More cooling down is being detected, and then the Opinicus notices it takes too long to heat up the hotend and giving the final error.
But all of this is because of a reboot of Marlin due to some power fluctuation.
If you say you have used the normal UM PrintCores, I'd advise buying a cheap UPS and make sure to use a grounded socket.
Not sure how your situation at home is, but if you have attached the printer's powerbrick onto the same subnet as for example big power users (fridge, oven, microwave, dishwasher) those might kick in at some point causing the powerfluctuation which leads to the brick getting into problems.
Changing to a different subnet and/or using an UPS might save the day.
Recommended Posts
Top Posters In This Topic
11
10
7
6
Popular Days
Sep 2
9
May 9
9
Jul 18
7
Apr 17
5
Top Posters In This Topic
le_avion 11 posts
The_Rob 10 posts
kmanstudios 7 posts
tomnagel 6 posts
Popular Days
Sep 2 2018
9 posts
May 9 2018
9 posts
Jul 18 2017
7 posts
Apr 17 2018
5 posts
Popular Posts
Marco_TvM
I noticed the following problem: Basically this tells me the hotend is found to be removed... Since this is not the actual case, it comes down to bad connection (cable) as said by @fbrc8-erin a
kmanstudios
Then your service provider made a bad mistake. For instance, I had this problem with my first UM3E. Second one is just fine. But, I reported it here and @fbrc8-erin sent me a brand new cable out faste
gr5
Even if it's "out of warranty" there's a good chance they will still honor the warranty. Especially since the problems started before the warranty ran out. Since you are in the USA I recommend going
Posted Images
Marco_TvM 34
Next more interesting stuff happens, but related to the previous issue:
We see that Opinicus thinks that a cold extrusion was prevented (due to lack of heating up) and following with another command to heat up hotend 0. This is however not happening: you can see it cooling down.
Link to post
Share on other sites