Chiron+Duet3+BlTouch
-
You can use a negative value for the M208 minima to tell the firmware that the endstops are beyond the edge of the bed.
So for example if x0,y0 is the front left corner, and the endstops are 20mm beyond that set the M208 minima to -20.
@razrudy said in Chiron+Duet3+BlTouch:
G1 H2 Y-5 F6000 ; go back a few mm
Only use H2 for the Z axis in your homing files to allow it to raise and lower without being homed. For the X and Y axis the moves should either be a homing move with H1 or a regular move without any H.
-
@razrudy said in Chiron+Duet3+BlTouch:
On DWC Y-10 will move the bed forward ( towards me/ top to bottom) which means hotend is moving Y+10.
Is this the right way to set this?This sounds backwards.
Rather than thinking of the bed moving, think of the position of the print head on the bed. If the bed is moving back and away from the front, then the print head is moving closer to the front edge of the bed.
-
This post is deleted! -
@Phaedrux sorted...it was indeed reverted.....now Y+10 is "moving" the nozzle in Y+ and bed in Y- direction and is homing the right way.
-
Done with basic config and now moving to small tweaks and tunings....I am wondering how much from the start and end g-code I can move to "DWC" and what/how much should stay in slicer? Not sure if there is any benefit on having start and end g-code on DWC. I am using PrusaSlicer and like many other slicer's I can have profile's for each printer I am using. If I match the speeds, accelerations , retractions and all other between firmware and slicer there should be no problem. Plus the start and end g-code in firmware is only to "complement" the slicer.
Can I use M98 P"mymacro.g" in the slicer? -
Config file at 31/12/2020
This values are just the starting point and some speeds , accelerations , steps/mm , heaters tuning......will need to be adjusted based on your machine; Configuration file for Duet 3 (firmware version 3) ; Configuration for Chiron+Titan Aero+Volcano+BlTouch ; executed by the firmware on start-up ; General preferences G21 ; works in mm G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Chiron" ; set printer name ; Drives M569 P0.0 S1 ; physical drive 0.0 goes forwards X M569 P0.1 S0 ; physical drive 0.1 goes backwards Y M569 P0.2 S0 ; physical drive 0.2 goes bacwards ZR M569 P0.3 S0 ; physical drive 0.3 goes backwards ZL M569 P0.4 S1 D2 ; physical drive 0.4 goes forwards E M584 X0 Y1 Z2:3 E4 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80 Y100 Z400 E460 ; set steps per mm M566 X1200 Y1200 Z12 E120 ; set maximum instantaneous speed changes (mm/min) M203 X9000 Y9000 Z180 E1200 ; set maximum speeds (mm/min) M201 X1000 Y800 Z250 E250 ; set accelerations (mm/s^2) M906 X1100 Y1100 Z1100 E1100 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X-6.0 Y-9.0 Z-20 S1 ; set axis minima M208 X411 Y405 Z445 S0 ; set axis maxima-need to remeasure this M671 X-40:440 Y200:200 ; leadscrews position at right and left of the X axis ; Endstops M574 X1 S1 P"!io0.in" ; configure active-high endstop for low end on X via pin io0.in M574 Y1 S1 P"!io1.in" ; configure active-high endstop for low end on Y via pin io1.in ;M574 Z1 S1 P"io2.in+io3.in" ; configure active-high endstop for low end on Z via pin-for original endstop's M574 Z1 S2 ; endstop set to z-probe ; Z-Probe M950 S0 C"io5.out" ; create servo pin 0 for BLTouch M558 P9 C"^io5.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X41.13 Y2.69 Z1.543 ; set Z probe trigger value, offset and trigger height M557 X42:405 Y0:405 S121:81 ; define mesh grid ; Heaters M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 M307 H0 A110.3 C842.7 D1.1 S0.5 V23.8 B0 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M308 S1 P"temp1" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin temp1 M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1 M307 H1 A373.1 C420.1 D3.0 S0.5 V24.1 B0 ; disable bang-bang mode for heater and set PWM limit M143 H1 S285 ; set temperature limit for heater 1 to 285C ; Fans M950 F0 C"out4" Q25000 ; create fan 0 on pin out4 and set its frequency M106 P0 S0 H1 T45 ; set fan 0 value. Thermostatic control is turned on M950 F1 C"out5" Q25000 ; create fan 1 on pin out5 and set its frequency M106 P1 S0 H1 T45 ; set fan 1 value. Thermostatic control is turned on M950 F2 C"out7" Q25000 ; create fan 2 on pin out7 and set its frequency M106 P2 S0 H-1 ; set fan 2 value. Thermostatic control is turned off ; Tools M563 P0 D0 H1 F0:2 ; define tool 0 G10 P0 X-6.0 Y-7.0 Z0.0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ; Custom settings are not defined ; Miscellaneous M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss ;M564 H0 ; moving axes before/without homing M591 P1 C"io4.in" S1 D0 ; filament run out sensor - work in progress -
@razrudy said in Chiron+Duet3+BlTouch:
Can I use M98 P"mymacro.g" in the slicer?
Yes you can.
There is also a special macro called
start.gthat will execute when a print is started and will run before any of the sliced gcode file. This can be a good place to do machine prep like homing and preheating.Ultimately, how you split it up is entirely up to you and what makes most sense for your workflow.
-
I am trying to set the Z offset but apparently I have a problem and not sure if it's a mechanic one or I am missing something
Every time I run G30 S-1 in the same spot I get wrong values...always decreasing with 0.005 or something like this...
I am usingG30 ;Manually lower the nozzle close the build plate G92 Z0 G1 Z10 G30 S-1And after each move I get a value with 0.005-0.002 difference
02/01/2021, 16:34:26: G1 XY0 02/01/2021, 16:36:57: G30 02/01/2021, 16:43:21: G92 Z0 02/01/2021, 16:43:46: G30 S-1: Stopped at height 1.435 mm 02/01/2021, 16:43:58: G1 Z10 02/01/2021, 16:44:06: G30 S-1: Stopped at height 1.433 mm 02/01/2021, 16:44:10: G1 Z10 02/01/2021, 16:44:19: G30 S-1: Stopped at height 1.430 mm 02/01/2021, 16:44:24: G1 Z10 02/01/2021, 16:44:32: G30 S-1: Stopped at height 1.425 mm 02/01/2021, 16:44:39: G1 Z10 02/01/2021, 16:44:48: G30 S-1: Stopped at height 1.423 mm 02/01/2021, 16:44:53: G1 Z10 02/01/2021, 16:45:02: G30 S-1: Stopped at height 1.415 mm 02/01/2021, 16:45:09: G1 Z10I also have problems with mesh bed compensation...it doesn't compensate on the left side. 3/4 of the build plate is coming up nice but the left side the nozzle is always low.
My build plate is crap but until I decide which one to get and replace it I am wondering why the mesh is not applied on the left side.Maybe because the gantry doesn't properly level with the build plate? Or because the probe is at X42 offset and can't get to X0-X5 for probing?
What's the right order for levelling all this?
I am running 4 points G32 without gantry levelling until I get a good level bed and after that I run
G29 X42:400 Y0:400 P5 and M374( map save)
Load map at the start with M375 -
@razrudy said in Chiron+Duet3+BlTouch:
M558 P9 C"^io5.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X41.13 Y2.69 Z1.543 ; set Z probe trigger value, offset and trigger height
You can try improving the repeatability of the BLTouch by changing your M558 and G31 as follows
M558 P9 C"^io5.in" H5 F60 T6000 R0.2 A10
G31 P25 X41.13 Y2.69 Z1.543See if that helps.
-
So the new BLT settings didn't help. I am still getting differences at every single probe and maybe once in 7-8 I get twice the same reading.
Maybe this happens because I have flexible couplers on the Z ?
Now I am trying to figure out why my heightmap is always ~1mm up on the heightmap tab.
No matter what I am trying I am always ending with this....what I am missing?
I redid multiple times the z calibration using M561 , G92 Z0 , G30 S-1 and setting the new offset and always I end up with this. Maybe this also affect the mesh compensation?
Everything is working except this mesh/leveling thing.; Configuration file for Duet 3 (firmware version 3) with SBC ; Configuration for Chiron+Titan Aero+Volcano+BlTouch ; executed by the firmware on start-up ; General preferences G21 ; works in mm G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Chiron" ; set printer name ; Drives M569 P0.0 S1 ; physical drive 0.0 goes forwards X M569 P0.1 S0 ; physical drive 0.1 goes backwards Y M569 P0.2 S0 ; physical drive 0.2 goes bacwards ZL M569 P0.3 S0 ; physical drive 0.3 goes backwards ZR M569 P0.4 S1 D2 ; physical drive 0.4 goes forwards E M584 X0 Y1 Z2:3 E4 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80 Y100 Z400 E407.5 ; set steps per mm M566 X1200 Y1200 Z12 E120 ; set maximum instantaneous speed changes (mm/min) M203 X9000 Y9000 Z180 E1200 ; set maximum speeds (mm/min) M201 X1000 Y800 Z250 E250 ; set accelerations (mm/s^2) M906 X1100 Y1100 Z1100 E1100 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X-6.0 Y-9.0 Z0 S1 ; set axis minima M208 X400 Y400 Z445 S0 ; set axis maxima-need to remeasure this M671 X-40:440 Y200:200 ; leadscrews position at right and left of the X axis ; Endstops M574 X1 S1 P"!io0.in" ; configure active-high endstop for low end on X via pin io0.in M574 Y1 S1 P"!io1.in" ; configure active-high endstop for low end on Y via pin io1.in ;M574 Z1 S1 P"io2.in+io3.in" ; configure active-high endstop for low end on Z via pin-for original endstop's M574 Z1 S2 ; endstop set to z-probe ;Stall Detection ;M915 P0 S-5 F0 H200 R0 ; P=drive motor , S= sensitivite , H=motorstep/sec ( check home file) ; Z-Probe M950 S0 C"io5.out" ; create servo pin 0 for BLTouch M558 P9 C"^io5.in" H5 F60 T6000 R0.2 A10 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X41.13 Y2.69 Z1.378 ; set Z probe trigger value, offset and trigger height M557 X42:380 Y0:400 P3 ; define mesh grid ; Piezo Z-probe ;M558 P8 C"io5.in" I1 R0.4 F300 X0 Y0 Z1 ;new piezo ;G31 X0 Y0 Z-0.1 P100 ;new piezo ; Heaters M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 M307 H0 A110.3 C842.7 D1.1 S0.5 V23.8 B0 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M308 S1 P"temp1" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin temp1 M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1 M307 H1 A373.1 C420.1 D3.0 S0.5 V24.1 B0 ; disable bang-bang mode for heater and set PWM limit M143 H1 S285 ; set temperature limit for heater 1 to 285C ; Fans M950 F0 C"out4" Q25000 ; create fan 0 on pin out4 and set its frequency M106 P0 S0 H1 T45 ; set fan 0 value. Thermostatic control is turned on M950 F1 C"out5" Q25000 ; create fan 1 on pin out5 and set its frequency M106 P1 S0 H1 T45 ; set fan 1 value. Thermostatic control is turned on M950 F2 C"out7" Q25000 ; create fan 2 on pin out7 and set its frequency M106 P2 S0 H-1 ; set fan 2 value. Thermostatic control is turned off ;M950 F3 C"out8" Q500 ; create fan 3 on pin out8 and set its frequency ;M106 P3 S0 H-1 ; set fan 3 value. Thermostatic control is turned off ; Tools M563 P0 D0 H1 F0:2 ; define tool 0 G10 P0 X-6.0 Y-7.0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ; Custom settings are not defined ; Miscellaneous ;M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss M564 H0 ; moving axes before/without homing ;M591 P1 C"io4.in" S1 D0 ; filament run out sensor - work in progressAnd here are the last outputs for G30 S-1
03/01/2021, 15:13:54: G30 S-1: Stopped at height 0.068 mm 03/01/2021, 15:14:03: G1 Z10 03/01/2021, 15:14:21: G30 S-1: Stopped at height 0.075 mm 03/01/2021, 15:14:24: G1 Z10 03/01/2021, 15:14:39: G30 S-1: Stopped at height 0.070 mm 03/01/2021, 15:14:43: G1 Z10 03/01/2021, 15:14:59: G30 S-1: Stopped at height 0.065 mm 03/01/2021, 15:17:59: Upload of config.g successful after 0s 03/01/2021, 15:18:00: : Warning: Firmware reset imminent 03/01/2021, 15:18:00: : Connection to Duet established 03/01/2021, 15:18:00: Connection interrupted, attempting to reconnect...: DCS has been stopped 03/01/2021, 15:18:09: Connection established 03/01/2021, 15:21:33: : Warning: the height map has a substantial Z offset. Suggest use Z-probe to establish Z=0 datum, then re-probe the mesh. 03/01/2021, 15:21:33: G29: 9 points probed, min error 0.506, max error 0.940, mean 0.783, deviation 0.134 Height map saved to file heightmap.csv 03/01/2021, 15:38:52: G30 03/01/2021, 15:41:22: G92 Z0 03/01/2021, 15:41:40: G1 Z10 03/01/2021, 15:41:55: G30 S-1: Stopped at height 1.668 mm 03/01/2021, 15:41:58: G1 Z10 03/01/2021, 15:42:12: G30 S-1: Stopped at height 1.665 mm 03/01/2021, 15:42:14: G1 Z10 03/01/2021, 15:42:29: G30 S-1: Stopped at height 1.663 mm 03/01/2021, 15:42:41: G1 Z10 03/01/2021, 15:42:54: G30 S-1: Stopped at height 1.670 mm 03/01/2021, 15:43:02: G1 Z10 03/01/2021, 15:43:20: G30 S-1: Stopped at height 1.668 mm 03/01/2021, 15:44:05: Upload of config.g successful after 0s 03/01/2021, 15:44:06: : Warning: Firmware reset imminent 03/01/2021, 15:44:07: : Connection to Duet established 03/01/2021, 15:44:07: Connection interrupted, attempting to reconnect...: DCS has been stopped 03/01/2021, 15:44:15: Connection established 03/01/2021, 15:50:35: : Warning: the height map has a substantial Z offset. Suggest use Z-probe to establish Z=0 datum, then re-probe the mesh. 03/01/2021, 15:50:35: G29: 9 points probed, min error 0.550, max error 1.164, mean 0.872, deviation 0.180 Height map saved to file heightmap.csv 03/01/2021, 18:13:07: G30 03/01/2021, 18:14:56: G92 Z0 03/01/2021, 18:15:06: G1 Z10 03/01/2021, 18:15:23: G30 S-1: Stopped at height -1.138 mm 03/01/2021, 18:15:26: G1 Z10 03/01/2021, 18:15:43: G30 S-1: Stopped at height -1.140 mm 03/01/2021, 18:15:46: G1 Z10 03/01/2021, 18:16:05: G30 S-1: Stopped at height -1.145 mm 03/01/2021, 18:16:36: G1 Z10 03/01/2021, 18:16:52: G30 S-1: Stopped at height -1.133 mm 03/01/2021, 18:16:57: G1 Z10 03/01/2021, 18:17:24: G30 S-1: Stopped at height -1.143 mm 03/01/2021, 19:26:40: M561 03/01/2021, 19:27:14: G92 Z0 03/01/2021, 19:28:08: G30 S-1: Stopped at height 1.395 mm 03/01/2021, 19:28:13: G1 Z5 03/01/2021, 19:28:23: G1 Z10 03/01/2021, 19:28:36: G30 S-1: Stopped at height 1.395 mm 03/01/2021, 19:28:41: G1 Z10 03/01/2021, 19:28:59: G30 S-1: Stopped at height 1.388 mm 03/01/2021, 19:29:13: G1 Z10 03/01/2021, 19:29:16: G1 Z10 03/01/2021, 19:29:18: G1 Z10 03/01/2021, 19:29:35: G30 S-1: Stopped at height 1.388 mm 03/01/2021, 19:29:38: G1 Z10 03/01/2021, 19:30:01: G30 S-1: Stopped at height 1.385 mm 03/01/2021, 19:30:14: G1 Z10 03/01/2021, 19:30:27: G1 Z10 03/01/2021, 19:30:39: G30 S-1: Stopped at height 1.375 mm 03/01/2021, 19:30:49: G1 Z10 03/01/2021, 19:31:16: G30 S-1: Stopped at height 1.372 mm 03/01/2021, 19:32:07: G1 Z10 03/01/2021, 19:32:52: G30 S-1: Stopped at height 1.378 mm 03/01/2021, 19:35:32: Upload of config.g successful after 0s 03/01/2021, 19:35:34: : Warning: Firmware reset imminent 03/01/2021, 19:35:34: : Connection to Duet established 03/01/2021, 19:35:34: Connection interrupted, attempting to reconnect...: DCS has been stopped 03/01/2021, 19:35:43: Connection established 03/01/2021, 19:39:46: : Warning: the height map has a substantial Z offset. Suggest use Z-probe to establish Z=0 datum, then re-probe the mesh. 03/01/2021, 19:39:47: G29: 9 points probed, min error 0.474, max error 1.061, mean 0.821, deviation 0.175 Height map saved to file heightmap.csvI am out of ideas and most likely it's just a small mistake somewhere but can't figure out where the problem is
-
I had the same heightmap offset problem a couple of days ago. The documentation is a bit ambiguous. I seem to have solved the problem by doing this in the calibration run (I use a macro).
; Heat Bed and Hotend - Home and Calibrate T0 ;make sure the tool is selected G90 ; use absolute coordinates M83 ; extruder relative mode M117 "Setting Calibration Temperatures" <snip> M290 R0 S0 ;remove any babysteps M561 ; reset any bed compensation M117 "Performing Mesh Calibration" G28 ; must be homed first G30 ; Perform a single probe to establish Z=0 (should already be at center because of home) G29 S0 ; perform mesh calibration save and loadI did a reboot at this point but am not sure if it's at all required.
Then this at the start of the print job
T0 ; turn on the tool M561 ; Remove any Bed Compensation G90 ; use absolute coordinates M83 ; extruder relative mode <snip> G28 ; home all G30 ; probe bed just to make sure G29 S1 ; enable mesh leveling <snip>I suspect there may be redundancy in my codes but .....
-
That's something I was thinking that there is some residue code that can't be seen on files and messing everything. think I will just save the config and make a new sd card and see how the things are working. ...after I will try your code.
-
@razrudy said in Chiron+Duet3+BlTouch:
Maybe this happens because I have flexible couplers on the Z ?
That could be part of it.
@Phaedrux said in Chiron+Duet3+BlTouch:
G31 P25 X41.13 Y2.69 Z1.543
You forgot to change it to G31 P25
@razrudy said in Chiron+Duet3+BlTouch:
03/01/2021, 15:21:33: : Warning: the height map has a substantial Z offset. Suggest use Z-probe to establish Z=0 datum, then re-probe the mesh.
This would indicate that you're not setting Z0 correctly before running G29 to create a mesh.
When you're doing G92 Z0 you've moved the nozzle to touch the bed first, right?
The inconsistency could certainly be from movement in the Z axis couplers.
-
@stuartofmt said in Chiron+Duet3+BlTouch:
I had the same heightmap offset problem a couple of days ago. The documentation is a bit ambiguous. I seem to have solved the problem by doing this in the calibration run (I use a macro).
; Heat Bed and Hotend - Home and Calibrate T0 ;make sure the tool is selected G90 ; use absolute coordinates M83 ; extruder relative mode M117 "Setting Calibration Temperatures" <snip> M290 R0 S0 ;remove any babysteps M561 ; reset any bed compensation M117 "Performing Mesh Calibration" G28 ; must be homed first G30 ; Perform a single probe to establish Z=0 (should already be at center because of home) G29 S0 ; perform mesh calibration save and load@stuartofmt this also worked for me..at least visual is now back in the right place...I will run a print and see how it goes. And now I have the home point at Z0.0
-
@Phaedrux said in Chiron+Duet3+BlTouch:
@Phaedrux said in Chiron+Duet3+BlTouch:
G31 P25 X41.13 Y2.69 Z1.543
You forgot to change it to G31 P25
how did I miss that?@razrudy said in Chiron+Duet3+BlTouch:
03/01/2021, 15:21:33: : Warning: the height map has a substantial Z offset. Suggest use Z-probe to establish Z=0 datum, then re-probe the mesh.
This would indicate that you're not setting Z0 correctly before running G29 to create a mesh.
When you're doing G92 Z0 you've moved the nozzle to touch the bed first, right?
I am following the guide on dozuki
Cancel any currently active mesh compensation with M561 Use the X and Y jog buttons to position the nozzle over the centre of the bed Jog the nozzle down until it is just touching the bed or just gripping a sheet of paper. If the firmware doesn't let you jog it down far enough, send M564 S0 to disable axis limits. Once you have the nozzle touching the bed, send command G92 Z0 to tell the firmware that the head is at Z=0 Jog the head up by 5 to 10mm Send command G30 S-1. The nozzle will descend or the bed rise until the probe triggers and the Z height at which the probe stopped will be reported. If you are using a nozzle-contact Z probe, the trigger height will be slightly negative. For any other type of Z probe where the probe triggers before the nozzle contacts the bed, it will be positive. Repeat from step 5 two or three times to make sure that the trigger height is consistent. In Duet Web Control, go to Settings -> System Editor and edit the config.g file. Set the Z parameter in the G31 command to the trigger height that was reported. Save the file. Open config-override.g and check that there are no G31 commands in it. If you find any, delete those lines and save the file. To apply the new trigger height, restart the Duet by sending M999 or pressing Emergency Stop.The only difference is that I point the probe to the middle of the bed not the nozzle.
M561
Probe pin to centre of the bed
Lower nozzle to touch the bed( paper method)
G92 Z0
G1 Z10
G30 S-1 -
@razrudy said in Chiron+Duet3+BlTouch:
G28 ; must be homed first G30 ; Perform a single probe to establish Z=0 (should already be at center because of home)
This is a pretty ambiguous combination because we can't see what the homeall is doing to home the Z axis, and we have no idea what XY location the G30 is being done in.
The important thing to remember is that the Z0 position is set in the same XY position whenever you set it. Your homeall, homez, and any other time you use G30 must be in the same position before and after G29 is used to create or load the height map. This is because the shape of the bed may give you a different z height depending on the XY location.
-
In my case homeall.g looks like this (homez sets to the same position) ... But I think you also answered one of the ambiguities in the documentation i.e. what coordinate (XY) is the bed height relative to. Seems the answer is "Wherever you set your Z-home"? EDIT: which needs be the same as your Z=0 datum.?
G91 ; relative mode G0 H2 Z10 F200 ; raise head above Z probe trigger height G0 H1 X-240 Y-240 F3000 ; move up to 240mm in the -X and -Y directions until the homing switches are triggered G0 H2 X5 Y5 F600; move slowly 5mm in +X and +Y directions G0 H1 X-10 Y-10 ; move up to 10mm in the -X and -Y directions until the homing switches are triggered G90 ; back to absolute mode G1 X110 Y110 F2000 ; put head over the center of the bed, or wherever you want to probe G30 ; lower head, stop when probe triggered and set Z to trigger height -
Yes I made sure that every mesh starts from the same point....
Looking at the DWC now before I run this macro my home position was X-12 and Y-14 instead of the real X-6 Y-7 so I had something doubled in my steps. Now everything is normal only by running that macro.
I suspect there was something related to baby steps but I never went more then 3mm up/down during printing and it's just strange how it was exactly double compared with the original values.
Also tried to manually delete the heightmap , any mesh level maps I had saved and using G29 S2 with no resultNow I am trying to figure out how I can do a mesh level starting from the centre of the bed instead of the home position because my centre bed is the lowest point.
G28
M98 P"move_probe_center _bed.g"
G29 S0
will work or how it will be the best?
Making specific points for probing on the bed.g will work?Thinking that the lowest point will be under Z0 and I may not get the nozzle down enough...or it will compensate below Z0?
-
I am back on the same situation....tried to do a print and there was no mesh compensation applied. after I cancelled the print I did a G29 and my height map is back "in air" with ~1mm......time to reset everything and start from scratch
-
Maybe reshare all your gcode files including start gcode
