AT command bin file: one particular mDot acts differently…

[Michael]

I am using UDK2 developer boards and mDots (I have several of each). One mDot acts differently from the others.

The first mDot (mDot #1) I used seemed to act properly. I could (re)load the original AT .bin file from
https://webfiles.multitech.com/wireless/mtdot/mdot-firmware-1.0.8.bin
or compile & upload the AT source available through the online compiler.

After which I could hit the device through the terminal window with AT commands (over the Comm port) and it would respond.

However, a second mDot (mDot #2), which seems to accept the AT bin file fine (flashing LEDs just like with mDot #1), instead is stuck in some kind of mode in which it outputs on the Comm port the message:
Joining network...

Typing in the terminal window is fruitless.

I tried mDot #3 and it acts properly (like mDot #1)

What’s going on with mDot #2?

Thanks.

edit: fixed typo

[Michael]

OK, after a few minutes of playing with #3, it now acts like #2.

Why might this be?

[Bryan Tran]

Hi Michael,

Try +++ and hit Enter key and see if it helps ?

Thanks,

BT

[Michael]

That did it. I got “Command not found”, but control returned to the AT command set.

What was going on?

[Bryan Tran]

Hi Michael,

Did you set the mDOT in AUTO OTA mode (AT+NJM=2) ? If so, then you need to +++ to get out of that mode.

Thanks,

BT

[Michael]

Hi BT,

No, I did not issue that command. At least not deliberately.
I will try to query the device should this happen again.

b/r

Mike

[Michael]

The unit was in that mode, 2, (I queried AT+NJM?) , but I did not issue the command.

[Author]

Posts