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
Because ejecting used-tips happens from the same position, the tips piles up and it happens that one get stuck on top of another blocking the ejector. Could be solved by making the robot eject every N tips in a quarter of the bin.
The text was updated successfully, but these errors were encountered:
Good point. I'll deal with this. the only problem is that the trash is going to be different for different users, i.e. there is no standard size for this. But we can say that it has to be at least a minimum width and height and then apply a bit of randomness to the actual point at which it ejects, which should prevent the pileup.
On Fri, Oct 5, 2018, 12:10 PM Frank Schwach ***@***.***> wrote:
Good point. I'll deal with this. the only problem is that the trash is
going to be different for different users, i.e. there is no standard size
for this. But we can say that it has to be at least a minimum width and
height and then apply a bit of randomness to the actual point at which it
ejects, which should prevent the pileup.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#13 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AS0XRyzj-XbCXHwzFR-12MNU3qwAy5Coks5uh4R4gaJpZM4SFmxf>
.
Because ejecting used-tips happens from the same position, the tips piles up and it happens that one get stuck on top of another blocking the ejector. Could be solved by making the robot eject every N tips in a quarter of the bin.
The text was updated successfully, but these errors were encountered: