Jump to content
Ultimaker Community of 3D Printing Experts
leliep

Error I2C_HEAD_COMM_ERROR, how to deal with?

Recommended Posts

After several weeks without any major problem my UM3 last night stopped with an error, while printing with with a 0.8 nozzle and displayed the following error message:

PrintCore in head slot 1 is taking too long to warm up.

-devMode-

internal message follows:

Waiting for hotend temperature is taking too long

After turning off the device and clearing up the mess I restarted the print process. After printing part of the first layer, it stopped with the following error message:

There is a communication error with the print head.

Go to ultimaker.com/ER18.

-devMode-

internal message follows:

Error I2C_HEAD_COMM_ERROR

  • I replaced the print core with an aa0.4 type and after restarting the print I got the previous error again after a short time of printing.
  • I restarted the print on extruder 2 and it went without a problem.

Maybe the cable to the print heads is defective? After 7 weeks of use?

The information at ultimaker.com/ER18 is not helpful in this case.

Anybody else seen this problem? What can I do next?

Thanks, -pl

Edited by Guest

Share this post


Link to post
Share on other sites

It did it again

After the first problem occurred I was able to print several parts with both extruders without of any problem, but today the above error occured again.

After completing the last night's print job with (only) extruder 2, my UM2 this morning sat there again with the same error message like 6 days ago.

There is a communication error with the print head.
Go to ultimaker.com/ER18
-devMode-
internal message follows:
Error I2C_HEAD_COMM_ERROR

I suppose in the cooldown phase after completion of printing the UM3 tried to communicate with the temperature sensor in extruder 1 (unused in the preceding job) without success, which led to the error.

Sending the request

http:///api/v1/system

gave this result:

