#[SOLVED] T0 error
1 messages · Page 1 of 1 (latest)
Roadrune: For some reason the I am a potato.log was changed to i am a potato 😛
Roadrune: So i can not write I am a potato here?
You are using Happy Hare?
If that’s the case unfortunately you will have to get support from their discord
No, i am using AFC
Okay, you should not have a mmu.log
But i had HH installed previously, are there "leftovers" causing issues?
Did you filling uninstall HH as well as charging your slicer settings to match AFC?
Roadrune: I was told to attach afc.log to this post, but only found I am a potato.log
You must still have HH installed which will not work with AFC
I think so, i followed the instructions for uninstall from the HH Discord, and followed the setup guide for afc.
Do you know how i can check that?
I’m not exactly sure and unfortunately I can’t look through your log at the moment. <@&1304550334839918672> thoughts here?
Make sure you don't have their gcode processing running as well and any files that have been uploaded will need to be deleted and re-uploaded as the stuff that's already added to you gcode when uploaded could be causing some weird errors with AFC
You mean in the RPI itself?
I think i need more teaspoons here unfortunatly, i do not know how to check or fix anything of what you said, sorry.
Ok, i checked with the HH guys, and all traces should be gone, it seems the log files cannot be deleted, so that's why the .log is still there.
I was asked to upload the afc.log file, but that don't excist in my printer.
So for the initial T0 error, you are using an older version of the AFC software and need to update if you want to use passing in PURGE_LENGTH with the T0 command.
To update ssh into your PI
Navigate to AFC-Klipper-Add-On ex cd AFC-Klipper-Add-On
Then run ./install-afc.sh and select U twice to update
this is also why your AFC.log is not there since you are on an older software
Does this finish in a flash? It happened so quick i am not sure it did anything?
If you restart your printer what is the AFC version when it prints out, if it's still v1.0.0 then it didn't update
v1.0.4-5
Yup it updated
And it seemed to have fixed my issue. Thank you.
So this issue is now solved and can be marked as so?
Yes