Feature request/feature I don't know exists.
-
Most Duet Gcode commands without a parameter return the current setting. To my knowledge neither M672 nor M672 S105 returns the current sensitivity. Would be very useful, as I tinkered with it and got it somewhere good, now it's a bit too sensitive after some changes and I have to trial and error from the beginning instead of bumping it up 3-5 settings.
-
Further, it seems the error I'm seeing may not actually be real. I'm getting a Error: Z probe already triggered at start of probing move during the probing, but it doesn't appear to halt on any of the probe points, and it eventually returns a deviation upon completion. An M665/666 returns values that aren't whats in my config.g which leads me to believe its storing the data despite the error
-
The sensitivity is stored in EEPROM on the effector, and the effector has no way or reporting what its sensitivity is. That is why M672 is unable to report the current sensitivity.
Are you sure that M665/666 isn't returning values that are stored in config-override.g ?
-
Can't tell now because I can't replicate the probe error. Ordinarily when a triggered at start error occurs doesn't it not provide a deviation at the conclusion? I seem to recall just getting the error. Now it throws that error mid probing (despite not seeing an early triggering) and then gives me a deviation anyway. Can't seem to replicate either regardless so all good. Interesting that the data on sensitivity is stored on the effector. Seeing as it's entered on the web control it should be possible to make the command send the setting to the effector as well as add it to config.g in text form so it's stored somewhere the settings page can reference or blank parameter gcode could return, but it's obviously not a dealbreaker, now I know I should add it commented out to my config so I can reference it later to change it slightly up or down.
Thanks as always for your help, I look forward to quadrupling the number of threads in this forum with my ignorance haha
-
The sensitivity is stored in EEPROM on the effector, and the effector has no way or reporting what its sensitivity is. That is why M672 is unable to report the current sensitivity.
Are you sure that M665/666 isn't returning values that are stored in config-override.g ?
I have the same issue
, could M672 S105:aaa:bbb command at the end of config.g be a good alternative ?
