effector tilting into bed on print

TimVukman

; bed.g
; called to perform automatic delta calibration via G32
;
; generated by RepRapFirmware Configuration Tool on Wed Jun 13 2018 16:33:57 GMT-0400 (Eastern Daylight Time)
M561 ; clear any bed transform
G28 ; home all towers
; Probe the bed at 3 peripheral and 3 halfway points, and perform 4-factor auto compensation
; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g.
G30 P0 X0 Y79.16 H0 Z-99999 ;Z Vertical Post
G30 P1 X61.72 Y-35.64 H0 Z-99999 ;Y Vertical Post
G30 P2 X-69.28 Y-40 H0 Z-99999 ;X Vertical Post
G30 P3 X0 Y38.48 H0 Z-99999 ;Between Z and Center
G30 P4 X27.75 Y-16.02 H0 Z-99999 ;Between Y and Center
G30 P5 X-34.64 Y-20 H0 Z-99999 ;Between X and Center
G30 P6 X0 Y0 H0 Z-99999 S6 ;Center
; Use S-1 for measurements only, without calculations. Use S4 for endstop heights and Z-height only. Use S6 for full 6 factors
; If your Z probe has significantly different trigger heights depending on XY position, adjust the H parameters in the G30 commands accordingly. The value of each H parameter should be (trigger height at that XY position) - (trigger height at centre of bed)

dc42

That looks OK to me. After probing the centre point, whichever device you sent the G32 command from should display the calibration result (on the Console page if it was sent from DWC or PanelDue). Something like this:

G32
Calibrated 8 factors using 16 points, deviation before 0.186 after 0.026

TimVukman

I started G32 from the duet display. (pushed on the keyboard picture, entered G32 and return) The machine goes through the process. At the end, the process stopped centered on the bed.

There was no text displayed in the little screen.

While running, the effector does not dive far enough to click the Effecter switch at every position. It clicks on most, but certainly not all.

I have cleared the log file in the browser

"1:01:18 PMG32
12:57:55 PMG32
12:57:47 PMMessage Log cleared!"

That's all I see.

TimVukman

Software Information
Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later
Firmware Version: 2.0(RTOS)RC6 (2018-05-29b4)
WiFi Server Version: 1.21
Web Interface Version: 1.21
Web Interface by Christian Hammacher
Licensed under the terms of the GPL v3

TimVukman

I should have added above that I cleared the log before I ran G32 from the browser window.
Nothing shows. That's the version of the log that is displayed

dc42

@timvukman said in effector tilting into bed on print:

G30 P6 X0 Y0 H0 Z-99999 S6 ;Center

If it is probing all the points including the centre one at the end, then it looks like it isn't processing the S6 part of the final G30 command. So I suggest you try deleting and re-typing that line in case it contains a non-printing character. You could also try changing S6 to something non-sensical such as S20, which should provoke an error message

TimVukman

Hi
10:53:22 AMG32
10:50:12 AMMessage Log cleared!

This is the result of clearing the log and running G32. Please note that the value in Bed.g for S in the last G30 is S30.

I have retyped the line

TimVukman

I deleted Bed.g. That was noticed! G32 would not run since the Macro was deemed missing

Danal

Try generating a completely new bed.g here:

http://www.escher3d.com/pages/wizards/wizardbed.php

TimVukman

I would appreciate so clarification on the G31 in Config.g
Here is mine
G31 P500 X11 Y0 Z-1.209

I am clear on Z-1.209 as that is my actual trigger height at center
I am clear on the P500 as that is the value of the Z probe for a mechanical switch

I'm not so clear on the X and Y values. In reading the documentation here,
https://duet3d.dozuki.com/Wiki/Gcode#Section_G30_Single_Z_Probe

for the G31 code,

"Xnnn Probe X offset(note)1
Ynnn Probe Y offset(note)1

Notes

(note)1X and Y offsets of the Z probe relative to the print head (i.e. the position when the empty tool is selected) can be specified. This allows you to calculate your probe coordinates based on the geometry of the bed, without having to correct them for Z probe X and Y offset."

