Filements in RepRapFirmware, fw or doc issue?

Megamannen

Hi,

https://docs.duet3d.com/User_manual/Reference/Gcodes#m701-load-filament

Why is this command running the configure.g-script?
Is this a bug in firmware or a bug in documentation?

When called the firmware does the following:

Run the macro file "load.g" in the subdirectory of the given material (e.g. /filaments/PLA/load.g)
Change the filament name of the associated tool, so it can be reported back to Duet Web Control

I was planning on having M701 PLA more as an state.
And in my start g-code have a M703 to activate heaters

gloomyandy

@megamannen See https://docs.duet3d.com/en/User_manual/Reference/DWC_filaments for a more complete discussion of the filament handling process.

Megamannen

@gloomyandy yeah, and that also states that you should do a 703 to load specific config for the loaded filament.

Now that is done automatically. Which doesn't match the documented behaviour

Phaedrux

@megamannen said in Filements in RepRapFirmware, fw or doc issue?:

Why is this command running the configure.g-script?

What exactly do you mean by this?

What firmware version are you using?

Megamannen

@Phaedrux
According to documentation M701 runs "filamanets/PLA/load.g" and you should run M703 to run "filamanets/PLA/config.g"

But when I load PLA it runs both filamanets/PLA/load.g and filamanets/PLA/config.g
(now I get unsure if it's the web-gui that does a M701 + M703 on filament change or if it's the M701 that does this undocumented behaviour)

fcwilt

@megamannen

If you load a filament from the DWC it first runs load.g for that filament and then runs config.g for that filament.

Frederick

Tinchus

I have just found this post after posting my own. Im having the same issue on 3.4 stable.

Docementation says for loading a filament, load.g will be executed but for executing the config.g I have to call for it using M703. But that is not happening: after load.g, the config.fg file is executed automatically.

Is this a bug or a new behaviour not documented?

Phaedrux

DWC runs both and always has. It's different than running M701 by itself.

OwenD

@megamannen said in Filements in RepRapFirmware, fw or doc issue?:

(now I get unsure if it's the web-gui that does a M701 + M703 on filament change or if it's the M701 that does this undocumented behaviour)

DWC issues all the commands necessary to complete the task at once.
My comments in this thread also apply here