[WP7605]What is Minimum Functionality

I have a problem with Minimum Functionality.
After using the command “AT+CFUN=0”, the device enters the Minimum Functionality state, but does this have any impact on the operating efficiency of the device?
I raise this question because it sometimes takes more time to execute “AT!GSTATUS?” after executing “AT+CFUN=0” than after executing “AT+CFUN=1”.

after executing AT+CFUN=0, there is no meaning to type AT!GSTATUS? as telecom stack is off.

thank you for your answer!but I also want to know what it have done after executing “AT+CFUN=0” and “AT!GSTATUS?”, and why it takes more time to response the result. after executing “AT+CFUN=0”, the answer for " AT!GSTATUS?" is like this :
!GSTATUS:
Current Time: 5794 Temperature: 40
Modem Mitigate Level: 0 ModemProc Mitigate Level: 0
Reset Counter: 3 Mode: LOW POWER MODE

OK

at+cfun=0 is to turn off the telecom stack, and module will be enter low power mode as status in AT!GSTATUS.

Can you add the timestamp to show how much time is needed in your case for AT+CFUN=0 and AT!GSTATUS?

sorry to keep you waiting! the longest time to wait the response of “AT!GSTATUS?” is about15 seconds.

how to reproduce the issue?
I don’t see problem with WP7605 with FW R17:



[2023-09-05 22:29:23.037] ati3
[2023-09-05 22:29:23.521] Manufacturer: Sierra Wireless, Incorporated
[2023-09-05 22:29:23.521] Model: WP7605
[2023-09-05 22:29:23.521] Revision: SWI9X07Y_02.28.03.05 000000 jenkins 2019/07/08 11:04:16
[2023-09-05 22:29:23.521] IMEI: 353532100012345
[2023-09-05 22:29:23.521] IMEI SV:  6
[2023-09-05 22:29:23.521] FSN: 2A917285012345
[2023-09-05 22:29:23.521] +GCAP: +CGSM
[2023-09-05 22:29:23.521] 
[2023-09-05 22:29:23.521] OK
[2023-09-05 22:29:25.149] at+cfun?
[2023-09-05 22:29:26.686] +CFUN: 1
[2023-09-05 22:29:26.686] 
[2023-09-05 22:29:26.686] OK
[2023-09-05 22:29:27.293] at+cfun=0
[2023-09-05 22:29:29.076] OK
[2023-09-05 22:29:36.526] at!gstatus?
[2023-09-05 22:29:38.465] !GSTATUS: 
[2023-09-05 22:29:38.465] Current Time:  129		Temperature: 34
[2023-09-05 22:29:38.465] Modem Mitigate Level: 0		ModemProc Mitigate Level: 0	
[2023-09-05 22:29:38.465] Reset Counter: 1		Mode:        LOW POWER MODE 
[2023-09-05 22:29:38.465] 
[2023-09-05 22:29:38.465] OK

BTW, what is the meaning of typing AT!GSTATUS? after telecom stack is off?

I don’t know the meaning , too. Maybe it’s not a good idea to typing AT!GSTATUS? when AT+CFUN=0.
futhermore, it takes times to reproduce the issue, please type AT!GSTATUS? every 10 seconds. this phenomenon occurs by chance.

if there is no meaning to type AT!GSTATUS? when AT+CFUN=0, i don’t see the meaning to reproduce the problem

but there is a answer for AT!GSTATUS? when AT+CFUN=0, not error. does it mean there are any meanings? and what I want to know is why it sometimes takes more time to execute “AT!GSTATUS?”, or could you give me some materials about this problem or about “there is no meaning to type AT!GSTATUS? when AT+CFUN=0”? I need these to prove this problem’s reason and advancing the maintanence. thank you.

I think you will always get Low power mode for aT!GSTATUS? during AT+CFUN=0, right?

yes, we can get it from the interpretation for AT+CFUN=0 . but I can’t see any interpretation about what is the Low power mode.

probably you can search “Radio off” in the PTS to understand it

ah, does Low power mode mean Airplane mode?

you can try this:

//set to flight mode

at+cfun=4
OK
at!gstatus?
!GSTATUS:
Current Time:  73               Temperature: 31
Modem Mitigate Level: 0         ModemProc Mitigate Level: 0
Reset Counter: 1                Mode:        LOW POWER MODE

OK
at!pcinfo?
State: Low Power Mode
LPM voters - Temp:0, Volt:0, User:1, W_DISABLE:0, IMSWITCH:0, BIOS:0, LWM2M:0, OMADM:0, FOTA:0
LPM persistence - None

OK

but I have no idea what is the difference between AT+CFUN=0 and AT+CFUN=4

yes, it seems like that there is no difference between AT+CFUN=0 and AT+CFUN=4.

AT+CFUN=4
OK
AT!GSTATUS?
!GSTATUS:
Current Time:  1450             Temperature: 39
Modem Mitigate Level: 0         ModemProc Mitigate Level: 0
Reset Counter: 3                Mode:        LOW POWER MODE

OK
AT!PCINFO?
State: Low Power Mode
LPM voters - Temp:0, Volt:0, User:1, W_DISABLE:0, IMSWITCH:0, BIOS:0, LWM2M:0, OMADM:0, FOTA:0
LPM persistence - User:1

OK
AT+CFUN=0
OK
AT!GSTATUS?
!GSTATUS:
Current Time:  1496             Temperature: 39
Modem Mitigate Level: 0         ModemProc Mitigate Level: 0
Reset Counter: 3                Mode:        LOW POWER MODE

OK
AT!PCINFO?
State: Low Power Mode
LPM voters - Temp:0, Volt:0, User:1, W_DISABLE:0, IMSWITCH:0, BIOS:0, LWM2M:0, OMADM:0, FOTA:0
LPM persistence - User:1

OK

and the Current Consumption under Airplane mode is only 25 mA, will it affect AT command processing efficiency?

no idea, you can make some test on this flight mode

thank you for your patient answer. maybe I should find a way to ignore the long time spent on the response. :thinking: