I have added the OLED screen, and the auto clippy but I have some odd behaviors. Screen works perfect, and 6 pulses does the cut operation.
However:
10 pulses is not giving me a response of what mode the 3DC is in - seems to be 3
Powering off and back on, the 3DC loses what filament is loaded, and it cycles the clippy! Not a good scenario. Shouldn't it remember the last loaded filament? And it shouldn't actuate the clippy unless commanded.
If T1 is loaded, and then called again, it cuts asks to back out, and reload T1. Shouldn't it ignore a T load if the requested T is already loaded?
Anyone else observed any of these behaviors?
Thanks,
Danny Brija
All 3 of those are by design.
The Mk4 Pro firmware only supports Mode 3, so there are no other modes to switch to
No, you need to unload the filament at the end of a print, that way it always starts at the unloaded position. The first color of a subsequent print might not be the same color as the last of the previous print. The 6 pulse command in the End GCode allows it to unload the last used filament, that way there is no last used filament. As for startup, since no filament should be loaded, cycling the servo allows the system to correctly position it for the first actual cut.
Why would you do that? No slicer commands a color change if there isn't one. Like the previous one, if it's between prints, our code assumes the 3DChameleon is started with the filament unloaded anyway.