It's simple enough to script. I've got an OS-X binary that does the conversion automatically (attached), though I've only tested it on 64-bit 10.9. I expect to have a web service that will include a base64 encode option sometime in the next week, so this is still pretty crude.

You need to have your a slic3r config similar to the one from Jason at github.com/jasongao/DaVinci1.0/. Export the gcode from slic3r. Then run xyzify from the command line. It reads the slic3r gcode file from standard input, and writes the result to standard output. It's not base64 encoded, but the mac version of XYZWare doesn't care (which is why no windows binary).  You can then import the resulting gcode file in XYZWare and print from it.

MWN. Not sure how to run it from the command line, Im a noob! can you run me thru the commands as a example? Thanks!

This new version adds support for Cura files. It will automatically replace G0 with G1 on import.

http://www.mediafire.com/download/j8fz6 … .42.v2.rar

Thanks I think I may already have this version, let me test it when i get home and i will not replace G0

http://www.mediafire.com/download/j8fz6 … .42.v2.rar

peitzgreene wrote:

w34 wrote:

If it is above the print bed to far you can set the z-offset in slic3r to a negative number to compensate for the height difference or try recalibrating and shoot for z-offset of 230-250 on the machine. You can also do the paper method of leveling the bed.

As for the file not starting for slic3r, it may be take a bit depending on your settings in slic3r. For instance if the heat and bed temperatures is set to 210/80 and slic3r is set to 230/100, it will heat for the cartridge temp first, then begin executing the gcode and wait for temp to reach the 230/100 set in the gcode, then it will print. If it does nothing after the 2nd heating to reach your target temps, then something is wrong in the gcode. Check to make sure all start code is removed in the slic3r settings. If that still doesn't work, upload the gcode so I can take a look.

Humm, I can not find the Z offset in Cura. Also 230-250 is the z-offset I have on the machine. And how would one go about doing the paper method on the stock firmware? Here is a gcode that I sliced up with Cura (I really like using Cura other then Slic3r)
Thanks.

In cura, select plugins->tweak at z->then set the z offset to something like -0.2 or however much it may be off by.

For the paper method I turn off the print, put a piece of standard printer paper on the heat bed and move the print head over the corners of the bed. Adjust to where all four starts to barely grip the paper, but you can still move the paper.

I will check out the gcode and see if I can replicate the issue.

Edit: tried the tweak at Z and it looks like it does something different. You will have to manually add it to the start code e.g.
G1 Z0.2
G92 Z0

Edit: Try this file.

K I think I figured it out, plugged into notepad++ and changed all g0 to g1, thought that the software version you made already did that. Working now, thanks for the help

w34 wrote:

peitzgreene wrote:

W34 Got a quick question for you here. So got the exe replaced and everything worked fine. Gcode would upload and it would start heating. Would get up to the proper temperature, then move to about the center about 1-2in above the bed, then would heat up again. After all of that would start printing, but 1-2in to high. In XYZware it looks fine.

I have no idea why it is doing this, any ideas?

I have tried Cura and Slic3r

Cura does what I listed

But Slic3r will not start printing, but it will move to the center and start heating and then stay there and keep heating.

Thanks

Great work by the way.

If it is above the print bed to far you can set the z-offset in slic3r to a negative number to compensate for the height difference or try recalibrating and shoot for z-offset of 230-250 on the machine. You can also do the paper method of leveling the bed.

As for the file not starting for slic3r, it may be take a bit depending on your settings in slic3r. For instance if the heat and bed temperatures is set to 210/80 and slic3r is set to 230/100, it will heat for the cartridge temp first, then begin executing the gcode and wait for temp to reach the 230/100 set in the gcode, then it will print. If it does nothing after the 2nd heating to reach your target temps, then something is wrong in the gcode. Check to make sure all start code is removed in the slic3r settings. If that still doesn't work, upload the gcode so I can take a look.

Humm, I can not find the Z offset in Cura. Also 230-250 is the z-offset I have on the machine. And how would one go about doing the paper method on the stock firmware? Here is a gcode that I sliced up with Cura (I really like using Cura other then Slic3r)
Thanks.

In cura, select plugins->tweak at z->then set the z offset to something like -0.2 or however much it may be off by.

For the paper method I turn off the print, put a piece of standard printer paper on the heat bed and move the print head over the corners of the bed. Adjust to where all four starts to barely grip the paper, but you can still move the paper.

I will check out the gcode and see if I can replicate the issue.

Edit: tried the tweak at Z and it looks like it does something different. You will have to manually add it to the start code e.g.
G1 Z0.2
G92 Z0

Edit: Try this file.

peitzgreene wrote:

W34 Got a quick question for you here. So got the exe replaced and everything worked fine. Gcode would upload and it would start heating. Would get up to the proper temperature, then move to about the center about 1-2in above the bed, then would heat up again. After all of that would start printing, but 1-2in to high. In XYZware it looks fine.

I have no idea why it is doing this, any ideas?

I have tried Cura and Slic3r

Cura does what I listed

But Slic3r will not start printing, but it will move to the center and start heating and then stay there and keep heating.

Thanks

Great work by the way.

