Whenever I get to color change 6 on ANY multi color print
coming from ANY lane on the boxturtle
My AFC crashes
#[Solved] AFC Disconnects - Repeatable (CAN termination improper & Others)
odd pebble
attached a 2 color voron cube as well as cereal gcodes
this is repeatable when i get to color change #6 the AFC disconnects
keen lance
it looks like lane 4 is failing to load to the toolhead, do you know why this might be?
odd pebble
ill have to triple check the distances but lane 4 definitely is printing
or is the crash because lane 4 is not at toolhead? Because it doesnt even get to the part where it tries to load lane 4 up into the hub
in real physical world
hm...
fierce canyon
microsteps: 8 # Recommend 8 or 16. Try both to avoid Klipper 'Timer too close' error (also try adjusting num_moves)
odd pebble
i am going to re run the print but i want to validate IRL if lane 4 attempts to spit down to toolhead
the way it looks in real life is that lane 3 retracts
it gets ready to kick lane 4 down to toolhead
but nothing happens (the extruder doesnt go and AFC crash)
keen lance
does it send this to console before it error?
||=====||==>--||-----||
TRG LOAD HUB TOOL```it does that for any leg i load during print
keen lance
from the log it looks like it is failing to load before the communication is lost
odd pebble
Let me film it or similar because its swapping out just fine before it gets to that change
i did just change microsteps from 16 to 8
going to attempt to film whats happening during the print failure
then attach a log that will accompany the video
uploading video to youtube due to size
changing microsteps got me further into color changes
simply changing the microsteps seems to have made that gremlin go away
[Solved ]AFC Disconnects - Repeatable (changing microsteps 16->8 fixed)
spoke too soon
did the same thing just much later in the print now
AFC Disconnects - Repeatable
it crashed so hard the FIRMWARE_RESTART command is not working i had to restart klipper via systemctl
keen lance
is all your software up to date?
keen lance
not sure if it will make a difference but upgrading your system could help. at one point, after updating klipper and not my system i had weird unexplainable problems. after updating they system they went away
odd pebble
btw it was a different leg it failed on but same fail situation
logs say it didnt hit hub/tool
AFC never tried to actually load that lane
it was like docker
Gtk gnutls
systemd
nfs
things i didnt THINK would matter to klipper
doing a apt upgrade -y now
odd pebble
OK
I tried everything
trsync adjust
tying it to 1 cpu core
i can now make it to layer 16 before i get a fail
I can now print this high 🤣
crystal zinc
so the resolution for this thread is to get a faster pi?
odd pebble
oh
- Check your CAN terminations and then the only issue you MIGHT have is your main MCU timing out (mine is a spider 2.1? older MCU and timed out a bit) if that happens im sorry for your life try to add some waits to toolchanges to avoid buffer overflow/timeout during changes
[Solved] AFC Disconnects - Repeatable (CAN termination improper)