@guitartoys You can't do G30 X0 Y20 (the X and Y are ignored in that case), so you will need to move to your homing X/Y first and then run G30 (with no parameters). Where on the bed do you normally print things? If like most people you normally print in the centre of the bed I would change the point you use to home z (ser z=0) to be that location.

@fcwilt I have now... I made two mistakes. The first was using G1 H2 and thinking it was G1 H1. Getting diagonal movements expecting horizontal sent me on a wild goose chase. The other is as mentioned in the article; 1.18 has inverted motor directions... but I hadnt even gotten there yet. All is well. Thank you!

@Macgyver There appears to be an issue with running a bed mesh (G29 S1) on a tool that is using axis mapping, ie the tool that is on the U axis mapped to the X axis. Currently you'll need to have the probe on the tool that uses the XY axes directly.

Ian

@droftarts Great!

@sportdoc have you tried reducing the M201 and M203 Z settings, in case the Z motor is losing steps when the Z axis reverses direction after the probe triggers?

@aceranic

I'm loading the PID values of the Nozzle and Bed, the Bedmeshing depending on Temperature and Bed Type on Print Start automatically.
It my seem like overkill but i prefer to automate as much as possible. My meshing seems consistent and varies just with Temperature. So ican mesh with higher resolution and start my prints faster.

I'm using Orca slicer to send Bed Temperature and Print temperature to my macro called PrintSetup that is poart of my start code

Start Code

M190 S{first_layer_bed_temperature[0]-5}; M104 S[nozzle_temperature_initial_layer] ; Wait initial layer temp M109 S[nozzle_temperature_initial_layer] ; Wait for Bed Temp M98 P"/macros/PrintSetup" B[bed_temperature] H[first_layer_temperature];

This Macro loads the coresponding Mesh for the defined Bedplate, and with the temperatures it also loads the right PId tune information. You can also define Offsets if your Probe has drift wiht different Temperature.

