#[Solved] Error "MCU 'QSTURTLE' shutdown: Timer too close"

1 messages · Page 1 of 1 (latest)

rough mesa
#

First time trying to get the boxturtle to load to the toolhead it throws this error.

lane1 filament failed to trigger pre extruder gear toolhead sensor, CHECK FILAMENT PATH
||=====||====||==>--||
TRG   LOAD   HUB   TOOL
To resolve set lane loaded with `SET_LANE_LOADED LANE=lane1` macro.
Manually move filament with LANE_MOVE macro for lane1 until filament is right before toolhead extruder gears,
 then load into extruder gears with extrude button in your gui of choice until the color fully changes
AFC debug: setting error state True
MCU 'QSTURTLE' shutdown: Timer too close
This often indicates the host computer is overloaded. Check
for other processes consuming excessive CPU time, high swap
usage, disk errors, overheating, unstable voltage, or
similar system problems on the host computer.
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown
~~~
frail idolBOT
#

<@&1304550334839918672>

rough mesa
#

Running the BTTpi 2 and the octopuss board

tall plank
#

I couldn't find anything of interest in the logs.

rough mesa
#

yeah I just dont know why but every time it gets past the hub it just instantly shuts down

tall plank
#

You could try reducing the fast move speed.

#

Usually timer too close indicates that the host computer is overloaded. I'm not sure if the BTT Pi2 is one of the hosts that is too underpowered.

rough mesa
#

I dont know what the recommended specs are

tall plank
#

I can't tell you what minimum specs are, but a Raspberry Pi 4 is fast enough. Just as a data point for comparison.

rough mesa
#

It runs at the same frquency as the pi 4 its basically equivalent to a 2 gig ram model of a pi 4

#

what should I lower the speeds to

tall plank
#

But the Pi4 has a significantly faster and more modern CPU. Frequency is not everything.

tall plank
# rough mesa

Try 50 just to test if this makes a difference. Can still go up if that works.

#

I'm not even sure if that helps. The errors often are trial-and-error.

rough mesa
#

also do I have to enable these every time?

image.png
tall plank
#

So don't bother 😄

rough mesa
#

dropping all to 50 now

#

I have also removed Obico just in case too

#

not running a webcam

tall plank
#

So it happened again with speeds down to 50, right?

rough mesa
#

yep

#

do I have to set a bowden length after the hub at all maybe?

#

cause it looks like an error after it exits the hub

#

Trying the error message recomendation right now to pull it down to the extruder

#

ok manually moved it to the extruder gears fine

#

trying a tool change

#

what do I need to change this too

image.png
tall plank
#

Lemme me check. Should be somewhere in the docs

#

Did you run lane and bowden length calibration yet?

rough mesa
#

no

#

my brain skipped over that for some reason

tall plank
#

Then you know what you've got to do 😄

#

Get it all to work reliably. Once that's done, then try upping the speeds until you get the "timer too close again".

rough mesa
#

I just saw oo load filament

tall plank
#

At that point you can still consider upgrading your host. But for now get it to work.

rough mesa
#

how do I manually set the tool to unloaded

tall plank
#

You mean you have it loaded and want to unload it now?

#

BT_TOOL_UNLOAD

#

Or you have it unloaded, but AFC still believes it's loaded?

#

UNSET_LANE_LOADED

rough mesa
#

i got it it was the second one

#

going through the lane and bowden length calibrations now

tall plank
rough mesa
#

where does it save the claibration results

tall plank
rough mesa
#

ok I finished the all lanes and bowden length calibrations am I good to try again?

#

Also do you iknow how I set what filament is where? it defaulats to 235 rightnow

tall plank
rough mesa
#

do I send it trying to load again?

tall plank
rough mesa
#

It worked then the brush command wiped after pooping and didnt lift the nozzle crashing into my bed oof

tall plank
#

That's good. The first part... not the second.

#

I don't use pooping/kicking myself, so i'm not really sure what happened here.
If you can't figure it out yourself (maybe go over the configuration options for pooping, kicking and brushing), then ping teachingturtles again.

rough mesa
#

how do I trun it off

#

turn

midnight tulip
#

variable_z_move is how high to raise the tool after AFC_BRUSH is called to avoid crashing into the bed

#

Assuming your brush is at Z0, you want to raise this to like 5

tidal roost
#

Or in your AFC.cfg you can set each of the major macros to False to not do them at all

rough mesa
#

when running the command it doesnt move to the start location

#

and im guessing its not supposted to be -1 on the z

midnight tulip
#

-1 on the Z means no Z move

tidal roost
#

I'm pretty sure that does not mean that for kick

#

are you kicking in the bed?

midnight tulip
#

Unless I'm crazy, -1 on Z on any of them means don't do a Z move

rough mesa
#

I click the AFC KICK macro and it plunges it from Z10 to Z-1 without going to the start point

#

just plunges into my bed

midnight tulip
#

Ah yeah, hold on

# 
description: Kick macro configuration variables
gcode: # Leave empty

variable_kick_start_loc           : 55, 345, 5  # Location to move before kick
variable_kick_z                   : .5       # Height to drop to for kick move
variable_kick_speed               : 150       # Speed of kick movement
variable_kick_accel               : 0         # Accel of kick moves. This will overwrite the global accel for this macro. Set to 0 to use global accel
variable_kick_direction           : "left"   # Direction to make the kick move (left, right, front, back)
variable_kick_move_dist           : 25        # How far to move to kick poop off
variable_z_after_kick             : 10        # Height of z after kick move```
#

Here's what I'm using as my kick vars

#

The -1 in your start location is telling it to actually go to -1

#

And because you have a Z limit allowed to go below 0 it's doing that

tidal roost
#

yeah there is no Z disable on kick I think

rough mesa
#

you can see the gash

midnight tulip
#

Yeah, set your Z start point to 5, and the kick_z to .5

#

What I just posted is the kick variables I've been using for months succesffuly

#

I'm kicking with the side of the SB housing off to the left

rough mesa
#

trying again

midnight tulip
#

Do not kick with the nozzle if you can help it, poops can stick to a hot nozzle

rough mesa
#

does the kick command run wihle printing or only on toolchanges while not printing

tidal roost
#

only on toolchanges unless you call it

midnight tulip
#

Whenever a toolchange occurs when it's enabled, or if you call it separately

rough mesa
#

so during a print it will go back and drop to the build plate and poop/kick

midnight tulip
#

Correct

rough mesa
#

ok I tried 0.5 and it scraped my buld plate a little but moved correctly

midnight tulip
#

thonk something is funky with your machine then

rough mesa
#

I just installed btt's eddy duo

#

maybe my z offset is off

#

idk

tidal roost
#

if you haven't printed with it yet then I would guess thats it

midnight tulip
#

Z 0.5 should not be touching your build plate

#

That's literally saying that your nozzle should be 0.5mm above it

rough mesa
#

let me recalibrate the eddy

#

OOOOO i have a z offest saved from when I had tap and the eddy doenst require one

midnight tulip
#

There ya go

rough mesa
#

I just delete the lines from the SAVE_CONFIG in printer.cfg right

midnight tulip
#

Yep

rough mesa
#

ok sweet

#

trying

#

got It!

#

I think I just have to make sure the cutter works now

#

How far from the hex nut should the depressor screw be?

tidal roost
#

whatever works for your printer, so long as you can get to full depression of the cutter its out far enough

rough mesa
#

got it sweet trying a tool change

#

do I have to do the bowden length claibration with each lane?

#

i got the timer too close error when it got to load T2

#

Ok so it loads lane one fine but when changing to lane 2 as soon as it starts to go past the hub it throws the error so i am assuming I need to do the bowden length calibration for each lane not just the lane claibration

tidal roost
#

what host are you running?

rough mesa
#

BTT pi 2

tidal roost
#

😬 that might be the issue with TTC. do you have klipper screen or USB cam?

rough mesa
#

just klipper screen

#

crowsnest is installed but I don't have a camera installed

tidal roost
#

you might be able to turn it fully off and see an improvement but idk how

rough mesa
#

so basically I need a pi 4 or 5 with more than 2 gb of ram

