I confirm that the DotStar driver was not working. I have now fixed it. The fix will be in the 3.3beta3 release. A preview 3.2beta2+ build including the fix is available at https://www.dropbox.com/sh/dupd9u1xppr1om5/AADYg4guuj2n8LJokVqtK-C7a?dl=0.

Hopefully to be resolved in 3.3

@dc42 i can test that

i´m back at my printer tomorrow and will let you know what are the results

@doctrucker said in Minor Bug: Autotune missing Phase 2 report:

@dc42 this was 3.3beta2, I guess you mean since that release?

Yes.

@dc42 That's fine. I've marked it solved and will stop watching it for updates. Didn't realise we were that close to the limit on the Duet2.

@r3d, this is now fixed in the 3.3beta source code. I have put a binary at https://www.dropbox.com/sh/oxyezimiusnosxa/AAAgjLNKuTL8oEcXgihZqojXa?dl=0.

@dc42 Thanks.

@print3d that's not supported. It's one or the other

@dc42 great!

@ErwinH78 are you sure you are running 3.2beta2 and not 3.3beta2? This is an old post and the current beta is 3.3beta2.

@Phaedrux Sorry, I completely missed your question. I got it resolved - it is a Duet 3 v1.0 board. It was finicky, but I got it updated. I had to redo somethings on the SBC to get it to work.

I still can't upgrade the bootloader though to 2.2

@jay_s_uk that was it thanks.

@ErwinH78 said in Problem with downgrade to 3.1.1:

i got it with bussa. it´s done thx

Glad to hear it.

Just out of curiosity why did you want to go back to 3.1.1?

Frederick

So, i was so dumb that i loaded a wrong filament profile on prusa slicer. It was the same PLA but the wrong color. That particular color is 1.8mm in diameter instead of 1.75. Switched to the correct profile and everything went ok. 😰 😰 😰

Forgot to reply and close this out: running beta 2 now, seems to be alright, but the root cause was my hardware and not the controller or the firmware. A slight oversight on my end was definitely the culprit!

Cheers!

Problem solved, I checked all files and there were a few that had space and tabs. They now have all tabs and the error has been fixed.
Thank you for all who helped👍

Thank you, here is the gcode file: https://we.tl/t-itUE75F1lq
The config files are here: https://we.tl/t-AeXDiQaFII

@o_lampe said in Missing steps 3.3b2 Mini sbc:

@carcamerarig
I'm also missing M669 = declaration of kinematic modell. It should come very early in the config.g. (eg. right behind the paneldue-line)

Not required for a std Cartesian as that is the default also not required for a Delta as the 665/666 set that one up.

SOLVED: Issuing M18 to turn off motors results in probe responding to deploy/retract.

Recap of issue:

Heat nozzle Extrude BLTOUCH probe does not respond to deploy retract

Suspect cause of issue is incorrectly formed stop, sleep, cancel scripts.

Perhaps these scripts should contain M18.

@Phaedrux many thanks for your assistance and input.

FOLLOW-ON Note in case it helps anyone else. This is my end of job script:

G1 H2 Z460 F3000 ; Drop the bed
G1 H2 X1 Y1 F8000 ; Move head near home position
M18 ; Motors off
M0 ; STOP which turns off heaters

I'm not sure why, but whilst there were instructions in stop.g the bed heater was shutdown but not the nozzle. So I emptied stop.g and in my shutdown.g the above results in the bed being parked, all heaters off and motors turned off, which finally results in the probe responding again.