{"country": "DE", "firmware": "3.7.7.20170627", "guid": "01d2b23d-6a83-41a0-a3e8-dcf0fde26d85", "hardware": {"revision": 0, "typeid": 9066}, "hostname": "ultimakersystem-ccbdd3001d93", "language": "", "log": ["Aug 28 05:49:06 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:06,882 INFO     procedure       Message: 'ABORT' for procedure 'PrintProcedure(key='PRINT')'", "Aug 28 05:49:06 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:06,883 INFO     procedure       Abort message received for procedure PrintProcedure(key='PRINT')", "Aug 28 05:49:06 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:06,886 INFO     procedure       Pass abort to RUN_POST_PRINT", "Aug 28 05:49:06 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:06,887 INFO     procedureStep   Aborting step: OtherProcedureStep(key='RUN_POST_PRINT')", "Aug 28 05:49:06 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:06,888 INFO     procedure       Message: 'ABORT' for procedure 'PostPrintProcedure(key='POST_PRINT')'", "Aug 28 05:49:06 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:06,889 INFO     procedure       Abort message ignored for procedure PostPrintProcedure(key='POST_PRINT')", "Aug 28 05:49:06 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:06,893 INFO     printerStateProperty State change: printing -> error", "Aug 28 05:49:06 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:06,916 INFO     procedure       PostPrintProcedure(key='POST_PRINT') is going to be aborted", "Aug 28 05:49:07 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:07,977 INFO     procedure       PostPrintProcedure(key='POST_PRINT') transitioning from HomeHeadStep(key='HOME_HEAD') --> QueueRawGCodeWaitStep(key='RESET_OFFSET_0')", "Aug 28 05:49:07 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:07,979 INFO     printerService  Procedure next step: POST_PRINT: RESET_OFFSET_0", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,157 INFO     procedure       PostPrintProcedure(key='POST_PRINT') transitioning from QueueRawGCodeWaitStep(key='RESET_OFFSET_0') --> ResetPropertyToDefaultStep(key='RESET_TUNE_OFFSET_TEMPERATURE_0')", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,159 INFO     printerService  Procedure next step: POST_PRINT: RESET_TUNE_OFFSET_TEMPERATURE_0", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,162 INFO     procedure       PostPrintProcedure(key='POST_PRINT') transitioning from ResetPropertyToDefaultStep(key='RESET_TUNE_OFFSET_TEMPERATURE_0') --> QueueRawGCodeWaitStep(key='RESET_OFFSET_1')", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,165 INFO     printerService  Procedure next step: POST_PRINT: RESET_OFFSET_1", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,276 INFO     procedure       PostPrintProcedure(key='POST_PRINT') transitioning from QueueRawGCodeWaitStep(key='RESET_OFFSET_1') --> ResetPropertyToDefaultStep(key='RESET_TUNE_OFFSET_TEMPERATURE_1')", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,280 INFO     printerService  Procedure next step: POST_PRINT: RESET_TUNE_OFFSET_TEMPERATURE_1", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,285 INFO     procedure       PostPrintProcedure(key='POST_PRINT') transitioning from ResetPropertyToDefaultStep(key='RESET_TUNE_OFFSET_TEMPERATURE_1') --> WaitForQueueToBeEmptyStep(key='WAITING')", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,287 INFO     printerService  Procedure next step: POST_PRINT: WAITING", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,292 INFO     procedure       PostPrintProcedure(key='POST_PRINT') transitioning from WaitForQueueToBeEmptyStep(key='WAITING') --> OtherProcedureStep(key='SWITCH_TO_HOTEND')", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,294 INFO     printerService  Procedure next step: POST_PRINT: SWITCH_TO_HOTEND", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,297 INFO     switchActiveHotendProcedure Target hotend = 1", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,304 INFO     printerService  Procedure start: SWITCH_ACTIVE_HOTEND: WAIT", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,313 INFO     printerService  Procedure next step: SWITCH_ACTIVE_HOTEND: WAIT", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,322 INFO     procedure       SwitchActiveHotendProcedure(key='SWITCH_ACTIVE_HOTEND') transitioning from WaitForQueueToBeEmptyStep(key='WAIT') --> SwitchActiveHotendStep(key='SWITCH_ACTIVE_HOTEND')", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,328 INFO     printerService  Procedure next step: SWITCH_ACTIVE_HOTEND: SWITCH_ACTIVE_HOTEND", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,335 INFO     procedure       SwitchActiveHotendProcedure(key='SWITCH_ACTIVE_HOTEND') transitioning from SwitchActiveHotendStep(key='SWITCH_ACTIVE_HOTEND') --> None", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,339 INFO     printerService  Procedure finished: SWITCH_ACTIVE_HOTEND", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,344 INFO     procedure       PostPrintProcedure(key='POST_PRINT') transitioning from OtherProcedureStep(key='SWITCH_TO_HOTEND') --> HomeHeadStep(key='HOME_HEAD')", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,347 INFO     printerService  Procedure next step: POST_PRINT: HOME_HEAD", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,725 INFO     procedure       PostPrintProcedure(key='POST_PRINT') transitioning from HomeHeadStep(key='HOME_HEAD') --> WaitForQueueToBeEmptyStep(key='WAITING')", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,727 INFO     printerService  Procedure next step: POST_PRINT: WAITING", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,732 INFO     procedure       PostPrintProcedure(key='POST_PRINT') transitioning from WaitForQueueToBeEmptyStep(key='WAITING') --> PowerDownSteppersStep(key='POWER_DOWN_STEPPERS')", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,734 INFO     printerService  Procedure next step: POST_PRINT: POWER_DOWN_STEPPERS", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,879 INFO     procedure       PostPrintProcedure(key='POST_PRINT') transitioning from PowerDownSteppersStep(key='POWER_DOWN_STEPPERS') --> WaitForQueueToBeEmptyStep(key='WAITING')", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,881 INFO     printerService  Procedure next step: POST_PRINT: WAITING", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,885 INFO     procedure       PostPrintProcedure(key='POST_PRINT') transitioning from WaitForQueueToBeEmptyStep(key='WAITING') --> None", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,890 INFO     printerService  Procedure finished: POST_PRINT", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,892 INFO     procedureStep   Step to Aborted state: RUN_POST_PRINT", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,901 WARNING  procedure       PrintProcedure(key='PRINT') is aborted and overruling outcome OutcomeBase.Aborted from OtherProcedureStep(key='RUN_POST_PRINT')", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,906 INFO     procedure       PrintProcedure(key='PRINT') transitioning from OtherProcedureStep(key='RUN_POST_PRINT') --> WaitMessageStep(key='WAIT_FOR_CLEANUP')", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,913 INFO     printJobStateProperty New print job state: post_print -> wait_cleanup", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,921 INFO     printerService  Procedure next step: PRINT: WAIT_FOR_CLEANUP", "Aug 28 05:49:09 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:09,887 INFO     registryFile    Saving preferences to /var/lib/griffin/printer_hotend_1_preferences.json", "Aug 28 05:54:10 ultimakersystem-ccbdd3001d93 connmand[196]: ntp: time slew -0.007819 s", "Aug 28 06:01:39 ultimakersystem-ccbdd3001d93 python3.4[182]: 2017-08-28 06:01:39,596 INFO     systemUpdate    Comparing firmware 'stable' old version '3.7.7.20170627' with new version '3.7.7.20170627' with result: True", "Aug 28 06:11:14 ultimakersystem-ccbdd3001d93 connmand[196]: ntp: time slew -0.008152 s", "Aug 28 06:28:19 ultimakersystem-ccbdd3001d93 connmand[196]: ntp: time slew -0.008002 s", "Aug 28 06:40:19 ultimakersystem-ccbdd3001d93 mjpg-streamer[257]: MJPG-streamer [257]: serving client: 192.168.10.135", "Aug 28 06:42:21 ultimakersystem-ccbdd3001d93 mjpg-streamer[257]: MJPG-streamer [257]: serving client: 192.168.10.135", "Aug 28 06:45:23 ultimakersystem-ccbdd3001d93 connmand[196]: ntp: time slew -0.008102 s"], "memory": {"total": 1057030144, "used": 176541696}, "name": "ultimaker", "platform": "Linux-4.2.0-rc7-opinicus-00002-g1e30dbd-armv7l-with-debian-8.1", "type": "3D printer", "variant": "Ultimaker 3"}

