Jump to content
Ultimaker Community of 3D Printing Experts
titatovenaar

CuraEngine crashes with multi extruder

Recommended Posts

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

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

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

    • Taking Advantage of DfAM
      This is a statement that’s often made about AM/3DP. I'll focus on the way DfAM can take advantage of some of the unique capabilities that AM and 3DP have to offer. I personally think that the use of AM/3DP for light-weighting is one of it’s most exciting possibilities and one that could play a key part in the sustainability of design and manufacturing in the future.
        • Like
      • 3 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!