![]() ![]() I got a friend to try and update his speccy but his is fine. So is this just some sort of API issue? I downloaded an old version of speccy and it seems to be displaying correctly. So what on earth could be causing such a bad temp spike? I even booted into the BIOS and my BIOS said my MB was like 26c! there's just no way it can be this hot.am I imagining things? I got this MB maybe like.in the summer? Juneish? so it can't possibly be broke can it? does anyone have any other suggestions for checking my temp? Same thing! if it matters I did dust/clean out my PC a few days ago and just gave it another quick clean just to make sure. If I remember correctly the older version of speccy didn't even come close to displaying it as that hot. Today I updated speccy and it said my MB was 114c! there's just NO way it can be that hot. (BIOS now updated to version 2003, release date ) I have followed the advice in post #1 and updated my BIOS to the latest version, but again this has not helped. I tried reinstalling Speccy (v1.29.714) and alternating the options from 'metric C' to 'Imperial F' but this did not fix the problem. The temperature display was correct before the Win10 update. The only unusual thing I have noticed is that Piriform Speccy is reporting an abnormally high temperature for the motherboard system temperature. I removed the heatsink and cleaned off the original thermal paste (which was somewhat crusty). So that leads me to believe it's a CPU seating issue (even though I used thermal paste to seat it two years ago when I built the machine) UPDATE 2 Well. I believe this is also called the "anniversary update"?Ī number of friends have posted that this update has caused them severe problems, so after it completed I have been checking my PC quite thoroughly. UPDATE 1 Temp is also just as high in BIOS. The fact you have to unplug the power connections tells me its the. However, it still is worth a try to reseat the processor in the socket and apply a fresh coat of thermal paste. Fantastic work.Last night Microsoft forced me (with only 10 mins notice!) to update my Windows 10 Home 64-bit to version 1607, build 14393.187. 'It will not turn back on before power connections are unplugged.' - This tells me the issue has absolutely nothing to do with the temperature of the processor. Uploads go perfectly every time from this Windows pc and other sketches I've loaded up just as I would expect in every way. This can help point to where the problem lies. Besides this odd issue with DHT sensors it works flawlessly. Try installing a different processor and see if the readings are still incorrect. Yet Im getting readings in the region of 47 Celsius from the MAX6675. The circuit board and the thermocouples are just sitting at ambient temperature on my desk (about 19 Celsius at the moment). However the actual temperatures indicated by the data are too high. I'm also entirely open to the option that I might be doing something stupid and take no offense to being shown where I'm in error. DHT11 readings are wildly inaccurate Issue 118 esp8266/Arduino GitHub. The data output from the MAX6675 is coherent and well formatted. Just let me know what will be most helpful. I will gladly recreate and further test the issue or provide any additional detail that might help with resolution. When using GPIO 3 (stealing from serial) the humidity is correct but the temperature is no different - still nothing close to a temperature.įorgive any lack of necessary detail here. When using GPIO 2 the reading is inaccurate for both temp and humidity. I've attempted on two different GPIO pins. Upon each receive of data from the DHT11 the values change drastically, by thousands. I've got a DHT11 sensor that reads correctly on an arduino nano but when used with the esp8266 arduino code it gives wildly inaccurate, rapidly changing values. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |