Ok found something.
The config.gcode had M83 in the beginning so the printer was in relative move for extruders while the slicer do it in absolute mode.

I have the same Slicer settings as i did before changing to Duet and then it did work fine and when printing the speed on the extruder is to fast by a factor of 100 or more, but the xy-axis moves slower than it should.
Seems like the speed for extruder is multiplied by some big number or the speed on xy-axis is by i small number.

I did test G1 E100 F300 now and the extruder slips on the filament, but i think that is strange since i did print fine before and it could print fast without problem

My stepper settings now and max speeds are exact same as it was on the old controller card, so that shouldn't be the problem.

Ok now i set it to 93 steps per mm and a max speed of 25 mm/s, and now it extrudes exactly 100 mm filament when extruding only 1 mm/s.
This is from the original settings.

But when printing the heads moves very slowly and the extruders spins to fast for it.

Why would the extruder move faster and the head slower when printing than when moved from the console?

I calibrated it when printing and then i hade to set it as low as 0.076 for it not to over extrude.
But i found that strange and decided to do the extruder calibration from the beginning, before that i had found 115 steps per mm extruded the correct amount, both 5 mm and 100 mm.
So i dont understand how it can differ so much.

I tried now with 100 mm again and if the steps per mm is higher than 30 it starts to slip.
But i think it needs to be higher, because it just extrudes 34 mm filament with that setting.

Another strange thing is that when printing it goes very slow, even though i have raised the acceleration to 8000.

I calibrated the extruders steps per mm by drawing a marking on the filament and extrude 5 mm from the g-console and measuring and adjust the steps per mm until it got right. But when i start a print the extruder spins way to fast and blocks it get blocked between the nozzle and bed.

When i extrude with g-code from the console the settings is 1100 steps per mm, but when printing i had to lower it to 0.076 for it not to over extrude.

Cant figure out what it can be.

@dc42:

How did you measure the trigger height?

By this method
https://duet3d.com/wiki/Using_mesh_bed_compensation

But i found the problem, in homeall.g this line "G92 Z2.5" was at the end, so everytime a print started it the printer did a homeall before starting the print and set the Z-postion to wrong relative level.
I commented away that line and after that it stops above the bed.

Gotta get some feeler gauges to measure the height more exactly and do a better calibration though, but problem solved

Hi
I just installed a Duet WiFI with a BLTouch as Z-probe on my Creality CR-10 and it works fine when moving and extruding now, and it can do Bed Probing and mesh leveling.
But when printing the head travels down in to the bed, so i do an emergency stop and put a paper under the head, and then raises it until it as hard pressed between as when measuring the trigger height. The distance i hade to raise it was the same as the trigger height.
I tried some different trigger heights in the config but it doesn't change anything and it has to be raised the same height anyway.
The trigger height is 0.92mm

My config has these lines
M574 X1 Y1 Z1 S1 ; Define active high microswitches
M558 P5 X0 Y0 Z1 H10 F200 T500 ;
G31 P10 X40 Y-25 Z0.92 ;