tidal roost
#

something about the BTT SBC seems to be borderline, but maybe I am wrong about the pi 2 version, I know the CB1 based version is overloaded

rough mesa
#

here are the differences

#

they are both quad core arm chips (pi4 and btt pi2)

#

and the btt is clocked a little higher so I don't know

tidal roost
#

I'll let someone else jump in, do you have the latest kernel version for it? Raspbian 12 based?

rough mesa
tidal roost
#

yeah bookworm

rough mesa
#

let me try one more time

tidal roost
#

ill let someone more knowledgeable on this chime in

rough mesa
#

Here are the most recent logs

#

Like I said lane 1 loads perfectly fine now but now 2 -4 don't

#

And the cut,wipe,kick macros work perfectly

#

<@&1304550334839918672>

rough mesa
#

ok unloaded all other filament except for T1 and it loaded

#

trying a toolchange maybe it is not pulling the filament out of the hub enough?

#

ok filament loaded into T2

tidal roost
#

Iirc there is a max move length variable that can be defined that might help

rough mesa
#

Ok so from T1-T2 works

#

I am using this part would that change anything?

#

Going to try a toolchange form T2 to T0

#

Just also realized i didn't have the fan for the AFC-Lite Plugged in during my first tests \

#

T2-T0 worked

#

Trying T0-T3

#

So I don''t know why but the only thing I changed was plugging in the little fan on the boxturtle and everything works

#

my confusion is immense

#

maybe it messes with the buck converter so that main chip was getting to little or to much power?

image.png
#

IDK

#

but going to set up my slicer and try a test print now

tidal roost
#

No idea, may have just been a fluke, and no that alternate hub shouldn’t impact a TTC

rough mesa
tidal roost
#

No, did you follow the initial startup?

rough mesa
#

sorry my print start macro

tidal roost
#

Oh yeah I seems to have the necessary bits

rough mesa
#

Move exceeds maximum extrusion (17.817mm^2 vs 0.640mm^2)

#

got this error on the first poop

#

welp i missed adding the M83 command to put the extruder into relative mode

tidal roost
#

you need to add max_extrude_cross_section:50 to your extruder section

rough mesa
#

oh did i miss where it siad to add that?

tidal roost
#

it may be expected it already be there since voron docs expect you to do a 100mm extrude for calibration

rough mesa
#

thanks for all the help trying the print again rn

rough mesa
#

man......

#

guess I just have to disable afc till I get a pi and a 5v power supply

#

cause using the happy hare software wouldnt be any better right?

#

Here is all my config files. I'm benching the boxturtle until someone figures this out as multiple people are having this same issue. or until I can by a stronger raspberry pi but it seems like a software optimization issue since multiple people seem to be having the same issue in various stages.

📎 config-20250428-195047.zip
#

If anyone knows some other steps to fis this let me know im still willing to try stuff too

tidal roost
#

or in AFC,cfg add max_move_dis: 500

rough mesa
#

trying

#

bumped down to 50 for all

#

uncommented

#

Uninstalled crowsnest

image.png
#

Loaded T0 fine starting the print again

rough mesa
#

One sucessful toolchange

#

Move out of range on the brush command fixed trying to print again

PXL_20250429_023902360.jpg
rough mesa
#

had another error but I gtg to bed will update tommorow

rough mesa
#

ok the issue im having now is the lane 3 and four resppolers dont seem to be rotating fast enough so its being really loose and almost falling off the spool

rough mesa
#

ok uping the speeds to default fixed it

#

two successfull toolchanges sos far

#

It's working!!!!

#

i dont know why orca made the purge tower sos large but hey its actually switching

#

[Solved] Error "MCU 'QSTURTLE' shutdown: Timer too close"

#

and I have all the speeds set to normal

#

looks like uninstalling crowsnest and obico did it

#

good thing i still have my BTT pi 1 I can use for streaming the webcam now

#

Huge thanks to @tall plank @midnight tulip @tidal roost for all the help with my issue! can't wait to get my serial hopefully and get some more prints underway!

rough mesa
#

welp got 3/4 of the way then got a nozzle clog