josh
/
Prusa-Firmware
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Partial fix for PFW-1334 

When a FSENSOR error happens, the first step for the MK3S should be to stop any loading by stopping the E-motor.

From this point, the buttons should determine what the MK3S does next.
This commit is contained in:
Guðni Már Gilbert 2022-06-25 09:13:39 +00:00 committed by D.R.racer
parent 2aa6cfc1ab
commit b8432e6bf2
1 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
Firmware/mmu2.cpp
View File

@ -733,6 +733,19 @@ void MMU2::ReportError(ErrorCode ec, uint8_t res) {
// - report only changes of states (we can miss an error message) // - report only changes of states (we can miss an error message)
// - may be some combination of MMUAvailable + UseMMU flags and decide based on their state // - may be some combination of MMUAvailable + UseMMU flags and decide based on their state
// Right now the filtering of MMU_NOT_RESPONDING is done in ReportErrorHook() as it is not a problem if mmu2.cpp // Right now the filtering of MMU_NOT_RESPONDING is done in ReportErrorHook() as it is not a problem if mmu2.cpp
// Depending on the Progress code, we may want to do some action when an error occurs
switch (logic.Progress())
{
case ProgressCode::FeedingToBondtech:
case ProgressCode::FeedingToFSensor:
// FSENSOR error during load. Make sure E-motor stops moving.
loadFilamentStarted = false;
break;
default:
break;
}
ReportErrorHook((uint16_t)ec, res); ReportErrorHook((uint16_t)ec, res);
if( ec != lastErrorCode ){ // deduplicate: only report changes in error codes into the log if( ec != lastErrorCode ){ // deduplicate: only report changes in error codes into the log