See https://www.duet3d.com/wiki/Using_mesh_bed_compensation#Checking_the_trigger_height.

@DjDemonD:

@Dougal1957:

with the nimble the original suggestion recommended a jerk of 1 which really slowed everything to a snails pace increased to 40 and it became usable again.

Doug

Yes, that might have been it come to think of it, well remembered. I'm using 40 too, no issues now. Did a 1 hour print on a caliblock with the nimble on the kossel xl, I use very minimal pressure advance with the nimble, the idea being just to account for the twist in the cable before it generates movement at the extruder.

What is your pressure advance setting, may I please ask? I'm moving to a nimble as soon as it gets delivered.

Also, DjDemonD, thanks for your mount design for the nimble on the smart effector. I'm planning on using that.

Glad you got it fixed. Personally I don't use config-overide.g for exactly the reason that you have discovered. I prefer to just have the one config.g file.

I can't think why changing the motor current should completely stop the extruder from working. The only thing that leaps out is that in the commented out line you have M906 X Y Z E but you've only set it for one extruder which may explain why only one extruder works. In the uncommented line you have the order as M906 X Y E:E Z. I wouldn't have expected the order to be critical but you could try M906 X800 Y800 Z1200 E1050:1050. BTW, 1,050 mA is a strange number to use. How did you arrive at it and why do you have a higher motor current setting for the extruders compared to the X and Y axes?

got it, feeling kinda dumb now, lol looked right past it more than once 😛 had 2 instead of 1 on M574 for X and Y must have done it in the config tool.

works perfectly after updating to the new firmware, thx.

Yes, change the M190 command to M140. Also put the T0 command before the G28 if you want to start the extruder heating before homing.

i am using the last stable 1.19.2 i think. thank you very much i will try that.

@Yonkiman:

Instead of a brush, take a look at this wiping method: https://youtu.be/E0y7x5uajUM?t=4m18s

Seems better than a brush because it's self-cleaning and wiped filament shouldn't accumulate anywhere except the trash can.

A wiper and a steel brush is how Stratasys has been doing this for years. I am using a thin piece of PTFE with a brass brush behind it. I have a bin that catches the purgings. An important part is extruding enough material so that it weighs enough and easily detaches from the nozzle rather than getting bunched up around and stuck to it.

0 Step errors, changed to the settings recommended now the lowest deviation I can get is .039 instead of .033 but the twisting is almost gone. It is still there but barely and nowhere near as much as it was.

The S parameter is the speed you get at the top end of the temperature range and above it.

That will happen if you use mesh bed compensation and the bed is sufficiently uneven that the Z speed changes needed to implement it are constrained by the Z jerk setting. Try a higher jerk setting if your Z axis can handle it.

The power outage protection works faster in firmware 1.20beta4 so I suggest you upgrade to that version first. Read the upgrade notes, in particular the parameters to the M911 command have changed.

Thank you.

Ok - I think I found the culprit!

I was running DWC behind an nginx reverse proxy (proxy_pass).
Apparently this causes problems: [c]proxy_set_header Host $http_host;[/c], because it will append the port number the the Host header [c]10.0.0.42:80[/c], which then, I think, causes an error here: https://github.com/dc42/RepRapFirmware/blob/871c22c0c5b1c5479488014f7d428efe423c38c7/src/DuetNG/HttpResponder.cpp#L360
Removing the proxy_set_header, which was part of include proxy_params, resolved this issue.

All in all a bunch of weird configurations & errors on my side. Still surprised that the config.g just disappeared.

OK, that fixed it. I looked at the deployprobe.g and retractprobe.g and noticed that the M280 codes included I1 at the end. Removing these has resolved the issue.

That thermistor has an unusual resistance at 25C, so it's likely to be hard to find a good match. The closest I found was https://www.digikey.co.uk/product-detail/en/epcos-tdk/B57891M0682J000/495-3071-ND/652254.

Can you adjust the firmware or the hardware that is used with it so as to accommodate a different thermistor?

I'm glad you solved it - thanks for letting us know.

@timcurtis67:

BTW deckingman, I think your printer is amazing and I love the experimental work you do with it. The results you post have helped many of us here.

Thank you for your efforts!

Ahhh, thanks man. A bit of positive feedback is always welcome.

And what about low PWM frequency? Not enough thermal inertia of the bed heater or somthing else?