Mesh grid compensation - Setup on Initial Gcode
-
@FelixH said in Mesh grid compensation - Setup on Initial Gcode:
@fcwilt said in Mesh grid compensation - Setup on Initial Gcode:
Perhaps the height map is being load somewhere else before you are doing the G30?
Frederick
this is my initial Gcode, set on the Slicer. Clearly the G30 command is sent before the G29 S1
G28 ; home all axes G1 Z15. ; go close to to the surface G30 ; Z=0 datum thing G1 Z75 ; go up a bit M291 P"Remove probe" R"Warning" S3 ; warning message G29 S1 ;use mesh grid to compensate G92 E0 G1 F1200 E10 G92 E0Yeah I'm not sure why it would still be giving you the warning about not establishing Z0 with a probe result when that's what your gcode order is doing.
-
@Phaedrux said in Mesh grid compensation - Setup on Initial Gcode:
Yeah I'm not sure why it would still be giving you the warning about not establishing Z0 with a probe result when that's what your gcode order is doing.
That's what I was hoping somebody could help me with...
-
Hi all,
I've been brainstorming by myself for a couple of days again about it and I'm still on the same place... could it have something to do with the absence of homeall.g? When I tap on the "Home all" icon, it homes all the axes just fine...
-
@FelixH well you have a delta so homedelta is your homeall far as I know.
-
that was my thought as well, but given it still does not work as it should...
-
For the sake of taking another fresh run at this, can you please provide your current config.g, bed.g, homedelta.g, your start gcode, a picture of your mesh heightmap, and a summary of the problem as it currently is?
-
The summary of the problem:
The following warning is thrown at the PanelDue / Webinterface every time I try to print something:
Warning: the height map was loaded when the current Z=0 datum was not determined probing. This may result in a height offset.even though and as far as I have been able to see, it's the right way to do it. The probe I use is one that was delivered with my printer, one of those limit switches attached with a magnet. I can understand how this is not the ideal probe, but so far is the one I have, and I see no reason for the warning message.
config.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 Thu Jul 12 2018 20:54:00 GMT-0500 (Central Daylight Time) ; General preferences G90 ; Send absolute coordinates... M83 ; ...but relative extruder moves ; After G32 auto-calibrate, copied from config-override.g ; Note: G31 Z (below) affects M665 H, and this is NOT yet calibrated. M665 L267.0 R132.382 H301.20 B106.0 X-0.174 Y0.096 Z0.0 ; Set delta radius, diagonal rod length, printable radius and homed height M666 X-0.14 Y-0.16 Z0.30 A0.00 B0.00 ; Put your endstop adjustments here, or let auto calibration find them ; Network M550 P"Kossel" ; Set machine name M552 S1 ; Enable network ;*** Access point is configured manually via M587 M586 P0 S1 ; Enable HTTP M586 P1 S0 ; Disable FTP M586 P2 S0 ; Disable Telnet ; Drives M569 P0 S0 ; Drive 0 goes forwards M569 P1 S0 ; Drive 1 goes forwards M569 P2 S0 ; Drive 2 goes forwards M569 P3 S1 ; Drive 3 goes forwards M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation M92 X80 Y80 Z80 E96 ; Set steps per mm M566 X300 Y300 Z300 E300 ; Set maximum instantaneous speed changes (mm/min) M203 X12000 Y12000 Z12000 E12000 ; Set maximum speeds (mm/min) M201 X3000 Y3000 Z3000 E3000 ; Set accelerations (mm/s^2) M906 X1000 Y1000 Z1000 E1000 I50 ; Set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 Z0 S1 ; Set minimum Z ; Endstops M574 X2 Y2 Z2 S1 ; Set active high endstops ; Z-Probe M558 P4 H5 F120 T6000 ; Set Z probe type to switch and the dive height + speeds G31 P1000 X0 Y0 Z16.10 ; Set Z probe trigger value, offset and trigger height M557 R105 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 B4267 C0 R4700 ; Set thermistor + ADC parameters for heater 0 M143 H0 S95 ; Set temperature limit for heater 0 to 120C M305 P1 T100000 B4267 C0 R4700 ; Set thermistor + ADC parameters for heater 1 M143 H1 S280 ; Set temperature limit for heater 1 to 280C M307 H1 A452.1 C123.2 D7.5 V12.5 B0 ;Hotend Autotune //Changed M307 H0 A158.1 C 741.8 D0.7 V12.3 B0 ;Bed Autotune //Changed ; Fans M106 P0 S0 I0 F500 H-1 ; PART FAN - Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off M106 P1 S1 I0 F500 H1 T45 ; HOTEND FAN - Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on M106 P2 S0.20 I0 F500 H-1 ; ELECTRONICS FAN - Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off ; 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 configuredbed.g
; bed.g ; called to perform automatic delta calibration via G32 ; ; generated by RepRapFirmware Configuration Tool on Thu Jul 12 2018 20:54:00 GMT-0500 (Central Daylight Time) M561 ; clear any bed transform G28 ; home all towers ; Probe the bed at 6 peripheral and 3 halfway points, and perform 6-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 Y104.9 H0 Z-99999 G30 P1 X90.85 Y52.45 H0 Z-99999 G30 P2 X90.85 Y-52.45 H0 Z-99999 G30 P3 X0 Y-104.9 H0 Z-99999 G30 P4 X-90.85 Y-52.45 H0 Z-99999 G30 P5 X-90.85 Y52.45 H0 Z-99999 G30 P6 X0 Y52.4 H0 Z-99999 G30 P7 X45.38 Y-26.2 H0 Z-99999 G30 P8 X-45.38 Y-26.2 H0 Z-99999 G30 P9 X0 Y0 H0 Z-99999 S6 ; 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)homedelta.g
; homedelta.g ; called to home all towers on a delta printer ; ; generated by RepRapFirmware Configuration Tool on Thu Jul 12 2018 20:54:00 GMT-0500 (Central Daylight Time) G91 ; relative positioning G1 S1 X355 Y355 Z355 F1800 ; move all towers to the high end stopping at the endstops (first pass) G1 X-5 Y-5 Z-5 F1800 S2 ; go down a few mm G1 S1 X10 Y10 Z10 F360 ; move all towers up once more (second pass) G1 Z-5 F6000 ; move down a few mm so that the nozzle can be centred G90 ; absolute positioning G1 X0 Y0 F6000 ; move X+Y to the centreinitial g-code
G28 ; home all axes M291 P"Attach probe" R"Warning" S3 ; warning message G1 Z15. ; go close to to the surface G30 ; Z=0 datum thing G1 Z75 ; go up a bit M291 P"Remove probe" R"Warning" S3 ; warning message G28; home again, in case the effector move by the removal of the probe G29 S1 ;use mesh grid to compensate G92 E0 G1 F1200 E10 G92 E0Picture of the mesh: please see avobe, I haven't measured again since
Many thanks for your worries!
-
While testing, I have just seen that when the G30 command is triggered, the following warning is shown on the Web Interface, but not on the PanelDue display:
Error: Z probe already triggered at start of probing movewhich I don't understand because is seems ok when it maps the bed...
-
@FelixH said in Mesh grid compensation - Setup on Initial Gcode:
Error: Z probe already triggered at start of probing move
That's odd. Does the switch signal need to be inverted?
-
@Phaedrux said in Mesh grid compensation - Setup on Initial Gcode:
@FelixH said in Mesh grid compensation - Setup on Initial Gcode:
Error: Z probe already triggered at start of probing move
That's odd. Does the switch signal need to be inverted?
I tried to invert it with the expected result: crash onto the bed. I followed all the articles I could possibly find and I'm pretty sure the probe is well connected. When is is deployed (aka connected) the light on the board is lit and the Z prove value on the web interface is 0. When I press the switch, the value ramps up to 1000 and the led is off...
I'm really running out of thing to try
-
G28 ; home all axes M291 P"Attach probe" R"Warning" S3 ; warning message G1 Z15. ; go close to to the surface G30 ; Z=0 datum thing G1 Z75 ; go up a bit M291 P"Remove probe" R"Warning" S3 ; warning message G28; home again, in case the effector move by the removal of the probe G29 S1 ;use mesh grid to compensate G92 E0 G1 F1200 E10 G92 E0I had written up a long post with a few things to test, but then I saw something that I think is the cause of the problem.
If you look at your start gcode, you home the towers, attach the probe, probe the bed, and then home the towers again, resetting the z datum, and then load the heightmap.
Remove the second G28. In fact, also remove the G29 S1 for now, since I don't trust the heightmap. If your homed height is correct, and the probe is accurate, and your initial delta calibration is good, you should at least be able to reliably get Z0 to touch the bed as it should at the same spot you probe the bed at.
If that works, re run the G29 to generate a new map after you've done another G30 at the center of the bed, but DON'T home the towers between that G30 and the G29.
-
this is something that I added this afternoon. But I will try you suggestion anyway. However, when I do a G1 Z0 for instance, the nozzle goes to a nice bed distance, but the print fails because no map is loaded...
I'll try your approach, however. -
I did the G30, and G29 S1 and tried it again without a second G28... nothing.
-
@FelixH alright. The gist of my alternate approach if this doesn't prove fruitful was to test using m558 P0 to use manual probing as a control experiment.
-
yeah, I think that's the next step. Just for the sake of it I tried to use the Stall Detection as probe (P10) but it didn't work...
-
@FelixH said in Mesh grid compensation - Setup on Initial Gcode:
Stall Detection as probe
Yeah that would be fundamentally impossible on a delta I think.
-
@Phaedrux said in Mesh grid compensation - Setup on Initial Gcode:
@FelixH alright. The gist of my alternate approach if this doesn't prove fruitful was to test using m558 P0 to use manual probing as a control experiment.
well, just tried that and it worked without errors. As it should.
Not only that, but I am also printing the model it gave everything away. At least I have confirmation that the problem was not reading the bed map.
-
So the probe is working for the height map creation with g29 but not for just setting the z0 with g30?
-
It appears so. Although when I send G30 followed by a G29 S1 from the console, no error or warning appears on the screen
-
@FelixH that's good. That's as it should be. Does that include g30 with the probe or manual?
