Unexpected startup behavior.

fcwilt

Hi,

I am using firmware 3.4.6.

If I had a filament type loaded in the DWC when I shut down the printer it seems that state is saved somewhere and restored when starting up again.

However it doesn't seem to be executing the load.g/config.g files for that filament, that would be executed when selecting the filament within the DWC.

So the settings made in the config.g file are not being applies and things are out of sync.

Is there a way in my startup code to execute the config.g file for the selected filament type, so things end up by in sync?

Thanks.

Frederick

omtek

See M703:

https://docs.duet3d.com/User_manual/Reference/Gcodes#m703-configure-filament

"After assigning a filament to a tool, this command may be used to run /filaments/<filament name>/config.g to set parameters like temperatures, extrusion factor, retract distance. If no filament is loaded, the code completes without a warning."

fcwilt

@omtek said in Unexpected startup behavior.:

See M703:

https://docs.duet3d.com/User_manual/Reference/Gcodes#m703-configure-filament

"After assigning a filament to a tool, this command may be used to run /filaments/<filament name>/config.g to set parameters like temperatures, extrusion factor, retract distance. If no filament is loaded, the code completes without a warning."

Thanks for the feedback.

How do I determine what the name is? I can see it on the screen but I need a way, in code, to do it for whatever the current name is.

Frederick

droftarts

@fcwilt I'm not sure how the filament name is being saved; I admit I don't use the filament functionality of DWC! I think there's a DWC filament json file that gets updated? However, you could save the filament name and tool number to a variable, and echo > those variable to a file, then load them at start up and run the appropriate filament config.

Ian

omtek

@fcwilt You set the name in DWC using the drop-down menu:

and you configure your filaments in the Filament section of DWC:

clicking on "New FIlament" will prompt you for a name

which will create the folder /filaments/<filament name>/ and empty config.g, unload.g, and load.g macros for you to use.

If you want to update the filament using a macro you'll have to echo > <your filament name> to filaments.csv; the value is stored at the end of the file. When you change the filament using DWC this file is updated automatically so your macro changes may be overwritten.

fcwilt

@omtek

Thanks for the feedback.

I've been without internet for a couple of days due to weather.

I found where the current filament info is kept.

I can take your idea and create a file to execute on startup to that will get things back in sync.

Thanks much.

Frederick

fcwilt

@droftarts

Thanks for the reply.

I believe I have a way to do what I want.

Frederick