Regarding the nozzle hitting the bed:
The gcode is trying to print at Z0, so unless you have adjusted your limit switch to trip at least a minimum layer height above contact, that's an issue. It's much better to actually zero your bed for contact, or just shy, then print at a defined positive Z value.
Recommended Posts
Dim3nsioneer 558
As you pointed out the generated gcode is missing UM2 characteristic start and end gcode. There must be a thread here on the forum, started by @Nicolinux iirc, about how to implement standard UM2 start procedure by RepRap gcode.
The UM2 might need volumetric RepRap gcode (I'm not sure about this because I always use UltiGCode on the UM2). From what you posted I think this GCODE uses rather filament lenth than filament volume for extrusion.
Link to post
Share on other sites
federicogiacomarra 0
Hi thanks,
I found few interesting post as well talking about the start_gcode or prefix, from @DidierKlein and @Das_enginer...
https://ultimaker.com/en/community/view/6190-startgcode-for-um2-not-changing
https://ultimaker.com/en/community/view/7885-kisslicer-1407
I found also the start_gcoce and the end_gcode in the github of the gcode generetor:
https://github.com/ProjectSilkworm/Silkworm/blob/master/GeneratorComponent.cs
the good news is that the Ultimaker 2 can read this gcode, tha bad one is that when i tried to print a test, the nozzle hitted the printind bed... basically the gcode override the machine settings...
What is the problem at this point? the g-code has a wrong z axis i can edit somehow or the g-code has a wrong "effect" on the um2 overriding the setting of the machine....
the example g-code above is this, a wireframe box lenght printing...If i can solve the problem of the nozzle hitting the printing bed i may be able to make a proper print test..
http://projectsilkworm.com/wp-content/uploads/2012/10/wireframe.jpg
Link to post
Share on other sites