Patrick.N Posted July 22, 2015 Author Report Share Posted July 22, 2015 Case analyzer results and differences compared to default settings, I will try and lift/mount my board up a millimeter or so from my casing and see if that helps Link to comment Share on other sites More sharing options...
John Posted July 22, 2015 Report Share Posted July 22, 2015 How long have you had this one running, out of curiosity? 23F/A seems okay, but running 46 degrees above ambient when idle is way too hot. Link to comment Share on other sites More sharing options...
Patrick.N Posted July 22, 2015 Author Report Share Posted July 22, 2015 It ran a few hours until it stopped, I'm currently lifting my board up a little bit so it doesn't rest flat at surface, can at least try and see Link to comment Share on other sites More sharing options...
John Posted July 22, 2015 Report Share Posted July 22, 2015 No, I believe the case analyzer results. I mean how long have you been running the DNA 200? Firmware prior to 7/9 could cause chip damage in rare circumstances that we've seen cause excessive heating, but if yours has never been run with firmware that early that would be cause for greater concern. Link to comment Share on other sites More sharing options...
Patrick.N Posted July 22, 2015 Author Report Share Posted July 22, 2015 Can see my exact timestamps in this image between installations, ran first firmware for a few days and upgrading when new builds to avail. Link to comment Share on other sites More sharing options...
Patrick.N Posted July 22, 2015 Author Report Share Posted July 22, 2015 I restored my board and software with latest firmware and pushed my board up a little bit from case.. still 0.09 charging and runs hot so can't really charge my battery anymore or longer than a few minutes before current drops, luckily i have an external lipocharger as well so I could charge it quickly after analyzingCurrent board temp is 145F Link to comment Share on other sites More sharing options...
John Posted July 22, 2015 Report Share Posted July 22, 2015 If you go into EScribe, go to help, go to About, then left click on the logo seven times, that will turn on debug options. After that, go into Device Monitor and see what your bandgap is reading. I bet it is reading high. Link to comment Share on other sites More sharing options...
Patrick.N Posted July 22, 2015 Author Report Share Posted July 22, 2015 Bandgap is 1.049v Link to comment Share on other sites More sharing options...
John Posted July 22, 2015 Report Share Posted July 22, 2015 Huh. I would have figured it would be higher. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now