error in lane locked

[blissful fox]

Hello, i got this error in random start AFC lane3 tool cmd: T2 LOCKED AND LOADED error in ToolHead. Lane identified as loaded but not identified as loaded in extruder i checked extruder and switch all are ok,

[low kelp]

Hi @blissful fox is the filament actually back behind the hub and inside the boxturtle, or is it currently loaded to the toolhead?

[blissful fox]

Hi, The Lane 1 is in toolhead at startup and lane3 send error. Of i unload /reload lane3 is ok for 3/4 power on. I do not use lane 3 between reload and error. It is just load

[low kelp]

Can you try to run

UNSET_LANE_LOADED

And then

SET_LANE_LOADED LANE=lane1

And then check

AFC_STATUS

[blissful fox]

Hello, result after error, it is only if lane is load in TH10:04 Turtle_1 Status LANE | Prep | Load | lane1 | <--> | <--> | lane2 | <--> | <--> | lane3 | <--> | <--> | lane4 | <--> | <--> | HUB: <-> Tool: <-> 10:04 AFC_STATUS 10:04 Manually set lane1 loaded to toolhead 10:04 Rotation distance reset : 4.6500 10:04 Rotation distance reset : 4.6500 10:04 Rotation distance reset : 4.6500 10:04 SET_LANE_LOADED LANE=lane1 10:04 Manually removing lane1 loaded from toolhead 10:04 UNSET_LANE_LOADED 10:04 ▶️ Initialisation terminée 10:04 E _ _ _ _ R |_|_|_|_|_| R | \____ O | \ R | |\ X | ! \_________/ |___| Turtle_1 10:04 lane4 tool cmd: T3 LOCKED AND LOADED 10:04 lane3 tool cmd: T2 LOCKED AND LOADED error in ToolHead. Lane identified as loaded but not identified as loaded in extruder 10:04 lane2 tool cmd: T1 LOCKED AND LOADED 10:04 lane1 tool cmd: T0 LOCKED AND LOADED in ToolHead 10:04 Box_Turtle Turtle_1 Prepping lanes 10:04 Waiting max 30s for moonraker to connect 10:04 AFC Version: v1.0.31-1558-07ff136

with color for STATUS:

[woeful echo]

Please run this debugging script when not printing and post the resulting link in chat.

[harsh junco]

are you manually removeing filament from the toolhead?

[blissful fox]

no, i let last used lane load

[harsh junco]

ok and doing this #1433132238194868255 message adjust lanes as needed
did not fix it?

[blissful fox]

i post result this morning, no change, just restart now after save_config then same error (lane 1 load print with it 1h ago)

for debug script result: https://termbin.com/k3fi

btw i add an alias for use personnal macro "BT_INIT" it is working like "Box_Turtle Turtle_1 Prepping lanes" at startup, i use BT_INIT in my start_print for verify no error with lanes. But problem is still present with lane3.

If i unload and reload lane3 no more error, until next restart

[harsh junco]

lane 1 is loaded too the toolhead as indicated?

[blissful fox]

yes

[harsh junco]

ok lets try this.
UNSET_LANE_LOADED
SET_LANE_LOADED LANE=lane3
Unset_lane_loaded
SET_LANE_LOADED LANE=lane1

[blissful fox]

first command say lane 1 🙁 15:59 Manually removing lane1 loaded from toolhead 15:59 UNSET_LANE_LOADED 15:58 ▶️ Initialisation terminée 15:58 E _ _ _ _ R |_|_|_|_|_| R | \____ O | \ R | |\ X | ! \_________/ |___| Turtle_1 15:58 lane4 tool cmd: T3 LOCKED AND LOADED 15:58 lane3 tool cmd: T2 LOCKED AND LOADED error in ToolHead. Lane identified as loaded but not identified as loaded in extruder 15:58 lane2 tool cmd: T1 LOCKED AND LOADED 15:58 lane1 tool cmd: T0 LOCKED AND LOADED in ToolHead

[harsh junco]

yeah that was expected

[harsh junco]

ok now what does prep give you

[harsh junco]

all good then

for some reason it had lane 3 still being loaded, possibly an e-stop during an unload or a prvious manual removal of the lane

[blissful fox]

i remove 'manually' from TH with tool_unload and unload lane with BT_LANE_EJECT

[harsh junco]

BT_tool_unload macro should be in your GUI of choice and is the appropriate unload command for AFC to get a lane out of the toolhead

[blissful fox]

yes i use it, just ommit BT as prefix

[blissful fox]

but in usual i use normal action by unload/load the good lane in slicer. That do not explain the problem

[pseudo glen]

what do you mean by this? You use TOOL_LOAD/TOOL_UNLOAD in your slicer?

[blissful fox]

i never unload lane after print, i use the slicer for load/unload the good lane, spool 1 = lane 1 etc

if i print ASA CF and had lane 1 load, that will unload by AFC macro

manually i just unload lane preload (in extruder,, not TH) for change spool by BT_LANE_EJECT

[pseudo glen]

Ok yeah that's fine, but like mc-red said earlier if you have errors with external macros when loading/unloading like Afc_park/cut/etc that can cause this error that you originally ran into

[blissful fox]

i use only AFC macro, i just adapt BT_PREP in personal macro BT_INIT for add somes M117/118 for debugging, and it is use in print_start only, not at startup

it is not best macro but i like check where i am...

[pseudo glen]

that should be fine and should not cause the original error

[blissful fox]

yes, i checked hardware with state of microswitch, the extruder screw and crimp + definition, i am ok (i work with AFC lite in usb)

if i let lane 2 load it is the same error only the lane 3

[harsh junco]

sounds like you have something wrong

[blissful fox]

yes, i though it was lane 3 pre-load longer than normal, and going to load switch, but it is not that....

[harsh junco]

This isn't the recomended way of commanding tool changes in print macros
BT_CHANGE_TOOL LANE={LANE}

[blissful fox]

if tool change is command by slicer, it is calling AFC macro so, BT_CHANGE_TOOL LANE={LANE} or i use shortcut on mainsail

BT_LANE_EJECT is used only if spool is preload in extruder

[harsh junco]

slicer noramlly calls T(x) commands as is listed in startup docs

the command you are using hard locks lanes to a tool

[blissful fox]

ohh ok, so what is the better solution...reset lane at end of print ? unload every time (more filament loose) ?