TheArchive/mayhem-firmware
1
0
Fork 0
mirror of https://github.com/portapack-mayhem/mayhem-firmware.git synced 2025-08-27 12:14:02 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated Dissecting the Temperature logger (markdown)

euquiq
2020-06-06 15:08:55 -03:00
parent 5195742103
commit 569e6db1c2
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
Dissecting-the-Temperature-logger.md

@@ -95,7 +95,7 @@ For our tests, we bypass the ºC conversion functionality in order to watch the
With our Portapack on, in iddle mode, the sensor **returns a value of 9** . If converted into ºC, such value should correspond to a temperature of about 0 / 1 ºC, which **seems to be wrong** (test room temperature is about 20ºC, and Portapack aluminium case is at about 26.7ºC).
### Second test
We place our Portapack in transmit mode, loop-playing a random earlier captured radio sample for about 30 minutes. The exterior aluminium case is at about 31.4ºC.
I placed my Portapack in transmit mode, loop-playing a random earlier captured radio sample for about 30 minutes. The exterior aluminium case is at about 31.4ºC.
Right after stopping the transmission, the sensor value is 10. We give it about 10 seconds and the value drops to 9. But Portapacks aluminium case is still abour 31.4ºC.
@@ -103,6 +103,9 @@ So, our observation indicates that MAX2832 temperature sensor is NOT giving out
At first glance, this sensor value **might** be the relative temperature change (increase) between ambient temperature (Which goes up when Portapack is transmitting, as evidenced on the aluminium case external measurement) and the MAX2837 temperature itself.
### Third test
I placed my Portapack outside, where it cooled down, for 30 minutes. Back inside, when powered up the sensor value was 7. About a minute later it increased by one, giving a value of 8. Portapack's case temp was about 20ºC
### Our second analysis
So what could be wrong ? We consider the following: