Closed hynci117 closed 5 years ago
Can we know your test FW version?
The FW is 3.7
+VER=1.0.1,3.7,SM42
This sequence during init (setting default sleep and persisting in eeprom) causes the module to stop responding:
AT+VER
# +VER=1.0.1,3.7,SM42
OK
AT+DEFMODE=6 # OK
AT+PS=0,1 # OK
AT+WDCT # OK
AT+DEFMODE=0 # OK
From now the module does not respond to any command and needs to be reset by external pin.
I have tried as below commands
OK
"Press Enter on my keyboard to wake up SM42" +PS=0,1 OK
OK
OK
OK
OK
OK
After setting AT+DEFMODE=6, the module can still respond some AT commands like "AT+VER", "AT+ADDR" "AT+BAND". I will try your commands later on.
I tried for this twice, not found the module hang up. The first time===================
OK
+PS=0,1 OK
OK
OK
OK
OK
OK
the second time=================
OK
+PS=0,1 OK
OK
OK
OK
Above some error message is because key in the wrong commands, not impact the result.
Thanks for the update. The sequence you entered works for me too. But there is a difference, you sent AT+WDCT=0 which resets the eeprom insted of AT+WDCT which stores the current settings. The shortest sequence of commands to reproduce after module reset: AT+PS=0,1\r AT+WDCT\r AT+SLEEP\r AT\r (just to wake up) AT+DEFMODE=0\r no response after
OK
OK
+PS=0,1 OK
OK
OK
OK
OK
OK
OK
Re-tried your commands sequence, the hang up issue did not happen.
I am getting the problem consistently. I tried on two other modules and one is working okay, the second one hangs in a different way (not reaching the Tx Done). Can it be related to the state of the wake-up pin or other wiring problems related to soldering? (One of the faulty modules is on the original Nucleo shield) If not, I will regard the modules as faulty and we can close this.
I have tried this commands sequence on one Nucleo shield board without any change on the board, because there has only one shield board on hands. After enter sleep mode with "AT+SLEEP", I used with pressing "Enter" in my keyboard that input into the module through UART, is it same? Then I tried to set working mode.
Yes, that should be the same. It works for you?
The module still works after above commands sequence, not happened with any hang up.
Okay, lets asume it is a hardware related problem and close this. Thank you for helping me.
The issue is as follows:
after reset issue the AT+SLEEP command (the default mcu sleep mode is set to 1 - stop mode), response is:
wake modue with at command, response:
module is now in idle, set it to LoRa mode with AT+DEFMODE=6, response:
Now the module does not respond to any command. Am I missing something? Is there a workaround?