1

Topic: Using Cura with Da Vinci 1.0

Hi All,

*** Just wanted to be sure this get's noticed... I'm not a programmer, have little to no experience with 3d Printers, so anything I post may have glaring issue's with it's accuracy. Bear this in mind if you try anything that I mention in this post. I am currently using the cartridge resetter so I can set temps to 230 for extruder and 100 for bed, and the modded version of XYZware to send things to the printer over USB.***

Ok, with the disclaimer out of the way...

I have been attempting to print with something other than XYZware or Slic3r and failing miserably. KISSlicer "air printed" as did Cura, so I took a look at the Gcode that the modified version of XYZware outputs. I noticed that unlike KISSlicer or Cura, it contains no "G0" commands. After doing a bit of research on the internet, I found out that G0 commands are used for fast travel, while G1 commands are used when the extruder is supposed to be doing something. I also tested Slic3r output and just like XYZware (not surprising since they use a version of it to slice with) it only uses G1 commands for everything.

This made me decide to do a simple test under the assumption that XYZ's version of the firmware ignores G0 commands. I sliced a small file in Cura, then I simply used notepad++ to replace all G0 commands with G1 and saved the output to a Gcode file. I then loaded the same file up in XYZ modded version and sliced it from there also saving it to a Gcode file, then loading it into another pane in notepad++. Then a copy and overwrite of the Cura header with the one from XYZmod, then save the output as a file to attempt to print.

The object is currently cooling on my Da Vinci and while I don't know yet if it's "perfect" it is assuredly not a total failure by any means. I did notice several "issue's" while it was printing. First is that the printer was running at a MUCH faster speed than I normally use. I use the excellent setting in XYZware and at most normal speed setting. This was running considerably faster than that, so I need to slow that down. Second thing is all the display showed when printing was the bed and extruder current temperature. I was somewhat surprised that the printer did do it's normal "shutdown wipe head parking and bed lower" procedure after I hit the down arrow twice to not wait for cooldown once it was done printing.

While I may at some point in time decide to try out the repetier firmware that was modded for the Da Vinci, I truly do like the cartridge "feature" of knowing what color is in the machine and how much is left on the spool. But while it may still need some tweaking, I can at least get prints out of other software than Slic3r or XYZware now.

2

Re: Using Cura with Da Vinci 1.0

I agree, XYZ does ignore G0 commands. I did the same when I import my Simplify3D gcode into XYZware several weeks ago and that was one of the changes that I made that was part of the first mod (although I only have it checking for Simplify3D gcode before it makes changes). There are several other commands that XYZ firmware ignores as well that slic3r does not use, but other slicers seem to use at times.  I will have to look at my source as I had xyz automatically make the changes where the invalid commands are used.

I currently do not use Cura, but if you do figure out the invalid commands other than G0 let me know and I will add them to the source so it can be done automatically on import for Cura gcode files. For cura I just added the line of code to replace all G0 and use G1 instead for cura files.

3

Re: Using Cura with Da Vinci 1.0

I intend to do another test print with Cura as soon as the "huge" print job I'm doing that I used KISSlicer on is done, if I find out anything I will surely let you know. Also, thanks much for all the software modding!

For anyone trying to set up Cura, I found out the source of my speed issue's. Cura for reasons I can't explain has you set the speeds in mm per second. I was expecting mm per minute the same as Gcode uses, so I totally botched that in my initial attempt at settings, since the defaults looked "safe". After dividing by the kind of numbers that the Da Vinci uses by 60 and putting them into the configuration, I realize that an Ultimaker must be MUCH faster on it's speeds than the Da Vinci is capable of. According to the comments from Daid, a "well tuned" Ultimaker can print at 150mm a second. The normal "fast travel" speed on a Da Vinci is 45mm a second (set at "Excellent" and "Fast" in XYZware) which is also the absolute max I've seen it spit out any Gcode line with any extrusion in it.

Fast travel default in KISSlicer appears to be 9000mm a minute or from Cura's perspective 150mm a second which is still faster than the Da Vinci appears to be able to move the extruder. Eventually we should have solid numbers for all the different slicer settings and be able to use whatever slicer we want to.

4

Re: Using Cura with Da Vinci 1.0

the repietier firmware uses the gcode G0(rapid travel)

5

Re: Using Cura with Da Vinci 1.0

Since I once again had to use Cura to slice up a large stl that crashes XYZware, it occured to me that others might have a use for the configuration I use. Cura has two files that you'll want to have correct settings in. You can just add these figures in the program settings itself instead of replacing the ini files, so it won't matter what version of Cura you happen to be using.

Remember to either do a search and replace of the gcode that you get from Cura of all G0 that you replace with G1 and add the header info, or if what your slicing won't kill XYZware, use w34's version and have all that handled for you. I'm using a cartridge resetter, so my temps might be higher than you can use, so set yours accordingly.

I honestly wish that XYZware would "improve" enough that even with it being slower than most other slicers that it could still be used for everything. But as it is, I'm glad there are other options.

Post's attachments

current_profile.ini 10.84 kb, 258 downloads since 2014-07-04 

preferences.ini 1.27 kb, 204 downloads since 2014-07-04 

You don't have the permssions to download the attachments of this post.

6

Re: Using Cura with Da Vinci 1.0

Has anyone been able to get their Da vinci to run directly on Cura? Assuming you are using Rep firmware of course. I cannot get it to connect using Cura.

Printing since 2009 and still love it!
Anycubic 4MAX best $225 ever invested.
Voxelabs Proxima SLA. 6 inch 2k Mono LCD.
Anycubic Predator, massive Delta machine. 450 x 370 print envelope.

7

Re: Using Cura with Da Vinci 1.0

Hello all, I created a little python script and config that will automatically convert Cura and slic3r gcode to 3w files that can be dropped into xyzware. Anyone willing to try this out and let me know if it works for you too?

The project is at github.com and it can be found here:

/masonsheffield/convert2daVinci

8

Re: Using Cura with Da Vinci 1.0

I am brand new to 3D printing and my Da Vinci 1.0.  Can someone tell me how you are exporting and importing Gcode out of these slicer programs?  I am already finding problems using the supplied software.

9

Re: Using Cura with Da Vinci 1.0

Hello rocky_beech,

This is a very old thread and topic, so unless you have very old firmware on your Da Vinci 1.0, most of what was written here will no longer apply. XYZ has continued to lock down the printer both firmware and software side since this thread was started, so you'll need far more "up to date" methods to get past XYZ approved programs.

At this point probably the easiest way to use a better slicer is either to upgrade to Repetier or use Simplify3d.