3/28/2023 0 Comments Cetus3d mkii x axis# note it is invalid for both the above be 0 Mm_max_arc_error 0.01 # The maximum error for line segments that divide arcs 0 to disable #mm_per_line_segment 5 # Cut lines into segments this size Mm_per_arc_segment 0.0 # Fixed length for line segments that divide arcs, 0 to disable # Robot module configurations : general handling of movement G-codes and slicing into movesĭefault_feed_rate 4000 # Default speed (mm/minute) for G1/G2/G3 movesĭefault_seek_rate 4000 # Default speed (mm/minute) for G0 moves # NOTE Lines must not exceed 132 characters, and '#' characters mean what follows is ignored This results in the axis set to X180.00, Y0.00 and Z180.10 due to the 4.90mm offset when callibrating. This writes the setting in the config-override file M500 #Store new zero location permanently (M500). MOVE NOZZLE DOWN GRADUALLY TO ALLOW PAPER TO FIT UNDER G1 X90 Y90 Z10 #Move nozzle to middle of plate at 10mm above zero I then calibrate the Z axis using a piece of paper under the nozzle in the center of the build plate using the following GCode: G28 #Home all axis My Smoothieware settings are down the bottom of the page - note gamma_max of 185. I'm a bit surprised there isn't more info on the TinyFab support site to allow a new user to get started. I'm so stuck and would appreciate any assistance. Cura and the Cetus3D but I am not sure if they involve the TinyFab CPU or if they are just for printing GCode in UpStudio as most of the posts are over a year old now. I am totally willing to experiment to get print quality to match / exceed what I was getting in Up Studio but I am having a lot of difficulty getting started. I am at the stage of trying to get a 20mm cube printed and have decided to use Cura for slicing and producing the G-Code and then issuing the GCode via Repetier-Host which I think TinyFab himself uses. I have now spent days getting the BLTouch installed and 3 point leveling working. I have my Cetus3D MkII with TinyFab CPU installed. First of all, apologies for the massive post. Only_retract_when_crossing_perimeters = 1 This is my final config: # generated by Slic3r 1.2.9 on Sun May 6 21:52:40 2018Įnd_gcode = M109 switch off extruder\nG0 Z-2 \nG0 X-178 Y2 \nM2 end of program Here ( ) you can see a comparison between prints using the Cetus slicer and g code generated in Slic3r with my settings. My settings are far from ideal and just a first step to use this amazing little printer at it’s full potential The initial idea behind this was to even out a slightly uneven bed. I printed the first layer of the raft at 350% thickness to close the gap between the nozzle and the bed. To read the actual value I used the calibration function in the cetus-program. To ensure that the nozzle won’t crash the bed I manually wrote some g-code to move the nozzle to all 4 corners and approach the bed slowly to 0.5mm, then I measured the gap between the nozzle and the bed with a feeler gauge. My Z-offset is 0.2mm above the print bed. The additional homing seems not to be necessary because the printer has to be initialized after startup anyway. After removing the additional “G28” (homing commands) everything worked fine. When I started to find the correct settings I first ran into the problem that every g code I wrote tried to move the x axis out of the limits. After playing with my new Cetus MkII for a few days I finally managed to find some useful settings for Slic3r.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |