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
HappyHare receives filament colors that are later displayed in the UI.
A reasonable continuation would be adding filament color validation for the gates.
There are a few options of arduino-compadible color sensors (TCS3200 and alike) that can be integrated into the selector (somewhere after the encoder), which can provide a reading on the filament color, that can be compared to the color provided by the slicer. The reading obviously won't be accurate, so a tolerance (possibly, a WIDE tolerance) is necessary.
It should be possible to bypass the check for transparent/rainbow/2-colored filaments, etc.
It is an absolutely random idea, but, theoretically, this kind of check can save some headache if the loading order is incorrect.
The text was updated successfully, but these errors were encountered:
Sounds like a wonderful and fun project.... but not something I have the energy for at the moment. Note that there is a new "automap" function that you can set to be color. So long as the gate map is accurate, then HH can automap the slicer tools to the correct gate...
HappyHare receives filament colors that are later displayed in the UI.
A reasonable continuation would be adding filament color validation for the gates.
There are a few options of arduino-compadible color sensors (TCS3200 and alike) that can be integrated into the selector (somewhere after the encoder), which can provide a reading on the filament color, that can be compared to the color provided by the slicer. The reading obviously won't be accurate, so a tolerance (possibly, a WIDE tolerance) is necessary.
It should be possible to bypass the check for transparent/rainbow/2-colored filaments, etc.
It is an absolutely random idea, but, theoretically, this kind of check can save some headache if the loading order is incorrect.
The text was updated successfully, but these errors were encountered: