#Spoolman not calculating/updating correctly.

1 messages · Page 1 of 1 (latest)

frozen mango
#

If gone thru the trouble shooting and in my logs i see this 2025-11-23 05:30:46,472 [spoolman.py:set_active_spool()] - Setting active spool to: 3 2025-11-23 05:30:52,559 [klippy_apis.py:start_print()] - Requesting Job Start, filename = pojemnik-na-krzemionke-tyl-ace-pro-4_ABS_1h45m.gcode 2025-11-23 05:30:52,645 [job_state.py:_send_job_event()] - Job Started: pojemnik-na-krzemionke-tyl-ace-pro-4_ABS_1h45m.gcode 2025-11-23 05:30:57,572 [authorization.py:_check_trusted_connection()] - Trusted Connection Detected, IP: 127.0.0.1 2025-11-23 05:33:15,885 [websockets.py:on_close()] - Websocket Closed: ID: 548553222608 Close Code: 1001, Close Reason: None, Pong Time Elapsed: 170847.45 2025-11-23 05:34:09,546 [spoolman.py:set_active_spool()] - Setting active spool to: None

I set active spool when print starts but it then sets it to None and i think that's why its not calculating.

tepid graniteBOT
#

<@&1304550334839918672>

tight yoke
#

Have you been setting your spoolid per lane in AFC?

frozen mango
#

i set them and it seems there now set back to Null...

#

is there a specific way to set them so they stay

tight yoke
#

You need to always set them when loading a new spool into your BT

frozen mango
#

so after i eject as an example?

tight yoke
#

ejecting a spool will cause the spoolid to be cleared

frozen mango
#

ahhh ok

#

yea been ejecting to tweak things under it then reloading so its been clearing them 😐

tight yoke
#

Do you have the AFC panel in mainsail/fluidd? This would help you see that an ID is not set

frozen mango
#

i use the mainline version for now im waiting for official release to use it

#

k now i know to redo the spool assignments after making changes to BT

tight yoke
#

you could always update to the one thats in #afc-squad, then update mainsail once its officially released

frozen mango
#

i wonder if that should be added to the troubleshooting page