RoboxDual › Forums › Software › RoboxSlicerExtension › robox-slicer-control-SNAPSHOT.jar - Cura 2.7
This topic contains 17 replies, has 3 voices, and was last updated by
nebbian 20 hours, 52 minutes ago.
-
AuthorPosts
-
September 8, 2017 at 8:29 pm #43848
@nebbian & @click and one other, I know you’re short of time, but I installed Cura 2.7 on the iMac tonight, but I cannot get it to see the Robox, despite moving line 313 with a # in the USBPrinterOutputDevice.py file, like previous versions, so I thought I’d play some more using AutoMaker and the robox-slicer-control-SNAPSHOT.jar
Selecting Cura 2.5 as an option and saving meant when I opened AutoMaker and hit Make, it opened my renamed Cura 2.7 now “Cura” in my Applications folder, as I had two copies of Cura (old & latest), rather than “Cura 2.5” which is in there too, and I was able to see the model. Unlike before, the time calls for the print were calculated , and it completed to the end, but when closing Cura it said “slicing failed”…
Info in images… but not a million miles away, obviously have to develop a profile for the Robox DM
I can see it hasn’t been post processed successfully, as my file was “x.gcode”, and didn’t get converted into “x.slicer.gcode”
Enjoy guys…
- This topic was modified 6 days, 14 hours ago by Mike.
Attachments:
You must be logged in to view attached files.September 8, 2017 at 9:13 pm #43858More info, but bear in mind, I haven’t put any printer settings data into Cura yet, as I was just seeing if it would slice, and then cancel the print straight away to stop it doing anything.
Attachments:
You must be logged in to view attached files.September 10, 2017 at 2:41 pm #43875Hi @17bt, thanks for looking at this.
There are a couple of problems with Cura compatibility at the moment. These are:
- It doesn’t support relative extrusion. Benraay wrote some code to work around this, but it’s commented out in the latest release. I’ll re-enable it and see how it goes.
- You can’t specify the output file when calling Cura via the command line. You’ve already run into this bug. You can work around it by changing the file name when it gets saved, but bear in mind that due to 1. above, you will not get a successful print.
- Cura seems to output G0 for travel moves, something that our script doesn’t handle (yet).
I managed to get my Robox to move tonight when using Cura, but it didn’t create a successful print at all. I don’t recommend trying Cura unless you’re willing to try uncommenting out the relative extrusion code and seeing what happens. I would also change the start GCode to just a simple home command.
Compulsive tinkerer
September 10, 2017 at 3:18 pm #43877Hmmm, @ nebbian I did start to read up about it, when I saw Benraay’s post using 2.5 and under extruding. I also saw how other folks were adapting Cura to their FDM printers, and seen a few things going on, but 2.7 is quite a bit different from 2.5, as they added some more bells and whistles, and also added independent flavours for RepRap, Marlin etc, but I saw they are looking at supporting relative extrusions in later builds. Also as Ultimaker pay for 90% of Cura development it is biased towards them, but if people, as in the community, put efforts into other printers, the dev team are happy to add them… lessons to be learned again perhaps 😉
I did look at the “variables” in Slic3r & early Cura, and seeing what AutoMaker looked for, some names being zeroed, others renamed, and searched for the Cura 2+ names too. I also looked at GCode parsers, plus other slicers like Ideamaker with removable support, but no point in buying Simply 3D yet, as their is no official CEL support, and probably unlikely to ever happen, so I’ll keep making support structures as a separate CAD model, then STL that.
It just a shame that we are in the doldrums having reached certain limits, and got frustrated by AutoMakers slicing habits, but at least the Slic3r port has it’s uses now. 🙂
PS I did get a similar file format, after I unchecked adding a prefix for the printer to it, but when I compared the slicing code, I did not the lack of relative E in the listing… that’s why I was looking at parsers. If I knew what I was doing it would help. 🙂
September 11, 2017 at 2:36 am #43886@17bt, don’t give up hope. There will be options soon.
Personally I quite dislike Cura’s interface, hence why I haven’t tried getting it working yet.
If you’re keen for a play, the lines you’re interested in are around here:
Compulsive tinkerer
September 11, 2017 at 2:13 pm #43910Here are the first two prints on the Robox using Cura 2.7.
I had to:
- Set the filament diameter in Cura to 1.3mm
- Change the speeds down to something realistic
- Modify the start GCode to have M82, and remove the priming code
- Slightly modify the Robox Slicer Extension to handle G0 moves
When slicing, I needed to change the output file to be xxxxxxx.slicer.gcode
So this seemed to work for a while. However when it came time to print those small parts, the retraction just didn’t want to work properly. Maybe I need to look at setting retraction to 0.5mm. It would be amazing if Cura supported relative extrusion, we wouldn’t have to go through these issues.
Attachments:
You must be logged in to view attached files.Compulsive tinkerer
September 12, 2017 at 6:16 am #43957OK we’re in business.
Use the latest flow application downloaded from github.
Import the attached settings into Cura.
You need to ensure that you save the file as xxxxxxxx.slicer.gcode (replacing the x’s with the md5 hash that is already present, you basically just put the word ‘slicer’ into the filename).
-
This reply was modified 3 days, 4 hours ago by
nebbian.
Attachments:
You must be logged in to view attached files.Compulsive tinkerer
September 12, 2017 at 8:56 pm #43971@nebbian, tried to update on macOS, looked like everything was Ok…still getting slicing failed.
I’ll uninstall and try again…
21:50:30.563 INFO [java.util.logging.LogManager$RootLogger log] Started robox slicer extension 21:50:30.563 INFO [java.util.logging.LogManager$RootLogger log] Started robox slicer extension 21:50:30.566 FINE [com.roboxing.slicerextension.flow.Arguments process] Invoked with arguments: 21:50:30.567 FINE [com.roboxing.slicerextension.flow.Arguments process] -v 21:50:30.567 FINE [com.roboxing.slicerextension.flow.Arguments process] -p 21:50:30.568 FINE [com.roboxing.slicerextension.flow.Arguments process] -c 21:50:30.568 FINE [com.roboxing.slicerextension.flow.Arguments process] 957d2d5bceee4f2f.roboxprofile 21:50:30.568 FINE [com.roboxing.slicerextension.flow.Arguments process] -o 21:50:30.569 FINE [com.roboxing.slicerextension.flow.Arguments process] 957d2d5bceee4f2f.gcode 21:50:30.569 FINE [com.roboxing.slicerextension.flow.Arguments process] 957d2d5bceee4f2f-0.stl 21:50:30.569 FINER [com.roboxing.slicerextension.flow.Arguments process] Argument : -v 21:50:30.569 FINER [com.roboxing.slicerextension.flow.Arguments process] Argument : -p 21:50:30.570 FINER [com.roboxing.slicerextension.flow.Arguments process] Argument : -c 21:50:30.570 FINER [com.roboxing.slicerextension.flow.Arguments process] Argument : -o 21:50:30.570 FINER [com.roboxing.slicerextension.flow.Arguments process] Argument : 957d2d5bceee4f2f-0.stl 21:50:30.571 CONFIG [com.roboxing.slicerextension.flow.Arguments ensureArgumentsValid] Assumed AM installation dir as /Applications/CEL 21:50:30.578 FINE [com.roboxing.slicerextension.flow.Controller process] Selecting Cura20 - current dir contains ‘PrintJobs’; /Users/mikecrane/CEL Robox/PrintJobs/957d2d5bceee4f2f 21:50:30.582 FINE [com.roboxing.slicerextension.flow.Controller process] Invoking Cura20 21:50:30.582 FINE [com.roboxing.slicerextension.flow.Cura20 invoke] Invoking Cura20 with args: 21:50:30.583 FINE [com.roboxing.slicerextension.flow.Cura20 invoke] /Applications/Cura.app/Contents/MacOS/cura 21:50:30.583 FINE [com.roboxing.slicerextension.flow.Cura20 invoke] file 21:50:30.583 FINE [com.roboxing.slicerextension.flow.Cura20 invoke] /Users/mikecrane/CEL Robox/PrintJobs/957d2d5bceee4f2f/957d2d5bceee4f2f-0.stl 21:52:09.875 FINE [com.roboxing.slicerextension.flow.Cura20 invoke] Successfully executed Cura20 with args: /Applications/Cura.app/Contents/MacOS/cura,file,/Users/mikecrane/CEL Robox/PrintJobs/957d2d5bceee4f2f/957d2d5bceee4f2f-0.stl 21:52:09.875 FINE [com.roboxing.slicerextension.flow.Controller process] Finished slicing with Cura20 21:52:09.876 FINE [com.roboxing.slicerextension.flow.Controller process] Invoking post processing Cura20 21:52:09.878 SEVERE [com.roboxing.slicerextension.flow.Main main] Error processing : java.io.FileNotFoundException: 957d2d5bceee4f2f.slicer.gcode (No such file or directory) at java.io.FileInputStream.open0(Native Method) at java.io.FileInputStream.open(FileInputStream.java:195) at java.io.FileInputStream.<init>(FileInputStream.java:138) at java.util.Scanner.<init>(Scanner.java:635) at java.util.Scanner.<init>(Scanner.java:629) at com.roboxing.slicerextension.flow.Slicer.postProcess(Slicer.java:80) at com.roboxing.slicerextension.flow.Cura20.postProcess(Cura20.java:87) at com.roboxing.slicerextension.flow.Controller.process(Controller.java:84) at com.roboxing.slicerextension.flow.Main.main(Main.java:67)
September 12, 2017 at 10:50 pm #43972you need to name the output file from Cura correctly.
From the log:
957d2d5bceee4f2f.slicer.gcode (No such file or directory)
That means you didn’t save the output file from cura as 957d2d5bceee4f2f.slicer.gcode
Good luck.
Compulsive tinkerer
September 13, 2017 at 4:33 am #43977@nebbian Thanks, but not being that daft, I did repeatedly add the “.slicer” suffix, as you can see in the screenshots
The only unusual thing is I get a “cannot Open File” notification when hitting Make and Cura opens, other than that everything is as you did. I saw the bug fix in the GitHub and updated again previously, so I’ll try again some other time, but thanks anyway.
Attachments:
You must be logged in to view attached files.September 13, 2017 at 6:34 am #43981September 13, 2017 at 8:04 am #43983 -
AuthorPosts
You must be logged in to reply to this topic.





