Did you tune your heaters and did you perform a extrusion calibration test?

@bpislife starting to look very good!

M561 and G92 S2 do exactly the same thing. M561 was implemented a long time ago. When I implemented mesh bed compensation, I added G92 S2 to keep the relevent commands in one place and make them easier to remember.

@yatinsd
M92 X100 Y100 Z100 E130 ; Set steps per mm

if all three (x,y,z) steppers use the same tooth count pulley, and the steppers all are the same type (for eg. 1.8 deg or 0.9deg per step) then the M92 X Y and Z values should be equal

After this is corrected then you can move on to the other two factor, the delta radius and diagonal rod length.

@timcurtis67
in the end it was that my E stepper acceleration was set too high.

Still cant understand why sending the command alone works while during printing not

@bartolomeus I recall the strongly recommended E acceleration setting for the Nimble is 120. ie try everything else first.

For a direct drive extruder like the Titan Aero like I see in your picture can still benefit from pressure advance. A value of 0.05 works well for me with PLA.

Your prints are starting to look pretty good.

I suspect there is an error in your homing files, so please post homez.g and homeall.g. Are you using the bltouch for Z homing, or a separate endstop switch?

After updating Firmware to 1.21 and tweaking a few settings it now works fine. Thanks again

@timcurtis67
thank you!

Hum ok,

So with my 200 steps motor and with à 1.25mm pitch rod it means 200 / 1.25 = 160 full steps per mm

and a 1mm / 160 = 0.006mm per step

It means à prcésision between 0.006mm and 0.024mm (4 steps)

Am I right ?

@t3p3tony said in M558 - What is 'Dive Height'?:

The Dive height is the height above the (assumed) height of the bed that a probing move will start:

The H parameter defines the Z probe dive height, which is the height above the trigger height from which probing starts. The default is 3mm or 5mm depending on firmware version. You may wish to increase it during initial calibration.

https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCartesianPrinter#Section_Z_probe_section

I have updated the gcode page as well to explain that.

@dc42 said in M558 - What is 'Dive Height'?:

It's also the maximum depth below the assumed position of the bed that probing will go to try to find the bed.

Thanks for the clarifications, @T3P3Tony & @dc42!

What type of bed heater is it? If it's a PCB bed heater, those are frequently under-powered. I think one of the problems is that the Chinese manufacturers don't control the copper thickness very well, so the heating power varies a lot between different samples of the same PCB heater.

If your PSU has a voltage adjustment pot, you can turn it up to get extra bed heating power.

The VIN voltage measurement on the Duet uses 1% tolerance resistors in the voltage divider, and the +3.3V supply as the voltage reference. The output of 3.3V regulator chip has a tolerance of +/-2.5% worst case and +/-0.5% typical. So even if you are really unlucky, the voltage reading shouldn't be significantly more than +/-4.5% off.

I have only used one type of PETG and thats the CF filled version from 3Dxtech and "extra" after retraction is a must. On a Titan Aero or Aqua with .4 nozzle 1mm of retraction with .5-.75 on restart is good. I haven't been able to find the right setup using pressure advance yet so those are the settings without it. I get similar results of starving on restart if I don't use the .5-.75. Just an FYI I also run the bed at 90c (40c enclosure) and 260 on the HE which results in excellent printing and bonding other than that occasional turd that falls off the nozzle

@hobsie so far the print quality with these belts has been phenomenal. If they are fake they are good ones. I think the biggest thing I noticed about them is that they are all cut very straight. The other belts seem to have a bit of wander. These are dead straight and they stay centered on the pulleys. They also sound quieter. I'm very pleased.

0_1527542401436_385AB447-A304-4B57-9116-43E658E382E7.jpeg

In firmware 1.21 and earlier, the MaxReps figure in the M122 report would indicate whether you were pushing the controller too fast. MaxReps of 50 or less was good, 100 was just about OK, more than 100 means that you need to reduce speed and/or microstepping. A side effect of MaxReps getting too high was web interface disconnections, because the MCU was spending all its time generating step pulses, leaving no time to service the network interface.

In firmware 2.0 MaxReps is monitored dynamically. If it gets too high, a short pause is inserted. But it looks like I need to do some more work on this. I think I understand what is going on and I will fix it in the next RC.

Here are three options:

Set up a bed.g file as if you are using the old 3-, 4- or 5-point bed compensation. In the G30 commands in that bed.g file, instead of using Z-9999, use the actual height error at the probe points.

Set up a grid using M557 and run G29 mesh bed probing. It will generate a heightmap.csv file. You can edit the height errors in that file (in DWC) to be the actual height errors at those points. Use G29 S1 to load that height map file.

Put a piece of paper on top of the buildtak, calibrate the Z probe trigger height when using that piece of paper, set up a grid using M557, and run G29 mesh bed probing. Then you can remove the paper and subsequently run G29 S1 to load the height map file.

BTW it may be that your gantry os sagging, rather than the bed is bulging.

@chapelhill I am using this https://www.thingiverse.com/thing:2206664 + a thing I made https://www.thingiverse.com/thing:2868944

It is pretty accurate/repeatable.

@peirof said in Height adjustment:

Regards,

a question, I do not know why, I will have played ... but since a few days ago I have a problem, it is not very important, but if something annoying ... I explain it.

First I will explain what I do before each impression:

1- Home the printer
2- Under the Nozzle until you touch a piece of paper with DWC
3- I define this point as Z = 0 (G92 Z = 0)
4- with DWC I raise the nozzle about 100 mm
5- I raise temperatures to work
6- I apply ABS Slurry
7- I load the filament, and with DWC, I extrude about 100 mm
8- Finally I print ... but ...

Start printing very separate from the bed, so with the microstepping I have to lower the nozzle about 2.5mm.

For some time now, it's like that ....

What should I do to start printing closer to the bed? (although then I ask for it with the Microstepping) Before I started more stuck, I do not know if I changed, before I had to lower the Nozzle so much.

You probably have a G28 homing command in your slicer start script, which undoes the G92 Z0.