Getting very frustrated with Ultimaker 3 Extended with long prints

[Marco_TvM 34]

Hello @The_Rob,

 

I've been looking into your latest logs, and see a lot of similarities.

Some excerpts from the log that caught my attention:

Quote

Jan 02 00:25:03 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:25:03,695 INFO     printerService  Procedure start: SET_HOTEND_TEMPERATURE_WAIT: SET_HOTEND_TEMPERATURE_WAIT
Jan 02 00:25:03 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:25:03,709 INFO     printerService  Procedure next step: SET_HOTEND_TEMPERATURE_WAIT: SET_HOTEND_TEMPERATURE_WAIT
Jan 02 00:25:03 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:25:03,723 INFO     waitForHeatableObjectsStep Setting target temperature of hotend-1 to 215C
Jan 02 00:25:03 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:25:03,730 INFO     procedure       WaitForHotendTemperatureProcedure(key='SET_HOTEND_TEMPERATURE_WAIT') transitioning from WaitForHotendTemperatureStep(key='SET_HOTEND_TEMPERATURE_WAIT') --> None
Jan 02 00:25:03 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:25:03,735 INFO     printerService  Procedure finished: SET_HOTEND_TEMPERATURE_WAIT
Jan 02 00:25:15 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:25:15,627 INFO     marlinProtocolHandler BUILD:Dec 22 2017 15:01:31
Jan 02 00:25:15 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:25:15,634 INFO     marlinProtocolHandler ADS1015 #0x48 ref.voltage=953
Jan 02 00:25:19 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:25:19,776 WARNING  marlinProtocolHandler Resend data request for sequence 0, but not found, before adjusting [MessageTuple(sequence_number=144, message='G1 X90.41 Y131.998 E17.7583', callback_function=None), MessageTuple(sequence_number=145, message='G1 X91.089 Y133.35 E17.77075', callback_function=None), MessageTuple(sequence_number=146, message='G1 X106.042 Y133.35 E17.89381', callback_function=None), MessageTuple(sequence_number=147, message='G1 X106.042 Y182.631 E18.29937', callback_function=None), MessageTuple(sequence_number=148, message='M100', callback_function=None)]
Jan 02 00:25:19 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:25:19,781 WARNING  marlinProtocolHandler Resend data request for sequence 0, but not found, after adjusting [MessageTuple(sequence_number=0, message='G1 X90.41 Y131.998 E17.7583', callback_function=None), MessageTuple(sequence_number=1, message='G1 X91.089 Y133.35 E17.77075', callback_function=None), MessageTuple(sequence_number=2, message='G1 X106.042 Y133.35 E17.89381', callback_function=None), MessageTuple(sequence_number=3, message='G1 X106.042 Y182.631 E18.29937', callback_function=None), MessageTuple(sequence_number=4, message='M100', callback_function=None)]
 

 

Here we can see the hotend started heating up, but then Marlin rebooted which indicates a short power surge/spike, just as @CarloK mentioned earlier as well. This then also causes mismatch in the communication protocol buffer between Opinicus and Marlin.

[Marco_TvM 34]

Next more interesting stuff happens, but related to the previous issue:

Quote

Jan 02 00:26:54 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:26:54,722 INFO     marlinProtocolHandler  cold extrusion prevented
Jan 02 00:26:56 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:26:56,444 INFO     marlinProtocolHandler  cold extrusion prevented
Jan 02 00:26:56 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:26:56,569 INFO     switchActiveHotendProcedure Target hotend = 0
Jan 02 00:26:56 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:26:56,572 INFO     printerService  Procedure start: SWITCH_ACTIVE_HOTEND: WAIT
Jan 02 00:26:56 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:26:56,582 INFO     printerService  Procedure next step: SWITCH_ACTIVE_HOTEND: WAIT
Jan 02 00:26:56 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:26:56,600 INFO     marlinProtocolHandler  cold extrusion prevented
Jan 02 00:26:56 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:26:56,610 INFO     marlinProtocolHandler  cold extrusion prevented
Jan 02 00:26:58 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:26:58,291 INFO     marlinProtocolHandler  cold extrusion prevented
Jan 02 00:26:58 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:26:58,497 INFO     marlinProtocolHandler  cold extrusion prevented
Jan 02 00:27:01 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:27:01,427 INFO     procedure       SwitchActiveHotendProcedure(key='SWITCH_ACTIVE_HOTEND') transitioning from WaitForQueueToBeEmptyStep(key='WAIT') --> SwitchActiveHotendStep(key='SWITCH_ACTIVE_HOTEND')
Jan 02 00:27:01 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:27:01,429 INFO     printerService  Procedure next step: SWITCH_ACTIVE_HOTEND: SWITCH_ACTIVE_HOTEND
Jan 02 00:27:02 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:27:02,689 INFO     procedure       SwitchActiveHotendProcedure(key='SWITCH_ACTIVE_HOTEND') transitioning from SwitchActiveHotendStep(key='SWITCH_ACTIVE_HOTEND') --> None
Jan 02 00:27:02 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:27:02,694 INFO     printerService  Procedure finished: SWITCH_ACTIVE_HOTEND
Jan 02 00:27:02 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:27:02,697 WARNING  materialManager No maximum temperature for material in hotend 0
Jan 02 00:27:02 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:27:02,717 INFO     printerService  Procedure start: SET_HOTEND_TEMPERATURE_WAIT: SET_HOTEND_TEMPERATURE_WAIT
Jan 02 00:27:02 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:27:02,728 INFO     printerService  Procedure next step: SET_HOTEND_TEMPERATURE_WAIT: SET_HOTEND_TEMPERATURE_WAIT
Jan 02 00:27:02 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:27:02,734 INFO     waitForHeatableObjectsStep Setting target temperature of hotend-0 to 190C
Jan 02 00:27:07 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:27:07,756 INFO     waitForHeatableObjectsStep Waiting for hotend-0 heatup: 85.0/190.0 (wait_tolerance: 0.0)
Jan 02 00:27:12 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:27:12,771 INFO     waitForHeatableObjectsStep Waiting for hotend-0 heatup: 82.7/190.0 (wait_tolerance: 0.0)
Jan 02 00:27:17 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:27:17,787 INFO     waitForHeatableObjectsStep Waiting for hotend-0 heatup: 80.5/190.0 (wait_tolerance: 0.0)
Jan 02 00:27:22 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:27:22,800 INFO     waitForHeatableObjectsStep Waiting for hotend-0 heatup: 78.4/190.0 (wait_tolerance: 0.0)
Jan 02 00:27:27 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:27:27,813 INFO     waitForHeatableObjectsStep Waiting for hotend-0 heatup: 76.4/190.0 (wait_tolerance: 0.0)
Jan 02 00:27:32 ultimakersystem-ccbdd30008a5 python3[330]: 1970-01-02 00:27:32,832 INFO     waitForHeatableObjectsStep Waiting for hotend-0 heatup: 74.5/190.0 (wait_tolerance: 0.0)

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.

 

[Marco_TvM 34]

And this leads to the final:

Quote

Jan 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.

 

[Marco_TvM 34]

Another short addendum, after talking with @CarloK:

If you can switch the brick with another printer's brick, see if the problem moves as well.

If it does, then it's unlikely an UPS will help, because then the brick seems to be on the very low end of the specifications.

 

[The_Rob 1]

This printer is running on the same power line as two more printers, only this one is getting the errors, even when they're running at the same time. They are placed in a laboratory, it is theoretically possible that there are power spikes or other fluctuations on the network, but afaik nothing else worth mentioning is connected to that subnet. (Some laptop chargers maybe)

wouldn't all the printers get the same error, if it was an issue of the outer power line?

 

Which part do you mean by brick, are you talking about the brick-like AC-adapter?

I'll try swapping those.

Edited May 9, 2018 by The_Rob

[SandervG 1,521]

28 minutes ago, The_Rob said:

Which part do you mean by brick, are you talking about the brick-like AC-adapter?

 

 

Yes, the power supply unit. The black thing between your wall and the Ultimaker ?

[The_Rob 1]

Just swapped it with another printer and started a print, I'll keep you updated on the results.

Didn't take a close look at the power supply unit for quite a while, after holding it in hand once again it's quite obviously the brick :D

[The_Rob 1]

Bad news.

Next print failed after two (?) hours again.

Another printer was running next to it, no errors there as usually.

Logs are included.

 

Do you have any other options that I can still try?

Logs3 (make it .zip).log

[tomnagel 126]

So the problem stayed with the same printer, after you switched the power supplies of 2 printers?

And you are using original Ultimaker Print Cores? Than I think you should contact your reseller. Your problem reproduces and it seems like a heater is out of specification, causing the overloaded power supply.

 

[The_Rob 1]

Yes, original printcores.

The faulty printer was still getting errors with a different brick.

Another printer was all okay, running with the faulty printers brick.

 

I'll contact iGo3D then, that's where we got all our printers.

And I hope that their service is not gonna be as bad as I heard before...

Edited May 11, 2018 by The_Rob

[Jason_k 0]

any updates on this error message.  i have had 3 prints fail consecutively with 3 different print cores, all the .4AA core. All at different times into the print, 3hrs, 8hrs and 16hrs of a 24hr print .  silicone gasket is in good condition and installed properly, just changed it about 1 month ago.  We print daily on this machine and never got the error message before these 3 last times.  attached are the logs i got after the first print.

2018-08-14 THRU 8-16.zip

[gr5 2,172]

If you are in USA then you should talk to Erin at fbrc8 ( @fbrc8-erin ).  She can fix any issue.  So what error message are you getting?  "too long to heat up"?  That one?

 

Erin would know this better but one common issue and very simple fix is that the cable at the top of the head gets half way unplugged.  Remove the two rear screws on the top of the head and the rear half of the to of the head pops off and you can re-seat the cable and shove more of the cable into the head - preferably with a shim to hold it tighter like some blue tape).

 

I took my UM3 print head apart last night for the first time (not completely but removed the top 4 screws and the side 4 screws) and there was a lot of gunk in there that I cleaned out.  You may have bad contact between the gold plated spots on the core and the gold fingers that touch it or they may need bending slightly?  I doubt this but it's a possibility.  I would use q-tips with isopropyl alcohol to clean those gold contacts both on the core and inside the head (you can get to them without taking anything apart - just slide out the core and you can see them).

[fbrc8-erin 272]

@Jason_k I agree with what @gr5 said, one of the first things to check is going to be reseating the cable, which generally helps if you're seeing an ER18 or ER19 error. 

Knowing the exact error message you're seeing would help.

Also, is your front fan running?

[CarloK 203]

@Jason_k I can't open the attached log files. There is an error with the file or it isn't a regular zip file.

[Jason_k 0]

The error message that I am seeing is "PrintCore in head slot 1 is taking too long to warm up".  All fans are running properly and all contacts are clean and straight.  I will check the cable to see if that is installed properly.

 

@CarloK My work has our zip files created at .7z as standard but the site wouldn't allow me to upload that type.  i changed extension name but that obviously didn't work.  attached is a properly created .zip file now.

2018-08-14.zip

[Jason_k 0]

I also just got a print work; I did change some things; i added a top shield to protect any cold air drafts and also switched material from PLA to TPU95 because it had a lower temp.  I need PLA for the print but I atleast did not get the error 4 times in a row

[gr5 2,172]

The core should be way over powered.  It can go to 350C easily although not recommended.  Did you remove the top of the print head?  It takes 30 seconds - remove rear two screws, remove the back half of the head.  It looks like huge section of the head might come off but it's just the top few millimeters and you can see inside and reduce the strain on the wires.

[Marco_TvM 34]

18 hours ago, Jason_k said:

The error message that I am seeing is "PrintCore in head slot 1 is taking too long to warm up".  All fans are running properly and all contacts are clean and straight.  I will check the cable to see if that is installed properly.

 

@CarloK My work has our zip files created at .7z as standard but the site wouldn't allow me to upload that type.  i changed extension name but that obviously didn't work.  attached is a properly created .zip file now.

2018-08-14.zip

 

I noticed the following problem:

Quote

Jan 01 17:16:43 ultimakersystem-ccbdd3004764 kernel: wlan0: Limiting TX power to 22 dBm as advertised by 00:42:68:bd:ea:c1
Jan 01 17:16:46 ultimakersystem-ccbdd3004764 python3[354]: 1970-01-01 17:16:46,762 INFO     hotendCartridgeManager setPresentChanged(0 is not present)
Jan 01 17:16:46 ultimakersystem-ccbdd3004764 python3[354]: 1970-01-01 17:16:46,773 INFO     hotendCartridgeManager _updateHotendGone deleting reference to hotend(0, b'\x0c\xbf]\x1e\x00\x00')
Jan 01 17:16:46 ultimakersystem-ccbdd3004764 python3[354]: 1970-01-01 17:16:46,797 INFO     heatableHotend  setting default on pid_Kp
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: 1970-01-01 17:16:48,163 INFO     hotendCartridgeManager setPresentChanged(0 is present)
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: 1970-01-01 17:16:48,192 INFO     heatableHotend  setting default on pid_Ki
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: 1970-01-01 17:16:48,230 INFO     heatableHotend  setting default on pid_Kd
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 flipflop_wsgi.py[405]: 17:16:48 - WAR - app.libs.printer_api:145 - Failed to fetch system info for printer at http://10.66.60.24/api/v1
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 flipflop_wsgi.py[405]: 17:16:48 - WAR - app.models.printer:259 - Unable to contact printer Printer(unique_name=ultimakersystem-ccbdd3004764, friendly_name=NPDUltimaker3Ext, uuid=d58932db-d52e-42f6-a597-5a6fd9cd6da9, enabled=True, reserved_by=None, status=unreachable, authenticated=True) at IP 10.66.60.24
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 connmand[215]: wlan0 {update} flags 36867 <UP>
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 connmand[215]: wlan0 {newlink} index 3 address 00:0E:8E:75:A5:EB mtu 1500
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 connmand[215]: wlan0 {newlink} index 3 operstate 2 <DOWN>
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 kernel: wlan0: deauthenticated from 00:42:68:bd:ea:c1 (Reason: 3=DEAUTH_LEAVING)
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 flipflop_wsgi.py[405]: 17:16:48 - WAR - app.models.printer:326 - Unable to contact printer Printer(unique_name=ultimakersystem-ccbdd3004764, friendly_name=NPDUltimaker3Ext, uuid=d58932db-d52e-42f6-a597-5a6fd9cd6da9, enabled=True, reserved_by=None, status=unreachable, authenticated=True) at IP 10.66.60.24 or find it via zeroconf.
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: 1970-01-01 17:16:48,531 WARNING  hotendCartridgeManager Reading data from hotend 0 eeprom failed.
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 flipflop_wsgi.py[405]: 17:16:48 - WAR - app.libs.printer_api:165 - Failed to fetch status for print job at http://10.66.60.24/api/v1
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 flipflop_wsgi.py[405]: 17:16:48 - WAR - app.libs.printer_api:175 - Failed to fetch status for historical print job http://10.66.60.24/api/v1
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 flipflop_wsgi.py[405]: 17:16:48 - WAR - app.libs.printer_api:175 - Failed to fetch status for historical print job http://10.66.60.24/api/v1
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 flipflop_wsgi.py[405]: 17:16:48 - WAR - app.libs.printer_api:175 - Failed to fetch status for historical print job http://10.66.60.24/api/v1
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 flipflop_wsgi.py[405]: 17:16:48 - WAR - app.libs.printer_api:175 - Failed to fetch status for historical print job http://10.66.60.24/api/v1
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 flipflop_wsgi.py[405]: 17:16:48 - WAR - app.libs.printer_api:175 - Failed to fetch status for historical print job http://10.66.60.24/api/v1
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 wpa_supplicant[254]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:42:68:bd:ea:c1 reason=3
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 wpa_supplicant[254]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="pentair-msc-ffs-w3" auth_failures=1 duration=10 reason=CONN_FAILED
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 wpa_supplicant[254]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 wpa_supplicant[254]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: 1970-01-01 17:16:48,820 WARNING  hotendCartridgeManager unknown hotend eeprom layout detected 25
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: 1970-01-01 17:16:48,821 ERROR    thread          Exception in thread: HotendCartridgeManager events
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: Traceback (most recent call last):
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: File "/usr/share/griffin/griffin/thread.py", line 33, in run
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: self.__target(*self.__args, **self.__kwargs)
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: File "/usr/share/griffin/griffin/printer/hotendCartridgeManager/hotendCartridgeManager.py", line 258, in _runEvents
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: self._updateHotendPresent(hotend_nr)
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: File "/usr/share/griffin/griffin/printer/hotendCartridgeManager/hotendCartridgeManager.py", line 148, in _updateHotendPresent
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: eventType.postEvent(eventType.HOTEND_CARTRIDGE_CHANGE, [hotend_nr, self._hotends[hotend_nr].getValue("hotend_cartridge_id"), self._hotends[hotend_nr].getSerial()])
Jan 01 17:16:48 ultimakersystem-ccbdd3004764 python3[354]: AttributeError: 'NoneType' object has no attribute 'getValue'

 

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 and/or the core itself wobly in the head (clean the core/connectors within the head)?

[le_avion 1]

After not using the UM3e for few months in frustration I started using it again and guess what? ER18 galore. I am on the latest firmware and I reset the cable at the print head for good measure but it didn't help. From day one I have experienced ER18s and I think I am ready to permanently give up on this printer. It is out of warranty and I don't think I am ready to throw more good money on a lemon. I am not sure what else to do anymore at this point!

 

ultimakersystem-ccbdd3001a3d.4.3.3.20180529.boot0.log.zip

[kmanstudios 1,120]

35 minutes ago, le_avion said:

From day one I have experienced ER18s

If you were having this issue since day 1, I have to wonder why you did not get in touch with your support or just get a new cable on warranty.

[le_avion 1]

Because 1st I was told its a known issue with the firmware so I waited for the update. Then it worked for a little while and then the problems came back. At no point anyone from UM came out and said to contact support or to get the cable replaced. Only recent responses mentioned trying to re-seat the connector at the back of the print head. They kept asking me to try this or try that. None which worked. If you search for my posts you'll see the history.

Edited September 2, 2018 by le_avion

[kmanstudios 1,120]

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 faster than you can say "Great Jumpin' Jehoshaphat!"

 

But, maybe this can help in the meanwhile. I have found that the placement of the clips holding the cable to the bowden tube will have a lot to do with it.

 

After reseating the cable in the head, I put one clip right on the base of the Bowden tube. Then the next one up the line about 2 inches above that.

 

This does two things:

1. Holds the  cable down into the printhead.
2. Prevents the Bowden tube from wiggling around at the base, which can loosen the printhead cable.

Since doing that, I have very, very few issues with the first UM3E.

 

I do hope this helps. And, man....not sure who told you that the ER18 was firmware related as it has always been a mechanical stress issue on my printer.

[kmanstudios 1,120]

6 minutes ago, le_avion said:

Because 1st I was told its a known issue with the firmware so I waited for the update. Then it worked for a little while and then the problems came back. At no point anyone from UM came out and said to contact support or to get the cable replaced. Only recent responses mentioned trying to re-seat the connector at the back of the print head. They kept asking me to try this or try that. None which worked. If you search for my posts you'll see the history.

Just to address this specifically, I can say that I have never seen your posts on this and I live here basically. I still cannot see why you did not contact your provider or force them to put you in contact with someone that is responsible.

 

But, I did a search and only found 3. This just may mean the search engine is yucky though. You only have 25 posts going back a year, so I cannot fathom where the others are.

 

This does suck though. But give the above advice a shot.

[kmanstudios 1,120]

On 7/17/2017 at 11:37 PM, fbrc8-erin said:

For most materials, the heat of the bed is what holds the print in place. Once the bed has cooled (which can happen depending on what sort of failed print/error you have), the print can either come off the bed altogether or be sufficiently loosened from it that if you tried to resume the print, the print just wouldn't stay adhered to the bed and you'd end up with a printing mess.

This is something that has been brought up before, but here is a thought:

 

If the printer can detect a failure , why can it not go into pause mode and keep the buildplate heated. this would keep it from loosening.

 

Also, I am thinking that the printer would not be left for such an extended period after a failure like this that it would damage the printer itself. I mean, I have printed things for up to two weeks and the printer never stops going, soooooo.......

[le_avion 1]

3 of my last 3 prints failed with the same error. 100% failure rate.

 

I will follow your advice and move the clips and see if this helps.  I will let you know.