effector tilting into bed on print

Danal

@timvukman said in effector tilting into bed on print:

@danal
I was under the impression that "Auto Delta Configuration" was supposed to make the changes (I presume in the conf or override files) by itself, whether that is to adjust the diagonal length, or radius, etc.

Auto Delta Config (which is the same as issuing G32) updates different things depending on the contents of the bed.g file. In particular the last G30 in bed.g will have an S parameter.

There are a lot of choices, but I tend to use S6 or S8 on Delta Printers. More info here:

https://duet3d.dozuki.com/Wiki/Calibrating_a_delta_printer#Section_Setting_up_the_bed_g_file

Danal

And, G32 does work (assuming no error messages), but it does NOT save its results across power cycles (and/or reboots). To save the results, issue:

M500

Also, the saved results must be reloaded. In your 'config.g', place an M501 somewhere near the end of the file.

.

By the way, you can look at what it saved. M500 really writes a file called "config-override.g". M501 reads that same file. You can look in that file with the system editor. When calibrating, your primary interest will be to compare the M665 command in 'config-override.g' vs. the one in 'config.g'.

Danal

And, last, the map you are showing is from mesh bed leveling. Get CALIBRATION (G32) working to your satisfaction before you mess with leveling...

TimVukman

Hi Danal
I have run auto config (g32) many times. ( and did an M500, then power cycled the printer)

Should I be running it in stages, ie a different value of S in bed.g starting at 4 and working up?

I did some manual adjustments in bed.g - H value, based on probing each point individually subtracting the center point result from the returned result.

My observation is that I sent the G0 with x and y values, which the printer moved to. When I issue the G30 S-1, the effector moved to center from where it was after the G0, and then probes there.

It was my understanding that the process I needed to follow was to determine the trigger height at center, including a sheet of paper and then set that as the 0 value for Z From there, the documentation directs you to adjusting the heights of the probing points in the bed.g file.

The only changes I have ever seen in the config.g.bak file are the height values that I manually added by putting them in there when G32 did not edit the file.

I have followed the Auto Calibration instructions to the letter. G32 does nothing.
I have run M665 and M666 without parameters and I get the values that are in my config.g file. M666 returns 0 across the board as the adjustments made.

I got onto the bed mesh map hoping that it would show me the changes as a visual.

It would appear to me then, that the issue is getting G32 to work.

While G32 is running, I get no feedback from the software interface. No coordinates change values, and nothing pops up on the screen to indicate any values when the bed is probed.

What steps can I take to find out what is going on?
Thanks
Tim

dc42

No need to run it in stages, you can use S6 or S8 from the start.

TimVukman

Hi dc42

Thanks! I have run it with 4 and have moved on to 6.

How do I know if it is working? I get not feedback at all.

Thanks
Tim

adavidm

Feedback appears in the console section of the interface, either PanelDue or DWC, depending on where you ran it from.

TimVukman

Hi
Here's what I see after running G32

3:42:51 PMM665
Diagonal 360.200, delta radius 103.000, homed height 203.000, bed radius 85.0, X 0.000°, Y 0.000°, Z 0.000°

3:43:04 PMM666
Endstop adjustments X0.00 Y0.00 Z0.00, tilt X0.00% Y0.00%

So, these parameters are what I entered in my config.g file. Nothing has been added / changed by running G32. Since it does not say if it was successful, or not, I don't know what to do with this information, and I don't know what steps to take next to understand why the effecter is moving down into the bed when I start to print.

I am including the Config-override.g content again as I see nothing there to indicate any changes or overrides.

; This is a system-generated file - do not edit
; Delta parameters
M665 L360.200 R103.000 H203.000 B85.0 X0.000 Y0.000 Z0.000
M666 X0.000 Y0.000 Z0.000 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 B0

It would appear, then, (to me), that my configuration information is ok.

Where do I go from here?

Should I now be looking at bed levelling?

Thanks
Tim

dc42

There should be a response from the G32 command, provided that the last G30 command in bed.g has the S parameter. Please share the bed.g file you used.

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 ...