Can no longer Join
- This topic has 2 replies, 2 voices, and was last updated 8 years, 9 months 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.
Home › Forums › Conduit: AEP Model › Can no longer Join
After some significant development efforts that were so far succesful (with mDot/UDK2 and Conduit/AEP) I reverted to the AT binaries to do some testing and now I cannot “join”.
I have prepared the mDot following Multitech’s tutorial:
at&f
at+ni=1,testnetwork
at+nk=1,testnetwork
at+fsb=1
at&w
atz
at+join
But the join returns a
"Join Error - Failed to join network
I’ve checked the settings on the Conduit – at least the ones matching the above settings and they match. I’ve tried a second mDot.
Any ideas?
Hmm…. what’s with the step:
atz
?
It clears all the values in the mDot now and when I try to join all the values have been reset: fsb=0, password is empty, etc.
I don’t recall this happening previously.
Michael,
I suspect there may be a problem with the external flash on your mDot. Can you see any error messages coming out the debug port when you start up the mDot running AT firmware?
The ATZ command does not reset the configuration but it does soft reset the system. If the filesystem on the external flash was unable to be mounted, it would look like the configuration was reset because the mDot would then revert to default configuration.
Cheers,
Mike