![]() ![]() I have better results with lower flow rates (dia 0.4 or 1900%), but more testing needs to be done. Filament diameters of around 0.38 translate to the 2200% cmeyer posted (flow rate factors in quadratic, so use fine steps when adjusting it). ![]() Flow rate percentage adjustments mess up the ‘layer view’ in Cura (from years of experience with an Ultimaker 2, I find this one of the most helpful features in Cura). Keep in mind that you may have to find a physical solution for levelling the build bed when using Cura.ĭ) With the current version of Cura (v3.3.1) it is better to adjust the flow rate of molten filament via the filament diameter, than the flow rate percentage. The nozzle is too far away from the bed, if the individual lines can be easily separated and do not stick together.)Ĭ) Up Studio allows for an 9-point calibration routine for the z-axis. The nozzle is too close to the bed, if the brim thickness (z-direction) gets to thin and translucent. If you use a brim around a test-model in Cura, the correct height is achieved, if the individual lines that make up the brim squash together nicely. As we are using the True Touch Probe, after auto leveling, the 9-point martix compensation values and the nozzle height value are all measured. (I think a painfully precise calibration is overkill. I did compile my ‘own version’ from the start code by chrisevich. Perhaps the info below will help someone in the future:Ī) I used the start and end code from chrisevich ( #11) which worked nicely for me.ī) the z-axis calibration code posted by cmeyer never worked for me. I just wanted to thank everyone who contributed to this thread - it helped me tremendously when setting up my Cetus3D MkII with Cura. G1 X50 E360 F300 extrude a 5cm purge line The Tiertime Cetus 3D Printer comes with the following specifications: Maximum Build Volume: 7L x 7W x 11H. G1 X2 Y178 F5000 move to back right corner Tiertime Cetus MK3 Specifications: Check price on Amazon. ![]() M206 X-180 offset X axis so the coordinates are 0.180, normally they are -180.0 Some of the settings I'm using (start/end g-code. For the same reason, you should always re-generate your gcode files when your offset changes. Don't run somebody else's gcode w/o knowing what you're doing, because the nozzle offset is part of the gcode, so you can scratch up your plate. Do the paper test and use a gcode file something like this:p.p1 cmeyer 02:41 edit CAUTION Your chances of damaging something are greater when you run gcode. the nozzle offset may be different than in Cetus Studio. make sure your nozzle offset is correct in the starting g-code ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |