effector tilting into bed on print
-
@dc42
Thanks for the heads up on M500. I have manually entered the trigger height in the G31. -
@timvukman said in effector tilting into bed on print:
- I realize that I can't say that something is moving in and X or Y direction relative to how I know those Axis in a cartesian model.
You probably already get this, but just to be sure:
Actually, you can and should state cartesian X and Y directions, when referring to X or Y moves caused by G-Code and/or the movement buttons in the web interface. The tip of the nozzle absolutely DOES move in cartesian space. The firmware moves the carriages on the towers in varying amounts and directions to make this true.
Example: Assume the nozzle is a Z50 an X0Y0. Command a move to Y10. Two of the towers will move down, and one up, in different amounts, so that the nozzle moves to X0Y10Z50. The moves will be "timed" so that the Z and X planes never deviate during the move.
This is how Delta's work.
I am trying to use the X Y and Z columns when describing directions of effector heading, unless I am using Z in the context of Height where 0 is the surface of the bed with the nozzle resting on a piece of paper. I have my printer facing me on a desk where I am looking between the X and Y columns with the Z column centered in the rear.
This is all correct when referring to the TOWERS. To repeat with different phrasing: TOWER X is NOT in any way related to the way the nozzle moves when it moves in cartesian X. In fact, some Delta firmware refers to the towers as Alpha Beta Gamma just to avoid any possible confusion.
1a. I had to switch my X and Y column motors and end stops to match the description that I was given here, but X is to my left face on, and Y is to my right and Z is at the back.
Good. That will make all of us be "on the same page" when describing things.
- I haven't really paid much attention to those offsets. I see that 11 in the X reference, but I have no idea why it is there.
This means your probe is 11mm in the (cartesian space) X direction from the tip of the nozzle.
My bed is 220mm in diameter. From the DWC, the position reports X0 and Y0 when homed. I measured across X in the cartesian directions and my nozzle is at 120mm. I would think it should be 110mm to center. My Y value measures as 120mm front to back. I would think it should also be at 110mm
Agreed.
Bed.g is now:
; bed.g file for RepRapFirmware, generated by Escher3D calculator
; 10 points, 6 factors, probing radius: 100, probe offset (0, 0)
G30 P0 X0.00 Y100.00 Z-99999 H0
G30 P1 X86.60 Y50.00 Z-99999 H0
G30 P2 X86.60 Y-50.00 Z-99999 H0
G30 P3 X0.00 Y-100.00 Z-99999 H0
G30 P4 X-86.60 Y-50.00 Z-99999 H0
G30 P5 X-86.60 Y50.00 Z-99999 H0
G30 P6 X0.00 Y50.00 Z-99999 H0
G30 P7 X43.30 Y-25.00 Z-99999 H0
G30 P8 X-43.30 Y-25.00 Z-99999 H0
G30 P9 X0 Y0 Z-99999 S6This looks pretty good to me. It should result in a circle of 6 probes about 100 mm from center (which may be off a little from what you said about centering), then a circle of 3 more about 50 mm, and one in the center. (That could be off, I'm eyeballing the numbers). It will then calculate just about everything except the diagonal rod length because of the S6 in the last command. That's the way I do it as well (10 points total, calc with S6) .
So that all looks good.
What does it do? What is the response you see in the Gcode console? I see things like: (where the M500s are me writing it to config-override.g)
1:13:09 PM M500 1:12:13 PM G32 Calibrated 6 factors using 10 points, deviation before 0.043 after 0.033 1:11:20 PM M500 1:11:07 PM G32 Calibrated 6 factors using 10 points, deviation before 0.504 after 0.045 -
Ok. I am pleased that we got on to common terms for things. I am not convinced that X11 is correct, but I will deal with that a little later.
At this point, I have not run Auto Calibrate since resetting everything. I will run it.
I will run it in the morning. It blew up my system. My bad, I didn't home it first. Now things don't seem very happy in printer land.
I powered it back up, ran the G32. It seems to be moving outside of the bed, so I shut it down.
I will report in the morning
-
@timvukman
Hi:
I have reduced the radius to 95 which the printer seems happy with. I do have an issue where one of the diagonal rods contacts the housing for the Z switch on the effector. It's light contact at 95. At 100 it popped off the magnetic rod.I ran auto config this morning with new values in bed.g based on the change in radius to 95
G32
Calibrated 6 factors using 10 points, deviation before 5.928 after 0.307The before number sure looks out of whack, no?
-
I suggest you adjust one or more probe points to avoid that contact between the rod and the Z switch.
The 0.307mm deviation is rather large, however as the before-figure is to high, it may come down if you run 1 or 2 more cycles of auto calibration.
-
Don't worry too much about that "before" value right now. That is based on the figures in your config.g and your config-override.g. We know they are some way out because you can't print at the moment.
Drop your radius to 90mm, you don't want any kind of contact. The reduced probing radius will not be an issue right now. EDIT - dc42 has suggested a better way by simply changing the coordinate of the problem point. If you are comfortable doing this then go ahead, my method should work if you are not feeling confident, however.
My suggestion is that you do the following:
- Home all axes - either with a G28 or by clicking Home in the web interface (DWC)
- Run calibration - either with a G32 or through the web interface.
- WITHOUT HOMING - run G32 again.
- Save to config-override.g by running M500
Once that's done, paste the complete content of config.g and config-override.g here, along with the results of the two G32 commands, above. You've changed quite a few things so worth getting an up-to-date look at your config.
It sounds like you are really close, so keep going!
adavidm
--edited for readability
-
Ok
Changed radius to 90
Power Cycled.
Homed
G32
Calibrated 6 factors using 10 points, deviation before 5.340 after 0.315
2nd G32
Calibrated 6 factors using 10 points, deviation before 3.517 after 0.315Config.g
; Configuration file for Duet WiFi (firmware version 1.20 or newer)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Wed Jun 13 2018 16:33:57 GMT-0400 (Eastern Daylight Time); General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves;*** The homed height is deliberately set too high in the following - you will adjust it during calibration.
M665 R95 L360.20 B100 H211 ; Set delta radius, diagonal rod length, printable radius and homed height
M666 X0 Y0 Z0 ; Put your endstop adjustments here, or let auto calibration find them; Network
M550 PMiniKossel ; Set machine name
M552 S1 ; Enable network
M587 S"BELL137" P"DAAE9D3D996E" I192.168.1.14 J192.168.1.254 K255.255.255.0 ; Configure access point and IP addresses. You can delete this line once connected
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet; Drives
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S0 ; Drive 3 goes backwards
M350 X16 Y16 Z16 E16 I0 ; Configure microstepping without interpolation
M92 X80 Y80 Z80 E663 ; Set steps per mm
M566 X1200 Y1200 Z1200 E1200 ; Set maximum instantaneous speed changes (mm/min)
M203 X18000 Y18000 Z18000 E1200 ; Set maximum speeds (mm/min)
M201 X1000 Y1000 Z1000 E1000 ; Set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E800 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 Z-0.1 S1 ; Set minimum Z; Endstops
M574 X2 Y2 Z2 S1 ; Set active high endstops; Z-Probe
M558 P4 H10 F120 T2400 I1 ; Set Z probe type to unmodulated and the dive height + speeds
G31 P500 X11 Y0 Z-1.172 ; Set Z probe trigger value, offset and trigger height
M557 R80 S20 ; Define mesh grid; Heaters
M307 H0 B0 S1.00 ; Disable bang-bang mode for the bed heater and set PWM limit
M305 P0 T100000 B3950 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 T100000 B4388 C0 R4700 ; Set thermistor + ADC parameters for heater 1
M143 H1 S280 ; Set temperature limit for heater 1 to 280C; Fans
M106 P0 S0 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S0 I0 F500 H-1 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P2 S1 I0 F500 H1 T45 ; Set fan 2 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 0C; Automatic power saving
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss; Custom settings are not configured
; Miscellaneous
T0 ; Select first tool
M501Config-Override.g
; This is a system-generated file - do not edit
; Delta parameters
M665 L360.200 R117.532 H211.495 B85.0 X1.681 Y0.185 Z0.000
M666 X4.164 Y4.016 Z-8.180 A0.00 B0.00
; Heater model parameters
M307 H0 A90.0 C700.0 D10.0 S1.00 V0.0 B0
M307 H1 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H2 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H3 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H4 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H5 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H6 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H7 A340.0 C140.0 D5.5 S1.00 V0.0 B0Should the M666 values be that high?
-
No, unless you really have mounted the Z tower endstop switch 12mm higher or lower than the other two then the corrections should not be that high. Also, after the first G32 the predicted deviation is 0.315 but the actual deviation as shown at the start of the second G32 is 3.517. The fact that these are so different indicates that your printer has a geometric error that auto calibration cannot correct for. I suggest you work through https://duet3d.dozuki.com/Wiki/Calibrating_a_delta_printer. If possible, mount a circular spirit level on the effector to monitor effector tilt.
Can you post some photos of your printer?
-
Hi
I will get some photos. My Switches are all at the same height. I think the Z belt is jumping on the geared tooth when it makes the first move toward the Z access. I'm not sure if it is hitting the housing that holds the switch for the probe on the left side of the effector, or if it is hitting the casing that holds the part cooling fan on the rear of the effector.
This started with the addition of the longer magnetic rods. There was only one size where I purchased them.
I will place the order for the duet effector today. Hopefully it will get here in about a week. -
Hi:
I pulled the effector off of the magnetic rods, and rotated it by one carriage to the right. I did not hear the belt jumping.
Home
G32
Calibrated 6 factors using 10 points, deviation before 2.242 after 0.241
6:19:39
Did not home
PMG32
Calibrated 6 factors using 10 points, deviation before 2.460 after 0.325 -
So, Given that this seems to have worked, are the results such that I could attempt printing, or are there more steps that I should take to make sure it is ok?
-
No, the calibration is way off, because the deviation before is always more than 2mm even though auto calibration thinks it has reduced it.
-
Ok,
run this morning.
G32
Calibrated 6 factors using 10 points, deviation before 0.888 after 0.625
G32
Calibrated 6 factors using 10 points, deviation before 1.866 after 0.294
G32
Calibrated 6 factors using 10 points, deviation before 1.121 after 0.343I have saved this into my settings. Something that does not seem right in that I have now issued a homeall and all the carriages go up at the same rate. Z carriage is leading ahead of X and Y. X and Y column limit switches trip around the same time shortly after Z
Once triggered, all three carriages drop by the 5mm as expected. Z bounces off the switch 4 or 5 times on the subsquent rise back to the switches since my effector is no longer centered.
-
I suggest you increase the amount by which the carriages drop after homing to a value higher than 5mm, so that you do not get the Z bounce as the effector is centred.
It still sounds to me that there is some geometrical error that is causing calibration to make excessive corrections. Can you mount a spirit level on the effector, to monitor effector tilt?
-
I can add to the amount the carriage drops. Will that reset the effector back to the center of the bed?
I have no way to do the spirit level, but I did film the effector while running auto configuration.
It 166Mb so I doubt I can attach it.
I can scroll through and select frames though.
-
In looking at the video, I can absolutely state that the effector does not stay level as it moves from point to point. The base of the effector tilts through every movement. Is it possible that 360.21mm magnetic arms are too long to be used?
-
@timvukman can you put the Video in a cloud location so we can see it alternatively can you photograph the effector and carriages and paste that here?
-
@timvukman the length itself is not a factor. The spacing of the rods (pairs must be parallel) and the difference in length of a given pair(lengths must be identical) are critical in avoiding effector tilt.
I agree with the other poster, your next step should be to get the video and clear photos of the effector, carriages and arms uploaded. YouTube is pretty straightforward to upload to, but there are dozens of similar services.
-
Ok:
I have a video uploading to YouTube. It is of the effector while it is executing a G32
Hmmm if this worked, then my video is at https://youtu.be/xvyjY2aBhl8.
Facinating
-
So, now that I have found out how easy it is to post videos on you tube, I will gladly entertain specific requests
for whatever may be helpful to isolate the issues.(personal vote goes toward operator malfunction. RTFM has already proved too hard to handle.)
