Quectel BG96 - Using the Quectel BG96 Module Configuration File

Using the Quectel BG96 module configuration file
The Eseye-enabled Quectel BG96 module operating parameters are contained in the configuration file,
which you can find here: /datatx/eseyeconfig.ini.
If this file does not exist, a backup configuration file is used instead: /datatx/eseyeconfig.bak. If neither
file exists, ETM uses internal default configuration parameters.
To display the contents of the current configuration file:
•
Send: AT+ETMCFG=show
To save the current configuration:
•
Send: AT+ETMCFG=save
For more information, see ETMCFG – read and write configuration file values on page33.
To update the configuration file over the air, see Updating the modem firmware using AWS
IoT jobs on page80.
You can deploy the configuration file using either: http, https, or tftp.
You can trigger an update using either SMS, MQTT, or AT command.
The .ini file is divided into sections, denoted by square brackets. Each section has parameters listed
underneath it.
Section Parameter Definition
[operation] Operational parameters
apptrace Application trace level (0-4), for Support purposes. Leave as 1
(default).
attrace AT command trace level (0-4), for Support purposes. Leave as 1
(default).
mode Operating mode, either:
mqtt
none (default)
nvqueue_enable The non-volatile memory NV queue is enabled by default to
prevent message loss during a power-cycle or reboot. Use:
0 – NV queue is not enabled
1 (default) – NV queue is enabled
nvqueuemaxsize Maximum size (in bytes) of the NV data TX queue. Default: 2048
bytes. If the queue size is exceeded, the oldest messages are
dropped.
Eseye-enabled Quectel BG96 module Developer Guide v1.8
62
Using the Quectel BG96 module configuration file