As part of the development of a product running on batteries and therefore in low power mode, I would like to know how to manage the abnormal DPM mode when there is no WIFI connection.
Indeed, when there is no connection, the abnormal DPM mode is launched. The DA16200 module tries to reconnect every 1 minute.
Is it possible to set the wake up period of the abnormal DPM mode to try to reconnect via AT commands?
Is it also possible to set a long period between wake-up / reconnection attempts? (for example every hour).
thank you for your answer but the command does not prevent reconnection attempts.
We have done it differently by performing a power down of the module if the connection fails.
If the device will be disconnected, you could try to use sleep mode 2.
According to the UM-WI-003 DA16200 DA16600 AT Command User Manual :
Abnormal DPM operation:
While DA16200 (DA16600) operates in DPM sleep, DA16200 (DA16600) executes an Abnormal DPM operation if DA16200 (DA16600) is in a “disconnected” state with the specified AP for some reason
Abnormal DPM works like this: DA16200 (DA16600) enters sleep with a predefined RTC timer (This is
called Abnormal DPM RTC Timer) configured if the AP connection fails. If DA16200 (DA16600) is woken up by the Abnormal DPM RTC timer, DA16200 (DA16600) tries to connect to the specified AP within a predefined period and sleeps again for a predefined time. The DA16200library provides default predefined values for Abnormal DPM, but users can modify the relevant parameters based on their application use case scenarios.
AT+SETSLEEP2EXT : Enter DPM Sleep 2 mode for the period specified
If you could provide more details regarding the application scenario, it would be very helpful to understand the use case.
Our product will detect the presence of an object and transmit the information via WIFI. The product works on batteries.
If the WIFI connection cannot be established or if there is a loss of connection, then it is necessary to enter in "sleep" mode and to try again periodically (let us admit every hour).
I tried to put the module in sleep 2 with a wake up period of 30 seconds (to test quickly) if the connection is not established but after the first wakeup the module does not go back to sleep.
I was thinking to do the sleep mode manually, meaning to turn off / on periodically the module directly by controlling its power supply.
Thanks for the description.
>>>I tried to put the module in sleep 2 with a wake up period of 30 seconds (to test quickly) if the connection is not established but after the first wakeup the module does not go back to sleep.
Could you please share the AT CMD sequence you are using? As far as I know, you are using the AT CMD.
Here is the sequence:
Thanks for sharing the AT CM sequence. We are working on this internally and will get back to you.
Could you please try to change the last AT CMD with that one and let us know?
after several tests, I conclude that the command AT+DPM=1,0 (or AT+DPM=1,1 it doesn't matter) doesn't pass after sending the command AT+SETSLEEP2EXT=30,1 because the module must already be in sleep 2 mode.
To solve my problem, I activated the DPM mode at the beginning of the program, without auto reboot, then finally if I have no wifi connection then I launch the command AT+SETSLEEP2EXT=30,1 and I have well a wake up then a sleep 2 periodically.
Here is the new sequence:
However, I have a new problem: the module does not wake up at all after having made 5 connection attempts (4 wake-ups).
we have reviewed our functional and finally the best thing would be to disable the automatic reconnection attempts so that we can manage it manually.
How to disable the periodic wake up and reconnection attempts in case of no connection to the AP?
I have an unwanted wakeup source 0x83 or 0x82.
Thanks for the reminder ( I was off for some days so perhaps I missed your last comment. Sorry!) Let me check this and will get back to you.
Hi Marty ,
Can you kindly try to disable the automatically connect when the MQTT is disconnected?
disable : AT+NWMQAUTO=0