[SOLVED] AFC with GooseBeltPurge (GBP) not passing purge lengths

[thorny widget]

Been attempting to integrate GBP with AFC. The directions call for updating AFC.cfg to point to goose_belt.cfg, which contains the purge macro and the slicer Machine G-Code to T[next_extruder] LENGTH=[flush_length]. Via console, goose_purge length=150 will purge as expected, however when either printing or calling for example T0 length=150, the length value is not parsing , result in no purge. Not sure if this the way AFC is coded for Purge_length or the goose_belt.cfg macros causing the lack of purging.

https://termbin.com/s94o

To summarise - with GBP purging works via the GUI and console, but not when called through the AFC integration.
Any suggestion / advise gratefully received <@&1304550334839918672>

[delicate dune]

To chime in, I've been helping Grizzle out and it seems that the parameters just aren't being passed to the poop macro from AFC. I've asked them to create a wrapper macro that prints out the exact macro being called by the poop_cmd, including any parameters, then call that wrapper as the poop macro in AFC.cfg.

 gcode:
 M118 GOOSE_PURGE {rawparams}
 GOOSE_PURGE {rawparams}```
The result is that only `GOOSE_PURGE` shows up in the console, not the length parameter.

[slate saffron]

I have not changed my line Purge yet. I use this to draw a line on my bed it's called adaptive line Purge kind of like how camp used to do

This is the best I can do to really help you at the moment till I get caught up

I haven't attempted a print yet with mine however this is me issuing a tool change command from mainsail using the AFC stuff

[delicate merlin]

I think AFC is looking for PURGE_LENGTH in the change filament gcode

[delicate dune]

@thorny widget, can you change line 167 in goose_belt.cfg from params.LENGTH to params.PURGE_LENGTH, then run a command T0 PURGE_LENGTH=100?

[delicate dune]

@thorny widget I think @delicate merlin is onto the root of the issue here. The only parameter that seems to be passed to the macro is PURGE_LENGTH. It doesn't seem to pass just any parameter name. I have done some testing with the names that match your config, and have been able to reproduce the issue. Renaming the parameter in the goose_belt.cfg file should work for you, then you'll just need to change your slicer config back to use the PURGE_LENGTH parameter name. I'll work with Graylag to update the GBP macro to be AFC compatible.

[thorny widget]

That assumption alligns with making the changes to line 167, it will now purge

[delicate dune]

I have suggested to Graylag to make the name change in the GBP macro. Looks like you're off and running now. BTW, the reason I didn't run into this is because I made this change in my GBP macro because I didn't want to mess with changing my slicer. I never thought that AFC was only passing in that specific parameter name.

<@&1304550334839918672>, I have a suggestion that the documentation should be updated to describe that the only parameter passed to the poop macro is PURGE_LENGTH and that any custom macro that is used in place of the AFC_POOP macro should conform to that naming.

[pure cedar]

If you hit the orange turtle at the bottom on the documentation page to be updated it will take you to add a GitHub suggestion. doing it this way tracks which page to update

[delicate dune]

Will do. thanks for the tip. I knew there was a better way of going about this.