Jump to content
titatovenaar

CuraEngine crashes with multi extruder

Recommended Posts

Posted · CuraEngine crashes with multi extruder

Hi,

I'm having this problem when I use a dual extruder with CURA 2.1. (x32/x64 tested) When setting extruder = 0 there's no problem. When setting extruder > 0 the CuraEngine crashes. I also tried all compatibility (for CURAEngine) modes available in Windows10 included administrator mode. But no succes.

Any ideas how to solve this problem?

Greets,

Share this post


Link to post
Share on other sites
Posted · CuraEngine crashes with multi extruder

Hi, Here are the latest error logs

2016-05-14 21:38:55,594 - DEBUG - Attempting to kill the engine process

2016-05-14 21:38:55,594 - DEBUG - Killing engine process

2016-05-14 21:38:55,595 - DEBUG - Engine process is killed. Recieved return code 3221225477

2016-05-14 21:38:55,595 - ERROR - A socket error caused the connection to be reset

2016-05-14 21:38:55,601 - INFO - Started engine process: F:\Program Files\Cura 2.1\CuraEngine.exe

2016-05-14 21:38:55,623 - DEBUG - Backend connected on port 49674

2016-05-14 21:38:56,136 - DEBUG - Sending data to engine for slicing.

2016-05-14 21:38:56,136 - DEBUG - Sending data to engine is completed

2016-05-14 21:39:00,957 - WARNING - Arcus Error (6, native 10054): Receiving type failed

2016-05-14 21:39:01,059 - DEBUG - Attempting to kill the engine process

2016-05-14 21:39:01,059 - DEBUG - Killing engine process

2016-05-14 21:39:01,059 - DEBUG - Engine process is killed. Recieved return code 3221225477

2016-05-14 21:39:01,059 - ERROR - A socket error caused the connection to be reset

2016-05-14 21:39:01,065 - INFO - Started engine process: F:\Program Files\Cura 2.1\CuraEngine.exe

2016-05-14 21:39:01,086 - DEBUG - Backend connected on port 49674

2016-05-14 21:39:01,608 - DEBUG - Sending data to engine for slicing.

2016-05-14 21:39:01,609 - DEBUG - Sending data to engine is completed

2016-05-14 21:39:03,792 - WARNING - Arcus Error (6, native 10054): Could not receive data for message

2016-05-14 21:39:03,894 - DEBUG - Attempting to kill the engine process

2016-05-14 21:39:03,894 - DEBUG - Killing engine process

2016-05-14 21:39:03,894 - DEBUG - Engine process is killed. Recieved return code 3221225477

2016-05-14 21:39:03,895 - ERROR - A socket error caused the connection to be reset

2016-05-14 21:39:03,900 - INFO - Started engine process: F:\Program Files\Cura 2.1\CuraEngine.exe

2016-05-14 21:39:03,922 - DEBUG - Backend connected on port 49674

2016-05-14 21:39:04,433 - DEBUG - Sending data to engine for slicing.

2016-05-14 21:39:04,434 - DEBUG - Sending data to engine is completed

Share this post


Link to post
Share on other sites
Posted · CuraEngine crashes with multi extruder

Technically speaking the dual extrusion isn't fully supported by 2.1, so it's not that surprising that it doesn't completely as intended.

This will be addressed in feature releases.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Our picks

    • Ultimaker Cura 4.0 | Stable available!
      Ultimaker Cura 4.0 is mainly focused on the improved user interface and cloud integration.
      As always, we want to collect your user feedback for this release. If there are any improvements you can think of, feel free to mention it here and help us to shape the next release.
      • 96 replies
×
×
  • Create New...

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!