PLS8-E: PWR_IND does not work as intended before first start [SOLVED] | Thales IoT Developer Community
June 27, 2018 - 8:46am, 1666 views
I have finally solved this issue.
WAKEUP from modem were connected to a GPIO not setup correctly so instead of an input it was undefined and happend to be high. Which caused some modems, but not all to act a bit crazy. PWR_IND went low as soon as WAKEUP went high. But after a start sequence on IGN, PWR_IND acted as expected when powering the modem both on and off.
I have seen that on some modules the PWR_IND signal does not work as intended.
I have to start the module once and after that PWR_IND works as expected.
PWR_IND is connected as the hardware interface description specifies.
Have anyone seen this? Is there a fix? Maybe even a firmware update that fixes this?