kjr

Well, After starting to disassemble the device, I think I found the problem! I first noticed that the batt sled screws were kinda loose. Pulled that out. Found the board is actually completely epoxy coated for protection (good), but no mounting screws on the board, as it's glued in, so not easily serviceable. So, after inspection, I put it back together and tightened the sled screws back down. Since then, with considerate use this weekend, the unit appears to be working just fine. I'm stoked! Not sure how those screws play a part in the chassis conductivity..........but all seems well now.

Thank you for the info and suggestions. I think the biggest challenge will be trying to find who/when I bought the mod. So many mods, so little receipts...... I have never dropped it. I cleaned the 510 (as suggested from initial searches on this matter). There was virtually no liquid on it. I'll pull the board and inspect. I highly doubt I'll find any ingress of liquid, and go from there. Thank you again, Chunky!

Thanks! Since my last reload of the firmware, I have not used the mod (2 days). Screenshot of DM shows shows really high temps.

EDIT: fix found and posted in #6 below. I have several DNA75 and 200 mods and have never seen this before. I have about 8 Freemax tanks tanks that I use in rotation all using the same .15 NI200 coils running between 38-45 watts on all my mods. The other day, after a few pulls, the mod read 'too hot'. The board shouldn't even have been much higher than ambient at that point. So, I plugged into escribe and the board was reading over 180F and room temp displayed 110F. It was about 68F outside. I tried soft reboot, nothing. Hard reboot, nothing. I was only successful in removing the error by updating the firmware (same version). I then went to use it, and again, after 5-6 pulls, it read TOO HOT. this has happened 4 times in a row now. I am not fully in-tune with escribe and its far reaching capabilities, as Iv'e only used it for basic programming changes. Does anyone have any knowledge of this, and a fix? Or, based on this just continuing to occur, is the board faulty? thanks,