I do not see how this functions. My understanding is that these values should identify the location of the actual switch relative to the nozzle since in my case, the nozzle contacts the bed to trip the switch.
In my G31 above, is it not saying that my nozzle is 11mm closer to the X pillar than my switch is? This would make the switch think it is measuring a value for X0, Z0 when the nozzle is physically at X0, Y0. I'm going to have to measure the 11mm. I don't think it is correct and I don't know where it came from. I might be a number from the manufacturer.

Danal

@timvukman said in effector tilting into bed on print:

My understanding is that these values should identify the location of the actual switch relative to the nozzle since in my case, the nozzle contacts the bed to trip the switch.

Yes. Conceptually correct.

.

Imagine a printer where the Z-Probe just triggered, and that the particular nozzle and Z-probe on our imaginary printer are mounted such that the probe triggers when the bed is 8.492mm below the nozzle, and the probe is mounted so that the probe's "sensor center" is 10mm in the plus X direction from the nozzle, and 5mm in the minus Y direction.

That would result in:

G31 X10 Y-5 Z-8.492

If, in your case, the nozzle IS the probe, the G31 will probably look something like this:

G31 X0 Y0 Z-0.1

Zero for X and Y, because the nozzle is the probe. Z- because the nozzle has to move a tiny bit "up" to sense, thus making it as though "the sensor is mounted a fraction above the nozzle". -0.1 is a starting guess. It may be -0.05 or -0.15 or ...

TimVukman

Thanks Danal
Here is the new beg.g file
; bed.g file for RepRapFirmware, generated by Escher3D calculator
; 10 points, 6 factors, probing radius: 10, probe offset (0, 0)
G30 P0 X0.00 Y10.00 Z-99999 H0
G30 P1 X8.66 Y5.00 Z-99999 H0
G30 P2 X8.66 Y-5.00 Z-99999 H0
G30 P3 X0.00 Y-10.00 Z-99999 H0
G30 P4 X-8.66 Y-5.00 Z-99999 H0
G30 P5 X-8.66 Y5.00 Z-99999 H0
G30 P6 X0.00 Y5.00 Z-99999 H0
G30 P7 X4.33 Y-2.50 Z-99999 H0
G30 P8 X-4.33 Y-2.50 Z-99999 H0
G30 P9 X0 Y0 Z-99999 S6

My bed is 220mm. I used 100mm as the radius in the formula

I get no messages, and nothing is recorded in the g-code console.

I watched it very carefully as something caught my eye while doing this so many times.

The effector goes off to a spot between my X and Z columns and lowers, but not enough to trip the Z switch, and then it moves left to just past the Z column and dips down again without triggering. It then centers and triggers.

I think it is doing the same thing 10 times and then stops.

Do you think maybe I've got a couple of axis motors mixed up?

I will check, but that is going to make me feel terrible if this has been for a dumb mistake.
If that's the case, it would still home properly, right? and I could still set my trigger height?
I'll update soon

Tim

TimVukman

my columns are

Y X

Is this correct?

TimVukman

Ok, The correct wires from the board go to the correct motors.

Whew!!

dc42

@timvukman said in effector tilting into bed on print:

The effector goes off to a spot between my X and Z columns and lowers, but not enough to trip the Z switch, and then it moves left to just past the Z column and dips down again without triggering. It then centers and triggers.

If you have deployprobe.g and retractprobe.g files in /sys that you didn't create yourself, delete them.

Danal

Looking at the printer, Z tower (motor, endstop) in the back, X to your left, Y to your right.

Then check movement. Make all moves with web control, if any validation step fails, stop and report back:

