Over night bug: Invalid Kinematics [Solved]
-
@joergs5 said in Over night bug: Invalid Kinematics [Solved]:
I thought about a little program to check those conditions
IMHO there is one order of commands that always works, even when adding tools and axes. Why not rewrite the configurator tool to apply this order?
-
@o_lampe said in Over night bug: Invalid Kinematics [Solved]:
@joergs5 said in Over night bug: Invalid Kinematics [Solved]:
I thought about a little program to check those conditions
IMHO there is one order of commands that always works, even when adding tools and axes. Why not rewrite the configurator tool to apply this order?
I already logged this to be fixed.
-
@dc42
Thank you!
I'm still unsure why I had it running the first time? Is there a chance that the drive mapping was in the memory even after I rerun config.g and that's why it accidently worked? -
@o_lampe, had you perhaps sent M669 from the console when you had it working the first time? Or perhaps you had run M98 P"config.g" ?
-
@dc42
Yes, I run M98... often for debugging. I don't remember, if I wrote a full M669 via console, I can check the cache. But I'm sure I only have a naked M669 there to check the matrix. -
@o_lampe, if you ran M98 P"config.g" that would have run the M669 command again, with the correct M584 drive assignments already set up from when config.g was run at boot time. So that's probably why it worked.
-
@dc42
In my case it would've been luck, but in other cases it would be better to erase eeprom every time. (Marlin insider)
As I said, I often restart/reset the printer and browser because of those funny accidents. -
@o_lampe, if you want to run config.g and have RRF forget the previous values as far as possible, you should run M502 instead of M98 P"config.g". However, even running M502 doesn't destroy things you have already created, such as new axes, heaters, fans etc.
-
@dc42
but hitting the emergency button in DWC does? -
@o_lampe thats a full system reset, so yes