The test command lists supported functional modes.
Response syntax:
+CFUN: (list of supported <fun>s)
The response parameters and their defined values are the following:
- <fun>
- 0 – Sets the device to minimum functionality. Disables both transmit and receive RF
circuits and deactivates LTE and GNSS services.
Note: A configuration made with an AT
command can be stored to
Non-volatile Memory (NVM) using
+CFUN=0 if the option is mentioned in the description of the
command. This is useful if the command relates to a permanent hardware configuration
because it avoids the need to give the command every time in the beginning of the
application.
Active %XPOFWARN warning blocks the storing to NVM.v1.3.x≥2
+CFUN=0 resets unsolicited notification
requests.
When setting the device to Minimum functionality mode, wait for
OK to make sure that NVM has been updated.
CAUTION:
+CFUN=0 causes writing to
NVM. When using +CFUN=0, take NVM wear into account.
- 1 – Sets the device to full functionality. Active modes depend on the
%XSYSTEMMODE setting.
- 2 – Sets the device to receive only functionality. Can be used, for example, to
pre-evaluate connections with %CONEVAL.v1.3.x
- 4 – Sets the device to flight mode. Disables both transmit and receive RF circuits and
deactivates LTE and GNSS services.
- 20 – Deactivates LTE without shutting down GNSS services.
- 21 – Activates LTE without changing GNSS.
- 30 – Deactivates GNSS without shutting down LTE services.
- 31 – Activates GNSS without changing LTE.
- 40 – Deactivates UICC.v1.1.x≥3v1.2.xv1.3.x
- 41 – Activates UICC.v1.1.x≥3v1.2.xv1.3.x
- 44 – Sets the device to flight mode without shutting down UICC.
The following command example returns the supported functional modes:
AT+CFUN=?
+CFUN: (0,1,4,20,21,30,31,40,41,44)
OK