Self sourced 2.4 R2. My first 3D printer ever

[lotech]

[gcode_macro _M401] ;needed a space here.
Got my M401 example from here: https://euclidprobe.github.io/06_klipper3.html

So here's what my M401 g-code probe attach looks like now:

#macro deploy klicky probe
[gcode_macro M401]
gcode:
G90
{action_respond_info("Entering M401")}
error_if_probe_deployed ; check to make sure that the probe is not already attached
_M401

[gcode_macro error_if_probe_deployed]
gcode:
QUERY_PROBE ; check probe status
do_error_if_probe_deployed ; logic check to verify probe is not already deployed

[gcode_macro do_error_if_probe_deployed]
gcode:
{% if not printer.probe.last_query %}
{action_raise_error("klicky Probe is already deployed - Remove and Return it to the dock")}
{% endif %}

#Macro to Deploy Bed Probe
[gcode_macro _M401] ;needed a space here before the _M401
gcode:
G90 ; use absolute coordinates
{% if printer.probe.last_query %}
G0 Z20 F3000 ; raise up to safe height
G0 X81 Y300 ; stop in front of dock
G0 X81 Y333 ; stop above dock
G0 Z15 F3000 ; lower onto the klicky to attach
G0 Y300 ; pull it from the dock
G0 Z20 F500 ; move up to elevation of Z20
{% endif %}
error_if_probe_not_deployed
{action_respond_info("Exiting M401")}

[gcode_macro error_if_probe_not_deployed]
gcode:
QUERY_PROBE
do_error_if_probe_not_deployed

[gcode_macro do_error_if_probe_not_deployed]
gcode:
{% if printer.probe.last_query %}
{action_raise_error("klicky Probe failed to deploy!")}
{% endif %}

And it seems to work. Comes in a little low, moving to the center of the bed after probing the z-pin.
A little higher would make it more comfortable.

 

[lotech]

So stuck that and the M402 in the macro department of the printer.cfg and they are working fine.
# Macro to retract Bed Probe
[gcode_macro M402]
gcode:
G90
{action_respond_info("Entering M402")}
error_if_probe_not_deployed
_M402

# Macro to Stow Bed Leveling Probe
[gcode_macro _M402]
gcode:
G90
{% if not printer.probe.last_query %} ; the logic on this needs function check
G0 Z20 F2400 ; set approach elevation of Z15 for fixed gantry system to clear probe over bed
G0 X175 Y175 F3000 ; start movements at center of the bed
G0 X81 Y300 Z15 ; move to position in front of dock
G0 X81 Y333 F240 ; put it in the basket
G0 X40 F240 F3000 ; quick swipe right off onto the dock
G0 Z20 F500 ; move up to elevation of Z20
M400 ; wait for moves to finish
G4 P250 ; forced pause here so motion is definite 90 travel to swipe
G0 X175 Y0 ; move to front center of bed
{% endif %} ; exit the if-then loop. was missing in previous versions
error_if_probe_deployed ; verify that the probe is detached. is corrected error
{action_respond_info("Exiting M402")}
It doesn't drop the probe off real well but I can easily fix that.
Main problem is still getting kicked off by wifi.
having a hard time figuring out how to access the pi with the ethernet cable.
thernet adapter Ethernet:

Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 169.254.97.99
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

Wireless LAN adapter Local Area Connection* 8:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Wireless LAN adapter Local Area Connection* 10:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 192.168.88.19
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.88.1

And the ifconfig on the pi:
pi@raspberrypi:~ $ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether b8:27:eb:35:62:17 txqueuelen 1000 (Ethernet)
RX packets 97 bytes 18285 (17.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 292 bytes 53576 (52.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 1657 bytes 900345 (879.2 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1657 bytes 900345 (879.2 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.88.15 netmask 255.255.255.0 broadcast 192.168.88.255
inet6 fe80::9ba8:5b3:57b7:7039 prefixlen 64 scopeid 0x20<link>
ether b8:27:eb:60:37:42 txqueuelen 1000 (Ethernet)
RX packets 4444 bytes 698095 (681.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3012 bytes 1369155 (1.3 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
This is with the cable attached.
Not sure what it all means. Not learning fast enough, ha.

 

[lotech]

I read this:

https://medium.com/@jrcharney/connect-your-raspberry-pi-to-your-computer-via-ethernet-4564e1e68922

And watched this:

Seems to connect better. I still have to hit try again occasionally but it's connecting better.
Still not sure it's using the ethernet cable but last time I played with it, it was connecting better.

Of course this line wasn't swiping right:
G0 X40 F240 F3000 ; quick swipe right off onto the dock. Changed X40 to X120 because,... absolute.
And I got rid of the F240.
calibrate_z is dropping off the probe now.

So next is clean the rails and regrease them. Retighten the necessary bolts.

Then bed mesh and work on print start macros right?