Public Network Mode
- This topic has 2 replies, 2 voices, and was last updated 7 years, 7 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.
Lawrence Griffiths.
Lawrence GriffithsThe manual states
>> join windows open at the default 5/6 seconds after end of transmission for OTA
Does this happen automatically?
Or do you have to set a Dot using AT+JD=5 ??
What bearing does AT+JD have in public network mode?
The reason for asking is I’ve had problems with a number of dot’s joining when APE Conduit is set to public mode. Though 3rd party devices work perfectly.
I can see the the join response message in Debug it looks around 5 secs after join request. So set AT+JD=5 and that seems to have helped but not all the time.
Feel I’m shooting in the dark what’s the correct practice?
Thanks
Lawrence
Mike FioreLawrence,
If the mDot/xDot is set to public network mode using AT+PN=1 or mDot::setPublicNetwork(true), you should be good to go.
Just setting the join delay to 5 will not work because the sync words are different between public and private modes. Changing the join delay should only be done to match a gateway with non-standard delays between the packet reception and transmission of the response. This is not likely to be the case.
Cheers,
Mike
Lawrence GriffithsMike thanks am using AT+PN=1
Just starting dinging when I was seeing the join and packet_sent on MQTT on AEP but the Dot was failing to join.
Will go back to defaults.