CuraEngine socket communication

[Luiz_coder 0]

Dear friends,

 

I have been trying to do some automation regarding slicing STL files to convert them to GCODE programmatically, i.e. through the use of a computer programming language.

I have tried basically these three approaches:

 

1) Calling CuraEngine as a command line process.

2) Connecting to CuraEngine socket.

3) Controling Cura GUI with a third part automation software.

 

With approach number 01 I can generate GCODEs, but they end up being malformed, a lot bigger in file size and there is also a limitation on the number of  "-s" parameters I can send through command line, thus bringing unsatisfiying results.

 

Approach number 03 is not very reliable, as it depends on how the app window is located on screen, resolution and other factors, although is the best way considering GCODE generation.

 

Approach number 02: I could successfully connect to CuraEngine socket through Java and LibArcus, but the only Google Protocol Buffers message I am able to send to CuraEngine is of "Progress" type. Also, I did not find any message types that allow me to load an STL file (as the CuraEngine "-l" argument does) neither to output a GCODE (as "-o").

 

So I kindly ask you guys if you can provide me with any code example of correct way of using CuraEngine with socket option.

 

What I am doing is executing "CuraEngine socket 127.0.0.1:8080" (or other port) and connecting to it with Java and LibArcus library.

It connects successfully, I can communicate with CuraEngine socket, but I don't know how to load an STL and send a "Slice" command and output the generated GCODE.

 

I've done a lot of research on the Internet but found nothing. So I ask for your kind help.

 

Regards,

Luiz.

 

[nallath 1,113]

Quote

With approach number 01 I can generate GCODEs, but they end up being malformed, a lot bigger in file size and there is also a limitation on the number of  "-s" parameters I can send through command line, thus bringing unsatisfiying results.

I've never ran into the number of parameters issue. Perhaps this is some issue with windows? I've also not have had them being malformated. The larger size is likely because of different settings.

 

Quote

Approach number 02: I could successfully connect to CuraEngine socket through Java and LibArcus, but the only Google Protocol Buffers message I am able to send to CuraEngine is of "Progress" type. Also, I did not find any message types that allow me to load an STL file (as the CuraEngine "-l" argument does) neither to output a GCODE (as "-o").

I really don't understand what you're doing here. The engine sends progress to the frontend, not the other way around. There is no command that allows you to load an STL as the -i command, you will need to send triangle soup yourself. You can also not let the engine directly save to disk like that. You will get a message with the g-code and you will need to save it yourself.

[Luiz_coder 0]

Nallath, thank you for your kind reply. I will do some additional research here, based on your comments.