Using the Cinterion® PLS62‑W Wireless Module configuration file

Maximum size (in bytes) of the NV data TX queue. Default: 2048 bytes. If the queue size is exceeded, the oldest messages are dropped.

The default size is intended for devices sending small message payloads. Increase this amount if you are using devices that send large message payloads.

For large messages, you must ensure that the maximum NV store size is at least four times the largest expected published message size, plus eight bytes for the storage header. For example, for 1000 byte messages, set a minimum nvqueuemaxsize of 4032.

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

Operating mode, either:

mqtt

none (default)

Preferred technology for connecting to the cellular network, either:

2G – 2G only

LTE – LTE only

any (default) – either 2G or LTE

Modem firmware OTA image URL, either: http or https

If this parameter is not set, it is not included in the configuration file.

Application firmware update URL, either: http or https

If this parameter is not set, it is not included in the configuration file.

Host firmware update URL, either: http or https

If this parameter is not set, it is not included in the configuration file.

Configuration file update URL, either: http or https

If this parameter is not set, it is not included in the configuration file.

AWS jobs topics subscription and for processing jobs instructions, either:

0 – Do not subscribe to AWS jobs topics

1 (default) – Subscribe to AWS jobs topics

AWS shadow mode for reporting a set value to the device shadow/twin, either:

simple (default) – Report only the content of the state reported object

complete – Report the complete JSON data

off – Do not report a set value

For more information, see EMQPERSIST – report a set value to the device shadow .

MQTT client ID. This parameter is ignored when AnyNet SMARTconnect™ connects to Google IoT.

If this parameter is not set, it is not included in the configuration file.

LWT message for notifying subscribed clients about an unexpected loss of connection. To enable LWT, you must configure <mqttlwttopic> and <mqttlwtmessage>. Use:

<message> – the MQTT message that is discarded if the client disconnects gracefully

If this parameter is not set, it is not included in the configuration file.

Last will and testament (LWT) message QoS, defining the guarantee of message delivery. Either:

1 – the message is sent or delivered to the receiver one or more times

LWT message retained message flag, either:

0 (default) – message flag not enabled. This is a required setting for AWS only.

1 – message flag enabled

Last will and testament (LWT) topic path for notifying subscribed clients about an unexpected loss of connection. To enable LWT, you must configure <mqttlwttopic> and <mqttlwtmessage>. Use:

topic – the topic path

If this parameter is not set, it is not included in the configuration file.

Alternative to the AWS IoT shadow for configuring AnyNet SMARTconnect™ behaviour. Subscription to this single topic enables commands to be sent from the cloud broker to AnyNet SMARTconnect™ via MQTT. Use either:

topic – the subscribe topic title

Predefined topic for single-publish systems. The <topicsuffix> is not added as a suffix to the singlepubtopic name, however you can use a token instead.

If this parameter is not set, it is not included in the configuration file.

QoS for single publish, defining the guarantee of message delivery. Either:

1 – the message is sent or delivered to the receiver one or more times

Predefined topic for single subscription systems.

If this parameter is not set, it is not included in the configuration file.

Quality of Service (QoS) for single subscription, defining the guarantee of message delivery. Either:

1 – the message is sent or delivered to the receiver one or more times

Appends a topic path to the end of the requested topic to uniquely identify the thing on the broker.

thingname (default) – the cloud thingName

imei – the unique IMEI number for the device

none – the exact topic is used, with no suffix appended

If topicsuffix is not present in the configuration file, then thingname is appended on the requested topic.

For formatting URCs, either:

0 – sends all URCs as ASCII-hex within quotes

For example: '{"key1":"val1"}' will appear in a URC as '+EMQ:<id>,15\r\n"7B226B657931223A2276616C31227D"'

1 (default) – this option enables sending URCs as either ASCII-hex or text, depending on the received payload.

• If the received payload is printable text (including JSON), then the URC data is sent as text.

  For example:

  '{"key1":"val1"}' will appear in a URC as '+EMQ:<id>,15\r\n{"key1":"val1"}'

  For JSON, the maximum payload is 1012 characters. Escaped quotes count as 1 character: \"

• If the received payload is binary data, then the URC data is sent as ASCII hex.

UDP IP address

If this parameter is not set, it is not included in the configuration file.

For configuring SMS handling, either:

0 – SMS handling disabled

1 (default) – SMS handling enabled

For configuring location, either:

0 (default) – location disabled

1 – location enabled; Cinterion® PLS62‑W Wireless Module will always try to establish a GPS/GNSS location while running