Setting up Cartesian Printer.
-
This might be a blunder on my part, or a mistake in the config tool, but check this out:
On the lower board, the terminal blocks labelled RTD1 and RTD2 will be temperature measurement channels 200 and 201 respectively.
I entered RTD1 into the config tool and ended up with:
M305 P1 T100000 B4138 C0 R4700 L0 H0 X201 ; Set thermistor + ADC parameters for heater 1 and remap it to channel 201
This might explain why my hot end is reading at 2000degC at room temp??
I'll try changing it to 200 and see what happens.
And yes, that put me with 0.5degC of the bed temp
Which would also mean that David's estimated settings for the bed thermistor were pretty good as well. -
That would make a difference yes
-
Regarding G31 P600 X1 Y1 Z2.5 ; Set Z probe trigger value, offset and trigger height:
1. Increasing the probe trigger height (G31 Z parameter) will make a bed crash more likely, because after the probe triggers, the firmware will think it can go down further before it reaches Z=0. You need to measure the trigger height as described in the IR sensor fitting instructions, and use that value.
2. The X and Y parameters are the offsets of the sensor sensitive area (just below the black capacitor) from the nozzle. They get subtracted from the XY coordinates in your bed.g file, so that the sensor is over those points during probing, not the nozzle.
3. You must always use P500 with the IR sensor.
HTH David
-
Regarding G31 P600 X1 Y1 Z2.5 ; Set Z probe trigger value, offset and trigger height:
1. Increasing the probe trigger height (G31 Z parameter) will make a bed crash more likely, because after the probe triggers, the firmware will think it can go down further before it reaches Z=0. You need to measure the trigger height as described in the IR sensor fitting instructions, and use that value.
2. The X and Y parameters are the offsets of the sensor sensitive area (just below the black capacitor) from the nozzle. They get subtracted from the XY coordinates in your bed.g file, so that the sensor is over those points during probing, not the nozzle.
3. You must always use P500 with the IR sensor.
HTH David
Thank you. I'll read the wiki a bit more.
Just starting to get my head around it all.
-
With my homing I am concerned whether I entered the right information in the config tool.
I am pretty sure I entered "high" for all axis'.
My X and Y limit switches are both in the front/left corner, and I had to reverse/enter a 0 value all 3 drives to get them to home to the right position.
Moving them manually with the paneldue I have to use + movement to move towards the homing position.
Is that correct?
It does seem so according to the wiki (I think), and I just want to be sure before I set the Z home position, which is currently in the right rear corner and I'd like to move it to the center
Here's how I'm set up at the moment:
; Endstops
M574 Z0 S0 ; Define active low and unused microswitches
M574 X2 Y2 S1 ; Define active high microswitches
M558 P1 X0 Y0 Z1 H5 F120 T6000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
G31 P500 X0 Y0 Z2.5 ; Set Z probe trigger value, offset and trigger height; Drives
M569 P0 S0 ; Drive 0 goes forwards
M569 P1 S0 ; Drive 1 goes forwards
M569 P2 S0 ; Drive 2 goes forwards -
Re run the config tool and left the high/low settings at their defaults.
Still had to reverse 2 steppers, but I realize this would be just due to wiring connections.
It now homes Z in the back/left corner, and I'd like to set my Z probe height/offset in the center.
My question is: Do I have the correct high/low settings for my machine which has the limit switches in the front/left corner of the gantry?
If not, could someone show me what changes to make?
I've gone through the wiki but am unsure.
Here's where I'm at now:
; Endstops
M574 Z0 S0 ; Define active low and unused microswitches
M574 X1 Y2 S1 ; Define active high microswitches
M558 P1 X0 Y0 Z1 H5 F120 T6000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
G31 P500 X0 Y0 Z2.5 ; Set Z probe trigger value, offset and trigger height; Drives
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S0 ; Drive 1 goes backwards
M569 P2 S0 ; Drive 2 goes backwards
M569 P3 S1 ; Drive 3 goes forwards -
Edit homez.g and homeall.g to put the probe/hotend where you want it to be for homing.
-
Edit homez.g and homeall.g to put the probe/hotend where you want it to be for homing.
Nice!
I was only doing it in homez.g. Didn't realize it had to be done in both.
Could someone confirm my X Y axis high/low settings in my question above please?
-
You need to decide where you want X=0 Y=0 to be. That in turn will fix which is the X axis and which is the Y axis. If you choose front left, X will be left-right and Y will be front-back. If you choose rear left then X will be back-front and Y will be left-right.
Having chosen where the origin will be, set the X and Y motor directions so that +X and +Y move the head away from that corner. You may need to swap the X and Y motor connections over to achieve this.
Then use config tool to specify whether each homing switch is at the low or the high end of its axis, to generate the correct M574 command and homing files. You don't need to home to the origin, you can home to zero on some axes and to max on others.
-
My understanding is that the standard configuration is that X=left to right, and y=front to back. If that is the case I'd rather keep it that way.
X0 and Y0, by which I assume you mean home/limit switch are in the front/left of the gantry.
It's almost correct…+ve moves X out of the home/corner, and moves the Z/build plate down.
The only problem is Y, which needs -ve to move out the the home/corner.
Is there anything I can change here in config.g that will fix that? Would M574 X1 Y1 S1 do it? nope, doesn't
M574 Z0 S0 ; Define active low and unused microswitches
M574 X1 Y2 S1 ; Define active high microswitches
M558 P1 X0 Y0 Z1 H5 F120 T6000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
G31 P500 X0 Y0 Z2.5 ; Set Z probe trigger value, offset and trigger height; Drives
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S0 ; Drive 1 goes backwards
M569 P2 S0 ; Drive 2 goes backwards
M569 P3 S1 ; Drive 3 goes forwards -
With that configuration, the origin will be at the front left. As your limit switches are also in the front left corner, they are both low end switches. So use M574 X1 Y1 S1.
-
With that configuration, the origin will be at the front left. As your limit switches are also in the front left corner, they are both low end switches. So use M574 X1 Y1 S1.
Thank you.
I re ran the config tool and that's what I ended up with.
-
Run the temp auto tunes on both the hot end (PT100) and the bed (thermistor).
Hot end:
Gain 895.7, Time Constant 305.4, Dead Time 11.5, Max PWM 1.0, Load Change P5.3, 10.23, D42.6
Bed:
Gain 108.0, Time Constant 554.5, Dead Time 11.0, Max PWM 1.0, Load Change P83.6, 13.81, D641.4
Not sure what it all means, but I'll put it up in case there are any glaring issues there.
-
Those figures look OK to me. Now add these M307 commands in config.g:
M307 H0 A108.0 C554.5 D11.0 B0
M307 H1 A895.7 C305.4 D11.5 P0.5I am suggesting the P0.5 for the hot end to slow down heating, because your hot end heater is so powerful. The B0 for the bed is to switch to PID mode, which should give you better temperature control.
-
Those figures look OK to me. Now add these M307 commands in config.g:
M307 H0 A108.0 C554.5 D11.0 B0
M307 H1 A895.7 C305.4 D11.5 P0.5I am suggesting the P0.5 for the hot end to slow down heating, because your hot end heater is so powerful. The B0 for the bed is to switch to PID mode, which should give you better temperature control.
Nice one.
That brought the 2 temps within 0.2-0.3 degC of each other.
-
OK, getting happier now.
Very impressed with the accuracy of the temp management, it really seems to hold right on the dot once up to temp. Of course I'd like to test real life temps at each point but I don't have an instrument to do it with yet.
Probing/homing height seems to be accurate and consistent as well, so that's all good.
I've now set up the automatic probing at 5 points, moving clockwise around the 4 corners of the board and ending up in the center.
I've already checked it with a straight edge and it's bent like a banana (I knew that and plan to make a new cast ally one in the future), but I've leveled it reasonably well with a feeler gauge manually.
I ran the auto probing (G32) 3 times in a row, and it was reasonably consistent.
After I finished I moved the extruder and started getting:
G28
Triangle interpolation: point outside all triangles!Can't see any reference to it in the wiki, what's that all about?
-
You can ignore that triangle interpolation message when homing, it's harmless. One of these days I'll fix it.
-
Can I change the retraction settings without going through the whole config tool again?
My Z is a direct drive and I understand the factory setting is more like 0.5-1mm at a higher speed.
I understand this can be controlled both by the firmware and the slicer as well? Does the slicer setting overwrite the default firmware setting? Should I just leave retraction at zero, then enter my setting/speed of choice through S3D to suit whatever material I'm printing with?
I'd also like to change the Z probing speed, as the second time I run the config tool I sped it up a little and it's a bit noisier.
I can't find this information in the wiki, what G codes would I be looking for?
-
Normally people set the retraction in the slicer. On printers with mixing extruders, it's typically better to select "Use firmware retraction" in the slicer and define the settings in firmware instead. If you don't select "Use firmware retraction" in the slicer then the firmware retraction settings are not used.
To adjust the probing speed see https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_Cartesian_printer#Z_probe_section.
-
Normally people set the retraction in the slicer. On printers with mixing extruders, it's typically better to select "Use firmware retraction" in the slicer and define the settings in firmware instead. If you don't select "Use firmware retraction" in the slicer then the firmware retraction settings are not used.
To adjust the probing speed see https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_Cartesian_printer#Z_probe_section.
Yes thanks, that's what I'll do as it will allow different retraction settings for different materials (recipes) to be saved in the slicer.
Do we have a wiki for setting up the extrusion rate/steps per mm/feed rates for a direct drive extruder?
I emailed you a bunch of questions about speed settings etc (sorry, didn't realize it was Sunday morning there) if you could when you have time.
Had an issue with it refusing to heat, which may have been me firing too many commands at once, and hopefully isn't the mystery issue which keeps blowing mosfets at my house.
