#filament not going back into extruder sensor [SOLVED]

1 messages · Page 1 of 1 (latest)

north vector
#

so everytime my filament loads back it goes past the filament extruder sensor in the box turtle i think its cause i dont got a macro for unloading filament properly anyone got a good macro i can use for unloading filament?

#

<@&1304550334839918672>

quartz radish
#

If its doing it on every unload on every lane you can try decreasing stn_unload, esp if its retracting the filament well past the tool head before the fast move.

north vector
#

no funny enough

#

only on lane 2

#

and its annoying when trying to print a diffrent colored perry the platapus

#

xD

#

and this issue first appeared after installing the tn-pro

quartz radish
#

Does lane 2 have a differen length for its bowden to hub length?

north vector
#

no

#

i made sure to cut them all the same length

quartz radish
#

In config, not the actual tube.

north vector
#

oh yes

#

lane 2 and 3 are identical value

#

but what i have noticed is after installing the tn-pro my toolhead dosent unload filament in 1 stroke anymore

#

it gotta run 2 times the command to get it past the filament sensor

#

wich wasnt there before i installed the tn pro

quartz radish
#

You might just need to run through calibration again.

north vector
#

i done that 8 times

#

xD

quartz radish
#

With the TN Pro?

north vector
#

mhm

#

5 times yestoday

#

and 3 times today

#

same with lanes

quartz radish
#

Are you using a tool sensor?

north vector
#

im useing a orbiter filament sensor

#

specificly the v2 of the orbiter filament sensor by ldo

quartz radish
#

I would try decreasing the bowden length a bit, esp if you look underneath and the other 3 lanes are well outside the hub between the hub and extruder.

north vector
#

il look into decreasing the bowden ik mine is unusually long but im also still working on a mercury one-1 mount cause it has no tophat i could put it on so it standing beside the printer

#

i also still need to enclosure it

#

so i can start printing abs on it rn all pieces on it was made on my prusa

#

and yea no just redid all calibrations

#

and lane 2 still did it again

quartz radish
#

I dont mean physically decrease the length.

north vector
#

ah u mean the value in the program

#

il try

#

but i didnt change the length yet

quartz radish
north vector
#

just redid valibration

quartz radish
#

In Your AFC_Turtle_1.cfg under the hub section, try decreasing it by like 20.

north vector
#

just tried

#

so far first load went well

#

we will see how the print goes

#

tho can take a few hours lol

#

so il msg once its done

north vector
#

welp the issue of the filament lever is working now a new issue popped up

#

lane2 FAILED TO LOAD TO TOOL, CHECK FILAMENT PATH
||=====||====||==>--||
TRG LOAD HUB TOOL

#

il get the full log

#

and i allready tried the max 500 config

quartz radish
#

Were you watching when this happened?

#

It should do a long move then a number of short moves to try to hit the tool sensor, I cant imagine decreasing by 20 would cause it to not make it unless its doing a lot of short moves already to hit the sensor.

north vector
#

yes it tries to load into the hub

#

then it cashs

#

aka it times out

quartz radish
#

Into the hub??

north vector
#

mhm

#

it crashs before it even reachs the tn-pro

#

this time

#

cause when i reboot the firmware

#

it reports it went into the hub

#

but not into the toolhead or buffer

quartz radish
#

OK I didnt read down to the bottom of you log as there was no mention of a crash before. You're getting TTC errors.

north vector
#

ttc?

quartz radish
#

Timer Too Close

north vector
#

well can i adjust that

quartz radish
#

What host is in the printer?

north vector
#

raspberry pi 3b+

#

and its running mainsail

#

standart klipper awell

#

for the box turtle afc_lite and klipper

#

idk what u mean specificly for host but if its just the board and the software on it

#

its above

#

as for the mainboard for the printer thats a skr mini e3v3

quartz radish
#

The Pi is what I was curious about.

north vector
#

well its a raspberry pi3b+

#

normale no biqu or anything

#

i just read up on others having the issues so i just enabled trsync to see if that helps

quartz radish
#

Was just trying to get some links together for you for that.

#

I believe for it to accept the max move distance you have to set the value under each extruder

#

Just noticed that in your config as well

north vector
#

acually no

#

max distance for me is in the top

#

not under each one

quartz radish
#

That may have changed in a recent update so disregard me on that then.

north vector
#

fair

#

and yea no

#

updating the trsync didnt work

#

22.29
MCU 'Turtle_1' shutdown: Timer too close
22.29
MCU 'Turtle_1' 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
22.29
MCU 'Turtle_1' shutdown: Timer too close
22.29
MCU 'Turtle_1' 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
22.29
MCU 'Turtle_1' shutdown: Timer too close
22.29
MCU 'Turtle_1' 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
22.29
PAUSING
22.29
lane4 FAILED TO LOAD TO TOOL, CHECK FILAMENT PATH
22.29
lane4 FAILED TO LOAD TO TOOL, CHECK FILAMENT PATH
||=====||====||==>--||
TRG LOAD HUB TOOL

quartz radish
#

How is your Pi getting power, out of curiosity?

north vector
#

externally

#

from a raspberry pi power brick

quartz radish
#

Ok.

north vector
#

havent gotten so far as to use a buck converter yet

quartz radish
#

There was another instance of a user with a 3b+ and running on buck they were having similar issues, I would stay with the wall adapter.

#

If you increase your bowden length back will it load without a TTC?

north vector
#

i can try

#

ok its reverted gonna try starting the print again

#

so far so good but i also added max_move_dis: 500 under ever lane

#

instead of at the start and that did change how the lane were loaded

#

maybe this will work

#

im gonna let it try printing and msg if something happends

quartz radish
#

Sorry for confusion on that.

north vector
#

its fine and no im not on dev branch

#

i just tried to add that manually

north vector
#

well the print aint done but so far

#

no issues

#

the filament in loading back fine and after changing the max move dis

#

on all 4 extruders

#

it seems it useing less processing power per command

#

but so far its only used 2 lanes il wait til all 4 colors has run

#

also

#

wrong chat to put that in

#

meant to say its still running without a problem

north vector
#

after adjusting the max move distance value and setting it back there hasnt been further problems

#

so this is solved

#

filament not going back into extruder sensor [SOLVED]

grand sluice
north vector
#

Acually i late changed it to 450

#

Cause of my max bowden distance

grand sluice
#

i think i'll reduce my bowden distance as much as I can

#

I have it pretty long

#

and maybe change the max_move_dis to be shorter like you have done

#

getting timer too close issues

north vector
#

Same here im running a mercury one.1 so im running it from the bottom to top

#

So pretty long path from box turtle to extruder

#

My suggestion is to yes to max move distance 500 cause then it will take a break between moves

#

Giving u less time out error

#

@grand sluice

#

Tho if u got any troubles refer to the docs or start a threat and ask the helping turtles

grand sluice
#

/s