# Big STM32 boards topic

**URL:** <https://www.thethingsnetwork.org/forum/t/big-stm32-boards-topic/13391>\
**Category:** End Devices (Nodes)\
**Created:** [April 10, 2018, 7:21pm UTC](https://www.thethingsnetwork.org/forum/t/big-stm32-boards-topic/13391 "2018-04-10T19:21:26Z")\
**Posts on this page:** 1\
**Showing post:** 205

<div class="post-metadata">

**Author:** ![cslorabox](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/cslorabox/32/35697_2.png) [@cslorabox](https://www.thethingsnetwork.org/forum/u/cslorabox)\
**Post date:** [September 7, 2020, 8:06pm UTC](https://www.thethingsnetwork.org/forum/t/big-stm32-boards-topic/13391/205 "2020-09-07T20:06:30Z")

</div>

Part numbers are a help, but really it would take examining the actual implementation detail of schematic and software to find the fault.

Consider going around and evaluating each I/Os sleep level compared to any internal or external pulling resistors.

See if you can get the radio out of the circuit _entirely_ and measure the current without it.

Consider desoldering the accelerometer, or make sure you’ve gotten it into the right mode - I have one from another brand that consumes more current on power-on, and only hits low consumption when it’s been explicitly configured to the proper mode.

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/big-stm32-boards-topic/13391)._
