Benraay

Lol good news that CEL is recruiting I’m not looking for a JOB now.

And like @17bt said a plugin system would be very interesting

like adding a custom slicer with some pre and post processing options.

To make a long story short.

I started some tests with slicing G-code with Slic3r and tweaking the g-gode produced to open the Robox specific Valve needles at the beginning of the code you put

G1 B1 that opens the valves

and at the end you put a

G1 B0 that closes the valves.

But the resulting prints have lots of strings and ooze.

And @nebbian…[Read more]

Hi @pete thanks for that, it will be better the have it here and clearly visible.

Like you know the mac version is working fine except some little issues.

And we are close to have a windows version working.

Good news it’s going forward the exe that must send parameters to java is working.

but now there are some bug in the java part.

It needs a bit more time to be debugged but we are closer !

Yes I just pushed it to the master

Yes I know the GIT solution to get bash working on Pc, I used it in the past.

But the problem is that the program is named CuraEngine.exe and if it is not a real exe file it will fail.

I tried multiple workarounds but with no success for now and I’m pretty close to get my c++ working.

@nebbian I will send the cmd that should work if it was an exe.

@nebbian I already made a try with kind of solution but the bat file in the exe is copied to a temp folder and it is impossible to find our jar file with relative path like we did in the curaEngine script.

So the only way is writing a real windows exe and c or c++ is the one with less dependencies and most lightweight and potentially cross platform.

Ok there some really annoying things on windows the CuraEngine needs to be named CuraEngine.exe so we need to write code with something that is able to produce an exe file.

I have started a thing with C++ but it’s bit tricky with the arguments and spaces to escape and all that stuff. But it’s maybe the only way to get it work.

I have also…[Read more]

Ok great it is working on my virtualbox, the USB 2 tip was the good one for setting it up !

I will make some tests and fix things if needed.

I already have a suggestion on the installer we should be able to give the slic3r path and the automaker path if we don’t find them in the “default folder”.

let’s coding I will give some feedback later !

Yes I didn’t have time this week to give it a try, I hope tonight having a bit of time, looking if the stuff is working well on PC with Virtualbox.

Thank you @17bt for your feedback, it’s really funny to play with all those new options we get with Slic3r

Hi @17bt,

it’s possible to print gcode sliced outside AM but you need at least to add a G1 B1 command at the beginning in order to open the robox valves and a G1 B0 at the end to close them.

you can also add the ROBoX macros at start and end to make the bed levelling and other stuff.

you can find them in an another gcode you already printed in…[Read more]

@leonardoamet yes it will we just need to make some tests @click is working on it and I will also look on it tonight.

We made it with Java especially to be cross platform.

For now only the Prusa Slic3r version is supported and tested (a bit, more tests need to be made on dual materials and also using quickFill head).
Normally with the latest changes @nebbian made on the postprocess Slic3r normal version should work but has not been tested.

I will work soon on the Cura 2.5 integration because I want to test some…[Read more]

I made also some prints with it we can now use the different layer height feature also.

I will work on the Cura 2.5 conversion, it’s mostly turning extrusion Relative I already made a part of the script doing that, would be a great tool !

People I got it translated I just pushed it in my feature branch.

I can make a pull request but the main class is just populated with a test taking a printjob and convert the gcode.

I just need to make the rename stuff at the end.

We can now start coding the next improvements with java !!

@nebbian yes the dual head is 0,4 mm nozzles and the single material is 0,3 mm

I have pushed my first lines of code in a feature branch, Java is much more verbose than pearl !!

but it’s easier to read maybe !

I just stopped on a special EXIT_IF:
I learn special things about perl, but need some time to know what it does.

I love the simple…[Read more]

Yes this version is much better and well maintained you can see last release was two weeks ago !

Latest stable version I use :

https://github.com/prusa3d/Slic3r/releases/tag/version_1.34.1.24

I had the same ridiculously high speed, I found out at the end that the perl postProcessor did not always handle the speed depending on the version of Slic3r you use !

It keeps the moving speed for printing if look at the robox postProcessed code you will probably see F1200 before the printlines it should be F480 or lower.

For now the best…[Read more]