How do I set the offset between nozzles/ head origin
-
Hello thanks for for checking this out. I'm having a bit of confusion setting up my chimera hot end, specifically with the G10 commands.
First issue:
I'm trying to set active and standby temperatures but when I try to go with 195/170 I get a heater error saying to check wiring and it will not let me power on heater 1. Like this:
; Tool definition section
M563 P0 D0 H1 ; Define tool 0 to use extruder drive 0 and heater 1
G10 P0 S195 R170 X18 Y0 ; Set tool 0 operating and standby temperatures
;*** If you have a dual-nozzle build, un-comment the following 2 lines
M563 P1 D1 H2 ; Define tool 1
G10 P1 S195 R170 X-18 Y0 ; Set tool 1 operating and standby temperaturesThe second question I have is how to determine the offset for the two nozzles. I measured the center to center distance between nozzles to be 18 so right now I have it set up as you see above.
after reading here https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_Cartesian_printer I realized that I may have determined that wrong. If someone could give me some clarification on this I would really appreciate it thanks.
-
If the distance between nozzles is 18mm, set one of the offsets to 9mm and the other to -9mm.
What exactly is the error message you get when you try to activate tool 0?
-
the error message says temperature excursion exceeded 15*C
-
the error message says temperature excursion exceeded 15*C
See https://duet3d.com/wiki/Spurious_heater_faults_and_how_to_avoid_them.
-
this page seems to be a dead link https://duet3d.com/wiki/Tuning_the_heat
-
Thanks for reporting that, I've fixed the link.
-
I was able to go through the auto tuning for both nozzles successfully. Now that I have my new M307 numbers do I have to remove the M301commands from the config file? I'm just not sure where the new numbers should be placed / the sequence of commands.
-
Yes you should remove the M301 commands.
The restrictions on the order in which commands are placed in config.g are listed at https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_Cartesian_printer#Main_configuration_file.
-
after auto tuning should I just send M500 to save the new settings? or should I be manually writing it into the config file? these are my updated settings after auto tuning but i'm still getting heater faults.
; Heater and thermistor section
;*** If you have a Duet board with 1K thermistor series resistors, change R4700 to R1000 to the following M305 commands
M305 P0 T100000 B3950 R4700 H0 L0 ; Put your own H and/or L values here to set the bed thermistor ADC correction
M305 P1 T100000 B4719 R4700 H0 L0 ; Put your own H and/or L values here to set the first nozzle thermistor ADC correction
M305 P2 T100000 B4719 R4700 H0 L0 ; Put your own H and/or L values here to set the second nozzle thermistor ADC correction
;M301 H1 P10 I0.10 D100 T0.50 S1.0 ; PID settings for extruder 0
;M301 H2 P10 I0.10 D100 T0.50 S1.0 ; PID settings for extruder 1
M307 H1 A415.9 C173.7 D4.4 B0
M307 H2 A450.6 C173.7 D4.6 B0
M570 S120 -
You can do whichever you like. But remember these:
1. Settings saved with M500 are saved in config-override.g and will only be used if you have a M501 command near the end of config.g. The M501 command simply runs config-override.g.
2. If you have a M501 command near the end of config.g then any M307 or M301 commands in config-override.g will override settings in config.g.
-
After doing everything suggested I'm still getting heater faults, is there anything else I can do? Sorry for all the questions this is my first time playing around with dual extrusion.
-
Which type of heater fault are you getting? Have you run M307 H1 and M307 H2 to check that the values set in config.g are the ones being used?
-
Which type of heater fault are you getting? Have you run M307 H1 and M307 H2 to check that the values set in config.g are the ones being used?
I did run both of these and the values are definitely set. I'm still getting the same fault message as before.
-
It seems to be ok now that I've set standby and running temps to 0 under G10. I'll do some more testing today and see what I come up with it seems to be those G10 temps that are throwing everything off
