#[Solved] lane1 Current lane not loaded, LOAD TRIGGER NOT TRIGGERED

1 messages · Page 1 of 1 (latest)

rich crescent
#

For some reason sometimes it will unload beyond the load sensor, and ive recalibrated my lanes/bowden length not sure what to adjust to fix this from happening during swaps, it will sometimes work and sometimes it will throw the error

hidden girderBOT
#

<@&1304550334839918672>

steel venture
#

When you calibrated Bowden length did you hold the buffer closed?

rich crescent
steel venture
#

I would recommend trying that, cutter doesn’t impact that

knotty goblet
#

Also your tool_stn_unload could be too much, if you still have problems you can add and make afc_unload_bowden_length a little bit shorter than your afc_bowden_length. If you update afc_unload_bowden_length make sure it does not already exist in the Afc_auto_vars.cfg file

rich crescent
#

i dont remember where i got these number i feel like i remember grabbing them from a table that showed starting values for certain toolhead combos but i cant find the page

rich crescent
knotty goblet
rich crescent
#

Seems to be better after doing all of the above, seem to be having a different issue after getting that figured out, i still use kamp purge line witch idk if that is smart but seems to have under extrusion when it goes from kamp purge line to the start of the print

knotty goblet
rich crescent
#

no, seems to be struggling to extrude right at the end of travel moves from purge/poop and toolchanges

steel venture
#

You might check if kamp purge has a retract at the end of it

steel venture
#

Well there isn’t one at the beginning of your print gcode I would guess

rich crescent
#

so i figured out retraction, but now im mid way through another print with the load lane error, it unloaded on filament swap beyond the load sensor again

#

is their more info you guys need from me to understand whats going on?

#

i shouldve also specified im using a nightowl not a BT

knotty goblet
#

What's in your AFC_auto_vars.cfg file?

knotty goblet
rich crescent
#

This file is autogenerated and updated when variables are not in your normal AFC config files

[AFC_hub NightOwl_Hub]
afc_unload_bowden_length: 1300.0
afc_unload_bowden_length:1280.0

i havent saved and restarted to apply the unload bowden length

steel venture
#

Why are there 2 unload lengths there? Also what’s your load length?

rich crescent
#

i was gonna comment out the top one on restart

#

its mid print

steel venture
#

Ah, you can comment it out now without hurting anything

knotty goblet
#

You can update the unload length without restarting with SET_BOWDEN_LENGTH macro but remove the top one first and just save before running it

rich crescent
knotty goblet
#

It's case sensitive, your H in hub needs to be capitalized

#

And the O in Owl

rich crescent
knotty goblet
#

Also length can be an equal like UNLOAD_LENGTH=1280

rich crescent
#

okay ill see how that does now

#

previously it was 1350 with TN not held down during calibration and now with it held down and lowered its 1280

knotty goblet
#

When you find a number that works you need to manually update that file, I forgot we don't have a save macro for it 😑

rich crescent
#

i dont see a bowden length i only see the bowden unload length

knotty goblet
#

Bowden length is in your AFC_Turtle_1.cfg file

rich crescent
#

[AFC_hub NightOwl_Hub]
afc_bowden_length: 1300.0
move_dis: 50 # Distance to move the filament within the hub in mm.
cut: False # Hub has Cutter

aw yep does this look right?

#

besides the new number il input

knotty goblet
#

Yup

rich crescent
#

thank you very much for your help again much appreciated i will come back to here if more issues arise on the next print

#

also is their a way to search through like old threads to find people with the same issue so i can look through the thread and see what their solution was?

steel venture
#

The normal search should work

rich crescent
#

No errors yet

knotty goblet
#

@rich crescent is this now solved?

rich crescent
#

I believe so