; 0=Bambulab Square BS ; 1=Textured Round TR ; 2=Smooth Round SR var BED_Type = 0 ;define Bed plate Type var BED_T = {param.B}; var EXT_T = {param.H}; var Probe_height = 0.36 ; determined wiht G30-S1 after manually leveling wiht paper ;Pinda Bed Levelsensor M558 P5 C"^exp.e2stop" H2 F460 T9000 A3 K0 G31 P500 X0 Y-31 Z{var.Probe_height} M106 P2 S30 M703 T0 if var.BED_T < 65 M307 H0 R0.383 K0.618:0.000 D1.11 E1.35 S1.00 B0 ;BED PID 58 !! G31 Z{var.Probe_height + 0} ;Pinda - is higher, + is lower G28 ;Home G1 X0 Y0 Z5 F12000 ;move to Probe location G30 ;Probe if var.BED_Type = 0 G29 S1 P"BS60.csv" elif var.BED_Type = 1 G29 S1 P"TR60.csv" elif var.BED_Type = 2 G29 S1 P"SR60.csv" elif var.BED_T < 75 M307 H0 R0.367 K0.732:0.000 D0.98 E1.35 S1.00 B0 ;PID 70°C G31 Z{var.Probe_height + 0} ;Pinda - is higher, + is lower G28 ;Home G1 X0 Y0 Z5 F6000 ;move to Probe location G30 ;Probe if var.BED_Type = 0 G29 S1 P"BS70.csv" elif var.BED_Type = 1 G29 S1 P"TR70.csv" elif var.BED_Type = 2 G29 S1 P"SR70.csv" elif var.BED_T < 85 M307 H0 R0.367 K0.732:0.000 D0.98 E1.35 S1.00 B0 ;PID 70°C make one for 80 G31 Z{var.Probe_height + 0} ;Pinda - is higher, + is lower G28 ;Home G1 X0 Y0 Z5 F12000 ;move to Probe location G30 ;Probe if var.BED_Type = 0 G29 S1 P"BS80.csv" elif var.BED_Type = 1 G29 S1 P"TR80.csv" elif var.BED_Type = 2 G29 S1 P"SR80.csv" elif var.BED_T < 95 M307 H0 R0.333 K0.400:0.000 D0.87 E1.35 S1.00 B0 ;85°C G31 Z{var.Probe_height + 0} ;Pinda - is higher, + is lower G28 ;Home G1 X0 Y0 Z5 F12000 ;move to Probe location G30 ;Probe if var.BED_Type = 0 G29 S1 P"BS90.csv" elif var.BED_Type = 1 G29 S1 P"TR90.csv" elif var.BED_Type = 2 G29 S1 P"SR90.csv" elif var.BED_T < 105 M307 H0 R0.282 K0.306:0.000 D1.30 E1.35 S1.00 B0 ;110°C G31 Z{var.Probe_height + 0} ;Pinda - is higher, + is lower G28 ;Home G1 X0 Y0 Z5 F12000 ;move to Probe location G30 ;Probe if var.BED_Type = 0 G29 S1 P"BS100.csv" elif var.BED_Type = 1 G29 S1 P"TR100.csv" elif var.BED_Type = 2 G29 S1 P"SR100.csv" elif var.BED_T < 115 M307 H0 R0.282 K0.306:0.000 D1.30 E1.35 S1.00 B0 ;110°C G31 Z{var.Probe_height + 0.038} ;Pinda - is higher, + is lower +0.038 G28 ;Home G1 X0 Y0 Z5 F12000 ;move to Probe location G30 ;Probe if var.BED_Type = 0 G29 S1 P"BS110.csv" elif var.BED_Type = 1 G29 S1 P"TR110.csv" elif var.BED_Type = 2 G29 S1 P"SR110.csv" elif var.BED_T < 125 M307 H0 R0.282 K0.306:0.000 D1.30 E1.35 S1.00 B0 ;110°C G31 Z{var.Probe_height + 0.038} ;Pinda - is higher, + is lower +0.038 G28 ;Home G1 X0 Y0 Z5 F12000 ;move to Probe location G30 ;Probe if var.BED_Type = 0 G29 S1 P"BS120.csv" elif var.BED_Type = 1 G29 S1 P"TR120.csv" elif var.BED_Type = 2 G29 S1 P"SR120.csv" else echo "Bed Temp Setting Out of Bounds" if var.EXT_T < 195 M307 H1 R4.434 K0.887:0.000 D5.41 E1.35 S1.00 B0 V24.0 ;190°C NEW echo "Print Temp Setting: ", var.EXT_T , "°C PID @190°C loaded" if var.EXT_T < 205 M307 H1 R3.883 K0.339:0.000 D7.06 E1.35 S1.00 B0 V24.3 echo "Print Temp Setting: ", var.EXT_T , "°C PID @200°C loaded" elif var.EXT_T < 225 M307 H1 R3.899 K1.407:0.000 D6.62 E1.35 S1.00 B0 V24.3 ;200°C echo "Print Temp Setting: ", var.EXT_T , "°C PID @200°C loaded" elif var.EXT_T < 235 M307 H1 R3.990 K2.754:0.000 D6.24 E1.35 S1.00 B0 V24.1;230°C NEW echo "Print Temp Setting: ", var.EXT_T , "°C PID @230°C loaded" elif var.EXT_T < 245 M307 H1 R4.538 K2.346:0.000 D4.59 E1.35 S1.00 B0 V23.8 echo "Print Temp Setting: ", var.EXT_T , "°C PID @240°C loaded" elif var.EXT_T < 265 M307 H1 R3.978 K0.322:0.000 D5.90 E1.35 S1.00 B0 V23.9 echo "Print Temp Setting: ", var.EXT_T , "°C PID @250°C loaded" elif var.EXT_T < 285 M307 H1 R4.047 K1.118:0.000 D5.47 E1.35 S1.00 B0 V24.3 echo "Print Temp Setting: ", var.EXT_T , "°C PID @270°C loaded" elif var.EXT_T < 295 M307 H1 R4.308 K8.893:0.000 D5.01 E1.35 S1.00 B0 V24.3 echo "Print Temp Setting: ", var.EXT_T , "°C PID @280°C loaded" else echo "Print Temp Setting Out of Bounds"

