One of the theory's goes that you can set temp below the "max" which is controlled by the firmware which it gets from the cartridge setting but can't go above the "max", the other is that while the initial temp might be set by the firmware gcode will over ride that regardless.

I've never tested it myself, my cartridge resetter set the nozzle temp at 240 and I've never needed to go above that. Obviously the temp set on a stock cartridge is fine for the material XYZ puts in it so I never changed that either.

Those who have advanced the "can't go above max" theory have used it to explain why a file with too high a setting won't print. The printer is waiting for the temp to get high enough and since it's above the max it will never get there and printing won't start.

Sadly I can't tell you which is the truth on this subject. I do know you can go lower temps in the gcode than the cartridge is set for on rev G firmware and that it will respect that.

XYZWare version: 1.0.8
Firmware: 1.1.J

Weekend Avenger: Yes, I agree about the XYZWare being limited and a bit slower than Slic3r. Also, am I right in thinking that perhaps the DaVinci does not support all the geocode commands that Slic3r puts in the final .gcode file?

I wonder if setting the temperature to high, for example, would cause the file to not print?

crocky: thanks for providing me your header info. I notice that your temp is lower than mine, and you have a T0 command thrown in. I'll try yours when I get back to the printer a week from now.

Now, if I can just figure out the printing problems from the other thread.

Excelsior!

If I actually want a semi valid "time to completion" guess, I'll slice in the modded version of XYZware so I can have a pastable header that has all the right numbers, though it won't affect the print at all.

XYZware is just missing so many important features that it prevents the printer from operating at the level that it should.

That is the only g-code that I put at top of the print, I copy it over to replace the first 20 or so lines in the g-code file. Works a treat and because I am on a mac I don't need any other conversions.. Works a treat with XYZ

New user here, although I've been reading these forums for awhile. As the topic says, I'm looking for a guide to use Slic3r with the DaVinci. I've been through the excellent tutorial on Scribd, and I have been able to use Slic3r to slice models with very nice supports where XYZWare wouldn't create ANY supports even when I check the box. Also, I've loaded the DaVinci config file into Slic3r successfully and generated the .gcode with no problems.

I export the geode file from Slic3r. Exports great and faster than XYZWare. I edit the .gcode file as described elsewhere with the proper codes in TextEdit. I save it. Then I drag and drop it into XYZWare. It displays fine in the software. I send it to the Da Vinci, it uploads (though slowly) and then...nothing. I might get a flash from the printer, but it doesn't print.

Here is the header code=======
; filename = composition.3w
; machine = daVinciF10
; material = abs
; layer_height = 0.2
; total_layers = 173
; total_filament = 0.00
; extruder = 1
; perimeters extrusion width = 0.40mm
; infill extrusion width = 0.67mm
; solid infill extrusion width = 0.67mm
; top infill extrusion width = 0.67mm
; support material extrusion width = 0.40mm

G21 ; set units to millimeters
M107
M190 S100 ; wait for bed temperature to be reached
M104 S230 ; set temperature

M109 S230 ; wait for temperature to be reached
G90 ; use absolute coordinates
G92 E0
M82 ; use absolute distances for extrusion
G1 F1800.000 E-1.00000
G92 E0
G1 Z0.300 F7800.000

===========
Am I missing something?