WP7607-1 ULPS exit doesn't work

IoT Modules
1

`I’m working on WP7607-1 power management.

**- 1-**   I remark a lot of inconsistency in Sierra documentations :(, the last one is : 
in 4118047_WPx5xx-76xx-77xx AT Command Reference_r6.pdf  page 95, it is given that 
"<gpio> (GPIO to configure as wakeup source)
• 36—GPIO36
• 38—GPIO38
"
in AirPrime_WP76xx_Product_Technical_Specification_Rev7_2.pdf : 
Table 4-8:
--------------------------------------------------------------------------
Signal Configuration Signal   |
--------------------------------------------------------------------------
Configurable                  |           Timer
                              |           GPIO2, GPIO36, GPIO38, GPIO42
                              |           ADC2
                              |           ADC3
----------------------------------------------------------------------------
Always enabled                |         POWER_ON_N
----------------------------------------------------------------------------

What is the correct GPIOs capable to weekup module from ULPS state ?

2 It is impossible to configure module to weekup through Timer time out :
here is module response when I try to do this :
ATi3
Manufacturer: Sierra Wireless, Incorporated
Model: WP7607-1
Revision: SWI9X07Y_02.25.02.01 000000 jenkins 2019/01/30 08:13:05
IMEI: 359780080107141
IMEI SV: 6
FSN: VP811485670310
+GCAP: +CGSM
OK

AT!POWERWAKE=1,10
OK
AT!POWERWAKE?
!POWERWAKE:

OK

Why module does not take into account AT!POWERWAKE=1,10 command ?

Thanks

2

Please try:
at!powerwake=1,60
AT!powermode=3

the module will wake up after 1 minute.

3

I dont understand your command !!!
AT!powermode=3 means that the weekup source is ADC ! see 4118047_WPx5xx-76xx-77xx AT Command Reference_r6.pdf page 94 for more informations.

why should I set time to 60 if my need is 10 secondes ?

evenif I try 60 second :
AT!POWERWAKE=1,60
OK
AT!POWERWAKE?
!POWERWAKE:

OK

module does not take it into account .

4

AT!POWERMODE is on page 92.

at!powerwake=1,60
OK
AT!POWERWAKE?
[ 3182.975162] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x081343c8 OPER:0x00000090

!POWERWAKE:
Last Wake Event: 1

OK
ati3
Manufacturer: Sierra Wireless, Incorporated
Model: WP7608
Revision: SWI9X07Y_02.25.02.01 000000 jenkins 2019/01/30 08:13:05
IMEI: 352913090101013
IMEI SV: 6
FSN: XG805285330104
+GCAP: +CGSM

OK

5

Please can you explain why time out should be set to 60s ? in documentation page 94
“1–4294967—Timer duration in seconds”
so, the time out can take any value in range 1–4294967.

as I give in my last message even if I try 60 seconds, module dont take it in acccount

AT!POWERWAKE=1,60
OK
AT!POWERWAKE?
!POWERWAKE:

OK

in documentation page 94: response should be like this :
"
Query: AT!POWERWAKE?
Response (WP76xx/WP77xx):
!POWERWAKE:
[ ULPM TIMER: ]
[ PSM TIMER: , ACTIVE TIMER: <active_time> SYNC: ]
[ GPIOxx: ]
…
[ ADCx: , , ]
[ Last Wake Event: ]
OK
"

I use WP7607-1, you use WP7608

ATi3
Manufacturer: Sierra Wireless, Incorporated
Model: WP7607-1
Revision: SWI9X07Y_02.25.02.01 000000 jenkins 2019/01/30 08:13:05
IMEI: 359780080107141
IMEI SV: 6
FSN: VP811485670310
+GCAP: +CGSM
OK

6

i set to 60 seconds because I saw after AT!POWERMODE=3 , it needs some time to go to ULPM mode.
So I give it some buffer time.

Maybe you can give a try on WP7608.

7

Can you give a try on WP7607-1 ?

8

I don’t have WP7607, instead I tested on WP7609 (without SIM card).
After AT!POWERMODE=3, it will wake up after 1 minute.

BTW, you can also try AT!POWERMODE=1 and see if it works for your module.

9

Can I conclude that module WP7607-1 is not reliable ? or note respect commande AT specification ?

10

I m waiting for your feedbak.
We validating our technical choice, please can you find a way to make a try on 7607-1 module ?

11

How is your test result of at! powermode=1

12

Result is KO.
Result is KO.

13

No problem is found on WP7607.
Please see attached log.
log.txt (17.9 KB)

14

Please can you execute

AT!POWERWAKE=1,30
AT!POWERWAKE?
AT!powermode=3

and see if module responses as described on documentation ?

Our need is to put module into low power mode wich allow very quic weekup, ULPS is it the right mode for our need? can you give an example to do this please ?
let me tel you that the only used interface is AT command.

I m waiting for your help

Thaks

15

AT!powerwake=1,30 is not working , please use longer period of time.

16

I try
AT!POWERWAKE=1,60
when I ask module with :

AT!POWERWAKE?
!POWERWAKE:

OK

The module dont take 60s into account
Is this a documentation issue ? because documenation tells that module should respond as
!POWERWAKE:
ULPM TIMER: 60

17

i guess this will be fixed in future release.
But from my testing, I don’t see any problem to wake up after ULPM mode.

18

Our need is to put module into low power mode wich allow very quic weekup, ULPM is it the right mode for our need? can you give an example to do this please ?
let me tel you that the only used interface is AT command.

I m waiting for your help

19

you can also press the RESET button to wake up the module.

20

in this case module restart ! weekup time will be very long
Our need is to put module into low power mode wich allow very quic weekup, ULPM is it the right mode for our need? can you give an example to do this please ?
let me tel you that the only used interface is AT command.

I m waiting for your help