@dc42 Thank you! I found it

@dc42 FYI: in the beta firmware 3.4 Beta 5 this "error" did not display.

For your suggestion: if the three "M569" commands are in line 1-3 it works without any event beeing triggered! THX!!!

@nomukaiki Sure I can share my config + macros. My printer is running but I made some changes compared to your config. E.g. I slowed down movements (your config is really chasing the axes around !)
I need to figure out how I can upload everything to github as this will be my first time ever I use github to upload [...]

@oliof thanks to your suggestions/effort my printer is running! Honestly if I knew that they were not using the orig. board I would have not bought the printer. And I plan to upgrade to the 3 mini as soon as I have enough time. To the "error": there was a change in one of the betas, when it started to appear. Sorry, I do not know any more when it accured but I think it was beta4. And the "error" is on all disabled drivers, not only on 9 as I falsly reported (I had a more closer look into the messages on the printer on restart).

@dc42 Thank you! I found it

@chrishamm I think I did not configure this as the documentation says: do not use it.

@Phaedrux
config.g
pause.g
filament-change.g
03-Change_Filament.txt

Duet Web Control 3.4.4
RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.4

@all: From your reactions I assume, that this is not a standard behaviour. As I used - as a base a configuration - a Caribou3d 320 config including macros I will now search for a macro / service which is not comming ootb and triggers this behaviour.

Question please: if I would want to implement a "shut down the heaters if nothing happens for some time", where would I start to implement it?

I want to use M600 in my slicer to make color changes with a single extruder.
It works flawless - if I am fast enough / close enough to the printer to do the change before "something" shuts down the motors and cuts the temperatures.

What I do not know (and do not find information about) is this "something".
What script / service / ... is shutting down the heaters and motors after some time if "nothing happens"?
Can I change the behaviour? (E.g. motor shut down: NOOOO, bed shutdown: please not, extruder shutdown: yes).

Thank you in advance!

Hi and just to be sure: I really did put them in line 1 to three, so not even a comment line above. If I used e.g. the standard comments before, the warning was there. And if the printer reboots, it complains about all three non exiting motors in the internal log. But just once and with no further noticeable disadvantage.

@dc42 FYI: in the beta firmware 3.4 Beta 5 this "error" did not display.

For your suggestion: if the three "M569" commands are in line 1-3 it works without any event beeing triggered! THX!!!

@nomukaiki Sure I can share my config + macros. My printer is running but I made some changes compared to your config. E.g. I slowed down movements (your config is really chasing the axes around !)
I need to figure out how I can upload everything to github as this will be my first time ever I use github to upload [...]

@oliof thanks to your suggestions/effort my printer is running! Honestly if I knew that they were not using the orig. board I would have not bought the printer. And I plan to upgrade to the 3 mini as soon as I have enough time. To the "error": there was a change in one of the betas, when it started to appear. Sorry, I do not know any more when it accured but I think it was beta4. And the "error" is on all disabled drivers, not only on 9 as I falsly reported (I had a more closer look into the messages on the printer on restart).

@nomukaiki I do have the same error. The "driver 9" does not physically exist and is is disabled in the config. But somehow the web-ui is triggered to send an event every time a browser session is started. I have no other error anywere and the printer is running well. (I: I am not using your config but my own and have now to compare your settings with mine. Thank you so much for posting them!)

Dear all, due to the fantastic support in this forum I could upgrade my Troodon v2 to RRF 3.4 (beta6) and started the adventure to understand / verify / rewrite my configuration files.

Now I fear that I am confusing myself and would like to get an answer to two questions, both regarding config.g and BLTouch:

My config.g looks like this:

...
; -----------------------
; Z-Probe
; -----------------------
;
M574 Z0 P"nil" ; no Z endstop switch, free up Z endstop input
M558 P9 C"^zprobe.in" H5 F600:120 T6000 ; set Z probe type to bltouch and the dive height + speeds
M950 S0 C"duex.pwm5" ; create servo pin 0 for BLTouch
M574 Z1 S0 ; set endstops controlled by probe
G31 P600 X0.0 Y21.0 Z1.72 ; set Z probe trigger value, offset and trigger height
M557 X10:292 Y21:291 S47:45 ; define mesh grid
...

1.: Is the 'M574 Z0 P"nil' line needed?
2.: Is the 'M574 Z1 S0' line needed?

I know that the Troodon is not using the original board. For this especially: thank you that you changed the FW so it is working now!! (And yes I wrote them that I am disappointed that their choice is not marked clearely on the product site as I bought under the impression of receiving a genuin board.)

If this sound odd, apologies upfront - but - is there a "Kaffeekasse" one could donate a "Kaffee"?

Thank you upfront and best regards,
Thomas

@pcr oh well ... why should it be so easy (...) THX I will try that