Conflict errors, print cores not reaching temperature

[Ellworx 2]

I am suddenly getting conflict errors and a problem whereby the print core gets very close to the start temperature but hangs up until the printer comes up with the error attached. I have reloaded software and tried everything that I think will solve the problem. Not sure they are even linked. Sometimes all I need to do is abort and then try again and it works.

 

Unrelated I think but I am also getting G-code errors when I try to open a cura project I've saved previously.

 

These issues seemed to coincide with several things. A new laptop and using digital factory.

 

I have an S5

[Jhawk6553 8]

Im guessing that either the pcb on your print core is bad or the one on your print head is bad unfortunately.

[Dadkitess 19]

Yeah that's an issue we've faced 3 times in the 3 past monthes, and it's irritating.

 

One PrintCore that was just fine, did not work with this error after reinserting in its exact same slot : we did a little machine maintenance, including the change of the front fan, nothing was disconnected or damages, it was made by the reseller. Once plugged in back, even after multiple restart of the machine, it shown this error, while a direct monitoring of the printcore actually shown a temperature reaching 280+°C. The reseller took the printcore to diagnose it, no idea of the answer it but they replaced it for free, fortunately.

 

2 weeks later, another error like this one, restart of the machine, went fine.

 

@MariMakes do you have an idea about this ? It looks like a pretty "recent" issue, hope that it won't happen more and more.

[robinmdh 100]

the only error I see is the printcore takes too long to heat up, this can be caused by:

• The heater of sensor being disconnected from the printcore.
• a weird situation where a high temperature is requested and then a only slightly higher or lower, this can take long because the heating response will be slower as it's already almost at that temperature. E.G: have the initial temperature in the gcode header file be 300 degC and then having an M109 S305 in the gcode, this can cause the watchdog for that temperature change to time out. but this is after 10 minutes of waiting.  you can fix that with Cura settings.
• a bug where a communication error happens right as the temperature is set, this can caused by be environment.
   

The 1-2 does mean it's waiting for both hotends, so i could also be that the one hotend is working fine but the other one is not?

[Ellworx 2]

I have finally sorted this problem out. Since I wasn't using core 2 at all I made the assumption that it would not be heated during the self levelling routine. Apparently the core needs to heat up to soften any plastic on the tip so that it does not give a false level (even though the core is is not being used so you wonder why this is) Replaced the faulty core 2 and all is good now. Thanks for the help.