I’m having problems with both Cura and Prusa slicers.
prusa: after first tool change the fan turns off and stays off for the rest of the print. I’ve checked the fan setting and even when set to on all time at 100% it makes no difference.
cura: as can’t modify the ender 3 profile for more than 1 extruded I made custom profile and set everything like for like, but when print starts it runs the extruder at lightening fast speed.
any ideas on how to resolve one or both of these as currently can’t use the chameleon if I can’t slice a model properly.
Just a note, the tool change works perfectly fine.
I'd look for two things in your Tool Change GCode.
One... if you have any M106 or M107 commands... remove them. They're the only thing that would turn on or off the fans... and my guess is there is a mismatch between them. M106 with an S parameter turns it on... and M107 turns it off. We don't need them anymore... and it's possible your filament settings contain no overrides for it. As for the lightening fast speed at the start... similar to the fans command, there is a relative mode and an absolute mode. My guess is that the start gcode puts it into one mode and the tool change gcode is switching it incorrectly.
Look for G90 and G91 commands, which set the printer in general to Absolute and Relative... and then look for M82 and M83 commands, which specifically set the extruder into Absolute and Relative modes. What I think is happening is that the 3D Chameleon is trying to move the filament while it's in absolute mode... but it should always only move it in relative mode. So... at the start of the Tool Change GCode, add a M83 to force it into relative mode. If you're not familar with what this means, basically, in absolute mode, if you give a command of G0 E100, it tells the extruder to go to the current 100mm position... but if you are in relative mode, it tells it to always go 100mm more. So, if you start out with the extruder at a 0 position... in absolute, it would move 100mm, but any subsequent G0 E100 commands would do nothing, because it's already at 100... but if you're in relative mode, if you issue it a second time, it would go to E200... and then E300 for the next command. My guess is that the initial E that is being passed to the Tool Change GCode is pretty far away from the Tool Changes commanded E... and if it's in absolute mode, it will try to get there too fast and stall the motor, or at least spin it at it's maximum speed.
If you need, please post (or email me) your tool change gcode (or a complete gcode file) so I can examine it and try to see what is happening.
Bill