Fatal error - High chamber temperature - Suspect code found!

[peterb-aus]

Earlier this week we had a warmish day with a maximum of 38deg, It was a little hotter in the workshop with three printers going, a dryer, laptop and me soldering a broken pcb.

The ECC, running 0.3, stopped with a chamber overtemperature error, the screen locked up and needed a power off reset. The chamber temp reading was 38C when it restarted. I opened the door and lid, temp dropped a bit, and resumed the print OK.

The filament profile had chamber temperature set to 0C.

I've been printing with higher chamber temps with PA6CF, but only with official firmware, without incident.

My workaround, which has held up so far, is to set the chamber temp to 100C in the filament profile.

With that I get a warning message at a chamber temp of 38C, but the print keeps going.

Something funny going on with the handling of chamber temp. I checked the temp with a lab thermometer, the inbuilt thermistor is reading about 1.5 (one and a half) degrees C high, close enough for this sort of application.

My workshop can easily get to 50 on a hot day with the machines going, so I think it needs fixed. I'll put my hand up for this, I'm OK with code, but have no idea about how the development is organised.

[peterb-aus]

I'm sort of on the track of this. Could one of the devs please send me a copy of the printer configuration file, or point me at it. I think its in one of the macro definitions.

[suchmememanyskill]

see /board-resource/printer.cfg (which is derived from /app/resources/configs/printer.cfg)

[peterb-aus]

see /board-resource/printer.cfg (which is derived from /app/resources/configs/printer.cfg)

Thanks, but I can't find that. I'm new to github, my programming is from the days of FORTRAN, UPL and COBOL mainly, and I'm teaching myself Klipper

[suchmememanyskill]

On your CC filesystem, not on github.

[peterb-aus]

On your CC filesystem, not on github.

Thanks, got it now.

[peterb-aus]

The cabinet temperature sensor is defined in printer.cfg:

[temperature_sensor box]
sensor_pin : PB13
sensor_type : NTC 100K beta 3950
min_temp : -200
max_temp : 125

It seems to be called by .app, all four of them.

Any suggestions on how to look at app in a formatted fashion? Its a bit dense for notepad, and my best text editor won't run on win10, its a win3.1 program.

I found in app four references to EXTURDER, its not mentioned in any other file on the ECC. Surely a typo.

äm7 ,l7 exturder Requested temperature (%.1f) out of range (%.1f:%.1f)
PWM value : exturder pid kp: exturder pid ki: exturder pid kd: heater bed control is not pid

😆

[peterb-aus]

The warning message "High chamber temperatures may cause filaments to soften and lead to extruder clogs.", which is what I get with the chamber temp set to 100 in the filament profile, is in https://github.com/OpenCentauri/cc-firmware/blob/33e562eb1e973db5a4863037859351b48e4a8a2f/resources/e100/translation.csv#L317

I have not yet found where specific lines in that file are called from.

Any clues as to where to look? The code seems a little messy.

Happy New Year

[peterb-aus]

I finally found what I think is the problematic code. The trigger temperature is hard coded. It should be a variable from the filament profile.

In the Elegoo source file app_print.cpp starting at line 332

if((ss->heater_state[HEATER_ID_BOX].current_temperature > 39.) && material_switch)
{
anomalies_number++;
}
else
{
anomalies_number = 0;
}

if(anomalies_number == 5)
{
    app_msgbox_push(WINDOW_ID_ROUTINE_MSGBOX, true, app_print_routine_msgbox_callback, (void *)MSGBOX_TIP_BOX_TEMP);
    anomalies_number = 0;
    return false; // 检测结束
}

[peterb-aus]

I'll leave it to the code gurus to fix.

I did say I was good at finding bugs, never mentioned anything about fixing them,