@haggan90 said in Belt driven Z (dropping problems ofc.):
I just tried a larger print overnight now, around 600g of filament, but I can still see some random lines on the part..
Could this be because I'm using a 0.8mm nozzle and 0.4mm layer height?
Would the artifacts be less if I go down to a 0.6mm nozzle you think?
0.8mm nozzle = 0.5mm square area, 0.6mm nozzle = 0.28mm sqare area.. so alot less filament...
Need pictures for this. Also best moving that into a seperate thread as your more likely to find others that can help too. However I heard layer thicknesses upto about 60% of nozzle diameter are ok. I run 0.3 on a 0.5mm nozzle and 0.24 on a 0.4mm nozzle.
So I've done further tweaking, and i might be onto something...
I ran M48.g as describe by this post: M48
G32 bed probe heights: -0.024 -0.013 -0.021 -0.012 -0.025 -0.020 -0.025 -0.030 -0.022 -0.041, mean -0.023, deviation from mean 0.008
Before I did this i was tweaking my bed according to the heightmap.csv
9 points probed, min error -0.048, max error 0.136, mean 0.029, deviation 0.054
Height map saved to file heightmap.csv This was done when heated at PLA Temps
Its looks like the following:
RepRapFirmware height map file v2 generated at 2019-06-28 01:25, min error -0.048, max error 0.136, mean 0.029, deviation 0.054
0.063, 0.026, 0.043
0.064, -0.007, -0.048
0.136, 0.029, -0.043
When cold it looks like the following:
RepRapFirmware height map file v2 generated at 2019-06-28 01:14, min error 0.014, max error 0.267, mean 0.111, deviation 0.071
0.161, 0.090, 0.110
0.154, 0.051, 0.014
0.267, 0.101, 0.048
The question is, what do you reckon, do you see these tweaks improving my first layer...?
For any one interested in the files, visit the Github Page:
@vacalos I have no experience with the prometheus splitter
I have used this splitter for some time : https://www.thingiverse.com/thing:3039887 with a e3d clone
At the moment I am using no splitter as I have a new printer and want to get other stuff done first before playing a round with a splitter again.
My biggest issue with the splitter was changing the filament. I couldn't get good tips on the filament for PLA at all. It did work reliable with abs only and like 90% with petg. I have tried a lot of different settings to get better filament tips without having to adjust the settings all the time for different materials or brands without success.
Next time I will build a cutting mechanism into a splitter to get rid of that problem.
Image of bed compensation heighmap AFTER linear rail Mod:
Its very good.... but i have to say that before mod, results are better.
Image of bed compensation heightmap BEFORE linear rail Mod, stock carriages:
I have to say, that results BEFORE they were strangely good...
These seem like sufficiently narrow deviations to me (see below). I run a 600mm (24") delta and what I settled on is to do a calibration, an M500, and a mesh every so often (particularly if I work on the printer), and do a calibration only in the start G-Code of every print.
I use a single value for L. Not right or wrong, just what I do. I also NEVER run the number factors in a calibration that can change L; my experience with that makes me shy away from it.
I run a bed.g generated from:
bed.g file for RepRapFirmware, generated by Escher3D calculator
; 16 points, 8 factors, probing radius: 280, probe offset (0, 0)
And config.g (or override) entries of:
M558 P5 R0.4 H5 F500 T18000 ; P5=Effector. R0.4 = Recovery time after each probe. H5 = Height from which to probe. F500 = Feedrate mm/min T18000 = rapid between probes, mm/min
G31 P100 X0 Y0 Z-0.1 ; Set Z probe trigger value, offset and trigger height
M557 R300 S75 ; Define mesh grid
; config-override.g file generated in response to M500 at 2019-01-18 16:32
; This is a system-generated file - do not edit
; Delta parameters
M665 L720.280 R328.965 H626.773 B304.0 X-0.173 Y0.125 Z0.000
M666 X1.176 Y-1.179 Z0.003 A-0.50 B0.11
Resulting in a height map of:
RepRapFirmware height map file v2 generated at 2019-05-25 13:51, mean error -0.065, deviation 0.040
0, -0.080, -0.135, -0.070, -0.046, 0.026, 0
-0.066, -0.065, -0.074, -0.062, -0.075, -0.074, 0.034
-0.103, -0.073, -0.106, -0.090, -0.094, -0.041, -0.052
-0.044, -0.065, -0.040, -0.089, -0.085, -0.090, -0.059
-0.105, -0.066, -0.075, -0.081, -0.086, -0.059, -0.120
-0.145, -0.058, -0.013, -0.038, -0.067, -0.081, -0.131
0, -0.102, -0.005, 0.011, 0.022, -0.024, 0
You can see that with my large-ish bed, I'm satisfied with final deviations in the .04 range. You are getting things about half that. Looks good to me.
P.S. Looks like five months since I bothered to do an M500 after a calibration (since I do one every time) and about a month since I did a mesh.
How about placing a force sensor between the lead screw and the piston and connect it to something that can read it? This will also give you the pressure.
Ali has many such sensors, e.g.
@nightreaver said in BLTouch Self-Triggering during multipoint probing:
@dc42 Can you confirm that M558 A has upper limit? When I set it to 15 with works okay, when I set it to 50 it seems like the limit goes down to A2 or something. Is this right?
From the Bug Fixes section of the firmware 2.03 release notes at https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md:
Setting M558 A parameter to anything >31 set it to 0 instead of to 31
Yes it would be possible to calibrate nonlinear extrusion using the filament monitor. This is unfortunately one of many things that I don't have time to implement right now. You could do it semi-automatically like this:
Create GCode files to print, that extrude into air at various speeds while also moving the print head in the XY plane.
At the start of each file, put the filament monitor in calibration mode (M591 Pn S0).
At the end of each file, use M591 Pn to report the calibration parameters, which includes the measured/commanded extrusion percentage.
You could combine all these files into a single file, using M226 to pause between the sections (which restarts the calibration).
Looks like your connection to Duet3D was lost, please wait while we try to reconnect.