Issuing

http:///api/v1/printer/diagnostics/temperature_flow/10

results in this:

[["Time", "temperature0", "target0", "heater0", "flow_sensor0", "flow_steps0", "temperature1", "target1", "heater1", "flow_sensor1", "flow_steps1", "bed_temperature", "bed_target", "bed_heater", "active_hotend_or_state"], [430249.375, 280.5, 0.0, 0.0, 0.0, 0.0, 280.5, 0.0, 0.0, 0.0, 0.0, 24.0, 0.0, 0.0, 16.0], [430249.46875, 280.5, 0.0, 0.0, 0.0, 0.0, 280.5, 0.0, 0.0, 0.0, 0.0, 23.799999237060547, 0.0, 0.0, 16.0], [430249.59375, 280.5, 0.0, 0.0, 0.0, 0.0, 280.5, 0.0, 0.0, 0.0, 0.0, 24.299999237060547, 0.0, 0.0, 16.0], [430249.6875, 280.5, 0.0, 0.0, 0.0, 0.0, 280.5, 0.0, 0.0, 0.0, 0.0, 24.0, 0.0, 0.0, 16.0], [430249.8125, 280.5, 0.0, 0.0, 0.0, 0.0, 280.5, 0.0, 0.0, 0.0, 0.0, 24.100000381469727, 0.0, 0.0, 16.0], [430249.90625, 280.5, 0.0, 0.0, 0.0, 0.0, 280.5, 0.0, 0.0, 0.0, 0.0, 24.0, 0.0, 0.0, 16.0], [430250.03125, 280.5, 0.0, 0.0, 0.0, 0.0, 280.5, 0.0, 0.0, 0.0, 0.0, 23.700000762939453, 0.0, 0.0, 16.0], [430250.125, 280.5, 0.0, 0.0, 0.0, 0.0, 280.5, 0.0, 0.0, 0.0, 0.0, 24.299999237060547, 0.0, 0.0, 16.0], [430250.25, 280.5, 0.0, 0.0, 0.0, 0.0, 280.5, 0.0, 0.0, 0.0, 0.0, 23.799999237060547, 0.0, 0.0, 16.0], [430250.34375, 280.5, 0.0, 0.0, 0.0, 0.0, 280.5, 0.0, 0.0, 0.0, 0.0, 24.0, 0.0, 0.0, 16.0]]

