Important changes to forums and questions
All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.
9 years ago.
(mDot can not save configurations) leave this question, it is working ;)
Hi,
please leave this question, it is working, i used public mode and get will get from gateway :)
I have one mDot with DEV KITs, when i changed the mDot Network Address, NSK and DSK as follow shows at+na=00000001 OK at+nsk=cb.75.96.1a.ae.fa.d1.23.ca.86.f1.dc.97.6f.28.10 OK at+dsk=0c.5c.3c.ff.d9.16.9b.fe.a6.0c.6c.29.b8.b6.34.59 OK at&w OK atz OK
but when i use the at&v to review my configuration, all of these three configuration become zero
--
at&v
Device ID: 00:80:00:00:00:00:9e:bc
Frequency Band: FB_915
Frequency Sub Band: 7
Public Network: off
Start Up Mode: COMMAND
Network Address: 00000000
Network ID: 2b:7e:15:16:28:ae:d2:a5
Network ID Passphrase:
Network Key: 2b.7e.15.16.28.ae.d2.a6.ab.f7.15.88.09.cf.4f.45
Network Key Passphrase:
Network Session Key: 00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00
Data Session Key: 00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00
Network Join Mode: OTA
---
is this normal? or there is a issue for mDot for the configuration save function?
Question relating to:
1 Answer
9 years ago.
Hi,
If you want to manually provision your mDot, it needs to be in MANUAL network join mode - yours is currently in OTA. That is why your configuration isn't sticking.
Cheers,
Mike