Home All (or G28) Validation: Proper home move.
Move Z downward, so web commands will be "negative" buttons. Move -50. Validation: Effector moves down, and stays centered between towers.
Move Y +100. Validation: Effector should move STRAIGHT TOWARD Z TOWER; and effector does not change height above bed at all. Yes, confusingly enough, Y+ is straight toward Z tower.
Move Y -100. Validation: Effector moves back to center, does not change height above bed.
Move X +100. Validation: Effector moves to a position NOT aligned with ANY tower... it will be between the Z and Y towers, about 2/3 toward the Y tower. (Of course, it is 90 degrees from the Y axis we found in step(3)... and 90 degrees is about 2/3 off from the 120 degree spacing of the towers). Height above bed should not change.

That validates every kind of move.

TimVukman

Home All (or G28) Validation: Proper home move.
Confirmed to have worked properly and registered in the system (web buttons Home X, Home Y, and Home Z turned blue. X is 0. Y is 0. Z is 198

Move Z downward, so web commands will be "negative" buttons. Move -50. Validation: Effector moves down, and stays centered between towers.
Confirmed that effector moved down 5 shots of 10 and is still centered. X is 0. Y is 0. X is Z is 148

Move Y +100. Validation: Effector should move STRAIGHT TOWARD Z TOWER; and effector does not change height above bed at all. Yes, confusingly enough, Y+ is straight toward Z tower.
Effector has moved to sit directly in front of the Z column. Height is 148. X is 0, Y is 80. Diagonal rods are almost, but not quite vertical.

Move Y -100. Validation: Effector moves back to center, does not change height above bed.
Effector has moved back to about center. Height is 148 X is 0, Y is -15

Move X +100. Validation: Effector moves to a position NOT aligned with ANY tower... it will be between the Z and Y towers, about 2/3 toward the Y tower. (Of course, it is 90 degrees from the Y axis we found in step(3)... and 90 degrees is about 2/3 off from the 120 degree spacing of the towers). Height above bed should not change.
It looks about right. X is 84.1 Y is -12.6 Z is 148

I took the top apart before I did what was above, because I had a small gap on one rail.

I had my motors / columns as described above which mean that I needed to swap X with Y to match the positions as you described them. I swapped the end stops as well.

One significant observation came when I removed the bed to trace the wires. On the left side, the bracket that clips on the rail and holds the female nut for the bed was not sitting down flat on the rail. It look like one end bent into the side of the rail. There was a definite fold line in the clip. I straightened that and put the clip back in place. It is now sitting flat. I believe that to be cause of the problem, IE the be was 1/8" higher there.

I ran Auto Delta Configuration from the browser interface. The start is not registered in the G-Code Console. There are no messages indicating pass, fail, or error in the G-Code Console.

There have been no changes in Config-Override.g.

I noticed that in my bed.g file, I had entered the radius as 10 instead of 100.

Fixed, created a new bed.g file.

The Auto Configuration certainly changed where it was probing and now appears appropriately spread out.

The was no on screen message during or after running Auto Configuration. There are no new messages in the G-Code Console. There are no changes or additions to the H values in the Bed.G file. There are no changes in Config-Override.g,

dc42

Did you see my earlier reply?

If you have deployprobe.g and retractprobe.g files in /sys that you didn't create yourself, delete them.

TimVukman

Hi dc42
Yes, I read it, but I did not delete the files as I forgot about it in swapping everything else around. I have now deleted the files and am pleased to report that I got a message on the screen and in G-Code console at the end of the AutoConfig.

"G32
Calibrated 6 factors using 10 points, deviation before 2.988 after 0.107"

M665 reported different settings than those that I entered in my Config.g.

**M665

Diagonal 360.200, delta radius 124.727, homed height 204.383, bed radius 85.0, X -0.501°, Y -4.385°, Z 0.000°**

**× M666

Endstop adjustments X2.88 Y1.39 Z-4.27, tilt X0.00% Y0.00%**

TimVukman

Ok
I ran Auto Configuration again, and I should not have done that.

My effector left the area defined by the bed. I killed it with emergency stop after one of the magnetic rods popped off the carriage. I don't think M500 was a good idea.

I have my original values for Config.g G31 written down.

Please advise as to how I should proceed. I will leave it alone until I hear back.