The 01-join sample application relies on the local module to handle joining. It does this by passing the fJoin flag = JOIN_YES, and supplying a semaphore to notify the application when the mote has joined.  Behind the scenes, the mote is using the joinDutyCycle parameter stored in its persistent parameter settings (default = 64 or 25%), and will listen continuously at this duty cycle until it joins a network.

An OCSDK application can control join behavior on its own by passing JOIN_NO and a NULL pointer for the join semaphore to the local module.  The 01-join_control illustrates using the application to control join behavior:

• It issues dnm_loc_joinCmd() to start the mote listening for a network
• It changes a