nice guild help me lots very clear and all the info is in one place > but what peramiter did you change to make a 120 point map i would love to give mine a better map
You set the grid with M557. Here's what I run in the morning as part of my MeshLeveling macro file: Code: M557 X09:291 Y16:199 S20 ; Define a 15x10 point grid for measuring the bed ; This assumes G31 used Z-Probe offset of x=31.7 y=15.3 Be careful though! You can easily define a grid that you cannot execute. If the probe gets positioned at a point where it's not over the bed, you can get a head crash For what it's worth here's my last leveling run:
thanks for the help i have a 350mmx 350mm bed with a 250mm x 250mm print size and as long as i dont go in minus in the x and y im golden i will use full bed size at a later point still working out the bugs in my design also my hole bed is in the red and not in the green have i missed a step on the set up
That begs many questions. What did it look like while that was running? What sensor are you using to measure height above the bed? What is the bed surface?
hi i found my problem to which you may are may not want to add a note in your guild is i did not change the m574 comande i still had this M574 X1 Y1 Z1 S0 and now ive changed to this M574 X1 Y1 Z0 S0 my machine was set up for micro switching at first and added dc42 A_K_A David Crocker ir sensor also a note about changing the amount of points probed by changing the S40 in the M557 command and i think your guild would be complete p.s not dissing your guild helped me loads big thumbs up from me
I just completed the upgrade to Duet 1.19 and am looking at the firmware release notes. https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md It seems there are some things to look out for: Height map files created with firmware 1.18 or earlier cannot be read by firmware 1.19, so you will need to run G29 S0 again to generate a new heightmap.csv file Height map filenames in G29, M374 and M375 commands must now be enclosed in double quotes Important! If you use an IR Z probe or some other type that does not need to be deployed, delete the files sys/deployprobe and sys/retractprobe.g if they exist, because they are now called automatically. You can do this in the System Files Editor of the web interface. If you have more than 32 probe points in your bed.g file, you will have to reduce the number to 32 YIKES !
i did it. Very easy to get bed leveled with lead screw. Works very well and z moves much smoother now with two driver. I did macro for this and i use bed.g for full mesh leveling.
@Ephemeris your memory is indeed better than mine. Finally these release notes were not such of a big deal. @potti5 so I have to add this to my MOAU list? (mother of all upgrades)
holy crap there is a difference of almost 0.6 mm between highest and lowest My values of the rumba mesh leveling show something similar. Something is off with my left y axis for sure, because its squeeking ( only finding that out now that the motors are so quiet I can fix the rest with shims on the rear of the bed
Would you be gentle enough to let me know your shopping list please and how to guide? I built printers and never used any auto-bed mesh levelling but I wish to introduce it on one particular machine with an aluminium plate as a heat bed and a thin sheet of borosilicate glass 2mm thick. Thanks in advance.
Apparent twist of the bed in 3D printers is frequently not caused by a twisted bed. In bed slingers it is usually caused by the two rods supporting the bed carriage being slightly twisted relative to each other instead of parallel. In machines with a bed that moves in Z, it is typically caused by the Y guide rails not being quite parallel.