And finally the result from

http:///api/v1/printer/heads/0

is this:

{"acceleration": 3000.0, "extruders": [{"active_material": {"GUID": "506c9f0d-e3aa-4bd4-b2d2-23e2425b1aa9", "guid": "506c9f0d-e3aa-4bd4-b2d2-23e2425b1aa9", "length_remaining": -1.0}, "feeder": {"acceleration": 3000.0, "jerk": 5.0, "max_speed": 45.0}, "hotend": {"id": "AA 0.4", "offset": {"state": "valid", "x": 0.0, "y": 0.0, "z": 0.0}, "serial": "d1fac2170000", "statistics": {"last_material_guid": "506c9f0d-e3aa-4bd4-b2d2-23e2425b1aa9", "material_extruded": 468080, "max_temperature_exposed": 280, "time_spent_hot": 2069820}, "temperature": {"current": 280.5, "target": 0.0}}}, {"active_material": {"GUID": "506c9f0d-e3aa-4bd4-b2d2-23e2425b1aa9", "guid": "506c9f0d-e3aa-4bd4-b2d2-23e2425b1aa9", "length_remaining": -1.0}, "feeder": {"acceleration": 3000.0, "jerk": 5.0, "max_speed": 45.0}, "hotend": {"id": "AA 0.4", "offset": {"state": "valid", "x": -0.07317073170731714, "y": 0.07317073170731714, "z": 1.4191436945413525}, "serial": "ae3fc2170000", "statistics": {"last_material_guid": "506c9f0d-e3aa-4bd4-b2d2-23e2425b1aa9", "material_extruded": 120620, "max_temperature_exposed": 280, "time_spent_hot": 806220}, "temperature": {"current": 280.5, "target": 0.0}}}], "fan": 0.0, "jerk": {"x": 20.0, "y": 20.0, "z": 0.4}, "max_speed": {"x": 300.0, "y": 300.0, "z": 40.0}, "position": {"x": 0.0, "y": 0.0, "z": 0.0}}

Thanks for any hints or recommendations (Ultimaker, are you listening?).

Edited by Guest
some more detail

Share this post


Link to post
Share on other sites

If the problem persists, please contact your reseller. But first make sure the printcores are properly placed into the slots ("until you hear a click"). A misplaced core could trigger the I2C error.

Thanks for your suggestion; I am pretty sure that they are placed correctly, but will verify once more and test again.

Share this post


Link to post
Share on other sites

If the problem persists, please contact your reseller. But first make sure the printcores are properly placed into the slots ("until you hear a click"). A misplaced core could trigger the I2C error.

Thanks for your suggestion; I am pretty sure that they are placed correctly, but will verify once more and test again.

what you should do;

open the back 2 screws of the print head. remove the long screws. open the back little "clip"

you can see the connection cable going in.

use a small knife or something to press on the clip on the cable end to remove the cable from the print head. WARNING, the clip must be pressed or you will damage the cable!!

see if all connectors are still in good shape..

plug the cable back in and ensure there is enough wiggle room.

rebuild the head

that should take care of it. it is most likely a slightly loose connection cable

Share this post


Link to post
Share on other sites

If the problem persists, please contact your reseller. But first make sure the printcores are properly placed into the slots ("until you hear a click"). A misplaced core could trigger the I2C error.

Thanks for your suggestion; I am pretty sure that they are placed correctly, but will verify once more and test again.

what you should do;

open the back 2 screws of the print head. remove the long screws. open the back little "clip"

you can see the connection cable going in.

use a small knife or something to press on the clip on the cable end to remove the cable from the print head. WARNING, the clip must be pressed or you will damage the cable!!

