Some notes based on questions I've gotten - test your sensor, mine's marked for pitch & roll, but be sure you know which is which before you mount it. The output is Actual Roll, Deviation from starting Roll, Actual Pitch, Deviation from starting pitch… as I have it in the code above. There are lots of other outputs you can enable, just by removing the comments for them. The ones I'm displaying are the kalman angles. For testing, especially with a different sensor, I'd enable more of the output.

maxDev is defined as 10... and not currently used. You can see I've commented out the bits for it in the output section, but that's where you could set it so that if the angle is more than 10 degrees from the start angle, send a hard stop / pause / warning or whatever to your printer.

Because you haven't done delta calibration yet? See https://duet3d.com/wiki/Calibrating_a_delta_printer.

🙂

@crispy:

@dc42:

Which firmware version were you using when that happened?

First noticed on 1.10, but also seen on 1.17-based firmware. But it was a lot less frequent on 1.17.

If you can find a print that reproduces the problem reliably in firmware 1.18.1 then I'll try to work out what is happening. You can help by running M122 after layer shifting occurs and reporting the Step Errors count.

To me, it looks like the part cooling is not as effective as it should be. In particular, I think that it's cooling one side better than the opposite side. I also have a Kossel XL and have replaced the part cooling fan ducting with something that provides air from more directions rather than just the single direction that the original duct features. I would say that improved it for me although I don't think I yet have an optimal solution. I often have to rotate parts on the build plate to get the most effective cooling. Unfortunately, that's not an option with your current model. In the past, I have just positioned a large fan off to the side of the build plate to move a large volume of air. Incidentally, what temperature are you printing at? Can it be reduced without the quality suffering?

lol i spoke too soon my new extruder stepper's shaft is too long. BRB getting out the dremel… 😉

I have a counterweight connected to my flying extruder to solve the problem of the hotend descending when the power is off. Works like a charm.

1.18beta1 is old, I suggest you upgrade to 1.18.1.

When you run auto tuning, the target temperature should be at least 10C lower than the temperature limit set by M143.

I am in the process of rewriting the Wi-Fi firmware.

Thank you!

The Duet has been used to run laser engravers before. There is data least one thread about this in the Ormerod or Duet forum at reprap.org.

Yes it can be used with the Duet wifi, you hook it up the same as you would to any other control board

I just updated the firmware to 1.18RC2 and the issue is fixed. Thank you so much for the help!

I think the diagram in the previous post is how they are suggesting you connect the probe to other equipment, not what is inside it.

I suggest you connect the brown and blue wires to the always-on fan connector, and the black wire through a small signal Schottky diode to the endstop STP pin, cathode to the black wire.

Thanks for all the info! I truly appreciate the help I'll check out the options and see which one is more will fit me better thank you.

Thanks for the help! Okay, sounds like trial and error it is. I asked as there is a section in the Wiki that has not been filled in about tuning stuff.

I have discovered one thing that I should have been obvious. You cannot use DWC to move the motors to see if there's any change in speed unless you change the move speed in Settings-User Interface-Machine. The default speed is limited to 100mm/sec.

Your config.g file should have a M501 command near the end, which causes config-override.g to be run. So the values in config-override.g override earlier settings in config.g.

I use both a phone/tablet and a PanelDue. I find the web interface on the tablet completely usable on the 7 inch screen (so a 10 inch will be better).

I do find the PanelDue a bit quicker to access key functions but that's at least partly because it's tethered/mounted on the printer so i don't have e to locate it in my office.

We're planning a modest increase in the very near future, and a greater increase in firmware 1.19. For Nema 23 motors, 2.3A rated current is a good choice, and is what I am testing with.

yes, but the interface speed seems odd (see output below).
If I remove the card and run M122 again, it says 'SD card 0 not detected, interface speed: 0.2MBytes/sec'.
If I start the Duet without card and run M122, I get 'SD card 0 not detected, interface speed: 30.0MBytes/sec'.

Diagnostics Used output buffers: 1 of 32 (2 max) Platform Diagnostics: Memory usage: Program static ram used: 13132 Dynamic ram used: 81780 Recycled dynamic ram: 3392 Current stack ram used: 2752 Maximum stack ram used: 3584 Never used ram: 29184 Last reset 00:00:14 ago, cause: power up Error status: 0 Bed probe heights: 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Free file entries: 10 SD card 0 detected, interface speed: 0.2MBytes/sec SD card longest block write time: 0.0ms MCU temperature: min 24.5, current 26.6, max 27.6 Supply voltage: min 0.4, current 0.6, max 0.9, under voltage events: 0, over voltage events: 0 Slowest main loop (seconds): 0.000512; fastest: 0.000042 Move Diagnostics: MaxReps: 0, StepErrors: 0\. Underruns: 0 Heat Diagnostics: Bed heater = 0, chamber heater = -1 GCodes Diagnostics: Move available? no Stack pointer: 0 of 5 macro is idle http is idle telnet is idle serial is ready with "M122" aux is idle file is idle Network Diagnostics: WiFiServer is disabled SPI underruns 0, overruns 0 Webserver Diagnostics: HTTP sessions: 0 of 8 ok