mDot AT Command program issue
- This topic has 2 replies, 2 voices, and was last updated 8 years ago by .
Viewing 3 posts - 1 through 3 (of 3 total)
Viewing 3 posts - 1 through 3 (of 3 total)
- You must be logged in to reply to this topic.
I have two mDots and a development board. Both mDots were supposed to be programmed for AT commands. One of the mDots worked as expected, and responded to the AT commands (over serial port from my computer), but the other wasn’t responding and I couldn’t see any output on the serial port. So I reflashed the mDot with the latest AT Command Firmware (3.0.0), and this got it working but not as I expected. It’s now running and sending output to the serial port, but it’s continually trying to join a network and not responding to AT commands on the serial port input. So it seems some other program is running inside the mDot’s MCU, but I don’t want to have to read through all the documentation to work out where it’s located just to reset to factory default. What’s the best method to reset the whole mDot module back to the basic AT Command mode that it shipped with?
Try entering the escape sequence +++
This should exit the join sequence of AT command mode if the device was configured AT+NJM=2
Then configure for regular join mode.
AT+NJM=1
AT&W
Otherwise the config can be erased from the bootloader.
Press enter directly after reset button is pushed in a debug port terminal.
bootloader :> erase lora.cfg
Perfect, thanks!