AFC MCU Discconect! (Solved)

[stable perch]

Hey guys i had change from USB to Can1 network, because i had MCU connection lost Over USB.
Today i had this issue as well at my print . Near finish the print the MCU turtle1 lost communication.

Here the Klippy Log its to big to load it over Discord.

https://1drv.ms/u/c/80c2af8021e7d0a2/ES-a32hcNHVGk09zzwUu-VMBxZrG4vvSVxrOok2u1A8GcA?e=gRwPkR

[acoustic marlin]

This sounds like something I’m familiar with 🥹

Try changing your max move distance to be lower. 500 or 1000mm

https://cdn.discordapp.com/attachments/1325184831105273856/1339041482920951819/Screenshot_20250211-180914.png?ex=67adefcf&is=67ac9e4f&hm=bf285a4510f957b92cfa23ff0a3bd47baed6a5f299c662530ce6f32bce3ca8c6&

[stable perch]

That means to do for me?

[stable perch]

Ahhh here i see

Its 1.200 mm

[stable perch]

Are you meaning now the bowden or the cfg?

And where to find?

[acoustic marlin]

In the AFC.cfg add “max_move_dis: 500”

[stable perch]

okay

But in which section?

[acoustic marlin]

I’m not sure if it’s working as intended right now but you can give it a go. I had a custom fix @plush edge was super nice to add in an earlier AFC release. I think he’s double checking this update is working as intended

Any section

I put it under the speed section

[stable perch]

Like this @acoustic marlin

Is it whil adding this any slower to the print or change itself?

[acoustic marlin]

Let me know if that works for you and actually breaks it up. Latest AFC update it’s not splitting for me right now

Only very small amount

But my god is it worth it

No random disconnects and ruined prints

[plush edge]

This reminded me, I am checking it now as well

[stable perch]

I give it an shot now

[plush edge]

Ok I know where I Fed up, put the same value in each AFC_stepper section in AFC_Turtle_1.cfg and this will work as I just tested it. I will fix it in the next update so that the global value will work for all steppers @acoustic marlin

[stable perch]

what are you meaning

Also extra in stepper?

@plush edge at stepper lanes

or at tmc steppers?

[plush edge]

[AFC_stepper lane1]

[stable perch]

so each stepper lane should the value

max_move_dis: 500

[plush edge]

yes for it to work correctly with the current software

[stable perch]

so for all 4 lanes

[plush edge]

yup

[stable perch]

So likje this

need i to recalibrate the afc?#

[plush edge]

no

it just breaks any moves greater that 500mm into chuncks of the value you put there

[stable perch]

okay

i had implented also at the lanes

So test pikachu are running

[acoustic marlin]

Thanks!! I’ll put that in tomorrow morning and start printing

[acoustic marlin]

Did it work?

[stable perch]

For the moment no disconnects , iam at calibration at purge but , today no disconnects at all

[acoustic marlin]

Same. I have my max length at 1000mm and it’s been good thru about 80 swaps now

[stable perch]

I am at 500 all fine

[stable perch]

yeah i will test also

[acoustic marlin]

I don't recommend 1000 mm. Having issues. Going back to 500mm

[stable perch]

Okay clear

[stable perch]

But 500 seems to be running well

[stable perch]

Hapenned again timeout

[plush edge]

can you put your klippy.log here please

[stable perch]

https://1drv.ms/u/c/80c2af8021e7d0a2/EQNqtYSNlR9NitJCwj_PXvYB0znLRGz_VCFykVLw5s6Wsw?e=NnoJeB

[stable perch]

here

Cant print with the Box Turtle

Neat the same spot as the first mcu timeout

[plush edge]

This shows up as well in your log b'Got error -1 in can read: (100)Network is down' your CAN network went down

[stable perch]

Its an second can

[plush edge]

Are you using a USB 2 CAN connector?

[stable perch]

Yes

Can1

[plush edge]

can you ssh in and type dmesg and does it show anything about a usb device disconnecting?

[stable perch]

Because had 2 can networks

nothing wierd

[plush edge]

hmmm, ok

[stable perch]

it only comes at larger prints

the whole day testing liitle prints there was no problem at all

And i dont know if i get on can 0

it burns my cartorgrapher

[stable perch]

Are can1 was going down?

So the first klippy log was also can network down?

[plush edge]

it does not show which can network went down

[stable perch]

The Turtle is the only on can1

It appears after hours

i wiggled all cables

[stable perch]

The question are why is can1 goes out after hours

[stable perch]

But now we will see i risk my cartographer now , because i am testing on Can0

I gave response of any issues on Can0 with cartographer and Turtle

[stable perch]

At the top are my first klippy log can you look pls if it was can too?

[plush edge]

You first was not because of a CAN disconnect

[stable perch]

okay

good to know

[acoustic marlin]

How many successful filament swaps did you get before crashing?

[stable perch]

i had upload my klippy second log

[acoustic marlin]

as far as I know I can't see in the log how many swaps were completed successfuly with a counter. I was just curious to compare to the max I have done successfuly before battling this same issue

[stable perch]

I am now on the risky can0 with cartographer

As far as i can see all run well

But wait till the bad spot cames

[stable perch]

First big print with 9 hours and 202 changes done @plush edge , changing to can0

[acoustic marlin]

That’s awesome! So your issue was just one of you can connections was unstable?

[stable perch]

Yeah my can1 disconnects , i only made can1 because cartographer , but it was disconnecting after some hours

So i go to the risk side and connected all to can0 what you not should do with an cartographer because it could destroy it

But in my situation all works fine on can0 with set max_move_dist to 500

It was an 9 hour print with 202 changes

[stable perch]

Dies Again At filament swap at the beginbning of an print @plush edge

https://1drv.ms/u/c/80c2af8021e7d0a2/Ea1tNcqruWdKhrKRZec8VIsB9jSFcS7h8Q2G4BXfNmXs5A?e=eKbFG8

here the new klippy log

But at the beginning at an print first filament swap

[plush edge]

you have a high amount of retransmit bytes, which I think lead to the crash. For some reason during printing your EBB36 device is always retransmitting 360 bytes which does not seem good to me

your bytes retransmit was low and then slowly started creeping bigger until it causes a TTC error

[stable perch]

Okay

the only thing thats new is spoolman

But on an seperatet pi

[plush edge]

I would not think that would cause this problem though...

[stable perch]

What do you think

The can0 network with carto?

[plush edge]

Yeah I am not really sure on this one

[stable perch]

okay i take an look

But iam wondering because Pikachu was running well

[plush edge]

Yeah that is weird, what PI version do you have?

[stable perch]

ahhhhhh i knbow it know

because ive updatet klipper

i had an rollback version

before

arrrrgghhh

need to rollback again

[acoustic marlin]

I just got an 80 swap print to work on latest klipper. 500 max distance

[stable perch]

Yeah because the new klipper had issues with carto

[acoustic marlin]

Ooooo gotcha okay

[plush edge]

cough kalico cough lol

[acoustic marlin]

Dude you live on the edge running that

[stable perch]

how was rollback the klipper @plush edge

i need to come back to this version

[stable perch]

i was testing it

i need to made the soft new

[plush edge]

you can use kiauh to roll it back

[zenith thicket]

no - you live on the edge running regular klipper

kalico guys don’t just randomly break shit

[acoustic marlin]

I don’t want to live on the edge 😄

[stable perch]

So i could stay on Kalico

[plush edge]

yes, I currently run kalico

[stable perch]

kay but i need to come back to this version

[kindred arrow]

@stable perch How is it going running your carto and BT on the same can network?

[stable perch]

For me it works, Printing over days and hours on can0 now

[kindred arrow]

Thanks. I may take the risk myself. What control board are you using? I wonder if that has anything to do with it. I have an M8P v1.1

[stable perch]

I Had an BTT E3EZ with CM4 Mounted

[zenith thicket]

can we mark this one as solved?

[stable perch]

Yes we can

AFC MCU Discconect! (Solved)

The Disconnects came , from an loosen Mellow sb2209 cable , ive change it to CNlinko Mounts