Maybe you can adapt it your needs

@ash100 the reason we haven't seen this before is that or recommendation us to home in open loop mode. You can do this by using M569 with D parameter to switch to open loop mode at the start if each homing file, and back to closed loop mode at the end.

Homing in closed loop mode may be possible with the right mechanics. The reason you get the position error is probably because after the homing switch is triggered, there is a latency of a few milliseconds before the command to stop the motor is received. If you can arrange your homing switch to trigger a small distance (2mm may be enough) before the physical stop is reached, so that the motor can overshoot the homing position slightly without hitting a hard stop, that may avoid the error. If it doesn't then I will need to amend the firmware to ignore position errors immediately after the motor is commanded to stop during homing.

@tcamguil said in [3.6.0-rc.2] Z-probe hits bed and U not moving running Mesh:

;Kliky L M558 P8 C"10.io0.in" H2:0.25 F1200:120 T18000 K1 R0.0 A15 S0.005 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X42.00 Y0.00 Z-25.000 K1 ; set Z probe trigger value, offset and trigger height ... ;Kliky R M558 P8 C"11.io0,in" H2:0.25 F1200:120 T18000 K1 R0.0 A15 S0.005 ; set Z probe type to bltouch and the dive height + speeds

Do you have one Klicky probe, or two? You seem to be defining two, on different IO inputs. Or is it the same Klicky, but it depends which tool head picks it up?

You have K1 set as the probe number for both probes, so most likely only one of them is actually being configured; the second effectively overwrites the first, so when the 1st toolhead (using the CAN '10' board) picks it up, it's looking on the wrong input for the probe response. Same for G31. Send M558 K# to check what probes are defined. Use a different K number for each probe. I don't know which probe number you are using in your 'pickupprobe.g' etc macros, but you could pass a parameter to the macro based on the tool number.

As far as I'm aware, the mesh should be applied to both tools. Please post your full config.g, maybe it's a config issue.

There is an issue running mesh probing on the U axis, it has been reported before, and your third issue sounds similar to this: https://forum.duet3d.com/topic/37165/issue-with-szp-on-secondary-idex-toolhead

Ian

@Eumldeuml said in Gradual layer shifts with integrated JMC stepper servos:

If I understand correctly, this means there won't be any direct connection from STEP+ on the driver/motor to STEP+ on the EBB? But the signals will still be differential?

That's correct. Drivers most commonly have opto isolated 5V inputs, which don't require differential drive. A few have RS422-compatible differential inputs; 3V drive is sufficient for those.

@troydeming
So I got home today and did the PID autotune and it is running perfectly now. Happy Camper am I

@apak Changed heater from 30W to 70W and problem was gone....

@ash100 I suggest you get a diagnostic report on the tool board by sending M122 B75 and post the result here.

@Dutchprinting if long straight moves are jerky, this usually means that you are using mesh bed compensation and the maximum Z instantaneous speed change set in M566 or M205 is too low to permit the required reversal of Z direction to apply mesh bed compensation.

If straight moves are K but curves are not OK, this probably means that the X and/or Y instantaneous speed change allowed is too low to follow the segments that the slicer generated for the curve at the speed requested by the slicer.

If the nature of your printer and print requires the Z axis to move other than for the purpose of implementing mesh bed compensation, then I guess the Z axis M566 setting may limit the speed even without mesh bed compensation being used.

From your config.g file I see that your M566 settings for Y and Z are rather low. We normally suggest at least 600 for X and Y.

Bear in mind that the resolution of the curve in the GCode file also has an effect. If the curve is made from longer segments, the direction change will be greater at each point between segment boundaries, so the slowdown will be greater. If the GCode was sliced from an STL model then the segment length will have been set in the STL file; so if you want shorter segments then you may need to go back to the program that generated the STL file and reconfigure it to generate shorter output segments (i.e. higher resolution output).

@jay_s_uk thanks a lot

M906 X1600 Y1600 Z1200 E1200 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout