Topics created by Googliola

@dc42 I think, it's the other way round. I split z to Z and U and hide the latter (P3) by

M584 X0 Y1 Z2:3 U3 E5:6:7:8:9 P3

Or maybe the U3 is messing things up?

Sidenote: hiding axis(es?) is causing trouble elsewhere too. Can't find the post right now, but I know someone else mentioned it. Will post back ASAIK.

Glad I found this topic! Sorry for dragging up an old topic but I don't see any other information on the wiki about this.

I'm looking for variable support as well. An example of an immediate want (notice I didn't say need lol) is the ability to call a macro with hotend first layer temperature and bed temperature parameters.

My Cartesian machines all will set initial hotend temp to 160° while bed heats up, then do a mesh bed leveling and finally heating up the nozzle to print temp just outside the print area and doing a purge line before it begins the print.

Yes I know that I can put this in Slic3r custom gcode for print start, but then I have to manage it for each printer 😁 I'd love to take advantage of just putting the macro call in the custom gcode section.

@dc42 having everything that goes to the console in the log (when configured to do so) + every debug output (when similarly configured) would be the best option. At all times as well not just when printing from SD. As long as there is sufficient bandwidth to write to the SD at the same time as reading. may need a RAM buffer.

I've moved this to the DWC Wishlist section.

The X40 and Y-40 move is basically to negate the nozzle offset of the BLTouch, so that I am probing the same spot that the nozzle actually touches.

The bed move by 10 was basically done to ensure enough clearance and dive height while I was still narrowing down the dive height. It also gives a longer dive height to allow for the probe to settle. That plus the lower speeds is an attempt to give the probe the best chance of getting a repeatable measurement.

I also have a macro for manual bed leveling and then another for mesh grid measurement. I don't run these very often, but they are nice to have when you need them.

1_1538593590722_0_Grid Compensation Assist.g
0_1538593590721_0_Auto Bed Level Assist.g

And there's also this bundle for tuning:
https://forum.duet3d.com/topic/6181/tuning-macros-menus-accel-jerk-retraction-pressure-advance

@fallenhorseman Glad I could help.

Note to all guys: Yeah 4k7Ohm Pullup to 5V is resolving that issues

Funnily, I dont need a pullup between 5V and the PWM of the FAN, but I need one between GND and Z-Probe (as you can barely see in my picture 😉 . I use the 'old' version of BLTouch which is not 3.3V 'tolerant'. Am I missing something or is that a typo on your side?