You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, MPU6050 motion detection works in such a way that the statement that motion has occurred is based on the finding that activation has occurred in ALL enabled axes.
In the case of a washing machine, it turns out that it is better to check that the stimulation occurred in ANY axis.
I wrote a script to implement this using rules. It works much better than the original motion detection included in the driver.
My suggestion is that there should be, for example, a checkbox toggling between ANY/ALL axes.
Below is a proposition of the driver part _P045_MPU6050.ino for a function that executes ANY instead of ALL axes.
At the moment, MPU6050 motion detection works in such a way that the statement that motion has occurred is based on the finding that activation has occurred in ALL enabled axes.
In the case of a washing machine, it turns out that it is better to check that the stimulation occurred in ANY axis.
I wrote a script to implement this using rules. It works much better than the original motion detection included in the driver.
My suggestion is that there should be, for example, a checkbox toggling between ANY/ALL axes.
Below is a proposition of the driver part _P045_MPU6050.ino for a function that executes ANY instead of ALL axes.
See forum thread
The text was updated successfully, but these errors were encountered: