I’ve pushed an update to the algorithm for everyone to test, its pretty nerdy but the details are here. I made a small mountain of test prints this week to validate all this:
The fact that I am spitting out full sheets at-will has me feeling confident that this is an improvement.
Other stuff in this update:
- The default pullback move distance was increased from 0.1mm to 0.2mm. Some users reported problems with taps that were too short and its better to be slow and safe vs go fast and fail. You can still change this if you find that its too long.
- There is now a check that the pullback elbow does not fall within the last 1/4 of the pullback move time. When the elbow is this late its not possible to be certain that the move was long enough.
- The
pullback_extra_timeoption was removed. This was adding an extra 300ms to all taps to gather additional data. With the longer default move distance this should not be necessary. - The
PROBE_ACCURACYtool now reports a new metric calledaverage delta. I wrote about this here. Hopefully this will help to spot cases wherePROBE_ACCURACYis used in adverse conditions and try to separate what is the probes fault and what is the environments fault.
Debugging tool updates:
- The debugging tool will now report the time it took for the python code to run the tap analysis. On a Pi4 I’m seeing around 130ms to 200ms.
- All of the JSON for the tap is copied to the clipboard (before it was only time and force)
The next thing that will happen is an update to surface the cause of bad taps in the debugging tool. I’ll be adding error codes to the websocket output so you can know why a tap was rejected.