@fcwilt said in multiple Z-Probe trigger heights in config-override.g:
So you think that limiting customers to executing G-code commands will prevent them from messing things up?
Never underestimate the power of a customer to mess things up. Some of them seem to view it as a challenge
Well, the beautiful thing about my setup is, they need a password for it. But I'm sure someone will try hard enough to manage to mess something up 
Still I don't want to make it too easy
@jay_s_uk I know about those and the extruder driver was always on the same board as the filament monitor
I'd love to keep some (global) variables upon restart.
Figured in keeping variables (global) after reset .gco files could be used, but it will get complicated soon.
Would love to see a M*** command that writes all currently set globals to a file variables.g (or alike) in sys, which could then be called while startup. This way you could simply change the value of one variable, and write them all back to the variables file if needed. kind of like with config-override.g
@jay_s_uk I did and it should be working. At least I don't see anything obvious.
M915
Driver 0.0: stall threshold -50, steps/sec 200, coolstep f, action on stall: run macro
Driver 0.1: stall threshold -50, steps/sec 200, coolstep f, action on stall: run macro
Driver 0.2: stall threshold -50, steps/sec 200, coolstep f, action on stall: run macro
Driver 0.3: stall threshold -50, steps/sec 200, coolstep f, action on stall: run macro
Driver 0.4: stall threshold 1, steps/sec 200, coolstep 0, action on stall: none
Driver 0.5: stall threshold 1, steps/sec 200, coolstep 0, action on stall: none
Driver 0.6: stall threshold 1, steps/sec 200, coolstep 0, action on stall: none
@jay_s_uk thanks - I'll give it a try and get back to you if needed!
@jay_s_uk we're in contact and diagnosing the issue yes