Topics created by jbjhjm

@dc42 thats nice and simple and easy. I like it!

ah yes this makes sense thanks @gloomyandy !

@chrishamm that fixes it thank you! 😄

@t3p3tony said in Heater Fault handling improvements:

@wdenker its been around in some form since RRF 1.14

That's only 2.16 versions ago.

@chrishamm works perfectly fine thank you for helping me out!

@t3p3tony I will let you know if anything new occurs. Maybe b5 and the tweaked raspi settings helped to make it go away. As the error did not occur often in the past, I'll continue and observe for some days.

@jbjhjm said in M703 - error if no filament is selected?:

if move.extruders[state.currentTool].filament == "" abort "Error: No filament selected" if move.extruders[state.currentTool].filament == null abort "Error: No filament selected"

I have not encountered a situation where the null check was needed - perhaps it can be null but I don't know when.

I have no test for a tool being selected as that is done just after the checks. I have no multi-tool printers.

T0 M703

Frederick

@jbjhjm said in Reset to default settings before/after print?:

@dc42 wouldn't that make it quite complicated to run test prints for finding max well-working acceleration levels etc?

Yes, so there would have to be a way to override it.

@engikeneer aaaah right got it! thx!

@pcr alright that explains why commenting out things had no effect, it just auto-switched to the single axis homing scripts