#I'm getting repeated TTC errors trying to print the torture turtle for the serial...

1 messages · Page 1 of 1 (latest)

chrome socket
#

Everything else prints fine it's the turtle in particular that is triggering it. I got to 90% on my best run, changed max_move_dis to 900, trsync to true, lowered the long moves accel, speeds settings in afc.cfg, tried disabling klipper screen, and crows nest. It just keeps doing it. I got further with all the shit enabled than I did with it disabled.

I'm running a c920 webcam on usb, beacon rev h on usb, ebb42 on can, and the BT on can. I have a rpi 4b 8gb running everything , it's always been on its own psu (the stock one that came with the pi), I get past about 70% in the torture turtle, and then it's like a crap shoot on when the TTC error is going to come.

My system loads barely peak 11% in any of them, nothing is overly hot. I had grok check my klippy.log, and it said nothing is wrong from what it can see.

I added the wipe macro to slow down the lane changes some, added m400 to the start of it.

Idk wtf is going on but I am starting to get really frustrated. I need some help....

sinful mesaBOT
#

<@&1304550334839918672>

chrome socket
#

Also my printer psu is a 350w not the 200-24 the LDO kit comes with stock so I doubt it's power fluctuations causing it.

sinful mesaBOT
chrome socket
#

Nevermind idk what I did to fix it but it finished this time... I updated klipper from the terminal, added m400 to my brush macro, cleared my old cache files, deleted old log files, as well as a few other things... I just got an alert from mobileraker that the print finished.

worn drum
#

If this pops up again: try Kalico in case you're still on mainline Klipper.

solar tree
#

Do you use a USB hub? Another thing others have seen the TTC being fixed by moving to a fresh USB card/moving to SSD/nvme drive.

chrome socket
#

I have too much shit plugged in via usb I knew this would be a problem ahead of time as well as the can u2c that’s why I went straight to the store rj11 port. I have a hd webcam, and my beacon, and obviously the main board.

#

My bad I read that wrong I’m getting ready for work… no I don’t use usb hubs on this printer everything goes right to the pi

#

I’m planning on moving to an ssd after this. I did the same thing on my other pi running home assistant that made a big difference.

It was probably my sd card bogged down. The only thing I really did different was delete all my old jobs, old printer.cfg backups, cleared my caches, and deleted any old log files. I added your m400 code to my brush.cfg too at the start. The rest of the shit was all the same as before.

chrome socket
worn drum
#

Besides that, Kalico has many features that Klipper doesn't have, and updates are much less likely to break your printer.

chrome socket
#

That's always a plus

cloud crypt