see if all connectors are still in good shape..

plug the cable back in and ensure there is enough wiggle room.

rebuild the head

that should take care of it. it is most likely a slightly loose connection cable

That’s a nice idea. But also if the machine is new to avoid having warranty issues I with warranty I would wait for the reseller advice

  • Like 2

Share this post


Link to post
Share on other sites

Arrgggg, I just talked to a technician from Conrad who told me to return the printer to them for repair or exchange. :-/

so to be honest, I'd ask them again if there is another way. as far as I know @fabric8 and fabric8erin keep me honest, if this error occurs there are some small steps your reseller would advise you to do. reseating the cable is one of them.

for example, the official US reseller, fabric8, has created this page on how to disconnect the data cable

https://fbrc8.zendesk.com/hc/en-us/articles/115000062743-Disconnecting-the-Printhead-UM3-UM3X-

that should be standard operating procedure.. not sending the printer back without any troubleshooting..

  • Like 1

Share this post


Link to post
Share on other sites

that should be standard operating procedure.. not sending the printer back without any troubleshooting..

Important note at the beginning

“Do not disassemble the printer unless you have been instructed to do so.”

not disagreeing with that, but if the first thing out of a resellers mouth is "just send it back" then that;s not ok with this error...

then again, perhaps I just like to live on the wild side :)

Share this post


Link to post
Share on other sites

that should be standard operating procedure.. not sending the printer back without any troubleshooting..

Important note at the beginning

“Do not disassemble the printer unless you have been instructed to do so.”

not disagreeing with that, but if the first thing out of a resellers mouth is "just send it back" then that;s not ok with this error...

then again, perhaps I just like to live on the wild side :)

Nono. I agree with you personally. I would have disassemble the heck out of it because that how I am. But warranty and stuff for um3 is different. So I prefer to be safe than sorry when the printer isn’t mine :D

Also we know there’s no magic unicorns inside and except the damage by ESD, the rest it’s pretty much like any printer. But also, well, is a 3K machine after all.

Edited by Guest

Share this post


Link to post
Share on other sites

that should be standard operating procedure.. not sending the printer back without any troubleshooting..

Important note at the beginning

“Do not disassemble the printer unless you have been instructed to do so.”

not disagreeing with that, but if the first thing out of a resellers mouth is "just send it back" then that;s not ok with this error...

then  again, perhaps I just like to live on the wild side :)

Nono. I agree with you personally. I would have disassemble the heck out of it because that how I am. But warranty and stuff for um3 is different. So I prefer to be safe than sorry when the printer isn’t mine :D

Also we know there’s no magic unicorns inside and except the damage by ESD, the rest it’s pretty much like any printer. But also, well, is a 3K machine after all.

agreed,

but he bought at Conrad who is NOT an official reseller. and if the first thing out of their mouths is "just send it back" I'd worry about what I would get returned to me. I'd contact either an official reseller, or play with it myself before I would send it back.

  • Like 2

Share this post


Link to post
Share on other sites

that should be standard operating procedure.. not sending the printer back without any troubleshooting..

Important note at the beginning

“Do not disassemble the printer unless you have been instructed to do so.”

not disagreeing with that, but if the first thing out of a resellers mouth is "just send it back" then that;s not ok with this error...

then  again, perhaps I just like to live on the wild side :)

Nono. I agree with you personally. I would have disassemble the heck out of it because that how I am. But warranty and stuff for um3 is different. So I prefer to be safe than sorry when the printer isn’t mine :D

Also we know there’s no magic unicorns inside and except the damage by ESD, the rest it’s pretty much like any printer. But also, well, is a 3K machine after all.

agreed,

but he bought at Conrad who is NOT an official reseller. and if the first thing out of their mouths is "just send it back" I'd worry about what I would get returned to me. I'd contact either an official reseller, or play with it myself before I would send it back.

Well, the printer kit contained a screwdriver which fits the screws we're talking about. I take that as a sign from above... ;-)