If it is above the print bed to far you can set the z-offset in slic3r to a negative number to compensate for the height difference or try recalibrating and shoot for z-offset of 230-250 on the machine. You can also do the paper method of leveling the bed.

As for the file not starting for slic3r, it may be take a bit depending on your settings in slic3r. For instance if the heat and bed temperatures is set to 210/80 and slic3r is set to 230/100, it will heat for the cartridge temp first, then begin executing the gcode and wait for temp to reach the 230/100 set in the gcode, then it will print. If it does nothing after the 2nd heating to reach your target temps, then something is wrong in the gcode. Check to make sure all start code is removed in the slic3r settings. If that still doesn't work, upload the gcode so I can take a look.

Humm, I can not find the Z offset in Cura. Also 230-250 is the z-offset I have on the machine. And how would one go about doing the paper method on the stock firmware? Here is a gcode that I sliced up with Cura (I really like using Cura other then Slic3r)
Thanks.

W34 Got a quick question for you here. So got the exe replaced and everything worked fine. Gcode would upload and it would start heating. Would get up to the proper temperature, then move to about the center about 1-2in above the bed, then would heat up again. After all of that would start printing, but 1-2in to high. In XYZware it looks fine.

I have no idea why it is doing this, any ideas?

I have tried Cura and Slic3r

Cura does what I listed

But Slic3r will not start printing, but it will move to the center and start heating and then stay there and keep heating.

Thanks

Great work by the way.

If it is above the print bed to far you can set the z-offset in slic3r to a negative number to compensate for the height difference or try recalibrating and shoot for z-offset of 230-250 on the machine. You can also do the paper method of leveling the bed.

As for the file not starting for slic3r, it may be take a bit depending on your settings in slic3r. For instance if the heat and bed temperatures is set to 210/80 and slic3r is set to 230/100, it will heat for the cartridge temp first, then begin executing the gcode and wait for temp to reach the 230/100 set in the gcode, then it will print. If it does nothing after the 2nd heating to reach your target temps, then something is wrong in the gcode. Check to make sure all start code is removed in the slic3r settings. If that still doesn't work, upload the gcode so I can take a look.

See above

Anyone know how to fix or reset my Z-offset on a Da Vinci machine?

I have no idea why it is doing this, any ideas?

I have tried Cura and Slic3r

Cura does what I listed

But Slic3r will not start printing, but it will move to the center and start heating and then stay there and keep heating.

Thanks

Great work by the way.

Sorry for the absence guys. I have alot of irons in the fire and I hope some big news for this forum within a week or so.

Thank you for the hard work w34.

Petra what firmware version are you using (I am running 1.1.G)? Any errors? What happens when you click print and then ok?
I will take a look at not being able to export to .3w. I may have uploaded the version where I already started making changes and was integrating slic3r control panel into the export and print feature of xyzware.

Hi w34, My firmware is 1.1.I and the error message "XYZware has stopped working.. windows will notify you when a solution is available."

But it is a "big" complex industrial part I am trying to print. I should know better and rather develop from the bottom up but I'm kind of eager to show the stratasys resellers we can do this without their ridiculous R15 per cc rate that they suddenly came up with, throwing my development of 7 months in the water.

I also saw that there is some support material missing under the duck tale of the part. And I have the Spaceclaim STL prep module that I think would shell the part better. So I'm back on modelling level and I will try your XYZware on a smaller part as well.

But here is the STL and the gcode.. XYZ support US also sent me a generated g-code from the STL part but it had a skirt so even the XYZ support guys couldn't slice the STL with XYZware and used Slic3r or another software to slice this part!

Edit: It looks as if the gcode didn't upload. I guess the 17mb zip is over forum limits. So I can put it in google drive if you want it to test with.

I haven't printed gcode larger than 10mb's, so I haven't run into that issue yet. So I haven't had the need to look at XYZWare's upload procedure yet. Upload it, that way we can take a look and we can see what can be done to optimize/fix/change xyzware's upload procedures for large files.

Edit: It looks as if the gcode didn't upload. I guess the 17mb zip is over forum limits. So I can put it in google drive if you want it to test with.

Sure, put the part up, and I'll test it this weekend.

Petra what firmware version are you using (I am running 1.1.G)? Any errors? What happens when you click print and then ok?
I will take a look at not being able to export to .3w. I may have uploaded the version where I already started making changes and was integrating slic3r control panel into the export and print feature of xyzware.

Hi w34, My firmware is 1.1.I and the error message "XYZware has stopped working.. windows will notify you when a solution is available."

But it is a "big" complex industrial part I am trying to print. I should know better and rather develop from the bottom up but I'm kind of eager to show the stratasys resellers we can do this without their ridiculous R15 per cc rate that they suddenly came up with, throwing my development of 7 months in the water.

I also saw that there is some support material missing under the duck tale of the part. And I have the Spaceclaim STL prep module that I think would shell the part better. So I'm back on modelling level and I will try your XYZware on a smaller part as well.

But here is the STL and the gcode.. XYZ support US also sent me a generated g-code from the STL part but it had a skirt so even the XYZ support guys couldn't slice the STL with XYZware and used Slic3r or another software to slice this part!

Edit: It looks as if the gcode didn't upload. I guess the 17mb zip is over forum limits. So I can put it in google drive if you want it to test with.