My understanding was that each new Marlin firmware .bin build and flash (especially with M502+M500) flushes out any previous errors or conditions, but I had a MAXTEMP E1 error reboot/reset loop migrate from one SKR 1.4 to a new one even though I checked all hardware, thermistors, and used clean, rewritten Marlin files. I'm wondering if Marlin/ PlatformIO reuses or migrates error conditions from dependencies or otherwise even using fresh/clean Marlin files?
Complete story here:
I got a weird problem (a handful of related problem reported on Reddit) I've been trying to figure out for the week. My SKR 1.4 Turbo (correctly) posted THERMAL RUNAWAY/thermal errors several times, I had a frayed heater wire, eventually it wouldnt restart, stuck in reset MAXTEMP E1 loop.
I replaced heater rod and thermistor, tested resistance good, and I tried everything with firmware I could think to get it to boot past error, no go, so I got a new board SKR 1.4. USBed it to Pronterface, worked fine, then wired it up to printer, the MAXTEMP error came up again, I unplugged all hardware, reflashed it with clean Marlin, the only way I could get it to boot was to first #define dummy 25C 998 temp, showed 300C in PFace, so I defined MAX TEMP to 300C, then in Pronterface it posted that temp unmoving.
Tried multiple edits to any relevant firmware settings, pins files, M502 factory resets, SD card format, tested known working thermister, and could not get TH0 or TH1 (P0_23, P024) plugs to work, or anything other than 300C reported for HE temp. I'm assuming 300C is open circuit/max/same as no thermistor? I just tried clean installing VS Code, deleting all the dependencies, IDEs, And yes, I'm checking that each new firmware is indeed overwriting last, has the right time and date, and several attempts using clean Marlin files. I stopped short of messing with any temperature.h or thermistor.h files, those are outside my understanding.
My only guess is that somehow the error or bad temp calibration/offset got effectively hardcoded on the board, migrated somehow from last board to new one, via firmware?--Is that possible? Do you have any suggestions? I've been on the Marlin Discord spamming those poor guys for the last week trying to figure this out, theyve been super helpful, but so far no fix.
The only other remote possibility is that this brand new board arrived with a non-working TH1 and TH0 port (HB P0_25 TB works fine) OR the MKS MINI 12864 display board or its SD saves errors and migrates them.
Latest attempted fix involved uninstalling VB Code, PlatformIO no luck--might have to try VMWare virtual machine to eliminate any other sources.Thanks
Edited 3 time(s). Last edit at 05/22/2020 02:31AM by okolepuka.