Btw, if I had known the support issue with Conrad previously, then I would have chosen another reseller. I really hesitate to ship the printer to them, because I fear that it might not get better by being sent across the country.

Thank you for the reference to the fabric8-document, it looks helpful and after opening the cable cover to get a peek into it, I'm pretty confident that checking the cable will do no harm. This is not the first box that I'm opening in my life.

  • Like 1

Share this post


Link to post
Share on other sites

leliep, did reseating the cable go okay? The other thing to check is to make sure you're running the most up to date firmware, which can make a difference with the i2c errors.

Yes, I disconnected and reseated the cable, but it looked absolutely ok, will try now whether the problem is still there...

For further reference I took some pictures to show the proper place to push to disconnect the plug ;-)

IMG_3448.thumb.jpg.352ba68f9d8480f99dc65309e0849540.jpg

IMG_3449.thumb.jpg.b8f7eccb6b03b8b84f29c18c71b4efcf.jpg

IMG_3450.thumb.jpg.e4b98e213e9e1d758a06f3591d0d19ed.jpg

IMG_3447.thumb.jpg.f560912955c53a4d972dc9230dec2cd3.jpg

Share this post


Link to post
Share on other sites

so how did it go? Did it go away and never come back?

 

Up to now it hasn't reappeared, but previously it already took some time to repeat. So right now I'm printing like mad, hoping that it will have gone.

(But - as I know from other projects - those things do not just disappear, they only hide. Until you can find the real reason, which I did not. Yet.)

Share this post


Link to post
Share on other sites

so how did it go? Did it go away and never come back?

Up to now it hasn't reappeared, but previously it already took some time to repeat. So right now I'm printing like mad, hoping that it will have gone.

(But - as I know from other projects - those things do not just disappear, they only hide. Until you can find the real reason, which I did not. Yet.)

...still counting... no problem till now.

Share this post


Link to post
Share on other sites

Sad to say that the problem has happened again, twice in the last two days.

Would it be helpful to post logfiles?

Contacting my reseller appears not be helpful; they want me to send back the device, which I want to avoid because I do not trust the DHL people to be careful with my UM3.

 

Glad to hear it sounds like the issue has been gone for a month. Generally reseating the cable does the trick in most cases.

 

Share this post


Link to post
Share on other sites

Would it make sense to check the other side of the extruder cable (@ the controller board)?

 

Sad to say that the problem has happened again, twice in the last two days.

Would it be helpful to post logfiles?

Contacting my reseller appears not be helpful; they want me to send back the device, which I want  to avoid because I do not trust the DHL people to be careful with my UM3.

 

Glad to hear it sounds like the issue has been gone for a month. Generally reseating the cable does the trick in most cases.

 

 

Share this post


Link to post
Share on other sites

Posting logfiles would be helpful yes. If you use something like wetransfer it allows us to take a peek.

Also, just out of curiosity, what Print Core are you using? Is it always the same Print Core?

If you, for example, use AA in both slots, if you change them, what happens: is the error for the same Print Core, or for the same slot?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Our picks

    • Introducing Ultimaker Cura 3.6 | Beta
      Ultimaker Cura 3.6 | Beta is available. It comes with new features, bug fixes, and UX improvements. We would really like to have your feedback on it to make our stable release as good as it can be. As always, you can download the beta for free from our website, for Windows, MacOS, and Linux.
        • Like
      • 95 replies
    • Print Core CC | Red for Ruby
      Q: For some users, abrasive materials may be a new subject matter. Can you explain what it is that makes a material abrasive when you are not sure which print core to use?
      A: Materials which are hard in a solid piece (like metals, ceramics and carbon fibers) will generally also wear down the nozzle. In general one should assume...
        • Like
      • 30 replies
    • "Back To The Future" using Generative Design & Investment Casting
      Designing for light-weight parts is becoming more important, and I’m a firm believer in the need to produce lighter weight, less over-engineered parts for the future. This is for sustainability reasons because we need to be using less raw materials and, in things like transportation, it impacts the energy usage of the product during it’s service life.
        • Like
      • 12 replies
×

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!