Page 1 of 1

EasyPrint3D aborts when slicing - without an error message

Posted: Wed Apr 01, 2020 8:50 pm
by JRichi
I have Windows 10.
Slicing seems to start correctly. Before the progress display starts, the EasyPrint3D program breaks down completely. Without an error.
The button Done! I can’t click. The gcode file is also not yet created.
What can I do?

Re: EasyPrint3D aborts when slicing - without an error message

Posted: Thu Apr 02, 2020 9:25 am
by William
Hi, can you provide your stl?
and you can try slice another model.
you can use Repetier Host to slice.

Re: EasyPrint3D aborts when slicing - without an error message

Posted: Fri Apr 03, 2020 5:02 pm
by JRichi
Hi William

the program always stops with the *.stl:
Program example files: deer.stl, case.stl
ASCII: comp01.dae_A.stl, test3.dae_A.stl
Binary: comp01.dae_B.stl, test3.dae_B.stl

I think the problem is not with the files.

-------------------
I am a newbie.
What you mean with "... use Repetier Host..."
-------------------

With Ultimaker 4.5 I can create the *.gcode files from the *.dae files. There are no problems.

Regards Juergen

Re: EasyPrint3D aborts when slicing - without an error message

Posted: Thu Apr 16, 2020 2:57 am
by JRichi
Hi Wiliam,

I reinstalled the EasyPrint 3D program and the printer driver.
The result is the same. Slicing stops without an error message.

Wenn ich das Slicing mit Ultimaker Cura 4.5

If I do slicing with Ultimaker Cura 4.5 then I can easily load the *.gcode file.

I have linked the *.gcode extension to the EasyPrint3D program.

When I double click on a *.gcode file I get an error message:
System.IO.FileNotFoundException: img/Disconnect.png
bei System.Drawing.Image.FromFile(String filename, Boolean useEmbeddedColorManagement)
bei RepetierHost.view.ThreeDControl.UpdatePrintPanel(Object sender, EventArgs e)
bei System.Windows.Forms.Timer.OnTick(EventArgs e)
bei System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

The program can then no longer be continued.

I would be very happy to receive a response.

Regards Juergen