User's Manual

power and shortens battery life. If battery life is the priority of the application, the
expectation of MLDP throughput may be lowered.
Once MLDP is enabled, connection parameters are decided and an active link has
been established between central and peripheral, setting GPIO 4 high enters MLDP
mode. In MLDP mode, any data input from RN4020 UART will be sent wirelessly to
the peer device. To get out of MLDP mode, GPIO 4 must be set low. After existing
MLDP mode, RN4020 should be back to default command mode.
To ensure data stream between two RN4020 devices, both devices must enter MLDP
mode. On the other hand, user has the option to enter MLDP mode automatically
when receiving a MLDP message from the peer device by setting the
MLDP_ENABLE_RX bit in RN4020 features (Check command “SR” and section
3.2.1.12). When MLDP_ENABLE_RX bit is set, MLDP mode could be initiated from
one side of communication.
Besides controlled by GPIO 4, MLDP mode also could be entered by issuing
command.
3.3.5.3 I
Command “I” put RN4020 into MLDP simulation mode.
Command “I” is only effective under all of following conditions are met:
 Central and Peripheral devices have been connected.
 MDLP mode is enabled by command “SR” and takes effect after power cycle on
both RN4020 devices.
Once command “I” is issued, RN4020 enters MLDP mode and all data through UART
will be transmitted to the peer device wirelessly. The only way to get out of MLDP
mode is to assert low on GPIO 4.
Example : I // Enter MLDP mode
3.3.5.4 SE,<0-2>
Command SE set the security mode for MLDP communications. It expects one
parameter.
If the parameter is 0, no additional security is required.
If the parameter is 1, MLDP data over the air will be encrypted. Bonding is required
before MLDP service starts.