Setting up for a THC-01 hotend
-
Are you testing it with manually-generated GCode commands? If so then you need to set at least the active temperature of each tool before you use it. You can do this using the G10 command (using the P parameter to specify which tool) or the M104 command (using the T parameter to specify which tool).
-
I'm trying to spit out a 25mm 2 color calibartion cube atm, all GCode given by Slic3r.
I've just inserted " M104 S[first_layer_temperature_[next_extruder]]" in the "Tool change G-Code" section in Slic3r printer setup now and made a new slice.
But already in the prime section it does in the start of the print it fails to set a new temp after assigning next tool.Sorry if i make it hard to understand, i can see myself struggling to with explaining this in a good way
Here's a snippet of the GCode:
https://drive.google.com/open?id=1Xc2L1HILKEj2lTF-ipzRrLRqsvBoB3Pr -
This is how the sliced GCode look like:
https://drive.google.com/open?id=1Zv8z6VV353ssVPBiUgDlFscZG1vo89ws -
You slicer isn't setting the temperature of tool T0 before it switches to it. That's OK if you let the firmware control the temperatures instead. You can use the G10 command to set the active and standby temperatures in firmware instead, in your slicer start GCode. The following will work with most slicers:
G10 P0 S[first_layer_temperature] R[first_layer_temperature] G10 P1 S[first_layer_temperature] R[first_layer_temperature]Most slicers will replace [first_layer_temperature] by the actual temperature you select in the slicer.
-
Ok? But won't that be all f'd up if let's say the first layer is with a PLA filament on T0, and down the road it's PETG on T1? Or am i getting something wrong with how the whole thing works?
-
@exerqtor said in Setting up for a THC-01 hotend:
Ok? But won't that be all f'd up if let's say the first layer is with a PLA filament on T0, and down the road it's PETG on T1? Or am i getting something wrong with how the whole thing works?
Yes, you really need to get your slicer to set the temperatures for the two tools independently. I am surprised your slicer isn't doing that already, because most do. Which slicer is it?
-
@dc42 That's what i thought to, it's the newest Slic3r PE (1.41.1winx64) who got released this weekend
-
@exerqtor I'm starting to veer away from PE version of Slicr£R because it's getting to be too biased towards Prusa's way of doing things and doesn't understand mixing hot ends (which is what I have). Anyway, if it's a 3 in 1 out hot end with a common heater, try setting the active and standby temperatures in the start gcode. So something like this:
G10 P0 S195 R195
G10 P1 S195 R195
G10 P2 S195 R195If you want to use a different temperature for tool 1, substitute the values for that in the above.
-
@deckingman I'm not using a mixing hotend, but more or less one that mimiks the MMU 1.0 so it's kinda just up my alley lol.
I'm going to try to add all the temps in the filament start gcode section and see how that fairs now. that way at least should change each time it goes for a new filament.
EDIT:
Still don't work, here's the newest sliced cube i did, it stil set T0 to 0c when it switches under the purging sequence. This time i manually set it back to 220 just to look what happened. Then it finished the purging part but when it was about to from the purge it beeped(the M300 i guess) and everything just stopped and the whole print halted.https://drive.google.com/open?id=1GO1YJb1_nxfEe0GjUVBRbXOxbaIJII4x
-
@exerqtor I know you aren't using a mixing hot end, but can you confirm that it has a single heater? i.e you have 3 inputs to a common nozzle but only use one at a time yes?
Assuming that's correct, then looking at you gcode file you start with Tool 1 (line 21), then there are various priming and wiping commands before we get to T0 in line 112. But there is nothing preceding that to set the temperature for tool 0. The filament gcode doesn't get run until much later (starting at line 303) so there is no point in putting the active and standby temperatures in there. Try putting those G10 commands in the start gcode as I suggested - preferably at the very beginning.
-
@deckingman Yeah a THC-01 hotend like the subject on the thread say =P
I just altered the start gcode, ofc that set the temps for the first layer. But the print still aborts after the priming section!
Last slice: https://drive.google.com/open?id=1EX-3pNZI0HHZLwLHR2xeXhb9diTIy5uz
EDIT:
Ok, i've got it to go past the priming now, removed every "M900,M907,M200" the final thing i had to remove was "M1 S10", the temps are still kinda wacky (look @ the file linked), but it's trying to print now.
Going to let it finish and see how it ends up. -
@exerqtor is it set to Marlin or RepRap gcode flavor?
-
@phaedrux Reprap/Sprinter.
-
What slicers whould ppl here suggest using though? I'm getting tired of this
-
@exerqtor I have success with Cura and Slic3r PE
-
@exerqtor Slic3R PE or the "dev" version. But rather than try to use Prusa's way of changing filaments, just use it to insert the tool changes then do your own macros to handle the filament changing and purging.
-
@t3p3tony said in Setting up for a THC-01 hotend:
@exerqtor I have success with Cura and Slic3r PE
I didn't have much luck with Cura (used it a couple month's and didn't like it to much).
@deckingman said in Setting up for a THC-01 hotend:
@exerqtor Slic3R PE or the "dev" version. But rather than try to use Prusa's way of changing filaments, just use it to insert the tool changes then do your own macros to handle the filament changing and purging.
Ok what's the dev verson? As far as i can see the newest update to the "normal" Slic3r is from 2015 or something =/ (Edit. just found the dev verson lol) downloading and trying now).
Yeah i'm thinking about doing that, but i can't seem to find a good way to do that either. Also making stuff from scratch is a pain if the function is already in the slicer imo.
-
............................ Also making stuff from scratch is a pain if the function is already in the slicer imo.
I'd agree with you if the function worked. But as you've discovered, the PE version adds commands such as M900 and M907 that are suited to Prusa's firmware but not the RepRap firmware that Duet uses. I know it may seem a bit of a pain to write your own macros, but it does meant that you have full control and can get the exact behaviour that you want, rather than be stuck with something designed for a specific machine.
-
Yeah true, but i have to say one thing. And that's i'm NEVER installing regualar Slic3r again what a utter piece of garbage!
-
@exerqtor said in Setting up for a THC-01 hotend:
Yeah true, but i have to say one thing. And that's i'm NEVER installing regualar Slic3r again what a utter piece of garbage!
Care to elaborate?
