2in1out y setup heater turns off by itself, cura
-
Anyone know the difference between printer start/ end gcode and extruder start/end gcode in cura ?
Some reason cura turns off my heater when it is done printing the last layer of one of the colors...
so it stops extruding due to no heater is turned on..When i remove my end gcode in cura completely, it works fine and keeps the temperature at the target... but then it does not shut off the heaters when done printing...
i think it is due to the way cura handles end gcodes for the printer and individual extruders...
Cant seem to make it want to stay at the targeted temperature for the selected tool..
im using a 2in1out y splitter..If the end gcode could be moved to a .g file and executed when the print is done at 100%, that would be preferred.. but i camt seem to find any posts regarding firmware controlled scripts/start-end gcode for cura..
Maybe im just looking the wrong places.. -
the start and end gcode shouldnt have anything to do with the tool changing.
its sounds a bit like the tools in the firmware are not correctly defined. in a y splitter setup the two tools share the same thermistor input, that needs to be defined in firmware.
-
That is defined as it should be....
I know this worked woth s3d a year ago, perfectly..
I also had it work with cura, about a year ago....Same files, same everything, same start/end gcode.. except the retract distance... even the same filament....
But ofc a newer firmware and a newer version of cura....
If it is the firmware, how come that removing my end gcode in cura, fixes it ?
I dont believe i can run several tools without setting standby and printing temp in config.g? I have not read anywhere it is possible to do so, though... so theyre at 0... but they were the same too, a year ago... i literqlly copy/pasted all of my old known-working text into this... so it is 100% indentical to what worked perfect a year ago...
-
@sungod3k said in 2in1out y setup heater turns off by itself, cura:
the start and end gcode shouldnt have anything to do with the tool changing.
its sounds a bit like the tools in the firmware are not correctly defined. in a y splitter setup the two tools share the same thermistor input, that needs to be defined in firmware.
here is my config.g section regarding heater and drives....
; Heaters
M301 H0 S1.00 P10 I0.1 D200 T0.4 W180 B30 ; Use PID on bed heater (may require further tuning)
M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S140 ; Set temperature limit for heater 0 to 140C
M305 P1 X201 ; Configure thermocouple for heater 1
M143 H1 S350 ; Set temperature limit for heater 1 to 350C
M307 H1 A407.6 C177.4 D3.2 B0
M305 P2 X201; Fans
M106 P0 S0 I0 F50 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F50 H1 T50 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on; Tools
M563 P0 D0 H1 ; Define tool 0
G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0CM563 P1 D1 H1 ; Define tool 1
G10 P1 X0 Y0 Z0 ; Set tool 1 axis offsets
G10 P1 R0 S0 ; Set initial tool 1 active and standby temperatures to 0Cstart and stop.g is completely empty...
tool change files are fine, i think....
i have removed M116 from the tool change files though, since i had issues with it waiting to stabilize completely, everytime it retracted and primed and started printing the prime tower...
-
i dont have acces to my config file atm, but the important thing is that the 2nd tool has the same thermistor as tool one.
although its indeed weird that it stopped working when cura changed.
have you updated the RRF config file since then?
-
yes, rrf firmware has been updated since.... the orignal files were generated about a year ago.... where it worked.... so it could easily have been changed...
how does M116 behave, when doing several tools? since mine have always worked fine with M104 and M109.... and still does, at least when i only use 1 color/extruder at a time...They share the same pt100 sensor.. X201
yes it is very weird.... at least to me it is... but if anything, ppls say if u ned me to share anything, its my first time asking an official question regarding the duet
ive always managed to get it all working by my own hand... its a bit frustrating.. feeling like a complete newbie even though ive had the board for over a year so any pointers, everything are welcomed -
it SEEMS its fixed, by removing my whole end gcode in cura, replacing it with M0, to call stop.g.. then i have put in my end gcode in stop.g, and now it seems to work
i will tell you in 14-15 hours when my dual color print hopefully is done
